Return to the Cued Recall Procedure page
___________________________________________________________________________________________________________________	

									*Cued Recall Procedure*
___________________________________________________________________________________________________________________	

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 05-11-2020
last updated:  06-02-2020 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC

Script Copyright © 06-02-2020 Millisecond Software

___________________________________________________________________________________________________________________
BACKGROUND INFO 	
___________________________________________________________________________________________________________________	

This script implements a variant of the Cued Recall Procedure. The Cued Recall Procedure was
introduced by Tolan & Tehan (1999) and was designed to study proactive interference effects on word retrieval. 
The Inquisit script implements a variant of the design described in Friedman & Miyake (2004).

References:

(1) Friedman, N.P. & Miyake, A. (2004). The relations among inhibition and interferene
control functions: a latent-variable analysis. Journal of Experimental Psychology: General,
133, 101-135.

(2) Tolan, G. A., & Tehan, G. (1999). Determinants of short-term forgetting:
Decay, retroactive interference, or proactive interference? International
Journal of Psychology, 34, 285–292.

for target/foil words:
(3) McEvoy, C. L., & Nelson, D. L. (1982). Category name and instance norms for 106 categories of various sizes. 
American Journal of Psychology, 95, 581-634.
Nairne, J. S. (1990). A feature model of immediate memory. Memory and Cognition, 18, 251-269.

___________________________________________________________________________________________________________________
TASK DESCRIPTION	
___________________________________________________________________________________________________________________	

Participants view either one or two blocks of four words each and must retrieve the word from the most recent
block that belongs to a cued category.

___________________________________________________________________________________________________________________	
DURATION 
___________________________________________________________________________________________________________________	
the default set-up of the script takes appr. 20 minutes to complete
___________________________________________________________________________________________________________________	
DATA FILE INFORMATION 
___________________________________________________________________________________________________________________		
The default data stored in the data files are:

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

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. 
																				
/trialCount:						custom trial counter (1-36) 

/trialCategory:						0 = practice trials
									1 = 2block_target (runs foil word in block1; target word in block2)
									2 = 2block_control (runs no foil words)
									3 = 1block
									(Note: the trials are run in a fixed order (that was determined randomly). To 
									change the order to a complete randomized order, go to 'list.testtrials' and follow instructions)
									
/target:							stores the selected target word for the current trial sequence
									(target word = the word that needs to be entered into the textbox)
 
/targetCategory:					stores the category of the selected target word 

/foil:								stores the foil word (if applicable for '2block_target' trials; otherwise empty) 
									Foil words come from the same category as the target words and are
									presented during the first block in '2block' trials.
									Foils are stronger representatives of the target category than the targets themselves
									Example: category bird; target = penguin, foil = robin

/foilBlockWords:					stores the 4 words presented during the 'foil' block 
									Notes: 
										- the foil block contains non-target words:
										=> it's the first block of 4 words for '2block' trials 
										=> no foil block for '1block' trials
										- the words are stored in the order they appeared
									
/targetBlockWords:					stores the 4 words presented during the 'target' block 
									Notes: 
										- the target block contains the target word; 
										=> it's the second block of 4 words for '2block' trials	
										=> it's the only/first block for '1block' trials
										- the words are stored in the order they appeared
										
/2digitNumber:						the 2digit number presented during distractor trial										
										
response:							the participant's response
										distractor trial: 
											scancode of response button
											31=S
											38=L
											
										recall trial:
											the entered word as it was typed
											
/recallResponse:					the recall response in lower case letters only											
											
											

correct:							accuracy of response: 1 = correct response; 0 = otherwise		
										distractor trials:
											1 = the presented number was correctly categorized
											0 = otherwise
											
										recall trial:
										1 = the entered word was the target word
										0 = otherwise
										Note: it is recommended to manually check the responses as 
										spelling errors will be noted as '0'
											
latency: 							the response latency (in ms); measured from: onset of trial											


/recallRT:							the duration (in ms) that it took participant to enter the recallSolution											
											

(2) Summary data file: 'cuedrecallprocedure_summary*.iqdat' (a separate file for each participant)*

inquisit.build:						the version/build of Inquisit
computer.platform:					the platform the script was run on (win/mac/ios/android)
script.startdate:					date script was run
script.starttime:					time script was started
script.subjectid:					assigned subject id number
script.groupid:						assigned group id number
script.sessionid:					assigned session id number
script.elapsedtime:					time it took to run script (in ms); measured from onset to offset of script
script.completed:					0 = script was not completed (prematurely aborted); 
									1 = script was completed (all conditions run)

Recall Performance:
									
/propCorrect_overall:				overall proportion correct recall (across all test trials)
/meanCorrRT_overall:				overall mean response time (in ms) of submitting correct recall response (across all test trials)

