Return to the Mathematical Processing Task page
						
									MATHEMATICAL PROCESSING TASK
SCRIPT INFO

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

Copyright © 01-15-2016 Millisecond Software


BACKGROUND INFO

											*Purpose*
This script implements a Mathematical Processing Task similar to the one described by:

UNIFIED TRI-SERVICE COGNITIVE PERFORMANCE ASSESSMENT BATTERY (UTC-PAB) I. DESIGN AND SPECIFICATION OF THE BATTERY. 
ENGLUND, C.E., REEVES. D.L., SHINGLEDECKER, C.A., THORNE, D.R., WILSON, K.P., & HEGGE. F.W. (1987).
REPORT NO. 87-10, NAVAL HEALTH RESEARCH CENTER, P 0 BOX 85122, SAN DIEGO, CALIFORNIA 92138
NAVAL MEDICAL RESEARCH AND DEVELOPMENT COMMAND, BETHESDA, MARYLAND (p.18)


											  *Task*
Participants are asked to categorize the solutions to simple arithmetic problems (e.g. 8 - 3 = ). 
They are asked to press one button (here: <) when the solution is smaller than 5 and another button 
when the solution is greater than 5 (here: >). Participants are asked to solve the problems from left
to right and respond as quickly and accurately as they can.
There are 3 conditions of arithmetic problems that differ in their cognitive demand:
A) low demand: one operator
B) moderate demand: two operators
C) high demand: three operators 


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

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

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 
/demand:						1 = low; 2 = moderate; 3 = high
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) 
/operation:						the sequence of operations
stimulusitem:					the presented stimuli in order of trial presentation
/problem:						contains the currently presented math problem
/solution:						contains the solution to the currently presented math problem
/resultcategory:				1 = solution < 5; 2 = solution > 5
response:						the participant's response (scancode of response key)
/responsecategory:				"correct"; "incorrect" (incorrect response); "response failure"
correct:						the correctness of the response (1 = correct; 0 = incorrect)
latency: 						the response latency (in ms)

/count_low:						counts all low demand trials
/countcorrect_low:				counts all correct low demand trials
/countspeederror_low:			counts all response failures in low demand trial
/countaccerror_low:				counts all accuracy errors in low demand trials
/meanrt_low:					mean correct latency (in ms) in low demand trials
/sd_low:						standard deviation of correct latencies in low demand trials
(same for moderate and high demand trials)

(2) Summary data file: 'MathematicalProcessingTask_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)
/demand:						1 = runs low demand task
								2 = runs moderate demand task
								3 = runs high demand task
/nr_lowdemandtrainingblocks -
/nr_highdemandtrainingblocks:	sets the number of training blocks for each demand condition
									Note: Typical training times for the tasks are as follows (recommended by: Englund et al, 1987) 
										Low Demand--7 three-minute blocks; 
										Moderate Demand--lO to 14 three-minute blocks
										High Demand--10 to 30 three-minute blocks.

/count_low:						counts all low demand trials
/propcorrect_low:				proportion correct low demand trials
/propspeederror_low:			proportion speed errors ('response failure') in low demand trials
/propaccerror_low:				proportion accuracy errors ('incorrect') in low demand trials
/meanrt_low:					mean correct latency (in ms) in low demand trials
/sd_low:						standard deviation of correct latencies in low demand trials
(same for moderate and high demand trials)

EXPERIMENTAL SET-UP
3 cognitive demand conditions: low, moderate, high. 
Assignment is done via groupnumber in this script.

Each condition runs for (default) 3 min (editable value).

A) Low cognitive demand: one operator (+, -); presentation time controlled by editable value (see section Editable Values) - default: 1500ms
B) Moderate cognitive demand: two operators (+-, -+, --); presentation time controlled by editable value (see section Editable Values) - default: 3000ms
C) High cognitive demand: three operators (+--, -+-, ++-); presentation time controlled by editable value (see section Editable Values) - default: 4000ms

Training:
By default, participants run through one block of training (3 min) for each demand condition in this script. 
Number of training sessions can be set under Editable Values.
Englund et al (1987) suggest the following:
* Low Demand--7 three-minute blocks; 
* Moderate Demand--lO to 14 three-minute blocks
* High Demand--10 to 30 three-minute blocks.
Training trials are 15s (default) long and provide feedback (red X) if the response is incorrect.

STIMULI
All problems are randomly generated right before presentation. 
Several constraints are placed on problem generation (Englund et al, 1987: A-F)
A) only digits 1-9
B) 0 < solution < 10
C) solution cannot be 5
D) roughly half the solutions < 5 (because the task is time-limited and not trial limited
there may be a slight frequency imbalance. The script is set up in such a way, that after every 10 trials, the frequencies should equal)
E) digits can only repeat if they are preceded by the same operator (e.g. 8 - 2 - 2 = )
F) when problems are solved from left to right: intermediate and cumulative solutions must be greater than 0
G) no repeats of immediately preceding problems

INSTRUCTIONS
Instructions are not original to Englund et al (1987). They are provided by Millisecond Software in the form
of html-files which can be edited.

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:

/responsekey_lower:						scancode of the response key for problems < 5 
											Note: scancodes under Tools -> Keyboard Scancodes (default: 51)
/responsekeylower_label:						label of the response key (default: '<')
/responsekey_upper:						scancode of the response key for problems > 5 
											Note: scancodes under Tools -> Keyboard Scancodes (default: 52)
/responsekeyupper_label:						label of the response key (default: '>')

/fontsize_problem:						fontsize of the targets in screen height percentages (default: 10%)

/blockduration:							the maximum task duration in ms (default: 180000)
/trainingtrialduration:					the maximum time allotted for demand trials of any kind during training blocks
/lowdemandduration:						the maximum time allotted for low demand trials in ms (default: 1500)
/moderatedemandduration:				the maximum time allotted for moderate demand trials in ms (default: 3000)
/highdemandduration:					the maximum time allotted for high demand trials in ms (default: 4000)

/nr_lowdemandtrainingblocks -
/nr_highdemandtrainingblocks:			sets the number of training blocks for each demand condition (default: 1)
											Note: Typical training times for the tasks are as follows (recommended by: Englund et al, 1987) 
													Low Demand--7 three-minute blocks; 
													Moderate Demand--lO to 14 three-minute blocks
													High Demand--10 to 30 three-minute blocks.

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