User Manual: Inquisit Trail Making Test


___________________________________________________________________________________________________________________	

									      Trail-Making Test
										  (German instructions)
___________________________________________________________________________________________________________________	


Script Author: Sean Draine, Ph.D. (seandr@millisecond.com) for Millisecond Software, LLC
last updated:  09-30-2024 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC

Script Copyright © 09-30-2024 Millisecond Software

German translations provided by K. Borchert for Millisecond Software
___________________________________________________________________________________________________________________
BACKGROUND INFO 	
___________________________________________________________________________________________________________________	
This script implements a computerized version of the Trail-Making Test (4 trails included).
The trial making test is an executive function test of visual attention and task switching.

The script only runs on screens that are at least W:L = 118mm : 153mm
(Note: ios and Android devices force a vertical layout for this script)

References:
	
Armitages, S. G. (1946) An analysis of certain psychological rests used for the evaluation of brain injury. 
Psychological Monographs, 60, 1.
	
Reitan, R. M. (1958). Validity of the Trail Making Test as an Indicator of Organic Brain Damage. 
Perceptual and Motor Skills, 8, 271-276. 

___________________________________________________________________________________________________________________
TASK DESCRIPTION	
___________________________________________________________________________________________________________________
Participants are asked to move the mouse in specific, predetermined sequences from nodes to nodes.											  

___________________________________________________________________________________________________________________	
DURATION 
___________________________________________________________________________________________________________________	
the default set-up of the script takes appr. 5 minutes to complete
___________________________________________________________________________________________________________________	
DATA OUTPUT DICTIONARY
___________________________________________________________________________________________________________________
The fields in the data files are:

(1) Raw data file: 'trailmakingtest_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)

computer.touch:					1 = the current screen is a touchscreen; 
								0 = the current screen is not a touchscreen
									
date, time: 					date and time script was run 
subject, group: 				with the current subject/groupnumber
session:						with the current session id

//screen data:
screenOK:						0 = screen is not big enough (script should terminate); 1 = screen is big enough 
display.getmmx(display.width):	the width of the current screen in mm 
display.getmmy(display.height):	the height of the current screen in imm

//parameter settings:
parameters.runA:				true =  the script runs SampleA/Trail1
								false = the script does NOT runs SampleA/Trail1
										
parameters.runB:				true =  the script runs SampleB/Trail2
								false = the script does NOT runs SampleB/Trail2	


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 such as feedback trials. Thus, trialNum 
									may not reflect the number of main trials run per block.
																		
startDotNumber:					specifies the current dot that participant is on
targetDotNumber:				specifies the current dot that needs to be connected next
sampleAErrors:					counts the errors made on SampleA Trail
trail1Errors:					counts the errors made on Trail1
sampleBErrors:					counts the errors made on SampleB Trail
trail2Errors:					counts the errors made on Trail2

errorTrailSampleA-
errorTrailTrail2:				saves all missed circles in the order made for each trail separately

sampleATime:					time (in ms) spent on SampleA Trail
trail1Time:						time (in ms) spent on Trail1
sampleBTime:					time (in ms) spent on SampleB Trail
trail2Time:						time (in ms) spent on Trail2


(2) Summary data file: 'trailmakingtest_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)

computer.touch:					1 = the current screen is a touchscreen; 
								0 = the current screen is not a touchscreen

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)
								
//screen data:
screenOK:						0 = screen is not big enough (script should terminate); 1 = screen is big enough 
display.getmmx(display.width):	the width of the current screen in mm 
display.getmmy(display.height):	the height of the current screen in imm

//parameter settings:
parameters.runA:				true =  the script runs SampleA/Trail1
								false = the script does NOT runs SampleA/Trail1
										
parameters.runB:				true =  the script runs SampleB/Trail2
								false = the script does NOT runs SampleB/Trail2	

								
//summary data:
sampleAErrors:					counts the errors made on SampleA Trail
sampleATime:					time (in ms) spent on SampleA Trail
sampleBErrors:					counts the errors made on SampleB Trail
sampleBTime:					time (in ms) spent on SampleB Trail
trail1Errors:					counts the errors made on Trail1
trail1Time:						time (in ms) spent on Trail1
trail2Errors:					counts the errors made on Trail2
trail2Time:						time (in ms) spent on Trail2
combinedErrors:				adds errors made on all 4 trails
combinedTrailTime:				combines the time (in ms) it took all 4 trails

___________________________________________________________________________________________________________________	
EXPERIMENTAL SET-UP 
___________________________________________________________________________________________________________________	
This script runs 4 trails (sampleA, trailA, sampleB, trailB)

Note: this script allows researchers to selectively run only one of the tasks if needed.
Check Editable Parameters: parameters.runA and parameters.runB
By default, this script runs both tasks

___________________________________________________________________________________________________________________	
STIMULI
___________________________________________________________________________________________________________________	
are provided in the included scripts

___________________________________________________________________________________________________________________	
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:
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.

/showTestErrorFeedback:					true = a yellow halo is presented over the correct circle (default)
										false = no extra errorfeedback is given (incorrect path is still erased however)
										
/ runA:									true =  the script runs SampleA/Trail1
										false = the script does NOT runs SampleA/Trail1
										
/ runB:									true =  the script runs SampleB/Trail2
										false = the script does NOT runs SampleB/Trail2