Open yarikoptic opened 4 years ago
re participants.tsv: Do you know where basic demographics of these people are available?
re CHANGES: Not clear what you mean by "Might be worth tagging this bids dataset releases"
re _T1wDividedByT2w: desc
approach sounds good, but .bidsignore
might be just as suitable.
re participants.tsv: Do you know where basic demographics of these people are available?
no - haven't looked
re CHANGES: Not clear what you mean by "Might be worth tagging this bids dataset releases"
Use git tag -a
to tag "releases" of the datasets with reflection in CHANGES (part of BIDS)
re _T1wDividedByT2w:
desc
approach sounds good, but.bidsignore
might be just as suitable.
suitable to pacify bids-validator, but not suitable e.g. to make this data usable out of the box by bids aware tools (such as pybids)
missing participants.tsv. Probably that is why bids-validator immediately fails to recognize it as BIDS
My understanding of the bids spec is that the participants.tsv file is optional, and thus wouldn't be why the bids-validator fails.
re _T1wDividedByT2w: I will ask the BEP003 authors what they think (bids-standard/bids-specification#462). In the meantime, do we want to go with _desc-dividedByT2w_T1w
?
@loj re participants.tsv: oh hoh -- you must be right! in BIDS spec it is shmooshed together with phenotype/
which is optional for sure. And I got a victim of a not-yet-addressed https://github.com/bids-standard/bids-validator/issues/792 .
To troubleshoot in this case I just left one subject (still trips), got all the data for it and it stopped "tripping" that generic validator error... heh heh
Sure thing validator does not yet support _desc
field from the BEP. But I noted that _desc-dc-restore
should probably be redone to not have -
in dc-restore
since -
is not yet allowed in the values for the keys... I kept suggesting adding it (https://github.com/bids-standard/bids-specification/issues/226) , but there is resistance and most likely +
would be introduced (someone yet to do a PR proposing it) instead to be allowed in the values. So you might better use it instead here or chime in on that issue to possibly tilt the scales toward allowing regular '-'.
as for demographics:
But I noted that
_desc-dc-restore
should probably be redone to not have-
indc-restore
since-
is not yet allowed in the values for the keys...
@yarikoptic Thanks for pointing this out. :-) I saw that you suggested/volunteered to create a PR allowing for both the -
and +
options, so for now, I think it makes sense to leave in the -
.
re _T1wDividedByT2w: T1wT2wratio
seems to be the popular suggestion.
re -
-- given the speed other, more trivial changes, get accepted, I would have not hold breath awaiting for -
to become legit. +
is an easier candidate. And here I feel that dcrestore
is still readable, and would immediately become "legit". just my 1c.
quick notes
participants.tsv
. Probably that is why bids-validator immediately fails to recognize it as BIDSbids-
prefix to the tag) and annotating them in CHANGES_T1wDividedByT2w
suffix is something unknown to plain BIDS or upcoming "common derivatives". I would have asked on https://github.com/bids-standard/bids-specification/issues relating to https://github.com/bids-standard/bids-specification/pull/265 on how BEP003 authors envision to encode it (could be_desc-dividedByT2w_T1w
)