- 
                Notifications
    You must be signed in to change notification settings 
- Fork 18
Add hyper-tuned capacity pathing for assignable via pipeline - first working solver for global planning with assignable vias against viagrid test #293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| The latest updates on your projects. Learn more about Vercel for GitHub. 
 | 
…rove obstacle and used node filtering logic and update visualization steps fix pathfinding to exclude nodes containing obstacles unless they contain targets and exclude already used nodes early remove large cost penalties for reused nodes in cost and heuristic calculations to simplify logic enhance visualization by adding green lines for solved subpaths and update stroke colors and step numbering for clarity
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| onSolved: (cms) => { | ||
| const winningSolver = cms.initialPathingHyperSolver?.winningSolver | ||
| if (winningSolver) { | ||
| // cms.initialPathingSolver = winningSolver | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
  Propagate hyper-solver winner to initial pathing solver
The hyper-parameter step constructs initialPathingHyperSolver but the onSolved handler never assigns its winningSolver to initialPathingSolver. As a result initialPathingSolver stays undefined and the following pathingOptimizer step falls back to a default greedy solver instead of using the tuned directive solver. The regression test added in this commit also asserts that winningSolver equals initialPathingSolver, so leaving this assignment commented out causes the test (and the pipeline’s downstream visualization) to fail and the hyper search has no effect.
Useful? React with 👍 / 👎.
| Thank you for your contribution! 🎉 PR Rating: ⭐⭐⭐ Track your contributions and see the leaderboard at: tscircuit Contribution Tracker Comment posted by tscircuitbot | 
Summary
Testing
https://chatgpt.com/codex/tasks/task_b_6901bf9173f4832e858ecc6df1169a24