v0.6.0

What's Changed

• API: Autofit a Siemens star to image for MTF calculation by @carterbox in #80
• REL: 0.6.0 by @carterbox in #83

Full Changelog: v0.5.5...v0.6.0

v0.5.5

What's Changed

• CI: Setup new CI testing using GitHub Actions by @carterbox in #79
• New geometry class and some minor fixes by @bwohlberg in #78
• DOC: Revise documentation by @carterbox in #81

New Contributors

• @bwohlberg made their first contribution in #78

Full Changelog: v0.5.4...v0.5.5

API Change and polygon intersections

• Major API change for probe.measure; now uses theta, h, v coordiantes
• Replace polytope with deterministic intersection calculations
• Change coverage glyphs to pie glyphs
• Moves tests from 3.4 to 3.6

Coverage Maps

Enhancements

• Add coverage maps as a metric
• Add wood-like phantom

Hierarchical Phantoms

Enhancements

• Speed of polytope library improved.
• Uses sphinxnb to automatically integrate demo notebooks into documentation.

Changed

• Phantom definitions are now hierarchical. Phantoms are may be nested inside each other. The Feature class is removed.
• Implements __repr__ for saving and loading phantoms. The old save and load methods are deprecated.

Documentation Update

This update mostly concerns improvement of generation and readability of the docs pages.

Polytope for computing polygon intersections

The main difference between this release and v0.1 is that the intersections of shapes beyond circles is calculated using the polytope library. This library was compared with other computational geometry libraries and was found to be faster because it uses linear systems of equations instead of symbolic computation.

Also, this version laid the groundwork for N-dimensional compatibility. Mainly, Points are specified with a list of coordinates instead of each coordinate as its own comma separated entry.