foni / dicompyler

Automatically exported from code.google.com/p/dicompyler
0 stars 0 forks source link

RTPlan dose obtained incorrectly - workaround found #55

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What is the expected output? What do you see instead?
70.00 Gy as prescirbed dose (total), I got the 14.00 (per beam) instead. This 
is due our RTPlan is storing dose references as:
Identical for Target / each beam
300a,0014 (DOSE Reference Sructure) = SITE
300a.0020 (Dose Reference Type) = TARGET
difference occours tat Dose Reference Description (300a,0016)

The problem occurs in my case when the if loop is trying to obtain the 'rxdose' 
which will be overwrited if similar items happens later in the RTPLAN which 
meets the criteria. For example if I export
data where target dose is 70.00, but the beams (x5) target dose is 14.00 and 
they occur later, the program will get the 14.00 instead of 70.00 for target 
prescribed dose.

Workaround / solution:
dicomparser.py file after line 578 I added the following line:
if item.TargetPrescriptionDose * 100 > self.plan['rxdose']:

this will overwrite the previous rxdose only if there is a higher number 
avaliable.

What version of the product are you using? On what operating system?
Ubuntu 10.11 + dicomplyer 0.42a

Please provide any additional information below.

Original issue reported on code.google.com by Akos.Gul...@gmail.com on 23 Nov 2011 at 9:26

Attachments:

GoogleCodeExporter commented 9 years ago
Thank you for catching this and providing a workaround. I have just committed a 
change like you suggested.

Can you provide an anonymized copy of the DICOM RT Plan file for testing? You 
may attach it to this issue or upload it via other means.

Original comment by bastula on 25 Nov 2011 at 8:55

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 8453c2daed63.

Original comment by bastula on 25 Nov 2011 at 8:57

GoogleCodeExporter commented 9 years ago
Here is the attachment with the example RTPLAN and the main.py (how I altered 
for the version 0.4a2 version).

This is a more appropriate way as this takes not only the appropriate dose but 
the same description (consistently)

I have one more question, which way do you prefer that I send a data that your 
program is compatible with our in-house developed TPS?

Thanks for the info and for your effort

Original comment by Akos.Gul...@gmail.com on 2 Jan 2012 at 7:16

Attachments:

GoogleCodeExporter commented 9 years ago
Thanks for the updated patch.

Do any of your plans that use VOLUME references use the description / name tag 
('DoseReferenceDescription') ? From the data I have seen, VOLUME references use 
the description of 'TARGET' which is not that useful.

The zip file that you sent is appropriate. Thank you for sending the example RT 
Plan file.

Original comment by bastula on 2 Jan 2012 at 6:41