Description
Workflow (cross-sectional, maybe longitudinal) will encounter an error if there are files stored at the subject level without expected entities. For example:
.
└── sub-001
├── ses-AA
│ ├── anat
│ ├── dwi
│ └── func
├── ses-BB
│ ├── anat
│ ├── dwi
│ └── func
├── ses-CC
│ ├── anat
│ ├── dwi
│ └── func
└── sub-001_sessions.tsvWill cause an error to be thrown because the TSV file is picked up by b2t and is a valid group (sub=A001, ses=None), but there is no matching T1w that can be found for this group for the cross-sectional anatomical workflow.
Steps to Reproduce
Run workflow on a dataset with a similar organization where there may be files stored at the subject level when there are sessions.
Expected Results
Should ignore these and just look at the sessions.
Actual Results
These files are being picked up.
Additional Notes
Initial thoughts are maybe we need to filter for the niftis, but maybe that is too restrictive?
Description
Workflow (cross-sectional, maybe longitudinal) will encounter an error if there are files stored at the subject level without expected entities. For example:
. └── sub-001 ├── ses-AA │ ├── anat │ ├── dwi │ └── func ├── ses-BB │ ├── anat │ ├── dwi │ └── func ├── ses-CC │ ├── anat │ ├── dwi │ └── func └── sub-001_sessions.tsvWill cause an error to be thrown because the TSV file is picked up by b2t and is a valid group (
sub=A001, ses=None), but there is no matching T1w that can be found for this group for the cross-sectional anatomical workflow.Steps to Reproduce
Run workflow on a dataset with a similar organization where there may be files stored at the subject level when there are sessions.
Expected Results
Should ignore these and just look at the sessions.
Actual Results
These files are being picked up.
Additional Notes
Initial thoughts are maybe we need to filter for the niftis, but maybe that is too restrictive?