Open mitch-1211 opened 2 weeks ago
Yes, the localization of the phantom depends on there being both high and low HU ROIs. This was started back in the catphan days and has been extended (beyond its foreseen uses) to all the CT-like phantoms. You can also adjust the hu_origin_slice_variance
parameter as well: https://pylinac.readthedocs.io/en/latest/cbct.html#localization-variance
A feature will be added to a future release that lets the user pass the slice number as an alternative to the localization as a fallback method.
Great to see some additional functionality added to the cheese module in
f3ea44c
, looking forward to 3.29!I am looking at implementing a Gammex RMI 465 electron density phantom in Radmachine, initial testing being performed with pylinac directly. I have submitted a phantom dataset through the google form for your reference.
I have the below code currently, which includes ROI definition:
Note I use the terminology
inner_roi_dist_mm
for the inner most ring of inserts,outer_roi_dist_mm
for the next ring moving outwards andperiphary_roi_dist_mm
for the 4 HU plugs at the periphery.We get a successful analysis using the above:
Something to note however: I've had to set
localization_radius
to be the distance corresponding toouter_roi_dist_mm
i.e not the inner most ring. Using the inner most ring results infind_origin_slice
raisingValueError("No slices were found that resembled the HU linearity module")
It's not necessarily and issue per-se, it's just something that people will probably run into. Is is possible there are too many inserts with HU close to background in the inner ring? We have three solid water inserts that are essentially background in that ring.