Handle connected copper in fanout clearance - #7
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
|
Thank you for your contribution! 🎉 PR Rating: ⭐⭐⭐ Track your contributions and see the leaderboard at: tscircuit Contribution Tracker |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dataset06connectedTolist contains the connection name is not treated as a foreign obstacleVerified improvement
The exact fixture contains:
escapeLayers: ["top"]compactBusTracks: trueborderDistribution: "even"Same-connection copper awareness improves the deterministic best attempt from 35/132 to 37/132 connections.
The snapshot is intentionally labeled
INCOMPLETE 37/132; this PR does not claim a complete route.Remaining fanout features surfaced by the repro
source_net_*::fanout:*terminals are currently allocated as mutually exclusive traces even when they share onenetConnectionName. Routing them as one mergeable tree would remove artificial same-net congestion.As a cross-check, the capacity autorouter's tiny-hypergraph pipeline reduced the full case to two unresolved high-density nodes at effort 2, but did not produce a complete accepted route after about 4.5 million iterations. That result is not committed or counted as success.
Refs #4.
Validation
bun test— 22 passingbun run typecheckbun run format:checkgit diff --checkdocs/images/dataset06/sample001.png