Open WillForan opened 2 months ago
What about fmap_...
(no dash)?
no -
(eg fmap_acq-rest
) works well! but the output still has heudiconv*_e1
instead of _echo-1
. Or maybe it should be magintude1
? And I think these are phase instead of phasediff(?)
tree -P '*nii.gz' -I '*_dicom'
.
└── fmap
├── sub-testbr_acq-dwi_magnitude_heudiconv710_e1.nii.gz
├── sub-testbr_acq-dwi_magnitude_heudiconv710_e2.nii.gz
├── sub-testbr_acq-dwi_magnitude_heudiconv710_e3.nii.gz
├── sub-testbr_acq-dwi_phasediff_heudiconv025_e1_ph.nii.gz
├── sub-testbr_acq-dwi_phasediff_heudiconv025_e2_ph.nii.gz
└── sub-testbr_acq-dwi_phasediff_heudiconv025_e3_ph.nii.gz
Summary
We collect a GRE fieldmap like that on issue #158 (phantom DICOM and nifti attached!, and here's a quick mp4 video scrolling through what they look like is).
I'd like to name the acquisition on the scanner inline with the ReproIn spec so the
reproin.py
heuristic can just "do the right thing"™ . But the single gre fieldmap series on the scanner produces dicoms with two series numbers: the first for the magnitude images and the second for the phase.I think the ideal name would be like
fmap-magnitude_acq....
orfmap-phasediff_acq...
but which ever we pick will mean half are labeled wrong.I tried a copy of the dicoms with the protocol (tag
0018,1030
) changed to the under-specifiedfmap-_acq-fl2
and get close
Platform details:
Choose one:
[x] Local environment
[ ] Container
Heudiconv version: