Closed bendhouseart closed 5 months ago
@bendhouseart - I believe this might be happening because of inconsistent timing information in the json files (i.e. the data is not BIDS compliant). Please verify that the 4th dimension of the nifti files matches the number of entries in the timing information in the json files.
Well, you nailed it; seems like we're up/down 1 frame between NIfTI and json:
[galassiae@elgreco3 PDE4B_BIDS]$ mri_info sub-PF12/ses-test/pet/sub-PF12_ses-test_run-2_pet.nii.gz | grep dimensions
dimensions: 200 x 200 x 111 x 19
[galassiae@elgreco3 PDE4B_BIDS]$ cat sub-PF12/ses-test/pet/sub-PF12_ses-test_run-2_pet.json | jq -r 'values.FrameTimesStart'
[
8695.0,
8995.0,
9295.0,
9595.0,
9895.0,
10195.0,
10495.0,
10795.0,
11095.0,
11395.0,
11695.0,
11995.0,
12295.0,
12595.0,
12895.0,
13195.0,
13495.0,
13795.0
]
Have encountered an error during the
create_weighted_average_pet
during integration:Ultimately leads the pipeline failing when it fails to locate the weighted average later on down the line:
Same error occurs w/ or without running
--petprep_hmc
flag on this dataset.