Clarify comparison and report controls
This commit is contained in:
parent
4aa36a6d65
commit
623de2e585
1 changed files with 26 additions and 21 deletions
|
|
@ -27,11 +27,12 @@ operations, XOR, or tolerance-based matching.
|
|||
|
||||
## Read change explanations
|
||||
|
||||
Unmatched objects can be paired to explain a replacement when the pairing is
|
||||
unique by kind, layer, and bounds, then by kind and layer. References also use
|
||||
their target cell. Ambiguous candidates remain independent removals and
|
||||
additions. Pairing helps explain the report; it does not establish persistent
|
||||
object identity or change the underlying counts.
|
||||
Pheon first pairs unmatched polygons, boxes, and paths that differ only in
|
||||
layer or type, with exactly one candidate in each revision. It then checks the
|
||||
remaining objects for unique matches by kind, layer, and bounds, followed by
|
||||
kind and layer. Reference matching uses the target cell. Ambiguous candidates
|
||||
are reported as separate removals and additions. These explanations apply to
|
||||
the current report and preserve the underlying addition and removal counts.
|
||||
|
||||
Reported bounds are envelopes of stored coordinates in cell-local database
|
||||
units. They exclude path width, rendered text size, and recursively transformed
|
||||
|
|
|
|||
Loading…
Reference in a new issue