Skip to content

Enable Hypergraph Auto‑Baked Tile Selection in FixedTopology Solver by Removing Hardcoded Via Tile and Via Diameter Overrides#661

Merged
seveibar merged 1 commit intotscircuit:mainfrom
AnasSarkiz:main
Mar 13, 2026
Merged

Enable Hypergraph Auto‑Baked Tile Selection in FixedTopology Solver by Removing Hardcoded Via Tile and Via Diameter Overrides#661
seveibar merged 1 commit intotscircuit:mainfrom
AnasSarkiz:main

Conversation

@AnasSarkiz
Copy link
Copy Markdown
Member

The FixedTopology high-density path was still forcing legacy via-tile/via-diameter behavior, which reduced alignment with hypergraph’s auto baked-tile selection.

This PR removes those overrides and standardizes FixedTopology routing on auto tile selection:

  • Removes manual viaDiameter handling from FixedTopologyHighDensityIntraNodeSolver.
  • Removes hardcoded/default via-tile plumbing and uses createConvexViaGraphFromXYConnections(inputConnections) in single-arg auto mode.
  • Sets route viaDiameter from actual routed vias, with generated via-tile diameter as fallback.
  • Removes viaDiameter passthrough from HyperSingleIntraNodeSolver when using FixedTopology mode.

Result: FixedTopology now consistently uses hypergraph’s internal baked auto-tile flow with cleaner, non-duplicated solver configuration.

…y Removing Hardcoded Via Tile and Via Diameter Overrides
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 13, 2026

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

Project Deployment Actions Updated (UTC)
capacity-node-autorouter Ready Ready Preview, Comment Mar 13, 2026 1:50pm

Request Review

@tscircuitbot
Copy link
Copy Markdown

🏃 Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [solver-name|all] [scenario-limit] --concurrency <n> --effort <n>

Examples:

  • /benchmark -> AutoroutingPipelineSolver, all scenarios (default concurrency uses the benchmark runner CPU count)
  • /benchmark AutoroutingPipelineSolver -> one solver, all scenarios
  • /benchmark all 20 -> all solvers, first 20 scenarios
  • /benchmark AutoroutingPipelineSolver 20 --concurrency 8 -> one solver, 20 scenarios, 8 workers
  • /benchmark AutoroutingPipelineSolver 20 --effort 2 -> one solver, 20 scenarios, 2x effort

Any PR whose title contains [BENCHMARK TEST] will automatically run the benchmark workflow on PR updates.

@AnasSarkiz
Copy link
Copy Markdown
Member Author

/benchmark

@tscircuitbot
Copy link
Copy Markdown

tscircuitbot commented Mar 13, 2026

🏃 Autorouting Benchmark Results

📊 PR Results
Benchmark Results (1x effort)

+---------------------------+----------------+--------------------+-----------+----------+----------+
| Solver                    | Completed %    | Relaxed DRC Pass % | Timed Out | P50 Time | P95 Time |
+---------------------------+----------------+--------------------+-----------+----------+----------+
| AutoroutingPipelineSolver | 88.6% (🕒3.8%) | 1.9% (🕒3.8%)      | 4/105     | 6.8s     | 76.7s    |
+---------------------------+----------------+--------------------+-----------+----------+----------+

Scenarios: 105
📊 Main Branch Results
Benchmark Results (1x effort)

+---------------------------+----------------+--------------------+-----------+----------+----------+
| Solver                    | Completed %    | Relaxed DRC Pass % | Timed Out | P50 Time | P95 Time |
+---------------------------+----------------+--------------------+-----------+----------+----------+
| AutoroutingPipelineSolver | 88.6% (🕒2.9%) | 1.9% (🕒2.9%)      | 3/105     | 8.1s     | 68.4s    |
+---------------------------+----------------+--------------------+-----------+----------+----------+

Scenarios: 105

📦 Artifact: https://github.com/tscircuit/tscircuit-autorouter/actions/runs/23053852028

@seveibar seveibar merged commit ed8caa1 into tscircuit:main Mar 13, 2026
13 checks passed
@tscircuitbot
Copy link
Copy Markdown


Thank you for your contribution! 🎉

PR Rating: ⭐⭐⭐
Impact: Major

Track your contributions and see the leaderboard at: tscircuit Contribution Tracker


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.

3 participants