-
Notifications
You must be signed in to change notification settings - Fork 5
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
Goal Boxes #65
Comments
This evaluation could be done inside of core if it preselected the points, but that wouldn't allow us to benchmark, so i think the method should at least be exposed here |
Here are some pull requests that might be helpful reference for this task: |
This might have already been done via: introduce alternative goal box functions. |
SimpleRouteJson
to support having alternative goals in pointsToConnect
We can't use a full connectivity map here, we should look at all the |
This might be a duplicate of: Orchestrators for nearest alternative goals. |
This might have already been done via: Alternative Goal Boxes Part 2/3 (math utilities, calculation of goal boxes, snapshot "worst case" example to fix). |
This might have already been done via: finish goal box implementation (net shortcuts). |
This might have already been done via: enable goalbox optimization. |
When routing, we can evaluate if there's a better goal for a point. This could also be done via an orchestrator that runs a couple short autoroutes
The text was updated successfully, but these errors were encountered: