pub fn same_axis2_placement(
a_axes: (&[f64], &[f64]),
a_location: &[f64],
b_axes: (&[f64], &[f64]),
b_location: &[f64],
epsilon: Option<f64>,
) -> boolExpand description
IfcSameAxis2Placement: do two placements describe the same frame?
Compares the two derived axes P[1]/P[2] and the location, each with
same_components.
§The schema compares ap1.Location with itself
The published function reads
IfcSameCartesianPoint(ap1.Location, ap1.Location, Epsilon) – ap1
twice, so the location is never actually tested and two placements that
differ only in origin compare equal. That is a defect, not an intent:
the surrounding function exists to decide frame identity, and the other
two terms both compare ap1 against ap2. This implementation compares
ap2.Location, and the test below pins that difference so it stays a
deliberate divergence rather than drifting back.