Having trouble getting fMRIprep to see phasdif and magnitude images

Hi,

I am not able to get fMRIprep to see my phasedif and mag images for distortion correction. I’ve scrolled through the BIDS rules and seem to be compliant. Not sure what I am missing here.

What I have tried…

  1. run a bids check and it’s not throwing any errors
  2. removing and adding an intendedfor field in the magnetic files
  3. adding a “readouttime” in the phsediff.json - just to see if it solved issue as above
  4. making sure the file names are correct and the same between phasedif and magnitude files
  5. removed the sub-utxxx/ from the intended field
  6. running with an updated version of the fMRIprep
  1. running without a bids_filter file

fMRIprep version 23.1.3 (having to run an old version)

Here are the fieldmap names…

image

Here is the json for the phasediff image

{
    "Modality": "MR",
    "MagneticFieldStrength": 3,
    "ImagingFrequency": 123.22341,
    "Manufacturer": "Siemens",
    "ManufacturersModelName": "MAGNETOM Vida",
    "InstitutionName": "UT Health Austin 3T",
    "InstitutionalDepartmentName": "Radiology",
    "InstitutionAddress": "Trinity 1601B,Austin,Houston,US,78712",
    "DeviceSerialNumber": "175689",
    "StationName": "AWP175689",
    "BodyPartExamined": "BRAIN",
    "PatientPosition": "HFS",
    "SoftwareVersions": "syngo MR XA31",
    "MRAcquisitionType": "2D",
    "SeriesDescription": "GRE-FieldMapping - MagnusMed",
    "ProtocolName": "GRE-FieldMapping - MagnusMed",
    "ScanningSequence": "GR",
    "SequenceVariant": "SP",
    "PulseSequenceName": "*fm2d2r",
    "ImageType": [
        "ORIGINAL",
        "PRIMARY",
        "P",
        "NONE",
        "PHASE"
    ],
    "ImageTypeText": [
        "ORIGINAL",
        "PRIMARY",
        "P",
        "DIS2D"
    ],
    "NonlinearGradientCorrection": true,
    "SeriesNumber": 9,
    "AcquisitionTime": "15:09:29.007500",
    "AcquisitionNumber": 1,
    "SliceThickness": 2,
    "SpacingBetweenSlices": 2,
    "EchoNumber": 2,
    "EchoTime": 0.00719,
    "TotalReadoutTime": 0.0939838,
    "RepetitionTime": 0.779,
    "MTState": false,
    "FlipAngle": 60,
    "EchoTime1": 0.00473,
    "EchoTime2": 0.00719,
    "B0FieldIdentifier": "phasediff",
    "PartialFourier": 1,
    "BaseResolution": 64,
    "ShimSetting": [
        -1781,
        -1870,
        9335,
        269,
        -353,
        -149,
        103,
        91
    ],
    "TxRefAmp": 322.4,
    "PhaseResolution": 1,
    "ReceiveCoilName": "HeadNeck_64_CS",
    "ReceiveCoilActiveElements": "HC1-7",
    "CoilString": "HeadNeck_64_CS",
    "PulseSequenceDetails": "%SiemensSeq%\\gre_field_mapping",
    "CoilCombinationMethod": "Sum of Squares",
    "MatrixCoilMode": "SENSE",
    "PercentPhaseFOV": 100,
    "PercentSampling": 100,
    "PhaseEncodingSteps": 64,
    "FrequencyEncodingSteps": 64,
    "AcquisitionMatrixPE": 64,
    "ReconMatrixPE": 64,
    "AcquisitionDuration": 98.922,
    "PixelBandwidth": 1056,
    "DwellTime": 7.4e-06,
    "PhaseEncodingDirection": "j",
    "ImageOrientationPatientDICOM": [
        0.999998,
        0.000114196,
        -0.00201576,
        -6.02368e-08,
        0.998401,
        0.0565311
    ],
    "InPlanePhaseEncodingDirectionDICOM": "COL",
    "ConversionSoftware": "dcm2niix",
    "IntendedFor": "ses-01/func/sub-ut0010_ses-01_task-rest_dir-AP_run-01_bold.nii.gz",
    "ConversionSoftwareVersion": "v1.0.20230411",
    "Dcm2bidsVersion": "3.1.0"
}

