You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am dealing with an error that I could not find anything similar to that in the forum. I am running MRIQC on my multi-shell diffusion data. I have encountered any issue below:
Stderr:
++ 3dvolreg: AFNI version=AFNI_22.2.07 (Aug 19 2022) [64-bit]
++ Authored by: RW Cox
�[7m*+ WARNING:�[0m If you are performing spatial transformations on an oblique dset,
such as /nesi/nobackup/uoa04027/Processed_mtay316/.mriqc_tmp/mriqc_wf/dwiMRIQC/_in_file_..nesi..nobackup..uoa04027..Processed_mtay316..bids..sub-case14..ses-c..dwi..sub-case14_ses-c_run-001_dwi.nii.gz/hmc_shells/mapflow/_hmc_shells2/sub-case14_ses-c_run-001_dwi_valid_b0.nii.gz,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:/nesi/nobackup/uoa04027/Processed_mtay316/.mriqc_tmp/mriqc_wf/dwiMRIQC/_in_file_..nesi..nobackup..uoa04027..Processed_mtay316..bids..sub-case14..ses-c..dwi..sub-case14_ses-c_run-001_dwi.nii.gz/hmc_shells/mapflow/_hmc_shells2/sub-case14_ses-c_run-001_dwi_valid_b0.nii.gz is 6.185800 degrees from plumb.
�[7m** FATAL ERROR:�[0m You can't register a 1 brick dataset to itself!
** Program compile date = Aug 19 2022
Traceback:
Traceback (most recent call last):
File "/opt/conda/lib/python3.9/site-packages/nipype/interfaces/base/core.py", line 453, in aggregate_outputs
setattr(outputs, key, val)
File "/opt/conda/lib/python3.9/site-packages/nipype/interfaces/base/traits_extension.py", line 330, in validate
value = super(File, self).validate(objekt, name, value, return_pathlike=True)
File "/opt/conda/lib/python3.9/site-packages/nipype/interfaces/base/traits_extension.py", line 135, in validate
self.error(objekt, name, str(value))
File "/opt/conda/lib/python3.9/site-packages/traits/base_trait_handler.py", line 74, in error
raise TraitError(
traits.trait_errors.TraitError: The 'oned_matrix_save' trait of a VolregOutputSpec instance must be a pathlike object or string representing an existing file, but a value of '/nesi/nobackup/uoa04027/Processed_mtay316/.mriqc_tmp/mriqc_wf/dwiMRIQC/_in_file_..nesi..nobackup..uoa04027..Processed_mtay316..bids..sub-case14..ses-c..dwi..sub-case14_ses-c_run-001_dwi.nii.gz/hmc_shells/mapflow/_hmc_shells2/sub-case14_ses-c_run-001_dwi_valid_b0.aff12.1D' <class 'str'> was specified.
I thought the error is due to the registration. After I used " -deoblique" I still got the same error. I used "-vvv" to get more verbose and see where the problem is. After checking the log, I noticed that the algorithm identified 5 volumes while I have four volume in my scan (0,1000,2000,3000). After checking my bval file, I realised that my 1000 and 2000 are fine, but my 3000 has one 2995 and two 3005 values. And interestingly, MRIQC recognises 2995 as a seperate shell [49]. Like below:
Okay, I've re-read the issue and in fact, the problem is you only have 4 volumes. In #1240 we prevented these datasets from being run. These could be addressed in the future as, e.g., EPI/PEPOLAR fieldmaps. For now, we will have to leave them out unsupported.
Hi MRIQC team,
I am dealing with an error that I could not find anything similar to that in the forum. I am running MRIQC on my multi-shell diffusion data. I have encountered any issue below:
Stderr:
I thought the error is due to the registration. After I used " -deoblique" I still got the same error. I used "-vvv" to get more verbose and see where the problem is. After checking the log, I noticed that the algorithm identified 5 volumes while I have four volume in my scan (0,1000,2000,3000). After checking my bval file, I realised that my 1000 and 2000 are fine, but my 3000 has one 2995 and two 3005 values. And interestingly, MRIQC recognises 2995 as a seperate shell [49]. Like below:
And most of the errors refers to shell2:
I am still not sure if this the issue or not. It would be great if you can help me with that.
Regards,
Maryam
The text was updated successfully, but these errors were encountered: