On 4/1/2011 6:56 PM, DJ Delorie wrote: > >> * bloat or reduce those shapes by a certain amount, > > PCB does it this way. The biggest problem is, a drc violation doesn't > always mean you know *where* it happened. If you actually measure > distances between objects, you know exactly where the violation > happens.
I'd suggest looking for papers on how the DRC checkers for IC verification work. I've not looked but I expect that magic (the program) has some sort of DRC and you may be able to find references there. The reason I suggest this is that presumably those algorithms will be plenty fast since they are designed to work on layouts which should be much more complex than even a complicated board. -Dan ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Gerbv-devel mailing list Gerbv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gerbv-devel
