View source for Data analysis - Stellar Prospector

'''Stellar Prospector'''

The game begins with SP_Phase1Begin (9) and comprises three phases, in this order:<br>
Phase 1: Visual cue-change signal.  Targets only, no distractors.<br>
Phase 2: Visual cue-change signal.  Targets and distractors.<br>
Phase 3: Auditory-visual cue-change signal.  Targets and distractors.

The task is to respond with a down-arrow key-press to high-value targets at fixation, whilst simultaneously monitoring for lower-value targets in the four sectors surrounding fixation in the upper visual hemifield, and responding with an up-arrow key-press to these.  At any given time, exactly one of the four sectors is the cued sector, in which 80% of targets will appear.

Depending on the numbers of trials available, data can be pooled across Phases 2 and 3, or even across all three phases.  (However, this matter of data pooling is for the experimenters to decide; the processing software should keep the phase-marker events intact.)  For translation of context-sensitive to context-free event codes:

<table BORDER="1">
<tr><th>		Original Event		</th><th>	following event							</th><th>	classification	</th></tr>
<tr><td ROWSPAN="3">	SP_CentralStimulusSpawn	</td><td>	SP_CentralStimulusResponsePressed CentralStimulus=<u>active</u>	</td><td>	hit		</td></tr>
<tr>						<td>		SP_PeripheralStimulusResponsePressed CentralStimulus=<u>active</u></td><td>	response error	</td></tr>
<tr>						<td>		SP_MissedCentralStimulus					</td><td>	miss		</td></tr>
<tr><td ROWSPAN="3">	SP_PeripheralStimulusSpawn</td><td>	SP_CentralStimulusResponsePressed CentralStimulus=<u>inactive</u></td><td>	response error	</td></tr>
<tr>						<td>		SP_PeripheralStimulusResponsePressed PeripheralStimulus=<u>active</u></td><td>	hit		</td></tr>
<tr>						<td>		SP_MissedPeripheralStimulus					</td><td>	miss		</td></tr>
<tr><td ROWSPAN="2">	SP_DistractorSpawn	</td><td>	SP_PeripheralStimulusResponsePressed PeripheralStimulus=<u>inactive</u></td><td>false alarm	</td></tr>
<tr>						<td>		SP_DistractorDisappear						</td><td>	correct rejection</td></tr>
</table>

Also re-code the associated response into a hit, a response error, or a miss based on the re-coding of the stimulus.  Response events that are not associated with any stimulus by the above rules and occur with PeripheralStimulus=<u>inactive</u> should be re-coded as false alarms.  (These will be quite rare in Phase 1, but more common in Phases 2 and 3 which involve distractors.)

For each of the three phases separately, and also for phases 2 and 3 pooled without phase 1, compute the following:<br>
Trial-by-trial values, mean, and standard deviation of:<br>
Reaction times to central stimuli<br>
Reaction times to validly cued peripheral stimuli (where the value of the <u>Sector</u> parameter for the SP_PeripheralStimulusSpawn event is the same as the value of the <u>Sector</u> parameter for the most recent SP_CueChange)<br>
Reaction times to all invalidly cued peripheral stimuli

When listing out the trial-by-trial values for the peripheral stimuli, also list the stimulus's polar coordinates <i>(r, &theta;)</i>, the number of the sector in which the stimulus appeared, and the number of the currently cued sector (from the most recent SP_CueChange).  Use this information to compute multiple regression coefficients of reaction time against the stimulus's <i>r</i> (its distance from fixation) and against the absolute value of the <u>difference</u> between the stimulus's &theta; and the &theta; that runs along the centre of the cued sector (-3&pi;/8, -&pi;/8, pi;/8, 3pi;/8; in general the formula is <u>Sector</u>&times;&pi;/4 - 3&pi;/8).  Also compute statistical significances for these regression coefficients.

