Home

TrueBeam Developer Mode - Radiotherapy Research Tools

1. Clear All Fault Interlocks Routine Interlocks eam Gantry amp Collimator Program Actual Program Program Techriqu sey 7 Energy ide mv z CT tng EIR cm CoR Lat 996 3 Rag Asym v kV Imager Vrt BREE cm Coll Y1 IEEE c Lng BEC cm Lng I 8729 cm Lat cm Lat EEFI cm Meter Range o 1200 R rn NENNT Scale Varian IEC gt j xi EEA kv Source vrt TEY cm Collect Trajectory Log L tM o 80 008 _tov0_1209 Z E S S status aes C Set Defauk Beam zx SE MIC cesses Open Standard Template Beam Open Custom Beam Positions rrents PWMS co pyffnication MLC Display Diagnostics Detached MLC Display Installed MLC Model NDS120 Initialized o F Commands NDS120 LED Diagnostics General e Power Brake Eu m Communication 9 collimator 96 0 iscale Varian TEC CorrB Retract LimSw Carra Retract Limsw Initialized o Status Ready CarrB Extend LimSw CarrA Extend LimSw eo Indirectly setting up the KV foils kV filters and kV collimators Unfortunately Developer Mode is currently unable to directly position the kV collimators also known as kV blades kV imaging foils and kV imaging filters Therefore if your XML Beam requests either kV imaging foils and or kV imaging filters or if the XML Beam requests specific positions for the kV collimators then you must use the following process to indirectly set up tho
2. eeeeeeeeeeseseeneeenee enne ennt enne nnne nnne 58 APPENDIX B Accessories List PEE Qe 78 Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 ii Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Introduction This document describes how to use the Developer Mode research capabilities of the Varian TrueBeam linear accelerator Developer Mode uses virtually the same control system as the TrueBeam Clinical modes However Developer Mode also enables access to additional more advanced control features which are not typically accessible or used by the Clinical Modes The user interface for Developer Mode is patterned after Service Mode Developer Mode is permitted access to the full set of capabilities that have been built into the TrueBeam control system Unlike the Clinical Modes which are typically driven by plans downloaded through a DICOM interface Developer Mode is driven by XML Beams loaded from local storage or network on the TrueBeam control console workstation computer XML Beams are essentially text scripts in XML format where a rich instruction set allows Developer Mode users to construct and deliver complex non standard beams imaging and gating In other words it is this ability of Developer Mode to load and deliver XML beams that gives Developer Mode users full access to the complete dynamic bea
3. Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 79
4. ImageMode id DynamicGainFluoro lt CalibrationSet gt IMG CBCT lt CalibrationSet gt lt ImageDestination gt ImageDestination lt ImageDestination gt lt KV gt KiloVolts 100 KiloVolts MilliAmperes 20 MilliAmperes lt MilliSeconds gt 20 lt MilliSeconds gt lt eFocalSpot gt Large lt eFocalSpot gt eFluoroLevelControl None eFluoroLevelControl lt KV gt lt AcquisitionParameters gt lt AcquisitionStart gt lt Comment out foils and KV collimation for now lt KvFilters gt lt Foil gt 1 lt Foil gt lt Shape gt 1 lt Shape gt lt KvFilters gt lt KvBlades gt lt Positions gt KVX1 13 3 KVX1 KVX2 13 3 KVX2 KVY1 10 0 KVY1 KVY2 10 0 KVY2 lt Positions gt lt KvBlades gt gt lt ImagingPoint gt 1 Stop the KV fluoro acquisition at 90 degrees ImagingPoint lt Cp gt 2 5 lt Cp gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 46 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt AcquisitionStop gt AcquisitionId 1 AcquisitionId AcquisitionSpecs AcquisitionStop ImagingPoint ImagingPoints ImagingTolerances RR RR KR eoo eoe eoe K K K K K K KK K K K K K K OK K K K Here are the gating parameters FK KK K K 2 2 K K K FK FK FK FK K K AK K K FK K FK FK FK K 2K 2 FK 2K FK FK K K
5. Validating an XML beam For an XML Beam to be valid it must conform to the TrueBeam XML Beam schema i e it must be syntactically valid It is typically convenient to check the syntactic validity of beams off line before attempting to load them into Developer Mode as the TrueBeam accelerator is typically not available for experimentation at all times There are many simple commercially available XML editors and a host of other programs such as Microsoft Excethat can be used to do this validation off line on most PCs While simple syntactic validation against the schema does not guarantee that the XML beam will be acceptable to the accelerator the chance of simple syntax errors is notheless reduced Many errors such as for example the position of an axis specified in an XML beam being outside of the mechanical range cannot be detected by simple schema validation and thus the accelerator control system may still find further errors on an XML beam that has otherwise passed simple schema validation Loading and delivering an XML Beam This section details how an XML beam is loaded into the TrueBeam control system and delivered i e step 3 in figure 6 To launch Developer Mode select the Research option from the Major Mode Selection menu Then type the appropriate User ID and Password Once in Developer Mode you can load an XML Beam using the Load Plan button and selecting Open Custom Beam from the menu A standard Windows file
6. don t care This means that for these axes the control system will allow the user to beam on at any position Below are some additional progressively more complicated XML beam examples It is also possible to look at some of the XML beams that the TrueBeam control system itself generates While Developer Mode cannot directly deliver DICOM plans the Treatment modes convert every DICOM plan that is loaded into the control system into an XML Beam Therefore any DICOM plan that is deliverable through the TrueBeam Treatment mode can also be translated in its equivalent XML Beam format For more details see the section Using a DICOM file as a starting point Introducing static positions and tolerances The following example adds enforcement of specific static positions and tolerances before the beam can be turned on lt VarianResearchBeam SchemaVersion 1 0 gt lt I mK KK AK K K K K K K K ok ok ok K K K K FK K K K CE CE CE CE K CK CE CE OK K FK CE CE CE CE K K CE CE CE OK CE CE CE K K K CE CE CE K K CE CE CE OK K OE FK E OK FK K K K K K OK K OK OK OK OK K 1 200 MU at 400MU min dose rate static field gt lt Requires that some axes are positioned within tolerance prior to beam on gt lt l KKK K K K K K K K K K K K K K K K FK FK K K K CE CE FK K CK CE FK K CK CE CE CE K K K K K CE CE K K FK K K K CE K K K K K CE K K K FK K OK FK FK FK K K K K K OK OK K K K gt lt SetBeam gt lt I
7. eeesee idest eene enne enne ee e eese nen nnt rennes nnns estne nent 7 The simplest example Beam On BB ES 7 Introducing static positions and tolerances ssssssssessseseeeeee eene eene nnne nennt n nnns n nri n nnns nnns 10 Adding static fields 090 ABER MDD ssssesscescersaseaees 13 A Dynamic Beam eeeee Eee Teese Een nnn nnn nnn nnn nas 15 MLC Carriage Movements 85 OO es MUDD s occeeeeeseeesesssccececesececesesesesseeseseees 17 Specifying Dose Rate and Velocity limits eese esee eee nnnns 17 The Time Element Dose Rates Axis Speeds and Beam Delivery Time sseeeeeeeeere 19 Velocity Limits 999b BM ose asecceceseesso MMMDbgsceseessnatecsecececsessnatsccecesassensnatsceececsesensnatseescersassaaea 20 IMAZING MEER Emm MED RD 21 The Imdgiljg ParameterS Sestion Mff EOD scocesccsssensccssssssccsessnsccsssssecsenensdcsesassecseanscesssaaaeees 21 Taking two MV and two kV images concurrent with beam eeseessseeeeeeeee nennen enne nnne 21 Imaging Modesme 0898 eo MUM ececescessnsateccececsessassatsececersessncnecscesseusessnnecteceseesessnanecseceseess 26 Using Dummy Contigllipoints BBB cccsessccssssssccsssssccssssssecsssenscesssansecsennsccsensssecsenansdcsesnsecsensnscesesaaaeees 28 Imaging Arm Positions Tolera
8. gt gt gt gt gt gt gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 74 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs complexType gt lt xs Sequence gt lt xs element minOccurs 0 maxOccurs 1 name Energy type xs string gt lt xs element minOccursz 0 maxOccurs 1 name DoseRate type xs double gt lt xs sequence gt xs complexType xs element lt END OF MV parameters gt lt RR RR ok K K K K K K K K K K K K K K K K K K K FK FK FK FK K K K K K K 2K 2K OK OK K K OK KOK KOK KOK KOK kV has more parameters ee K K K K K K K K 2 2 FK FK 2 FK K K 2 K K K K K FK FK FK FK FK 2K 2K K K K K FK 2 2K 2K 2 K K K K K K KKK K os lt xs element name KV gt lt xs complexType gt lt xs Sequence gt lt xs element minOccurs 1 maxOccurs 1 name KiloVolts type xs double gt lt xs element minOccurs 1 maxOccurs 1 name MilliAmperes type xs double gt lt xs element minOccurs 1 maxOccurs 1 name MilliSeconds type xs double gt lt xs element minOccurs 0 maxOccurs 1 name eFocalSpot default Large lt xs simpleType gt xs restriction base xs string gt xs enumeration value Small gt lt xs enumeration value Large gt xs restriction xs simpleType lt xs element gt END OF eFocalSpot
9. 1 gt lt RR k K K K K k K K K K ok eoe K K K K K FK K K K K K K K K K FK FK FK K K K K K FK 2K 2K K AK K K K FK FK FK 2K K K 2 K FK FK FK FK K K K OK K OK K KOK KKK oos lt Specify a String identifier for this Research beam optional gt lt d k KK EA EK k k k k KEk k k kk k k k k k k k 2 2 2 k OK OK OK k k k k KK OK OK ROK cos lt xs element name GUID type xs string minOccurs 0 maxOccurs 1 gt 4 mn RR E K K K K K K K K K k K K K K K K AK K k K K KK K K K K K K K K FK K K K K K 2 K 2K K K K K k 2K K KK K K FK K FK K 2K K K OK K K K KOK ROKK oos lt Specify the MLC model required for this ResearchBeam Optional gt lt Rule If MLC model is specified machine will accept experiment plan gt lt only if equipped with same MLC model gt lt RR K K k K K K K K K K K K K K K K K K K K FK K K K K K K K K K FK FK FK K K K K K K K 2K K AK K K 2 K FK 2K 2K 2K AK 2K K FK FK FK FK K K K OK K K K KOK KKK oos lt xs element name MLCModel minOccurs 0 maxOccurs 1 gt lt xs simpleType gt xs restriction base xs string lt Three types of MLCs are possible 80 leaf 120 leaf and 1201eaf high definition xs enumeration value NDS80 gt xs enumeration value NDS120 xs enumeration value NDS120HD xs restriction xs simpleType xs element lt RR RR KK oko A A A A oe oe poke ooo ook 2 2 K K K K 2 2K KK KK 2K OK K K OK K KK KOK KK oos lt Specify
10. END OF MVAcquisitionTrigger gt lt xs element name KVAcquisitionTrigger gt xs complexType xs complexContent lt xs extension base AcquisitionTrigger gt lt xs complexContent gt lt xs complexType gt lt xs element gt lt END OF KVAcquisitionTrigger gt xs choice lt xs sequence gt xs complexType xs element lt END OF GatingParameters gt lt xs sequence gt xs complexType xs element END OF ImagingParameters gt lt RR RRR RK K K K K K K K K K K KK OK FK FK FK K OK K OK K K OK OK OK BEAM HOLD DEVICES Optional BeamHoldDevice Definition The planned beam hold devices RULES 1 A missing beam hold device means that the beam hold devie must not be ready 2 A present beam hold device must be ready 3 The MV beam gets held if the beam hold device requests to held the beam 4 Id attribute specifies the id of the beam hold device number between and 15 FK K ee K K K K K K K K K FK FK FK FK FK FK K K K K K 2 AK K K K KK K K K K K K K KK KKK oo Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 71 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs element name BeamHoldDevices minOccurs maxOccurs 1 gt lt xs complexType gt Xs sequence lt xs element name Dev minOccurs 0 lt x
11. KVY1 gt lt KVY2 gt 10 0 lt KVY2 gt lt Positions gt lt KvBlades gt lt ImagingPoint gt t Stop the KV fluoro acquisition at 90 degrees lt ImagingPoint gt lt Cp gt 2 5 lt Cp gt lt AcquisitionStop gt lt AcquisitionId gt 1 lt AcquisitionId gt lt AcquisitionSpecs gt lt AcquisitionStop gt lt ImagingPoint gt lt ImagingPoints gt lt ImagingTolerances gt lt ImagingParameters gt lt SetBeam gt lt VarianResearchBeam gt Example 9 Taking continuous images If a continuous image acquisition is started but never stopped then it continues until the end of the beam at which point it is turned off automatically The line lt ImageDestination gt ImageDestination lt ImageDestination gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 36 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Causes the control system to save evey single images it takes in continuous mode Axis numbering Sometimes during control system operation error messages relating to a specific mechanical axis are displayed These axes are often referred to by numerical index Following is a table of the numerical index convention for axes Index Axis Index Axis Index Axis 1 Gantry Rotation 2 Collimator Rotation 3 Couch Vertical Couc
12. NV gt lt AcquisitionParameters gt lt Acquisition gt lt ImagingPoint gt lt ImagingPoints gt lt ImagingTolerances gt lt ImagingParameters gt lt SetBeam gt lt VarianResearchBeam gt Example 7 Dummy control points facilitate specifying where exactly images are to be acquired One imaging programming style could be to specify a dummy control point for every imaging action So a dummy control point in ControlPoints is created for every imaging action specified in the ImagingPoints These dummy control points act as reference handles for the imaging section and the imaging section can be written to reference only the dummy control points Imaging Arm Positions Tolerances and Motions The previous examples did not specify positions for the imager arms It was assumed that the imaging arms would be placed at the proper imaging positions prior to beam on However it is possible to specify explicit positions for one or more of the three imaging arms These positions must be specified through the Imaging Points elements in the Imaging Section of the XML beam It is also possible to specify tolerances associated with these arm positions Finally it is possible to move one or more of the three imaging arms during the beam However as previously mentioned imaging arm motions do NOT follow the linear segment model as other motions do If a beam specifies motions for one or more of the imaging arms then
13. The TrueBeam control system employs many algorithms and active servo control mechanisms to ensure that the actual MU vs position trajectory delivered matches the linear segmented trajectory specified by the user in the XML file or other planning entity if in Treatment Mode Generally the control system will actively compute and manage MU delivery velocity of moving parts acceleration of moving parts and segment transitions to match the actual trajectory with the planned segmented trajectory So for example if MU delivery were to temporarily slow down somewhat due to unexpected transient phenomena the control system will proportionately slow down all moving axes so that beam progression continues along the planned segmented trajectory When a beam first starts or every time the respiratory gate closes and beam resumes if the beam is gated the beam and motion of every moving axis are ramped up according to a pre calculated acceleration profile The objective is to accommodate the moving axis exhibiting the most demanding instantaneous inertia characteristics If motion on a moving axis stops or is not responding to motion velocity or acceleration commands as expected by its motion model then beam delivery is halted and a fault is generated In general during beam delivery including beamless segments the control system continuously logs the radiation delivered and position of every moving axis every 10 msec or 20 msec time interval depend
14. 0 926 1 626 0 175 0 475 0 475 0 075 0 525 0 625 0 325 1 025 1 825 2 025 1 625 1 025 0 525 0 326 0000000000000000909090909090 A lt Ml1c gt lt Cp gt lt second control point Just deliver 110 MU without moving gt Cp Mu 110 Mu Cp lt third control point No MU just move gantry to new position and Mlc to new shape gt Cp GantryRtn 90 00 GantryRtn Mlc lt ID gt 1 lt ID gt lt B002000000000000000 0 0 0 988 0 235 0 775 0 995 1 475 1 525 1 52 8250 25 3 625 R825 1 325 3 725 3 125 0 725 1 925 1 620 0 170 0 50000000000000000 0 0 0 O0 O O B 0000000000000000 0 0 O 0 218 0 115 0 826 0 826 1 666 Nb 0 775 0 9m 0 275 0 525 0 825 0 725 1 025 1 725 2 325 2 025 1 425 0 720 0 92000000000000000000 900 0 0 O A M1c 7 Cp lt fourth control point Just deliver 72 MU 2182 110 without moving anything Cp Mu 182 Mu Cp ControlPoints SetBeam NarianResearchBeam Example 3 Adding static fields with MLC Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 14 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans A Dynamic Beam Below is a dynamic beam example This beam is similar to a RapidArc type Beam except that it also rotates the collimator during irradiation The gantry makes a full clockwise revoluti
15. 025 0 525 0 326 000000 0000000000000 90 0 A Mlc Cp Cp Mu 110 Mu Cp cp 5 deliver remaining 106 8 MU Cp cp 6 No MU just move to next field and ready MLC for square MV image gt GantryRtn 90 00 GantryRtn Y155 00 Y1 Y255 00 Y2 X1 6 00 X1 X2 6 00 X2 Mlc lt ID gt 1 lt ID gt lt B0000000000000000000 80 8 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 0000000000 0020000000020 8 90 B 4 0000000000000000000 0 0 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 0000000000 0000000000000 0 A Mlc Cp cp x Drive MLC and jaws to 2nd field shape Cp Cp lt cp 7 Use dummy cp to index KV image gt Cp Cp lt cp 8 Use dummy cp to index MV image gt Cp Mu 113 2 Mu Cp lt cp 9 Deliver 3 2 MU to square field to take MV image gt Cp lt cp 10 Drive MLC and jaws to field shape gt lt Y 1 gt 5 31 lt Y1 gt lt Y2 gt 4 81 lt Y2 gt lt X1 gt 7 18 lt X1 gt lt X2 gt 7 18 lt X2 gt Mlc lt ID gt 1 lt ID gt B50900000000000000000 0 0 O 1 775 2 375 2 075 2 075 0 125 0 325 0 225 0 175 1 275 1 475 0 825 1 425 2 325 2 425 2 225 1 525 0 525 0000000 0000000090900590090909090 B A 00000000000000000000 0 1 826 2 426 2 126 2 126 0 025 0 825 1 225 1 525 1 625 2 625 2 825 2 625 2 02
16. 100 00 CouchLng CouchRtn 180 0 CouchRtn Y155 00 Y1 Y255 00 Y2 X1 6 00 X1 X2 6 00 X2 Mic lt ID gt 1 lt ID gt B5090000000000000000000 0 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 0000000000 0020000000020 8 0 0 O B 4 0000000000000000000 0 0 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 000 5 0000000000 0000000000090 8 0 lt A gt Mlc Cp lt Cp gt lt Cp gt lt cp 1 Use dummy cp to index KV image gt lt Cp gt lt Cp gt lt cp 2 Use dummy cp to index MV image gt Cp Mu 3 2 Mu Cp l cp 3 Deliver 3 2 MU to square field to take MV image gt Cp lt cp 4 Drive MLC and jaws to field shape gt lt Y 1 gt 5 31 lt Y1 gt lt Y2 gt 4 81 lt Y2 gt lt X1 gt 7 18 lt X1 gt lt X2 gt 7 18 lt X2 gt Mlc lt ID gt 1 lt ID gt B5090000000000000000000 0 0 675 0 875 1 575 1 125 1 725 2 225 2 725 3 225 3 425 1 025 3 325 2 925 0 425 1 825 1 425 0 075 0 27000 0000 0000000000090 lt B gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 29 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt A0000000000000000000 0 O 0 726 0 926 1 626 0 175 0 475 0 475 0 075 0 525 0 625 0 325 1 025 1 825 2 025 1 625 1
17. AcquisitionParameters gt ImageMode id Highres gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt NV gt lt AcquisitionParameters gt lt Acquisition gt lt ImagingPoint gt MEC Take KV image 2nd field lt ImagingPoint gt lt Cp gt 7 lt Cp gt lt Acquisition gt lt AcquisitionId gt 3 lt AcquisitionId gt lt AcquisitionSpecs gt lt Handshake gt true lt Handshake gt lt KV gt true lt KV gt lt AcquisitionSpecs gt lt AcquisitionParameters gt lt ImageMode id HighQuality gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt lt KV gt KiloVolts 80 KiloVolts MilliAmperes 50 MilliAmperes MilliSeconds 10 MilliSeconds eFluoroLevelControl None eFluoroLevelControl lt KV gt lt AcquisitionParameters gt lt Acquisition gt lt ImagingPoint gt 1 Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 31 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Take MV image 2nd field gt lt ImagingPoint gt lt Cp gt 8 lt Cp gt lt Acquisition gt lt AcquisitionId gt 4 lt AcquisitionId gt AcquisitionSpecs Handshake true Handshake AcquisitionSpecs lt AcquisitionParameters gt ImageMode id Highres gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt
18. DF fae Gantry 17 014 E mo E MU 145 00 Gantry 9 375 H Control Point i 1 MU 200 Actual trajecto 22m E joctory Gantry 30 a mae h MU 130 00 A Control Point i Gantry 3 750 MU 120 Gantry 0 0 MU Fig 3 Trajectory and Linear Segment between Control Points The figure shows segment i defined by control points j and i 1 Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 5 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans By convention beam delivery between control points is always specified in terms of cumulative MU So in the figure segment i happens to define the arc like portion of a beam During this arc segment the gantry moves 30 from position 0 to position 30 while 80 MU 200 MU 120 MU are delivered The implied linearity means that the control system will control MU delivery and gantry angle so that the relationship between MU and gantry angle remains linear within any one segment So in the above example when cumulative MU reaches 130 MU the gantry will be at 3 750 when the MU reaches 145 MU the gantry angle will be at 9 375 etc Notice that since the position of every mechanical axis is tied to MU the relative position of axes with respect to each other is also precisely fixed during beam delivery In other words during beam delivery motions fol
19. FK FK FK FK FK K FK FK FK oko FK FK FK FK K K K K K FK FK FK 2K 2K 2K 2K 2K 2K KK K K K K K Kk KKK os lt Energy gt 6x lt Energy gt lt Mu gt 0 lt Mu gt lt DRate gt 300 lt DRate gt lt Cp gt lt Cp gt lt ControlPoints gt lt ImagingParameters gt RR RR RR KK K K K K K K K K K K KK K K K K K FK K AK K K OO 2K AK K OK 2K 2K OK FK FK KOK OK K OK KOK Here is where we specify that outside treatment mode K k k 2 E 2 E 2 Ek k k k k k K REE EEE EREE E kk k k k k KEk k k K k k k k k kk k k K k k k k kk k k KOK KOK cos lt OutsideTreatment gt lt RRR RR KK k K KO OK KK K K K K K K KK K K K K K OK OK KOK 2K K K This is just a limit of max MU to be delivered Actual MU delivered will be just what is enough to take the MV image we are requesting K 2K ee K FK FK FK K K K K FK FK FK FK FK 2 FK K K FK FK FK K K K K K FK K FK FK K K K K K 2 FK 2K 2K 2 K K FK FK FK FK FK OK K K K K K K KK KKK y lt MaxMu gt 100 lt MaxMu gt lt OutsideTreatment gt lt ImagingPoints gt lt ImagingPoint gt Cp 0 Cp Acquisition AcquisitionId 1 AcquisitionId AcquisitionSpecs lt AcquisitionParameters gt lt ImageMode id Highres gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt lt MV gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 40 Reminder Developer Mode is intended for non clinical use only an
20. K K K K K K KKK os lt GatingParameters gt lt Filter gt BreathingPhase lt Filter gt QualityThreshold 0 0 QualityThreshold lt RR ER KK K k K K K KK KK KK KK KOK FK FK OK OK OK KOK KKK Setting KV gating to true here makes the KV obey the gate SEEK 2K 2K K K FK K K K K K K FK FK FK FK FK FK FK FK K FK 2 FK K K K K K K K K K K K K K OK KKK 2o lt KVGating gt true lt KVGating gt lt GatingWindow gt lt Entry gt 125 lt Entry gt lt Exit gt 230 lt Exit gt lt GatingWindow gt lt GatingParameters gt lt ImagingParameters gt RRR k kk k k k k KKK KK KK KK OK k k k k k OK EK KOK KOK KOK OK KKK The beam hold device must also be listed here in the beam hold device area Beam hold device with id 4 is TrueBeam s stnadard respiratory gate Establishing a gating device here makes the MV beam obey the gate PEE eK FKK 2 K FK A FK FK K 2 2K 2 K AK FK FK FK KOK K K OK KK KOK KKK cos lt BeamHoldDevices gt lt Dev Id 4 gt lt BeamHoldDevices gt lt SetBeam gt lt VarianResearchBeam gt Example 12 Gating the MV beam Both the kV and MV beams can be gated in the same beam however the gating parameters gating window and gating thresholds are common to both beams Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 47 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans
21. Mode User s Manual Draft Not for Further Distribution April 2011 21 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans arc is maintained at all times In other words in this example MU vs position linearity in the arc segment is maintained at all times regardless of any imaging related temporary slowdowns lt VarianResearchBeam SchemaVersion 1 0 gt lt E k k RK K K K k K K KE A K K K K K FK FK FK K K K K K K K FK FK FK FK K K K K FK K 2K K 2K K K K KK OK OK 2K 2K K 2K K K K K OK ROKK cos lt Arc Beam delivers 180 MU over 200 degree angle 5 arc regions at different MU deg MV images taken at 10 MU and 172 79 MU KV images taken at 20 MU and 120 MU gt lt E k k k RK K k K K K K K K K K K K K K K K K K FK K K K K FK FK FK FK FK K K K K K FK FK FK K FK K K FK K FK 2K 2K K K K K K OK OK OK OK KOK OK K K K OK Kk kk cos lt SetBeam gt lt Id gt 1 lt Id gt lt MLCMode1 gt NDS12 HD lt MLCModel gt lt Accs gt lt Accs gt lt ControlPoints gt Cp control point zero gt lt SubBeam gt lt Seq gt lt Seq gt lt Name gt Arc N Image lt Name gt lt SubBeam gt Energy 6x Energy Mu 0 Mu DRate 300 DRate GantryRtn 0 00 GantryRtn Cp lt Control points 1 2 3 4 5 follow gt Cp Mu 40 Mu GantryRtn 40 00 GantryRtn Cp 40 deg 01 MU deg gt Cp Mu 100 Mu GantryRt
22. OK OK OK OK OK OK OK K Type for imaging during treatment Images may be acquired during treatment If the beam is paused while XI is in an acquiring state the current image s will be dropped and the treatment beam can be resumed under SPV control at the control point where it was paused If the system is equipped for imaging but no images have to be acquired for a treatment beam this type is used at well In this case imaging points shall contain the initial arm positions but no acquisitions 2 KK K FK FK FK FKK K FK K K FK FK FK K K K K K K FK FK FK A K K K FK 2 2K 2K K K K FK FK FK FK FK K K 2 AK FK FK FK FK 2K K K K K K K K K K K K K kK KKK gt lt xs element name DuringTreatment gt lt xs complexType gt lt xs Sequence gt lt xs sequence gt xs complexType xs element lt RRR KR KK K K K K EK koe oko K K FK K K FK K oe FK FK FK ok eoe eoo FK FK FK K K K K K FK FK K K K K K K K OK KOK KOK KOK OK KOK Type for imaging outside treatment Supervisor shall terminate the beam as soon as one of the following condition is fulfilled 1 All acquisitions are completed normal termination 2 The maximum MU limit MaxMu is reached 3 The operator stops the beam 4 A fault occurs Supervisor beam state never changes to paused The reason of termination can be determined from the supervisor beam history Note The corresponding beam has the following characteristics 1 There may be no MV energy defined e
23. The imaging arms do not move between control points Then When the beam reaches a control point where new arm positions are specified in general a fractional control point then any beam and motion on the other axes stop Then The imaging arms are moved to their new positions Once the imaging arms have reached their new positions then Any beam and motion on the other axes resumes Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 32 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans The following figure illustrates how imaging arms move relative to beam and other non imaging arm axis motions Non Arm axis position e g Collimator Rotation Position __s _ MU delivery and other motions stop Arm position while arms move MU W Control Points i and i 1 Control Point i 2 Control Point i 3 at fractional control point Imaging Control Point j i 1 Xxx New arm positions at Fig 4 Imaging Arm motions in MU vs Position space Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 33 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Positions gt Non Arm axis position e g Collimator Rotatio
24. User s Manual Draft Not for Further Distribution April 2011 73 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs element minOccurs 0 maxOccurs unbounded name ImageDestination type xs string lt xs element minOccurs 0 maxOccurs unbounded lt xs element minOccurs 0 maxOccurs 1 lt xs complexType gt lt xs Sequence gt name Movie gt name NotificationDestination type xs string gt lt xs element minOccurs 0 maxOccurs 1 name Destination type xs string gt name Parameters lt xs element minOccurs 0 lt xs complexType gt lt xs Sequence gt lt xs element minOccurs 0 lt xs element minOccurs 0 lt xs element minOccurs 0 lt xs element minOccurs 0 lt xs element minOccurs 0 lt xs element minOccurs 0 lt xs element minOccurs 0 lt xs element minOccurs 0 lt xs element minOccurs 0 lt xS Sequence gt xs complexType maxOccursz 1 maxOccurs 1 maxOccurs 1 maxOccurs 1 maxOccurs 1 maxOccurs 1 maxOccurs 1 maxOccurs 1 maxOccurs 1 maxOccurs 1 lt xs element gt lt END OF Movie Parameters gt xs sequence xs complexType xs element END OF Movie gt lt xs element minOccurs 0 maxOccurs 1 lt xs element minOccurs maxOccurs 1 name Cache type xs boolean name cutOff type xs int name
25. and use the Treatment Mode to convert a DICOM file into an XML Beam Note Converting Clinical DICOM fields into XML Beams and studying these system generated XML beams is perhaps an important step in learning how to compose XML Beams The system generated XML beams can then also be used as a starting point further edited and modified to create new custom XML Beams The following is a description of how to use Clinical Mode to convert a DICOM field or sequence of fields into an XML Beam To perform the DICOM to Beam XML conversion pick the field that you would like to convert and load it into the control system by pressing the PREPARE button on the Control Console If you would like to convert an entire sequence of fields which are part of the same plan use the normal field automation feature of TrueBeam if you are unfamiliar with the field automation feature see TrueBeam TrueBeamSTx Instructions for Use manual Once the field is loaded the c vmsos temp TDSTreatment LastSetBeam xml file is written so you can exit Treatment Mode i e it is not necessary to proceed to actually delivering the beam Notice that the LastSetBeam xml file as generated by the machine does not contain line breaks so it is difficult to read and edit Line breaks can be added by simply opening the file with a program such as Microsoft XML Notepad and then saving it again Microsoft XML Notepad can be downloaded as freeware The new file containi
26. default specifications for the imaging mode specified will be used therefore the element is left empty The ImageMode id Highres element specifies the image mode In this case High Resolution also referred to as High Quality There are other MV imaging modes available such as Continuous Dosimetry Triggered and Lowres also referred to as Low Dose These modes correspond to those available in the Treatment and Service Modes The Treatment imaging modes are also described in the TrueBeam Technical Reference Guide Volume 2 Imaging document See also the section Imaging Modes below CalibrationSet DefaultCalibrationSetld CalibrationSet signifies that the default calibration set will be used for this image acquisition The first kV image The first kV image is taken half way into the first segment as implied by the lt Cp gt 0 5 lt Cp gt element That computes to the point when the MU counter reaches 20 MU The lt Handshake gt true lt Handshake gt element allows the image exposure and image reading to be synchronized with MV beam delivery While it is possible to take images where MV radiation and image acquisition either kV or MV are not synchronized it is generally recommended that this parameter be set to true The lt KV gt true lt KV gt element signifies that this is a kV image ImageMode id HighQuality is the kV imaging mode In this case High Quality There are other kV imaging modes a
27. g kV imaging or dark field Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 65 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans acquisition MaxMu shall be 0 in this case 2 The meterset values in the control points have no semantics 3 There may be 2 successive control points with no changes in any value FK K 2 2 FK FK K K K K K K FK FK FK FK FK K K K FK 2 FK FK FK FK FK K K K FK FK FK K K K K K K K FK FK FK K 2K 2K K K K FK FK OK 2K KK K K K K KOK KKK cos lt xs element name OutsideTreatment gt lt xs complexType gt lt xs sequence gt lt xs element minOccurs 1 maxOccurs 1 name MaxMu type xs double gt lt xs sequence gt lt xs complexType gt lt xs element gt xs choice lt END OF either During or Outside Irradiation imaging gt lt RR RRR k k RK K K KK K K K AK AK K K K FK K K K K K K K K KO K K K K K FK FK FK FK FK K K K K FK 2K 2K AK K K K OK KK 2K OK 2K 2K OK K K KOK Specify Custom Target Permission true false FKK K FK K K 2 K FK FK FK FK FK FK FK FK K FK K K K K FK FK FK oko K K K 2 FK FK K FKK K K K K FK 2 FK K 2 K 2 K FK FK K FK K K K K K K K K K K K KKK os name CustomTargetPermission type xs boolean default false gt lt xs element minOccurs 0 maxOccurs 1 lt RRR RK RK K K KK A K K k K K K K K K K K K K FK FK FK FK FK
28. gt lt Lng gt lt Lng gt lt Vrt gt 70 lt Vrt gt lt Pitch gt lt Pitch gt lt Positions gt lt Kvd gt lt Kvs gt lt Positions gt lt Lat gt lt Lat gt lt Lng gt lt Lng gt lt Vrt gt 98 lt Vrt gt lt Pitch gt lt Pitch gt lt Positions gt lt Kvs gt lt ImagingPoint gt 1 Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 35 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Start the KV fluoro acquisition at 40 degrees lt ImagingPoint gt lt Cp gt 1 lt Cp gt lt AcquisitionStart gt lt AcquisitionId gt 1 lt AcquisitionId gt AcquisitionSpecs Handshake true Handshake AcquisitionSpecs lt AcquisitionParameters gt ImageMode id DynamicGainFluoro lt CalibrationSet gt IMG CBCT lt CalibrationSet gt lt ImageDestination gt ImageDestination lt ImageDestination gt lt KV gt lt KiloVolts gt 100 lt KiloVolts gt lt MilliAmperes gt 20 lt MilliAmperes gt MilliSeconds 20 MilliSeconds eFocalSpot Large eFocalSpot eFluoroLevelControl None eFluoroLevelControl lt KV gt lt AcquisitionParameters gt lt AcquisitionStart gt lt KvFilters gt lt Foil gt 1 lt Foil gt lt Shape gt 1 lt Shape gt lt KvFilters gt lt KvBlades gt lt Positions gt lt KVX1 gt 13 3 lt KVX1 gt lt KVX2 gt 13 3 lt KVX2 gt lt KVY1 gt 10 0 lt
29. have an xml extension XML is a widely used standard to transfer information between computers XML is text so it is easily read and manipulated using a text editor XML does not do anything by itself and imposes only a few simple syntax rules XML is simply a way to transfer information packets called elements in XML parlance Typically these information packets elements are organized into a hierarchical tree structure however no particular tree structure is imposed by XML itself It is essentially up to the entities that exchange information using the XML standard to define and agree upon the particular tree structure s that will be used and the meaning of the information contained in the elements Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 6 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans More easy to read general information on XML is provided at http www w3schools com xml The site provides simple tutorials about XML Note This site is not controlled or endorsed by Varian in any way Similar sites can also be found through a simple web search The Varian TrueBeam XML Schema For the specific case of the TrueBeam machine the specific XML information tree accepted by the TrueBeam control system is defined in the so called Varian TrueBeam XML Schema or simply TrueBeam Schema The TrueBeam schema
30. is NOT cleared for use on humans Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 1 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Support Questions about True Beam Developer Mode can be sent to TrueBeamDeveloper Varian com Operational Overview In summary the typical workflow in using Developer Mode consists of a Using an editor to create XML documents conforming to the Varian TrueBeam XML Schema b transferring the XML script files to the accelerator s control system c loading and running the XML script files through Developer Mode The following figure shows the basic steps involved 4 BEAM ON 1 Use a text editor typically on an auxiliary computer to create an XML Beam script 2 Transfer the XML Beam tothe TrueBeam control console computer typically via network 3 Load XML plan on TrueBeam Developer Mode Fig 1 Elementary workflow of developing and delivering an XML beam There are many methods of transferring the XML Beam file to the TrueBeam control console computer However transferring copying the file via network is recommended Other methods such as memory sticks CDs and other digital media are more prone to infection with viruses and other malware On TrueBeam accelerators the I drive is typically configured as a network drive and can
31. lt Pitch gt lt Pitch gt lt Positions gt lt Kvs gt lt ImagingPoint gt lt RR RK k k K k K K K KK OK K K K K K OK OK OK OK OK K K KKK Stop the continuous image acquisition 2 2K ee 2 K K K K K K K FK 2 FK FK FK FK K K FK 2 FK K K K K K K K K K K K K K BOK KK K 2o lt ImagingPoint gt lt Cp gt 1 lt Cp gt lt AcquisitionStop gt lt AcquisitionId gt 1 lt AcquisitionId gt lt AcquisitionSpecs gt lt AcquisitionStop gt lt ImagingPoint gt lt ImagingPoints gt lt ImagingTolerances gt Ha RR RR RK KK k k EK OK KK KK OK k k EK EK EK OK KOK KOK KOK OK EK Here are the gating parameters 2 k ak ak ak 2 2 k 3k k Fk FK A Eg oe k k 2 kkk k k k k k k k OK OK OK KK KOK ROKK os lt GatingParameters gt lt Filter gt BreathingPhase lt Filter gt QualityThreshold 0 0 QualityThreshold lt mR RE RK k k KK k k oe eoo eo OK EK OK KKK K K KOK OK OK OK KOK KKK Setting KV gating to true here makes the KV obey the gate FKK FK K FKK oe Fk FK FK FK FK K K K K K FK FK FK K K K 2 KK 2K 2K K KK OK K K KKK OK oos lt KVGating gt true lt KVGating gt lt GatingWindow gt lt Entry gt 125 lt Entry gt lt Close gate starting at 125 degrees gt Exit 230 Exit Open gate starting at 230 degrees gt GatingWindow GatingParameters lt ImagingParameters gt lt RRR RR KK K k k K K K K K K K KK K K FK FK K K OK KOK K OK OK K K The beam hold device must also be listed here in
32. lt Seq gt lt Seq gt lt Name gt Beam ON lt Name gt lt SubBeam gt lt Energy gt 6x lt Energy gt lt Mu gt lt Mu gt DRate 520 DRate GantryRtn 360 00 GantryRtn CollRtn 177 05 CollRtn CouchVrt 90 0 CouchVrt CouchLat 100 00 CouchLat CouchLng 100 00 CouchLng CouchRtn 180 0 CouchRtn lt Y 1 gt 5 31 lt Y1 gt lt Y2 gt 4 81 lt Y2 gt lt X1 gt 7 18 lt X1 gt lt X2 gt 7 18 lt X2 gt Mlc ID 1 ID lt B0000000000000000000080 0 550 0 875 1 465 1 125 1 835 2 125 2 555 3 625 3 775 1 225 4 325 2 925 1 325 1 725 1 525 0 175 0 27 0000000000000 0 0 0 O0 O0 8020 O B A 0000000000000000000 0 0 0 726 0 926 1 626 0 175 0 575 0 495 0 175 0 725 0 825 0 465 1 025 1 825 2 025 1 625 1 025 0 525 0 32060000000000000000 0 0 O A Example 5 Specifying Dose Rate and Velocity Limits As mentioned the limit will ensure that gantry speed will not exceed 2 5 degrees per second However the actual instantaneous gantry speed chosen by the control system may be lower for those segments of the RapidArc which may involve delivery of large number of MU large MLC leaf movements or in this case a lot of collimator rotation Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 18 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans The velocity limit is gl
33. or segment velocity Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 19 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans of the other axes necessary to maintain the user specified MU vs position trajectory as specified in the XML Beam file while still respecting any user imposed dose rate or velocity limits Generally the limiting rate can vary from segment to segment So for example it may turn out that a segment where the limiting rate is gantry velocity may be followed by a segment where the limiting rate is dose rate or the maximum velocity of another mechanical axis eg one of the MLC leaves The control system also contains algorithms to more precisely control the finite accelerations of various mechanical axes Since the accelerator s mechanical parts have mass and associated inertia it is generally not possible to instantaneously change their speed at segment transitions i e at control points The control system employees various more sophisticated algorithms to handle these segment transitions so that the user specified MU vs position trajectory as specified in the XML beams is followed at all times including segment transitions The total wall clock time to deliver a beam is simply the sum of the times required to deliver every segment However note that the time counter shown on the Developer
34. selection window will appear Navigate to the folder containing the XML Beam you want to deliver and select Open The XML Beam is now read into the TrueBeam control system If the XML Beam is found to be invalid an error will be displayed at this point Press the PREPARE button on the TrueBeam Control Console to prepare the beam for delivery It is typically convenient to push the Axis Positions button at this point to facilitate positioning the axes to their starting positions as specified in the XML Beam The initial positions required by the plan will appear in the Program columns of the interface Pressing Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 48 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Go To causes the initial axes positions from the XML Plan to become Target Positions Target positions can now be activated in groups Gantry amp Collimator group Couch Linear group and Couch Rotation group and motion can be initiated using either the TrueBeam control console or the in room pendants The process is similar to activating Target Positions and moving axes in Treatment and Service Modes Note and Workaround if your XML Beam requires either kV imaging foils and or kV imaging filters or if the XML Beam requires specific positions for the kV collimators then you must use th
35. specifies the valid syntax and acceptable information content of XML Beam files Studying the TrueBeam schema is a way to learn about all the capabilities of Developer Mode Schema is yet another generic XML standard a standard language used to describe schemas It is also written in XML but its elements contain specific keywords used to describe the structure of XML trees such as elements and syntax details about which child elements are mandatory which are optional the valid data types for an element etc A tutorial on XML schemas can be found at http www w3schools com schema default asp Becoming familiar with the Varian XML Beam Schema is an essential part of doing research with Developer Mode The Varian XML Beam Schema is described in the file SetBeam xsd The xsd extension is typical of XML schema files The SetBeam xsd file is included in Appendix A SetBeam xsd can be used as a reference to the XML language accepted by TrueBeam Varian also provides an electronic copy of SetBeam xsd Upon examination of the Varian XML Beam schema one sees that many of the elements in an XML Beam are optional so the tree structure of XML beams can vary significantly from beam to beam Simple fixed beams can be described as simple trees of just a few elements while in general dynamic beams with more control points require more elements Also beams that take images are typically described by trees of greater depth since in general the informat
36. to their resumption position by the time the gate closes again e g axis overshoot during a very short gate then beam remains suspended until all the overshooting axes return to their resumption positions Following is an example of a gated MV beam The example is an arc with 5 different zones of MU degree densities kV images are being continuously taken in the 40 to 90 degree region of the arc The MV beam gantry rotation and kV imaging are all gated lt VarianResearchBeam SchemaVersion 1 0 gt lt RRR KK RK K K K K KR K AK KO FK FK K K OK K K FK FK FK FK K K K OK 2K 2K OK K K KK FK OK OK KOK K K K K K OK KKK KE oos lt Arc Beam delivers 180 MU over 200 degree angle to 200 deg 5 arc regions at different MU deg Continuous KV images are taken in the 40 to 90 degree region of the arc However both the MV beam as well as the imaging KV beam are gated gt lt E k k k k k kk kk k K K k K K K K AK AK K K K K K K K K K K K k K FK FK FK K K K K K K FK FK FK FK K K K K K 2K 2K 2K 2K AK K K KK OK OK OK OK OK K K K K K K K KK KK gt lt SetBeam gt lt Id gt 1 lt Id gt lt MLCModel gt NDS120HD lt MLCModel gt lt Accs gt lt Accs gt lt ControlPoints gt Cp lt control point 0 zero gt SubBeam Seq 0 Seq Name Arc N Image lt Name gt lt SubBeam gt Energy 6x Energy Mu 0 Mu DRate 600 DRate GantryRtn 0 00 GantryRtn Cp Cp Mu 40 Mu GantryRtn 40 00 Ga
37. weight type xs double lt xs element minOccurs 0 maxOccurs 1 name HistogramRoi gt lt xs complexType gt lt xs sequence gt lt xs element minOccurs 1 maxOccurs 1 name X1 type xs int lt xs element minOccurs 1 maxOccurs 1 name Y1 type xs int lt xs element minOccurs 1 maxOccurs 1 name X2 type xs int lt xs element minOccurs 1 maxOccurs 1 name Y2 type xs int lt xs sequence gt lt xs complexType gt lt xs element gt lt END OF HistogramRoi gt lt RR RK K K K K K K K K K K K K K K K K K K K K K K K FK 2K FK FK K K K K K OK K K K OK KOK KOK KOK KOK Specify either kV or MV parameters 2 KK K FK 2 FKK K K FK FK FK FK FK K K K K K FK FK 2 FK 2K K K K K FK FK FK FK 2 K K FK FK FK FK FK FK FK 2K 2K 2K 2K K K K K K K KK KKK o lt xs choice minOccurs 1 maxOccurs 1 gt lt a RR RR KK K K K K K A K K K K K K K K K K K K K K K K FK FK FK K K K K 2 2K OK KK K K OK KOK OK KOK KOK MV parameters are just energy and dose rate ee 2 K K K K K K K K FK FK FK ok eoe K K K 2 K AK K K K FK FK FK FK FK 2K 2K K 2K FK 2K OK OK K K K K K KOK KKK gt lt xs element name MV gt name width type xs int gt name height type xs int gt name frameRate type xs double name crop type xs boolean name invert type xs boolean name pixelValue type xs int name pixelValue255 type xs int name RaiseFault type xs boolean gt gt gt gt gt
38. whether to track this beam and the tracking parameters optional Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 58 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Define the tracking enable status plus the tracking capability ratio Tracking capability ratio range between and 1 0 with 1 0 means tracking trajectory would be generated with full capabilities of axes gt lt RR K kK K K K K K K K K K K K K K K K K K A 2 K K K K K FK FK FK FK FK K K K K 2 2 2K K K K K 2 2K 2 KK FK FK 2K OK K OK OK K K K KOK ROKK oos lt xs element name Tracking minOccurs 0 maxOccurs 1 gt lt xs complexType gt lt xs Sequence gt lt units are 1 deg sec or 1 cm sec gt lt xs element name TrackingEnabled type xs boolean minOccurs 1 maxOccurs 1 gt lt RRR RK k KK K K K k K K A K K K K K FK OK OK K K K K K OOK KO 2K OK 2K 2K OK K K OK OK Capability ratio is restricted to be between 0 0 and 1 0 SK K K K K K K A K FK FK FK 2 oe K FK K FK K oe oe FK FK FK FK oko FK FK FK FK FK AK K K K K FK 2 FK K 2 K K K K KK FK K K KK K K K K K K KKK cos lt xs element name CapabilityRatio minOccurs 1 maxOccurs 1 gt lt xs simpleType gt xs restriction base xs double gt lt xs minInclusive value 0 xs maxInclusive value 1 gt lt xs restriction gt lt xs simpleType gt lt xs e
39. xs simpleType name KvFilterType gt xs restriction base xs integer gt xs minInclusive value 0 gt xs maxInclusive value 2 xs restriction xs simpleType lt RRR k k k K KK KK K k K K K K K K K K K K K FK K K K K K FK oe A poke K FK A K K 2 2K 2 eoe EE K K K FK FK FK K FK K K K K FK FK 2 FK OK K K K OK K K K Type Element Definition for Arm positions FKK 2K 2K 2K 2K 2K 2K FK K K K K K K FK FK FK FK FK FK FK FK K FK FK FK FK FK FK FK K K FK K FK FK K 2K K K K K K K 2 2K 2K K K K FK 2 FK K K K FK FK FK FK FK FK FK FK AK 2K a FK K FK K K K K K K KK OK OK OK cos lt xs complexType name ArmPositionsType gt lt xs choice gt lt RR ER k k k k KK K K K K K K K K K K K AK K K FK FK K K K K K K OK FK FK FK K K AK AK K FK FK FK K K K K K K 2 2K 2K 2K K K K K K FK K K FK FK K KOK KOK K K K KOK Predefined positions for PU Position Type retracted arm is in a pre defined fully retracted position extended arm is either in a pre defined extended position or in a pre defined clinical area the VRT and LNG coordinates are within a pre defined polygon where the image can be taken according to the treatment plan mid arm is in a pre defined Mid position between retracted and extended none all other positions When used in setTarget means cancel target FKK K K KK K K K FK FK FK FK FK K K K K K K K FK K K 2K 2K 2 FK FK FK FK K K K AK K FK FK FK 2 K K K K KK FK FK AK AK K K K K K FK K 2K 2K 2K K K K 2 FK FK 2
40. 000000 0 0 0 726 0 895 1 626 0 175 0 466 0 475 0 075 0 525 0 625 0 325 1 025 1 825 2 025 1 625 1 025 0 525 0 326000000000000000 0 0 0 O0 80 O A lt Mlc gt lt Cp gt lt Cp gt Mu 6 09 Mu lt Deliver 6 09 2 13 MU gt GantryRtn 355 07 GantryRtn M1c lt ID gt 1 lt ID gt lt B0000000000000000000080 0 674 0 8 1 575 1 125 1 725 2 225 2 625 3 125 3 325 1 425 3 225 2 925 818 1 825 0 925 0 175 0 172000000000000000 0 0 O 0 O0 O B A 000000000000000000000 0 725 0 851 1 626 0 175 0 375 0 075 0 075 0 525 0 725 0 475 1 125 1 025 2 025 1 525 1 025 0 525 0 225 00000000000 0 0 0 0 0 O0 O 0 O O A Mlc Cp Several more control points here Cp Mu 590 88 Mu GantryRtn 0 00 GantryRtn completed 360 gantry revolution gt Mlc ID 1 ID lt B0000000000000000000080 1 275 1 475 1 375 0 825 2 975 4 074 724 274 3 125 3 425 3 525 3 425 3 125 1 375 0 482 1 425 0 325 0 775 0000000000000000 0 0 O B A 000 00000000000000000 0 1 326 1 526 1 426 1 918 3 125 4 125225 246m6 2 875 1 975 2 275 2 275 2 225 1 525 1 025 0 325 0 82200000000000000000 090 0 0 0 lt A gt Mlc Cp ControlPoints SetBeam NarianResearchBeam Example 4 A dynamic beam with simultaneous MU delivery and motions Note on imaging arms motions An XML Beam can also specify motions for the three imaging arms MV imager kV Imager and kV Sour
41. 1 name ImagingPoints gt Example Beam group with 3 beams First beam has 5 control points 0 amp 8804 Cp amp 8804 4 Second beam has 2 control points 5 amp 8804 Cp amp 8804 6 Third beam has 3 control points 7 amp 8804 Cp amp 8804 9 FK KK K FK 2 2 K K 2 FK FK FK K K K K K FK FK FK FK 2K K 2K K K FK 2 FK FK 2 AK K 2 FK FK FK FK FK FK K K K K FK FK KK K K K K K OK OK K K K K KKK cos lt xs element minOccurs 1 maxOccurs unbounded name ImagingPoint gt lt xs complexType gt lt xs sequence gt lt RR RK kk K K K K K K KK FK K K K FK FK FK FK KK OK K K K K KK OK KOK KKK The fractional control point This refers to the list of beam control points in element ControlPoints above This factional control point is essentially what determines where in the beam the image will be taken In other words this fractional control point i what corelates the Imaging and beam control points FKK K K ee 2 FK FK FK K K K K 2 2K 2 FK K K K K K K K K FK FK 2K 2K K FK FK FK FK 2 FK FK FK K K FK FK FK FK FK FK FK K K K K K K K K KKK co lt xs element minOccurs 1 maxOccurs 1 name Cp type xs double gt 4 HR ER k k k K K K K K K K K k k K K K K K K K K K K FK K K K K oe FK FK K K K K FK FK K 2K K K K K K KK OK KOK OK K K OK K Acquisitions at this imaging point You can either do a simple Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 20
42. 11 67 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans acquisition or start stop a continuous acquisition at any imaging control point A K K K K 2K FK FK FK K K K K K K 2K FK 2 2 K K K K K K FK FK FK FK a FK FK FK 2 FK FK FK K FK 2 KK FK K K K K K K K OK BOK cos lt xs element minOccurs 0 maxOccurs 8 name Acquisition type Acquisition gt maxOccurs 8 name AcquisitionStart type Acquisition gt lt xs element minOccurs 0 maxOccurs 8 name AcquisitionStop type Acquisition gt lt xs element minOccurs 0 4 RR ER k k k K K K K K K k k k k K K K K K K K K K K K K FK FK FK FK K K FK K K K K FK FK FK FK FK K K K K K K FK FK KOK FK OK K KOK kV filter settings optional at this imaging point A K FK K 2 FK FK FK K K K K K K 2 FK 2 K K K K 2K K FK FK FK K 2 FK FK FK FK FK FK FK a K 2 KK FK K K K K K K K OK OK cos lt xs element minOccurs 0 name KvFilters xs complexType lt xs all gt lt xs element name Shape type KvFilterType minOccurs 0 maxOccurs 1 gt lt xs element name Foil type KvFilterType minOccurs 0 maxOccurs 1 gt maxOccurs 1 lt xs all gt lt xs complexType gt lt xs element gt lt HR RR KB k K AK KK K K K FK OK OK 2K OK KOK KOK KKK K desired optional arm kv blade positions before the image acquisition Specify either blade tracking or blade positions FKK K K ee 2 FK FK FK K K K K K K 2K 2 2 FK E
43. 2K K K K K K K K OK KOK K K K K K OK KL y lt xs element name SubBeam minOccurs 0 xs complexType Xs sequence lt xs element name Seq type xs unsignedInt minOccurs 1 maxOccurs 1 gt lt xs element name SubbeamGUID type xs string minOccurs 0 maxOccurs 1 gt lt xs element name Name type xs string minOccurs 0 maxOccurs 1 gt lt xs element name MaxRadTime type xs double minOccurs maxOccurs 1 gt lt xs element name TrackingTrainingOnly type xs boolean minOccurs 0 maxOccurs 1 maxOccurs 1 gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 62 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs sequence gt lt xs complexType gt lt xs element gt lt END SubBeam gt RRR KK KK K K K K K K K A A K K K K K K FK K K K K K K K FK K 2K 2K K K K K K OK 2K 2K K K K OK KOK ROKK cos lt 1 Energy starting at this control point A unique signature for the energy in the form dds where dd 0 99 s x e or h where x MV X Rays e MeV electrons h Mev HDTSe electons k KV beams Examples 6x 6 MV X Rays and 12e 12 Mev electrons and k kv beam gt RR KK K K K K KK KK KE KK OK FK K K K OK FK OK FK K OK KOK KOK KK K K KOK kK KKK oos lt xs element name Energy type xs string minOccurs m
44. 5 1 525 1 025 0 525 0 025000009090 00000000000000 90 O A Mlc Cp Cp Mu 182 Mu Cp cp 11 deliver remaining 68 8 MU for 2nd field gt lt ControlPoints gt 1 gt lt I MAGING S E C T I ON gt 1 gt lt ImagingParameters gt lt DuringTreatment gt lt ImagingPoints gt lt Take KV image 1st field gt lt ImagingPoint gt lt Cp gt 1 lt Cp gt lt Acquisition gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 30 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt AcquisitionId gt 1 lt AcquisitionId gt lt AcquisitionSpecs gt Handshake true Handshake KV true KV lt AcquisitionSpecs gt lt AcquisitionParameters gt lt ImageMode id HighQuality gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt lt KV gt KiloVolts 80 KiloVolts MilliAmperes 50 MilliAmperes MilliSeconds 10 MilliSeconds eFluoroLevelControl None eFluoroLevelControl lt KV gt lt AcquisitionParameters gt lt Acquisition gt lt ImagingPoint gt lt Take MV image 1st field gt lt ImagingPoint gt lt Cp gt 2 lt Cp gt lt Acquisition gt lt AcquisitionId gt 2 lt AcquisitionId gt lt AcquisitionSpecs gt lt Handshake gt true lt Handshake gt lt AcquisitionSpecs gt lt
45. E K K K FK FK FK FK 2 FK FK 2 FK FK FK K K 2K FK FK OK FK K K KK K K OK OK cos lt xs element name KvBlades minOccurs 0 maxOccurs 1 gt lt xs complexType gt lt xs Sequence gt lt xs choice minOccurs 1 maxOccurs 1 gt lt xs element name Tracking type xs boolean gt lt RR RR KK KK FK K K OK OK KK OK OK OK K K OK OK OK OK OK KOK K Positions of the kV Blades units in cm SKK 2K 2K K K Ee K K K K FK FK FK FK FK FK K K FK FK FK FK FK 2 K K K K FK FK 2K 2K 2K 2K K K FK OK K K K KOK ROKK cos lt xs element name Positions gt lt xs complexType gt xs all Must specify all kV collimator positions but unlike MV collimators they can be listed in any order lt xs element minOccurs 1 maxOccurs 1 name KVX1 type DoubleNone gt lt xs element minOccurs 1 maxOccurs 1 name KVX2 type DoubleNone gt lt xs element minOccurs 1 maxOccurs 1 name KVY1 type DoubleNone gt lt xs element minOccurs 1 maxOccurs 1 name KVY2 type DoubleNone gt lt xs all gt xs complexType lt xs element gt lt xs choice gt lt xs sequence gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 68 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs complexType gt lt xs element gt lt xs element minOccurs 0 maxOccurs 1 name Mvd type ArmPosition
46. E kk 2 2 k k KEk k k KK k kk k k OK KK ROK cos MaxMu 0 MaxMu aR k RR eoo A OK EPE gt k 3k k k k k EK KK k KK k k OK OK OK k OK OK OK k Here is where we specify that outside treatment mode 2 k ak ak ak 2 ak 2 EE k gt k k k A kakak k k k k k k k KEE k k k k k K k k OK OK KK k K k k OK KOK KOK KKK kkk Lo lt OutsideTreatment gt lt ImagingPoints gt lt RRR RR k k KK k K k K k K K K KK K K K K K OK KK KK OR OK OK OK OK OK OK KOK KOK K KOK K Start continuous acquisition in DynamicGainFluoro mode a good choice for CBCT FKK FK K FK K K KK FK 2 FK FK FK K K K K FK K FK FK K K K K K FK FK FK FK FK 2K 2K KK FK FK K K K K OK KOK KKK gt lt ImagingPoint gt lt Cp gt 0 lt Cp gt lt AcquisitionStart gt lt AcquisitionId gt 1 lt AcquisitionId gt lt AcquisitionSpecs gt lt Handshake gt true lt Handshake gt lt KV gt true lt KV gt lt AcquisitionSpecs gt lt AcquisitionParameters gt ImageMode id DynamicGainFluoro CalibrationSet IMG CBCT CalibrationSet ImageDestination ImageDestination ImageDestination KV Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 38 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans KiloVolts 100 KiloVolts MilliAmperes 40 MilliAmperes MilliSeconds 10 MilliSeconds eFocalSpot Large eFocalSpot e
47. FK FK 2K 2K 2K K K K FK FK FK FK 2 K K FK 2 FK FK KK OK K K K OK K K K TypeDef for Tolerances of a PU arm Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 76 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans BR 2 K K K K K K FK FK FK FK 2 FK K K FK FK FK FK FK FK FK K K FK K FK FK K 2K K K K K K K FK FK K 2 K K FK FK FK FK 2K K 2 FK FK FK FK FK FK FK 2 K FK 2 K K K K K K K KOK K kK OK ROK cos lt xs complexType name ArmTolerances gt lt XS sequence gt lt units are deg or cm gt lt xs element name Lat type xs double minOccurs 1 maxOccurs 1 gt lt xs element name Lng type xs double minOccurs 1 maxOccurs 1 gt lt xs element name Vrt type xs double minOccurs 1 maxOccurs 1 gt lt xs element name Pitch type xs double minOccurs 1 maxOccurs 1 gt lt xs sequence gt lt xs complexType gt RRR KK K K K K K KK FK FK K K K K K K K FK 2 K K K K FK FK AE 2 2 2 K K K K FK 2 2 K K 2 KK KK OK OOK KOK KOK TypeDef for Acquisition trigger FKK 2K 2K 2K 2K 2K FK FK K K K K 2 K FK FK FK FK FK FK K K K FK FK FK FK FK FK FK K K FK K FK FK AK 2K 2K K K K K FK 2 2K 2K K K K o 2 FK FK AK 2K K FK FK FK 2 FK FK 2K 2K K K K FK FK K K K K K KK OK OK OK cos lt xs complexType name AcquisitionTrigger gt lt xs sequence gt lt xs element minOccurs 0 maxOccurs 1 name Tr
48. FK FK FK FK FK FK 2 KK FK FK OK OK K K OK KKK OK KKK oos maxOccurs 1 gt lt xs element name Accs minOccurs 1 lt xs annotation gt lt xs documentation gt The planned Accessory Codes for each slot lt xs documentation gt xs annotation xs complexType xs sequence lt xs element name Acc1 type xs int minOccurs 0 maxOccurs 1 lt xs element name Acc2 type xs int minOccurs maxOccurs 1 gt lt xs element name Acc3 type xs int minOccurs 0 maxOccurs 1 lt xs element name Acc4 type xs int minOccurs 0 maxOccurs 1 gt lt xs sequence gt xs complexType xs element lt 2 RR RR RK K K AK AK K K K K K K oe eoe oe oe FK FK FK FK K ooo 2 oko 2 K K FK FK K 2K 2K 2K 2 K FK FK 2 2 K K OK KOK OK KK OK KOK K Control points list This is where you define the the dose vs position relationship trajectory in dose position space describing the beam from beginning to end Typically at each control point the amount of dose and motions to be performed are listed BE K 2K 2K K K K K FK K K K K K FK ook eoe A K FK FK K K K K FK K KK FK FK K K K K K K 2 FK FK 2K 2 FK 2 FK FK FK FK 2K AK AK AK FK FK FK FK FK 2K K K K OK K K OK OK KKK oos lt xs element name ControlPoints minOccurs 1 maxOccurs 1 gt xs complexType lt xs sequence gt lt RR RRR RK KK KK EK K KK K FK K OK K FK FK FK FK FK FK K K K FK K K OK K K K K OK KK K K KOK KKK os lt The control points 2 i
49. FluoroLevelControl None eFluoroLevelControl lt KV gt lt AcquisitionParameters gt lt AcquisitionStart gt lt KvFilters gt lt Foil gt 1 lt Foil gt lt Shape gt 1 lt Shape gt lt KvFilters gt lt Kvd gt lt Positions gt lt Lat gt lt Lat gt lt Lng gt lt Lng gt lt Vrt gt 50 lt Vrt gt lt Pitch gt lt Pitch gt lt Positions gt lt Kvd gt lt Kvs gt lt Positions gt lt Lat gt lt Lat gt lt Lng gt lt Lng gt lt Vrt gt 10 lt Vrt gt lt Pitch gt lt Pitch gt lt Positions gt lt Kvs gt lt ImagingPoint gt lt RR RR k k k k K Kk K K K KE OK OK OK K K K K K KK OK OK OK KOK KOK OK Stop the continuous image acquisition Fkk ak k 3k 2 2 2 2g k k 2 2 Fk Fk Fk 2 KEk k KK KK k k k k KKK ROK oo lt ImagingPoint gt lt Cp gt 1 lt Cp gt lt AcquisitionStop gt AcquisitionId 1 AcquisitionId AcquisitionSpecs lt AcquisitionStop gt lt ImagingPoint gt lt ImagingPoints gt lt ImagingTolerances gt lt ImagingParameters gt lt SetBeam gt lt VarianResearchBeam gt Example 10 Taking images only i e imaging only no therapeutic beam One of the main advantages of the lt OutsideTreatment gt mode is that MV images can be acquired without having to explicitly specify the MU required to acquire these images The control system automatically delivers the MV MU necessary to take the images based on the image type In general the MU necessary to take various ima
50. K 2K 2K K K K K KOK KOK KKK 2o lt SetBeam gt lt Id gt 1 lt Id gt MLCModel NDS120HD MLCModel Accs lt ControlPoints gt lt Cp gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 37 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans SubBeam Seq 0 Seq Name CBCT FullFan360 Name SubBeam lt Energy gt k lt Energy gt lt HR RR RK k AK k K k K k KE A OK K K K OK FK OK KOK KOK K K OK K K OK MU and dose rate are 0 since we will be taking KV images only and we are using the outside treatment mode A K K KK K K K k K 2 FK K K K K K K FK FK 2K oe okekeo oe poe FK 2 K FK FK FK FK FK FK KK K K OK KK K OK Kk oos lt Mu gt 0 lt Mu gt lt DRate gt 0 lt DRate gt lt Start the gantry in the overtravel range gt lt GantryRtn gt 364 lt GantryRtn gt lt Cp gt lt Cp gt lt Gantry rotates 368 degrees all the way on the other side of the overtravel range gt lt GantryRtn gt 4 lt GantryRtn gt lt Cp gt lt ControlPoints gt lt Defines the imaging parameter for the beam and each control point gt lt ImagingParameters gt lt OutsideTreatment gt lt RRR RR k k RK A oko oe KK 3k 3k OK K 2k 2K 3k OK OK k k OK KOK 2K No need to set a max MU because we re taking KV images only A ee ak 3k 2 2 2k k 2 3k 3k 3k 2 k K k 2k Ek dk 2 K KE
51. K 2K K 2K 2K 2 K FK K K K K OK K K OK ROK cos lt xs element name SpecialPosition minOccurs 0 maxOccurs 1 gt lt xs simpleType gt xs restriction base xs string xs enumeration value retracted gt lt xs enumeration value mid gt lt xs enumeration value extended gt lt xs enumeration value none gt lt xs restriction gt lt xs simpleType gt lt xs element gt lt RRR RK k K KK 2K 2K K K AK K K K KK K 2K K K FK FK FK FK FK FK 2 K FK FK FK K FK FK FK K K K K FK K K K K K K 2 2 2K 2K 2K K KK KK KK KOK FK OK OK OK OK Axes definitions for a working position of an arm FKK K K KK 2 K K KK FK FK FK K AK K K K FK FK FK FK 2K 2K AK 2 FK FK FK FK FK 2 K K FK FK FK FK FK 2 K 2 FK FK FK AK K K K K K K 2 2K K 2 FK 2 2K FK 2K 2 2K AK 2 FK FK K K K K K K K OK ROK cos lt xs element name Positions minOccurs 0 maxOccurs 1 gt xs complexType lt xs Sequence gt lt units are deg or cm gt lt xs element minOccurs 1 maxOccurs 1 name Lat type xs double gt lt xs element minOccurs 1 maxOccurs 1 name Lng type xs double gt lt xs element minOccurs 1 maxOccurs 1 name Vrt type xs double gt lt xs element minOccurs 1 maxOccurs 1 name Pitch type xs double lt xs sequence gt lt xs complexType gt lt xs element gt xs choice xs complexType RRR E k k k K K K K oe oko K K K K K K K FK ok K oe FK FK K K K oe K FK FK K ok K K FK 2K 2K 2K 2K 2K K K K
52. K FK FK 2K 2K KOK K K K KOK OK KL y lt xs element minOccurs 0 maxOccurs 1 name Mvd type ArmTolerances gt lt xs element minOccurs 0 maxOccurs 1 name Kvd type ArmTolerances gt lt xs element minOccurs 0 maxOccurs 1 name Kvs type ArmTolerances lt HERE RK K K KK K K K K K KK K 2K 2K 2K OK K K K FK FK 2K OK KK OK FK FK OK KOK OK K kV Blade kV collimator tollerances FK KK K K 2 K K K FK FK FK FK FK K K 2K K K K FK FK FK 2K 2K 2K 2K K 2 FK FK FK FK FK K 2 K FK FK FK FK FK FK K K K K K FK K K K K K K K OK OK K K K K KKK gt name ImagingTolerances gt lt xs element minOccurs 0 maxOccurs 1 name KvBlades gt lt xs complexType gt Xs sequence lt units are deg or cm gt lt xs element name KVY1 type xs double minOccurs 1 maxOccurs 1 gt lt xs element name KVY2 type xs double minOccurs 1 maxOccurs 1 gt lt xs element name KVX1 type xs double minOccurs 1 Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 69 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans maxOccurs 1 gt lt xs element name KVX2 type xs double minOccurs 1 maxOccurs 1 gt lt xs sequence gt lt xs complexType gt lt xs element gt lt xs sequence gt lt xs complexType gt lt xs element gt lt END OF ImagingTolerances gt l
53. K FK OK OK FK OK K K OK K K KK K os lt xs complexType name Acquisition gt lt XS sequence gt lt xs element minOccurs 1 maxOccurs 1 name AcquisitionId type xs int gt lt RRR RK k k KK K A KO K K K FK K FK FK FK KK K K A A K K K FK K K K K 2 K FK 2K 2K 2K 2K K KK FK FK 2K 2K K OK KOK FK FK FK OK OK KK Container for any detailed XI acquisition information needed by SPV in setup phase Handshake hand shaking between SPV and XI required If yes SPV will pause delivery until XI is ready for acquisition If not SPV will merely trigger the acquisition in time KV is kv Beam MVDose estimated total amount of MVDose required in order to acquire the image This is used by SPV to calculate radiation time Gating for gated MV radshot FKK K K KK K K K FK FK FK FK FK K K K K K FK FK 2 K K K AK K FK FK FK 2 K K K FK FK FK FK FK FK 2 K K K FK FK FK FK K K K K K K K AK 2K 2K K K K 2 2K 2K 2K 2K 2K 2K K K FK FK K K K K K K KK KK os lt xs element minOccurs 1 maxOccurs 1 name AcquisitionSpecs gt lt xs complexType gt lt xsS Sequence gt lt xs element minOccurs 0 maxOccurs 1 name Handshake type xs boolean lt xs element minOccurs 0 maxOccurs 1 name KV type xs boolean lt xs element minOccurs z 0 maxOccurs 1 name MVDose type xs double lt RR RK K K K K K K K K K K K K K K FK K K K K K K FK FK FK FK FK 2 K K K 2 FK FK K 2 K 2 2K 2K K K K K K FK FK K 2K 2 K K FK FK OK KO 2K 2K OK FK OK FK K K Enumerat
54. K OK K K OK lt Two static MLC fields delivered at two different gantry angles First field delivers 110 MU second field 72 MU lt I mK EK K K K KK OK OK K K K K K K K K OK FK K CE CE OK K K K CE CE K OE K SE CE CE CE CE K FK CE CE CE CE CE CE CE CK CE CE CE K CE CE CE CE CE CE CE K K OK CE OK K E K K OK OK OK K K OK SetBeam Id 1 Id MLCModel NDS120HD MLCModel lt Accs gt lt Accs gt lt ControlPoints gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 13 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt Cp gt lt first control point Set up to initial positions gt lt SubBeam gt lt Seq gt lt Seq gt Name Beam ON Name lt SubBeam gt lt Energy gt 6x lt Energy gt lt Mu gt lt Mu gt DRate 400 DRate GantryRtn 180 00 GantryRtn CollRtn 180 0 CollRtn CouchVrt 90 0 CouchVrt CouchLat 100 00 CouchLat CouchLng 100 00 CouchLng CouchRtn 180 0 CouchRtn Y155 31 Y1 lt Y2 gt 4 81 lt Y2 gt lt X1 gt 7 18 lt X1 gt lt X2 gt 7 18 lt X2 gt lt Mlc gt lt ID gt 1 lt ID gt lt B0000000000000000020280 0 0 0 675 0 875 1 575 1 125 1 725 2 225 2 725 3 225 3 425 1 025 3 325 2 925 0 425 1 825 1 425 0 075 0 275 000000000000000009090909090 B A 0000000000000 0 0 O0 O O O O O 0 726
55. K OK OK KK 2K OK 2K 2K OK K OK OK K Max Velocity Table This table can be used to specify top velocities of axes to be used in the treatment RULES 1 If an individual axis has a specified max velocity value then the Control System will use the smaller of the specified max velocity and the maximum supported max velocity of that axis 3 Ae FK FKK FK 2 K FK FK 2 K AK K K K FK FK FK FK 2K 2K 2K AK K K K K FK A K 2K FK FK FK FK FK FK K K K K K FK FK FK FK FK FK K K K K K K K K K K K K OK OK K K K kK KKK co lt xs element minOccurs 0 maxOccurs 1 name ImagingVelTable gt xs complexType Xs sequence lt List of max velocities desired for each Clinac axis gt lt units are 1 deg sec or 1 cm sec gt lt xs element name GantryRtn type xs double minOccurs 0 maxOccurs 1 lt xs element name CollRtn type xs double minOccurs 0 maxOccurs 1 lt xs element name CouchVrt type xs double minOccurs 0 maxOccurs 1 gt minOccurs e maxOccurs 1 lt xs element name CouchLng type xs double minOccurs 0 maxOccurs 1 lt xs element name CouchRtn type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CouchLat type xs double lt xs element name X1 type xs double minOccursz e maxOccurs 1 gt lt xs element name X2 typez xs double minOccursz e Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribu
56. LC leaves must move at some control point then all the leaves must be included even those that do not move In other words the MLC shape is always listed as a unit and the MLC shape can be omitted from a control point only when the entire MLC shape remains the same i e none of the leaves move between the control points Note While it is redundant to re list across control points the same position for an axis that does not move doing so does not render the beam invalid Another related rule is that if an axis is going to move at some point in the beam then an initial position must be established for this axis at the first control point This of course is true regardless of whether MU is simultaneously delivered while the axis is moving during beam delivery or whether the motion is part of a beamless segment As a corollary if an axis is not listed in the first control point then it cannot appear in any subsequent control points You may notice that the XML Beam of this example does not include a position for Couch Lateral It is not necessary to list positions for all the axes Some can be left as don t cares in which case the control system will not enforce any particular positioning for those axes prior to beam on The above example also specifies tolerances for some of the mechanical axes The control system will prevent beam on unless the axes are positioned to their listed positions within their specified tolerance Therefore
57. Mode user interface does not account for time spent in beamless segments i e motion only segments Therefore when delivering an XML Beam the time shown in the counter will not match the wall clock time for those beams that contain one or more motion only segments i e the counter will typically show less than wall clock time in these cases Velocity Limits The following maximum velocities apply to any XML Beam that moves one or more axes dynamically Unless the XML beam itself specifies a lower velocity limit ceiling then the following values are used to calculate the position vs time trajectory for all moving axes As explained in the previous section the actual instantaneous velocity observed at any point in the beam may be lower than the limits below or any lower limit specified by the user in the XML Beam itself because of other constraints such as dose delivered or other moving axes Axis Max Velocity MLC Carriage 1 20 cm sec MLC Leaf 2 50 cm sec GantryRtn 6 00 deg sec Collimator Rtn 15 00 deg sec CouchVrt 2 00 cm sec CouchLat 4 00 cm sec CouchLng 8 00 cm sec CouchRtn 3 00 deg sec Coll X1 2 40 cm sec Coll X2 2 40 cm sec Coll Y1 2 40 cm sec Coll Y2 2 40 cm sec Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 20 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for u
58. Once periodicity is established the Analysis section on the display changes from orange into dark blue Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 51 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Overwriting Interlocks With the appropriate user rights it is possible for a developer mode user to overwrite machine interlocks User rights in developer mode follow the same general principle as Service Mode In general it is not recommended to overwrite interlocks in Developer Mode It is expected that a functional machine will be able to deliver any valid XML beam without faults and interlocks In that sense it is recommended that users whose access to the TrueBeam machine is limited to Developer Mode be given Basic user rights in the OSP Oncology System Platform system Developer Mode like Service Mode does not allow users with Basic rights to overwrite interlocks and faults Using a DICOM file as a starting point It is possible to use the TrueBeam Treatment mode to convert a DICOM field or even a sequence of fields into a Beam XML When a DICOM field is loaded into the Treatment Modes for delivery the DICOM field is always first converted into the equivalent XML Beam since XML Beam is the native TrueBeam control system format It is therefore possible to exploit this fact
59. Type gt xs restriction base xs double gt lt Obviously dose rate cannot be less than 0 xs minInclusive value gt xs restriction xs simpleType Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 63 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs element gt lt Axis positions Units are degrees for rotational axes and centimeters for linear axes gt lt In Varian internal scale gt lt xs element name GantryRtn type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CollRtn type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CouchVrt type xs double minOccurs 0 maxOccurs 1 gt minOccurs 0 maxOccurs 1 gt lt xs element name CouchLng type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CouchRtn type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CouchLat type xs double lt Note The Collimator positions including MLC designate the resulting field size at isocenter gt lt xs element name Y1 type xs double minOccursz 0 maxOccurs 1 gt lt xs element name Y2 type xs double minOccurs 0 maxOccurs 1 gt lt xs element name X1 type xs double minOccurs 0 maxOccurs 1 gt lt xs element name X2 type xs double minOccurs 0
60. Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not For Further Distribution March 2012 Developer Mode is intended for non clinical use only and is NOT cleared for use on humans This page intentionally blank Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 This page intentionally blank Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Table of Contents IMEROCUCTION RM 1 SUP POM Weitere 2 Operational Overview 55g eec e eem tete AE e ah A E T 2 Access to Developer Mode ie edet te ete at mem ee oe 3 Mula kw C 3 Creating Varian XML Beams esses EEE EE E 3 The MU vs Position Trajectory MOdel ccccscccccccessssssssececeeecseseansesececessesesaaseeececesseseaaeaeeeeecsssuseaaeaeeeesens 3 Composing XML beams eere eee erret MD o Ebenen nennen erret r nennen rennen tente 6 The Varian TrueBeam XML Schema
61. Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 55 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans resumption positions are and there is also no automatic way to instruct the system to move to those resumption positions The end result is that typically in this situation the XML beam must be reloaded and restarted from the beginning This is especially true if any axis is intentionally moved by the user even further away from the resumption point Notice how control system response to an interrupted beam whether interrupted due to interlock fault or beam off button is different than interruption due to gating In gating when the gate opens the control system actively drives all moving axes back to the appropriate resumption point In beams interrupted by interlock fault or beam off button the control system simply stops all moving axes in the shortest possible distance That typically results in a small position overshoot relative to the point where the beam was interrupted Partial Beams not supported Partial Beams are not supported in the current version of Developer Mode In the clinical Treatment Modes it is possible to instruct the system to deliver only the last X MU of a beam initially intended to deliver a total of Y MU X lt Y The purpose of this feature in the Treatment Modes is to address the nee
62. ams Unlike Service Mode those features that could affect machine performance in the Clinical Modes e g Beam Tuning have been disabled in Developer Mode This is why unlike Service Mode Developer Mode does not provide low level access to the various accelerator sub components The purpose of this restriction is to keep Clinical Mode operations insulated from research performed using Developer Mode The essential extra feature that Developer Mode provides compared to Service Mode is the ability to load and execute XML Beams Creating Varian XML Beams Before we describe the details of how to create beam files using XML it is important to first present the MU versus Position Trajectory Model used throughout the TrueBeam control system architecture The MU vs Position Trajectory Model The MU versus Position Trajectory Model or simply Trajectory Model is a central concept within the TrueBeam control system architecture and thus applies to all modes Treatment Service Developer QA etc According to the Trajectory Model all beams whether the typically more complex beams that are Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 3 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans enabled only through Developer Mode or the simpler beams available in the Clinical and Service Modes are all described as a relation
63. at 100 00 CouchLat CouchLng 100 00 CouchLng CouchRtn 180 0 CouchRtn lt Y 1 gt 5 31 lt Y1 gt lt Y2 gt 4 81 lt Y2 gt lt X1 gt 7 18 lt X1 gt lt X2 gt 7 18 lt X2 gt Mlc ID 1 ID lt B0000000000000000008080 0 550 0 875 1 465 1 125 1 835 2 125 2 555 3 625 3 775 1 225 4 325 2 925 1 325 1 725 1 525 0 175 0 27 7 0000000000000 0 0 0 0 O 0 O O B 0000000000000000000 0 0 0 726 0 926 1 626 0 175 0 575 0 495 0 175 0 725 0 825 0 465 1 025 1 825 2 025 1 625 1 025 0 525 0 32600000000000000000 0 0 0 O A Mlc Cp Cp lt In this next control point MU is being delivered uniformly as the Gantry and Collimator rotate while MLC changes shape gt lt Mu gt 2 13 lt Mu gt lt Deliver 2 13 MU gt GantryRtn 357 03 GantryRtn lt Rotate gantry from 360 to 357 03 deg gt CollRtn 177 54 CollRtn lt Rotate collimator from 177 05 to 177 54 deg gt Mlc lt and linearly change to following MLC shape gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 15 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt ID gt 1 lt ID gt lt B0000000000000000000080 0 674 0 825 1 575 1 125 1 725 2 225 2 670 3 200 3 425 1 025 3 325 2 925 0 425 1 825 1 425 0 075 0 27 00000000000000000 0 O B A 50000000000000
64. axOccurs 1 gt RR k k k K K K K K K KK KK K KOK FK 2K 2K K 2K K K OO 2K 2K KK OK KOK KOK KOK OK K Cumulative Dose in units of 1 MU floating point number can thus be fractional MU Since dose is cumulative the dose for this control point must be greater or equal to the dose specified in the previous control point This dose specified in this control point minus the dose specified in the previous control point is the dose delivered in the last segment segment defined by this control point and previous control point If dose is the same as previous control point then the segment ending at this control point delivers no dose no dose segment BA Re K K K K K FK FK FK OE AK K K FK FK FK FKK K K K FK FK FK FK FK K K K K K 2 KK K K FK FK FK 2 2K 2K KK K K OK KOK OK KL gt lt xs element name Mu minOccurs 0 maxOccurs 1 gt lt xs simpleType gt xs restriction base xs double gt lt Obviously dose cannot be less than gt xs minInclusive value 0 gt xs restriction xs simpleType xs element RR K K K k K KK RK KK K K KK 2K 2K OK K OK OK OK OK KOK K K OK Dose rate in MU per minute for this control point Note The dose rate specified here acts as a dose rate ceiling the actual dose rate is computed on a per segment basis and may be lower than this dose rate if another moving axis is the speed limiting parameter SLP gt lt xs element name DRate minOccurs 0 maxOccurs 1 gt lt xs simple
65. be safely used to upload XML Beams to the accelerator Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans In order to facilitate offline development the typical workflow also includes two offline tools an XML Beam Checker tool and an Emulator tool These tools allow offline syntax checking and simulated delivery of XML Beams These tools are described later in the document Access to Developer Mode Access to Developer Mode is subject to license and user rights Once a valid license has been issued authorized users are allowed to launch Developer Mode by selecting Research from the TrueBeam control system main page and typing the user name and password Access rights for individual users are configured using the OSP Server platform as for Service Mode It is recommended that users who need access to Developer Mode only i e no acess to Service Mode be given Basic user rights The Basic level of access does not allow the overwriting of interlocks and faults which in most cases is adeguate for research purposes User Interface As mentioned in the introduction in terms of look and feel the Developer Mode user interface is essentially a subset of the Service Mode user interface with one very powerful addition The ability to load and deliver XML Be
66. ce However these mechanical axes cannot be moved while the MV beam is on and their motion does not follow the standard linear intra segment trajectory pattern as the Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 16 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans other mechanical axes do This restriction is described in more detail in the section Imaging Arm Positions Tolerances and Motions When the imaging arms are moved all other motions as well as beam are stopped while the arms move Motions for the imaging arms is specified via the Imaging Parameters Imaging parameters are described later in this document Note and limitation on the kV collimators also known as kV blades kV imaging foils and kV imaging filters The current version of Developer Mode does not support motion of the kV collimators and or changing of the kV imaging foils and or kV imaging filters during beam delivery Fixed positions for the kV collimators as well as a single set of kV imaging foils and kV imaging filters to be used throughout the beam can requested in the XML Beam However these settings must be indirectly established prior to beam on For more details on this limitation see the section Indirectly Setting Up the kV Foils kV Filters and kV Blades later in this document MLC Carriage Movements Specifyi
67. d deceleration of all moving axes and MU delivery until the motions and beam come to an instantaneous complete stop Then motions and beam are immediately re accelerated to the speeds and dose rate required in the next segment While this behavior does not affect the dosimetry of the beam since positions and beam are always accelerated and decelerated in a precisely synchronized fashion the overall time required to deliver the beam may be extended if the beam contains a large number of beam to motion only segment transitions The total beam time extension amounts to a small fraction of a second for each beam to motion only segment transition and vice versa In some versions of Developer Mode the last control point ina beam must contain an MU specification even if the last segment delivers no MU i e the MU specified in the last control point is the same as the MU specified in the next to last control point or an MU counter value established at an earlier control point This is simply a syntax peculiarity of some earlier versions of Developer Mode which otherwise has no dosimetric implications Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 57 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans APPENDIX A The Varian TrueBeam XML Schema Following is the Varian TrueBeam XML Schema lt xml version 1 0 encoding u
68. d gt 1 lt Id gt lt MLCMode1 gt NDS12 HD lt MLCModel lt TolTable gt lt GantryRtn gt 30 lt GantryRtn gt CouchVrt 2 00 CouchVrt CouchLng 1000 00 CouchLng CouchRtn 3 50 CouchRtn lt TolTable gt lt Accs gt lt Accs gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 10 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt ControlPoints gt lt Cp gt lt SubBeam gt Seq 0 Seq Name Beam ON Name SubBeam Energy 6x Energy Mu 0 Mu DRate 400 DRate GantryRtn 221 00 GantryRtn CollRtn 180 0 CollRtn CouchVrt 90 54 CouchVrt CouchLng 100 00 CouchLng CouchRtn 180 0 CouchRtn Y155 31 7 Y15 Y2 4 81 Y2 lt X1 gt 7 18 lt X1 gt lt X2 gt 7 18 lt X2 gt lt Ml1c gt lt ID gt 1 lt ID gt lt B0000000000008000000908020 0 675 0 875 1 575 1 125 1 725 2 225 2 725 3 225 3 425 1 Gime 325 2 92589 425 1 825 1 425 0 075 0 275 0000000000000 909000 90 0 0 0 O B A 00000000000000000 0 0 O0 0 726 0 926 1 626 0 175 0 475 0 475 0 075 0 525 0 625 0 325 1 025 1 825 2 025 1 625 1 025 0 525 0 326 0000000000000009090909050 0 O A lt Mlc gt lt Cp gt lt Cp gt lt Mu gt 20 lt Mu gt lt Cp gt lt ControlPoints gt lt SetBeam gt lt VarianResearchBeam gt Examp
69. d is NOT cleared for use on humans lt AcquisitionParameters gt lt Acquisition gt lt Mvd gt lt Positions gt lt Lat gt lt Lat gt lt Lng gt lt Lng gt lt Vrt gt 50 lt Vrt gt lt Pitch gt lt Pitch gt lt Positions gt lt Mvd gt lt ImagingPoint gt lt ImagingPoints gt lt ImagingTolerances gt lt ImagingParameters gt lt SetBeam gt lt VarianResearchBeam gt Example 11 Letting the control system deliver only as much MV MU as necessary to acquire image s Gating It is possible specify XML Beams where the beam and or imaging are gated in real time The gating can be respiratory or in general some other device that provides real time gating information to the control system GATING THE kV Imaging beam Following is an example where kV imaging is gated The example acquires images for CBCT but kV imaging stops when the gate is open Notice that motions e g gantry rotation in this example is not gated Only the kV beam is gated lt VarianResearchBeam SchemaVersion 1 0 gt lt RR RK k k K K K K k k K KK K FK OK KK KOK KK OK K K K K K Rotate gantry 368 degrees and take KV images to be used for Cone Beam Reconstruction CBCT However take images only when gate is open and slow down the gantry to take enough images for CBCT SKK 2K 2K 2K 2K FK 2K K K K K K K 2K K FK FK FK FK K K K K K K FK 2 2K 2K K K K 2 K FK FK FK 2K 2K 2K RK K K K K K KK KKK gt lt SetBeam gt l
70. d of delivering at a later time the remainder of beams that had to be abandoned before completion However this feature is not supported in the current version of Developer Mode Dry Runs not supported The TrueBeam clinical Treatment modes support the concept of a Dry Run i e the ability to simulate all the dynamic motions of a Beam without actually delivering any MU However the current version of Developer Mode does not support Dry Runs CBCT Reconstructor not available in Developer Mode The CBCT reconstructor that is typically available in Treatment Modes is not currently connected to Developer Mode Therefore while XML Beams delivered through Developer Mode may acquire CBCT projections in any one of the imaging modes available in the Treatment modes reconstruction must be performed through other means Maximum number of control points is 5000 The maximum number of control points that can be specified in the current version of Developer Mode is 5000 Images taken by an XML beam may not be available in real time in their designated directories while the XML beam is still executing The images typically become available a fraction of a second after delivery of the XML Beam completes Motion only segments may exhibit unsynchronized motion If a motion only segment moves more than one axis then the implied linearity between motions i e all axes move proportionately is maintained unless the segment also moves the MLC If a Mo
71. e trick described in the section Indirectly Setting Up the kV Foils kV Filters and kV Collimators to activate these settings since Developer Mode is currently unable to directly activate these settings prior to beam on However the control system still enforces these settings and will thus prevent Beam On through an Initial Position Interlock until the kV foils kV filters and kV blades are set up to match any such settings requested in the XML Beam If the XML Beam specifies any collimator accessories these accessories would have to mounted on the machine at this point Otherwise an Accessory interlock will ultimately prevent beam on Once all the axes have been positioned to their starting position the MV Ready button will light up on the Control Console Proceeding to beam on is the same as for the Treatment Modes Press and hold the MV Ready button for a few seconds The system will go through a pre beam on check cycle then the MV Beam On button will light Pressing the MV Beam On button at this point initiates delivery of the XML Beam If the XML beam that was loaded contains only kV beam outside treatment then only the kV Beam on button will light on the Control Console Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 49 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans
72. ee angle 0 to 200 deg 5 arc regions at different MU deg Continuous KV images are taken in the 40 to 90 degree region of the arc gt lt l K KK K K K K K K K K K K K K K K K K K K K K K K K K K K K FK K K K K K K K K K K K K K K K K K K K K K K K K K K K E K K K K K K K K K K K K K K K KK KK gt lt SetBeam gt lt Id gt 1 lt Id gt lt MLCModel gt NDS120HD lt MLCModel gt lt Accs gt lt Accs gt lt ControlPoints gt Cp lt control point zero gt SubBeam Seq 0 Seq Name Arc N Image lt Name gt lt SubBeam gt Energy 6x Energy Mu 0 Mu DRate 600 DRate GantryRtn 0 00 GantryRtn Cp Cp Mu 40 Mu GantryRtn 40 00 GantryRtn Cp 40 deg 01 MU deg gt Cp Mu 100 Mu GantryRtn 80 00 GantryRtn Cp 40 deg 01 5 MU deg gt Cp Mu 140 Mu GantryRtn 100 00 GantryRtn Cp 20 deg 22 0 MU deg gt Cp Mu 170 Mu GantryRtn 160 00 GantryRtn Cp 60 deg 00 5 MU deg gt Cp Mu 180 Mu GantryRtn 200 00 GantryRtn Cp 40 deg 00 25 MU deg gt lt ControlPoints gt lt This is the imaging instructions section of the beam gt lt ImagingParameters gt lt DuringTreatment gt lt ImagingPoints gt lt Make sure that KV source and imager are extended before starting lt ImagingPoint gt Cp 0 Cp lt Kvd gt lt Positions gt lt Lat gt lt Lat
73. ement name CouchLat type xs double minOccurs maxOccurs 1 gt lt xs element name CouchLng type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CouchRtn type xs double minOccursz 0 maxOccurs 1 gt lt xs element name X1 type xs double minOccurs 0 maxOccurs 1 gt lt xs element name X2 type xs double minOccursz 0 maxOccurs 1 gt lt xs element name Y1 type xs double minOccurs 0 maxOccurs 1 gt lt xs element name Y2 type xs double minOccurs 0 maxOccurs 1 gt lt xs sequence gt xs complexType Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 60 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs element gt lt 22 E K KK K K K A K K K A 2 K K K K K FK FK FK FK FK K K 2 K FK 2K 2 2 K K FK oe oe 2 K FK FK 2 2 K K K FK FK FK FK KK OK K K Specify any accessories to be used RULES 1 A missing element for a slot means that ANY accessory can be installed in the slot without causing an interlock i e don t care 2 The value zero in a slot means that no accessory must be installed in the slot 3 Any other integer value in a slot means that an accessory with that accessory code must be installed in that slot SEKoKokeokeke oe K K K K K K FK FK FK FK FK FK FK K K K FK 2 K K K K FK oe FK FK K K K K K K FK FK FK FK 2K K
74. erts it into an MU vs time and position vs time trajectory This conversion takes place a priori that is before beam on when the XML beam is loaded into the control system to be more exact when the PREPARE button is pressed on the TrueBeam machine s Control Console In general the control system will compute the time progression so that the beam is delivered as fast as possible given a the inherent machine limits e g maximum possible dose rates maximum possible speeds maximum accelerations etc b the user specified MU vs position trajectory in the XML beam and c any additional user specified limits such as a dose rate ceiling and axis velocity limits The control system computes the dose rate and axis velocities on a per segment basis For every segment the control system analyzes the number of MU to be delivered and total axis movement for that segment It then determines what is referred to as the Limiting Rate for that segment The limiting rate is the rate that limits how fast a segment can be delivered The limiting rate may result to be either the dose rate or the maximum velocity motion rate of an axis These in turn may result to be either the inherent machine maximum dose rate and inherent machine axis velocities or the lower user specified Dose Rate Ceiling and or velocity limits The control system uses the maximum possible rate for the Limiting Rate and then computes proportionally the segment dose rate and
75. ges can be configured in Service Mode The following example illustrates how MV images can be acquired in the lt outside treatment gt mode leaving the number of MU unspecified and thus letting the control system deliver the minimum number of MU required for the requested images VarianResearchBeam SchemaVersion 1 0 gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 39 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt RRR k k RK K k K k k K K K K KO K K K OK OK KOK OK K K OK K K KOK KOK Takes MV image in outside treatment mode thus leaving the MU unspecified Min MU required for image requested will be pulled out of configuration for the image requested K 2 Ee K K K K K K K K 2 FK FK FK K K K K K K K FK FK FK FK K K K 2 K FK 2 FK K 2K 2K K KK K K 2K K K K K KK KKK os lt SetBeam gt lt Id gt 1 lt Id gt lt MLCModel gt NDS120HD lt MLCModel gt lt Accs gt lt ControlPoints gt lt Cp gt lt SubBeam gt lt Seq gt lt Seq gt lt Name gt MV Outside Name SubBeam lt HR ER KK Kk K K K A A K FK OK K AK OK OK KOK KE OK KOK KOK K K OK KOK OK K K KOK KOK Desired energy is set to 6MV But MU is left at 0 Control system will deliver just enough MU to acquire the image type we are requesting K K ee FK FK K K K K K K FK FK FK
76. gt name eFluoroLevelControl default Low gt lt xs element minOccurs 0 maxOccurs 1 xs simpleType xs restriction base xs string gt xs enumeration value None gt xs enumeration value Low gt xs enumeration value High gt xs restriction xs simpleType xs element END OF eFluoroLevelControl lt xs element minOccurs 0 maxOccurs 1 name AutoBrightnessControl type xs boolean default false gt lt xs Sequence gt xs complexType lt xs element gt lt END OF kV parameters xs choice lt xs sequence gt lt xs complexType gt lt xs element gt lt END OF AcquisitionParameters gt lt xs sequence gt lt xs complexType gt lt END OF Acquisition gt RRR E k k k K KK K KK K K K K K K K K K K K K K FK FK FK FK K K K K K K FK A K K K K 2 2K 2K 2K 2K K K K FK 2 K 2K 2K 2K K K FK FK FK FK 2 K K FK FK FK FK FK FK OK K K K OK K K OK TypeDef for simple enumeration of the three kV filter positions 0 1 2 FKK K 2 K FK FK FKK K FK FK FK FK K 2K K K K K FK FK 2 2K 2K K 2 K K FK 2 FK FK K K FK FK FK FK FK FK FK FK 2 K K FK 2 K K K K K FK 2K 2K 2K 2K K K K K FK 2 2K 2K 2K 2K 2K 2K FK FK FK FK K K K K K K K KKK os Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 75 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt
77. h Lateral 5 Couch Longitudinal 6 Couch Rotation 7 Collimator X1 8 Collimator X2 9 Collimator Y1 10 Collimator Y2 11 Collimator MLC 12 Reserved 13 MV Detector Shoulder 14 MV Detector Elbow 15 MV Detector Wrist 16 MV Detector Hand 17 kV Detector Shoulder 18 kV Detector Elbow 19 kV Detector Wrist 20 kV Detector Hand 21 kV Source Shoulder 22 kV Source Elbow 23 kV Source Wrist 24 kV Source Hand 25 kV X1 Collimator 26 kV X2 Collimator 27 kV Y1 Collimator 28 kV Y2 Collimator 29 kV Filter Foil 30 kV Filter Shape Taking Images Only It is possible to construct XML Beams that take images only This is done by specifying a special mode the OutsideTreatment mode in the imaging section of an XML beam The following example shows how the outside treatment mode can be used to take kV images only This example rotates the gantry 368 degrees and sets up the kV imager to take continuous kV images in DynamicGainFluoro mode 11 fps This type of beam could be used to acquire projections for Cone Beam CT CBCT reconstruction Notice that no MV radiation is delivered in this Beam VarianResearchBeam SchemaVersion 1 0 gt I mK KK K K K K K K K ok K K ok K K K ok ok K K CE CE CE CE K K CE CE CE K CK CE CE CE CE K K K CE CE CE CE OK E E OK OK OK OK OK K K K Rotate gantry 368 degrees and take KV images to be used for Cone Beam Reconstruction CBCT SKK 2K 2K 2K 2K FK K K K K K K K K 2K K FK FK K K K K K K K FK 2 2 K K K K K K K FK FK FK 2K 2
78. he next etc The control system maximizes the speed of the limiting parameter and then adjusts all other parameters proportionately dose rate and speeds of moving axes so that the linear relationship of dose vs position defined by the control points is followed precisely If you want to limit the speed of any axis so that it never exceeds a certain speed in any one segment in your beam then you can use this table to set axis velocity limits The maximum velocity that you specify will act as a velocity ceiling The actual speed of any axis in any one segment may be lower if another axis or does rate is the limiting parameter If the limit you specify is higher than the inherrent maximum axis velocity then your limit will be ignored and the intrinsic maximum velocity will be used a s a limit FKK K K K Kk k K FK K K K K K K K FK KK FK FK K 2K 2K FK FK FK FKK ok K oe oe 2 FK K K K K K 2 2 2 2 K 2 2K 2K K 2K 2K KK KK 2K 2K K K OK K K OK KKK Kk oo lt xs element name VelTable minOccurs 0 maxOccurs 1 gt xs annotation lt xs documentation gt Max Velocity Table xs documentation xs annotation xs complexType lt xs Sequence gt lt units are in degrees sec or cm sec gt lt xs element name GantryRtn type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CollRtn type xs double minOccurs maxOccurs 1 lt xs element name CouchVrt type xs double minOccurs 0 maxOccurs 1 lt xs el
79. ield However since Developer Mode and the Clinical Modes use the same control system this element is also present in Developer Mode Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 9 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans proportionately lower speeds for the moving axes in the segment in order to adhere to the MU vs position Trajectory specified in the XML Beam It is important to reiterate that while the control system will never exceed the dose rate ceiling specified in the XML file regardless of which one turns out to be the limiting factor on each segment MU or one of the motions the control system will always use an appropriate combination of dose rate and motion speeds so that the MU vs Position Trajectory implied by the control points is satisfied More information on his topic can be found in the section The Time Element Dose Rates Axis Speeds and Beam Delivery Time later in this document lt Cp gt is the container for the second control point In this example it contains only one element lt Mu gt 100 lt Mu gt implying that 100MU will be delivered statically i e radiation will be delivered while nothing moves In this particular example all the positions of the mechanical axes i e gantry collimator rotation MLC shape couch positions etc are not specified and are thus
80. iggerDelay type xs double gt lt xs element minOccurs 0 maxOccurs 1 name TriggerOnEnter type xs boolean lt xs element minOccurs 0 maxOccurs 1 name TriggerOnExit type xs boolean lt xs element minOccurs 0 maxOccurs 1 name SingleTrigger type xs boolean gt lt xs sequence gt lt xs complexType gt lt RRR RR RK K K K K K K K A A A FK FK FK FK K K K K FK OK FK K K K K K K 2K 2 K 2 K K K FK FK 2K 2K 2K 2K K K FK FK FK FK 2 K K FK FK FK FK FK K K OK K K K OK K K K TypeDef for simple element none string FKK K 2 K FK FK FKK K K FK FK FK K 2K 2K K K 2K FK FK 2 2K 2K 2K 2K 2K K K FK 2 FK FK K 2 FK FK K FK FK FK FK FK K K FK FK K FK K K K K K K FK FK K K 2K K K K FK FK FK KK 2K 2K OK FK FK 2K OK OK K K K K K K K KKK cos lt xs simpleType name NoneValue gt lt xs restriction base xs string gt lt xs enumeration value none gt lt xs restriction gt lt xs simpleType gt lt RRR RR KK KK KK KK A KK A EA A OK A K K K FK 2K 2K 2K 2K AK K K FK FK FK 2K 2K 2K 2K K K FK FK FK FK K FK 2K K K FK FK FK FK FK K K K K K K K K K TypeDef for simple element DoubleNone i e xs double extended to include the value none FKK ee 2 K K K K K 2K FK FK FK FK 2 K FK FK K K AK K K oleo 2K AK AK FK FK FK FK K K K AK K AK K FK FK FK FK FK K K K K FK FK FK K K K K K K K FK FK FK AK AK K K K FK KK 2K 2K 2K K K K K K K KKK os lt xs simpleType name DoubleNone gt lt xs union memberTypes xs double NoneValue g
81. ilar to velocity and thus the dose rate limit ceiling is similar to the velocity limits ceilings They are all simply limits on rate of change d Imaging may also have some effect on velocities as beam progression may have to be throttled down or suspended during certain phases of the image acquisition process Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 17 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans The following XML Beam portion shows how a gantry velocity limit of 2 5 degrees per second and a dose rate ceiling limit of 520 MU min may be specified for the previous RapidArc example VarianResearchBeam SchemaVersion 1 0 gt lt RRR RK RK K K KK A K K K K FK FK K K K K K FK FK FK FK FK FK 2 2 K K K KK 2K 2K K K OK K K KOK KKK gt lt RapidArc with collimator rotation Gantry rotates 360 MLC changes shape and also collimator rotates gt 4 EE RK k K K K K K k k K K K K K K K K K K K FK K K K AK K K FK FK FK FK FK K K K K FK FK FK FK FK FK K K K K FK 2K 2K AK K K K K K 2K 2K 2K 2K 2K K K K K K KOK KKK gt lt SetBeam gt lt Id gt 1 lt Id gt MLCMode1 NDS120 MLCModel VelTable GantryRtn 2 50 GantryRtn lt VelTable gt lt Accs gt lt Accs gt lt ControlPoints gt lt Cp gt lt first control point Set up to initial positions gt lt SubBeam gt
82. ime see automatic positioning of axes prior to beam on later in the document Notice that tolerances apply only to the initial position of static axes that is axes that do not move during beam delivery For dynamic axes any specified tolerance becomes meaningless and the tight Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 12 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans internal control system tolerance is applied for any axis which will move during beam delivery This is true regardless of whether the axes will move concurrent with the beam or will move within the context of a motion only segment Finally the position of static axes is actively frozen during beam delivery The position is then monitored to within the internal tight tolerance of 0 1 cm or 0 1 In the unlikely event that a static axis should move during beam delivery a MOTN Motion interlock will occur Note on MLC leaf format The positions of the leaves in the XML Beam must be separated by exactly one blank space While the Beam Checker Tool allows a variable number of spaces some TrueBeam control system versions require exactly one single space Note on MLC carriage positions MLC leaves are mounted ona movable carriage If the MLC will move while delivering the XML Beam the control system automatically computes the optimal position
83. in this example the gantry would have to be positioned to within 0 3 degrees of its listed position of 221 00 degrees The couch vertical would have to be positioned to within 2 00cm of its specified 90 54 cm position i e between 88 54 and 92 54 cm The couch rotation would have to be positioned to within 3 5 degrees from 180 i e between 175 5 and 183 5 degrees Notice that collimator rotation has a position of 180 00 degrees listed but no tolerance has been specified for that axis When no tolerance is specified for an axis the default is that a tight internal control system tolerance applies by default This tolerance is 0 1 cm centimeters for translational axes and 0 1 degrees for rotational axes So in this example collimator rotation would have to be positioned at 180 00 0 1 degrees for the system to allow beam on The Multileaf Collimator MLC must always be at the exact specified shape in order to beam on In other words the MLC always defaults to an internal tight tolerance It is not possible to specify wider tolerances for the leaf positions In the above example notice how the couch longitudinal tolerance has been set very wide In essence that means that the control system will allow beam at any couch longitudinal position The effect is similar to leaving the couch position unspecified as a don t care However specifying a position albeit with a large tolerance provides a target position to easily drive to at delivery t
84. ion for gated MV radshot none once or continuously FKK K ee K K K K K K K K 2 FK FK FK FK 2 K K FK 2 FK FK K K K K FK FK FK FK K 2K K K K K K FK FK FK FK K 2 FK FK FK FK FK K K 2K 2 K FK FK FK FK FK K K K 2K OK OK OK KOK KKK oos lt 2 F K k k K K K K K K K KK K K MAX LTN E E E K k KK E EROR k k EK EO K K K K K k K K K EK K K FK K K K OK K K K K K KKK KKK oos lt xs element minOccurs 0 maxOccurs 1 name Gating gt lt xs simpleType gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 72 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans xs restriction base xs string xs enumeration value none xs enumeration value once xs enumeration value continuously xs restriction lt xs simpleType gt lt xs element gt lt xs sequence gt lt xs complexType gt lt xs element gt lt END OF AcquisitionSpecs gt lt HR ER KK K k K K K K k K k K K K K K K K K A AK K K K K FK FK K 2 FK AK K K AE FK FK FK FK K K K K FK K AK 2 K K K FK 2 2 2K 2K K K K KK KK KOK FK OK OK OK OK Container for image acquisition specifications FKK K K K K 2 K K FK FK FK FK FK K K K K K FK FK FK 2K K K K K FK FK FK FK FK K K K K K FK FK FK 2 FK FK K 2 FK FK FK AK AK K K K FK K 2 2K K 2 K 2 2K FK 2K 2K 2K 2K AK 2 FK FK FK K K K K OK OK ROK oos name AcquisitionParameters gt lt xs element
85. ion required to take images is more hierarchically organized The simplest example Beam On The following example is one of the simplest beams that can be written for the TrueBeam machine When executed through developer mode this beam simply delivers 100 monitor units of radiation VarianResearchBeam SchemaVersionz 1 0 nA RR RK k k k k k k k k k KK k k k k kk k k kkk kkk Ly lt Just beam on for 100 MU gt E K k k k k KKK K k K K K K K K K K K K K K K K Kk kkk oos lt SetBeam gt lt Id gt 1234 lt Id gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 7 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans MLCModel NDS120HD MLCModel lt Accs gt lt Accs gt lt ControlPoints gt lt Cp gt lt SubBeam gt Seq 0 Seq Name Beam ON Name SubBeam Energy 6x Energy Mu 0 Mu DRate 300 DRate Cp Cp Mu 100 Mu Cp lt ControlPoints gt lt SetBeam gt lt VarianResearchBeam gt Example 1 Just Beam On One of the simplest XML beams The first element lt VarianResearchBeam SchemaVersion 1 0 gt is mandatory and the attribute SchemaVersion must currently be set to 1 0 as shown here The purpose of this attribute is to prevent incompatible files from being loaded on the TrueBeam machine e g sh
86. ious paragraph implies that possible setups for these parameters in Developer Mode is limited to what is available in the Treatment modes Similarly imaging calibrations for CBCT acquisitions are limited to what is also available in the Treatment Modes One implication is that CBCT acquisitions must be with the kV detector at 150 cm SID This is not because of limitations in acquisition using an XML Beam The reason is because calibrations are needed for reconstruction and the only way to calibrate a CBCT mode is using the clinical system Unfortunately there is no way to modify the existing clinical modes so that a calibration can be made under non standard conditions Activating the Gating Hardware If your beam uses the gating hardware you must activate it before beam on After you have pressed the PREPARE button on the TrueBeam Control Console start the NDI camera acquisition manually by extending the tracking pane as shown in the image below T eddeg TN ms Fixed Room System Camera System Analysis Lateral Ex cm X BENZ cm Amplitude E cm Longitudinal cm Y BRE cm Phase o o 0 3 seconds ago 4 747 gt Vertical li E i cm Z EC cm Quality ER NOTE Tracking is not activated until you have pressed the PREPARE button on the TrueBeam Control Console Typically approximately four tracking cycles are required to establish periodicity of the tracking signal QualityThreshold
87. is NOT cleared for use on humans The following example illustrates the concept It delivers two static fields except that motion from the first field to the next is automatic In addition a pair of orthogonal kV MV images is taken before each field A total of four dummy control points have been introduced to facilitate indexing where images are to be taken This example also illustrates how an MV and a kV image can be acquired at the same MU point Also notice how the MLC is opened to a rectangular field in order acquire the MV image and then closed to the field shape before delivering the remainder of the field MU VarianResearchBeam SchemaVersion 1 0 gt HR RRR RRR k KK KK KK RK RK KK RK E E KK KOK KK KOK KKK KK KK OK KKK KKK Two static MLC fields First delivers 110 MU 3 2 for image 106 8 Second field delivers 72 MU 3 2 for image 68 8 Orthogonal MV KV images taken before each field 3 A A A A A 2 A A A OK KK OK k KOK KK KKK EK KK KKK KKK cos lt SetBeam gt lt Id gt 1 lt Id gt lt MLCMode1 gt NDS12 HD lt MLCMode1 gt lt Accs gt lt Accs gt lt ControlPoints gt Cp lt cp 0 Set up to initial positions square MLC field gt SubBeam Seq 0 Seq Name Demo Dummy control points Name SubBeam Energy 6x Energy Mu 0 Mu DRate 600 DRate GantryRtn 180 00 GantryRtn CollRtn 180 0 CollRtn CouchVrt 90 0 CouchVrt CouchLat 100 00 CouchLat CouchLng
88. ld occur if only one jaw is dynamic 5 MU is cumulative From one control point to the next it can only go up or stay the same It cannot decrease 6 There are some special additional rules for the first control point The first control point A Must specify a Dose value of 0 MU B Must contain Mu C Must contain DRate D Must contain SubBeam 7 Subsequent Control Points A Must contain Energy only if it is changing B Must contain Mu only if it is changing i e not a no dose segment C Must contain DRate only if it is changing D Must contain axes whose positions are changing dynamic axes E May not contain axes including MLC which were not contained in the first Control Point gt lt RRR RR RK K K K K KK KK K K AK OK FK K K K OK K K FK FK FK FK FK K K K K K K 2K K K K K KKK K K KOK KKK os lt xs element name Cp minOccurs 2 maxOccurs unbounded gt xs annotation xs documentation for more details xs documentation xs annotation xs complexType xs sequence lt xs element name TreatProgressEvent type xs string minOccurs 0 maxOccurs 1 gt lt HR K k k k K K K K K K KK KK K K K K K KK K OK OK K K OK 2K KOK K K OK KOK ROKK cos lt This is an optional tag A SubBaeam element that is used to tag the control point as the beginning of a new Sub Beam gt FE K K k k K K K K K K k K K K K K K K K K K K K K K K K K K K K FK K K K K K K FK FK K 2K
89. le 2 Adding static positions and tolerances This example delivers 200 MU statically Nothing moves during beam delivery However this example enforces specific mechanical positions By specifying positions for Gantry Rotation Collimator Rotation Couch Longitudinal Couch Vertical Couch Rotational Collimator jaws Y1 Y2 X1 X2 and an MLC shape this example will not allow beam on unless the mechanical axes listed are at their specified position Units As a general rule all positions in XML Beam files are always in Varian scale and the units are centimeters cm for translational axes and degrees for rotational axes There is no limit to the number of decimal points that can be specified however there is a practical positioning accuracy limit associated with the finite resolution and accuracy of the machine s position sensors Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 11 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans If the position of an axis is not listed at a control point it is assumed that it will not move and thus remain at the position established at some previous control point This avoids repetition of positions for axes that do not move and thus reduces the size of XML files required to specify a beam This rule however does not apply for individual MLC leaves If any of the M
90. lement gt Xs sequence xs complexType lt xs element gt lt RR RRR KK K K A A K K K K FK K K K K K K K FK FK FK FK FK K K K K K FK A 2K 2K K K 2 2K FK 2K 2K 2K 2 K FK FK FK FK FK 2 K FK FK FK OK OK KK OK K K FKK K K K K K K K K ok K K K K K K K K K K OK FK K K K K K K K K K K K K K K K K K K CE K K FK OK K FK K K K K K K K K K K FK OK K K K K K K K K K K K K K K K K K K K K Specify a tollerance table to be used optional RULES 1 If an individual axis has a specified zero tolerance value or a missing tolerance element the Control System will impose its tight internal tolerance on that axis 2 If the entire tolerance table is missing the Control System will impose its tight internal tolerance on all axes De k K K K K K K K K FK o eo FK K K K K K FK FK K K K K FK FK FK FK FK FK K 2K K K K FK FK 2 K 2 FK FK FK 2 FK K K AK AK K K FK FK FK FK K OK K K OK K KK OK KKK oos lt xs element name TolTable minOccurs 0 maxOccurs 1 gt lt xs annotation gt lt xs documentation gt Tolerance Table xs documentation xs annotation xs complexType Xxs sequence lt units are deg or cm gt lt xs element name GantryRtn type xs double minOccurs maxOccurs 1 gt lt xs element name CollRtn type xs double minOccurs maxOccurs 1 gt lt xs element name CouchVrt type xs double minOccursz 0 maxOccurs 1 gt lt xs element name CouchLat type xs double minOccurs 0 maxOccurs 1 gt l
91. low an exact predetermined predictable and repeatable path as specified in the XML Beam the plan A segment that delivers radiation only without motion a horizontal segment in the trajectory graph of figure 2 is referred to as a Beam Only Segment or Static Segment A segment that simply moves one or more axes but delivers no MU a vertical segment in the trajectory graph of figure 2 i e a segment defined by control points with the same cumulative MU is referred to as a Motion Only Segment or Beamless Segment In principle Motion only segments are subject to the same standard linearity of motion principle though there is a significant exception The exception is that if a Motion only segment delivers neither MV nor KV radiation and there is MLC motion in the segment then the motions are not synchronized see also Motion only segments may exhibit unsynchronized motion in the Limitations section Composing XML beams In principle the only tool needed to use developer Mode is a text editor to compose XML files There are also many commercially available XML editors that can simplify XML editing but simple text editors are typically adequate As already mentioned the basic operation in TrueBeam Developer Mode is to compose XML files and then load them on the TrueBeam control system to deliver beam and or take images These XML instruction files are referred to as XML Beam Files or simply XML Beams and as is typical of xml files they
92. m imaging and gating capabilities of the TrueBeam linear accelerator While the user interface UI for Developer Mode has a very similar look to Service Mode the Developer Mode UI does not allow modifications to any machine configuration or operational parameters which may affect the functionality of Clinical Modes So for example it is not possible to access the various accelerator subcomponents e g functions such as beam and motor tuning in Developer Mode This general philosophy of Developer Mode guarantees that the normal operation of Clinical Modes cannot be affected by Developer Mode activities The following is a broad description of the additional control system features that are accessible through developer Mode Define and deliver dynamic beams with arbitrary motion trajectories in MU Position space for precisely controlled predetermined variable dose rate and simultaneous motion on potentially all accelerator axes e g pre programmed variable beam dose rate with simultaneous motion on gantry and or potentially all collimation axes and or potentially all couch axes Program the acquisition of a variety of single images and or start and stop several continuous imaging sequences at any predefined arbitrary point in the above beam motion trajectory Enable the respiratory gating signal to suspend resume beam progression and or imaging As a reminder Developer mode is intended strictly for non clinical use Developer Mode
93. maxOccurs 1 gt RR ERK KKK KK K K K K KK K K K OK K K K K K OK K K K K K K OK OK OK OK KKK MLC positions in cm projected at isocenter FK K ee 2 K K K K K K K K FK 2 FK FK K K FK AK K K K K FK KK 2K 2K 2K 2K K K FK OK K K K K KK oo lt xs element name Mlc minOccurs 0 maxOccurs 2 gt lt xs complexType gt lt XS Sequence gt lt ID 1 means primary MLC ID 2 means secondary MLC gt lt xs element name ID type xs int minOccurs 1 maxOccurs 1 gt lt Array of MLC positions for Bank B for this control point leaf positions are delimited by spaces The first leaf in the array is B 1 and the last leaf is B 40 B 60 0r A 26 The positions are defined in the array as double in 1 cm units in Varian scale Values represent logical as opposed to physical positions in the Isocenter Plane gt lt xs element name B type xs string minOccurs 1 maxOccurs 1 gt lt Same as above but for Bank A gt lt xs element name A type xs string minOccurs 1 maxOccurs 1 gt lt xs sequence gt lt xs complexType gt lt END of MLC Positions gt lt xs element gt xs sequence lt END OF Cp elements list gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 64 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs comple
94. middle of an XML Beam In other words all MV radiation specified in a particular XML beam is delivered at the same energy Mu is the cumulative MU for this control point Since this is the first control point the MU here must be zero lt DRate gt is the maximum dose rate to be used for this beam in Monitor Units per minute 300MU min in this example This element is mandatory in the first control point For static beams the control system will deliver the Beam at this dose rate However for dynamic beams this dose rate is to be interpreted simply as a user defined dose rate ceiling that is a maximum dose rate not to be exceeded For dynamic beams where MU must be delivered concurrently with motions the control system will generally compute and use a different dose rate on every segment The segment dose rate used generally depends on which parameter is the limiting factor for that segment i e MU or one of the concurrent motions Therefore in general there is a maximum dose rate that can be used in a dynamic segment depending on what else is moving in that same segment If this maximum possible dose rate exceeds the ceiling dose rate specified by the user in the XML beam then the control system will use the lower user specified ceiling dose rate Of course the control system will then use also use 3 The lt SubBeam gt is a construct used primarily by the clinical modes when radiation fields are combined into one automated f
95. minOccurs 0 maxOccurs 1 lt xs complexType gt lt xS Sequence gt lt xs element minOccurs 1 maxOccurs 1 name ImageMode gt lt xs complexType gt lt xs Sequence gt lt xs element minOccurs 0 maxOccurs unbounded name Overwrite gt lt xs complexType gt lt xs simpleContent gt lt xs extension basez xs string xs attribute name parameter type xs string use required gt xs extension lt xs simpleContent gt xs complexType xs element xs sequence xs attribute name id type xs string use required ImageMode has a mandatory attribute id xs complexType lt xs element gt END OF ImageMode gt lt xs element minOccurs 0 maxOccurs 1 name AcquisitionMode gt lt xs complexType gt lt xs Sequence gt lt xs element minOccurs 0 maxOccurs unbounded name Overwrite gt xs complexType xs simpleContent lt xs extension basez xs string xs attribute name parameter type xs string use required xs extension xs simpleContent xs complexType xs element lt xs sequence gt lt xs attribute name id type xs string use required lt AcquisitionMode has a mandatory attribute id gt lt xs complexType gt lt xs element gt lt END OF AcquisitionMode gt lt xs element minOccurs 0 maxOccurs 1 name CalibrationSet type xs string gt Varian Medical Systems TrueBeam Developer Mode
96. n 80 00 GantryRtn Cp 40 deg 01 5 MU deg gt Cp Mu 140 Mu GantryRtn 100 00 GantryRtn Cp 20 deg 22 0 MU deg gt Cp Mu 170 Mu GantryRtn 160 00 GantryRtn Cp 60 deg 0 5 MU deg gt Cp Mu 180 Mu GantryRtn 200 00 GantryRtn Cp 40 deg 00 25 MU deg gt lt ControlPoints gt lt This is the imaging instructions section of the beam gt lt ImagingParameters gt lt DuringTreatment gt lt ImagingPoints gt lt FR F k k kk k k k Re k k k k k k kk OK KOK EK os lt Instructions for first MV image gt lt kkk er k k k a ok k k k k k kk OK KK EK os lt ImagingPoint gt lt Cp gt 0 25 lt Cp gt lt Index image to be taken at 10 MU point gt lt Acquisition gt lt AcquisitionId gt 1 lt AcquisitionId gt lt AcquisitionSpecs gt lt will use default specs gt lt AcquisitionParameters gt lt ImageMode id Highres gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt MV lt this is an MV image gt lt AcquisitionParameters gt lt Acquisition gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 22 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt ImagingPoint gt HERRERA REA RA RARE KK EKA KEK oko EKER S lt Instructi
97. n Y m i MU I I I Noa i Ts NA x UN MU delivery and other motions stop while arms move Arm position bu mm dia mm m m m t rF v E Time gt Control Point i Control Poin ie atfractional control point Control Point i 2 Control Point i 3 Imaging Control Point j i 1 xxx New arm positions at Fig 5 Imaging Arm motions in Time vs MU and Position space As a corollary it is not possible to move the imaging arms during irradiation Taking Continuous Images Developer Mode also supports all the continuous imaging modes Image acquisitions can be started and stopped at any point in the beam using the Imaging Point elements in the Imaging Section of the XML Beam Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 34 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans The following example illustrates continuous imaging The example consists of a 180 to O degree arc beam where kV images are taken continuously in DynamicGainFluoro mode at 11 frames per second VarianResearchBeam SchemaVersion 1 0 lt l mK RK K K K K K K K K K ok K K K K K K K K K K K K K K K K K K K K K K K K FK K K FK K K K K K K K K K K K K K K K CE K E K K K K K K E K K K K K K K K K K KK gt lt Arc Beam delivers 180 MU over 200 degr
98. nces and Motions ccccssscccssssnececssececeeseeeececseeeecesseeeecseeeeaeceseeeaeeeseenaeess 32 Taking Continuous SIHETCEBS RR 34 Axis NUMBERING enin RERO MNA 37 USTED 37 Cru ipee EE 41 Validating an XML beam seti ee ne EE 48 Loading and delivering an XML Be aM cccessscccccecsssessnseceecceceesessnaeeececsseeseseaesececeseesesasaeeeeeeesseseaeaeeeenens 48 Indirectly setting up the KV foils kV filters and kV collimators eeeeeeeeeeerenennen 50 Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 i Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Limitations for kV foil kV filter kV collimator and Imaging Calibration cc cccsccssssecssssecssseessteesssseeeees 51 Activating the Gating Hardware cccccssscccsssscecsssnececsesnececseseeecsesueeecsesaeeecseaaeeeceesaeeecseaaeeecsesaeeeseeseeeeeees 51 Overwriting InterlOCkS e rettet ente ones ea etta ven teta even sacs aa eto te dete uet en save Cea ed TR Sia NR 52 Using a DICOM file as a starting point innen ehe a nine eevee a 52 Trajectory Records Trajectory Logs nennen enne nnne nennen sinere nn nnns 54 Enabling Trajectory LOBS ro ere ret cere ee or enn eae e Peu nece pestem tna eoe Ye nee dong audn 54 Limitations arreter tr Pet oa tta et eile tote tet 55 APPENDIX A The Varian TrueBeam XML Schema
99. ng Dose Rate and Velocity limits All the previous XML beam examples contain a Dose Rate specification As already mentioned in general this dose rate should be interpreted as a limit a ceiling Therefore the dose rate parameter is better referred to as a Dose Rate Ceiling As the name implies this is a limit setting which enables the user to instruct the control system to never exceed the specified dose rate limit As already explained in general it is not possible to specify an absolute fixed target dose rate for a dynamic beam This is because in general for a dynamic beam there are other instantaneous factors such as motions or image acquisitions that may indirectly impose a lower dose rate See also the section The Time Element Dose Rates Axis Speeds and Beam Delivery Time later in this document Similarly it is possible to specify a Velocity Table inside an XML Beam The Velocity Table contains velocity limits for the various mechanical axes These again are simply velocity limit ceiling settings which enable the user to instruct the control system to never exceed the specified velocities In general the actual instantaneous velocity of an axis may be lower than the set limit This is because the actual instantaneous velocity within a segment will generally depend on other motions taking place or beam being delivered in the same segment From a conceptual standpoint when dose is viewed simply as another axis dose rate is sim
100. ng line breaks can now be viewed and edited using any text editor such as Microsoft Notepad Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 52 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Notice that the LastSetBeam xml file thus generated cannot be directly delivered through Developer Mode The following simple edits are necessary to make this file compatible for delivery in Developer Mode 1 Add the tags lt VarianResearchBeam SchemaVersionz 1 0 lt VarianResearchBeam gt so that they are the first and last tags in the entire file 2 Remove the tags lt TreatmentMode gt lt TreatmentMode gt from the plan file including whatever tags are enclosed by the TreatmentMode tags For example lt TreatmentMode gt lt CDATA FTM gt lt TreatmentMode gt should be deleted Once these simple edits are performed it should be possible to load and deliver the resulting XML beam through Developer Mode NOTE Any gating parameters used in the DICOM file will not be included in the LastSetBeam xml that is generated using the procedure above Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 53 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Trajectory Records Trajectory Logs
101. ntryRtn Cp 40 deg 01 MU deg gt Cp Mu 100 Mu GantryRtn 80 00 GantryRtn Cp 40 deg 1 5 MU deg gt Cp Mu 140 Mu GantryRtn 100 00 GantryRtn Cp 20 deg 022 0 MU deg gt Cp Mu 170 Mu GantryRtn 160 00 GantryRtn Cp 60 deg 00 5 MU deg gt Cp Mu 180 Mu GantryRtn 200 00 GantryRtn Cp 40 deg 00 25 MU deg gt ControlPoints lt This is the imaging instructions section of the beam gt lt ImagingParameters gt lt DuringTreatment gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 45 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt ImagingPoints gt lt ImagingPoint gt Cp 0 Cp lt Kvd gt lt Positions gt lt Lat gt lt Lat gt lt Lng gt lt Lng gt lt Vrt gt 70 lt Vrt gt lt Pitch gt lt Pitch gt lt Positions gt lt Kvd gt lt Kvs gt lt Positions gt Lat 0 Lat Lng 0 Lng Vrt 90 Vrt Pitch 0 Pitch Positions lt Kvs gt lt ImagingPoint gt lt Start the KV fluoro acquisition at 4 degrees lt ImagingPoint gt lt Cp gt 1 lt Cp gt lt AcquisitionStart gt lt AcquisitionId gt 1 lt AcquisitionId gt AcquisitionSpecs Handshake true Handshake AcquisitionSpecs lt AcquisitionParameters gt
102. o describe non linear behavior Five regions of different MU per degree radiation density comprise the arc Two MV images are taken concurrent with the beam one at the 10 MU point and one at the 172 79 MU point Also two kV images are taken one at the 20 MU point and one at the 120 MU point While generally speaking the image acquisitions are in a sense concurrent with the MV beam typically image taking will interfere briefly with beam delivery This is because the imager and beam 5 as the imaging system must be notified that the imaging point has been delivery must handshake reached the MV beam must be suspended while reading images taken in certain modes etc Typically these handshake operations are short and only introduce minor delays into the XML beam delivery In the following example a very short pause slowdown is seen in both the gantry speed and the MV beam delivery while the 4 images are being acquired However these slowdowns are already planned by the control system a priori i e before beam on Therefore in this example the short gantry slowdown is synchronized with beam so that the implied linearity of MU vs gantry angle implied in the Portions of the handshake can be eliminated through the lt handshake gt parameters in the imaging section However the handshake cannot be completely eliminated even if the lt handshake gt parameter is set to false Varian Medical Systems TrueBeam Developer
103. obal within the beam The velocity limit for an axis will apply regardless of whether MU is delivered concurrently with motion or whether the motion happens within the context of a motion only segment i e beamless segment Specifying velocity limits for axes that never move during the beam has no effect The Time Element Dose Rates Axis Speeds and Beam Delivery Time The XML beams do not contain a time element In other words it is not possible for the user to specify the exact time progression and overall time required to deliver an XML beam This is because it would be quite complicated for users to evaluate all the trajectory and dose interdependencies present in a dynamic beam It is thus the machine which has knowledge of its limitations eg dose rate speeds accelerations that is best suited to convert the dose position relationship implied in a specific XML beam into a Dose Position Time trajectory As mentioned users can exercise some limited control in the timing by specifying dose rate ceilings and velocity limits for various axes in their XML beams However there is no direct user control of the time element The XML beam remains to a large extent simply the specification of an MU vs position trajectory The time element is eventually computed by the control system when the XML beam is loaded for delivery In an abstract way by introducing the time element the control system takes the XML MU vs position trajectory and conv
104. of the carriages based on the MLC shape or sequence of shapes The carriages are then automatically moved into position together with the leaves when the user loads the XML Beam and performs a Go To If the sequence of MLC shapes requested is such that multiple carriage positions are required then multiple carriage positions are automatically computed when the beam is loaded into the control system Then during Beam delivery when the point is reached where a new carriage position is needed then beam as well as all other motions are temporarily suspended while the MLC carriages are moved to their new positions Adding static fields The following example shows a Beam that delivers two static fields The Beam On button is pressed only once After the MU for the first field is delivered static segment the motion to the next field happens automatically without beam motion only segment Then upon reaching the second field the beam comes on automatically While in this example the motion and the beam are not simultaneous from a control system standpoint this is considered a dynamic beam since in a general sense it requires the coordination of both beam and motion after the Beam On button is pressed VarianResearchBeam SchemaVersion 1 0 gt lt I mK KK K K K K K OK K K K K ok K K K K K FK CK CE CE CE OE K K CE CE K CE K CE CE CE CE CE K FK CE CE CE CE CE CE CE CK CE CE CE K K CE CE CE K K K K K OK CE OK E E K K K OK O
105. on from 360 to 0 degrees while MU is being delivered As seen in the control points parameters gantry rotation is not proportional to MU therefore the MU is not uniformly distributed along the arc i e variable MU per degree However within a segment i e between any two successive control points the behavior is linear i e MU delivered gantry motion and change in MLC shape are all proportional As previously mentioned this intra segment linearity is actively enforced by the control system lt VarianResearchBeam SchemaVersion 1 0 gt lt l K KK K K K K K K K K K K K K K K K FK K K K CE CE CE K K CE CE CE K CE CE CE CE CE K K K KK KK K FK K K K K K K K K K KK K K K K OK K K K K K K E K K OK K K K K gt lt RapidArc with collimator rotation Gantry rotates 360 MLC changes shape and also collimator rotates gt lt l KKK K K K K K K K K K K ok K K K K FK FK CE CE CE CE CE K K CE CE CE FK CK CE CE CE K K K K K K K K K FK K K OK OK K K OK K OK K K 2 k KRE ek kk k kkk kkk kkk S lt SetBeam gt lt Id gt 1 lt Id gt MLCModel NDS120 MLCModel lt Accs gt lt Accs gt lt ControlPoints gt lt Cp gt lt first control point Set up to initial positions gt SubBeam Seq 0 Seq Name Beam ON lt Name gt lt SubBeam gt lt Energy gt 6x lt Energy gt lt Mu gt lt Mu gt DRate 400 DRate GantryRtn 360 00 GantryRtn CollRtn 177 05 CollRtn CouchVrt 90 0 CouchVrt CouchL
106. ons for first KV image gt okokeke oko xokek ook ko oko oko ooo oko E KEKE dy ImagingPoint Cp 0 5 Cp Index image to be taken at 20 MU point Acquisition AcquisitionId 2 AcquisitionId AcquisitionSpecs Handshake true Handshake lt KV gt true lt KV gt lt AcquisitionSpecs gt lt AcquisitionParameters gt lt ImageMode id HighQuality gt lt ImageMode gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt lt KV gt KiloVolts 80 KiloVolts MilliAmperes 50 MilliAmperes MilliSeconds 10 MilliSeconds eFluoroLevelControl None eFluoroLevelControl lt KV gt lt AcquisitionParameters gt lt Acquisition gt lt ImagingPoint gt lt l a RR k k k k k k aa k k ok kb elec ok ok kk k k k EE _ gt lt Instructions for second KV image gt UIS k k ok ok K Rek ck ok ok k Rk ok ok k k k k k PEEL Ek S lt ImagingPoint gt lt Cp gt 2 5 lt Cp gt lt Index image to be taken at 120 MU point gt lt Acquisition gt lt AcquisitionId gt 3 lt AcquisitionId gt lt AcquisitionSpecs gt lt Handshake gt true lt Handshake gt lt KV gt true lt KV gt lt AcquisitionSpecs gt lt AcquisitionParameters gt ImageMode id HighQuality lt ImageMode gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt lt KV gt KiloVolts 70 KiloVolts MilliAmperes 15 MilliAmperes MilliSeconds 10 MilliSecond
107. or Mount W300UT30L 3927 Compensator Mount W45R20L 3912 Compensator Mount W45L20L 3913 Compensator Mount WA5IN20L 3914 Compensator Mount W450UT20L 3915 Compensator Mount Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 78 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans W60R15L 3900 Compensator Mount W60L15L 3901 Compensator Mount W60IN15L 3902 Compensator Mount W60O0UT15L 3903 Compensator Mount A06 4000 AccessoryMount ELECTRON_SQUARE A10 4001 AccessoryMount ELECTRON_SQUARE A15 4002 AccessoryMount ELECTRON_SQUARE A20 4003 AccessoryMount ELECTRON_SQUARE A25 4004 AccessoryMount ELECTRON_SQUARE A10X6 4006 AccessoryMount ELECTRON_RECT FT POINTER 8167 InterfaceMount FFDA A10 4094 ElectronAperture FFDA A06 126 ElectronAperture e ARC Applicator 4094 AccessoryMount PF Grat Upper 3801 InterfaceMount PF Grat Lower 3792 Compensator Mount CustomBlockTray 1 1664 AccessoryMount UpperCustomComp 1 364 InterfaceMount LowerCustomComp 1 364 Compensator Mount CustomFFDA6 1 125 ElectronAperture CustomFFDA 3328 3707 ElectronAperture IsoCal Plate 3600 InterfaceMount CustomSRSAppl 3265 3326 AccessoryMount STEREOTACTIC CustomSRSMount 3264 InterfaceMount
108. ould a later version of the TrueBeam machine with a different and incompatible XML syntax become available sometime in the future The lt SetBeam gt element is the overall container element for the beam and is also required in every XML beam file The Id element is an integer identifier for the entire beam Developer Mode does not impose any restriction on how this field is used Essentially Developer Mode users are free to identify their XML beams as they see fit The lt MLCModel gt is also required for every beam It lists the MLC model intended to be used with this beam For example the standard Milleneum 120 MLC is referred to as NDS120 whereas the smaller leaf HD MLC is referred to as NDS120HD If the specified MLC model does not match the MLC model on the target machine the control system will prevent beam on through an interlock The lt Accs gt element lists any accessories that must be mounted to deliver this beam A list of the accessories accepted by TrueBeam and their corresponding codes is listed in Appendix B The control system will prevent beam through an accessory interlock until the listed accessories are mounted Leaving this element empty as in this example means that any accessory including no accessories is compatible with this beam i e accessories are essentially don t care in this case The element must always be present even if left empty As of 2010 Check the Varian website for upda
109. re image is read out Dosimetry Dosimetry NoSyncDRI Unsynchronized 1024 x 768 MV imager continuously reads out accumulated dose independent of the beam pulse High Quality Highres Triggered Triggered High Resolution Radshot Radshot 1024 x 768 MV imager reads out the entire frame with full resolution during beam hold Same as above but image acquisition is triggered by gating device Low Dose Lowres Low Resolution Radshot 512 x 384 One image acquired in higher contrast lower resolution mode Imaging modes that use the above Single Image KV or Radshot MV Acquisition techniques should be used in conjunction with the lt Acquisition gt element while the imaging modes that use the Continuous KV Synchronized MV or Unsynchronized MV Acquisition techniques should be used in conjunction with the lt AcquisitionStart gt and lt AcquisitionStop gt elements Continuous imaging is discussed later in this document Using Dummy Control points When taking images it is often convenient to introduce extra dummy control points in an XML beam These dummy control points can then be used as reference points to index image acquisition Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 28 Reminder Developer Mode is intended for non clinical use only and
110. s eFluoroLevelControl None eFluoroLevelControl Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 23 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt KV gt lt AcquisitionParameters gt lt Acquisition gt lt ImagingPoint gt HK EKER eoe oko ARERR seo xo EKER EKER E oos lt Instructions for second MV image gt ook eoe okokok oko je ok seo o EEEE REE kkk oos ImagingPoint Cp 4 279 Cp lt Index image to be taken at 172 79 MU point gt lt Acquisition gt lt AcquisitionId gt 4 lt AcquisitionId gt lt AcquisitionSpecs gt lt AcquisitionParameters gt lt ImageMode id Highres gt lt CalibrationSet gt DefaultCalibrationSetId lt CalibrationSet gt MV gt lt AcquisitionParameters gt lt Acquisition gt lt ImagingPoint gt lt ImagingPoints gt lt ImagingTolerances gt lt mandatory even if empty gt lt ImagingParameters gt lt SetBeam gt lt VarianResearchBeam gt Example 6 Acquiring kV and MV images concurrent with MV beam The lt DuringTreatment gt element signifies that the images are part of an XML Beam that also delivers therapeutic MV radiation NOTE Some elements contain the word treatment because the same XML scripts are internally used by the control system to deliver beam in
111. s however these arms do not follow the same exact dose vs position model as the accelerator mechanical axes do More details about moving the imaging arms can be found in the imaging section of this document Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 4 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans The linear segment defined by two successive control points is simply called Segment The piecewise linear trajectory defined by the entire sequence of control points is referred to as the Segmented Trajectory or simply Trajectory This piecewise linear trajectory becomes the implied ideal trajectory to be followed at delivery time Another way to look at Control Points is that Control Points are essentially a mechanism to specify inflection points in the Trajectory i e points where the axis motion per MU delivered changes The sequencing convention for segments and control points is that the two successive control points i 1 and i define segment i Therefore a beam starts with control point O so control points O and 1 define segment 1 It is important to reiterate that there is an implied linear path within a segment and that the TrueBeam control system strictly enforces this implied linearity during beam delivery The implied linearity is illustrated in the following example ir Mra MU 165 37
112. s on the control system version The developer mode user can request that the these MU position records be permanently stored on disk for later analysis Enabling Trajectory Logs The developer mode user can request that a trajectory log be stored on disk for every beam delivered via Developer Mode Trajectory logs are enabled by checking the box shown below on the Developer Mode user interface Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 54 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans kys triel eves wc woo wom re PNDT Machine Status Beam Gantry amp Collimator Program Machine ae energy 1e wv CTY 2 Mach State Beam State M s FEX faa Coll Rtn On None my 2 ENT Water Temperature AS E ym Actual 39 599 C Dose Rate x oo Expected 39 000 C to C mel ENT Coll v1 NE c User ID Physicist o 1200 Y2 cm x NEZ sho to ue me 10m ino x 1 NEKE cn oad Plan Set Defauk Beam Open Standard Template Beam Open Custom Beam The box is not checked by default so it must be checked upon entering Developer Mode if trajectory logging is desired While the box remains checked the control system will generate a separate trajectory log for every beam delivered A message to the user is displayed e
113. s complexType gt xs attribute name Id type xs int gt xs complexType xs element Xs sequence xs complexType xs element maxOccurs 1 gt lt xs all gt lt xs complexType gt lt xs element gt lt END OF SetBeam element gt lt RRR E k k k K KK K K K KK A A K K K K KK OK FK AK K K K K FK 2 2 2 EE FK K 2 2 K K FK FK FK OK FK K OK K K K OK OK OK FRR K K K K K K KK K K K K FK K K FK K K K K K K K K K FK K K K K K K K K K K FK K FK K KK K K FK K K ok K K K K K K K K K K K K FK K K K K K K K K K K K K K K K K K K OK K K OK K K K K K K K K TYPE DEFINITIONS FR OK K K K K K K KK K K K K FK K K FK K K K K K K K K K FK K K K K K K K K K K K K K OK K K K FK K FKK K K K K OK K KK K K K OK K K OK K FK K OK K K ok K K K K K OK OK K OK OK K K K K K K K FKK 2K 2K 2K 2K 2K FK FK K K K K 2K K FK FK FK FK FK 2 FK K K FK 2 FK FK FK FK FK K K EE K K K K K FK FK FK 2K 2K AK AK K K FK eoe FK FK K FK FK FK FK FK FK FK FK 2K K K FK FK K K K K K 2K OK OK K K K K KKK Kk os lt RRR k k k K K K K K K K K K K K K K K K K K K K K K K K K K K FK FK FK FK K K K K FK K FK FK K K K K K K 2K FK 2K K 2K K 2 2K 2K 2K 2K K K FK FK FK FK K K 2K K FK FK FK FK FK FK K K K K K K K K K TypeDef for container Acquisition describing one image source FKK K K FK 2 FK FKK K K FK FK FK K 2K 2K K K K FK FK FK 2K 2K K K 2K K K FK FK FK FK FK K FK K FK FK FK FK FK FK FK FK K K 2 K FK AK K K 2 K FK 2K 2K K 2K K K K K FK FK 2K 2K 2K 2K OK FK F
114. s the 120 MU point Acquisition parameters differ from the first kV image Here a pulse of 70 kilo Volts 15 mA and 10 milliseconds in duration is used to pulse the kV source The second MV image This image is acquired at control point 4 279 which corresponds to an MU of 172 79 MU Imaging Modes As shown in the previous example the id attribute of the mageMode element is used to select the basic imaging mode for a particular image or sequence of images Of course in Developer Mode a single XML Beam may combine acquisition of many different images each image or image sequence using a different imaging mode The id attribute strings that must be specified to select the various imaging modes are shown in the following table A brief description of the basic imaging mode is also shown Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 26 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans KV Imaging Modes Imagin String id Acquisition Acquisition Resolution Definition ging 8 q q Mode Mode Technique A basic mode intended for CBCT projections In this mode each pixel Dynamic XP i i yr DynamicGain Single Image 1024 x 768 a toma tically Switches Gain to a larger gain before reaching saturation Postea allowing a wider dynamic range Dynamic As above but i
115. s the minimum number of control points gt 4 E k k k k k K K K k K K k K K K K K K K K K K K K K K K AK K FK FK FK FK K FK K K K K FK K FK FK FK FK K K K K K K K K K K K K K K K K KOK KKK gt lt General Control Point Rules 1 Unspecified i e unplanned STATIC Axes should NOT APPEAR in ANY Control Point The Control System will not enforce any tolerance restrictions on such axes However the Control System will still ensure that these axes do not move from wherever they are placed once when the system transitions to READY NOTE MLC may be unspecified STATIC by this rule 2 Specified STATIC Axes whose initial positions are contained in the Beam need only appear in the First Control Point The controller will ensure that they do not move from wherever they are placed once it goes to READY 3 Specified DYNAMIC Axes whose position program is contained in Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 61 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans the Beam need only appear in the First Control Point and any subsequent Control Point where there is a change in their position The controller will ensure that they follow their position program during the treatment 4 Only one independent jaw of a pair may be appear in a Control Point It is not necessary for both to appear This cou
116. sType lt xs element minOccurs 0 maxOccurs 1 name Kvd type ArmPositionsType lt xs element minOccurs 0 maxOccurs 1 name Kvs type ArmPositionsType lt desired arm position after the image acquisition gt lt xs element minOccurs 0 maxOccurs 1 name MvdAfter type ArmPositionsType lt xs element minOccursz 0 maxOccurs 1 name KvdAfter type ArmPositionsType namez KvsAfter type ArmPositionsType lt xs element minOccurs 0 maxOccurs 1 lt xs sequence gt lt xs complexType gt lt xs element gt END OF single imaging point element gt lt xs Sequence gt lt xs complexType gt lt xs element gt lt END OF Imaging Points sequence gt lt 2E RK k k K K K K K A A EK A K K K HK FK FK K K K K K FK FK FK FK K K K K K K AK 2K K K K K K KK 2K OK 2K OK OK OK OK KOK OK Tolerances of the imaging equipment PU arms kV collimation system aK 2 ee K A FK FK K K K K K K 2 K 2 FK FK FK 2 K K K oko eoe FK K oko K FKK FK 2 K 2K K K K FK FK FK FK 2K K K KO K K K K FK FK OK 2K K K K K KKK oos lt xs element minOccurs 1 maxOccurs 1 xs complexType lt xs Sequence gt lt units are deg or cm gt ma RRR K K K K RR KK AK K K K K K FK OK FK K 2K 2K 2K K K OK KK OK KOK KOK KOK OK K Tolerances for MV detector kV detector and kV source arms FK K K ee 2K K K FK K K 2K K 2 FK K FK FK 2 K K FK FK FK FK K K K K K FK FK FK FK K K K K K K FK FK a 2K 2K K K FK F
117. se on humans Imaging The following sections describe how to add imaging to the XML Beam files Kilo Voltage and Mega Voltage images can be taken anywhere in the XML beam In the most general case Kilo Voltage kV and Mega Voltage MV images are taken either before therapeutic MV MU is delivered and or after therapeutic MV MU is delivered and or interspersed into a beam while therapeutic MV MU is delivered or axes are moved in motion only segments It is also often desirable to construct XML Beams that take images only We discuss the more general case first XML Beams that take images concurrent with the MV therapeutic beam The Imaging Parameters Section Imaging instructions inside an XML Beam are given via lt ImagingPoints gt which are logically equivalent to the ControlPoints that are used to specify the MU vs position trajectory of the therapeutic MV beam However the ImagingPoints are specified after the ControlPoints in a separate section called ImagingParameters The imaging points are then synchronized to the therapeutic beam by referencing the ControlPoints from inside the ImagingPoints see following examples Taking two MV and two kV images concurrent with beam The following example shows an XML Beam that delivers a 180 MU 200 degree gantry rotation arc field The Beam contains more than two control points to make the number MU per degree vary throughout the arc i e inflection points are needed t
118. se parameters prior to beam on using the imager calibration mode 1 Exit Developer Mode and enter the Imager Calibration mode from the Major Mode Selection menu Right click on a CBCT or other imaging mode and select Acquire a Test Image from the options note the system must not be in stand by mode for this option to be available Make sure to select a mode which will match the foil shape filter and kV collimator positions in the XML Beam 2 The system will immediately open a scan acquisition window and move the filter foil and kV collimators to predetermined positions according to the imaging mode selected Do not proceed with the calibration Rather cancel out of the scan acquisition environment by selecting the green arrow in the upper left hand corner of the Imager Calibration environment Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 50 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Remember that although the Developer Mode environment is currently unable to set up kV foils kV filters and kV collimators the system still interlocks if these settings do not match what is being requested in the XML beam Limitations for kV foil kV filter kV collimator and Imaging Calibration The indirect procedure that must be used to set up kV foil kV filter and kV collimator parameters as described in the prev
119. ship between MU and position t In more mathematical terms the Trajectory Model treats the position of all mechanical axes as a function of MU So there is one function per axis which describes movements if any during beam delivery i e Axis Position F MU These functions are called Trajectory Functions and the entire ensemble of trajectory functions for all axes is abstractly referred to as The Trajectory For those axes that never move throughout a beam the Trajectory Function degenerates to a flat line Gantry F MU B Segments Coll Rotation F2 MU N Jaw Y1 F3 MU Jaw Y2 F4 MU Jaw X1 Fs MU Jaw X2 Fg MU MLC Leaf 1A F4 MU MLC Leaf 1B F 2 MU Position MLC Leaf 60B F4 25 MU Couch Vertical Fm MU Couch Longitudinal Fm2 MU cm P Control Points Fig 2 The MU vs Position Trajectory model Control Points and Segments The Trajectory functions are segmented into linear segments This facilitates representation of the function in digital form within the TrueBeam control system In other words the trajectory functions are described in terms of a finite number of discrete points called Control Points The Developer Mode user or any other planning entity for that matter essentially programs the machine trajectory by specifying these Control Points in an XML Beam file Note The three imaging arms MV imager KV imager and KV source can also be automatically moved during beam
120. t 2E k k RK K K K K K A K K FK FK A K K K K FK FK FK FK FK K K K K K AK 2K 2K K K K K KK 2K 2K 2K 2K OK K K OK OK Gating Parameters If the respiratory gating that feeds into the XI is to be used then specify gating parameters here FKK K FK K FK FK KK FK FK FK FK 2 FK FK FK FK K K K K FK FK FK FK FK FK K K K K K KK FK FK FK FK AK K K K K K 2 FK FK AK 2 K 2 FK FK FK FK FK K K K K K K K K K K KKK os maxOccurs 1 name GatingParameters gt lt xs element minOccurs 0 lt xs complexType gt lt xs Sequence gt lt xs element minOccursz 0 maxOccurs 1 name Source type xs string gt lt xs element minOccursz 0 maxOccurs 1 name Filter type xs string gt lt xs element minOccurs 0 maxOccurs 1 name QualityThreshold type xs double gt lt xs element minOccurs 0 maxOccurs 1 name KVGating type xs boolean lt xs element minOccurs 0 maxOccurs 1 name Position gt lt xs complexType gt lt xs Sequence gt lt xs element minOccurs 1 maxOccurs 1 name X type xs double gt maxOccurs 1 name Y type xs double gt lt xs element minOccurs 1 maxOccurs 1 name Z type xs double gt lt xs element minOccurs 1 Xs sequence lt xs complexType gt lt xs element gt lt END OF Position gt lt xs element minOccurs 0 maxOccurs 1 name Orientation gt xs complexType XS sequence lt xs element minOccurs 1 maxOccurs 1 name Qx type xs double g
121. t lt xs simpleType gt lt xs schema gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 77 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans APPENDIX B Accessories List Accessory Code Range Slot Applicator Type NoAccy1 O InterfaceMount NoAccy2 O AccessoryMount NoAccy3 O ElectronAperture NoAccy4 O Compensator Mount UnkAcc1 4095 InterfaceMount UnkAcc2 4095 AccessoryMount UnkAcc3 4095 ElectronAperture UnkAcc4 4095 Compensator Mount UnkAcc5 127 ElectronAperture W15R30U 3920 InterfaceMount W15L30U 3921 InterfaceMount W15IN30U 3922 InterfaceMount W150UT30U 3923 InterfaceMount W30R30U 3924 InterfaceMount W30L30U 3925 InterfaceMount W30IN30U 3926 InterfaceMount W300UT30U 3927 InterfaceMount W45R20U 3912 InterfaceMount W45L20U 3913 InterfaceMount W45IN20U 3914 InterfaceMount W450UT20U 3915 InterfaceMount W60R15U 3900 InterfaceMount W60L15U 3901 InterfaceMount W60IN15U 3902 InterfaceMount W60OUT15U 3903 InterfaceMount W15R30L 3920 Compensator Mount W15L30L 3921 Compensator Mount W151N30L 3922 Compensator Mount W150UT30L 3923 Compensator Mount W30R30L 3924 Compensator Mount W30L30L 3925 Compensator Mount W30IN30L 3926 Compensat
122. t lt xs element minOccurs 1 maxOccurs 1 name Qy type xs double gt lt xs element minOccurs 1 maxOccurs 1 name Qz type xs double gt lt xs element minOccurs 1 maxOccurs 1 name QO type xs double gt lt xs sequence gt lt xs complexType gt xs element lt END OF Orientation lt xs element minOccurs 1 maxOccurs unbounded name GatingWindow Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 70 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs complexType gt lt xsS Sequence gt lt xs element minOccurs maxOccurs 1 name Axis type xs string gt lt xs element minOccurs 1 maxOccurs 1 name Entry type xs double gt lt xs element minOccurs 1 maxOccurs 1 name Exit type xs double gt lt xs element minOccurs maxOccurs 1 name EntryDelay type xs double gt lt xs element minOccurs 0 maxOccurs 1 name FaultOnExit type xs boolean gt lt xs sequence gt lt xs complexType gt lt xs element gt lt END OF GatingWindow gt lt xs choice minOccurs 0 maxOccurs unbounded lt xs element name MVAcquisitionTrigger xs complexType xs complexContent lt xs extension base AcquisitionTrigger gt lt xs complexContent gt lt xs complexType gt lt xs element gt lt
123. t Id gt 1 lt Id gt lt MLCModel gt NDS120HD lt MLCModel gt lt RRR k k k K K K K K k K k K K K K K K K K K K K K K K K K K K FK FK FK FK K K K K K K FK FK K K K K K K KOK KKK Slow down the Gantry to take enough images for CBCT in spite of the gate FK KK K K K K K FKK K K K FK FK K K K K K K K 2 FK FK K K K K K FK 2 K K 2K K K FK FK FK 2K K K K K K K K OK KKK os lt VelTable gt lt GantryRtn gt 2 00 lt GantryRtn gt lt VelTable gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 41 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt Accs gt lt ControlPoints gt lt Cp gt SubBeam Seq 0 Seq Name CBCT FullFan360Gated Name SubBeam Energy Ok Energy Mu 0 Mu DRate 0 DRate lt Start the gantry in the overtravel range gt GantryRtn 364 GantryRtn Cp Cp lt Gantry rotates 368 degrees all the way on the other side of the overtravel range GantryRtn 4 GantryRtn Cp lt ControlPoints gt lt Defines the imaging parameter for the beam and each control point gt lt ImagingParameters gt lt OutsideTreatment gt MaxMu 0 MaxMu OutsideTreatment lt ImagingPoints gt lt I wR K K K K K K K K K K K ok K ck ok ok K K K K ok K K K K K ok K K K K K K K K K E K K KOK K K K KK Start continuo
124. t xs element name CouchLng type xs double minOccurs 0 maxOccurs 1 gt lt xs element name CouchRtn type xs double minOccurs maxOccurs 1 gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 59 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt xs element name Y12 type xs double minOccursz 0 maxOccurs 1 lt independent Y tolerance gt lt xs element name X12 type xs double minOccursz 0 maxOccurs 1 lt independent X tolerance gt lt xs sequence gt xs complexType xs element lt RR RR K K K K K K AK eoe K K K K K K K K oe oko FK FK FK FK FK K K K K K FK K 2K K K K K 2 2K 2 KK KK 2K 2K OK K OK K KK KOK ROKK oos lt Velocity limit table Two consecutive control points define a segment There is always a limit to how fast a segment can be delivered Depending on MU delivered and motions performed in each segment the limiting factor to how fast a segment can be delivered turns out to be either the max dose rate or one of the moving axis This is the speed limiting parameter for the segment which can be either one of the mechanical axes or the dose rate Obviously the limiting parameter can change from segment to segment e g it can be dose rate in one segment max gantry rotational speed in the next segment leaf speed in t
125. ted requirement s Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 8 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt ControlPoints gt is the overall container for the control points that will define the MU vs Position Trajectory for this beam Cp is the container for parameters associated with a control point Since control points are used to specify the segments of the Trajectory function a beam must contain at least 2 control points i e one segment minimum The first control point is special as it must contain some additional parameters see below The lt SubBeam gt element is mandatory at the first control point However the SubBeam element is typically of little interest to Developer Mode users It contains an integer sequence identifier and a generic string name Energy is a mandatory element in the first control point It specifies the MV beam energy to be used The format is dds where dd 0 99 and s x e or h where x MV X Rays e MeV electrons h MeV HDTSe electrons and k kV beams used for beams that take kV images only and thus deliver no MV beam Examples 6x for 6 MV X Rays 12e for 12 MeV electrons and Ok for kV beam only The lt Energy gt element can appear only in the first control point It is not possible to switch energies in the
126. tf 8 gt lt xs schema xmlns VMSHET xsd os varian com HET xmlns xs http www w3 0rg 2001 XMLSchema RRR k k k K KK A A K K K K FK FK A K K K K K K FK K K K K K K 2 2 2K 2K K K K FK K K 2K 2 KK FK OK K K K KK K KOK OK KL gt 1 SET BEAM gt lt The root element defining the beam gt lt RRR k k k K KK K k K K K K K A K K K K K K FK FK FK K K K K K K FK K K K K K K K FK EE K K K FK K FK 2K 2K KK K K K K K KK OK KOK OK KL gt lt xs element name SetBeam gt lt xs complexType gt lt xs all gt lt a RR RR K K K K K K K K K K EK K K K K K K K FK K K K KK K FK FK FK FK FK FK K K K K 2 2 OR AK K KK K FK KK OK OK K 2K K OK OK K K KOK KKK oo lt Specify The Version of the Varian Research Beam Schema optional but strongly recommended If the version is missing gt lt a RR RR K K K K K K K K A A oe oe FK FK FK oko K K K K FK K K K K K 2 RK AK KK KK K OK K K K K OK K KOK KK oos lt xs element name SchemaVersion type xs string minOccurs 0 maxOccurs 1 lt a RR RR K K K K K K K K K K K K K K AK K A K K K K KK K K K K FK K K K K K K KK 2 K K K K K K k 2K K KK K K FK FK FK K 2K K K K K K K KOK KK oos 1 Specify an integer number to be be used as a unique identifier for this gt 1 Research Beam gt a RR k k BK KK Ek k EK k k k k A OE k k k 2 K OE 2 k kk k k k k k k k k KK k OK k k k k kk KOK ROKK oos lt xs element name Id type xs int minOccurs 1 maxOccurs
127. the beam hold device area Beam hold device with id 4 is TrueBeam s stnadard respiratory gate Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 43 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans FK KK K K 2 FK FK FK K FK K K K FK FK FK K K K K 2 FK FK FK K K 2 K K K K K K K K K K K K KKK cos lt BeamHoldDevices gt lt Dev Id 4 gt lt BeamHoldDevices gt lt SetBeam gt lt VarianResearchBeam gt Example 12 Gated kV images The above example uses Breathing Phase gating with the gate closing between 125 and 230 Other types of gating are also possible such as amplitude or breath hold For amplitude gating the following XML excerpt can be used for the gating parameters lt GatingParameters gt lt Filter gt BreathingAmplitude lt Filter gt lt QualityThreshold gt 0 01 lt QualityThreshold gt lt GatingWindow gt Entry 1 0 Entry lt in centimeter units gt lt Exit gt 2 0 lt Exit gt lt in centimeter units gt lt GatingWindow gt lt GatingParameters gt For breath hold gating the following XML excerpt can be used for the gating parameters lt GatingParameters gt lt Filter gt PassThrough lt Filter gt QualityThreshold 0 0 QualityThreshold lt GatingWindow gt lt Axis gt z lt Axis gt Entry 10 Entr
128. the clinical modes However as a reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Specifying image acquisition points Notice how in general the imaging points reference the control points in terms of fractional control points So the lt Cp gt 0 25 lt Cp gt element in the first MV image is what indexes the image acquisition to the MV beam It essentially tells the control system to take the MV image 0 25 into the 1 segment i e fraction 0 25 along the way from control point O to control point 1 This is the point where the MU reaches 10 MU Similarly element lt Cp gt 4 279 lt Cp gt in the second MV image tells the control system to Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 24 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans take the image at fraction 0 279 into the B segment i e transition from control point 4 to control point 5 At fractional control point 4 279 the MU will be 172 79 MU The first MV image The Acquisitionld 1 Acquisitionld is a user specified unique integer identifier for the image Typically it is desirable to assign a unique identifier to each image acquisition within an XML Beam AcquisitionSpecs is an element that enables the user to change the default acquisition specifications In this example the
129. tion April 2011 66 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans maxOccurs 1 gt lt xs element name Y1 type xs double minOccurs maxOccurs 1 gt lt xs element name Y2 typez xs double minOccursz e maxOccurs 1 gt lt xs sequence gt lt xs complexType gt lt xs element gt lt END OF Imaging Velocity Table gt lt xs element minOccursz 0 maxOccurs 1 name LatchBEL type xs boolean default true gt lt xs element minOccurs 0 maxOccurs 1 name LatchKVBEL type xs boolean default true gt lt RRR RR RK K K K HK A FK FK K K K OB EK A FK FK K K K K K K 2K 2K K K K K KK 2K OK 2K 2K OK K K OK OK Sequence of imaging points An initial imaging point at Cp 0 is mandatory for all imaging axes which are specified in a subsequent imaging point SKK 2K ee K K K K K K 2K 2K 2 FK FK FK 2 K K K K FK FK FK FK FK FK 2 K K K K 2 FK FK K K 2K 2K K K FK FK FK FK 2K 2K 2K K K K FK FK FK OK K K K K K KKK oo lt xs element minOccurs 1 lt xs complexType gt lt xs Sequence gt RRR k k K K K K K K K KK KK K K AK KK A K K K K 2K 2K 2K K K K K KK OK KOK KOK KOK OK K Imaging point Refers to fractional control point indices e g 3 5 means with all Clinac axes averaged between control points with indices 3 and 4 In case of a beam group or superbeam Cp refers to the fractional control point index of the combined beam maxOccurs
130. tion only segment delivers neither MV nor KV radiation and there is MLC motion in the segment then the motions are not synchronized In this non synchronized mode of motion the axes do not follow the proportional linear motion implied in the general model and thus each axis moves independently typically at maximum speed In this In Treatment Modes these Dry Runs can be performed inside the treatment room using the in room pendant since the primary use of this feature is to visually check equipment and patient clearances with respect to any dynamic motions to be performed during the treatment Note that while here we are describing clinical mode features Developer Mode is not intended for clinical use As a reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 56 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans uncoordinated motion case the motion path is unpredictable as each axis is simoultaneously but independently moved between the positions specified at the two control points that define the segment Motion only segments trigger instantaneous stops When the control system transitions from a beam segment a segment delivering MU to a motion only segment and vice versa the control system performs a synchronize
131. us Gain DynamicGainFluoro Continuous 1024 x 768 arecontnuous y acquired at 11 frames Fluoro per second Dynamic ee yr DynamicGainLowFra d m ced Gain Low te Single Image 1024 x 768 See Dynamic Gain merate Framerate D 2 Dynamic Gain ynamic DynamicGainLowFra Low Framerate As above except that Gain Low i i merateFluoro Continuous 1024x768 WE are continuously Framerate acquired at 7 frames Fluoro per second High i i M HighQuality High Quality 2048x1536 F Pixel resolution Quality used 2x2 pixels merged into Low Dose LowDose Single Image 1024 x 768 gneto achievehigher contrast but lower resolution As above but the Triggered Triggered Low Dose Single Image 1024 x 768 images are triggered by respiratory gating Same as Low Dose but Fluoro Fluoro Continuous 1024 x 768 images continuously readout at 15 frames per second Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 27 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans MV Imaging Modes Imaging Mode String id Acquisition Mode Acquisition Technique Resolution Definition Continuous Continuous Sync Synchronized 1024 x 768 The MV imager readout is synchronized with the pause between pulses Several lines are read at each beam pulse until the enti
132. us acquisition in DynamicGainFluoro mode a good choice for CBCT FKK K FK FK K 2 K FK K FK FK FK 2 K K K FK eee 2K 2 FK FK K FK FK FK K 2K K FK OK 2K K K K OK KOK KKK gt lt ImagingPoint gt lt Cp gt 0 lt Cp gt lt AcquisitionStart gt AcquisitionId 1 AcquisitionId lt AcquisitionSpecs gt lt Handshake gt true lt Handshake gt lt KV gt true lt KV gt lt AcquisitionSpecs gt lt AcquisitionParameters gt lt ImageMode id DynamicGainFluoro gt lt CalibrationSet gt IMG CBCT lt CalibrationSet gt lt ImageDestination gt ImageDestination lt ImageDestination gt lt KV gt KiloVolts 100 KiloVolts MilliAmperes 40 MilliAmperes MilliSeconds 10 MilliSeconds eFocalSpot Large eFocalSpot eFluoroLevelControl None eFluoroLevelControl lt KV gt lt AcquisitionParameters gt lt AcquisitionStart gt lt KvFilters gt lt Foil gt 1 lt Foil gt lt Shape gt 1 lt Shape gt lt KvFilters gt lt Kvd gt Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 42 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt Positions gt lt Lat gt lt Lat gt lt Lng gt lt Lng gt lt Vrt gt 50 lt Vrt gt lt Pitch gt lt Pitch gt lt Positions gt lt Kvd gt lt Kvs gt lt Positions gt lt Lat gt lt Lat gt lt Lng gt lt Lng gt lt Vrt gt 100 lt Vrt gt
133. vailable such as DynamicGain DynamicGainFluoro DynamicGainLowFramerate DynamicGainLowFramerateFluoro LowDose Triggered and Fluoro These modes correspond to those available in the Treatment and Service Modes The Treatment imaging modes are also described in the TrueBeam Technical Reference Guide Volume 2 Imaging document See also the section Imaging Modes below CalibrationSet DefaultCalibrationSetld CalibrationSet means that the default calibration set will be used to acquire this image 7 Note that MU precision is typically limited to the quantization imposed by integral beam pulses The MU per beam pulse varies by energy As an example for 6MV X Rays each pulse delivers approximately 0 03 MU Therefore dose precision at 6X is quantized around 0 03 MU For the FFF energy modes MU per pulse and the resulting quantization is coarser up to 0 11MU Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 25 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans lt KiloVolts gt 80 lt KiloVolts gt lt MilliAmperes gt 50 lt MilliAmperes gt and Milliseconds 10 Milliseconds are the Kilo Voltage current in mA and duration in milli seconds of the kV image exposure pulse The second kV image This image is acquired at lt Cp gt 2 5 lt Cp gt which corresponds to the point where MU reache
134. very time a trajectory log is generated indicating the file name of the trajectory log The file name contains the date and time that the Trajectory Log was generated Trajectory logs are stored in the directory C VMSOS AppData TDS Output TrajectoryLog Research Trajectory logs are currently stored in binary format The exact format of trajectory record files is described in a separate document Trajectory logs can be large and thus can potentially end up occupying a significant amount of disk space It is recommended that trajectory logs be copied to another location at regular time intervals e g every day or after about a couple of hours of beam time and then removed from the control system console computer Limitations Interrupted Beams Interrupted dynamic XML Beams pose a challenge in the current version of Developer Mode If delivery of a dynamic Beam is interrupted because of a beam off or fault then any moving axes will typically stop some small distance away from their required resumption point overshoot The amount of overshoot depends on the axis inertia If the overshoot is greater than the internal axis tolerance then an interlock axis position interlock will prevent immediate resumption of Beam delivery Unfortunately there is no indication on the Developer Mode interface as to what those On version 1 5 and 1 6 control systems trajectory logs require about one GB of disk space for every hour of recorded beam time
135. xType gt lt xs element gt lt END OF Cp gt lt xs sequence gt xs complexType lt xs element gt lt END OF ControlPoints list gt lt RR RR kK K K K K K K K K K A A K K K K K K K K FK FK FK FK K K K K K FK 2 2 AK K K K FK FK 2K 2K 2K 2K 2 K FK FK FK FK FK K K K OK KOK FK FK FK K OK KOK K FKK K K K K K ok ok K K K K K FK K K FK FK K K K FK FK FK K K FK K FK FK K K K K FK FK FK K E K K K K K K FK K K FK K K FK K K K K K K FK FK K FK K K K K K K K K K K K K K K K K K K K IMAGING PARAMETERS Optional FKK K K K K K ok ok K K K K K FK K K FK K K K K K ok FK K K FK K FK FK K K K K FK K FK K E K K K K K K K K K K K K K K K K K K K K K OK FK K K K K K K K K K K K K K K K K K K K ee K K K K K K K K K FK FK FK FK FK FK K K K K K FK FK K K K K K FK FK FK FK FK K K K 2 K FK 2 K 2 FK 2 FK FK FK K 2K AK K K FK FK FK FK FK K 2K K K OK K KK OK KKK oo lt xs element name ImagingParameters minOccurs 0 maxOccurs 1 gt lt xs complexType gt lt xsS Sequence gt lt RRR RK RK K K K K K K KK K K K K KK FK KK K ok K K K KK OK KK 2K 2K 2K 2K OK KOK KOK K Specify whether images will be taken during MV beam or outside MV irradiation FKK K K K K FK K A FK FK FK FK 2 FK FK FK FK K oe oko eoe oe K K K K FK eo FK FK K K K K K FK FK 2 FK FK FK AK K K FK KK K K K KK K K K K K K KKK os maxOccurs 1 gt lt xs choice minOccurs 1 lt RR RE k k k KK K K KK K K K K K RK KK A AB K FK FK K K K K OK K K OK 2K
136. y lt in centimeter units gt lt Exit gt 15 lt Exit gt lt in centimeter units gt FaultOnExit false FaultOnExit lt EntryDelay gt 5 lt EntryDelay gt lt GatingWindow gt lt GatingParameters gt GATING THE MV Imaging beam As mentioned the MV beam can also be gated Varian Medical Systems TrueBeam Developer Mode User s Manual Draft Not for Further Distribution April 2011 44 Reminder Developer Mode is intended for non clinical use only and is NOT cleared for use on humans Notice that when the MV beam is gated all beam progression i e both MV beam and any ongoing motions are suspended while the gate is open Typically this leads to those mechanical axes that were in motion while the gate opened overshooting their position while they are aggressively stopped overshoot is more likely to happen on the heavier axes such as the gantry However the control system maintains active control of the mechanical axes and immediately drives back the overshooting axes to their appropriate resumption position Then once the gate closes again the axes are in position ready to resume the beam On resumption the finite acceleration of the mechanical axes is taken into consideration and any beam is ramped up proportionately as to maintain the MU vs position relationship specified in the XML beam at all times If following a gate open and overshoot the mechanical axes have not returned

TrueBeam Developer Mode - Radiotherapy Research Tools

Contents

Download Pdf Manuals

Related Search

Related Contents