-
Notifications
You must be signed in to change notification settings - Fork 34
Issues: fNIRS/snirf
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Suggestion] Increased compatability for mutliple AUX data channels to be stored in a single AUX block
enhancement
New feature or request
#158
opened Sep 19, 2024 by
DamianNeurode
[Suggestion] Make detector- and sourceindex to array (needed for SRS & StO2)
enhancement
New feature or request
#157
opened Sep 16, 2024 by
Horschig
Create a comprehensive set of example data
enhancement
New feature or request
#156
opened Sep 13, 2024 by
rob-luke
What happens if both /nirs(i)/data(j)/measurementLists and /nirs(i)/data(j)/measurementList are both present
help wanted
Extra attention is needed
#155
opened Sep 13, 2024 by
rob-luke
Multiplex configuration description for enahnced data processing
#141
opened Apr 19, 2024 by
samuelpowell
/nirs(i)/stim(j)/data does not use TimeUnit
breaking
A change that would break backwards compatibility with previous releases of the specification
v2.0
Things to be considered for version 2
#111
opened Apr 27, 2022 by
rob-luke
Consider removing support for multiple /nirs{i} blocks: for many applications, a SNIRF file should only contain one acquisition from a single subject
wontfix
This will not be worked on
#88
opened Sep 29, 2021 by
sstucker
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.