For the peripheral stimluli only (not the central stimuli), in Phases 2 and 3 only (exlcuding Phase 1), in two separate computations one for the currently cued sector and the other for the currently uncued sectors, complute d' ("d prime") using the tallies of hits, correct rejections, false alarms and misses.  (If any of these tallies is zero, estimate d' by increasing it to 1.)

<table BORDER="1">
<tr><td>	1
</td><td>	SP_PeripheralStimulusResponsePressed<br>&nbsp;&nbsp;&nbsp;&nbsp;PeripheralStimulus=<i>{inactive, active}</i><br>&nbsp;&nbsp;&nbsp;&nbsp;CentralStimulus=<i>{inactive, active}</i><br>&nbsp;&nbsp;&nbsp;&nbsp;Gather=<i>{inactive, active}</i>
</td><td>	The up-arrow key has been pressed, indicating a response to a peripheral stimulus (as this response might be a false alarm, a peripheral stimulus may or may not actually have been active); the parameters indicate the current activity of the central and any peripheral stimuli, and whether the game will be responsive to this key press or whether it's temporarily inactive as a penalty for a previous, incorrect key press.
</td></tr>

<tr><td>	2
</td><td>	SP_CentralStimulusResponsePressed<br>&nbsp;&nbsp;&nbsp;&nbsp;PeripheralStimulus=<i>{inactive, active}</i><br>&nbsp;&nbsp;&nbsp;&nbsp;CentralStimulus=<i>{inactive, active}</i><br>&nbsp;&nbsp;&nbsp;&nbsp;Gather=<i>{inactive, active}</i>
</td><td>	The down-arrow key has been pressed, indicating a response to the central (fixation) stimulus (as this response might be a false alarm, the central stimulus may or may not actually have been active); the parameters indicate the current activity of the central and any peripheral stimuli, and whether the game will be responsive to this key press or whether it's temporarily inactive as a penalty for a previous, incorrect key press.
</td></tr>

<tr><td>	5, 6
</td><td>	SP_Start_Menu_Action
</td><td>	At the beginning of the game, a selection has been made from the menu. (These codes should not be being transcribed onto the parallel port and thus should not be appearing in the EEG log.)
</td></tr>

<tr><td>	7
</td><td>	SP_MenuSelectButtonPressed
</td><td>	The player has pressed the space bar in response to an instruction prompt
</td></tr>

<tr><td>	9
</td><td>	SP_Phase1Begin
</td><td>	Phase 1 of the game has begun: visual cues only (no simultaneous auditory cue), targets only (no distractors)
</td></tr>

<tr><td>	10
</td><td>	SP_Phase2Begin
</td><td>	Phase 2 of the game has begun: visual cues only (no simultaneous auditory cue), 50% targets and 50% distractors
</td></tr>

<tr><td>	11
</td><td>	SP_Phase3Begin
</td><td>	Phase 3 of the game has begun: simultaneous visual and auditory cues, 50% targets and 50% distractors
</td></tr>

<tr><td>	12
</td><td>	SP_End
</td><td>	The game has ended; the player has collected enough peripheral stimuli (and ejected enough central stimuli) to fill the power bar
</td></tr>

<tr><td>	13
</td><td>	SP_PeripheralStimulusSpawn Sector=<i>{0, 1, 2, 3}</i><br>&nbsp;&nbsp;&nbsp;&nbsp;{X, Y}=<i>screen coordinates</i><br>&nbsp;&nbsp;&nbsp;&nbsp;ThetaRadians=<i>angle from fixation in polar coordinates [&mdash;&pi/2;, &pi/2;]</i><br>&nbsp;&nbsp;&nbsp;&nbsp;RadialDistanceInPixels=<i>display-coordinates distance from fixation</i><br>&nbsp;&nbsp;&nbsp;&nbsp;ScreenDistanceInCm=<i>linear distance from fixation (cm)</i><br>&nbsp;&nbsp;&nbsp;&nbsp;RhoRadians=<i>anglular distance from fixation (radians)</i><br>&nbsp;&nbsp;&nbsp;&nbsp;AzimuthPhiRadians=<i>azimuth from fixation (radians)</i><br>&nbsp;&nbsp;&nbsp;&nbsp;ElevationLambdaRadians=<i>elevation from fixation (radians)</i>
</td><td>	A lower-value stimulus in one of the four peripheral sectors, away from fixation, has appeared;<br>the parameters give distance from the fixation point in several redundant coordinate systems
</td></tr>

