As discussed starting a discussion thread on how files will be renamed into BIDS derivatives.
One thing to clarify: the final output of a preprocessing pipeline (for func or anat) MUST be described as desc-preproc. This is done to facilitate knowing which file to "grab" no matter what software is used afterwards.
Also "provenance tracking" knowing the "parent" files of given file can be done in BIDS derivatives in the side-car json files, so it might not have to be encoded in the filename.
@mohmdrezk @marcobarilari @CerenB #
TODO
[ ] show examples of filenames with the run and the ses entity
[ ] break down the renaming tables by "workflow" to show how files are renamed after each analysis step
As discussed starting a discussion thread on how files will be renamed into BIDS derivatives.
One thing to clarify: the final output of a preprocessing pipeline (for func or anat) MUST be described as
desc-preproc
. This is done to facilitate knowing which file to "grab" no matter what software is used afterwards.Also "provenance tracking" knowing the "parent" files of given file can be done in BIDS derivatives in the side-car json files, so it might not have to be encoded in the filename.
@mohmdrezk @marcobarilari @CerenB #
TODO
run
and theses
entityfunc
anat
Not listed: some of the outputs of the segmentation done by the ALI toolbox for lesion detection