MR images not recognized as an image series

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open a folder containing a set of MR dicom images.
2. dicompyler will not recognize this as an image series.
3. You will not be able to click 'Select' to view these images in the program.

What is the expected output? What do you see instead?
That it identifies it as an image series, e.g. (MR, 34 images)
That you can select it and view the images as with a CT image series.

What version of the product are you using? On what operating system?
dicompyler version 0.4a2, Windows XP

Please provide any additional information below.
It would be nice if dicompyler worked with MR images too, as this modality is 
being used in radiotherapy too.

Best regards,
Chris

Original issue reported on code.google.com by chris.le...@gmail.com on 2 Aug 2011 at 7:36

Attachments:

• ct.PNG
• mr.png

[GoogleCodeExporter]

It is rather easy to make MR data show up in dicompyler (only a few lines 
required).

However, support needs to be added to the 2D view to properly display the 
orientation and image for coronal and sagittal views that are common in MR.

Original comment by bastula on 12 Aug 2011 at 6:58

• Changed state: Accepted

[GoogleCodeExporter]

I see, so the issue is not about display of MR vs CT, but rather the support of 
image orientation of the images related to the patient.

May I propose as a first (simple) solution, of instead of looking at the 
modality for deciding on whether the image series is supported or not, that you 
look at the Image Orientation (Patient) tag (0020,0037), and accepts the image 
series if it has the simple, normal axial orientation, e.g. '1\0\0\0\1\0'?

Perhaps display a reason of why it is not accepted if it deviates from this 
orientation?

Of course, ideally, I think it would be great if dicompyler were able to handle 
images with ANY orientation. I have some MR images with non-orthogonal scan 
axis, and it would be awesome if I could display such image series in 
dicompyler too. Though I understand that this will take some work to implement 
and likely can not be expected in a short term...

Best regards!
Chris

Original comment by chris.le...@gmail.com on 12 Aug 2011 at 9:03

[GoogleCodeExporter]

Hi Chris,

Thanks for the suggestion. Based on what you described, I think the best way is 
to detect whether the patient has the IOP tag in the first place (which would 
mean it is a volumetric image series is present). This would also allow PET 
images (and volumetric images which I am not familiar with) to also be 
displayed.

Currently, dicompyler just looks for the CT SOP Class UID. I was originally 
planning to add SOP Class UIDs for all the important classes, but I think using 
IOP detection would be better since it is more generalized.

However, there is a small bug that needs to be corrected first such that the 
dicompyler is loading multiple series when only a single series is selected.

Once that bug is fixed, I should be able to add IOP detection support, and 
following that add the orientation markers.

In the mean time, I have attached a screen shot showing CT, MRI, and PET 
support.

Adit

Original comment by bastula on 16 Aug 2011 at 2:19

Attachments:

• CT_MRI_PET_support.png

[GoogleCodeExporter]

This issue was closed by revision 57d9155cc415.

Original comment by bastula on 24 Aug 2011 at 1:13

• Changed state: Fixed