Isodoses in the 2D View don't display properly if the number of frames is not equal to the number of images

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Read a DICOM RT Dose file that has a different number of frames than image 
slices

What is the expected output? What do you see instead?
Isodoses should display properly, but instead they are either not shown or 
shown in the wrong location.

The fix is to use the tag Image Position (Patient) (0020,0032) tag in 
combination with the Grid Frame Offset Vector (3004,000C) tag to determine the 
start location and subsequent locations of the multi-frame dose matrix.

Original issue reported on code.google.com by bastula on 9 Oct 2010 at 7:06

[GoogleCodeExporter]

Original comment by bastula on 12 Nov 2010 at 4:23

• Added labels: Milestone-NextRelease

[GoogleCodeExporter]

This issue was closed by revision 27a20da390.

Original comment by bastula on 26 Nov 2010 at 9:43

• Changed state: Fixed

[GoogleCodeExporter]

By default, the dose is set to display if the dose plane is within 1.5 mm 
(threshold) of the CT image. If there is no dose plane within this range, the 
dose plane will be interpolated. This value is adjustable in dicomparser.py and 
will be user-modifable later on, once the preference interface is implemented.

Original comment by bastula on 26 Nov 2010 at 10:22

[GoogleCodeExporter]

This issue was updated by revision b2db1399c5.

Original comment by bastula on 27 Nov 2010 at 7:30

[GoogleCodeExporter]

This issue was updated by revision 9da0f34cf2.
This update has infinitely better contour generation with the added benefit of 
speed since the matplotlib backend is written in C.
The isodoses properly show multiple contours per isodose line and will respect 
holes in the particular curve.
The new curves are not as smooth as the curves generated by the previous 
method, but will be addressed in Issue 29.

Original comment by bastula on 10 Dec 2010 at 5:23