Return to the Paced Motor Timing Task page
						
									  PACED MOTOR TIMING
SCRIPT INFO

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 06-17-2013
last updated: 02-03-2016 by K.Borchert (katjab@millisecond.com) for Millisecond Software LLC

Copyright © 02-03-2016 Millisecond Software


BACKGROUND INFO

											*Purpose*
This script implements a Paced Motor Timing procedure similarly to the one described in:

Wittmann, M., Leland, D.S., Jan Churan, J. & Paulus, M.P.(2007). Impaired time perception and motor timing
in stimulant-dependent subjects. Drug and Alcohol Dependence, 90, 183–192.

											  *Task*
participants are asked to synchronize keyboard clicks with a steady pacer signal of equally spaced beeps.
In condition A: pacer signal (beep) is played for all test trials.
In condition B: pacer signal (beep) is only played in the beginning.

Note: taps in this script are accepted before or after a beep is played.


DATA FILE INFORMATION: 
The default data stored in the data files are:

(1) Raw data file: 'PacedMotorTiming_raw*.iqdat' (a separate file for each participant)

build:							Inquisit build
computer.platform:				the platform the script was run on
date, time, subject, group:		date and time script was run with the current subject/groupnumber 
blockcode, blocknum:			the name and number of the current block
trialcode, trialnum: 			the name and number of the currently recorded trial
									(Note: not all trials that are run might record data; by default data is collected unless /recorddata = false is set for a paTIcular trial/block) 
/condition:						1 = pacer signal present until the end; 2 = pacer signal stops after a predetermined number of trials
/reps:							stores the number of pacer repetitions for the current block
/SOA:							stores the SOA for the current block
/response1:						stores the first registered response in a trial ("after beep"); for paced trials
/response2:						stores the second registered response in a trial ("before beep"); for paced trials
/altresponse:					used for debugging: stores any other response (but should never set)
/PrevRT:						stores the actual reaction time of the previous response (in ms)
/CurrRT:						stores the actual reaction time of the current response (in ms)
/NextRT:						stores the actual reaction time of the next response if applicable (in ms)
									Example: if tap for the next signal is given slightly before the next signal actually occurs
									the actual next reaction time will be something like 990ms (for SOA = 1000ms) BUT the deviation will be 10ms
/PrevResponse_dev:				stores the ms deviation of the previous tap									
/CurrResponse_dev:				stores the ms deviation of the current tap from the beep
/NextResponse_dev:				stores the ms deviation of the next tap IF tap was given slightly before the next tone was played
									Note: the next response is automatically converted to the current response for the next trial/tap
									and no other current response can occur
/countresponses:				a counter variable that counts all registered responses (should be 20, max.21 - otherwise participant simply pressed the Spacebar a lot or didn't press it enough)
/TI:   							TI = response/Tap Interval (time between taps); stores the length of the response interval in ms (ideal TI = SOA)
/start_TI:						stores the elapsed time of the script at the start of the response/tap interval in ms(RI)
/warning:						participant responded in a way that the script did not account for (please, let us know) (once set, it stays that way)

(2) Summary data file: 'PacedMotorTiming_summary*.iqdat' (a separate file for each participant)

script.startdate:				date script was run
script.starttime:				time script was started
script.subjectid:				subject id number
script.groupid:					group id number
script.elapsedtime:				time it took to run script (in ms)
computer.platform:				the platform the script was run on
/completed:						0 = script was not completed (prematurely aborted); 1 = script was completed (all conditions run)
/reps:							number of test trials (default: 20) Note: the start beep does not count towards this number
/valid_reps:					number of paced/unpaced trials used for summary statistics (default: the last 10 pacers/trials)
									Note: in condition B, the pacer signal does not play anymore for these trials
/SOA_1:							SOA 1 in ms (default: 1000ms) => SOA = Stimulus Onset Asynchrony
/SOA_2:							SOA 2 in ms (default: 2000ms)
/SOA_3:							SOA 3 in ms (default: 4000ms)
/meanToA_condA_SOA1-
/meanToA_condA_SOA3: 			mean TapOnsetAsynchrony (ToA) for conditionA for SOA1/SOA2/SOA3; based on the last 10 (default) trials
								(ToA = Deviation from pacer beep; includes all recorded deviations for the target trials)								
+ corresponding Standard Deviations								
																
/meanTI_condA_SOA1-
/meanTI_condB_SOA3:				mean Tap Interval (time intervals between taps) in ms based on the last 10 (default) intervals
+ corresponding Standard Deviations	

/InvalidDeviations_conditionA_SOA1-
/InvalidDeviations_conditionA_SOA3:		number of reactions (deviations > parameters.max_asynchrony) for the last 10 (default) test trials in condition A

/nrResponses_condA_SOA1-
/nrResponses_condB_SOA3:		stores the number of responses made in the different conditions (should be 20, max.21 - otherwise participant simply pressed the Spacebar a lot or didn't press it enough)

/warning:						participant responded in a way that the script did not account for (please, let us know) (once set, it stays that way)


EXPERIMENTAL SET-UP
- 2 pacing conditions (paced vs. unpaced) x 3 Stimulus Onset Asynchronies (SOAs: 1000ms, 2000ms, 4000ms)
- paced vs. unpaced tested in blocked format with paced conditions running first
- SOAs are sampled randomly within the pacing conditions

Paced Condition:
In the Paced Conditions deviations from the pacer signal are recorded. These deviations can occur (slightly) before or (slightly) after the
beeper signal. Additionally, number of invalidresponses (absolute deviations of 120ms from the pacer beep) and Response Tap Intervals 
(time intervals between taps) are recorded.

Unpaced Condition:
In the unpaced condition, only Response Tap Intervals are recorded (in the summary data file).

Note: If only a subset of the conditions should be run, go to section Experiment and follow instructions.
 
STIMULI
see section Editable Stimuli

INSTRUCTIONS
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:

/reps:							number of test trials (default: 20) Note: the start beep does not count towards this number
/valid_reps:					number of paced/unpaced trials used for summary statistics (default: the last 10 pacers/trials)
									Note: in condition B, the pacer signal does not play anymore for these trials
/SOA_1:							SOA 1 in ms (default: 1000ms) => SOA = Stimulus Onset Asynchrony
/SOA_2:							SOA 2 in ms (default: 2000ms)
/SOA_3:							SOA 3 in ms (default: 4000ms)
/max_asynchrony:				maximum absolute deviation in ms from pacer that that is considered a synchronous response (default: 120ms)
/pretrialpause:					the pause of the get-ready trial (default: 1000ms)

Copyright © Millisecond Software. All rights reserved.
Contact | Terms of Service | Security Statement | Employment