Problem with RT dose

Support
1

Hi, I’m starting to use Slicer RT. The problem is that I have not found a manual to handle it. I’m using it thanks to my knowledge with Eclipse of Varian Eclipse but I have a problem when calculating the dose, I get the following error: “No study currentNode for reference dose” I think it has to do with the “

Captura%20de%20pantalla%20de%202019-01-22%2015%3A45%3A12
Captura%20de%20pantalla%20de%202019-01-22%2015%3A45%3A12971×700 117 KB
output dose volume” but I don’t know exactly what to do to fix it.

My steps are:

1- I download a sample image.
2- I paint the volumes with the segment editor.
3- I go to external beam planning and configure the beams.

That I have to do?
I upload a screenshot with the error

Many thanks.

2

@PaoloZaffino @gcsharp @cpinter

3

Hi,
did you try to set a new volume for output dose volume?

Paolo

4

I solved the problem. The issue was that sample images are not DICOM images. Once I loaded DICOM images, the sofware works.

1 Like
5

Sorry I missed this thread. The difference between DICOM and non-DICOM images are the subject hierarchy. In order to use dose volumes you need a subject and a study in which the anatomy image and the dose volume are. You can do it in the Data module.
https://www.slicer.org/wiki/Documentation/Nightly/Modules/Data#How_to

6

Should we be creating these automatically?

7

That’s an option but I feel it wouldn’t help things much.

If we add only the volume nodes automatically under a dummy patient and study, then it would be inconsistent.
On the other hand if we add all node types automatically then it would be the same problem as now, namely that there would be no meaningful grouping of all the different nodes, but a flat list under a study that is in reality meaningless. I think it would be more confusing as the user could feel that all the nodes belond to a study somehow.

From the RT point of view: if you have a dose volume under the dummy study, then the dummy study would contain the dose unit and the dose grid scaling, which, when exporting, will be needed to be moved under a different study (that has a name, contains just the nodes that are needed, etc.), and the new study won’t contain the same information unless explicitly specified. I think it is a greater hurdle than the current one; to create a real study and use that from the beginning.

Also not sure how it would conflict with the assignment of subjects when loading DICOM (there are multiple plugins implemented by different people), however, I think this issue could be avoided if we’re careful.

8

It could be possible to add some heuristics that would try to build the study automatically (and/or may ask for essential information from the user). It could be launched when the user wants to start computation and it is detected that the data is not under a study.

9

Yes, creating an operation-specific dummy study at the time of not finding a study might be a viable solution.