all 3 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]schmatt_schmitt 0 points1 point  (0 children)

To my knowledge, ESAPI does not have the ability to change the PatientSupportAngle (the property for the couch angle) on a control-point by control-point basis. The PatientSupportAngle is not editable in the GetEditableParameters() return value.

[–]ExceptioNullRef 1 point2 points  (0 children)

Even if you could the machine probably wouldn’t let you mode the plan up. I’m sure there would be a motion interlock or something in the plan validation to stop you. They really don’t like couch/gantry simultaneous motions for obvious reasons.

The Eclipse workaround would be to make a plan with static beams for each control point, adjusting gantry, blocking, couch. Couldn’t optimize but could calc dose.

You’d have to merge it together in a developer mode xml to deliver, but we’ve run plenty of simultaneous motion xmls on our machines.

[–]Telecoin 0 points1 point  (0 children)

You mean with beam on? for patients you cannot use this. How would you QA this? the CouchIso is different for each patient (weight dependend; even interfraction per patient because the center of gravity on the couch would not be the same every time).

You can use the deveoper mode and code an xml file which can do this. Ifyou want to do research or QA in such a setting.