QC Report falls on dMRI scans when no bval=0 found
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
SPN20 has scans where the bval is b=5 rather than 0 due to the protocol used in MODSOCCS (the bvalue varies slightly throughout the protocol). As a result dm_qc_report ends up failing entirely if it cannot find a b=0 volume in the dMRI despite the scan being fine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the dm_qc_report entry point and trace how it handles dMRI b-values when no b=0 volume is present. Reproduce the failure with an affected SPN20 scan, then verify that QC completes successfully for scans using b=5 volumes while retaining the existing behavior for scans with b=0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100