Open
Conversation
- Added SameNetSegmentMergingSolver to merge close same-net trace segments - Integrated into SchematicTracePipelineSolver pipeline - Added demo page SameNetSegmentMergingDemo.page.tsx - Merges collinear segments within 0.5 unit threshold
…same Y or same X)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Author
|
100% bounty claim |
|
Hey @mitchellecm7 ! We have stopped the bounty program. But we do sponsor people. For more information about this, look into the docs, you can alos join our discord. |
Author
|
@rushabhcodes but did I pass the bounty, and also you do sponsor people? The docs and discord Link |
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
2 participants
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.
Fix: Merge same-net trace lines that are close together (#34)
/claim #34
Problem
When multiple traces on the same net are routed in parallel, the
TraceOverlapShiftSolveroffsets them slightly to avoid exact overlap.This results in visually redundant near-duplicate lines that should
render as one.
Solution
Added
mergeCloseParallelSegmentsutility that:globalConnNetIdthresholddistance in Y,and their X-intervals overlap → snaps both to midpoint Y
thresholddistance in X,and their Y-intervals overlap → snaps both to midpoint X
0.1schematic units (configurable)Integrated into
TraceCleanupSolverso it runs automatically in the pipeline.Demo
Before: (two separate parallel same-net traces):
After: (merged to same Y):
the UI video link
correct.mp4
Files Changed
lib/utils/mergeCloseParallelSegments.ts— core merge utilitylib/solvers/TraceCleanupSolver/TraceCleanupSolver.ts— integrate merge passsite/SchematicTracePipelineSolver/MergeSameNetTraces.page.tsx— demo fixturetests/mergeCloseParallelSegments.test.ts— unit testsTests