Dicom2bids issue after Siemens upgrade - no pairing

[ebeanato]

Hello,

I am haveing some issues related to the pairing of a dwi sequence when using dicom2bids.

I have a a multishell aquisition in both AP and PA. In my config files I defined:

{
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "dir-AP",
            "criteria": {
                "ProtocolName": "*MultiShell_107dir*",
                "ImageType": ["ORIGINAL", "PRIMARY", "DIFFUSION", "NONE", "ND", "NORM", "MFSPLIT"]
            }
        },
	{
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-ADC_dir-AP",
            "criteria": {
		"ProtocolName": "*MultiShell_107dir*",
                "SeriesDescription": "*ADC*"
            }
        },
        {
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-TRACEW_dir-AP",
            "criteria": {
                "ProtocolName": "*MultiShell_107dir*",
                "SeriesDescription": "*TRACEW*"
            }
        },
        {
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-FA_dir-AP",
            "criteria": {
                "ProtocolName": "*MultiShell_107dir*",
                "SeriesDescription": "*_FA*"
            }
        },
        {
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-ColFA_dir-AP",
            "criteria": {
                "ProtocolName": "*MultiShell_107dir*",
                "SeriesDescription": "*ColFA*"
            }
        },
	{
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-ADC_dir-PA",
            "criteria": {
                "ProtocolName": "*MultiShell_b700_PA*",
                "SeriesDescription": "*ADC*"
            }
        },

        {
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-TRACEW_dir-PA",
            "criteria": {
                "ProtocolName": "*MultiShell_b700_PA*",
                "SeriesDescription": "*TRACEW*"
            }
        },
        {
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-FA_dir-PA",
            "criteria": {
                "ProtocolName": "*MultiShell_b700_PA*",
                "SeriesDescription": "*_FA*"
            }
        },
        {
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "acq-ColFA_dir-PA",
            "criteria": {
                "ProtocolName": "*MultiShell_b700_PA*",
                "SeriesDescription": "*ColFA*"
            }
        },
        {
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "dir-PA",
            "criteria": {
                "ProtocolName": "*MultiShell_b700_PA*",
                "ImageType": ["ORIGINAL", "PRIMARY", "DIFFUSION", "NONE", "ND", "NORM", "MFSPLIT"]
            }
        }

All files are converted and recognized apart the main dwi file in the AP direction (first sequence of the config file part above). In the json file in the tmp_dcm2bids folder I find the following entries which I then used in the config file:

• "ProtocolName": "MultiShell_107dir_bmax3000_1"
• "ImageType": ["ORIGINAL", "PRIMARY", "DIFFUSION", "NONE", "ND", "NORM", "MFSPLIT"]
  I don't understand since the other AP images (FA, ADC, ...) are paired whilst the main one not.

I also tried to use simply:

{
            "dataType": "dwi",
            "modalityLabel": "dwi",
            "customLabels": "dir-AP",
            "criteria": {
                "ProtocolName": "*MultiShell_107dir*",
            }
        },

Still, this does not work.

The terminal output always ends up to:
INFO:dcm2bids.sidecar:No Pairing <- 035_AVC215_T2_MultiShell_107dir_bmax3000_1_20221209094910_20230526_180055565000_1.3.12.2.1107.5.2.43.166081.300000221209113

Do you have an idea why the sequence is not recognized?

Thank you very much in advance

[audreymhoughton]

Hi @ebeanato - do you have an estimate on how many subjects this problem affects?

[ebeanato]

Hi,

thank you for replying, in this moment at least 3 different subjects, either one or two sessions

[audreymhoughton]

Hi @ebeanato - Thanks for identifying that subject count for me! Unfortunately, we haven't had a chance to dive into this yet. We've got quite a few subjects with issues on our plate right now, so we will only be able to address this after some time due to the small subject count. Thank you again for bringing it to our attention. If you encounter more subjects with this issue or a new one, please let us know! We appreciate the help.