Winston-Lutz Multi-Target¶

Overview¶

Added in version 3.9.

The Multi-Target Winston-Lutz (MTWL) is an advanced test category meant to measure multiple locations away from isocenter, typically to represent multi-lesion SRS cases. The MTWL module can analyze images with any number of BBs in any arrangement. It is generalizable such that new phantom analyses can be created quickly.

Technically, there are two flavors of multi-target WL: multi-field and single field. An example of a multi-field WL is the SNC MultiMet. Each field is centered around each BB. The BB position is compared to that of the field. This is closest to what the patient experiences since it incorporates both the gantry/coll/couch deviations as well as the MLCs.

An example of a single-field multi-target WL is Machine Performance Check. The BBs are compared to the known positions. This removes the error of the MLCs to isolate just the gantry/coll/couch.

Currently, only the multi-field flavor is supported, but work on the single-field flavor will occur to support things like secondary checks of MPC.

This is why the class is called WinstonLutzMultiTargetMultiField as there will be an anticipated WinstonLutzMultiTargetSingleField.

Differences from single-target WL¶

Warning

The MTWL algorithm is new and provisional. There are a number of limitations with the algorithm. Hopefully, these are removed in future updates. The algorithm is still considered valuable even with these limitations which is why it is released.

Important

In a nutshell, the MTWL analyzes BB positions only, whereas vanilla WL provides more machine-related data as well as BB position data.

Unlike the single-target WL algorithm (aka “vanilla” WL), there are more limitations to acquisition and outputs. This should improve over time, but for now you can think of the MTWL as a subset of the vanilla WL algorithm:

Utility methods such as loading images are the same.
Outputs related to the BBs are different.
BB size is not a parameter but is part of the BB arrangement.
Single images cannot be analyzed.
Axis deviations (Gantry wobble, etc) are not yet available.
Couch rotation images are dropped as they cannot yet be handled.
Interpreting filenames is not yet allowed.

See the following sections for more info.

Image Acquisition
Supported Phantoms

Running the Demo¶

To run the multi-target Winston-Lutz demo, create a script or start an interpreter session and input:

from pylinac import WinstonLutzMultiTargetMultiField

WinstonLutzMultiTargetMultiField.run_demo()

Results will be printed to the console and a figure showing the zoomed-in images will be generated:

Winston-Lutz Multi-Target Multi-Field Analysis
==============================================
Number of images: 8

2D distances
============
Max 2D distance of any BB->Field: 5.27 mm
Mean 2D distance of any BB->Field: 2.00 mm
Median 2D distance of any BB->Field: 2.53 mm

BB #      Description
--------  ----------------------------------
Iso       Left 0.0mm, Up 5.0mm, In 0.0mm
Out       Left 0.0mm, Up 0.0mm, Out 60.0mm
In        Left 0.0mm, Up 0.0mm, In 30.0mm
Left/Out  Left 10.0mm, Up 10.0mm, Out 30.0mm

Image                   G    C    P    Iso    Out    In    Left/Out
--------------------  ---  ---  ---  -----  -----  ----  ----------
=0, Gantry sag=0.dcm    0    0    0   0      5.27  2.61        2.61
=0, Gantry sag=0.dcm    0    0   45   0.01   5.24  2.61        2.53
=0, Gantry sag=0.dcm    0    0   90   0      5.27  2.61        2.61
=0, Gantry sag=0.dcm    0    0  270   0      5.27  2.61        2.61
=0, Gantry sag=0.dcm    0    0  315   0.01   5.24  2.61        2.53
=0, Gantry sag=0.dcm   90    0    0   0.05   0.07  0.1         0.38
=0, Gantry sag=0.dcm  180    0    0   0      5.27  2.61        2.46
=0, Gantry sag=0.dcm  270    0    0   0.05   0.67  0.07        0.1

Image                   Couch Angle    Yaw Error (°)
--------------------  -------------  ---------------
=0, Gantry sag=0.dcm              0             4.96
=0, Gantry sag=0.dcm             45             4.91
=0, Gantry sag=0.dcm             90             4.96
=0, Gantry sag=0.dcm            270             4.96
=0, Gantry sag=0.dcm            315             4.91

(Source code)

