0hmx - Why do we not use something like path pa...
Why do we not use something like path path-finding algo (say a* or something else) and add constraints like 90-degree turns only, and the minimum amount of turns! use rules to get the behavior we want! I do not have much knowledge in circuit design so this could be a dumb question just curious to know the answer
5 Replies
Yes this is how most people build an initial autorouter. The issue is that autorouters connect hundreds of different traces, and if you route a trace you may find it blocks another trace. I've found that something more complex is necessary
Maybe I will try to make an experimental version of this just to see if this could be done! Do not have a plane right now let see where this goes!
sg, it's a very good way to learn. Our high density autorouter uses sequential A* path finders
Ooo, then why does https://github.com/tscircuit/schematic-trace-solver use the elbo generation and manipulation algorithm, I was talking in reference to this. I think something like A* would help here also!
we previously used a schematic trace solver that used A, the issue is 1) it's slow 2) the traces aren't aesthetic
schematic trace solver solves for the simplest traces, if a trace has too many bends we intentionally don't show it
Something important: A is a search algorithm, not just a pathfinding algorithm, so we can use A* without forming a slow "discrete grid"