Skip to content

Separate visually merged component-pin traces - #952

Open
ShiboSoftwareDev wants to merge 1 commit into
mainfrom
codex/fix-cross-net-shared-segment
Open

Separate visually merged component-pin traces#952
ShiboSoftwareDev wants to merge 1 commit into
mainfrom
codex/fix-cross-net-shared-segment

Conversation

@ShiboSoftwareDev

Copy link
Copy Markdown
Contributor

Summary

  • treat different-net parallel runs as overlapping when their rendered strokes visually merge near separate pins of the same component
  • keep the broader overlap behavior unchanged for unrelated routes
  • add a reduced TIDA-01141 LM393 comparator-input reproduction and update affected routing snapshots

Why

The TIDA-01141 current/voltage-sense schematic produced two electrically separate comparator-input traces only 0.01 schematic units apart. With a 0.02-unit trace stroke, the SVG rendered them as one wire with an apparent junction. The overlap solver previously handled only mathematically collinear centerlines.

Verification

  • bun test (274 pass, 4 skip)
  • bunx tsc --noEmit
  • focused TIDA-01141 regression asserts at least the minimum rendered centerline clearance

@vercel

vercel Bot commented Aug 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
schematic-trace-solver Ready Ready Preview Aug 27, 2026 8:38am

Request Review

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.

1 participant