Return to the Child IAT page
___________________________________________________________________________________________________________________	

								Child Implicit Attitude Test (IAT) - template
___________________________________________________________________________________________________________________	

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

Script Copyright © 03-13-2020 Millisecond Software

This script incorporates Inquisit code and materials generously provided by Dr. Andrew Scott Baron
into the general IAT framework offered by Millisecond Software LLC.  Appearance of the task,
as well as instructions and stimuli are Dr. Baron's originals (with minor edits).

Millisecond Software LLC thanks Dr. Baron for generously sharing his script and materials!

___________________________________________________________________________________________________________________
BACKGROUND INFO 	
___________________________________________________________________________________________________________________

The Implicit Association Task (Greenwald, McGhee, & Schwartz, 1998) is a widely-used cognitive-behavioral paradigm
that measures the strength of automatic (implicit) associations between concepts in people’s minds relying 
on latency measures in a simple sorting task.
 
The strength of an association between concepts is measured by the standardized mean difference score of 
the 'hypothesis-inconsistent' pairings and 'hypothesis-consistent' pairings (d-score) (Greenwald, Nosek, & Banaji, 2003). 
In general, the higher the d-score the stronger is the association between the 'hypothesis-consistent' pairings 
(decided by researchers). Negative d-scores suggest a stronger association between the 'hypothesis-inconsistent' pairings.

Inquisit calculates d-scores using the improved scoring algorithm as described in Greenwald et al (2003). 
Error trials are handled by requiring respondents to correct their responses according to recommendation (p.214).

D-scores obtained with this script:
Positive d-scores: support a stronger association between 'Flowers-Good' and 'Insects-Bad' than for the opposite pairings
Negative d-scores: support a stronger association between 'Insects-Good' and 'Flowers-Bad' than for the opposite pairings

References:
Greenwald, A. G., McGhee, D. E., & Schwartz, J. K. L. (1998). Measuring individual differences in implicit cognition: 
The Implicit Association Test. Journal of Personality and Social Psychology, 74, 1464-1480.

Greenwald, A. G., Nosek, B. A., & Banaji, M. R. (2003). Understanding and Using the Implicit Association Test: 
I. An Improved Scoring Algorithm. Journal of Personality and Social Psychology, 85, 197-216.


SPECIFIC SCRIPT INFO:
This script offers a template to run the IAT with children as young as age 5:

Baron, A. S., & Banaji, M. R. (2006). The development of implicit attitudes: Evidence of race 
evaluations from ages 6, 10 & adulthood. Psychological Science, 17, 53-58. 

See Baron & Banaji (2006) for description of specific response interface used with young 
children (two large USB buttons). For full instructions for administering the Child IAT to children
and other related material, please contact the first author.

The instructions embedded below are for adults (and older adolescents) to read when self-administering the task.

___________________________________________________________________________________________________________________
TASK DESCRIPTION	
___________________________________________________________________________________________________________________	
Participants are asked to categorize attributes (e.g. "joyful"; "tragic") and target pictures(e.g "daisy" vs. "wasp") 
into predetermined categories via keystroke presses. The basic task is to press a left key (E) if an item (e.g. "joyful")
belongs to the category presented on the left (e.g. "Good") and to press the right key (I) if the word (e.g. "tragic") 
belongs to the category ("Bad") presented on the right.
For practice, participants sort items into the target categories "Flowers vs. Insects" and the attribute categories "Good vs. Bad".
For the test, participants are asked to sort categories into the paired/combined categories (e.g. 
"Flower OR Good" on the left vs. "Insect OR Bad" on the right). Pairings are reversed for a second test 
(e.g. "Insects OR Good" on the left vs. "Flowers OR Bad" on the right). Order is counterbalanced by groupnumber.							  

___________________________________________________________________________________________________________________	
DURATION 
___________________________________________________________________________________________________________________	
the default set-up of the script takes appr. 5.5 minutes to complete

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

(1) Raw data file: 'childiat_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
										Note: odd/even groupnumbers balance the order in which 
										hypothesis-compatible/incompatible blocks are run
										odd = compatible - incompatible
										even = incompatible - compatible
										
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
										
conditionOrder:					c-ic: consistent -> inconsistent
								ic-c: inconsistent -> consistent
																													
