Duplicate Task Name Causes Duplicate session_ids and Data #76
Description
When multiple iTrace-Core and Plugin data pairs have identical task names (i.e. Task1, Task1, Task1), running the fixation filter results in all session_ids being identical to the first task that was loaded as shown in this screenshot:
This results in all fixations with the same session_id being identical, despite being 3 different pairs of data files. In other words, the fixation data for session_id 638047432593826165 will be generated 3 times for each fixation_run_id.
A current workaround is to change the task_name in each Core file to be distinct (i.e. Task1-1, Task1-2, Task1-3), which results in session_ids being correctly identified and fixation data being correctly generated:
