Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protocol specific documentation #96

Open
2 tasks
aspaNeuro opened this issue Oct 21, 2024 · 0 comments
Open
2 tasks

Protocol specific documentation #96

aspaNeuro opened this issue Oct 21, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation feature New planned feature

Comments

@aspaNeuro
Copy link
Contributor

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:

  • Document protocol specific LSL messages
  • Implement protocol specific messages for the VR experiment
@aspaNeuro aspaNeuro added documentation Improvements or additions to documentation feature New planned feature labels Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation feature New planned feature
Projects
None yet
Development

No branches or pull requests

2 participants