_images/winston_lutz_multi-1_00.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-1_01.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-1_02.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-1_03.png — (`png`, `hires.png`, `pdf`)¶

Image Acquisition¶

The Winston-Lutz module will only load EPID images. The images can be from any EPID however and any SID. To ensure the most accurate results the following should be noted:

Images with a rotated couch are dropped and not analyzed (yet) but will not cause an error.
The BBs should not occlude each other.
The BBs should be >5mm apart in any given image.
The radiation fields should have >5mm separation in any given image.
The BB and radiation field should be <=5 mm away from the nominal location given by the arrangement.

Coordinate Space¶

The MTWL algorithm uses the same coordinate system as the vanilla WL. Coordinate Space.

Passing a coordinate system¶

No coordinate system is passed or used (yet).

Note

This is a target for the MTWL algorithm, so expect this to change in the future.

Supported Phantoms¶

Currently, only the MultiMet-WL cube from SNC is supported. However, the algorithm is generalized and can be easily adapted to analyze other phantoms. See Custom BB Arrangements.

Typical Use¶

Analyzing a multi-target Winston-Lutz test is simple. First, let’s import the class:

from pylinac import WinstonLutzMultiTargetMultiField
from pylinac.winston_lutz import BBArrangement

From here, you can load a directory:

my_directory = "path/to/wl_images"
wl = WinstonLutzMultiTargetMultiField(my_directory)

You can also load a ZIP archive with the images in it:

wl = WinstonLutzMultiTargetMultiField.from_zip("path/to/wl.zip")

Now, analyze it. Unlike the vanilla WL algorithm, we have to pass the BB arrangement to know where the BBs should be in space. Preset phantoms exist, or a custom arrangement can be passed.

wl.analyze(bb_arrangement=BBArrangement.SNC_MULTIMET)

And that’s it! You can now view images, print the results, or publish a PDF report:

# plot all the images
wl.plot_images()
# save figures of the image plots for each bb
wl.save_images(prefix="snc")
# print to PDF
wl.publish_pdf("mymtwl.pdf")

Visualizing BBs in space¶

The BBs can be visualized by using the plot_location() method and will show all the measured BB locations and their nominal locations.

(Source code, png, hires.png, pdf)

Changing BB detection size¶

To change the size of BB pylinac is expecting you must change it in the BB arrangement. This allows phantoms with multiple BB sizes to still be analyzed. See Custom BB Arrangements

Custom BB Arrangements¶

Note

Changed in version 3.22.

The BB arrangement was changed to a be a class instance instead of a simple dictionary. See BBConfig.

The MTWL algorithm uses a priori BB arrangements. I.e. you need to know where the BBs should exist in space relative to isocenter. The MTWL algorithm is flexible to accommodate any reasonable arrangement of BBs.

To create a custom arrangement, say for an in-house phantom or commercial phantom not yet supported, define the BB offsets and size like so. Use negative values to move the other direction:

from pylinac.winston_lutz import BBConfig

my_special_phantom_bbs = [
    BBConfig(
        name="Iso",
        offset_left_mm=0,
        offset_up_mm=0,
        offset_in_mm=0,
        bb_size_mm=5,
        rad_size_mm=20,
    ),  # 5mm BB at iso
    BBConfig(
        name="Left",
        offset_left_mm=30,
        offset_up_mm=0,
        offset_in_mm=0,
        bb_size_mm=4,
        rad_size_mm=20,
    ),  # 4mm BB 30mm to left of iso
    BBConfig(
        name="Down and In",
        offset_left_mm=0,
        offset_up_mm=-20,
        offset_in_mm=10,
        bb_size_mm=5,
        rad_size_mm=20,
    ),  # BB DOWN 20mm and in 10mm
    # keep going as needed
]

Pass it to the algorithm like so:

wl = WinstonLutzMultiTargetMultiField(...)
wl.analyze(bb_arrangement=my_special_phantom_bbs)
...

Algorithm¶

The MTWL algorithm is based on the vanilla WL algorithm. For each BB and image combination, the image is searched at the nominal location for the BB and radiation field. If it’s not found it will be skipped for that combo. The BB must be detected in at least one image or an error will be raised.

The algorithm works like such:

Allowances

The images can be acquired with any EPID (aS500, aS1000, aS1200) at any SID.
The image can have any number of BBs.
The BBs can be at any 3D location.

Restrictions

Warning

Analysis can fail or give unreliable results if any Restriction is violated.

Each BB and radiation field must be within 5mm of the expected position in x and y in the EPID plane. I.e. it must be <=7mm in scalar distance.
BBs must not occlude or be <5 mm from each other in any 2D image.
Images with a rotated couch are dropped and not analyzed (yet) but will not cause an error.
The radiation fields should have >5mm separation in any given image.

Analysis

This algorithm is performed for each BB and image combination:

Find the field center – The spread in pixel values (max - min) is divided by 2, and any pixels above the threshold is associated with the open field. The pixels are converted to black & white and the center of mass of the pixels is assumed to be the field center.
Find the BB – The image is converted to binary based on pixel values both above the 50% threshold as above, and below the upper threshold. The upper threshold is an iterative value, starting at the image maximum value, that is lowered slightly when the BB is not found. If the binary image has a reasonably circular ROI, is approximately the right size, and is within 5mm of the expected BB position, the BB is considered found and the pixel-weighted center of mass of the BB is considered the BB location.
Evaluate against the field position – Once the measured BB and field positions are known, both the scalar distance and vector from the field position to the measured BB position is determined.

Benchmarking the Algorithm¶

With the image generator module we can create test images to test the WL algorithm on known results. This is useful to isolate what is or isn’t working if the algorithm doesn’t work on a given image and when commissioning pylinac. It is common, especially with the WL module, to question the accuracy of the algorithm. Since no linac is perfect and the results are sub-millimeter, discerning what is true error vs algorithmic error can be difficult. The image generator module is a perfect solution since it can remove or reproduce the former error.

Note

With the introduction of the MTWL algorithm, so too a multi-target synthetic image generator has been created: generate_winstonlutz_multi_bb_multi_field().

Warning

The image generator is limited in accuracy to ~1/2 pixel because creating the image requires a row or column to be set. E.g. a 5mm field with a 0.336mm pixel size means we need to create a field of 14.88 pixels wide. We can only set the field to be 14 or 15 pixels, so the nearest field size of 15 pixels or 5.04mm is set.

2-BB Perfect Delivery¶

Create a perfect set of fields with 1 BB at iso and another 20mm left, 20mm down, and 60mm inward (this is the same as the demo, but is good for explanation).

import pylinac
from pylinac.winston_lutz import BBConfig
from pylinac.core.image_generator import simulators, layers, generate_winstonlutz_multi_bb_multi_field

wl_dir = 'wl_dir'
generate_winstonlutz_multi_bb_multi_field(
        simulator=simulators.AS1200Image(sid=1000),
        field_layer=layers.PerfectFieldLayer,
        final_layers=[layers.GaussianFilterLayer(sigma_mm=1),],
        dir_out=wl_dir,
        field_offsets=((0, 0, 0), (20, -20, 60)),
        field_size_mm=(20, 20),
        bb_offsets=[[0, 0, 0], [20, -20, 60]],
)
arrange = (
    BBConfig(name='Iso', offset_left_mm=0, offset_up_mm=0, offset_in_mm=0, bb_size_mm=5, rad_size_mm=20),
    BBConfig(name='Left,Down,In', offset_left_mm=20, offset_up_mm=-20, offset_in_mm=60, bb_size_mm=5, rad_size_mm=20),
)

wl = pylinac.WinstonLutzMultiTargetMultiField(wl_dir)
wl.analyze(bb_arrangement=arrange)
print(wl.results())
wl.plot_images()

(Source code)

_images/winston_lutz_multi-3_00.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-3_01.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-3_02.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-3_03.png — (`png`, `hires.png`, `pdf`)¶

which has an output of:

Winston-Lutz Multi-Target Multi-Field Analysis
==============================================
Number of images: 4

2D distances
============
Max 2D distance of any BB->Field: 0.00 mm
Mean 2D distance of any BB->Field: 0.00 mm
Median 2D distance of any BB->Field: 0.00 mm

BB #          Description
------------  -----------------------------
Iso           Left 0mm, Up 0mm, In 0mm
Left,Down,In  Left 20mm, Down 20mm, In 60mm

Image                   G    C    P    Iso    Left,Down,In
--------------------  ---  ---  ---  -----  --------------
=0, Gantry sag=0.dcm    0    0    0      0               0
=0, Gantry sag=0.dcm   90    0    0      0               0
=0, Gantry sag=0.dcm  180    0    0      0               0
=0, Gantry sag=0.dcm  270    0    0      0               0

As shown, we have perfect results.

Offset BBs¶

Let’s now offset both BBs by 1mm to the left:

import pylinac
from pylinac.winston_lutz import BBConfig
from pylinac.core.image_generator import simulators, layers, generate_winstonlutz_multi_bb_multi_field

wl_dir = 'wl_dir'
generate_winstonlutz_multi_bb_multi_field(
        simulator=simulators.AS1200Image(sid=1000),
        field_layer=layers.PerfectFieldLayer,
        final_layers=[layers.GaussianFilterLayer(sigma_mm=1),],
        dir_out=wl_dir,
        field_offsets=((0, 0, 0), (20, -20, 60)),
        field_size_mm=(20, 20),
        bb_offsets=[[1, 0, 0], [21, -20, 60]],  # here's the offset
)
arrange = (
    BBConfig(name='Iso', offset_left_mm=0, offset_up_mm=0, offset_in_mm=0, bb_size_mm=5, rad_size_mm=20),
    BBConfig(name='Left,Down,In', offset_left_mm=20, offset_up_mm=-20, offset_in_mm=60, bb_size_mm=5, rad_size_mm=20),
)

wl = pylinac.WinstonLutzMultiTargetMultiField(wl_dir)
wl.analyze(bb_arrangement=arrange)
print(wl.results())
wl.plot_images()

(Source code)

_images/winston_lutz_multi-4_00.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-4_01.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-4_02.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-4_03.png — (`png`, `hires.png`, `pdf`)¶

with an output of:

Winston-Lutz Multi-Target Multi-Field Analysis
==============================================
Number of images: 4

2D distances
============
Max 2D distance of any BB->Field: 1.01 mm
Mean 2D distance of any BB->Field: 0.50 mm
Median 2D distance of any BB->Field: 0.50 mm

BB #          Description
------------  -----------------------------
Iso           Left 0mm, Up 0mm, In 0mm
Left,Down,In  Left 20mm, Down 20mm, In 60mm

Image                   G    C    P    Iso    Left,Down,In
--------------------  ---  ---  ---  -----  --------------
=0, Gantry sag=0.dcm    0    0    0   1.01            1.01
=0, Gantry sag=0.dcm   90    0    0   0               0
=0, Gantry sag=0.dcm  180    0    0   1.01            1.01
=0, Gantry sag=0.dcm  270    0    0   0               0

Both BBs report a shift of 1mm. Note this is only in 0 and 180. A left shift would not be captured at 90/270.

Random error¶

Let’s now add random error:

Note

The error is random so performing this again will change the results slightly.

import pylinac
from pylinac.winston_lutz import BBConfig
from pylinac.core.image_generator import simulators, layers, generate_winstonlutz_multi_bb_multi_field

wl_dir = 'wl_dir'
generate_winstonlutz_multi_bb_multi_field(
        simulator=simulators.AS1200Image(sid=1000),
        field_layer=layers.PerfectFieldLayer,
        final_layers=[layers.GaussianFilterLayer(sigma_mm=1),],
        dir_out=wl_dir,
        field_offsets=((0, 0, 0), (20, -20, 60)),
        field_size_mm=(20, 20),
        bb_offsets=[[0, 0, 0], [20, -20, 60]],
        jitter_mm=2  # here we add random noise
)
arrange = (
    BBConfig(name='Iso', offset_left_mm=0, offset_up_mm=0, offset_in_mm=0, bb_size_mm=5, rad_size_mm=20),
    BBConfig(name='Left,Down,In', offset_left_mm=20, offset_up_mm=-20, offset_in_mm=60, bb_size_mm=5, rad_size_mm=20),
)

wl = pylinac.WinstonLutzMultiTargetMultiField(wl_dir)
wl.analyze(bb_arrangement=arrange)
print(wl.results())
wl.plot_images()

(Source code)

_images/winston_lutz_multi-5_00.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-5_01.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-5_02.png — (`png`, `hires.png`, `pdf`)¶

_images/winston_lutz_multi-5_03.png — (`png`, `hires.png`, `pdf`)¶

with an output of:

Winston-Lutz Multi-Target Multi-Field Analysis
==============================================
Number of images: 4

2D distances
============
Max 2D distance of any BB->Field: 4.21 mm
Mean 2D distance of any BB->Field: 1.74 mm
Median 2D distance of any BB->Field: 1.39 mm

BB #          Description
------------  -----------------------------
Iso           Left 0mm, Up 0mm, In 0mm
Left,Down,In  Left 20mm, Down 20mm, In 60mm

Image                   G    C    P    Iso    Left,Down,In
--------------------  ---  ---  ---  -----  --------------
=0, Gantry sag=0.dcm    0    0    0   2.38            2.71
=0, Gantry sag=0.dcm   90    0    0   1.06            1.39
=0, Gantry sag=0.dcm  180    0    0   4.21            1.39
=0, Gantry sag=0.dcm  270    0    0   0.48            0.34

API Documentation¶

Bases: WinstonLutz

Parameters¶

directorystr, list[str]: Path to the directory of the Winston-Lutz EPID images or a list of the image paths
use_filenames: bool: Whether to try to use the file name to determine axis values. Useful for Elekta machines that do not include that info in the DICOM data. This is mutually exclusive to axis_mapping. If True, axis_mapping is ignored.
axis_mapping: dict: An optional way of instantiating by passing each file along with the axis values. Structure should be <filename>: (<gantry>, <coll>, <couch>).
axes_precision: int | None: How many significant digits to represent the axes values. If None, no precision is set and the input/DICOM values are used raw. If set to an integer, rounds the axes values (gantry, coll, couch) to that many values. E.g. gantry=0.1234 => 0.1 with precision=1. This is mostly useful for plotting/rounding (359.9=>0) and if using the keyed_image_details with results_data.
dpi: The dots-per-inch setting. Only needed if using TIFF images and the images do not contain the resolution tag. An error will raise if dpi is not passed and the TIFF resolution cannot be determined.
sid: The Source-to-Image distance in mm. Only needed when using TIFF images.

machine_scale: MachineScale¶

images: Sequence[WinstonLutzMultiTargetMultiFieldImage]¶

image_type¶: alias of WinstonLutzMultiTargetMultiFieldImage

bb_arrangement: tuple[BBConfig]¶

bbs: list[BB3D]¶: 3D representation of the BBs

classmethod from_demo_images()[source]¶: Instantiate using the demo images.

static run_demo()[source]¶: Run the Winston-Lutz MT MF demo, which loads the demo files, prints results, and plots a summary image.

analyze(bb_arrangement: tuple[BBConfig, ...], is_open_field: bool = False, is_low_density: bool = False, machine_scale: MachineScale = MachineScale.IEC61217)[source]¶

Analyze the WL images.

Parameters¶

bb_arrangement: The arrangement of the BBs in the phantom. A dict with offset and BB size keys. See the BBArrangement class for keys and syntax.

plot_location(show: bool = True, viewbox_mm: float | None = None, plot_bb: bool = True, plot_isocenter_sphere: bool = True, plot_couch_iso: bool = True, plot_coll_iso: bool = True, show_legend: bool = True)[source]¶

Plot the isocenter and size as a sphere in 3D space relative to the BB. The iso is at the origin.

Only images where the couch was at zero are considered.

Parameters¶

showbool: Whether to plot the image.
viewbox_mmfloat: The default size of the 3D space to plot in mm in each axis.
plot_bbbool: Whether to plot the BB location; the size is also considered.
plot_isocenter_spherebool: Whether to plot the gantry + collimator isocenter size.
plot_couch_isobool: Whether to plot the couch-plane-only isocenter size. This will be zero if there are no images where the couch rotated.
plot_coll_isobool: Whether to plot the collimator-plane-only isocenter size. This is shown along the Z/Y plane only to differentiate from the couch iso visualization. The collimator plane is always normal to the gantry angle. This will be zero if there are no images where the collimator rotated.
show_legendbool: Whether to show the legend.

property bb_shift_vector: Vector, float, float, float¶

Calculate the ideal shift in 6 degrees of freedom to place the BB at the isocenter.

Returns¶

Vector: The ideal shift vector in mm for the cartesian coordinates. X,Y, and Z follow the pylinac coordinate convention.
float: Yaw; The ideal rotation about the Z-axis in degrees.
float: Pitch; The ideal rotation about the X-axis in degrees.
float: Roll; The ideal rotation about the Y-axis in degrees.

Parameters¶

prefixstr: The prefix name of the file to save to. The BB name is appended to the prefix.

save_images_to_stream(**kwargs) → dict[str, BytesIO][source]¶: Save the individual image plots to stream

plot_summary(show: bool = True, fig_size: tuple | None = None)[source]¶: Plot a summary figure showing the gantry sag and wobble plots of the three axes.

plot_axis_images(axis: Axis = Axis.GANTRY, show: bool = True, ax: Axes | None = None)[source]¶

Plot all CAX/BB/EPID positions for the images of a given axis.

For example, axis=’Couch’ plots a reference image, and all the BB points of the other images where the couch was moving.

Parameters¶

axis{‘Gantry’, ‘Collimator’, ‘Couch’, ‘GB Combo’, ‘GBP Combo’}: The images/markers from which accelerator axis to plot.
showbool: Whether to actually show the images.
axNone, matplotlib.Axes: The axis to plot to. If None, creates a new plot.

property max_bb_deviation_2d: float¶: The maximum distance from any measured BB to its nominal position

property mean_bb_deviation_2d: float¶: The mean distance from any measured BB to its nominal position

property median_bb_deviation_2d: float¶: The median distance from any measured BB to its nominal position

results(as_list: bool = False) → str[source]¶

Return the analysis results summary.

Parameters¶

as_listbool: Whether to return as a list of strings vs single string. Pretty much for internal usage.

Publish (print) a PDF containing the analysis, images, and quantitative results.

Parameters¶

filename(str, file-like object): The file to write the results to.
notesstr, list of strings: Text; if str, prints single line. If list of strings, each list item is printed on its own line.
open_filebool: Whether to open the file using the default program after creation.
metadatadict: Extra data to be passed and shown in the PDF. The key and value will be shown with a colon. E.g. passing {‘Author’: ‘James’, ‘Unit’: ‘TrueBeam’} would result in text in the PDF like: ————– Author: James Unit: TrueBeam ————–
logo: Path, str: A custom logo to use in the PDF report. If nothing is passed, the default pylinac logo is used.

class pylinac.winston_lutz.WinstonLutzMultiTargetMultiFieldImage(file: str | BinaryIO | Path, use_filenames: bool = False, **kwargs)[source]¶

Bases: WLBaseImage

A 2D image of a WL delivery, but where multiple BBs are in use.

Parameters¶

filestr: Path to the image file.
use_filenames: bool: Whether to try to use the file name to determine axis values. Useful for Elekta machines that do not include that info in the DICOM data.

find_field_centroids(is_open_field: bool) → list[Point][source]¶

Find the centroid of the radiation field based on a 50% height threshold. This applies the field detection conditions and also a nearness condition.

Returns¶

points: The CAX point locations.

find_bb_centroids(bb_diameter_mm: float, low_density: bool) → list[Point][source]¶: Find the specific BB based on the arrangement rather than a single one. This is in local pixel coordinates

class pylinac.winston_lutz.WinstonLutzMultiTargetMultiFieldResult(*, pylinac_version: str = '3.22.0', date_of_analysis: datetime = None, num_total_images: int, max_2d_field_to_bb_mm: float, median_2d_field_to_bb_mm: float, mean_2d_field_to_bb_mm: float, bb_arrangement: tuple[BBConfig, ...], bb_maxes: dict[str, float], bb_shift_vector: Vector, bb_shift_yaw: float, bb_shift_pitch: float, bb_shift_roll: float)[source]¶

Bases: ResultBase

This class should not be called directly. It is returned by the results_data() method. It is a dataclass under the hood and thus comes with all the dunder magic.

Use the following attributes as normal class attributes.

Create a new model by parsing and validating input data from keyword arguments.

Raises [ValidationError][pydantic_core.ValidationError] if the input data cannot be validated to form a valid model.

self is explicitly positional-only to allow self as a field name.

num_total_images: int¶

max_2d_field_to_bb_mm: float¶

median_2d_field_to_bb_mm: float¶

mean_2d_field_to_bb_mm: float¶

bb_arrangement: tuple[BBConfig, ...]¶

bb_maxes: dict[str, float]¶

bb_shift_vector: VectorSerialized¶

bb_shift_yaw: float¶

bb_shift_pitch: float¶

bb_shift_roll: float¶

model_computed_fields: ClassVar[dict[str, ComputedFieldInfo]] = {}¶: A dictionary of computed field names and their corresponding ComputedFieldInfo objects.

model_config: ClassVar[ConfigDict] = {'arbitrary_types_allowed': True}¶: Configuration for the model, should be a dictionary conforming to [ConfigDict][pydantic.config.ConfigDict].

model_fields: ClassVar[dict[str, FieldInfo]] = {'bb_arrangement': FieldInfo(annotation=tuple[BBConfig, ...], required=True), 'bb_maxes': FieldInfo(annotation=dict[str, float], required=True), 'bb_shift_pitch': FieldInfo(annotation=float, required=True), 'bb_shift_roll': FieldInfo(annotation=float, required=True), 'bb_shift_vector': FieldInfo(annotation=Vector, required=True, metadata=[PlainSerializer(func=<function to_json>, return_type=PydanticUndefined, when_used='always')]), 'bb_shift_yaw': FieldInfo(annotation=float, required=True), 'date_of_analysis': FieldInfo(annotation=datetime, required=False, default_factory=builtin_function_or_method), 'max_2d_field_to_bb_mm': FieldInfo(annotation=float, required=True), 'mean_2d_field_to_bb_mm': FieldInfo(annotation=float, required=True), 'median_2d_field_to_bb_mm': FieldInfo(annotation=float, required=True), 'num_total_images': FieldInfo(annotation=int, required=True), 'pylinac_version': FieldInfo(annotation=str, required=False, default='3.22.0')}¶

Metadata about the fields defined on the model, mapping of field names to [FieldInfo][pydantic.fields.FieldInfo].

This replaces Model.__fields__ from Pydantic V1.

class pylinac.winston_lutz.BBConfig(*, name: str, offset_left_mm: float, offset_up_mm: float, offset_in_mm: float, bb_size_mm: float, rad_size_mm: float)[source]¶

Bases: BaseModel

Create a new model by parsing and validating input data from keyword arguments.

Raises [ValidationError][pydantic_core.ValidationError] if the input data cannot be validated to form a valid model.

self is explicitly positional-only to allow self as a field name.

to_human() → str[source]¶: Convert one BB location to a human-readable str

model_computed_fields: ClassVar[dict[str, ComputedFieldInfo]] = {}¶: A dictionary of computed field names and their corresponding ComputedFieldInfo objects.

model_config: ClassVar[ConfigDict] = {}¶: Configuration for the model, should be a dictionary conforming to [ConfigDict][pydantic.config.ConfigDict].

model_fields: ClassVar[dict[str, FieldInfo]] = {'bb_size_mm': FieldInfo(annotation=float, required=True), 'name': FieldInfo(annotation=str, required=True), 'offset_in_mm': FieldInfo(annotation=float, required=True), 'offset_left_mm': FieldInfo(annotation=float, required=True), 'offset_up_mm': FieldInfo(annotation=float, required=True), 'rad_size_mm': FieldInfo(annotation=float, required=True)}¶

Metadata about the fields defined on the model, mapping of field names to [FieldInfo][pydantic.fields.FieldInfo].

This replaces Model.__fields__ from Pydantic V1.

Winston-Lutz Multi-Target¶

Overview¶

Differences from single-target WL¶

Running the Demo¶

Image Acquisition¶

Coordinate Space¶

Passing a coordinate system¶

Supported Phantoms¶

Typical Use¶

Visualizing BBs in space¶

Changing BB detection size¶

Custom BB Arrangements¶

Algorithm¶

Benchmarking the Algorithm¶

2-BB Perfect Delivery¶

Offset BBs¶

Random error¶

API Documentation¶

Parameters¶

Parameters¶

Parameters¶

Returns¶

See Also¶

Parameters¶

Parameters¶

Parameters¶

Parameters¶

Parameters¶

Returns¶