___________________________________________________________________________________________________________________ CHILD IOWA GAMBLING TASK ___________________________________________________________________________________________________________________ script based on Millisecond Software's IowaGamblingTask.iqjs 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 sample implements a child friendly Iowa Gambling Task. The task assesses risk learning by utilizing rewards and punishment in an uncertain simulated real-life decision making context. The implemented procedure is based on: Garon, N., C. Moore, and D.A.Waschbusch, Decision making in children with ADHD only,ADHD-anxious/depressed, and control children using a child version of the IowaGambling Task. J AttenDisord, 2006. 9(4): p. 607-19. This script runs with panda bears and snow leopards instead of bears and tigers (Garon et al, 2006) ___________________________________________________________________________________________________________________ TASK DESCRIPTION ___________________________________________________________________________________________________________________ Participants are asked to select cards from one of 4 decks with their mouse. The cards are "turned over" and reveal at least 1-2 panda bears and occasionally snow leopard(s). The panda bears bring good fortune: each panda means 1 golden coin for the participant. The snow leopards, however, take away good fortune: each snow leopard takes away 1 golden coin. The four different decks can be categorized as advantageous (deck3/4: overall more pandas than snow leopards are uncovered) or disadvantageous (deck1/2: overall more snow leopards than pandas). ___________________________________________________________________________________________________________________ DURATION ___________________________________________________________________________________________________________________ the default set-up of the script takes appr. 5 minutes to complete ___________________________________________________________________________________________________________________ DATA OUTPUT DICTIONARY ___________________________________________________________________________________________________________________ The fields in the data files are: (1) Raw data file: 'childigt_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 deckOrderGroup: the experimental deck group (1-4) the subject was randomly assigned to (refers to order of the advantageous (deck3, deck4) and disadvantegeous (deck 1, deck2) decks on the screen) group1: deck1(D), deck2(D), deck3(A), deck4(A) group2: deck4(A), deck1(D), deck2(D), deck3(A) group3: deck3(A), deck4(A), deck1(D), deck2(D) group4: deck2(D), deck3(A), deck4(A), deck1(D) 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 roundCounter: tracks the number of igt-blocks run cardsSelected: counts the number of card selections (across all blocks) card1ItemNumber- card2ItemNumber: store the itemnumber of the card face that needs to be presented on screen for each of the 4 decks response: the participant's response (e.g. which deck was chosen; the response "deck1" refers to the actual disadvantegous deck1 and not the position of the deck on the screen) responseCategory: "advantageous" vs. "disadvantageous" latency: the response latency (in ms) gain: stores the trial's gain depending on choice loss: stores the trial's loss depending on choice currentTotal: stores the current amount of coins won (2) Summary data file: 'childigt_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) deckOrderGroup: the experimental deck group (1-4) the subject was randomly assigned to (refers to order of the advantageous (deck3, deck4) and disadvantegeous (deck 1, deck2) decks on the screen) group1: deck1(D), deck2(D), deck3(A), deck4(A) group2: deck4(A), deck1(D), deck2(D), deck3(A) group3: deck3(A), deck4(A), deck1(D), deck2(D) group4: deck2(D), deck3(A), deck4(A), deck1(D) countDeck1Select- countDeck4Select: count all the actual deck1-deck4 choices across all blocks propDeck1Select- propDeck4Selectt: proportion of specific deck selections Note: deck1 always refers to deck1 and not specific deck location countAdvantageTotal: counts the total number of advantageous selections (deck 3 & deck 4) countDisadvantageTotal: counts the total number of disadvantageous selections (deck 1 & deck 2) net: difference btw. total number of advantageous and disadvantageous selections (positive NET -> overall more advantageous selections) countAdvantage1: counts the number of advantageous selections (deck 3 & deck 4) during trials 1-20 countDisadvantage1: counts the number of disadvantageous selections (deck 1 & deck 2) during trials 1-20 net1: difference btw. number of advantageous and disadvantageous selections during trials 1-20 countAdvantage2: counts the number of advantageous selections (deck 3 & deck 4) during trials 21-40 countDisadvantage2: counts the number of disadvantageous selections (deck 1 & deck 2) during trials 21-40 net2: difference btw. number of advantageous and disadvantageous selections during trials 21-40 countAdvantage3: counts the number of advantageous selections (deck 3 & deck 4) during trials 41-60 countDisadvantage3: counts the number of disadvantageous selections (deck 1 & deck 2) during trials 41-60 net3: difference btw. number of advantageous and disadvantageous selections during trials 41-60 countAdvantage4: counts the number of advantageous selections (deck 3 & deck 4) during trials 61-80 countDisadvantage4: counts the number of disadvantageous selections (deck 1 & deck 2) during trials 61-80 net4: difference btw. number of advantageous and disadvantageous selections during trials 61-80 ___________________________________________________________________________________________________________________ EXPERIMENTAL SET-UP ___________________________________________________________________________________________________________________ The default set-up runs - 1 Block of 40 IGT trials - Awareness Task (optional) - 1 Block of 40 IGT trials (= 80 IGT trials total) - Awareness Task (optional) To change the the default set-up (e.g. number of trials, remove awareness task) go to section EXPERIMENT and follow further instructions IGT Trials: - List elements control the selection of the specific cards for each deck (see section LISTS for more info). By default, the lists select specific outcomes (reward-loss contingencies) randomly without replacement across 10 trials in this script. To hard-code a specific reward-loss continency sequence for each deck, go to section LISTS and follow instructions. Deck1: across 10 turns => 2 pandas every time but 2 x 13 snow leopards (-> net win: -6) Deck2: across 10 turns => 2 pandas every time but 2 x 6 snow leopards and 2 x 7 snow leopards (->net win: -6) Deck3: across 10 turns => 1 panda every time but 4 x 1 snow leopard (-> net win: +6) Deck4: across 10 turns => 1 panda every time but 2 x 2 snow leopards (-> net win: +6) Note: the actual screen position of deck1-deck4 is determined randomly !!!Awareness Task: is optional (set under Editable Values -> parameters.runawarenesstest); The Awareness Task is coded in Helper Script "childIGT_AwarenessTask.iqjs". The optional Awareness Task asks participants to say how much they like each of the four decks. ___________________________________________________________________________________________________________________ STIMULI ___________________________________________________________________________________________________________________ All stimuli are provided by Millisecond Software LLC and are NOT original to Garon et al (2006). The stimuli can be exchanged for custom ones under Editable Stimuli. ___________________________________________________________________________________________________________________ INSTRUCTIONS ___________________________________________________________________________________________________________________ All instructions are provided by Millisecond Software LLC and are NOT original to Garon et al (2006). The instructions are provided in form of html pages (see section Editable instructions) and can be edited directly in the html files. ___________________________________________________________________________________________________________________ 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: /startAmount: startamount (default = 0) /showCardInfo: true = shows information about number of cards played/how many more to come false = does not display this information on the screen /maxigtTrials: max number of igt trials run (default: 80) Note: by default each block of igt trials runs 40 trials (to change, go to section BLOCKS) changing the number here only affects the counting of the trials /runAwarenessTest: true = runs awareness test midtest and posttest (as Garon et al 2006) (default) false = skips the awareness test ___________________________________________________________________________________________________________________ CHILD IOWA GAMBLING TASK AWARENESS TASK - helper script (does not run on its own) ___________________________________________________________________________________________________________________ helper script for childIGT.iqjs last updated: 07-26-2023 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC Script Copyright © 07-26-2023 Millisecond Software ___________________________________________________________________________________________________________________ BACKGROUND INFO ___________________________________________________________________________________________________________________ * This helper script implements the code for an Awareness Task Survey which can be used for the childIGT.iqjs as in: Garon, N., C. Moore, and D.A.Waschbusch, Decision making in children with ADHD only,ADHD-anxious/depressed, and control children using a child version of the IowaGambling Task. J AttenDisord, 2006. 9(4): p. 607-19. ___________________________________________________________________________________________________________________ TASK DESCRIPTION ___________________________________________________________________________________________________________________ For each of the 4 decks presented in the IGT, participants are asked how much they like the highlighted deck and why. ___________________________________________________________________________________________________________________ DATA OUTPUT DICTIONARY ___________________________________________________________________________________________________________________ The data is stored in the main script ___________________________________________________________________________________________________________________ EXPERIMENTAL SET-UP ___________________________________________________________________________________________________________________ Garon et al (2006) don't provide a detailed description of their awareness questions. Millisecond Software provides an (untested) EXAMPLE of an awareness task using multiple choice and short answer questions (responses are not scored by computer). A different set of questions can be coded for the awareness task or the awareness task can be given verbally to each participant and removed from the set-up (see section EXPERIMENT in main script). Awareness Task in this script: (see section TRIALS) script asks 2 multiple choice questions per deck 1) How much do you like to select cards from this deck? 2) Why? (Openended question) Order of Decks tested: actual deck1 -> actual deck2 -> actual deck3 -> actual deck 4 ___________________________________________________________________________________________________________________ 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.