author : Kenneth Rioja
description : Data dictionnary of variables from the tova csv

<variable_name>
	<type>
	<description>
----------------------------------------------------------------
browser, browser_version, mobile, os, fullscreen, vsync_rate
	...
	Please refer to : https://www.jspsych.org/7.2/plugins/browser-check/#data-generated
block
	string
	Block name, can take the value of 'practice', or 'sa' = sustained attention, or 'ic' = inhibitory control
trial_type
	string
	Plugin name used to run the trial (https://www.jspsych.org/7.0/overview/plugins/#data-collected-by-all-plugins)
time_elapsed
	int
	Milliseconds spent between the start of the experiment and the end of the trial. (https://www.jspsych.org/7.0/overview/plugins/#data-collected-by-all-plugins)
real_trial_index
	int
	Manually created - (find '*MODIFIED*' in jspsych.js), real trials are begining with 1, 0 are the pluggins – if the participant has done multiple practice blocks, then there should be a 1 and a 2 lying between, do not take it into account. When cleaning data, filter by block and you should have it all ordered by block (from 1 to n_trial).
logStart
	timestamp
	yyyy-mm-ddThours:minutes:seconds.milisecondsZ, time when experiment starts
subject_id
	string
	Subject ID, whether taken from the URL or manually if `ask_for_id = true`
study_id
	string
	Study ID, whether taken from the URL or manually if `ask_for_id = true`
session_id
	string
	Session ID, whether taken from the URL or manually if `ask_for_id = true`
monitorsize_inch
	double
	Screen diagonal size in inch, as provided by the participant at the beginning of the task. This value does not interact with any of the code's variables, it is not used to compute stimulus size.
distance_cm
	double
	Distance screen-eye in cm as measured by the blind spot calibration.
pxperdeg
	double
	Pixel per degree, manually provided in the global variables or taken through calibration (that you must implement yourself).
monitor_width_px, monitor_height_px
	int
	Width and height in pixel of the monitor used.
presentation_time
	int
	Time in miliseconds elapsed between the onset of the stimulus i and the offset of the stimulus i
soa
	int
	Stimulus onset asynchrony, time in miliseconds elapsed between the onset of the stimulus i and the onset of the stimulus i + 1. soa = presentation_time + reaction time (RT not present in the variables here, but you can compute it obviously). Varies between 250ms and 4100ms.
resp_window
	int
	Response window in ms. If you answer anytime before the end of the resp_window, it will activate the buffer_time, e.g., soa=4100, resp_window=2000, buffer_time=2100, it means that if you answer before 2000ms, the trial will wait 2100ms before going to the next trial ELSE next trial will be 4100ms after the begining of the trial. NOTE : it only affects the aesthetic display of the trials, not the outcome in terms of FA, correct, etc...
buffer_time
	int
	Buffer time in ms. Time to wait after the next trial when response was given before the end of 'resp_window'. NOTE : it only affects the aesthetic display of the trials, not the outcome in terms of FA, correct, etc...
stimulus_width_va
	double
	Physical width in va of the stimulus on screen. Coming from stim_diag_va / Math.sqrt(2).
stimulus_width_cm
	double
	Physical width in cm of the stimulus on screen. Coming from stim_diag_cm / Math.sqrt(2).
stimulus_width_px
	double
	Virtual width in pixels of the stimulus on screen, virtual means that as long as you do not know what is the size of ONE pixel on YOUR screen, you don't know the 'real' size. Coming from stim_width_deg * px2deg.
logEnd
	timestamp
	yyyy-mm-ddThours:minutes:seconds.milisecondsZ, time when experiment ends
rt
	int array
	Rt's from all reponses during the soa, if empty, participant did not answer
stimulus
	string
	Label of the stimulus ('shapeup' or 'shapedown'), see 'stimulus_label' in bl_tova.js
trial_condition
	string
	Trial condition : Go = target, NoGo = non-target
position_is_top
	int
	Position of the stimulus during presentation_time : 1 = stimulus image displayed at the top of the screen, 0 = stimulus image displayed at the bottom of the screen
effective_response
	int
	Participant's response : 0 = refrained, 1 = pressed spacebar, 2 = pressed spacebar multiple times
correct
	int
	Whether the trial was correct (1) or incorrect (0)
trial_accuracy
	string
	Trial outcome (expected x effective) can have those values : "correct rejection", 'miss', "false alarm", 'hit'