Return to the Partner GNAT page
						
								Partner GNAT Script
SCRIPT INFO

last updated: 01-12-2016 by K.Borchert (katjab@millisecond.com) for Millisecond Software LLC
Copyright © 01-12-2016 Millisecond Software



BACKGROUND INFO

											*Purpose*
	This script implements the Partner GNAT procedure (study 2) described in:

	Lee, S., Rogge, R. D., & Reis, H. T. (2010). Assessing the seeds of relationship decay: Using implicit evaluations to detect 
	the early stages of disillusionment. Psychological Science, 21(6), 857-864.

	This script calculates d'prime values.

											  *Task*
Participants are asked to categorize attributes and partner-related items (e.g words  "supportive", "partner name") 
into predetermined categories via keystroke presses. The basic task is to press the Spacebar if an item (e.g. supportive")
belongs to the category currently being tested (e.g. "Constructive"") and to do nothing if it doesn't.
For practice, participants sort items into categories "Constructive", and "Destructive".
For the test, participants are asked to sort categories into the paired/combined categories (e.g. 
"Partner OR Constructive"). When an item belongs to either one of these two categories, 
participants should press the Spacebar.


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

(1) Raw data file: 'PartnerGNAT_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 
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) 
stimulusitem:					the presented stimuli in order of trial presentation
response:						the participant's response
correct:						the correctness of the response (1 = correct; 0 = incorrect)
error:							1 = error; 0 = correct
latency: 						the response latency (in ms)

	pg_hits						number of hits for the partner/good pairing
	pg_misses					number of misses for the partner/good pairing
	pg_falsealarms				number of false alarms for the partner/good pairing
	pg_correctrejections		number of correct rejections for the partner/good pairing
	pb_hits						number of hits for the partner/bad pairing
	pb_misses					number of misses for the partner/bad pairing
	pb_falsealarms				number of false alarms for the partner/bad pairing
	pb_correctrejections		number of correct rejections for the partner/bad pairing

	pg_hr						hitrate for partner/good pairing
	pg_fr						false alarm rate for partner/good pairing
	pg_z_hr						z-value of hitrate for partner/good pairing
	pg_z_fr						z-value of false alarm rate for partner/good pairing
	pg_dprime					d' for partner/good pairing
	pb_hr						hitrate for partner/bad pairing
	pb_fr						false alarm rate for partner/bad pairing
	pb_z_hr						z-value of hitrate for partner/bad pairing
	pb_z_fr						z-value of false alarm rate for partner/bad pairing
	pb_dprime					d' for partner/bad pairing

(2) Summary data file: 'PartnerGNAT_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; 1 = script was completed (all conditions run)
	pg_hits						number of hits for the partner/good pairing
	pg_misses					number of misses for the partner/good pairing
	pg_falsealarms				number of false alarms for the partner/good pairing
	pg_correctrejections		number of correct rejections for the partner/good pairing
	pb_hits						number of hits for the partner/bad pairing
	pb_misses					number of misses for the partner/bad pairing
	pb_falsealarms				number of false alarms for the partner/bad pairing
	pb_correctrejections		number of correct rejections for the partner/bad pairing

	pg_hr						hitrate for partner/good pairing
	pg_fr						false alarm rate for partner/good pairing
	pg_z_hr						z-value of hitrate for partner/good pairing
	pg_z_fr						z-value of false alarm rate for partner/good pairing
	pg_dprime					d' for partner/good pairing
	pb_hr						hitrate for partner/bad pairing
	pb_fr						false alarm rate for partner/bad pairing
	pb_z_hr						z-value of hitrate for partner/bad pairing
	pb_z_fr						z-value of false alarm rate for partner/bad pairing
	pb_dprime					d' for partner/bad pairing


EXPERIMENTAL SET-UP
* 2 Practice Blocks of 16 trials (8 go/8 nogo): good  -> bad
-> items are randomly sampled 
* 2 test blocks (order counterbalanced by groupnumber): 
-> testing of paired categories "partner OR good" vs. "partner OR bad" 
-> items are randomly sampled
-> 70 trials: 20 partner (go trials), 20 attribute go trials, 30 attribute no-go trials
	
 STIMULI
can be edited under section Editable Stimuli

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

	intertrialinterval			default is 400ms
	responsetimeout				default is 600ms

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