You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm planning on trying MicroPather out as part of a circuit board autorouter. On a PCB, a given area can only be used by a single trace. So I would like to be able to use a single graph that represents the PCB, and run MicroPather multiple times on it, once for each required trace. Each time a trace is found, I would then need to remove the nodes used by that trace from the graph.
For performance, I would like to avoid having a second representation of the PCB where I keep track of which areas have been used in previous traces, since, I think, that would require me to generate a new graph and nodes for each trace.
Can MicroPather be used in this way?
I've done some successful experiments with MicroPather for my stripboard autorouter, so I'll probably try it first, even if I do have to regenerate the graph from a separate representation for each trace.
The text was updated successfully, but these errors were encountered:
I'm planning on trying MicroPather out as part of a circuit board autorouter. On a PCB, a given area can only be used by a single trace. So I would like to be able to use a single graph that represents the PCB, and run MicroPather multiple times on it, once for each required trace. Each time a trace is found, I would then need to remove the nodes used by that trace from the graph.
For performance, I would like to avoid having a second representation of the PCB where I keep track of which areas have been used in previous traces, since, I think, that would require me to generate a new graph and nodes for each trace.
Can MicroPather be used in this way?
I've done some successful experiments with MicroPather for my stripboard autorouter, so I'll probably try it first, even if I do have to regenerate the graph from a separate representation for each trace.
The text was updated successfully, but these errors were encountered: