Skip to content

Add same-net trace segment bridge phase#371

Open
HunterCML wants to merge 1 commit into
tscircuit:mainfrom
HunterCML:codex/same-net-trace-bridge-29
Open

Add same-net trace segment bridge phase#371
HunterCML wants to merge 1 commit into
tscircuit:mainfrom
HunterCML:codex/same-net-trace-bridge-29

Conversation

@HunterCML
Copy link
Copy Markdown

Summary

/claim #29

Adds a dedicated post-cleanup SameNetTraceSegmentBridgeSolver phase for close same-net trace segments. The phase runs after TraceCleanupSolver and before the second net-label placement pass so later label/collision phases consume the bridged traces.

Scope

  • groups routed traces by userNetId / globalConnNetId / dcConnNetId
  • only bridges horizontal-with-horizontal or vertical-with-vertical internal segments
  • requires close coordinates and overlapping projections
  • preserves endpoint-only segments so pin anchors are not moved
  • leaves different nets untouched
  • exports the solver for focused reuse/tests

Validation

  • npx --yes bun test tests/solvers/SameNetTraceSegmentBridgeSolver/SameNetTraceSegmentBridgeSolver.test.ts
  • npx --yes bun test tests/examples/example29.test.ts tests/examples/example30.test.ts tests/examples/example34.test.ts
  • npx --yes bun run build
  • .\node_modules\.bin\tsc.exe --noEmit
  • git diff --check

AI-assisted with OpenAI Codex; I reviewed the diff and kept the phase conservative to avoid merging unrelated nets or moving endpoint-only pin segments.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 20, 2026

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

Project Deployment Actions Updated (UTC)
schematic-trace-solver Ready Ready Preview, Comment May 20, 2026 1:34am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant