Skip to content
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

Add a flag to ignore specific runs for some subjects #82

Open
SamGuay opened this issue Oct 31, 2023 · 1 comment
Open

Add a flag to ignore specific runs for some subjects #82

SamGuay opened this issue Oct 31, 2023 · 1 comment

Comments

@SamGuay
Copy link

SamGuay commented Oct 31, 2023

Your idea

I have a couple of subjects with several runs of T1w or FLAIR and I naively thought that .bidsignore was an (okay) place to indicate which runs to ignore. Little did I know, .bidsignore is meant for the validator only and doesn't do anything (#131). Unless I missed something in the BIDS-App documentation, it appears there is no simple way to ignore certain runs. The problem atm is it creates a robust template with all the runs available for a participant and won't tell unless you skim the logs.

The rogue way is to simply delete the undesired scans but I hope there could be way to deal with this problem without deleting files.

Would a --bids-filter-file à la smriprep #104 solve this problem? I never used such in the past so I don't know.. Maybe a simple hack to ignore specific runs for some subjects only already exists ?

Am I right in thinking that the most straightforward approach to address this would likely involve passing a file that contains a list of scans to be ignored/removed when listing the T1w, T2, flair, etc.?
Cheers!

@Remi-Gau
Copy link
Contributor

Remi-Gau commented Nov 6, 2023

it appears there is no simple way to ignore certain runs.
Nothing standardize

The problem atm is it creates a robust template with all the runs available for a participant and won't tell unless you skim the logs.

Checking what will become the new spec for the BIDS app: it also makes no suggestions.

https://bids-standard.github.io/execution-spec/inputs.html#reserved-arguments

I would recommend the bids-filter-file approach the same way fmriprep does it.
There is a suggestion to apply it to MRIQC and I have used it in BIDSPM.

Note that bids filter file just mentions scans to include though, not to exclude.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants