Skip to content

Make make_valid output order deterministic - #1630

Merged
urschrei merged 1 commit into
mainfrom
fix_validity_ordering
Nov 2, 2026
Merged

urschrei merged 1 commit into
mainfrom
fix_validity_ordering

Conversation

@urschrei

@urschrei urschrei commented Nov 2, 2026

Copy link
Copy Markdown
Member

trace_rings iterated a HashSet of boundary edges to pick ring start edges, so ring start vertices and polygon order depended on the per-process RandomState seed. Iterate the edges in spade's order instead, keeping a HashSet only for membership tests.

Fixes #1629

If an agent or LLM was involved in this change, please say so below, and note what it was used for. Autonomously-opened pull requests are not accepted: see our policy on agents and LLMs.

  • I agree to follow the project's code of conduct.
  • I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

trace_rings iterated a HashSet of boundary edges to pick ring start
edges, so ring start vertices and polygon order depended on the
per-process RandomState seed. Iterate the edges in spade's order
instead, keeping a HashSet only for membership tests.

Fixes #1629


Signed-off-by: Claude <noreply@anthropic.com>
@urschrei
urschrei force-pushed the fix_validity_ordering branch from 5b21586 to da51343 Compare November 2, 2026 21:06
@urschrei
urschrei added this pull request to the merge queue Nov 2, 2026
Merged via the queue into main with commit a4a6087 Nov 2, 2026
19 checks passed
@urschrei
urschrei deleted the fix_validity_ordering branch November 2, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

make_valid returns coordinates in a non-deterministic order

3 participants