Replies: 4 comments 2 replies
-
Note: show examples of filenames with the |
Beta Was this translation helpful? Give feedback.
-
Possibly helpful, adding some DAGs (directed acyclic graphs for the different workflows) |
Beta Was this translation helpful? Give feedback.
-
So, don't know if still valid or too late but it looks good to me. I have played a lot with the |
Beta Was this translation helpful? Give feedback.
-
Ideally I would like to add information in some json file explaining where each file came from because despite its non-bids character the spm prefix makes it very easy to know where the file came from (data provenance). |
Beta Was this translation helpful? Give feedback.
-
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
Beta Was this translation helpful? Give feedback.
All reactions