___________________________________________________________________________________________________________________ *SUBLIMINAL PRIMING - Draine & Greenwald (1998)* *Batch Script* ___________________________________________________________________________________________________________________ Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC Date: 06-24-2013 last updated: 10-17-2023 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC Script Copyright © 10-17-2023 Millisecond Software ___________________________________________________________________________________________________________________ BACKGROUND INFO ___________________________________________________________________________________________________________________ This script implements a batch script to run a Subliminal Priming Procedure with adaptive response window. In general, priming procedures are simple response-timed binary categorization tasks of items from two target categories (e.g. positive vs. negative adjectives). Priming Procedures are based on the assumption that people respond faster if the target category was already 'mentally activated' by briefly presenting items (called 'primes') that are closely connected in one's mind. For example, a person should be faster to quickly categorize the target word 'good' as 'positive' after the brief presentation of the prime word 'ice-cream' than after the brief presentation of the prime word 'famine'. Priming Procedure can thus be used to study implicit attitudes. Faster reaction times to targets after primes from a specific category are interpreted as indicative of an existing relationship/association between the categories in the person's mind. If the primes are presented with a temporal duration that can be consciously processed, the primes are called 'supraliminal'. If the duration of the primes is so short that they are outside one's conscious awareness the primes are called 'subliminal'. This script uses subliminal primes. The implemented primining procedure in this script constraints response latencies to fall within a narrow response window. The default set-up uses response windows that are adaptive to people's speed performance. The implemented procedure is based on: Draine, S.C, & Greenwald, A.G. (1998). Replicable Unconscious Semantic Priming. Journal of Experimental Psychology: General, 127, 286-303. ___________________________________________________________________________________________________________________ TASK DESCRIPTION ___________________________________________________________________________________________________________________ Participants are asked to do 2 tasks. Task 1 (Indirect Measure, evaluation classification): Participants are asked to categorize target words (names) into negative/positive (male/female) categories. Targets are preceded by masked primes of 3 different prime durations. Participants are asked to respond within an adaptable response window. Primes can be either congruent or incongruent with the target category. (this procedure is run by script subliminalpriming_draine_im.iqjs) Task 2 (Direct Measure): Participants are asked to categorize masked primes (words/names OR letter strings of Xs and Gs) that appear for 3 different prime durations into words (names) or letter strings. Primes are followed by distractor words but participants are asked to ignore the distractors. (this procedure is run by script subliminalpriming_draine_dm.iqjs) Notes: (1) in this script -> odd groupnumbers run pleasant/unpleasant words; even groupnumbers run male/female names (2) default response keys are "A" and "L" A(left): unpleasant/male/XG string L(right): pleasant/female/word/name ___________________________________________________________________________________________________________________ DURATION ___________________________________________________________________________________________________________________ IM: Practice Sessions ~8 minutes IM: Test 6 blocks at ~2 minutes => ~12 minutes DM: Practice Session ~5 minutes DM: Test 6 blocks at ~2 minutes => ~12 minutes Total: ~37 minutes ___________________________________________________________________________________________________________________ DATA OUTPUT DICTIONARY ___________________________________________________________________________________________________________________ separate data files are generated for the Indirect Measure and the Direct Measure Task See 'subliminalpriming_draine_im.iqjs' and 'subliminalpriming_draine_dm.iqjs' ___________________________________________________________________________________________________________________ EXPERIMENTAL SET-UP ___________________________________________________________________________________________________________________ See 'subliminalpriming_draine_im.iqjs' and 'subliminalpriming_draine_dm.iqjs' ___________________________________________________________________________________________________________________ STIMULI ___________________________________________________________________________________________________________________ See 'subliminalpriming_draine_im.iqjs' and 'subliminalpriming_draine_dm.iqjs' ___________________________________________________________________________________________________________________ INSTRUCTIONS ___________________________________________________________________________________________________________________ See 'subliminalpriming_draine_im.iqjs' and 'subliminalpriming_draine_dm.iqjs' ___________________________________________________________________________________________________________________ *SUBLIMINAL PRIMING (Draine): INDIRECT MEASURE* ___________________________________________________________________________________________________________________ Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC Date: 04-22-2015 last updated: 09-30-2024 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC Script Copyright © 09-30-2024 Millisecond Software ___________________________________________________________________________________________________________________ BACKGROUND INFO ___________________________________________________________________________________________________________________ This script implements a Subliminal Priming Procedure with adaptive response window. In general, priming procedures are simple response-timed binary categorization tasks of items from two target categories (e.g. positive vs. negative adjectives). Priming Procedures are based on the assumption that people respond faster if the target category was already 'mentally activated' by briefly presenting items (called 'primes') that are closely connected in one's mind. For example, a person should be faster to quickly categorize the target word 'good' as 'positive' after the brief presentation of the prime word 'ice-cream' than after the brief presentation of the prime word 'famine'. Priming Procedure can thus be used to study implicit attitudes. Faster reaction times to targets after primes from a specific category are interpreted as indicative of an existing relationship/association between the categories in the person's mind. If the primes are presented with a temporal duration that can be consciously processed, the primes are called 'supraliminal'. If the duration of the primes is so short that they are outside one's conscious awareness the primes are called 'subliminal'. This script uses subliminal primes. The implemented primining procedure in this script constraints response latencies to fall within a narrow response window. The default set-up uses response windows that are adaptive to people's speed performance. The implemented procedure is based on: Draine, S.C, & Greenwald, A.G. (1998). Replicable Unconscious Semantic Priming. Journal of Experimental Psychology: General, 127, 286-303. Notes: by default this script runs with an adaptive response window with a center of 400ms after onset of target. To change the Response Window, check section 'Response Window' ___________________________________________________________________________________________________________________ TASK DESCRIPTION ___________________________________________________________________________________________________________________ Participants are asked to categorize target words (names) into negative/positive (male/female) categories. Targets are preceded by masked primes of 3 different prime durations. Participants are asked to respond within an adaptable response window. Primes can be either congruent or incongruent with the target category. Notes: (1) in this script -> odd groupnumbers run pleasant/unpleasant words; even groupnumbers run male/female names (2) default response keys are "A" and "L" A(left): unpleasant/male L(right): pleasant/female ___________________________________________________________________________________________________________________ DURATION ___________________________________________________________________________________________________________________ IM: Practice Sessions ~8 minutes IM: Test 6 blocks at ~2 minutes => ~12 minutes Total: ~20 minutes ___________________________________________________________________________________________________________________ DATA OUTPUT DICTIONARY ___________________________________________________________________________________________________________________ The fields in the data files are: (1) Raw data file: 'subliminalpriming_draineIM_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 session: with the current session id stimCategory: 1 = evaluation task; 2 = gender classification task task: Indirect Measure 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. Thus, trialNum may not reflect the number of main trials run per block. practicePhase: number of current practice phase (IM: 1-5) IM: 1 = phase 1 (only target practice); can be repeated 2 = phase 2 (masked prime); can be repeated 3 = phase 3A (introduction of Response Window: observation) 4 = phase 3B (introduction of Response Window: practice); phase 3 can be repeated 5 = phase 4 (practice the same as test trials; only congruent trials with primeDuration 50ms); phase 4 cannot be repeated 0 = test trials primeDuration: stores the current prime duration (1 = 17ms, 2=33ms, or 3=50ms) congruence: 1 = prime and target are congruent; 0 = prime and target are not congruent prime: stores the itemnumber of the current prime primeCat: stores the category of the current prime: 0 = unpleasant/male; 1 = pleasant/female imTarget: stores the itemnumber of the current target imTargetCat: stores the current target category: 0 = unpleasant/male; 0 = pleasant/female (Indirect Measure task) flagIMTarget: 1 = prime and target are the same; 0 = otherwise (Note:this should generally not happen) response: the participant's response (scancode of response button: 30(A)-left, 38(L)-right correctResponse: the correct scancode response for the current trial latency: the response latency (in ms) * Indirect Measure (IM) Trials: latency is measured from onset of target word * Direct Measure (DM) Trials: latency is measured from onset of prime inWindow: 1 = response in response window; 0 = response outside of response window (for relevant trials) correct: 1 = correct classification of the target; 0 = otherwise (independent of latency) response.windowProcedureTest.windowCenter: stores the current windowcenter in ms (center measured from target Onset) response.windowProcedureTest.windowWidth: stores the current width of the response window propInResponseWindowPerBlock: calculates the proportion of responses made during the response window (per block) propErrors: calculates the error proportion in a block meanRT: calculates the mean reaction time (in ms) in a block (correct and incorrect responses) stimulusItem: stimuli presented (in order) Prime -> stimulusitem 4; targetdistractor -> stimulusitem 7 (2) Summary data file: 'subliminalpriming_draineIM_summary*.iqdat' (a separate file for each participant) inquisit.version: Inquisit version run computer.platform: the platform the script was run on (win/mac/ios/android) startDate: date script was run startTime: time script was started subjectId: assigned subject id number groupId: assigned group id number sessionId: assigned session id number elapsedTime: time it took to run script (in ms); measured from onset to offset of script completed: 0 = script was not completed (prematurely aborted); 1 = script was completed (all conditions run) stimCategory: 1 = evaluation task; 2 = gender classification task imPercentCorrect: percent correct within IM task (across testblocks) -> correct: classified target correctly imMeanRT: meanRT in ms (for correct and incorrect responses) in IM task (across testblocks) * IM Trials: latency is measured from onset of target word imRhit17: the hit rate for the IM task: a hit is defined as a "pleasant" (female) response after a "pleasant" (female) prime; for primeDuration 17ms imRFA17: the False Alarm rate for the IM task: a FA is defined as a "pleasant" (female) response after a "unpleasant" (male) prime; for primeDuration 17ms imSignalTrialCount17: counts all trials across IM testblocks that present a category2 prime (pleasant, female) -> signal trials; for primeDuration 17ms imSignalTrialCount17: counts all trials across IM testblocks that present a category1 prime (unpleasant, male) -> noise trials; for primeDuration 17ms imHit17: number of hits (indirect measure): how often a female/pleasant judgment is made with a female/pleasant prime; for primeDuration 17ms Note: response does not have to be correct to be a hit imFA17: number of false alarms (indirect measure): how often a female judgment is made with a maleunpleasant prime; for primeDuration 17ms (same for primeDuration 33ms, 50ms) __________________________________________________________________________________________________________________ EXPERIMENTAL SET-UP OF INDIRECT MEASURE: EXPERIMENTAL BLOCK ___________________________________________________________________________________________________________________ * 6 Blocks of 50 trials => 300 trials total * across the 300 trials: - 12 trialtypes: 2 primes (pleasant vs. unpleasant) x 2 targets (pleasant vs. unpleasant) x 3 primeDurations => order is randomly determined => each trialtype runs 25 times => each prime duration is presented equally often => half the trials are congruent (prime and target come from the same category, e.g. both are pleasant) the other half is incongruent (prime and target come from different categories) => each prime is equally often presented at each prime duration (each prime is used once in each of its 6 possible trialtypes: e.g. 'lucky' can be used in trials pp17, pp33, pp50, pu17, pu33, pu50) * per block: - each block runs min. 4 repetitions of each trialtype (max. 5); order randomly determined - each block runs each word as a prime once - each block attempts to run each word as a target once (violations can occasionally occur, see below) - primes and targets are never the same !!! NOTE: the no-repeat sampling process for targets can be overridden for targets to ensure that primes and targets are never the same (in this case, a previously presented target can be presented twice) Indirect Measure Trial Sequence (*Note: the trial sequence uses refresh frames instead of times (on a 60Hz Monitor, 1 vertical frame ~ 16.67ms)) forward mask (for ~150ms) -> PRIME (~17, ~33, ~50ms - tested within-block) -> backward MASK (~17ms) -> 67ms after onset of prime: target ->wait for response (latencies are measured from target onset on) -> target erased after 183ms -> initial response window: 334ms after onset of target, a black exclamation point appears to indicate the start of the response window (initial response window: center = 400ms, width = 133ms) *If response happens within specified Response Window: black ! changes to red ! for 300ms *If response happens before specified Response Window: no ! appears *If response happens after specified Response Window: black ! disappears without ever changing color 600ms after each response the next trial (sequence) is started. => RESPONSE WINDOW starts by default ~334ms after onset of target with a response window center = 400ms and width = 133ms. RESPONSE WINDOW ADJUSTMENT RULES: if adaptive RW is used: updates the response window at the end of a block (after 50 trials) if applicable => increases RW if errorrate is above the acceptable rate AND mean latencies are lower than the acceptable limit (default: errorrate greater or equal to 0.45 AND mean latency > windowcenter + 100ms) => decreases RW if errorate is acceptably low AND latencies are acceptably low (default: errorrate less or equal to 0.2 AND mean latency <= windowcenter + 100ms) => in any other case no changes to RW are made Note: Adjustments made to the adaptive response window based on performance during a block that runs the response window procedure apply to all subsequent blocks that run the same response window procedure. Thus, in this script practice and test blocks run a different response window procedure element so that potential effects of practice performance do not carry over to the test blocks (see section RESPONSE WINDOW PROCEDURE ELEMENTS) IM PRACTICE phase 1 (only target practice); 20 trials; can be repeated phase 2 (masked prime); 50 trials x 2; can be repeated phase 3A (introduction of Response Window: observation); 5 trials phase 3B (introduction of Response Window: practice); 15 trials; phase 3 (all 20 trials) can be repeated phase 4 (practice the same as test trials; only congruent trials with primeDuration 50ms); 50 trials; phase 4 cannot be repeated ___________________________________________________________________________________________________________________ STIMULI ___________________________________________________________________________________________________________________ from Draine & Greenwald (1998) odd groupnumbers run: evaluation stimuli (pleasant/unpleasant) see: subliminalpriming_draineIMEvaluationstims.iqjs even groupnumbers run: gender stimuli (female/male), see: subliminalpriming_draineIM_genderstims.iqjs ___________________________________________________________________________________________________________________ INSTRUCTIONS ___________________________________________________________________________________________________________________ instructions are not the originals. 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. The parameters you can change are: General Adjustments: /fontHeight: height of the stimuli font used (default: 5%) /responseKeyLeft: left responsekey (default: A) /responseKeyRight: right responsekey (default: L) Duration Adjustments: / getReadyDuration: duration (in ms) of the get-ready-trial /iti: intertrialinterval: the time between response and next forward mask (default: 600ms) ___________________________________________________________________________________________________________________ *SUBLIMINAL PRIMING (Draine): DIRECT MEASURE* ___________________________________________________________________________________________________________________ Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC Date: 04-22-2015 last updated: 09-30-2024 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC Script Copyright © 09-30-2024 Millisecond Software ___________________________________________________________________________________________________________________ BACKGROUND INFO ___________________________________________________________________________________________________________________ In general, priming procedures are simple response-timed binary categorization tasks of items from two target categories (e.g. positive vs. negative adjectives). Priming Procedures are based on the assumption that people respond faster if the target category was already 'mentally activated' by briefly presenting items (called 'primes') that are closely connected in one's mind. For example, a person should be faster to quickly categorize the target word 'good' as 'positive' after the brief presentation of the prime word 'ice-cream' than after the brief presentation of the prime word 'famine'. Priming Procedure can thus be used to study implicit attitudes. Faster reaction times to targets after primes from a specific category are interpreted as indicative of an existing relationship/association between the categories in the person's mind. If the primes are presented with a temporal duration that can be consciously processed, the primes are called 'supraliminal'. If the duration of the primes is so short that they are outside one's conscious awareness the primes are called 'subliminal'. This script uses subliminal primes. This script runs the Direct Measure Task of Draine & Greenwald (1998). In the Direct Measure Task, participants are explicitly told to try to pick up information about the prime even though the primes are presented so fast that they might think they didn't see them. Draine, S.C, & Greenwald, A.G. (1998). Replicable Unconscious Semantic Priming. Journal of Experimental Psychology: General, 127, 286-303. ___________________________________________________________________________________________________________________ TASK DESCRIPTION ___________________________________________________________________________________________________________________ Participants are asked to categorize masked primes (words/names OR letter strings of Xs and Gs) that appear for 3 different prime durations into words (names) or letter strings. Primes are followed by distractor words but participants are asked to ignore the distractors. Notes: (1) in this script -> odd groupnumbers run pleasant/unpleasant words; even groupnumbers run male/female names (2) default response keys are "A" and "L" A(left): XG string L(right): word/name ___________________________________________________________________________________________________________________ DURATION ___________________________________________________________________________________________________________________ dm: Practice Session ~5 minutes dm: Test 6 blocks at ~2 minutes => ~12 minutes Total: ~17 minutes ___________________________________________________________________________________________________________________ DATA OUTPUT DICTIONARY ___________________________________________________________________________________________________________________ The fields in the data files are: (1) Raw data file: 'subliminalpriming_draineDM_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 (winmaciosandroid) date, time: date and time script was run subject, group: with the current subject/groupnumber session: with the current session id task: Direct Measure 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. Thus, trialNum may not reflect the number of main trials run per block. stimCategory: 1 = evaluation stims 2 = gender stims practicePhase: number of current practice phase (1-3) 0 = phase 1 (red, unmasked primes with primeDuration = 50ms); can be repeated 1 = phase 2 (red, masked primes with primeDuration = 50ms); can be repeated 2 = phase 3 (black, masked primes with primeDuration = 50ms); can be repeated 99 = test trials primeDuration: stores the current prime(wordstring)duration (1 = 17ms, 2=33ms, or 3=50ms) congruence: empty = not applicable in this script prime: stores the itemnumber of the current prime primeCat: stores the category of the current prime: 0 = unpleasant/male; 1 = pleasant/female dmTrialType: 1 = WORD; 2 = XG string (in dm task) dmDistractor: stores the itemnumber of the current dmDistractor response: the participant's response (scancode of response button: 30(A)-left, 38(L)-right correctResponse: the correct scancode response for the current trial latency: the response latency (in ms); latency is measured from onset of prime correct: 1 = correct classification of the red prime; 0 = otherwise expressions.propErrors: calculates propErrors in a block expressions.meanRT: calculates the mean reaction time (in ms) in a block (correct and incorrect responses) stimulusItem: stimuli presented (in order) Prime -> stimulusitem 4; targetdistractor -> stimulusitem 7 (2) Summary data file: 'subliminalpriming_draineDM_summary*.iqdat' (a separate file for each participant) inquisit.version: Inquisit version run computer.platform: the platform the script was run on (win/mac/ios/android) startDate: date script was run startTime: time script was started subjectId: assigned subject id number groupId: assigned group id number sessionId: assigned session id number elapsedTime: time it took to run script (in ms); measured from onset to offset of script completed: 0 = script was not completed (prematurely aborted); 1 = script was completed (all conditions run) stimCategory: 1 = evaluation stims 2 = gender stims dmPctCorrect: percent correct within dm task (across testblocks) -> correct: classified prime correctly as word or XG string dmMeanRT: meanRT in ms (for correct and incorrect responses) in dm task (across testblocks) * dm Trials: latency is measured from onset of prime dmHitRate17: the hit rate for the dm task: a hit is defined as a "word response" for a word prime; for primeDuration 17ms dmFARate17: the False Alarm rate for the dm task: a FA is defined as a a "word response" for a string prime; for primeDuration 17ms dmSignalTrialCount: counts all trials across dm testblocks that present a word target -> signal trials; for primeDuration 17ms dmNoiseTrialCount: counts all trials across dm testblocks that present a string target -> noise trials; for primeDuration 17ms dmHit17: number of hits (direct measure): how often a word is identified as a word; for primeDuration 17ms dmFA17: number of false alarms (direct measure): how often a string is identified as a word; for primeDuration 17ms (same for primeDuration 33ms, 50ms) ___________________________________________________________________________________________________________________ EXPERIMENTAL SET-UP OF DIRECT MEASURE: EXPERIMENTAL BLOCK ___________________________________________________________________________________________________________________ * 6 Blocks of 50 trials => 300 trials total * across the 300 trials: - 12 trialtypes: 2 primes (pleasant/unpleasant) x 2 prime formats (word vs. xg string) x 3 primeDurations => order is randomly determined => each trialtype runs 25 times => each prime duration is presented equally often => 1/2 the trials are word trials (150), 1/2 trials are xg string trials (150) => each prime is equally often presented at each prime duration => two consecutive blocks run the 50 prime stimuli * across 2 consecutive blocks: across 100 trials - each stimulus is called once as a prime - each trialtype is sampled min. 8 times (max. 9) - Primes and distractors are never the same !!! NOTE: the no-repeat sampling process can be overridden for targets to ensure that primes and targets are never the same Direct Measure Trial Sequence: forward mask (for 150ms) -> PRIME (17, 33, 50ms - tested within-block) -> backward MASK (17ms) -> 67ms after onset of prime: distractor *Response latency is measured from onset of prime *Note: the trial sequence uses refresh frames instead of times (on a 60Hz Monitor, 1 vertical frame ~ 16.67ms) *No Response Window is used for Direct Measure dm PRACTICE phase 1 (red, unmasked primes with primeDuration = 50ms); 30 trials; can be repeated phase 2 (red, masked primes with primeDuration = 50ms); 30 trials; can be repeated phase 3 (black, masked primes with primeDuration = 50ms); 30 trials; can be repeated ___________________________________________________________________________________________________________________ STIMULI ___________________________________________________________________________________________________________________ from Draine & Greenwald (1998) odd groupnumbers run: evaluation stimuli (pleasant/unpleasant) see: subliminalpriming_draineDM_evaluationStims.iqjs even groupnumbers run: gender stimuli (female/male), see: subliminalpriming_draineDM_genderstims.iqjs ___________________________________________________________________________________________________________________ INSTRUCTIONS ___________________________________________________________________________________________________________________ see section Editable Instructions ___________________________________________________________________________________________________________________ INSTRUCTIONS ___________________________________________________________________________________________________________________ instructions are not the originals. 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. The parameters you can change are: General Adjustments: /fontHeight: height of the stimuli font used (default: 5%) /responseKeyLeft: left responsekey (default: A) /responseKeyRight: right responsekey (default: L) Duration Adjustments: / getReadyDuration: duration (in ms) of the get-ready-trial /iti: intertrialinterval: the time between response and next forward mask (default: 600ms)