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

BIDS filters are applied across queries #101

Open
tsalo opened this issue Feb 27, 2025 · 2 comments
Open

BIDS filters are applied across queries #101

tsalo opened this issue Feb 27, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@tsalo
Copy link
Collaborator

tsalo commented Feb 27, 2025

What happened?

It looks like collect_derivatives is expecting a single filter dictionary (e.g., {'subject': ['01'], 'task': ['rest']}) to apply to all queries. However, we generally want filters to be specific to the file type being queried (e.g., {'bold_raw': {'task': ['rest']}, 'anat_mni152nlin6asym': {'reconstruction': 'norm'}}).

I am labeling this as a bug instead of a feature request because different file types have different entities that may apply, so (except for a couple of exceptions, like subject and session, that are handled internally by fMRIPost-AROMA) there aren't any "general" filters you'd want to apply across file types.

What command did you use?

n/a

What command did you use to run fMRIPrep?

What version of fMRIPost-AROMA are you running?

main as of a90f01f

How are you running fMRIPost-AROMA?

Other

Is your data BIDS valid?

Yes

Please copy and paste any relevant log output.

Additional information / screenshots

No response

@tsalo tsalo added the bug Something isn't working label Feb 27, 2025
@tsalo
Copy link
Collaborator Author

tsalo commented Feb 27, 2025

The annoying thing about the filter is that, if we want to apply filters independently to each file type, the filters end up being very long. I've noticed that in XCP-D (see PennLINC/xcp_d#1306 (comment)).

@tsalo
Copy link
Collaborator Author

tsalo commented Feb 27, 2025

With #102, we will use the filter dictionary on BOLD queries, but will only grab the "subject" and optionally "session" entities for anatomical queries. Maybe that's the best way forward- basically we let users control which BOLD files are collected, but not which anatomical files are used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant