mghro/rad-collision

Platform for collision detection during treatment planning in radiotherapy

RadCollision is an open-source platform designed to aid treatment planners in the choice of beam incidence angles that do not collide with the patient or couch. It loads a 3D model (STL file) of a LINAC and/or couch into a 3D window, that can be rotated interactively to assess collision risk. One can also load a 3D scan of the patient done e.g. with a smartphone, if full patient geometry is needed.

The (currently available) interface layers of the RadCollision platform are:

• SlicerRT (C++) -- full integration into open-source TPS
• RayStation (IronPython2.7/CPython2.7/CPython3.6) -- full integration into proprietary TPS
• Python 3 -- independent of TPS
• MATLAB -- independent of TPS

For RayStation, Here are some screenshots of the capabilities and a news release:

• https://www.youtube.com/watch?v=TlFGaw2NK6Q
• https://www.youtube.com/watch?v=6osJI_xftAE
• https://physicsworld.com/a/open-source-software-detects-potential-collisions-in-radiotherapy-plans/

Alternatives

Alternative solutions are described here:

• References of https://doi.org/10.1088/2057-1976/aba442
• Eclipse: https://doi.org/10.1002/acm2.12673
• Pinnacle: https://doi.org/10.1002/acm2.12915 https://aapm.onlinelibrary.wiley.com/doi/abs/10.1118/1.4924827
• Visual Basic: https://doi.org/10.1016/j.canrad.2020.01.003
• Visual C#.Net: https://doi.org/10.1002/acm2.12963
• MATLAB: https://doi.org/10.1002/acm2.12998
• Unity 3D: https://doi.org/10.3389/fonc.2021.617007
• Varian: https://doi.org/10.1002/acm2.13496

Licensing

This software platform is open-source, and is designed to work / be embedded with commercial TPS through their native scripting interface. You can use, modify and contribute to it. Original attribution/citation shall be granted to:

F Hueso-González et al 2020 - Biomed. Phys. Eng. Express 6 055013, "An open-source platform for interactive collision prevention in photon and particle beam therapy treatment planning". https://doi.org/10.1088/2057-1976/aba442 https://arxiv.org/abs/2007.05248

Please be aware that some submodules used by this software platform contain other licenses specific to these repositories.

Created and documented by

Fernando Hueso-González - [email protected] Massachusetts General Hospital and Harvard Medical School

Acknowledgment

Thanks to everyone reporting issues. See also Acknowledgment section on https://doi.org/10.1088/2057-1976/aba442 https://arxiv.org/abs/2007.05248

rad-collision's Issues

Trigger support from other TPS companies

Ask other TPSs to incorporate support for importing STL files as ROI.

Could use the open-source VTK functions that does that, see Slicer3D.

Robotic Arm lateral shift - error in sign depending on patient orientation

The geometry for the 2 arms do not line up.
Seems like one of the arms might be going in the opposite direction it is supposed to.

Use PatientOrientation

Right now, only HFS, FFS, etc tags are used.

Use instead the exact PatientOrientation matrix for supporting any custom rotation.

Convert angle slider bars to wheels

So that you do not have to move the mouse so much when reaching one end.

see e.g. https://forum.qt.io/topic/79940/qml-circular-slider/12

Inflate ROI function to account for safety margins

Add an Inflate ROI function, either in the core layer, or on the TPS-side, that takes into account a safety margin before calculating the ROI overlap.

beamset checking

report global collision results on a beam basis, rather than stopping and continuing for each beam

prepare more DOF for collimator rotation, eccentric rotation, etc

As in http://perk.cs.queensu.ca/sites/perkd7.cs.queensu.ca/files/Suriyakumar2017a.pdf Figure 5

Check Figure 3 for transformation matrices, and Slicer3D github code

Couch Pitch and Roll angles

couch pitch and roll angles are being ignored for the moment.

check collision in trajectory inbetween fixed beams

Add further checkbutton to GUI to check for collision in between fixed beams.

Problem: we need to support specifying the rotation direction.

Suggestion: Issue template to request some basic details?

Would it be an idea to setup a simple issue template for new issues to query some data from the user, for example RayStation version as well as perhaps a traceback when available?

I think this could give you valuable information.

More on issue templates can be found at https://docs.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository

Extend to other TPS

Write more interface layer for other TPS, e.g. Eclipse, Pinnacle, Astroid, ...

Separate better core from interface layer

Better separate Core Layer from Interface Layer

3d model database

Create a database with open 3D models of accelerators self-drawn in FreeCAD for those hospitals not able to get the original files / or NDAs.

To be potentially stored in Slicer RT, here:
https://github.com/SlicerRt/SlicerRT/tree/master/RoomsEyeView/TreatmentMachineModels/

RayStation bugs

These have been reported to RaySearch:

ROI collision intelligent selection

Automatize ROI selections for collision report intelligently, to spare computation time.

mismatch of couch angle naming convention

luke found that in proton therapy, there script crashes when clicking on check beamset. Apparently proton RTplans have a CouchAngle rather than a CouchRotationAngle.

Error: Unhandled Exception: System.InvalidOperationException: Object has no member 'CouchRotationAngle'.
Error:    at Microsoft.Scripting.Runtime.LightExceptions.CheckAndThrow(Object value)
Error:    at Microsoft.Scripting.Interpreter.FuncCallInstruction`2.Run(InterpretedFrame frame)
Error:    at Microsoft.Scripting.Interpreter.Interpreter.HandleException(InterpretedFrame frame, Exception exception)
Error:    at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
Error:    at Microsoft.Scripting.Interpreter.LightLambda.Run2[T0,T1,TRet](T0 arg0, T1 arg1)
Error:    at IronPython.Compiler.PythonCallTargets.OriginalCallTarget1(PythonFunction function, Object arg0)
Error:    at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
Error:    at _Scripting_(Object[] , Object )
Error:    at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
Error:    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
Error:    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
Error:    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
Error:    at System.Threading.ThreadHelper.ThreadStart(Object obj)

auto-choose couch

Use plan info to choose automatically couch, as in the case of the linac

read STL file paths from JSON ini file

So that script does not need to be changed ever, just adapt the INI file content.

DSC: make more efficient

Instead of using DSC, choose a more efficient algorithm to calculate ROI overlap

Automatic registration of body phantoms to complete patient geometry

See 2.1.4 section of
https://aapm.onlinelibrary.wiley.com/doi/full/10.1002/acm2.12673

Calculate minimum distance of collision

with an enable checkbox to not slow down everything

Relates/alternative to safety margin #5