-
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
acq_time
for sessions.tsv
?
#948
Comments
I believe I added I didn't realize the definition read weirdly (I probably didn't really look at it in context), so we should probably adjust that. I assume we want to allow/support I added |
Well it is just a bit incompatible with the fact that there will be one row per session. Current version for sessions.tsv:
Maybe something like:
ah OK I forgot about this one. |
Damn ... I think both of you are right (Taylor for including it; Remi for pointing out it seems weird). I agree with your direction above @Remi-Gau to rephrase what Furthermore, I think the
And in "Units", there is a good documentation of how anonymization can be done ... so maybe we could just delete that "duplicate" part from the |
It seems that
acq_time
andpathology
are now mentioned as columns for sessions TSV files.I am not sure why this happened, but I am not sure it makes sense to have acquisition time in
sessions.tsv
ANDscans.tsv
.And if we do have an
acq_time
then the current definition is taken from the scan level and read bizzarrely for sessions.Am I missing something here?
For
pathology
, was that introduced through thesample entity
PR?@tsalo is it possible we did not cross check things properly when we started using the schema for this?
See the latest version:
https://bids-specification.readthedocs.io/en/latest/03-modality-agnostic-files.html#sessions-file
See the stable version
https://bids-specification.readthedocs.io/en/stable/06-longitudinal-and-multi-site-studies.html#sessions-file
The text was updated successfully, but these errors were encountered: