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

Intendedfor fmap entry update to accept "bids::sub-xx" #658

Open
karl-koschutnig opened this issue Nov 8, 2023 · 2 comments
Open

Intendedfor fmap entry update to accept "bids::sub-xx" #658

karl-koschutnig opened this issue Nov 8, 2023 · 2 comments
Assignees

Comments

@karl-koschutnig
Copy link

Hi experts,
I am a little bit confused and would appreciate any help.
We convert our data with bidscoiner into BIDS. Fieldmaps can be automatically assigned to (for example) DWI-images using the "Intendedfor" tag. As stated in the latest bids-specifications, this would be done as followed:
"IntendedFor": [
"bids::sub-01/ses-pre/func/sub-01_ses-pre_task-motor_run-1_bold.nii.gz",
"bids::sub-01/ses-pre/func/sub-01_ses-pre_task-motor_run-2_bold.nii.gz"]}
The latest bids-validator is happy with this notation !!

However, qsiprepr (19.1) - more precisely the bids-validator provided in that container - doesn't find the referenced images. It took me a while to figure out that the following notation is needed:

"IntendedFor": [
"ses-pre/func/sub-01_ses-pre_task-motor_run-1_bold.nii.gz",
"ses-pre/func/sub-01_ses-pre_task-motor_run-2_bold.nii.gz"]}

So, "bids::sub-xx" should not be used.

Is there a way to fix this problem? Is there anyone else out there having this problem?

Thanks for your help

Karl

@cookpa
Copy link
Collaborator

cookpa commented Nov 8, 2023

It looks like BIDS URIs are not currently supported for fieldmaps in pybids (#950)

@mattcieslak
Copy link
Collaborator

Either way, qsiprep has a very old bids-validator installed and is need of an update.

@mattcieslak mattcieslak added this to the 0.20 milestone Dec 11, 2023
@mattcieslak mattcieslak self-assigned this Dec 11, 2023
@mattcieslak mattcieslak removed this from the 0.20 milestone Jan 11, 2024
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

3 participants