Return to the Door Opening Task page
						
									DOOR OPENING TASK
SCRIPT INFO

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 12-12-2013
last updated: 01-08-2016 by K.Borchert (katjab@millisecond.com) for Millisecond Software LLC

Copyright © 01-08-2016 Millisecond Software


BACKGROUND INFO

											*Purpose*
This script implements the DoorOpeningTask as described in:

Matthys, W., van Goozen, S. H. M., de Vries, H., Cohen-Kettenis, P. T., & van Engeland, H. (1998). The Dominance 
of Behavioural Activation over Behavioural  Inhibition in Conduct Disordered Boys with or without Attention Deficit 
Hyperactivity Disorder.Journal of Child Psychology and Psychiatry, 5, 643–651.


											  *Task*
Participants are asked to open doors. Opening a door is either rewarded with 1 point that is added to the total winnings 
or punished by 1 point being subtracted from the total winnings. The number of winning doors decreases over the 
course of the experiment while the number of losing doors increases. Participants can quit the experiment at any 
point keeping the number of points earned up to this point.



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

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

build:								Inquisit build
computer.platform:					the platform the script was run on
date, time, subject:				date and time script was run with the current subjectnumber 
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) 
/nextoutcome:						stores the win/loss status of the current door
											1 = it's a win door
											0 = it's a loss door
response:							the participant's response (here: scancode of the response key)
/quit:								tracks whether participant has decided to quit
											0 = participant is still playing
											1 = participant has quit the game
latency: 							the response latency
/TotalScore:						tracks the total points earned (updated in trial.doorchoice)

summary variable:
/totalnumberdoors:					saves the total number of doors that could be potentially opened during the experiment
/count_opendoors:					tracks the number of doors openend.

(2) Summary data file: 'DoorOpeningTask_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; 1 = script was completed (all conditions run)

/skip_100percWin:					true = block.100perc_win is skipped (default)
									false = block.100perc_win is run
/skip_0percWin:						true = block.0perc_win is skipped (default)
									false = block.0perc_win is run
summary variable:
/totalnumberdoors:					saves the total number of doors that could be potentially opened during the experiment
/count_opendoors:					tracks the number of doors openend.



EXPERIMENTAL SET-UP:
1. Instruction Block
2. Block "100percent wins" (block.100perc_win) => optional; see editable value parameters.skip_100percWin
...
12. Block "0percent wins" (block.0perc_win) => optional, see editable value parameters.skip_0percWin

Each block potentially presents 10 doors with a pre-assigned win/loss ratio (see list.100perc_win - list.0perc_win)
=> within those 10 trials win/losses are randomly sampled (without replacement)

Matthys et al (1998) ran all 11 text blocks (max number of doors: 110) with a beginning credit of 0 points.
Win and Loss amount both equaled 1 point.

STIMULI
are provided by Millisecond Software; see section Editable Stimuli

INSTRUCTIONS
Instructions are not original and can be easily edited under section Editable Instructions
(Matthys et al, 1998, provide instructions on p.645).


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:

/responsekey_open:							scancode of the response key to open doors
												Note: scancodes under Tools -> Keyboard Scancodes (default: 57)
/responsekey_openlabel:						label of the response key (default: )

/responsekey_quit:							scancode of the response  key to quit (default: 16)
/responsekey_quitlabel:						label of the response key to quit (default: 'Q-key')

/feedbackduration:							default presentation duration of the win/loss door feedback screen (default: 1000ms)

/startcredits:								the number of points that participants start with (default: 0)
													Note: that's the amount specified in Matthys et al (1998)
/winamount:									the number of points that participants get for opening a win door (default: 1)
/lossamount:								the number of points that participants lose for opening a loss door (default: 1)

/skip_100percWin:							true = block.100perc_win is skipped 
											false = block.100perc_win is run (default)
/skip_0percWin:								true = block.0perc_win is skipped
											false = block.0perc_win is run  (default)

/present_feedbacksummary:					true = one the final page of the experiments, the total score is displayed (default)	
											false = one the final page of the experiments, the total score is Not displayed


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