Return to the Subliminal Priming Task page
						
									 SUBLIMINAL PRIMING PROCEDURE
SCRIPT INFO

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 04-25-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 the Subliminal Priming Procedure as described in:

Michael A. Olson, M.A. & Fazio, R.H. (2002). Implicit acquisition and manifestation of classically conditioned attitudes.
Social Cognition, 20, 89-103.

											  *Task*
After seeing an alphanumeric mask (that is very briefly "interrupted" by a subliminal prime), 
participants are asked to categorize adjectives as positive or negative.
Two primes are used that have been conditioned to be a positive and a negative CS in a prior study
(for more info on the conditioning part of the study see Olson & Fazio, 2002).


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

(1) Raw data file: 'SubliminalPriming_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 particular trial/block) 

/selectprime1:					store the assignment (itemnumber) of primes to prime1 and prime2
/selectprime2:
/targetindex:					stores the targetindex of the current target adjective
response:						the participant's response (scancode of response button)
correct:						the correctness of the response (1 = correct; 0 = incorrect)
latency: 						the response latency (in ms)
							
(2) Summary data file: 'SubliminalPriming_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)
/propcorrect:					overall proportion correct (test trials only)
/meanRT:						overall correct mean latency in ms (test trials only)
/meanRT_prime1pos:				correct mean latency (in ms) in Prime1-Positive Adjective Pairings
/meanRT_prime1neg:				correct mean latency (in ms) in Prime1-Negative Adjective Pairings
/meanRT_prime2pos:				correct mean latency (in ms) in Prime2-Positive Adjective Pairings
/meanRT_prime2neg:				correct mean latency (in ms) in Prime2-Negative Adjective Pairings
/propcorrect_prime1pos:			proportion correct in Prime1-Positive Adjective Pairings
/propcorrect_prime1neg:			proportion correct in Prime1-Negative Adjective Pairings
/propcorrect_prime2pos:			proportion correct in Prime2-Positive Adjective Pairings
/propcorrect_prime2neg:			proportion correct in Prime2-Negative Adjective Pairings


EXPERIMENTAL SET-UP:
* 2 primes (Shelder vs. Metapod) x 2 adjective valence (positive vs. negative) 
=> 4 experimental trial conditions
* 16 positive and 16 negative adjectives

Blocks:
1) Practice Block: runs 16 trials (8 with positive and 8 with negative adjectives) with a pseudo "prime" 
to achieve a similar "look" as the experimental trials (Olson and Fazio (2002) may not have used a pseudo "prime")
2) 2 Experimental Blocks of 32 trials: 
- across all 64 experimental trials, each prime is paired once with each of the 32 adjectives.
- all 32 adjectives are sampled ONCE during each block (no repeats); see LISTS for more details

Trials: stimulus durations taken from Olson & Fazio (2002)
- pre-mask consisting of a string of alphanumeric characters for 56ms
- followed by a prime for 28ms
- post-mask (same alphanumeric string) for 42ms
- 98ms later: adjective
=> timeline: 0ms: premask; 56ms: prime; 84ms: postmask; 126ms: postmask eraser; 224ms: adjective

STIMULI
most of the stimuli used in this script are not the originals; 
they can be edited under section Editable Stimuli

INSTRUCTIONS
the instructions used in this script are not originals;
they 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:

/fontheight:						sets the height of the font for all text stimuli (default: 5%)

Responsekeys:						good/bad response keys get assigned by groupnumber	
									more info under EXPERIMENT
/responsekey_left:					scancode of the left responsekey (default: 30)
/responsekey_leftlabel:				corresponding label of the left responsekey (default: "A")
/responsekey_right:					same for the right responsekey
/responsekey_rightlabel 

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