use copper-pour-aware rectdiff regions for rv1106 pathing - #2536
use copper-pour-aware rectdiff regions for rv1106 pathing#2536mohan-bee wants to merge 12 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Benchmark This PRRun benchmarks by commenting on this PR: Comment Everything after Use Any PR whose title contains |
9b0c27c to
72b030e
Compare
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
e01c2f1 to
c3ddd13
Compare
c3ddd13 to
a55d383
Compare
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 1 improved, 3 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (4 partial, including failed or timed-out samples).
Changed outcomes (4)
Workflow: View run |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsThe paired benchmark ended with cancelled before both reports were produced. Workflow: View run |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
|
/benchmark-all --pipeline 9 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 85/85 samples (0 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 85/85 samples (0 partial, including failed or timed-out samples).
Workflow: View run |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
|
/benchmark --pipeline 9 --dataset srj18 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
seveibar
left a comment
There was a problem hiding this comment.
Based on the video i dont think this is conceptually valid
there is no way to merge overlapping free nodes that dont have the exact same bounds without shrinking to only the overlap area and stitching across the remaining, or forming new nodes where the overlapping area becomes a multilayer and subtracted from the others- in which case this should be part of whatever solver does node construction
|
/benchmark-all --pipeline 9 --same-machine |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 85/85 samples (0 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 85/85 samples (0 partial, including failed or timed-out samples).
Workflow: View run |
Same Machine Benchmark ResultsBoth revisions ran sequentially in one Blacksmith job on Dataset:
Outcome changes: 0 improved, 0 regressed. DRC issues are totaled across solved samples. Timing percentiles include solved and timed-out samples; negative timing deltas are faster. Main pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
PR pipeline stage timingsAutoroutingPipelineSolver9_PreloadedTraceGraph Recorded timings: 16/16 samples (3 partial, including failed or timed-out samples).
Workflow: View run |
Motivation
Before
After
30ebd720b25c0c4264de2c1ee58200f18b25beb4, refresh the same full-board pathing snapshot, and retain the 30-second pathing assertion. The focused local test passed in 15.4 seconds, including snapshot checking; this is not a same-machine benchmark claim.