Handling external contours in 2D display

[GoogleCodeExporter]

2D structure/contour view is looking good. 

I am wondering what the best way to deal with external/skin contours. I suspect 
there is no standard name for this. Maybe the user should be able to designate 
the structure as external or simply "filled".

The attached file shows an external contour of a head. The "expected" behavior 
is that the contour only displays on the skin itself and is not filled in. That 
seems to be the standard behavior for TPS's.

Using the latest revisions as of 19 June 2010.

Original issue reported on code.google.com by roy.coding@gmail.com on 20 Jun 2010 at 6:22

Attachments:

• external-contour1.jpg

[GoogleCodeExporter]

Yes, I was thinking about this as well. It turns out that all the special types 
of contours (GTV, CTV, etc) are listed in the RT Structure Set file under RT 
ROI Observations Sequence (see DICOM standard Part 3 Section C.8.8.8 for the 
complete listing of special contours). The external/body/skin is marked as 
EXTERNAL and we can detect that.

I will try to address this issue so that dicomparser includes this information 
so that the 2D View can read it before rendering the contours.

Take a look at the screenshot to see where the information is stored.

Original comment by bastula on 20 Jun 2010 at 6:47

Attachments:

• ROIobservations.png

[GoogleCodeExporter]

I think I have fixed this in my repo.

See this revision (718cdbf31a):

http://code.google.com/r/roycoding-dicompyler/source/detail?r=718cdbf31accd82a37
1f0623730a02671881d263

I can roll a patch if you'd like or you can pull the changes.

Original comment by roy.coding@gmail.com on 21 Jun 2010 at 1:23

Attachments:

• external-contour2.jpg

[GoogleCodeExporter]

This issue was closed by revision 790ce2a665.

Original comment by bastula on 21 Jun 2010 at 3:16

• Changed state: Fixed