09-02-2020, 11:32 AM
In some tasks participants are required to make a response or choice via a keypress, but it is important that the stimuli remain on screen for the same amount of time on each trial. In other words the key press should not terminate the trial.
In these scenarios, a simple solution is to follow the Keyboard Trigger node with a Timer Trigger node that has its Start Time property linked to the .startTime of the preceding Display Screen node. Please note that it is important to separate the Keyboard Trigger node and Timer Trigger node - either with a Null Action node, or, as in the example below with an Update Attribute node that updates the variable that stores the keypress response. A direct connection from the Displat Screen node to the Timer Trigger allows the trial to terminate after the correct duration, even if no keyboard response is made.
For a more complicated example of a task in which multiple keypresses are recorded within a trial, please see the RECALL_SEQ sequence in the Create False Memories Example.
In these scenarios, a simple solution is to follow the Keyboard Trigger node with a Timer Trigger node that has its Start Time property linked to the .startTime of the preceding Display Screen node. Please note that it is important to separate the Keyboard Trigger node and Timer Trigger node - either with a Null Action node, or, as in the example below with an Update Attribute node that updates the variable that stores the keypress response. A direct connection from the Displat Screen node to the Timer Trigger allows the trial to terminate after the correct duration, even if no keyboard response is made.
For a more complicated example of a task in which multiple keypresses are recorded within a trial, please see the RECALL_SEQ sequence in the Create False Memories Example.