sappelhoff
commented
3 days ago Since more folks are working with eyetracking data in MNE, I propose that MNE-BIDS is a good place to implement this support.
I'd be very happy to see that!
I imagine that only the new schema validator will be able to validate eye tracking BIDS data
100%
(assuming that the legacy validator that is written in JS will not be updated)
yes, that will not happen
So if https://github.com/mne-tools/mne-bids/pull/1302 is not merged soon, I'd also be willing to help bring that across the finish line.
Help in the form of commits pushed to that branch (or PRs against my branch / etc.) would be very very welcome!
How do folks feel about supporting I/O for eyetracking BIDS?
I think we need it!
Your support and contributions would be very welcome @scott-huberty!
Describe the problem
xref BEP 020 : The community is converging on a BIDS specification for eye-tracking data. MNE-Python has also supported eye-tracking data since v1.4 (May 2023).
Once BEP 020 is merged, actually implementing software to help researchers read/write BIDS compliant eye-tracking data is the natural next step.
Describe your solution
Since more folks are working with eyetracking data in MNE, I propose that MNE-BIDS is a good place to implement this support.
I imagine that only the new schema validator will be able to validate eye tracking BIDS data (assuming that the legacy validator that is written in JS will not be updated). So if #1302 is not merged soon, I'd also be willing to help bring that across the finish line.
How do folks feel about supporting I/O for eyetracking BIDS?
Describe possible alternatives
Don't support I/O for BIDS compliant eyetracking data, at least not yet.
Additional context
I will be applying for grant funding (USSRI) to request funding that would allow me to dedicate a portion of my time to do this. If I am not granted the award, I will still be interested in this to the extent that my projects would benefit from it, but I may not be able to dedicate as much time to the effort.