r/neuro • u/Voicu_Adelin-Gerorge • 4h ago
What makes setting up an EEG/BCI experiment so painful, and would a better workflow tool help? (student project, feedback welcome)
Hi r/neuro,
I'm one of five master's students at DTU. For a UX course we've been looking at how people set up EEG and brain-computer interface experiments, and the software side seems to be a big barrier: connecting a headset, checking that the signal is actually usable, running a calibration session, working out what the results mean, and keeping track of runs. A lot of that appears to live in scattered scripts and tool-specific GUIs.
So I'd like to start with the discussion question. If you've done EEG or BCI work (research, a lab course, a hobby kit, anything):
- Which step of setting up an experiment was the most frustrating or error-prone?
- What do you wish the software told you that it doesn't?
- Do you think a single tool that walks you through the workflow would be useful, or would you rather stay with your own scripts?
To make the question concrete we built a click-through prototype called Silvia. Disclosure: we made it, it's a non-commercial course project, and we're not selling anything. It uses simulated data only, so the signals and numbers are placeholders, and it isn't a validated or clinical tool. No account or headset needed: https://silvia-snowy.vercel.app/prototype
We'd welcome feedback in general. If you try it, any of these help:
- Could you see yourself using something like this?
- Do you see any value in it, and for whom?
- What did you like, and what confused you?
- What's missing, and what would you change first?
A couple of sentences is plenty. If you'd rather answer privately there's a 3-minute anonymous form: https://forms.cloud.microsoft/e/03fR0q15M0
We may quote anonymous comments in our course report. I'll be in the comments to reply and to discuss, and I'm happy to hear that the whole premise is off.