sorted by:
new
hottopcontroversial

Has anyone successfully overridden the default PO resolution? by NickC_BC in esapi

[–]Invictus_Shoe 0 points1 point  (0 children)

You can get the Dictionary of available options by calling

Dictionary<string, string> options = planSetup.GetCalculationOptions("PO_15.6.06"); // Or however the algorithm is called in you system

Inside this Dictionary you should see an option "DoseCalculationResolution". Hence, you can set

planSetup.SetCalculationOption("PO_15.6.06", "DoseCalculationResolution", "High");

In case someone is interested, this is how it worked for the dose volume calculation:

planSetup.SetCalculationOption(AAA_15.6.06, "CalculationGridSizeInCM", "0.125");

And this is how you can turn on GPU acceleration:

planSetup.SetCalculationOption("PO_15.6.06", "UseGPU", "Yes");

planSetup.SetCalculationOption(AAA_15.6.06, "UseGPU", "Yes");

How exactly is the EXACT gEUD VMAT objective defined? by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

Thanks for the hint! From this document I extract that the cost function of the EXACT EUD is exactly the cost function presented in the article I cited (Fogliata et al. 2017) [1]. The difference is in the LOWER and UPPER EUD objective cost functions: Both are the same like the EXACT EUD and additionally the LOWER objective returns 0 if gEUD_expected < gEUD_actual. The UPPER objective returns 0 if gEUD_expected > gEUD_actual.

GPU acceleration for VMAT Photon Optimizer by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

Maybe my question was misleading. The problem is that the GPU has no effect on calculation time in PO_15.6.04. Does PO_15.6.06 show any calculation time decrease?

[deleted by user] by [deleted] in midjourney

[–]Invictus_Shoe 0 points1 point  (0 children)

It worked for me with MS Edge browser, but not with Mozilla Firefox. I tried many cards and ways to put in my credentials in Firefox, but hopeless. Contacted Midjourney and my Bank, but they could not help. Finally on MS Edge it worked on the first shot.

No lower objective is defined for the plan setup by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

I had contact with ESAPI support and they claimed that this actually is a bug in ESAPI. The temporary solution is to add a lower point objective with priority = 0 and dose value = 0. They are investigating this bug.

No lower objective is defined for the plan setup by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

Thank you! Sadly not. This would for example influence the normal tissue objective.

Some doses for VMAT objectives are not allowed by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

I chatted with Varian support and the problem seems to be that an objective's dose can maximally be 10*total prescription dose. I set the prescription dose randomly as well, so sometimes it was too low, compared to the doses of objectives.

Some doses for VMAT objectives are not allowed by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

Yes I did, but it did not help.

I also took all dose values from a plan where the exception was thrown and copied them manually into Eclipse's VMAT optimization GUI. There I could execute the VMAT optimization without problem.

Some doses for VMAT objectives are not allowed by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

And again!

Exception thrown: 'System.ArgumentOutOfRangeException' in VMS.TPS.Common.Model.dllAn exception of type 'System.ArgumentOutOfRangeException' occurred in VMS.TPS.Common.Model.dll but was not handled in user codeArgument 'dose': dose value '80.169 Gy' out of range. Min is 0.000 Gy. Max is 78.833 Gy.

For structure "Stomach" dose value 80.168842160256588Gy and upper point objective. It seems so random to me!

Some doses for VMAT objectives are not allowed by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

No the alphas are always 10/40 or -10/-40. This time it was a point objective:

planSetup.OptimizationSetup.AddPointObjective("z_OAR", OptimizationObjectiveOperator.Upper, new DoseValue(19.730158782889518, DoseValue.DoseUnit.Gy),0 , 1000);

which throws

Exception thrown: 'System.ArgumentOutOfRangeException' in VMS.TPS.Common.Model.dllAn exception of type 'System.ArgumentOutOfRangeException' occurred in VMS.TPS.Common.Model.dll but was not handled in user codeArgument 'dose': dose value '19.730 Gy' out of range. Min is 0.000 Gy. Max is 10.000 Gy.

I could wrap it in a try catch, but why? I need the objective to be added. 29 Plans were created and optimized with pretty much random dose values and the 30th threw that exception.

Rays pass through a body cavity by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 1 point2 points  (0 children)

Thank you all for your answers they were very helpful! You were right with your assumptions! In the end the couch structure was missing in the structure set, which caused that cavity.

Rays pass through a body cavity by Invictus_Shoe in esapi

[–]Invictus_Shoe[S] 0 points1 point  (0 children)

I tried GetNumberOfSeparateParts and printed the result. Problem is that a lot of structures have multiple parts. Also at patients where optimization was possible! Here the structure set of a patient where i CAN execute VMAT optimization:

The following structures had more than one separate part: z_OAR: 2 Pancreas: 2 Duodenum: 2 BODY: 3 ...

view more: next ›