Replies: 3 comments 4 replies
-
As described in the typical use section (https://pylinac.readthedocs.io/en/latest/acr.html#typical-use), you need to analyze the phantom first. So:
|
Beta Was this translation helpful? Give feedback.
-
There are two bugs I can see. The configuration extent check has a rounding error. Note the 53.2738 vs 53.2739. This is obviously rounding differences. This can be worked around using this snippet: https://gist.github.com/jrkerns/073c72d6b55c20afc84a55029eb28410
Which looks like so: Unfortunately, the It also looks like the geometric module is a bit different than what I can see from the ACR docs (Figure 4, page 8 of https://www.acraccreditation.org/-/media/ACRAccreditation/Documents/MRI/LargePhantomGuidance.pdf?la=en). What version of the phantom is this? |
Beta Was this translation helpful? Give feedback.
-
Thank you very much for the feedback. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
I tried to test the ACRMRILarge module.
I have put 11 MRI slices of a dedicated acquisition in a folder and I try to pull these lines:
from pylinac import ACRMRILarge
acr_folder = r"C:/Temp/ACR"
mri = ACRMRILarge(acr_folder)
mri.results()
and when a enter the mri.result() I have the following problem:
Is there any specific acquisition protocol or code to make is work?
Thanks a lot,
Paul
Beta Was this translation helpful? Give feedback.
All reactions