Skip to content

Honor declared pad clearance in differential-pair post-processing - #64

Open
seveibar wants to merge 1 commit into
mainfrom
fix/post-processing-pad-clearance
Open

Honor declared pad clearance in differential-pair post-processing#64
seveibar wants to merge 1 commit into
mainfrom
fix/post-processing-pad-clearance

Conversation

@seveibar

@seveibar seveibar commented Sep 5, 2026

Copy link
Copy Markdown

Summary

  • Accept an optional minTraceToPadEdgeClearance and propagate it through routing, simplification, length matching, and final copper validation.
  • Preserve the legacy trace-width-based margin when callers omit the setting.
  • Add the failing SOIC differential-pair geometry from feat: use Pipeline 9 as the default autorouter core#3654 as a regression: the declared 0.1 mm clearance must not be rejected using a 0.15 mm trace-width margin.

Validation

  • 82 tests passed (857 assertions), including existing visual snapshots.
  • TypeScript and structural checks passed (existing advisory folder warnings).
  • Core differential-pair endpoint, skew, and trace DRC assertions pass with this fix and the autorouter forwarding the declared clearance.

Supports tscircuit/core#3654.

@vercel

vercel Bot commented Sep 5, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
differential-pairs-solver Ready Ready Preview Sep 5, 2026 6:17am UTC

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