pylinac
pylinac copied to clipboard
jrkerns
Pylinac tools for Elekta
Hi, I'm an Elekta user and I was wondering if you can incorporate tools for Elekta machine such as DynamicLogFiles, IVIEW EPID, XVI CBCT, Agility MLC...I can provide you data if needed.
Hi . I do some research on DynamicLogFiles . I can help you with doing the software working for your Elekta machine. You can sent me the Dynamic LogFiles on [email protected] if you want.
Great. See this section https://github.com/jrkerns/pylinac#contributing. I would need the data and associated descriptions so that it can be parsed properly.
@zism @bozhikovstanislav, the PyMedPhys library has some tools for Elekta log files (such as converting TRF files to CSV format https://pymedphys.com/user/interfaces/cli/trf.html). The API is still in flux and the library as a whole is still in beta, but you might get some benefit from it...
I just uploaded QA Images for two Elekta head types.
- Agility Head on Versa HD (0.5cm leaves)
- Synergy MLCi (1.0cm leaves)
Image Types Include:
- FC2 Phantom (Rad Light)
- QCKV - KV image Quality
- QCMV - MV Image Quality
- CBCT CATPHAN (Synergy one has a plug in the wrong place)
- VMAT CAT - Static Gantry Picket Fence and Diaphragm Abutment Tests (Agility Versa HD Only)
- VAMT PF - EPID sag causes image to skew (could do relative gamma on it)
Note that Elekta does not give the user the ability to apply dose or profile corrections to the EPID images. Elekta leaves it up to the third party software to implement dose calibration and re-apply profile corrections.
Worse yet the EPID images are automatically rescaled for better appearance to the human eye, and the rescaling factor (called "pixel factor") is not stored in the DICOM data. The pixel factor is stored in the iView database. Customers has to buy a special developer licence to allow them to use an API to search the iView database to get PixelFactor data for each image.
The nice thing about access to the iView database is that you can pull additional information about the beam and patient. (See upload via contributing)
Out of interest I didn't have much difficulty reading the iView database with the "dbfread" library.
See the following notebook for a prototyping example:
https://www.github.com/pymedphys/pymedphys/tree/master/examples%2Fprotyping%2Fread_iViewDB%2F003_RCCC_batch.ipynb
On Tue., 26 May 2020, 12:13 pm quantumquark07, [email protected] wrote:
I just uploaded QA Images for two Elekta head types.
- Agility Head on Versa HD (0.5cm leaves)
- Synergy MLCi (1.0cm leaves)
Image Types Include:
- FC2 Phantom (Rad Light)
- QCKV - KV image Quality
- QCMV - MV Image Quality
- CBCT CATPHAN (Synergy one has a plug in the wrong place)
- VMAT CAT - Static Gantry Picket Fence and Diaphragm Abutment Tests (Agility Versa HD Only)
- VAMT PF - EPID sag causes image to skew (could do relative gamma on it)
Note that Elekta does not give the user the ability to apply dose or profile corrections to the EPID images. Elekta leaves it up to the third party software to implement dose calibration and re-apply profile corrections.
Worse yet the EPID images are automatically rescaled for better appearance to the human eye, and the rescaling factor (called "pixel factor") is not stored in the DICOM data. The pixel factor is stored in the iView database. Customers has to buy a special developer licence to allow them to use an API to search the iView database to get PixelFactor data for each image.
The nice thing about access to the iView database is that you can pull additional information about the beam and patient. (See upload via contributing)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jrkerns/pylinac/issues/182#issuecomment-633772138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSBK65KHVUHZDBFAQ4LVHLRTMQTRANCNFSM4HCNBCPQ .
That’s great news!
Sent from my iPhone
On May 26, 2020, at 2:25 AM, Simon Biggs [email protected] wrote:
Out of interest I didn't have much difficulty reading the iView database with the "dbfread" library.
See the following notebook for a prototyping example:
https://www.github.com/pymedphys/pymedphys/tree/master/examples%2Fprotyping%2Fread_iViewDB%2F003_RCCC_batch.ipynb
On Tue., 26 May 2020, 12:13 pm quantumquark07, [email protected] wrote:
I just uploaded QA Images for two Elekta head types.
- Agility Head on Versa HD (0.5cm leaves)
- Synergy MLCi (1.0cm leaves)
Image Types Include:
- FC2 Phantom (Rad Light)
- QCKV - KV image Quality
- QCMV - MV Image Quality
- CBCT CATPHAN (Synergy one has a plug in the wrong place)
- VMAT CAT - Static Gantry Picket Fence and Diaphragm Abutment Tests (Agility Versa HD Only)
- VAMT PF - EPID sag causes image to skew (could do relative gamma on it)
Note that Elekta does not give the user the ability to apply dose or profile corrections to the EPID images. Elekta leaves it up to the third party software to implement dose calibration and re-apply profile corrections.
Worse yet the EPID images are automatically rescaled for better appearance to the human eye, and the rescaling factor (called "pixel factor") is not stored in the DICOM data. The pixel factor is stored in the iView database. Customers has to buy a special developer licence to allow them to use an API to search the iView database to get PixelFactor data for each image.
The nice thing about access to the iView database is that you can pull additional information about the beam and patient. (See upload via contributing)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jrkerns/pylinac/issues/182#issuecomment-633772138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSBK65KHVUHZDBFAQ4LVHLRTMQTRANCNFSM4HCNBCPQ .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Do you have a newer iView with the upgrade to SQL?
Sent from my iPhone
On May 26, 2020, at 8:01 AM, Eric Dick [email protected] wrote:
That’s great news!
Sent from my iPhone
On May 26, 2020, at 2:25 AM, Simon Biggs [email protected] wrote:
Out of interest I didn't have much difficulty reading the iView database with the "dbfread" library.
See the following notebook for a prototyping example:
https://www.github.com/pymedphys/pymedphys/tree/master/examples%2Fprotyping%2Fread_iViewDB%2F003_RCCC_batch.ipynb
On Tue., 26 May 2020, 12:13 pm quantumquark07, [email protected] wrote:
I just uploaded QA Images for two Elekta head types.
- Agility Head on Versa HD (0.5cm leaves)
- Synergy MLCi (1.0cm leaves)
Image Types Include:
- FC2 Phantom (Rad Light)
- QCKV - KV image Quality
- QCMV - MV Image Quality
- CBCT CATPHAN (Synergy one has a plug in the wrong place)
- VMAT CAT - Static Gantry Picket Fence and Diaphragm Abutment Tests (Agility Versa HD Only)
- VAMT PF - EPID sag causes image to skew (could do relative gamma on it)
Note that Elekta does not give the user the ability to apply dose or profile corrections to the EPID images. Elekta leaves it up to the third party software to implement dose calibration and re-apply profile corrections.
Worse yet the EPID images are automatically rescaled for better appearance to the human eye, and the rescaling factor (called "pixel factor") is not stored in the DICOM data. The pixel factor is stored in the iView database. Customers has to buy a special developer licence to allow them to use an API to search the iView database to get PixelFactor data for each image.
The nice thing about access to the iView database is that you can pull additional information about the beam and patient. (See upload via contributing)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jrkerns/pylinac/issues/182#issuecomment-633772138, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSBK65KHVUHZDBFAQ4LVHLRTMQTRANCNFSM4HCNBCPQ .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
We have both, at different sites. I have been able to access both, but I haven't yet put the time to port my code over to the new schema.
On Tue., 26 May 2020, 10:03 pm quantumquark07, [email protected] wrote:
Do you have a newer iView with the upgrade to SQL?
Sent from my iPhone
On May 26, 2020, at 8:01 AM, Eric Dick [email protected] wrote:
That’s great news!
Sent from my iPhone
On May 26, 2020, at 2:25 AM, Simon Biggs [email protected] wrote:
Out of interest I didn't have much difficulty reading the iView database with the "dbfread" library.
See the following notebook for a prototyping example:
https://www.github.com/pymedphys/pymedphys/tree/master/examples%2Fprotyping%2Fread_iViewDB%2F003_RCCC_batch.ipynb
On Tue., 26 May 2020, 12:13 pm quantumquark07, < [email protected]> wrote:
I just uploaded QA Images for two Elekta head types.
- Agility Head on Versa HD (0.5cm leaves)
- Synergy MLCi (1.0cm leaves)
Image Types Include:
- FC2 Phantom (Rad Light)
- QCKV - KV image Quality
- QCMV - MV Image Quality
- CBCT CATPHAN (Synergy one has a plug in the wrong place)
- VMAT CAT - Static Gantry Picket Fence and Diaphragm Abutment Tests (Agility Versa HD Only)
- VAMT PF - EPID sag causes image to skew (could do relative gamma on it)
Note that Elekta does not give the user the ability to apply dose or profile corrections to the EPID images. Elekta leaves it up to the third party software to implement dose calibration and re-apply profile corrections.
Worse yet the EPID images are automatically rescaled for better appearance to the human eye, and the rescaling factor (called "pixel factor") is not stored in the DICOM data. The pixel factor is stored in the iView database. Customers has to buy a special developer licence to allow them to use an API to search the iView database to get PixelFactor data for each image.
The nice thing about access to the iView database is that you can pull additional information about the beam and patient. (See upload via contributing)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/jrkerns/pylinac/issues/182#issuecomment-633772138 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABSBK65KHVUHZDBFAQ4LVHLRTMQTRANCNFSM4HCNBCPQ
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jrkerns/pylinac/issues/182#issuecomment-633981921, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSBK66YPW6V2DJ2BSHMVX3RTOVXNANCNFSM4HCNBCPQ .