Return to the Prospective Memory Task (Color Matching) page
						
									EVENT-BASED PROSPECTIVE MEMORY TASK
SCRIPT INFO

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 09-06-2016
last updated: 01-10-2017 by K.Borchert (katjab@millisecond.com) for Millisecond Software LLC

Copyright © 01-10-2017 Millisecond Software


BACKGROUND INFO

											*Purpose*
											
This script implements a computerized Event-based Prospective Memory (PM) Task described by:

Smith, R.E, & Ute J. Bayen, U.J. (2006). The Source of Adult Age Differences in Event-Based Prospective Memory: 
A Multinomial Modeling Approach. Journal of Experimental Psychology: Learning, Memory, and Cognition , 32, 623–635.

for stimuli selection:
Smith, R. E., & Bayen, U. J. (2004). A multinomial model of event-based prospective memory. 
Journal of Experimental Psychology: Learning, Memory, and Cognition, 30, 756–777.

Battig, W. F., & Montague, W. E. (1969). Category norms of verbal items in 56 categories: 
A replication and extension of the Connecticut category norms. 
Journal of Experimental Psychology, 80, 1–46.


											  *Task*
Participants run a color-matching task. During a baseline phase they see a sequence of 4 colored squares followed by
a word probe that either repeats one of the square colors (then press 'y') or doesn't (then press 'n'). 
During the prospective memory task phase, the basic task stays the same but every 10th word is a target
word (previously introduced and studied) that requires a different (or additional) response: press key
'z'.

!Note: due to the nature of the task, the task is not supported on touchscreen devices
(the touchscreen devices would present a z-responsekey throughout the baseline/PM task, thus potentially 
serving as an additional PM reminder)


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

(1) Raw data file: 'ProspectiveMemoryTask_colorMatchingTask_raw*.iqdat' (a separate file for each participant)

PM = Prospective Memory

build:							Inquisit build
computer.platform:				the platform the script was run on
date, time, subject, group:		date and time script was run with the current subject/groupnumber 
blockcode, blocknum:			the name and number of the current block
trialcode, trialnum: 			the name and number of the currently recorded trial
									(Note: not all trials that are run might record data; by default data is collected unless /recorddata = false is set for a particular trial/block) 
																
/order:							order of stim lists used for baseline-PM (Prospective Memory) task: "AB" vs. "BA"
/phase:							"task practice", "PM training", "baseline", "PM task"
/trialcount_Phase:				counts the number of trials run in each phase 
/list:							stim list currently used: "A" vs. "B"
/trialtype:						"target-match", "target-nomatch", "filler-match", "filler-nomatch"
/targettype:					"target" vs. "filler"
/matchtype:						"match" vs. "nomatch"
/stim:							stores the currently presented probe stimulus
/response:						the participant's response for the currently recorded trial
/response_task:					stores the scancode of the response button hit after stim was presented: 21 = yes; 49 = no
/correct_task:					accuracy of color-matching task response: 1 = task response was correct; 0 = otherwise		
/rt_task:						lateny (in ms) of color-matching task response
									- it's either measured from onset of stim or
									- from positive PM response	(during PM phase only)
/PMresponse:					1 = PM (prospective memory) response was made; 0 = no PM response was made (if applicable during PM phase)
/rt_PM:							latency (in ms) of PM response (if applicable during PM phase)
									- it's either measured from onset of stim or
									- from task response							
/responseSequence:				"task only", "PM only", "task-PM", "PM-task"
/color:							stores the color of the probe
/color1:						stores the color of the first square
/color2:						stores the color of the second square
/color3:						stores the color of the third square
/color4:						stores the color of the fourth square
/avoidColor:					stores the color that should not be sampled

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

script.startdate:				date script was run
script.starttime:				time script was started
script.subjectid:				subject id number
script.groupid:					group id number
script.elapsedtime:				time it took to run script (in ms)
computer.platform:				the platform the script was run on
/completed:						0 = script was not completed (prematurely aborted); 1 = script was completed (all conditions run)
/propCorrect_filler1:			proportion correct filler trials during baseline
/meanRT_filler1:				mean latency (in ms) of correct filler trials during baseline
/propCorrect_filler2:			proportion correct filler trials during PM-task phase (based only on trials when task response precedes PM response or task response is only response)
/meanRT_filler2:				mean latency (in ms) of correct filler trials during PM-task phase (based only on trials when task response precedes PM response or task response is only response)

