-
Notifications
You must be signed in to change notification settings - Fork 163
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
[FIX] arrays of 3D coordinates MUST supply numeric values in x, y, z order #623
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nitpicks
src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md
Outdated
Show resolved
Hide resolved
Thanks @hoechenberger I'll have to adjust table pipes in a new commit. I'll wait a bit though, because I'll also have to fix "e.g." -> "for example", see #626 |
a16be18
to
79eca7c
Compare
@@ -59,12 +59,12 @@ also encourage users to provide additional meta information extracted from the | |||
manufacturer specific data files in the sidecar JSON file. Other relevant files | |||
MAY be included alongside the original EEG data in `/sourcedata`. | |||
|
|||
Note the RecordingType, which depends on whether the data stream on disk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Remi-Gau I just rebased my changes on top of your "e.g." -> "for example" changes and noticed the trailing blank lines whitespace. Just as a hint for you: It may be nice (for any project you are doing) to configure your editor to automatically remove trailing whitespace.
Or is there a particular reason for having that?
fixes #613
In this PR I add a clarification for all JSON fields that accept an
object of arrays
where the arrays are expected to contain 3D coordinates.this is the clarification:
While doing this PR I stumbled over a small oddity: In MRI
AnatomicalLandmarkCoordinates
are expected to be in voxel unitsWhereas in MEG and EEG, it says:
probably related to https://github.com/bids-standard/bids-examples/issues/190 ... this is not very well specified in BIDS currently and I lack the practical experience (use cases, broad overview of research practice) to improve the state of the art. cc @robertoostenveld with whom I have discussed about this in #520 (comment)