response:						the response key pressed (e.g. 18 or 23)										
								Note: script saves the final and -by design- correct response for each trial
										
correct:						the accuracy of the initial response
										0 = initial response was incorrect and needed to be corrected
										1 = initial response is correct
										
latency:						the latency of the final (correct) response in ms; measured from onset of stim
stimulusnumber:					the number of the current stimulus
stimulusitem:					the currently presented item


Only meaningful for the last row of data in the raw data file (upon completion of IAT):

expressions.da:					d-score of the first short blocks
expressions.db:					d-score of the second long blocks

expressions.d:					overall d-score (non-weighted mean of the 2 d-scores); main DV

								Suggested Interpretation:

											D-score <= -0.65 => "a strong" preference for hypothesis-NONconforming pairings
											D-score < -0.35 => "a moderate" preference for hypothesis-NONconforming pairings
											D-score < -0.15 => "a slight" preference for hypothesis-NONforming pairings																						
											-0.15 <= D-score <= 0.15 "little to no" preference
											D-score > 0.15 => "a slight" preference for hypothesis-conforming pairings
											D-score > 0.35 => "a moderate" preference for hypothesis-conforming pairings
											D-score >= 0.65 => "a strong" preference for hypothesis-conforming pairings

expressions.percentcorrect:     the overall percent correct score of initial responses in test trials of D-score qualifying latencies

expressions.propRT300:			the proportion of response latencies < 300ms

expressions.excludeCriteriaMet:	1 = yes, exclusion supported per Greenwald et al (2003, p.214, Table 4):
								More than 10% of all response latencies are faster than 300ms
								0 = otherwise
									

(2) Summary data file: 'childiat_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)
								
conditionOrder:					c-ic: consistent -> inconsistent
								ic-c: inconsistent -> consistent								

expressions.da:					d-score of the first short blocks
expressions.db:					d-score of the second long blocks

expressions.d:					overall d-score (non-weighted mean of the 2 d-scores); main DV

								Suggested Interpretation:

											D-score <= -0.65 => "a strong" preference for hypothesis-NONconforming pairings
											D-score < -0.35 => "a moderate" preference for hypothesis-NONconforming pairings
											D-score < -0.15 => "a slight" preference for hypothesis-NONforming pairings																						
											-0.15 <= D-score <= 0.15 "little to no" preference
											D-score > 0.15 => "a slight" preference for hypothesis-conforming pairings
											D-score > 0.35 => "a moderate" preference for hypothesis-conforming pairings
											D-score >= 0.65 => "a strong" preference for hypothesis-conforming pairings

expressions.percentcorrect:     the overall percent correct score of initial responses in test trials of D-score qualifying latencies

expressions.propRT300:			the proportion of response latencies < 300ms

expressions.excludeCriteriaMet:	1 = yes, exclusion supported per Greenwald et al (2003, p.214, Table 4):
								More than 10% of all response latencies are faster than 300ms
								0 = otherwise
									
___________________________________________________________________________________________________________________	
EXPERIMENTAL SET-UP 
___________________________________________________________________________________________________________________

Hypothesis-consistent pairings vs. hypothesis-inconsistent pairings; tested within-subjects 
=> order is counterbalanced by groupnumber assignment

Sequence:
1. Target Category sorting training
2. Attribute sorting training
3. 1. Test Block of hypothesis-consistent* pairings with 20 trials (half the participant start with inconsistent pairings)
4. 2. Test Block of hypothesis-consistent pairings with 40 trials
5. Target Category sorting training with targets switching sides
6. 1. Test Block of hypothesis-inconsistent pairings with 20 trials
7. 2. Test Block of hypothesis-inconsistent pairings with 40 trials

In all Test Blocks:
* attributes and targets alternate
* attributes as well as targets are randomly selected without replacement

___________________________________________________________________________________________________________________	
STIMULI
___________________________________________________________________________________________________________________
Stimuli can be edited under section Editable Stimuli

___________________________________________________________________________________________________________________	
INSTRUCTIONS 
___________________________________________________________________________________________________________________
Instructions can be edited under 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:

/showsummaryfeedback:		set parameter showsummaryfeedback = true to display summary feedback to participants at the end 
							set parameter showsummaryfeedback = false if no summary feedback should be presented to participants (default)