Hi @AustinBipolar,

I mentioned this in your earlier post (Dcm2bids version 3.1.0 intended for field - #5 by AustinBipolar), but you need to remove the leading sub-utxxx/ from the IntendedFor field. Also, for future posts, please surround the contents of json files with tick marks so it looks nicely formatted

Like this

Best,
Steven

Sorry, I added ticks. Also, I ran it without the "sub-utxxx/ in the IntendedFor field but hadn’t listed it as “something I tried above”. I amended this now though in the original post. It’s still not finding the fieldmaps when I made this change.

Can you share the command you ran please? And the output of tree run on the subject directory? And if you have it, the beginning of the fmriprep output log that should include the SDCflows setup.

Code through singularity container

module load tacc-singularity

find /scratch/06953/jes6785/NNDC_JAN_22/derivatives/fmriprep-23.1.3_JAN_24_dist_corr/sourcedata/freesurfer/sub-ut0010/ -name *IsRunning* -type f -delete

unset PYTHONPATH; singularity run -e \

-B /scratch/06953/jes6785/NNDC_JAN_22/ \

-B /scratch/06953/jes6785/HOME/opt/templateflow:/opt/templateflow \

-B /scratch/06953/jes6785/WORK/ \

/work/06953/jes6785/Containers/fmriprep_23.1.3.sif \

/scratch/06953/jes6785/NNDC_JAN_22/ /scratch/06953/jes6785/NNDC_JAN_22/derivatives/fmriprep-23.1.3_JAN_24_dist_corr/ participant \

--participant-label sub-ut0010 \

-w /scratch/06953/jes6785/WORK/ \

--fs-license-file /work/06950/jalmeida/ls6/apps/fmriprep/license.txt \

-v \

--skip_bids_validation \

--bids-filter-file /scratch/06953/jes6785/NNDC_JAN_22/fMRIprep_files_needed/ses-01_bf.json \

--stop-on-first-crash --output-spaces MNI152NLin2009cAsym:res-2 MNI152NLin2009cAsym:native --ignore slicetiming \

--fs-subjects-dir /scratch/06953/jes6785/NNDC_JAN_22/derivatives/fmriprep-23.1.3_nodistortion_correction/sourcedata \

--mem-mb 190000 --nthreads 4

sub-ut0010/
├── ses-01
│   ├── anat
│   │   ├── sub-ut0010_ses-01_rec-normDefaced_T1w.json
│   │   └── sub-ut0010_ses-01_rec-normDefaced_T1w.nii.gz
│   ├── dwi
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-AP_dwi.bval
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-AP_dwi.bvec
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-AP_dwi.json
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-AP_dwi.nii.gz
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-PA_dwi.bval
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-PA_dwi.bvec
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-PA_dwi.json
│   │   ├── sub-ut0010_ses-01_acq-sbref_dir-PA_dwi.nii.gz
│   │   ├── sub-ut0010_ses-01_dir-AP_dwi.bval
│   │   ├── sub-ut0010_ses-01_dir-AP_dwi.bvec
│   │   ├── sub-ut0010_ses-01_dir-AP_dwi.json
│   │   ├── sub-ut0010_ses-01_dir-AP_dwi.nii.gz
│   │   ├── sub-ut0010_ses-01_dir-PA_dwi.bval
│   │   ├── sub-ut0010_ses-01_dir-PA_dwi.bvec
│   │   ├── sub-ut0010_ses-01_dir-PA_dwi.json
│   │   └── sub-ut0010_ses-01_dir-PA_dwi.nii.gz
│   ├── fmap
│   │   ├── sub-ut0010_ses-01_acq-spinechofmap_dir-AP_epi.json
│   │   ├── sub-ut0010_ses-01_acq-spinechofmap_dir-AP_epi.nii.gz
│   │   ├── sub-ut0010_ses-01_magnitude1.json
│   │   ├── sub-ut0010_ses-01_magnitude1.nii.gz
│   │   ├── sub-ut0010_ses-01_magnitude2.json
│   │   ├── sub-ut0010_ses-01_magnitude2.nii.gz
│   │   ├── sub-ut0010_ses-01_phasediff.json
│   │   └── sub-ut0010_ses-01_phasediff.nii.gz
│   ├── func
│   │   ├── sub-ut0010_ses-01_task-rest_dir-AP_run-01_bold.json
│   │   ├── sub-ut0010_ses-01_task-rest_dir-AP_run-01_bold.nii.gz
│   │   ├── sub-ut0010_ses-01_task-rest_dir-AP_run-02_bold.json
│   │   ├── sub-ut0010_ses-01_task-rest_dir-AP_run-02_bold.nii.gz
│   │   ├── sub-ut0010_ses-01_task-rest_dir-AP_run-03_bold.json
│   │   ├── sub-ut0010_ses-01_task-rest_dir-AP_run-03_bold.nii.gz
│   │   ├── sub-ut0010_ses-01_task-rest_dir-AP_run-04_bold.json
│   │   └── sub-ut0010_ses-01_task-rest_dir-AP_run-04_bold.nii.gz

Note I tried running without the bidsfilter file - I know it’s probably something obvious but I can’t find it as have been looking at this for several hours. I’ve also been running it so the fieldmaps are only applied to the first resting state run 01. once I get it to work I’ll apply to all of them.

Forgot this one

240122-18:05:44,880 nipype.workflow IMPORTANT:
	 Running fMRIPrep version 23.1.3

         License NOTICE ##################################################
         fMRIPrep 23.1.3
         Copyright 2023 The NiPreps Developers.
         
         This product includes software developed by
         the NiPreps Community (https://nipreps.org/).
         
         Portions of this software were developed at the Department of
         Psychology at Stanford University, Stanford, CA, US.
         
         This software is also distributed as a Docker container image.
         The bootstrapping file for the image ("Dockerfile") is licensed
         under the MIT License.
         
         This software may be distributed through an add-on package called
         "Docker Wrapper" that is under the BSD 3-clause License.
         #################################################################
240122-18:05:44,882 nipype.workflow WARNING:
	 Previous output generated by version 0+unknown found.
240122-18:05:45,552 nipype.workflow IMPORTANT:
	 Building fMRIPrep's workflow:
           * BIDS dataset path: /scratch/06953/jes6785/NNDC_JAN_22.
           * Participant list: ['ut0010'].
           * Run identifier: 20240122-180501_2ab35969-e758-40a2-bb46-01e5c57095b7.
           * Output spaces: MNI152NLin2009cAsym:res-2 MNI152NLin2009cAsym:native-True:res-native.
           * Pre-run FreeSurfer's SUBJECTS_DIR: /scratch/06953/jes6785/NNDC_JAN_22/derivatives/fmriprep-23.1.3_nodistortion_correction/sourcedata.
240122-18:05:46,374 nipype.workflow INFO:
	 No single-band-reference found for sub-ut0010_ses-01_task-rest_dir-AP_run-01_bold.nii.gz.
240122-18:05:46,813 nipype.workflow INFO:
	 No single-band-reference found for sub-ut0010_ses-01_task-rest_dir-AP_run-02_bold.nii.gz.
240122-18:05:47,125 nipype.workflow INFO:
	 No single-band-reference found for sub-ut0010_ses-01_task-rest_dir-AP_run-03_bold.nii.gz.
240122-18:05:47,431 nipype.workflow INFO:
	 No single-band-reference found for sub-ut0010_ses-01_task-rest_dir-AP_run-04_bold.nii.gz.
240122-18:05:51,5 nipype.workflow INFO:
	 fMRIPrep workflow graph with 1027 nodes built successfully.

Can you run without --skip-bids-validation and return the BIDS validation report in the beginning? And this is without the leading sub-utXXX/ in the IntendedFor? And also remove the --bids_filter_file for now. Feel free to share the contents here so we can see if it would have an impact.

Here it is, it complains about my perfusion files and my ses-02 fieldmap - which are both not bids complain, but there are no error relating to my ses-01 fmap or func files. (sorry, I didn’t paste these scans into the above as I felt it was too much information). This is when I ran without my bids_filter_file.

Making sure the input data is BIDS compliant (warnings can be ignored in most cases).
bids-validator@1.11.0
(node:393052) Warning: Closing directory handle on garbage collection
(Use `node --trace-warnings ...` to show where the warning was created)
	1: [ERR] Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder. (code: 1 - NOT_INCLUDED)
		./fMRIprep_files_needed/ses-01_bf.json
			Evidence: ses-01_bf.json
		./fMRIprep_files_needed/ses-01_bfwd.json
			Evidence: ses-01_bfwd.json
		./fMRIprep_files_needed/ses-01r_bf.json
			Evidence: ses-01r_bf.json
		./fMRIprep_files_needed/ses-02_bf.json
			Evidence: ses-02_bf.json
		./fMRIprep_files_needed/ses-02_bfwd.json
			Evidence: ses-02_bfwd.json
		./fMRIprep_files_needed/ses-03_bf.json
			Evidence: ses-03_bf.json
		./fMRIprep_files_needed/ses-03_bfwd.json
			Evidence: ses-03_bfwd.json
		./fMRIprep_files_needed/ses-event_bf.json
			Evidence: ses-event_bf.json
		./fMRIprep_files_needed/ses-event_bfwd.json
			Evidence: ses-event_bfwd.json

	Please visit https://neurostars.org/search?q=NOT_INCLUDED for existing conversations about this issue.

	2: [ERR] You must define 'RepetitionTimePreparation' for this file. 'RepetitionTimePreparation' is the interval, in seconds, that it takes a preparation pulse block to re-appear at the beginning of the succeeding (essentially identical) pulse sequence block. The data type number may apply to files from any MRI modality concerned with a single value for this field. The data type array provides a value for each volume in a 4D dataset and should only be used when the volume timing is critical for interpretation of the data, such as in ASL. (code: 200 - REPETITION_TIME_PREPARATION_MISSING)
		./sub-ut0010/ses-01/perf/sub-ut0010_ses-01_acq-3dpcasl_asl.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-3dpcasl_asl.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-calShortTR_m0scan.nii.gz

	Please visit https://neurostars.org/search?q=REPETITION_TIME_PREPARATION_MISSING for existing conversations about this issue.

	3: [ERR] M0Type was not defined correctly. If 'M0Type' is equal to separate, the dataset should include a *_m0scan.nii[.gz] and *_m0scan.json file. (code: 202 - M0Type_SET_INCORRECTLY)
		./sub-ut0010/ses-01/perf/sub-ut0010_ses-01_acq-3dpcasl_asl.nii.gz
			Evidence: /sub-ut0010/ses-01/perf/sub-ut0010_ses-01_acq-3dpcasl_m0scan.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-3dpcasl_asl.nii.gz
			Evidence: /sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-3dpcasl_m0scan.nii.gz

	Please visit https://neurostars.org/search?q=M0Type_SET_INCORRECTLY for existing conversations about this issue.

	1: [WARN] Each _phasediff.nii[.gz] file should be associated with a _magnitude1.nii[.gz] file. (code: 92 - MISSING_MAGNITUDE1_FILE)
		./sub-ut0010/ses-02/fmap/sub-ut0010_ses-02_acq-fmapPH_phasediff.nii.gz

	Please visit https://neurostars.org/search?q=MISSING_MAGNITUDE1_FILE for existing conversations about this issue.

	2: [WARN] The recommended file /README is missing. See Section 03 (Modality agnostic files) of the BIDS specification. (code: 101 - README_FILE_MISSING)

	Please visit https://neurostars.org/search?q=README_FILE_MISSING for existing conversations about this issue.

	3: [WARN] The Authors field of dataset_description.json should contain an array of fields - with one author per field. This was triggered because there are no authors, which will make DOI registration from dataset metadata impossible. (code: 113 - NO_AUTHORS)

	Please visit https://neurostars.org/search?q=NO_AUTHORS for existing conversations about this issue.

	4: [WARN] It is recommended to define 'VascularCrushing' for this file. 'VascularCrushing' is a boolean value indicating if an ASL crusher method is used. (code: 137 - VASCULAR_CRUSHING_MUST_DEFINE)
		./sub-ut0010/ses-01/perf/sub-ut0010_ses-01_acq-3dpcasl_asl.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-3dpcasl_asl.nii.gz

	Please visit https://neurostars.org/search?q=VASCULAR_CRUSHING_MUST_DEFINE for existing conversations about this issue.

	5: [WARN] It is recommended to define 'AcquisitionVoxelSize' for this file. 'AcquisitionVoxelSize' is an array of numbers with a length of 3, in millimeters. This parameter denotes the original acquisition voxel size, excluding any inter-slice gaps and before any interpolation or resampling within reconstruction or image processing. Any point spread function effects (e.g. due to T2-blurring) that would decrease the effective resolution are not considered here. (code: 143 - ACQUISITION_VOXELSIZE_MISSING)
		./sub-ut0010/ses-01/perf/sub-ut0010_ses-01_acq-3dpcasl_asl.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-3dpcasl_asl.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-calShortTR_m0scan.nii.gz

	Please visit https://neurostars.org/search?q=ACQUISITION_VOXELSIZE_MISSING for existing conversations about this issue.

	6: [WARN] It is recommended to define 'BackgroundSuppressionPulseTime' for this file, when the 'BackgroundSuppression' is set to true. 'BackGroundSuppressionPulseTime' is an array of numbers containing timing, in seconds, of the background suppression pulses with respect to the start of the labeling. In case of multi-PLD with different background suppression pulse times, only the pulse time of the first PLD should be defined. (code: 144 - BACKGROUND_SUPPRESSION_PULSE_TIME_MISSING)
		./sub-ut0010/ses-01/perf/sub-ut0010_ses-01_acq-3dpcasl_asl.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-3dpcasl_asl.nii.gz

	Please visit https://neurostars.org/search?q=BACKGROUND_SUPPRESSION_PULSE_TIME_MISSING for existing conversations about this issue.

	7: [WARN] It is recommended to define 'BackgroundSuppressionNumberPulses' for this file, in case 'BackgroundSuppression' is set to true. 'BackgroundSuppressionNumberPulses' is the number of background suppression pulses used. Note that this excludes any effect of background suppression pulses applied before the labeling. (code: 179 - BACKGROUND_SUPPRESSION_PULSE_NUMBER_MISSING)
		./sub-ut0010/ses-01/perf/sub-ut0010_ses-01_acq-3dpcasl_asl.nii.gz
		./sub-ut0010/ses-02/perf/sub-ut0010_ses-02_acq-3dpcasl_asl.nii.gz

	Please visit https://neurostars.org/search?q=BACKGROUND_SUPPRESSION_PULSE_NUMBER_MISSING for existing conversations about this issue.

        Summary:                  Available Tasks:             Available Modalities: 
        598 Files, 46.81GB        JH resting state A>>P        MRI                   
        10 - Subjects             resting state                                      
        3 - Sessions                                          

For reference, here is my BIDS filter file for session 01

{
    "t1w": {
        "datatype": "anat",
        "session": "01",
        "suffix": "T1w"
    },
    "t2w": {
        "datatype": "anat",
        "session": "01",
        "suffix": "T2w"
    },	
    "bold": {
        "datatype": "func",
        "session": "01",
        "suffix": "bold",
	"direction": "AP"
    }
}

(edit to remove as earlier comment was deleted)

Would it be possible to share one subject’s data?

I should also note that the version you’re using is notoriously not great with GRE field maps. 23.2.0 should do the trick.

Tried the updated version too :frowning: No joy :frowning:

You could try to get rid of those BIDS validation error with a .bidsignore file but I don’t think it would solve your issue with the fieldmap.

Could you try to remove the "IntendedFor" line in the fmap json file? I got reports from users for who there was an issue when both IntendedFor and B0FieldIdentifier were present in a json file. (Don’t forget to add a B0FieldSource in the json file of the target func images).

Thanks - I also saw this thread…

So, I have a field map which dcm2bids labeled a phasedif and two (names have changed slightly from what I mentioned above) magnitude images. Here is what I have named them.
sub-ut0010_ses-01_acq-rest_magnitude1.nii.gz
sub-ut0010_ses-01_acq-rest_magnitude2.nii.gz
sub-ut0010_ses-01_acq-rest_phasediff.nii.gz

func images are labeled
sub-ut0010_ses-01_task-rest_dir-AP_run-01_bold.nii.gz

In the JSON files, I have tried… (tried #1 below with BOTH fmriprep v 23.1.3 and 23.2.0). I should say that this DOESN’T THROW A BIDS VALIDATION ERROR when trying that.

  1. Only a B0FieldIdentifier (all above fieldmaps JSONS) and B0FieldSource (BOLD) that look like this…

FMAPS (Phasdif and Mag)

"B0FieldIdentifier": "acq_rest"

FUNC

 "B0FieldSource": "acq_rest"
  1. Only using the “IntendedForFields” in BOTH the BOLD and FIELDMAP (phasdif+magnitude) JSON

FMAP (phasdiff+magnitude)

 "IntendedFor": "ses-01/func/sub-ut0010_ses-01_task-rest_dir-AP_run-01_bold.nii.gz"

BOLD

"IntendedFor": "ses-01/fmap/sub-ut0010_ses-01_acq-rest_phasediff.nii.gz"

or

"IntendedFor": [
        "ses-01/fmap/sub-ut0010_ses-01_acq-rest_phasediff.nii.gz",
        "ses-01/fmap/sub-ut0010_ses-01_acq-rest_magnitude1.nii.gz",
        "ses-01/fmap/sub-ut0010_ses-01_acq-rest_magnitude2.nii.gz"
    ],

Still No luck; what am I missing here? Is having these magnitude images possibly causing the issues?

Also, for complete disclosure… Here is an example of my func json, obviously the IntendedFor/ B0 field changes as mentioned above.

{
    "Modality": "MR",
    "MagneticFieldStrength": 3,
    "ImagingFrequency": 123.223407,
    "Manufacturer": "Siemens",
    "ManufacturersModelName": "MAGNETOM Vida",
    "InstitutionName": "UT Health Austin 3T",
    "InstitutionalDepartmentName": "Radiology",
    "InstitutionAddress": "Trinity 1601B",
    "DeviceSerialNumber": "175689",
    "StationName": "AWP175689",
    "BodyPartExamined": "BRAIN",
    "PatientPosition": "HFS",
    "SoftwareVersions": "syngo MR XA31",
    "MRAcquisitionType": "2D",
    "SeriesDescription": "rs1-fMRI-SMS - MagnusMed",
    "ProtocolName": "rs1-fMRI-SMS - MagnusMed",
    "ScanningSequence": "EP",
    "SequenceVariant": "SK",
    "ScanOptions": "PFP\\FS",
    "PulseSequenceName": "*epfid2d1_128",
    "ImageType": [
        "ORIGINAL",
        "PRIMARY",
        "FMRI",
        "NONE"
    ],
    "ImageTypeText": [
        "ORIGINAL",
        "PRIMARY",
        "M",
        "ND"
    ],
    "NonlinearGradientCorrection": false,
    "SeriesNumber": 10,
    "AcquisitionTime": "15:13:14.395000",
    "AcquisitionNumber": 1,
    "SliceThickness": 2,
    "SpacingBetweenSlices": 2,
    "EchoTime": 0.031,
    "RepetitionTime": 1.3,
    "MTState": false,
    "FlipAngle": 77,
    "PartialFourier": 0.75,
    "BaseResolution": 128,
    "ShimSetting": [
        -1765,
        -1885,
        9387,
        282,
        -277,
        -33,
        235,
        108
    ],
    "TxRefAmp": 322.4,
    "PhaseResolution": 1,
    "ReceiveCoilName": "HeadNeck_64_CS",
    "ReceiveCoilActiveElements": "HC1-7",
    "CoilString": "HeadNeck_64_CS",
    "PulseSequenceDetails": "%SiemensSeq%\\ep2d_bold",
    "RefLinesPE": 22,
    "CoilCombinationMethod": "Sum of Squares",
    "MultibandAccelerationFactor": 6,
    "PercentPhaseFOV": 100,
    "PercentSampling": 100,
    "EchoTrainLength": 96,
    "PartialFourierDirection": "PHASE",
    "PhaseEncodingSteps": 128,
    "FrequencyEncodingSteps": 128,
    "AcquisitionMatrixPE": 128,
    "ReconMatrixPE": 128,
    "BandwidthPerPixelPhaseEncode": 10.557,
    "ParallelAcquisitionTechnique": "SMS",
    "EffectiveEchoSpacing": 0.00074003,
    "DerivedVendorReportedEchoSpacing": 0.00074003,
    "AcquisitionDuration": 402.18,
    "TotalReadoutTime": 0.0939838,
    "PixelBandwidth": 1628,
    "DwellTime": 2.4e-06,
    "PhaseEncodingDirection": "j-",
    "SliceTiming": [
        0,
        0.69,
        0.1,
        0.7875,
        0.1975,
        0.8875,
        0.295,
        0.985,
        0.395,
        1.0825,
        0.4925,
        1.1825,
        0.59,
        0,
        0.69,
        0.1,
        0.7875,
        0.1975,
        0.8875,
        0.295,
        0.985,
        0.395,
        1.0825,
        0.4925,
        1.1825,
        0.59,
        0,
        0.69,
        0.1,
        0.7875,
        0.1975,
        0.8875,
        0.295,
        0.985,
        0.395,
        1.0825,
        0.4925,
        1.1825,
        0.59,
        0,
        0.69,
        0.1,
        0.7875,
        0.1975,
        0.8875,
        0.295,
        0.985,
        0.395,
        1.0825,
        0.4925,
        1.1825,
        0.59,
        0,
        0.69,
        0.1,
        0.7875,
        0.1975,
        0.8875,
        0.295,
        0.985,
        0.395,
        1.0825,
        0.4925,
        1.1825,
        0.59,
        0,
        0.69,
        0.1,
        0.7875,
        0.1975,
        0.8875,
        0.295,
        0.985,
        0.395,
        1.0825,
        0.4925,
        1.1825,
        0.59
    ],
    "ImageOrientationPatientDICOM": [
        0.998889,
        0.0368238,
        0.0294159,
        -0.0392464,
        0.995475,
        0.0865407
    ],
    "InPlanePhaseEncodingDirectionDICOM": "COL",
    "ConversionSoftware": "dcm2niix",
    "ConversionSoftwareVersion": "v1.0.20230411",
    "Dcm2bidsVersion": "3.1.0",
    "B0FieldSource": "acq_rest"
}

Hi @AustinBipolar

You don’t need (and perhaps shouldn’t use) IntendedFor in the BOLD JSON

No that shouldn’t be an issue.

I am happy to take a look at your data if you can share it.

Best,
Steven

Ok, removed the intended for from the BOLD and still didn’t work. Was just trying to add in both as per this comment in this link…

To test version 23.1.3, I excluded the B0Field from all jsons and included the IntendedFor for AP/PA and all BOLD jsons accordingly. It worked. This also worked with version 21.0.1.

This issue was solved offline (after file renaming and metadata altering to fit BIDS validity).