/propCorrect_PMresponses:		proportion correct target trials (=hits) during phase 'PM task'
/propFalseAlarms:				proportion of False Alarms (=positive PM response) during filler trials during phase 'PM task'
/nr_hits:						number of correct PM responses during PM task phase
/nr_FA:							number of False Alarms during PM task phase


EXPERIMENTAL SET-UP

Phase 'Task Practice':
- 6 trials running filler match and filler nomatch trials in random order
(if block A is run first, the stimuli are selected randomly from list A, otherwise from list B)
- errorfeedback is presented for 500ms

Phase 'Baseline':
- samples stimuli from list A (targetsA, fillerA) or list B (targetsB, fillerB) => order of A/B is counterbalanced by groupnumber 
(odd groupnumbers run:AB; even groupnumbers run:BA)
- 62 test trials (6 target trials: 3 match/3 nomatch; 56 filler trials: 28 match/28 nomatch)
- target trials: 10th, 20th, 30th, 40th, 50th, 60th trial (!!!BUT: targets are indistinguishable from fillers and don't require any specific response)
	- it is randomly determined which of the 6 targets to present
	- it is randomly determined whether the trial is a match or a nomatch trial
- the order of the remaining 56 filler trials (match vs. nomatch) is randomly determined as are the presented stimuli

Trial Sequence:
square1(500ms)->blank(250ms)->square2(500ms)->blank(250ms)->square3(500ms)->blank(250ms)->square5(500ms)->blank(250ms)
->Probe until response -> ITI: 1000ms (Note; during phase 'PM task' filler and target trials collect possible additional responses
during the intertrial interval also)


Phase 'PM training': 
- all 6 targets presented on screen for study (self-paced)
- recall test: 6 textboxes (targets need to be entered in any order - will get converted to lowercase letters automatically)
- recall is repeated as long as it takes for all 6 targets to be recalled correctly
- a break follows the 'PM training' phase

Phase 'PM task':
- samples stimuli from the list not run during baseline
- 62 test trials (6 target trials: 3 match/3 nomatch; 56 filler trials: 28 match/28 nomatch)
- target trials: 10th, 20th, 30th, 40th, 50th, 60th trial (!target trials require a PM response)
	- it is randomly determined which of the 6 targets to present
	- it is randomly determined whether the trial is a match or a nomatch trial
- the order of the remaining 56 filler trials (match vs. nomatch) is randomly determined as are the presented stimuli

STIMULI
2 lists: A vs. B with 62 stimuli each (6 targets and 56 fillers)
- Each target comes from from a different category (= 6 target categories per list)
- Filler items come from the same target categories as the targets from their respective lists.

Millisecond Software attempted to recreate the original lists using the procedure outlined in Smith & Bayen (2006), p. 626.
More info under section Editable Stimuli. The selected words can easily be exchanged for others. 

colors: 
- blue, green, red, yellow, white
- probe color is selected randomly without replacement for each trial with the constraint that:
	- each of the 5 colors is used equally often in match trials (65 = 62 test trials + 3 task practice trials)
	and nomatch trials (65 = 62 test trials + 3 task practice trials)
- color of squares is randomly determined with the constraint that no color is repeated within the same trial
(=> in match trials: one color has to be the probe color but its position is randomly determined)
- all stimuli are presented on a black background

size:
- size can be edited under section "Editable Parameters"

INSTRUCTIONS
not original to Smith & Bayen (2006); 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.

/ squareDuration:			duration (in ms) of square presentation (default: 500ms)
/ ISI:						duration (in ms) of black interstimulus interval following each square (default: 250ms)
/ ITI:						intertrial interval (in ms) after each response (default: 1000ms)
/ breakDuration:			duration of the break (in ms) before the Prospective Memory task phase (default: 600000ms = 10min)

/ probeSize:				the size of the probes in % of canvas height (default: 3%)
/ squareSize:				the size of the squares in % of canvas height (default: 30%)

/ yesResponsekey:			the scancode of the yes responsekey (default: 21)
/ yesResponsekey_label:		the label of the yes responsekey (default: 'Y')
/ noResponsekey:			the scancode of the no responsekey (default: 49)
/ noResponsekey_label:		the label of the no responsekey (default: 'N')	
/ PM_Responsekey:			the scancode of the prospective memory (PM) task key (default: 44)
/ PM_Responsekey_label:		the label of the PM task key (default: 'Z')


Copyright © Millisecond Software. All rights reserved.
Contact | Terms of Service | Security Statement | Employment