In the outdoor experiments there is a protocol made with keypresses that are logged and create EEG LSL messages:
There is the need to describe what each action does and how LSL codes are created in function of this.
The codes are 35000 35100 35200 35300
indoor VR
In the indoor experiments, no protocol-specific LSL messages are going to the EEG, we assumed that because with random sync messages, synchronization between these different streams was achieved, so there would be no need to go further and implement the protocol-specific messages in this case. However after speaking with Starlab team we noticed that they are using these to post process EEG data for specific chunks defined by these parameters.
Actions to solve this issue:
[ ] Document protocol specific LSL messages
[ ] Implement protocol specific messages for the VR experiment
Outdoor
In the outdoor experiments there is a protocol made with keypresses that are logged and create EEG LSL messages: There is the need to describe what each action does and how LSL codes are created in function of this. The codes are 35000 35100 35200 35300
indoor VR
In the indoor experiments, no protocol-specific LSL messages are going to the EEG, we assumed that because with random sync messages, synchronization between these different streams was achieved, so there would be no need to go further and implement the protocol-specific messages in this case. However after speaking with Starlab team we noticed that they are using these to post process EEG data for specific chunks defined by these parameters. Actions to solve this issue: