Skip to content

warpcorrect: Fix comparison to marker#3364

Open
Lestropie wants to merge 1 commit into
masterfrom
warpcorrect_tolerance
Open

warpcorrect: Fix comparison to marker#3364
Lestropie wants to merge 1 commit into
masterfrom
warpcorrect_tolerance

Conversation

@Lestropie
Copy link
Copy Markdown
Member

Using (vec-val).isMuchSmallerThan(precision) had two issues: firstly, the help string claimed that the precision term related to the L2 norm, but no such norm was computed; secondly, the input scalar to .isMuchSmallerThan() was treated as the scalar value to which to compare, to which a default precision multiplier was then applied. Comparison to zero with a precision tolerance is more consistent with intent.

Discovered while trying to process the same data set as that which exposed #3362.

Using (vec-val).isMuchSmallerThan(precision) had two issues: firstly, the help string claimed that the precision term related to the L2 norm, but no such norm was computed; secondly, the input scalar to .isMuchSmallerThan() was treated as the scalar value to which to compare, to which a default precision multiplier was then applied. Comparison to zero with a precision tolerance is more consistent with intent.
@Lestropie Lestropie requested a review from a team May 17, 2026 05:42
@Lestropie Lestropie self-assigned this May 17, 2026
@Lestropie Lestropie added the bug label May 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant