Skip to content

Fieldmaps acquired during each part of a session splits into two not differentiated #624

@neurorepro

Description

@neurorepro

It is relatively common to have a single theoretical session splits practically into two sessions due to the length of the protocol, so e.g. anat, task 1, task 2, fmap in the morning and DWI, task 3, fmap in the afternoon.

heudiconv can deal with this with the option -g all to group all files no matter the series UID which changes after each practical session and would give an error otherwise.

The issue I am having is that when the grouping is applied to a dataset with a fieldmap having the same series id (e.g. 2_myfieldmap) during each practical session, the two fieldmaps are not differentiated as can be seen in dicominfo.tsv. The resulting detected fieldmap magnitude ('M' in protocol type) has then twice the number of files, and same for the phase, resulting in this kind of output for conversion:

│       │   ├── sub-s01_ses-01_magnitude1.json
│       │   ├── sub-s01_ses-01_magnitude1.nii.gz
│       │   ├── sub-s01_ses-01_magnitude2.json
│       │   ├── sub-s01_ses-01_magnitude2.nii.gz
│       │   ├── sub-s01_ses-01_magnitude3.json
│       │   ├── sub-s01_ses-01_magnitude3.nii.gz
│       │   ├── sub-s01_ses-01_magnitude4.json
│       │   ├── sub-s01_ses-01_magnitude4.nii.gz
│       │   ├── sub-s01_ses-01_phasediff1.json
│       │   ├── sub-s01_ses-01_phasediff1.nii.gz
│       │   ├── sub-s01_ses-01_phasediff2.json
│       │   └── sub-s01_ses-01_phasediff2.nii.gz

Would there be any suggestion on how to tackle this issue ?

Would the only solution be to convert each practical session (i.e. with a unique study UID) separately and group them later in a single theoretical session ? This would be quite cumbersome and a shame considering the great -g option normally made for this kind of case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions