FAILED execution of DTIPrep with cryptic error code about dtiprep HOT 5 OPEN

Can you give a bit more info on how you run the tool? Is it called through Slicer or the command line?
which operating system?

Is there anything else in the log file?

Martin

from dtiprep.

Hello,
the same behaviour is on Ubuntu LTS (64bit) and on Debian 8 (64bit), only the exact number sometimes differ. In all cases, it is called from the commandline. I am attaching the stdout output (dtiprep.txt) and possibly relevant outputs. Let me know, it there is anything I can add to help to solve the issue.

Thanks
George

Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCReport.txt
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCReport_xml.txt

dtiprep.txt

from dtiprep.

Hi George
Finally got around to look at your report. A few comments:

• the tool seems to run all the way to the end, before faulting. Is there anything written out? What is the list of output data? The error could be not meaningful in your case.
• While I don't know what caused the error, your data is quite peculiar, and that may have lead to the faulty run:
  --there is really no baseline image, the lowest b-value seems be around 250 (which is the first DWI), is that correct?
  --That first image is really bad, DTIPrep rejects nearly all of its slices. Also the second DWI is rejected, so that it takes the third DWI as baseline for further processing. That DWI has a b of more than 1000.
  -- Not sure why DTIPrep did not recognize that there are no baselines. It should have quit after step 1.

from dtiprep.

Hi,
it is multiband dataset - actudally it outputs following files:

Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_XMLQCResult.xml
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCReport.txt
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed_DTI_frobeniusnorm.nrrd
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed_DTI_MD.nrrd
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed_DTI_colorFA.nrrd
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed_DTI_FA.nrrd
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed_DTI.nrrd
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed_IDWI.nrrd
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed_Baseline.nrrd
Fantom_20160219_001_051_cmrr_mbep2d_diff_bezpatu_QCed.nrrd

However, as B0 gets duscarded (and all the other images are b=1000) the rest of the calculation does not make much sense.

On the other hand, I am getting the above mentioned error on all datasets, so I believe this is not study-related :-(

from dtiprep.

Thanks George

I can see that all the output was generated, so the error must have happened right at the end. While we do not observe it here, it seems that there is actually no issue with the computation, so I would simply disregard this error.

Re the specific dataset, like you mentioned, after B0 discarding the rest of the DWI data cannot be salvaged (this shows why multiple B0's are a good thing).

from dtiprep.