Just a suggestion. It would be nice to modify the log analyzer module so it can be compatible with the trajectory logs generated by the new Varian Halcyon linac. If someone is interested in doing so (I am not proficient enough in Python to do it myself), I could provide examples of trajectory logs from this machine.
I attach to this message an example of a trajectory log generated by an Halcyon 2.0. It corresponds to a prostate treatment of an anonymized patient, consisting in three full arcs. I also attach the pdf report produced by pylinac analyzing this file.
I hope you can modify the code to correctly interpret the logs for this machine.
Marcelino,
Thanks for the log. Unfortunately, I can’t find the log specification for Halcyon (weird). The TrueBeam has a new v4.0 log. Considering the physical differences between the halcyon and TB it does not appear that v3 or 4 also include the Halcyon version. I will see what I can do but without a log spec it’s very hard to determine the log data layout.
Marcelino,
Could you attach the RT plan for this patient (assuming it’s anonymized)? That would help me verify the log parsing as I confirmed there is no Halcyon log spec file.
Hi James:
I am sorry for the late reply. I have just uploaded a zip file in your Dropbox containing a clinical RT plan, a QA plan of the same patient, and the corresponding log files for both plans. The clinical plan was delivered in clinical mode, so only one log was generated, including all arcs. The QA plan was delivered in QA mode and a log file was generated for each arc in the plan. It is a plan for a prostate patient with 3 full arcs. All files are anonymized.
Kind regards and thanks for your efforts