Page MenuHomePhabricator

Error loading DCE-MRI DICOM image
Open, HighPublic

Description

To whom it may concern,

I use MITK-v2018.04.02-windows-x86_64
I encountered an error while loading DCE-MRI DICOM image.
This problem is in some case (loading 77 DCE-MRI images and 12 images had this problem)


I don't quite understand the meaning of the error message.
So I would like to ask how to solve such an error to successfully load the image.

I adopted the extended tofts model to estimate the features of BBB permeability.
Another problem is that I want to know the meaning of fit starting parameters (e.g. Ktrans Value: 15. Does it mean that the Ktrans value start from 15? However, Ktrans value is considered to be in the range of 10-4 to 10-3 min-1 )

The other problem is that I want to know the formula of relative signal enhancement and the meaning of conversion factor k (Conversion: Signal to Concentration)

Thank you !

Sincerely,Sharon Yu

Event Timeline

sharonYu created this task.May 20 2020, 8:29 AM
sharonYu added a project: MITK.
sharonYu triaged this task as High priority.May 21 2020, 9:24 AM
sharonYu edited projects, added MITK (2020); removed MITK.
floca moved this task from Backlog to Perfusion on the MITK (2020) board.
floca added a subscriber: floca.

Hi, thanks for reporting the problem. I think it is caused by a known problem fixed by T27321: [DICOM reader] DICOM 3D+t image reader should condense only images of the same series.. To verify the assumption you could either:

  1. test the loading with a current master build of mitk
  2. or ensure that only the DCE dicom files are in the directory (e.g. no scout images or other sequences) while loading. This option would also be your workarround if you want to use an older version.

Please let us know if the problem can be solved by 1 or 2, thus iif it is realy the known problem or a so far unknown problem. Thanks.

floca added a subscriber: kompan.May 22 2020, 2:53 PM

@kompan FYI I think the loading error is a known/fixed issue (see above).

Hi,

I try these two method to solve the problem.
However, they didn't work.

@sharonYu OK. damn. Would it be possible to provide pseudonomized test data that shows the problem?
Just to be sure. Could you load one of the cleaned directories that still have a problem in the MITK DICOM Browser and check how much series are detected? Thanks.

It seems that all the test data (dce_2CXM_ValidationDataSet) load successfully.

It seems that all the test data (dce_2CXM_ValidationDataSet) load successfully.

Thanks for the info!
To improve the chance to pinpoint the problem, we either need on problematic data set or at least you should scan one of the directories with the MITK DICOM Browser and check how many series were detected. Thanks.

We scan the raw DCE-MR image directory using the MITK DICOM Browser and got the correct Dicom information in the list. However, the error message showed when pressing the View bottom.


floca added a comment.Jun 1 2020, 11:22 AM

@sharonYu Thanks for the update. It seems to realy be an so far unkown problem. Would it be possible to provide an anonymized data set to debug the situation and see what is happening in code?

The zip file below is the DCE-MR image.

floca edited projects, added Cleared, DICOM; removed Missing Info.Jun 3 2020, 10:05 PM

@sharonYu Thanks for the data. That helped to identify the problem.

Reason is that the dynamic time information is completly encoded in the triggertime and the AcquesitionTime (1) only encodes seconds and (2) has no meanding for the dynamic sequence. We hadn't such an interpretation of the DICOM standard so far. To fix this properly some aditions rework in our DICOM sorting logic are needed.

sharonYu added a comment.EditedJun 16 2020, 3:46 PM

@floca

I am sorry for being late reply.

I would like to ask the DICOM file loading problem could you help us solve it?
Or will the new version of MITK improve the function of DICOM file loading?