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

The inheritance principle is not completely supported #685

Open
tsalo opened this issue Jan 29, 2024 · 3 comments
Open

The inheritance principle is not completely supported #685

tsalo opened this issue Jan 29, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@tsalo
Copy link
Member

tsalo commented Jan 29, 2024

I haven't done anything near a complete inventory of where metadata is loaded in QSIPrep, but in at least one location (get_metadata_for_nifti), inherited metadata is not support.

I think the best solution is to use a BIDSLayout to load metadata instead of directly finding the (potentially multiple) JSONs associated with a NIFTI. This might be easier if we implement the Nipreps Config object.

@tsalo tsalo added the bug Something isn't working label Jan 29, 2024
@tsalo
Copy link
Member Author

tsalo commented Feb 1, 2024

Found another case, where bval and bvec files are grabbed based on the DWI filename. I'm not sure where in the code this happens (other than that it's in the merge workflow), but that seems to be the case.

Per chat with @mattcieslak, bvals should vary by run, but inheritance should definitely apply to magnitude and phase images, which come from the same run. So you'd typically have sub-X_dwi.bval for sub-X_part-mag_dwi.nii.gz and sub-X_part-phase_dwi.nii.gz.

@akimbler
Copy link

Partially related to this, I've noticed that when running qsirecon. I frequently get outputs that seem to be jammed together combinations of other input filenames with updated entities appended, rather than proper inheritance via entities.
image
image

@mattcieslak
Copy link
Collaborator

I agree, the qsirecon output names need a major overhaul. That's underway in #688 and will be in the next release. We're going to keep it close to BEP016

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

3 participants