___________________________________________________________________________________________________________________
FINGER TAPPING TEST (FTT)
___________________________________________________________________________________________________________________
Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
last updated: 10-01-2024 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC
Script Copyright © 10-01-2024 Millisecond Software
___________________________________________________________________________________________________________________
BACKGROUND INFO
___________________________________________________________________________________________________________________
This script offers an adaptation of the Finger Tapping Test (aka Finger Tapping Oscillation Test) - FTT- for the computer.
The FTT is a test of self-directed motor-speed.
More background information can be found under:
http://books.google.com/books?id=jQ7n4QVw7-0C&pg=PA1043&lpg=
PA1043&dq=Finger+Tapping+Test&source=bl&ots=F52XMBRtZ5&sig=
6fAZl7iCbkBccO4sws0OMiflUCk&hl=en&sa=X&ei=Pwn6ToKgKIrjiALoqdyhDg&ved=0CF0Q6AEwBg#v=
onepage&q=Finger%20Tapping%20Test&f=false
___________________________________________________________________________________________________________________
TASK DESCRIPTION
___________________________________________________________________________________________________________________
Participants are instructed to tap the SPACEBAR with either the index finger of their dominant or non-dominant hand
as often as they can within a 10s time period (=default). The 10s time period starts with the first tap.
Valid taps are those that occur within that 10s time period.
___________________________________________________________________________________________________________________
DURATION
___________________________________________________________________________________________________________________
the default set-up of the script takes appr. 7 minutes to complete
___________________________________________________________________________________________________________________
DATA FILE INFORMATION
___________________________________________________________________________________________________________________
The default data stored in the data files are:
(1) Raw data file: 'fingertapping_raw*.iqdat' (a separate file for each participant)
build: The specific Inquisit version used (the 'build') that was run
computer.platform: the platform the script was run on (win/mac/ios/android)
date, time: date and time script was run
subject, group: with the current subject/groupnumber
session: with the current session id
blockcode, blocknum: the name and number of the current block (built-in Inquisit variable)
trialcode, trialnum: the name and number of the currently recorded trial (built-in Inquisit variable)
Note: trialnum is a built-in Inquisit variable; it counts all trials run; even those
that do not store data to the data file.
response: response in the current trial (e.g. 57 = spacebar press)
dominanthand: whether the dominant (1) or the non-dominant hand (0) is tested
blockcount: keeps track of the number of blocks run for each hand
tapcount: counts the valid taps in each round (=score)
rank1-values.rank10 the ranking of the scores
ScoreDetermined: 1 = the final score was determined; 0 =otherwise
FinalScore the final score for the current hand
score_dominant: the final score for the dominant hand
score_nondominant: the final score for the non-dominant hand
restperiod: the duration of the restperiod after a round
parameters.maxdifference: the max difference in scores of the five scores used to calculate final score
parameters.blocklength: the duration of a block ("round") - after the first tap
(2) Summary data file: 'fingertapping_summary*.iqdat' (a separate file for each participant)
inquisit.version: Inquisit version run
computer.platform: the platform the script was run on (win/mac/ios/android)
startDate: date script was run
startTime: time script was started
subjectid: assigned subject id number
groupid: assigned group id number
sessionid: assigned session id number
elapsedTime: time it took to run script (in ms); measured from onset to offset of script
completed: 0 = script was not completed (prematurely aborted);
1 = script was completed (all conditions run)
score_dominant: the final score for the dominant hand
score_nondominant: the final score for the non-dominant hand
Note: see scoring information below
___________________________________________________________________________________________________________________
EXPERIMENTAL SET-UP
___________________________________________________________________________________________________________________
Scoring: Participants run through a mandatory number of 5 rounds (=blocks). The scores (=number of taps) get ranked from lowest to highest
If the scores of these 5 rounds are within 5 (=default) taps of each other, the final score is the mean tapping score.
If the score of these 5 rounds are not within 5 taps of each other, an additional block is run, until 5 scores can
be found that are within a 5-point range (checking starts from the 5 highest ranked scores to the lowest ranked scores).
The final score is the mean of these 5 scores.
The maximum number of rounds is 10. If no 5 scores can be found that are within a 5 point range from each other,
the final score is the mean of all 10 tapping scores. A separate score for the dominant and the non-dominant hand is kept.
Order: Testing starts with a practice round, followed by 5-10 testing rounds with the dominant hand and ends
after 5-10 rounds of testing with the non-dominant hand.
After each round of testing, participants receive feedback and get at least a 10s (=default) rest period.
After every 3 (=default) testing rounds, this resting period is increased to 60s (=default).
1. Practice Phase: 10s (Task: press the spacebar as many times as you can)
2. Test Phase 1: Dominant Hand
* runs minimum 5 blocks (10s each) and maximum 10
* after 5 blocks are run, the tapping counts are ranked and compared to each other: if 5 scores are are within 5 taps (default) of each other
the FinalScore is calculated. If the FinalScore is found, no more blocks are run for the current hand. If the
FinalScore is not found, an additional block is run. The Phase ends after max. 10 blocks.
If no five scores can be found that are within 5 taps of each other after 10 blocks, the average tapping count is used as the Final Score
2. Test Phase 2: Non-Dominant Hand
* runs minimum 5 blocks (10s each) and maximum 10
* after 5 blocks are run, the tapping counts are ranked and compared to each other: if 5 scores are are within 5 taps (default) of each other
the FinalScore is calculated. If the FinalScore is found, no more blocks are run for the current hand. If the
FinalScore is not found, an additional block is run. The Phase ends after max. 10 blocks.
If no five scores can be found that are within 5 taps of each other after 10 blocks, the average tapping count is used as the Final Score
___________________________________________________________________________________________________________________
STIMULI
___________________________________________________________________________________________________________________
see section Editable Instructions
___________________________________________________________________________________________________________________
EDITABLE CODE
___________________________________________________________________________________________________________________
check below for (relatively) easily editable parameters, stimuli, instructions etc.
Keep in mind that you can use this script as a template and therefore always "mess" with the entire code
to further customize your experiment.
The parameters you can change are:
maxdifference: the maximal difference between 5 consecutive scores (default is 5)
blocklength: determines the length of the block (default: 10s)
longrestperiod: determines how long the restperiod is after block3 (and block6)
regularrestperiod: determines the regular restperiod after a block
longrestperiodblock: determines after how many blocks there should be a longer restperiod (default: after every 3 testing blocks)
