Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[INFRA] Convert entity table to yaml #475
[INFRA] Convert entity table to yaml #475
Changes from 8 commits
18a3f24
02c3403
6ea0dfd
6626368
5c26565
d6601e7
ee9535f
56a42b6
596ed00
45fdfca
9ec4e09
d03d895
8d3436c
aa1ac3e
5791baf
2193404
cc69735
c41a0dc
797b23c
56447c3
06429b5
e58931d
ef49d03
69b50fe
0673b73
b11685d
8d0b612
26f56ed
0bacc04
e2b923b
532bb6c
4041d00
bfac102
6ce57e1
4e291e2
c9020f5
bf80162
37132a4
814e453
0984f8c
cab708a
8aa4994
592a0db
1159d66
5576c66
330e4dc
a233116
85ba0ca
dd4e1c1
125c492
5c426b0
86650bf
177b15a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
<rant>
wow, I didn't know that (sub)folders are allowed here. I truly think this was a step backward for meeg proposal to just allow all those formats -- there is no 'standardization' now, tools will just support some but not the other formats etc.</rant>
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.
I assume all extensions are supposed to have dots?
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.
Now that I look at it, it looks like the 4d format just has a folder with no suffix. Here's what it looks like:
I guess I should just put a
/
there, instead of4d/
or.4d/
?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.
yeah, this format is the biggest pain ever ... we should ask some MEG people what to do (in particular, Robert O. once he's back from vacation)
Can we have
/
with a comment that this is for BTi/4D data?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.
Done in 4e291e2, but I'll hold off on resolving this in case further discussion is needed.
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.
Dear @tsalo -- Thank you for leading this effort! It is really fun to look at BIDS in such as structured way!
So within this
datatypes/
we indeed have datatypes which gained theirfolder/
within BIDS hierarchy (they also have themselves duplicated now indatatypes
) such asanat/
,func/
,fmap/
, etc. (+beh/
which isn't imaging), and then we have another group -- those which could have indeed been a modality of their own, but they are not "imaging data". They became auxiliary files which could go along with base imaging (andbeh/
)datatypes
. I think thatphoto
,channels
etc should get their own "folder" in this schema, e.g.auxiliary
orauxdatatypes
, and be moved there (instead of being underdatatypes
)datatypes/
entries can get rid of thedatatypes
field in their .yaml files -- they should then have 1-to-1 correspondence from the filename to corresponding datatype.On the top level (for inclusion) I see smth like
This would make it easier to tell one (which gets its own folder in BIDS) from another (just provides additional suffixed files).
Alternative could be - keep as is, and then add additional field (in a yet to be created higher level "inclusion" file) to signal which datatype is
auxiliary
, but then it would be a bit less structured IMHO and most likely we would need to maintain that redundant self mentioning withindatatypes
for the base data types.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.
I split
auxdatatypes
fromdatatypes
and dropped thedatatypes
key from thedatatype
yamls. I have to say, it looks much cleaner.