Skip to content

Reproduce sample 4 duplicate-port overcapacity - #135

Draft
ShiboSoftwareDev wants to merge 2 commits into
mainfrom
agent/repro-duplicate-port-physical-capacity
Draft

Reproduce sample 4 duplicate-port overcapacity#135
ShiboSoftwareDev wants to merge 2 commits into
mainfrom
agent/repro-duplicate-port-physical-capacity

Conversation

@ShiboSoftwareDev

Copy link
Copy Markdown
Contributor

What this reproduces

The congested-port prepass can turn one graph opening into more physical lanes than the opening can carry.

This fixture uses the real dimensions of a sample 4 opening: it is 0.396 mm tall. With a 0.1 mm trace and 0.1 mm trace clearance, only two lanes fit. The current prepass creates seven lanes inside a fixed 0.05 mm band.

Snapshot

Seven overlapping lanes in the sample 4 opening

  • Blue rectangles are the two real graph regions on either side of the opening.
  • Red bands are the physical 0.1 mm traces.
  • Orange bands show the required 0.2 mm center-to-center pitch.
  • Black dots are the graph port centers.

The overlapping red/orange bands make the bug visible: the graph advertises seven routes through space that can carry only two.

Scope

This PR adds only the focused fixture and SVG snapshot. The fix is stacked separately so the same test naturally changes from the invalid seven-lane output to the legal two-lane output.

@vercel

vercel Bot commented Aug 2, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
tiny-hypergraph Ready Ready Preview Aug 2, 2026 4:09am

Request Review

@tscircuitbot

Copy link
Copy Markdown

Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [benchmark.sh args...]
/benchmark --dataset <hg07|srj18> --limit <n> --solver <core|poly> --families <default|default+deep|all> --concurrency <n|auto>

Everything after /benchmark is forwarded directly to ./benchmark.sh.
The result comment shows the matching dataset from the latest stored main-branch benchmark artifact beside the PR run; main is not rerun for each PR benchmark request.

Examples:

  • /benchmark -> hg07, all samples, core solver
  • /benchmark --dataset srj18 --limit 20 -> first 20 srj18 samples
  • /benchmark --dataset srj18 --concurrency auto -> srj18 samples with runner CPU-count concurrency
  • /benchmark --sample sample002 -> one hg07 sample
  • /benchmark --limit 20 --solver poly -> first 20 hg07 samples with the poly solver
  • /benchmark --limit 40 --families default+deep -> first 40 hg07 samples with deeper candidate families

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

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.

2 participants