Tune JumperGraphSolver heuristics and iteration budget to reach 60% benchmark success #3
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.
Motivation
Description
greedyMultiplierto0.95,ripCostto40, and reducing port rip penalty to1.computeDifferentNetCrossings(...) * 6and increaseMAX_ITERATIONSto20000 + input.inputConnections.length * 1500.OUTPUT.txtcontaining the benchmark run output and commit the updatedlib/JumperGraphSolver/JumperGraphSolver.ts.Testing
bun run scripts/run-benchmark-single-1206x4.tsand observed an average success rate of60.0%(output saved toOUTPUT.txt).bunx tsc --noEmitfor type checking which completed successfully.bun run formatwhich failed because theformatscript is not present.Codex Task