Hi Frederico,
Just a guess here but looks like it might be a problem with the dicom headers
of your mri data...I am not aware how MITK does the slice ordering (or how it
identifies slices to be of the same volume) but it might make use of different
headers than the 3M3 app. Ideally it should use ImagePositionPatient &
ImageOrientationPatient to do the ordering which are very standard ... but the
presence of other headers (that are not set correctly) might confuse it.
Examining the dicom headers of your series might shine more light ...
InstanceNumber (should be proportional to slice order)
SliceLocation (if it exists - should be proportional to slice order)
Also check that the SeriesNumber and UIDs (StudyInstanceUID , SeriesInstanceUID
etc.. ) are the same for all slices in your particular series
Hope it helps
Kind regards,
Lucas
From: [email protected]
[mailto:[email protected]] On Behalf Of Federico Milano
Sent: 15 March 2013 16:01
To: Fetzer, Andreas
Cc: [email protected]
Subject: Re: [mitk-users] Loading a DICOM volume
Hi Andreas,
If I load it with the Dicom Editor the Data Manager sees it as a single volume
(that's ok!!!) but it distorts it. You can see the kind of distorsion from the
screenshot.
Best regards,
Federico
On Thu, Mar 14, 2013 at 12:08 PM, Fetzer, Andreas
<[email protected]<mailto:[email protected]>> wrote:
Hi Frederico,
have you tried loading your data with our Dicom Editor? You can find
documentation here:
http://docs.mitk.org/nightly-qt4/org_mitk_gui_qt_dicom.html
Please note that the dicom editor is a rather new component in MITK and hence
it is currently experimental. However we are eager for feedback which helps us
to improve the dicom editor.
Best regards
Andreas
From: Federico Milano [mailto:[email protected]<mailto:[email protected]>]
Sent: Montag, 11. März 2013 15:51
To: [email protected]<mailto:[email protected]>
Subject: [mitk-users] Loading a DICOM volume
Hi. I'm using the ProjectTemplate application to load a MRI DICOM series
representing a volume in the Data Manager. The problem is that each image is
loaded as a different Data Node, and not as a single volumetric image (this
also happens in the workbench application). On the other hand, if I load it in
the MITK 3M3 Data Manager, the series is recognized as a volume and loaded as a
single data node. I know that MITK 3M3 is closed source and developed by a
private company, but do you have any clue if there is some difference in the
way DICOM files are treated? I'm working in research and I would really need to
load these images as a volume.
Thanks in advance,
Federico
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
