Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com), Millisecond
Created: January 31, 2024
Last Modified: January 10, 2025 by K. Borchert (katjab@millisecond.com), Millisecond
Script Copyright © Millisecond Software, LLC
This Inquisit script implements a Negative Priming Procedure with affective stimuli. Negative Priming is generally characterized as the implicit memory effect in which actively suppressing information processing of a stimulus can impair processing of related material shortly thereafter. Negative Affective Priming uses stimuli of different valences (positive vs. negative). It has been used in the study of impaired cognitive processing in depression (Joorman & Gotlib, 2010)
The implemented Negative Affective Priming procedure is based on the published paradigm by Joorman & Gotlib (2010).
15 minutes
Participants see two words on top of each other. One is the target word (printed in blue) and one is the distractor (printed in red). The words come from different valence categories (one is positive and the other negative). Participants are asked to ignore the red words. Their task is to categorize the blue words as positive or negative via corresponding keyboard responses.
Test trials are divided into 2 parts: Part1 are the Priming Trials (PTrials). Part2 are the Target Trials (TTrials).
For Negative Priming (NP) trials, the valence of the ignored (red) word in the PTrial (=distractor) is the same as the valence of the (blue) target word in the TTrial. The valence of the (blue) target in PTrials is opposite of the valence of the (blue) target in TTrials => negative priming is expected (slower responses in TTrials due to negative priming via the suppressed distractor of the same valence) => since the attended targets are of opposite valences there should not be any 'positive' valence priming effect
For Control (Ctrl) trials, the valence of the ignored (red) word in the PTrial is neutral compared to the positive or negative target word in the TTrial. The valence of the (blue) target in PTrials is opposite of the valence of the (blue) target in TTrials (same as in NP trials) => no negative priming is expected (neutral suppressed distractor should NOT negatively prime the target in the TTrial) => since the attended targets are of opposite valences there should not be any 'positive' valence priming effect in Ctrl trials either
Differences in TTrial Response Times in NP condition should be due to Negative Priming.
Although PTrials and TTrials are individual trials from a participant's perspective, participants may nonetheless potentially catch on the predictable response pattern created by PTrials and TTrial always requiring opposite responses. Thus, this script has the built-in functionality to add filler trials to obscure this response pattern.
provided by Millisecond - can be edited in script negativepriming_instructions_inc.iqjs.
The words used will depend on the actual language (e.g. English) used for the instructions.
The following will explain how the English words were selected for this script.
For remaining languages, the information will be provided in the language specific script
negativepriming_instructions_inc.iqjs.
provided by Millisecond - can be edited in script negativepriming_instructions_inc.iqjs
File Name: negativepriming_summary*.iqdat
| Name | Description |
|---|---|
| inquisit.version | Inquisit version number |
| computer.platform | Device platform: win | mac |ios | android |
| computer.touch | 0 = device has no touchscreen capabilities; 1 = device has touchscreen capabilities |
| computer.hasKeyboard | 0 = no external keyboard detected; 1 = external keyboard detected |
| startDate | Date the session was run |
| startTime | Time the session was run |
| subjectId | Participant ID |
| groupId | Group number |
| sessionId | Session number |
| elapsedTime | Session duration in ms |
| completed | 0 = Test was not completed 1 = Test was completed |
| propCorrect | Proportion correct responses across all test trials (TTrial only) |
| meanCorrRT | Mean correct response time across all test trials (TTrial only) extreme latency outliers removed (300 <= latency <= 2000) |
| propRTOutliers | Proportion removed latency data relative to all latency data (correct or incorrect responses) |
| propCorrectNP | Proportion correct responses across all NP trials (TTrial only) |
| meanCorrRTNP | Mean correct response time across all NP trials (TTrials only) - extreme outliers removed (see SCORING) |
| propCorrectCtrl | Proportion correct responses across all Control trials (TTrial only) |
| meanCorrRTCtrl | Mean correct response time across all Control trials (TTrials only) - extreme outliers removed (see SCORING) |
File Name: negativepriming_raw*.iqdat
| Name | Description |
|---|---|
| build | Inquisit version number |
| computer.platform | Device platform: win | mac |ios | android |
| computer.touch | 0 = device has no touchscreen capabilities; 1 = device has touchscreen capabilities |
| computer.hasKeyboard | 0 = no external keyboard detected; 1 = external keyboard detected |
| date | Date the session was run |
| time | Time the session was run |
| subject | Participant ID |
| group | Group number |
| session | Session number |
| blockcode | The name the current block (built-in Inquisit variable) |
| blocknum | The number of the current block (built-in Inquisit variable) |
| trialcode | The name of the currently recorded trial (built-in Inquisit variable) |
| trialnum | The number of the currently recorded trial (built-in Inquisit variable) trialnum is a built-in Inquisit variable; it counts all trials run even those that do not store data to the data file. |
| blockCounter | Tracks the number of blocks run |
| trialCounterPerBlock | Tracks the number of trials run per block (Test Trial = (PTrial + TTrial) count as one trial) |
| trialPhase | "P" (PTrial), "T" (TTrial), "F" (Filler) |
Iv: Stays The Same Across Pttrial And Ttrial |
|
| trialType | 1 = NP; 2 = Ctrl (Main IV); 3 = Filler (ignored for data analyses) |
| targetValenceTTrial | 1 = target in TTrial is negative; 2 = target in TTrial is positive |
| targetPositionPTrial | 1 = target in PTrial is on top; 2 = target in PTrial is on the bottom |
| targetPositionTTrial | 1 = target in TTrial is on top; 2 = target in TTrial is on the bottom |
Changes Btw. Ptrial And Ttrial |
|
| targetWord | The currently presented target word |
| distractorWord | The currently presented distractor word |
| targetValence | 1 = the currently presented target is negative; 2 = the currently presented target is positive |
| distractorValence | 1 = the currently presented distractor is negative; 2 = the currently presented distractor is positive; 3 = distractor is neutral |
| targetPosition | 1 = current target is on top (distractor on bottom); 2 = current target is on the bottom (distractor on top) |
| correctResp | Stores the correct response key for the current trial |
Dvs |
|
| response | The response of participant (scancode of response button) |
| responseText | The response button pressed Example response = 18 (scancode) => responseText = "E" |
| correct | Correctness of response (1 = correct, 0 = error) |
| latency | Response latency (in ms); measured from: onset of words |
| validRT | 1 = latency falls within 300 <= latency <= 2000 (see editable parameters) 0 = latency falls outside of specified range |
Additional Variables |
|
| targetY | Stores the vertical screen coordinate of the target |
| distractorY | Stores the vertical screen coordinate of the distractor 0% = top of the screen -> 100% bottom of the screen |
Ratings Of Targets And Distractors |
|
| tValence | The valence rating assigned to the current target |
| tArousal | The arousal rating assigned to the current target |
| tDominance | The dominance rating assigned to the current target |
| tLength | The length of the current target |
| dValence | The valence rating assigned to the current distractor |
| dArousal | The arousal rating assigned to the current distractor |
| dDominance | The dominance rating assigned to the current distractor |
| dLength | The length of the current distractor |
Previous Stimuli Used (To Check That No Repeats Across Ptrials And Ttrials) |
|
| prevDistractor | Stores the distractor stimulus from the previous trial |
| prevTarget | Stores the target stimulus from the previous trials |
The procedure can be adjusted by setting the following parameters.
| Name | Description | Default |
|---|---|---|
Design |
||
| numberOfBlocks | Number of test blocks to run | 5 |
| numberTTrialsPerBlock | Number of TTrials run per block should be a multiple of 16 if there are 32 TTrials in a block, there are also 32 PTrials in a block (so from a participant's perspective there are 64 test trials)! | 32 |
| ratioFillerToTTrial | Script adds an additional (0.5*TTrials) number of filler trials to each block by default: 0.5*32 = 16 filler trials (filler trials are single trials not double ones!) for a total of 32 TTrials per block there will be: 32 PTrials + 32 TTrials + 16 filler trials = 80 single trials from participant perspective) | 0.5 |
| targetColor | The color of the target words (require a response) | blue |
| distractorColor | The color of the distractor words (should be ignored) | red |
Latency Outlier Removal |
||
| minLatency | The minimum acceptable response time (in ms) | 300 |
| maxLatency | The maximum acceptable response time (in ms) | 2000 |
Sizing And Position Parameters |
||
| wordHeightPct | The relative height of the words (relative to canvas height) | 8% |
Positions: The Percent Vertical Active Canvas Position (Top = 0 -> Bottom = 100%) |
||
| topY | Top canvas position | 35% |
| bottomY | Bottom canvas position | 65% |
Timing Parameters |
||
| getreadyDuration | The duration (in ms) of the get-ready trial | 3000 |
| fixationDurationMS | The duration (in ms) of the fixation cross | 500 |
Response Keys |
||
| leftResponseKey | The assigned left response key (left side on QWERTY keyboard) | "A" |
| rightResponseKey | The assigned right response key (right side on QWERTY keyboard) | "L" |
| positiveResponseKey | Assignment of right or left response key to positive key | parameters.rightResponseKey |
| negativeResponseKey | Assignment of left or right response key to negative key | parameters.leftResponseKey |