09-09-2020, 02:21 PM
Dual Task Interference
Required Experiment Builder Version: 1.4.402 or higher
EyeLink Required: No
Type: Complete Example
Difficulty Level: Easy
This example illustrates:
The project is implemented based on Experiment 1 described in the following paper:
In the next 10 experiment blocks, results are recorded in the RESULTS_FILE.txt. However, there is no feedback message for each experiment trial. The event timing can be checked in the recorded messages.txt file.
Most importantly, the project shows how to use a PrepareSequence action node (TRIAL -> PREPARE_SEQUENCE in the project) to load the four dynamically chosen letters as fast as possible in order to meet the strict requirement for event timing control in the experiment. It also illustrates, among other things, an experiment design that shows on the screen four random letters with a target letter F either present (together with 3 randomly chosen distractor letters) or absent (all the four letters shown are randomly chosen distracter letters). Furthermore, in the target letter F present condition, F may appear randomly at one of the four possible positions within the letter array.
**Additional detailed information about the project is given in the notes section for most nodes. To see notes for a given node, either mouse over that node or click on it to display the notes window. If the notes window is not visible, go to the "View" drop down menu in Experiment Builder, select "Properties", and check "Note".
Instructions:
Dual_Task_Interference.ebz (Size: 65.37 KB / Downloads: 23)
Required Experiment Builder Version: 1.4.402 or higher
EyeLink Required: No
Type: Complete Example
Difficulty Level: Easy
This example illustrates:
- How to use Conditional nodes to check the task type
- How to use an internal counter to track total errors
- How to display different feedback based on task performance
The project is implemented based on Experiment 1 described in the following paper:
- Pashler, H. (1984). Processing Stages in Overlapping Tasks: Evidence for a Central Bottleneck. Journal of Experimental Psychology: Human Perception and Performance, 10, 358-377.
In the next 10 experiment blocks, results are recorded in the RESULTS_FILE.txt. However, there is no feedback message for each experiment trial. The event timing can be checked in the recorded messages.txt file.
Most importantly, the project shows how to use a PrepareSequence action node (TRIAL -> PREPARE_SEQUENCE in the project) to load the four dynamically chosen letters as fast as possible in order to meet the strict requirement for event timing control in the experiment. It also illustrates, among other things, an experiment design that shows on the screen four random letters with a target letter F either present (together with 3 randomly chosen distractor letters) or absent (all the four letters shown are randomly chosen distracter letters). Furthermore, in the target letter F present condition, F may appear randomly at one of the four possible positions within the letter array.
**Additional detailed information about the project is given in the notes section for most nodes. To see notes for a given node, either mouse over that node or click on it to display the notes window. If the notes window is not visible, go to the "View" drop down menu in Experiment Builder, select "Properties", and check "Note".
Instructions:
- Download the Dual_Task_Interference.ebz example from this message.
- Launch the Experiment Builder application.
- Unpack the Dual_Task_Interference.ebz file to a location on your Experiment Builder PC with "File menu -> Unpack".
- Open the project in Experiment Builder.
- Deploy the project to a new folder.
- Run the Dual_Task_Interference.exe from the deployed directory.
Dual_Task_Interference.ebz (Size: 65.37 KB / Downloads: 23)