User Manual: Inquisit Cake Gambling Task


___________________________________________________________________________________________________________________	

									     CAKE GAMBLING TASK
___________________________________________________________________________________________________________________

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 07-31-2014
last updated:  03-08-2024 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC

Script Copyright © 03-08-2024 Millisecond Software

___________________________________________________________________________________________________________________
BACKGROUND INFO 	
___________________________________________________________________________________________________________________	
This script runs the Inquisit implementation of the Cake Gambling Task, a child-friendly version 
of the Cambridge Gambling Task, as described by Van Leijenhorst et al (2008).
The Inquisit implementation is written for touchscreens but can also be used with the mouse.

References:

Van Leijenhorst L, Westenberg PM, & Crone EA. (2008). A developmental study of risky decisions on the cake gambling task:
age and gender analyses of probability estimation and reward evaluation. Dev Neuropsychol, 33(2):179-96

Van Leijenhorst L et al (2010). Adolescent risky decision-making: Neurocognitive development of reward and
control regions. NeuroImage, 51, 345–355

___________________________________________________________________________________________________________________
TASK DESCRIPTION	
___________________________________________________________________________________________________________________
Computer presents a cake with 6 pieces. A varying number of pieces are chocolate (brown) and strawberry (pink) 
pieces. The computer picks one of these slices at random. The task is to bet coins on whether the computer will 
select a chocolate or a strawberry piece. The number of coins that can be bet on strawberry/chocolate predictions
are presented on the bottom of the screen. The participant has to select the preferred option via pressing 
the response boxes.

Strawberry pieces and chocolate pieces are associated with low and high risk bets, respectively (counterbalanced). 
The number of coins bet on the low risk flavor stays the same throughout (default: 1 coin); 
the number of coins bet on the high risk flavor changes.

If the computer selects the chosen flavor, the participant earns all the coins bet. 
If the computer selects the other flavor, the participant loses all the coins bet by default 
(can be changed under Editable Parameters).
If the participants does not select a flavor in time, the script treats the trial as a bet on the losing flavor.

___________________________________________________________________________________________________________________	
DURATION 
___________________________________________________________________________________________________________________	
the default set-up of the script takes appr. 12 minutes to complete

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

(1) Raw data file: 'cakegamblingtask_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

parameters.punishment:				true (1)= if gamble is lost the coins bet will be subtracted from total (default)
									false (0) = if gamble is lost the coins bet will not be subtracted from total
								
										
highriskcolor:						the color assigned to the high risk
highriskposition:					the screen position of the high risk choice (left vs. right)
lowriskcolor:						the color assigned to the low risk 
lowriskposition:					the screen position of the low risk choice (left vs. right)

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.
										
counttrials:						custom trial counter										
																																				
ratio:								"5:1", "4:2", "3:3"
parameters.lowriskgamble_reward:	constant money awarded for a low risk gamble
values.highriskgamble_reward:		the monetary reward associated with the risky gamble for the current trial
stimulusitem:						the presented stimuli in order of trial presentation

response:							the participant's response (highriskchoice vs. lowriskchoice)
																			
latency: 							the response latency in ms (measured from onset of response signal)

responsecategory:					categorization of pressed response key into "high risk" vs. "low risk" (or "did not choose")

winningwedge:						number of the wedge that was selected by computer
risk_winningwedge:					whether the winning wedge was of the low or high risk flavor (low vs. high)

gambleoutcome:						1 = participant wins the gamble; 
									2 = participant loses the gamble
								
totalwinnings:						stores the total amount of money won across all trials


(2) Summary data file: 'cakegamblingtask_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)

punishment:							true (1)= if gamble is lost the coins bet will be subtracted from total (default)
									false (0) = if gamble is lost the coins bet will not be subtracted from total

highriskcolor:						the color assigned to the high risk
highriskposition:					the screen position of the high risk choice (left vs. right)
lowriskcolor:						the color assigned to the low risk 
lowriskposition:					the screen position of the low risk choice (left vs. right)
totalwinnings:						stores the total amount of money won

prop_nodecision:					proportion of trials in which participant did not make a choice

proprisky_51A -
proprisky_33E:						proportion risky choices for each of the experimental conditions
									Note: even for ratio 3:3, the selection of the color that is associated with 
									higher risk is still counted as "risky"

Note: A-E => refers to the reward conditions for the high gamble (see section Editable Parameters)							
								
___________________________________________________________________________________________________________________	
EXPERIMENTAL SET-UP 
___________________________________________________________________________________________________________________	
* By default, script runs 3 ratios: 3(low risk):3(high risk), 4(low risk):2(high risk), 5(low risk):1(high risk) 
(if only specific ratios should be run, go to section BLOCKS and follow instructions)
* By default, script runs 5 coin bets for the riskier flavor: 1, 3, 5, 7, 9 
(numbers can be changed under section Editable Parameters)
* assignment of flavor to low/high risk option as well as 
location of high risk/low risk response keys (right or left) is counterbalanced by groupnumber
(=> 4 groupnumbers; more info under section EXPT)

Practice Block:
* 15 practice trials => runs each of the ratio x coin bets once
* order is selected at random

Test Block:
* 270 trials => each combination of ratios x coin bets is run 18 times
* order is selected at random
* after a sequence of 90 trials (default) a rest trial of 1 min rest (default) is presented

Trial Sequence:
-> blank screen (1000ms, default) 
-> Cake Presentation without response signal (3000ms, default) 
-> Cake Presentation WITH response signal (2000ms)*
-> blank screen (default 0ms)
-> Feedback

!!!NOTE: if participant does not make a choice within the given timeframe, this script assumes the 
losing flavor/bet was chosen 

___________________________________________________________________________________________________________________	
STIMULI
___________________________________________________________________________________________________________________
- all images provided under the Creative Commons license
- change images under Editable Stimuli/Editable Instructions

- soundfiles from https://mixkit.co/

___________________________________________________________________________________________________________________	
INSTRUCTIONS 
___________________________________________________________________________________________________________________
The provided instructions are not original to Van Leijenhorst et al (2008). 
Most instructions are provided by Millisecond Software in htm format. Changes to the instructions can be made
directly to the htm files.
After instructions and before the practice trials, one demo trial is run which could be used to
go through the task with participants.

___________________________________________________________________________________________________________________	
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: