Return to the Inattentional Blindness Task (animation) page
___________________________________________________________________________________________________________________	

									INATTENTIONAL BLINDNESS- Computerized Input
										-with dynamically generated stimuli-
___________________________________________________________________________________________________________________

last updated:  03-12-2021 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC

Note: this script is based on An Raes' original inattentionalblindness.iqx script that collects
the input on paper and pencil
___________________________________________________________________________________________________________________
BACKGROUND INFO 	
___________________________________________________________________________________________________________________	
This script runs an Inattentional Blindness Task adapted from:

Most, S. B., Scholl, B. J., Clifford, E. R., & Simons, D. J. (2005). 
What you see is what you set: sustained inattentional blindness and the capture of awareness. 
Psychological review, 112(1), 217–242. https://doi.org/10.1037/0033-295X.112.1.217

___________________________________________________________________________________________________________________
TASK DESCRIPTION	
___________________________________________________________________________________________________________________
Participants view several animated displays that depict members of 4 shapes in white and black 
floating around in a field. The task is to count how often a certain kind of shape bumps into the walls.
At some point during the experiment, a target stimuli (here: a red X) moves through the space.
											  
___________________________________________________________________________________________________________________	
DURATION 
___________________________________________________________________________________________________________________	
the default set-up of the script takes appr. 5 minutes to complete

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

(1) Raw data file: 'dynamicinattentionalblindness_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
script.sessionid:				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 such as feedback trials
									
/focusDistractor:				the type of figure randomly selected to pay attention to (1-4)									
										
stimulusitem:					the presented stimuli in order of trial presentation
response:						the participant's response (scancode of response buttons)
latency: 						the response latency (in ms)

/fig1_borderCount-fig4_borderCount:	the computer counted bounces  

/notice_critical:				1 =participant noticed something during critical trial; 
								0 = otherwise
							
/response_critical:				contains the detailed description of the stimulus noticed during the critical trial


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

computer.platform:				the platform the script was run on (win/mac/ios/android)
script.startdate:				date script was run
script.starttime:				time script was started
script.subjectid:				assigned subject id number
script.groupid:					assigned group id number
script.sessionid:				assigned session id number
script.elapsedtime:				time it took to run script (in ms); measured from onset to offset of script
script.completed:				0 = script was not completed (prematurely aborted); 
								1 = script was completed (all conditions run)

values.notice_critical:			1 =participant noticed something during critical trial; 
								0 = otherwise
							
 values.response_critical:		contains the detailed description of the stimulus noticed during the critical trial

___________________________________________________________________________________________________________________	
EXPERIMENTAL SET-UP 
___________________________________________________________________________________________________________________
2 trials that present animated displays without target
2 trials that present animated displays with a target (here: red X) without target alert 
-> however, instructions at the end ask whether something unusual was noticed
1 trial that presents video with a target with explicit target alert 
___________________________________________________________________________________________________________________	
STIMULI
___________________________________________________________________________________________________________________
see section Editable Stimuli

Note: the animated displays are randomly created displays by the script.

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