topasmc / dicom-interface

DICOM RT Interface for TOPAS
MIT License
23 stars 8 forks source link

Plan_tutorial.txt #13

Open mem0r1 opened 3 years ago

mem0r1 commented 3 years ago

Hi

I have read the Wiki and followed the tutorials which are contained there.

I have noticed the plan_tutorial.txt file. The view.txt example has also a line (commented out by default): #includeFile = plan_tutorial.txt refering to it. Running view.txt with includeFile = QA_tutorial.txt with topas seems to work fine and outputs a .Dw file. I have also tried running with includeFile = plan_tutorial.txt, as far as I unterstood also a Patient_Dw file should be outputed, which however doesnt happen.

Just to assure that I unterstand everything correctly:

Thanks for your excellent work on this project and many thanks for your support.

Best regards

Stephan

ferdymercury commented 1 year ago

@jungwookshin Do you know why running plan_tutorial.txt does not produce any output?

ferdymercury commented 1 year ago
  • The plan_tutorial.txt should simulate a proton plan irradation ?

Yes, I think so.

* The DW files contain the dose ?

Yes. @jungwookshin is it in Gy or in another unit? Could you add this info to the Wiki?

* How are the DW files encoded ? How to read them ?

Double64, little endian. You can open them using for example "Amide", File, Import, Raw Data, select the number of bins equal to the ones you can see in the .binheader text file. If you run the QA_tutorial, set for example:

image

This might be also something for the wiki.

* Is there an additional purpose of running the `treatment_session` executable on its own, besides testing ?

It's mainly for testing https://github.com/topasmc/dicom-interface/wiki/test-with-cli. Other than that, this interface can be used outside of TOPAS, for combination with other programs, so that could be one reason, to provide one example on how to use it outside.

* Should plan_tutorial.txt output DW files by default or do I have to change some setting ?

I think it should, but it doesn't.

* The rbe_1p1_complete.hpp file contains the variables
  `treatment_machine_ion<T>::SAD_[0] = 1800.0; treatment_machine_ion<T>::SAD_[1] = 2000.0;`
  and also `rti::treatment_machine_ion<T>::source_to_isocenter_mm_`

* Are the two SAD_ components equivalent to the Virtual Source axis distance in DICOM Tag (300a,030a) ?

Yes. See https://github.com/topasmc/dicom-interface/issues/5#issuecomment-647629800 and https://github.com/topasmc/dicom-interface/issues/5#issuecomment-649787803 but right now they ones from the DICOM file are ignored. It's in the TO-DO list.

* Where can the source_to_isocenter specification be found for a particular machine ? The Dicom files we have do not contain such a specification. Is the source_to_isocenter distance measured along the Z-axis of the Gantry coordinate system ?

This is something your manufacturer can inform you about, or you can measure experimentally. Yes, it's the Z coordinate.

jungwookshin commented 1 year ago

@jungwookshin Do you know why running plan_tutorial.txt does not produce any output?

The following line was missing and now it was added and pushed.

Sc/DoseGrid_Dw/Quantity = "DoseToWater"