/propCorrect_2block_target:			proportion correct recall in 2block-foil/target condition
/meanCorrRT_2block_target:			mean response time (in ms) of submitting correct recall response in 2block-foil/target condition

/propCorrect_2block_control:		proportion correct recall in 2block-control condition (no foil is run)
/meanCorrRT_2block_control:			mean response time (in ms) of submitting correct recall response in 2block-control condition

/propCorrect_1block:				proportion correct recall in 1block-control condition
/meanCorrRT_1block:					mean response time (in ms) of submitting correct recall response in 1block-control condition								

DistractorTask Performance:

/propCorrect_DistractorTask_overall:		overall proportion correct magnitude judgments (across all test trials)
/meanCorrRT_DistractorTask_overall:			overall mean response (in ms) of making correct magnitude judgments (across all test trials)

/propCorrect_DistractorTask_2block_target:	proportion correct magnitude judgments in 2block-foil/target condition
/meanCorrRT_DistractorTask_2block_target:	mean response (in ms) of making correct magnitude judgments in 2block-foil/target condition

/propCorrect_DistractorTask_2block_control:	proportion correct magnitude judgments in 2block-control condition
/meanCorrRT_DistractorTask_2block_control:	mean response (in ms) of making correct magnitude judgments in 2block-control condition

/propCorrect_DistractorTask_1block:			proportion correct magnitude judgments in 1block-control condition
/meanCorrRT_DistractorTask_1block:			mean response (in ms) of making correct magnitude judgments in 1block-control condition
																
							
* separate data files: to change to one data file for all participants (on Inquisit Lab only), go to section
"DATA" and follow further instructions

___________________________________________________________________________________________________________________	
EXPERIMENTAL SET-UP 
___________________________________________________________________________________________________________________	


(1) DEMO
2 demo trials to explain the procedure:
- 1block
- 2block (fixed sequence)

The demo trials provide more time to the participants for instructions, the distractor task 
as well as the recall trials.

(2) TEST
1 test block of 36 trials (12 trials per 3 trialtypes): by default the order of the trials is fixed
(one random sequence has been determined a-priori, see list.testtrials)

General trial set-up:

-> get ready (2000ms)
-> instructions (aloud/silent) (1000ms)
-> block1 words (each of the 4 words is presented for 1000ms) -> 'foil' block
			(word1 -> word2 -> word3 -> word4)
-> instructions (aloud/silent) (1000ms)
-> block2 words (each of the 4 words is presented for 1000ms) -> 'target' block
			(word1 -> word2 -> word3 -> word4)
-> 8 distractor trials (magnitude trials; each 2 digit number is presented for 1000ms)
			(number1 -> number2 -> number3 -> number4 -> number5 -> number6 -> number7 -> number8)
-> cued recall trial (presents target category; time limit = 5000ms)

(a) 12 '2block-target' trials:
	- presents 2 blocks of 4 words: 
		- first block is referred to as the 'foil' block in this script; it contains the foil word
		that is matched to the randomly selected target (they come from the same category), 
		the remaining three words are randomly selected filler words
		(order of 4 words is randomly determined)
		- second block is referred to as the 'target' block in this script; it contains
		the randomly selected target word; the remaining three words are randomly selected
		filler words 
		(order of 4 words is randomly determined)
		- 'aloud' instructions are given to the first block (foil block); 
		'silent' instructions are given to second block (target block)

(b) 12 '2block-control' trials: same as above but instead of a foil word, a fourth filler word
is selected for the 'foil' block

(c) 12 '1block' trials:
	- presents 1 block of words ('target block')
	- all four words are randomly selected filler words
	- order of words is randomly determined
	- 'aloud' instructions are given to the block

Notes: 
- no word is ever repeated in this experiment. Categories are only repeated for foil and target words.
- the target words/target categories are randomly selected for each trial.

___________________________________________________________________________________________________________________
STIMULI
___________________________________________________________________________________________________________________
provided by Millisecond Software - can be edited under section Editable Stimuli

36 Target/Foil Categories: selected from

McEvoy, C. L., & Nelson, D. L. (1982). Category name and instance norms for 106 categories of various sizes. 
American Journal of Psychology, 95, 581-634.
Nairne, J. S. (1990). A feature model of immediate memory. Memory and Cognition, 18, 251-269.

Note: Foil words were always the words with a higher correlation with the target category compared to the
target words themselves.

Remaining filler words were taken from the above article as well as from everyday life. 
Constraints: Filler words should never overlap with any of the selected target categories.
All words can easily be replaced under section Editable Stimuli.

___________________________________________________________________________________________________________________	
INSTRUCTIONS 
___________________________________________________________________________________________________________________	
provided by Millisecond Software - 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: