Hello James,
Yes, I’ve tried Google Chrome and can now upload .bin files for analysis.
Another question…What is the difference between the ‘Expected Fluence’ and ‘Actual Fluence’? The Gamma analysis always gives a 100% pass rate regardless of the Gamma-Distance-to-Agreement and Gamma-Dose-to-Agreement values. What is the algorithm actually comparing? Please explain. Thank you.
Best regards,
Kris Armoogum
Principal Radiotherapy Physicist
Royal Derby Hospital
UK
Kris,
Glad it’s working.
The .bin file holds two pieces of information regarding the MLCs during treatment. The position they’re supposed to be at, and the position they are actually at. This is recorded every 20ms by default on a truebeam. The planned positions come from the RTPlan file, and the actual positions come from the MLC encoders. You can read about the log reading library here. The open area formed by the MLCs is summed every 20ms (weighted by MUs delivered) to create a composite fluence. Pylinac runs a gamma on the actual fluence and planned fluence. In practice, there is hardly ever a large difference between the planned and actual positions/fluence, so tight tolerances are usually needed to tell a difference. Let me know if this clarifies things,
James
Hi James,
Can you give me access to the website app? I signed up but did not receive a confirmation email.
thanks,
Baozhou
Hello Michel,
I am running into a similar problem using iview. The pylinac docs say that it will first look at the filename to attribute the collimator angle but I get an error message saying that beamlimitingdeviceangle is not found or something like that. I don’t mind using pydicom to add the dicom field but do you happen to know which value pylinac will use? For instance if there is a difference between the filename and the dicomtag?
Hi Ellis,
James implemented a more elegent solution, but it really depends on the workflow.
Here are the dicom elements (using pydicom) :
GantryAngle
BeamLimitingDeviceAngle
PatientSupportAngle
Ellis,
Here is the reference on using file names. Note this is only applicable for the WL module and is not used in other modules. On how pylinac looks for the axis value. Pylinac will look up the filename first; if it doesn’t find anything there, it will look up the DICOM tag.
Hey James,
I am experiencing the issue that I cannot upload .zip files to your site. It gives me the message that the upload has failed. I tried Firefox and Chrome. Can you check if this is an issue on your side or if I have to check mine?
Thank you
I’m assuming this is for CBCT? Does the demo file work on your end?
Hello James,
I am interested in using the webapp and could you please kindly let me know how to sign up and get the sign up code from you. By the way, i havent seen the Winston Lutz module added to the web app, will it happen soon.
Mark Chan
Just go to the website and sign up.
The WL module is not in the app currently. I just found out that Heroku has increased their “slug size” limit, which was the limitation of advancing pylinac versions. I will consider adding it, but with my time so limited with other projects and so many people using the app now I am considering commercializing it.
Hello All.
Is this still available ? is a demo online version available ? Thanks