Return to the Affective Priming Procedure with Words page

						
							AFFECTIVE PRIMING - TEMPLATE with prime words and prime targets

SCRIPT INFO

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 06-09-2015
last updated: 01-30-2016 by K.Borchert (katjab@millisecond.com) for Millisecond Software LLC

Copyright © 01-30-2016 Millisecond Software


BACKGROUND INFO

											*Purpose*
This script implements a simple Affective Priming procedure with supraliminal word primes and word targets.
Not based on any particular published paradigm.


											  *Task*
Participants are asked to categorize affective target words into pleasant and unpleasant categories.
For baseline measures, a baseline supraliminal prime '***' precedes the target words.
For test measures, affective supraliminal word primes precede the target words.  


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

(1) Raw data file: 'AffectivePriming_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/groUP_testnumber 
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)
/primecategory:					Unpleasant vs Pleasant
/targetcategory:				Unpleasant vs Pleasant
/primeitemnumber:				stores the itemnumber of the currently presented prime
/prime:							stores the presented prime
/targetitemnumber:				stores the itemnumber of the currently presented target
/target:						stores the presented target
stimulusitem:					the presented stimuli in order of trial presentation
response:						the participant's response
correct:						the correctness of the response (1 = correct; 0 = incorrect)
latency: 						the response latency (in ms)


(2) Summary data file: 'AffectivePriming_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 (across baseline and test)
/meanRT:						overall mean correct latency in ms (across baseline and test)
/propcorrect_base:				proportion correct baseline trials
/meanRT_base:					mean latency (ms) of correct baseline trials
/propcorrect_test:				proportion correct test trials
/meanRT_test:					mean latency (ms) of correct test trials
/propcorrect_U_base:			proportion correct Unpleasant baseline trials
/meanRT_U_base:					mean latency (ms) of correct Unpleasant baseline trials
/propcorrect_P_base:			proportion correct Pleasant baseline trials
/meanRT_P_base:					mean latency (ms) of correct Pleasant baseline trials
/propcorrect_UU_test:			proportion correct test trials that pair Unpleasant primes with Unpleasant targets
/meanRT_UU_test:				mean latency (in ms) of correct test trials that pair Unpleasant primes with Unpleasant targets
/propcorrect_UP_test:			proportion correct test trials that pair Unpleasant primes with Pleasant targets
/meanRT_UP_test:				mean latency (in ms) of correct test trials that pair Unpleasant primes with Pleasant targets
/propcorrect_PU_test:			proportion correct test trials that pair Pleasant primes with Unpleasant targets
/meanRT_PU_test:				mean latency (in ms) of correct test trials that pair Pleasant primes with Unpleasant targets
/propcorrect_PP_test:			proportion correct test trials that pair Pleasant primes with Pleasant targets
/meanRT_PP_test:				mean latency (in ms) of correct test trials that pair Pleasant primes with Pleasant targets


EXPERIMENTAL SET-UP_test
2 affective primes (pleasant vs unpleasant) x 2 affective targets (pleasant vs unpleasant), tested within subjects

1. baseline ("practice"): 48 trials (all 48 targets) are tested with a baseline prime (***); targets are selected at random
2. test: 48 trials (all 48 targets); targets are selected at random
	- all 48 words occur once as prime and once as target
	- prime and target are never the same
	NOTE: in rare circumstances, the prime can be repeated to ensure that target and prime are not the same

Trialsequence:		Prime (200ms, editable) -> prime-target ISI (100ms, editable) -> Targets (until response; latency measured from onset of target)->ITI (2500ms)

STIMULI
Words are taken from:
Draine, S.C, & Greenwald, A.G. (1998). Replicable Unconscious Semantic Priming. Journal of Experimental Psychology: 
General, 127, 286-303.

INSTRUCTIONS
generic 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:

/baselineprime:								the symbols used for the baseline "prime"
/primeheight:								the size of the primes in % of canvas height (default: 5%)
/targetheight:								the size of the targets in % of canvas height (default: 5%)

/primeduration:								the duration of the primes in ms (default: 200ms)
/PT_ISI:									the duration of the prime-target interstimulus interval (default: 100ms)
/ITI:										the intertrial interval (default: 2500ms)

/responsekeyleft:							the scancode of the left response key (Note: by default, this is assigned to the Unpleasant category)
/responsekeyleft_label:						the label of the left response key (default: E)
/responsekeyright:							the scancode of the right response key (Note: by default, this is assigned to the Pleasant category)
/responsekeyright_label:					the label of the right response key (default: I)

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