<tr><td>	14
</td><td>	SP_CentralStimulusSpawn
</td><td>	The high-value stimulus at the fixation point has activated
</td></tr>

<tr><td>	15
</td><td>	SP_DistractorSpawn<br>&nbsp;&nbsp;&nbsp;&nbsp;Sector=<i>{0, 1, 2, 3}</i><br>&nbsp;&nbsp;&nbsp;&nbsp;{X, Y}=<i>screen coordinates</i><br>&nbsp;&nbsp;&nbsp;&nbsp;ThetaRadians=<i>angle from fixation in polar coordinates [&mdash;&pi/2;, &pi/2;]</i><br>&nbsp;&nbsp;&nbsp;&nbsp;RadialDistanceInPixels=<i>display-coordinates distance from fixation</i><br>&nbsp;&nbsp;&nbsp;&nbsp;ScreenDistanceInCm=<i>linear distance from fixation (cm)</i><br>&nbsp;&nbsp;&nbsp;&nbsp;RhoRadians=<i>anglular distance from fixation (radians)</i><br>&nbsp;&nbsp;&nbsp;&nbsp;AzimuthPhiRadians=<i>azimuth from fixation (radians)</i><br>&nbsp;&nbsp;&nbsp;&nbsp;ElevationLambdaRadians=<i>elevation from fixation (radians)</i>
</td><td>	A distractor in one of the four peripheral sectors, away from fixation, has appeared;<br>the parameters give distance from the fixation point in several redundant coordinate systems
</td></tr>

<tr><td>	16
</td><td>	SP_CueChange<br>&nbsp;&nbsp;&nbsp;&nbsp;Sector=<i>{0, 1, 2, 3}</i><br>&nbsp;&nbsp;&nbsp;&nbsp;Sound=<i>{true, false}</i>
</td><td>	The visual cue has changed to the designated sector;<br>it is accompanied by an auditory cue iff Sound=true
</td></tr>

<tr><td>	17
</td><td>	SP_MissedPeripheralStimulus
</td><td>	The currently active peripheral (low-value) stimulus has timed out and disappeared without a response
</td></tr>

<tr><td>	18
</td><td>	SP_MissedCentralStimulus
</td><td>	The currently active central (high-value) stimulus has timed out and disappeared without a response
</td></tr>

<tr><td>	19
</td><td>	SP_DistractorDisappear
</td><td>	The currently active distractor has disappeared
</td></tr>
</table>

Data can be epoched by the stimulus events SP_CueChange, SP_CentralStimulusSpawn, SP_PeripheralStimulusSpawn, SP_DistractorSpawn.  ICA can be run either separately on each of these classes of epochs, or on all pooled, or on grouped subsets (for example pooling SP_PeripheralStimulusSpawn with SP_DistractorSpawn).  Epochs should be long enough to include the associated behavioural response events.

ERPs and ERSPs can be computed to each of these stimulus events.  Difference waves between SP_PeripheralStimulusSpawn and SP_DistractorSpawn may also be of interest.  In addition, response errors (see above for definitions) can be analysed for the error-related negativity.

(Originally the intent was to flicker the backgrounds in the four sectors at different fundamental frequencies, so that covert attention to a particular sector would be encoded in the EEG frequency spectrum via a slight increase in SSVEP amplitude at that fundamental frequency.  However, many subjects found the flickering distracting, and in addition some autism-spectrum subjects found it painful.  The flickering therefore was disabled for most subjects.)