-
Notifications
You must be signed in to change notification settings - Fork 135
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
What is the coordinate system for these datasets (see list)? #215
Comments
For those who are generally interested in coordinate systems in BIDS, I have created a wiki page that summarizes the status quo and also lists currently open questions and issues. --> https://github.com/bids-standard/bids-specification/wiki/Coordinate-Systems-for-MEG-EEG-iEEG It's a WIKI, so please add and/or correct items! |
I am not sure how this coordsystem description from ieeg_motorMiller2007 fails the validator, sorry if I am missing something obvious: content or coordsystem: Validator schema: |
some fields in the motorMiller2007 dataset have values like bids-examples/ieeg_motorMiller2007/sub-fp/ses-01/ieeg/sub-fp_ses-01_space-Talairach_coordsystem.json Lines 1 to 7 in a305798
|
I see, so Talairach is in this accepted list, but is not an accepted format for the coordsystem.json schema. There are iEEG datasets that will only share/have available atlas based coordinates, and I think it would be best to allow the fields from the appendix. |
ds000117"Elekta/Neuromag" => "ElektaNeuromag" ds000246
ds000248"ctf" => "CTF" ieeg_epilepsy / ieeg_epilepsy_ecogRenamed files:
I'm not sure I understand the logic of not supporting the same list of identifiers for |
To be clear: I am not opposed at all to the idea that all entries in the table at the bottom of appendix VIII would be valid fields. It's just that so far the specification does not say that. And when I updated the validator recently to behave according to the spec, these issues turned up. To me this suggests that we should go back to the specification and clarify several parts, making things like Thanks for opening the PRs @ftadel I'll take a look at them soon! |
Please see bids-standard/bids-specification#700 where I suggest some changes to the bids-specification that will turn the current problems into non-problems. Together with @ftadel's fixes we'd then have solved all problematic datasets I listed in this issue. |
These issues have now been solved in a series of PRs to spec, validator, and examples. Thanks everybody for your feedback! |
The following datasets currently all fail validation due to wrong coordinate system naming:
"T1w"
to"Image"
, depending on how WIP: Overhaul CoordinateSystem details for MRI, MEG, EEG, iEEG bids-specification#700 goeswe should fix them.
As a reminder, the coordinate systems appendix in the BIDS specification describes the permissible values for the
*CoordinateSystem*
fields.Until recently, we did not validate this field properly, so many BIDS datasets have erroneous entries there. The lack of "errors" has also made people believe that all sorts of values can be used for
*CoordinateSystem*
fields, so I imagine that this may come as a surprise for some.We have several options:
I would be very happy for input from @dorahermes and @ftadel regarding the ieeg datasets. Do we need to extend the BIDS "coordinate systems" appendix to cover more acceptable fields for iEEG?
@ftadel may also be able to help with
ds000246
andds000247
.I'd also like to loop in @robertoostenveld for this discussion for his experience with many data formats and coordinate systems.
The text was updated successfully, but these errors were encountered: