Realized-pair matching
Deprecated compatibility route
This v0.7 historical module will be removed in v0.8. Import
realization diagnostics from pyvoro2.inverse.separator instead.
pyvoro2.powerfit.realize
Compatibility exports for separator realization matching.
RealizedPairDiagnostics
dataclass
Diagnostics for matching candidate constraints to realized boundaries.
geometry
property
Return optional boundary/cell geometry and tessellation diagnostics.
requested_image_matching
property
Return requested-pair and periodic-image matching diagnostics.
to_records(constraints, *, use_ids=False)
Return one plain-Python record per candidate pair.
to_report(constraints, *, use_ids=False)
Return a JSON-friendly report for realized-boundary matching.
unaccounted_records(*, ids=None)
Return one record per realized-but-unaccounted unordered pair.
UnaccountedRealizedPair
dataclass
One realized internal boundary whose unordered pair was not supplied.
to_record(*, ids=None)
Return a plain-Python record for the unaccounted pair.
UnaccountedRealizedPairError
Bases: ValueError
Raised when unaccounted_pair_check='raise' finds absent pairs.
match_realized_pairs(points, *, domain, constraints, weights=None, radii=None, return_boundary_measure=False, return_cells=False, return_tessellation_diagnostics=False, tessellation_check='diagnose', unaccounted_pair_check='diagnose')
Determine which resolved pair constraints correspond to realized boundaries.
The matching is purely geometric: each requested ordered pair (i, j, shift)
is checked against the set of realized cell boundaries in the power
tessellation, including explicit periodic image shifts. Supply exactly one
of mathematical weights (preferred) or backend-compatible radii.
:::