update_bids_layout.py misses DWI .bval/.bvec renaming and IntendedFor in DWI json file #7

Open
opened 2026-07-03 16:53:19 +00:00 by ron · 1 comment
Member

While using update_bids_layout.py to update the Mannheim and Heidelberg Q01 BIDS datasets, I noticed two issues with the DWI updates:

1. The script renames the DWI NIfTI and JSON files (e.g. adding dir-PA), but does not rename the corresponding .bval and .bvec files. As a temporary workaround, I implemented a small script (rename_dwi_bval_bvec.py) to rename them
2. The reverse PE EPI JSONs moved to fmap/ do not receive an IntendedFor entry pointing to the corresponding DWI image. I therefore had to add this manually using add_dwi_intendedfor.py

I compared this with the original fix_dwi_sdc.sh script, which correctly handled both the .bval/.bvec renaming and the IntendedFor update. It looks like these two steps may have been omitted during the Python port.

Adding these two updates would make the resulting dataset fully BIDS compliant and remove the need for manual post processing.

While using update_bids_layout.py to update the Mannheim and Heidelberg Q01 BIDS datasets, I noticed two issues with the DWI updates: 1. The script renames the DWI NIfTI and JSON files (e.g. adding dir-PA), but does not rename the corresponding .bval and .bvec files. As a temporary workaround, I implemented a small script (rename_dwi_bval_bvec.py) to rename them 2. The reverse PE EPI JSONs moved to fmap/ do not receive an IntendedFor entry pointing to the corresponding DWI image. I therefore had to add this manually using add_dwi_intendedfor.py I compared this with the original fix_dwi_sdc.sh script, which correctly handled both the .bval/.bvec renaming and the IntendedFor update. It looks like these two steps may have been omitted during the Python port. Adding these two updates would make the resulting dataset fully BIDS compliant and remove the need for manual post processing.
Member

Thanks for paying close attention! I need to take a closer look, I expected everything to be OK. I will get back to you on Monday.

Thanks for paying close attention! I need to take a closer look, I expected everything to be OK. I will get back to you on Monday.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
q02/rdmtools#7
No description provided.