Open seveibar opened 2 months ago
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.
We can't use a full connectivity map here, we should look at all the pcb_trace
elements, see which one connects to either of the pointsToConnect
, the rewrite both the start
and goal
point to be the nearest point between the two nets
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