You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For this task, we want to create a simple page that displays a graph taken from the OpenBCI headset if the EEG headset is running. If the headset is not running, we'd show the user an error message that the headset isn't properly configured as well as link them to where the current code is on their computer to ask them to adjust their code.
Details
The UI for this should be similar to the .drawio file. If the headset is connected, we display a graph. We first need to check if the headset is connected. We do this using brainflow (https://brainflow.readthedocs.io/en/stable/). Using this, we can check if the OpenBCI headset is connected or not. If it is connected, we'd display the graph and an example of what this could possibly look like is here:
If the headset is not connected, we'd show and error message and we'd use os to link to the local code to the repo in order to let the user know there may be an issue with the code.
Deliverable
The deliverable for this will be a eegconfig class that displays the graph/error message
The text was updated successfully, but these errors were encountered:
OpenBCI Headset Config
Overview
For this task, we want to create a simple page that displays a graph taken from the OpenBCI headset if the EEG headset is running. If the headset is not running, we'd show the user an error message that the headset isn't properly configured as well as link them to where the current code is on their computer to ask them to adjust their code.
Details
The UI for this should be similar to the
.drawio
file. If the headset is connected, we display a graph. We first need to check if the headset is connected. We do this using brainflow (https://brainflow.readthedocs.io/en/stable/). Using this, we can check if the OpenBCI headset is connected or not. If it is connected, we'd display the graph and an example of what this could possibly look like is here:If the headset is not connected, we'd show and error message and we'd use
os
to link to the local code to the repo in order to let the user know there may be an issue with the code.Deliverable
The deliverable for this will be a
eegconfig
class that displays the graph/error messageThe text was updated successfully, but these errors were encountered: