


















































Hacker News โข 04/05/2026 05:50 
























































|s, it's router1, if it has =s, it's router2

--router router2








synth_aegis command would be cool, it would only really need the JSON descriptor I think.
























DRT_THREADS set to the number of machine threads, and many other parts of the flow are single-threaded.
-threads $NIX_BUILD_CORES























































ERROR add_global_connections failed to make any connections for 'rst_n_pad/DVDD' to VDD. (edited)





























































































box mode and a few time the wiring mode. Never use import from spice or the other mode .....






























































































































































































































































































poly.2 about min spacing was fixable by just adding a few poly boxes; the otheres are basically via pushing though, I don't do that by hand.

















nix ps shows the klayout command has been running for 9017.5s









via.5a: via.5a : min. m1 enclosure of 0.15um via of 2 adjacent edges : 0.085um aren't as easy because e.g. that one seems to only blame the via's perimeter for that rule violation, despite it actually being the surrounding geometry on m1 that is too close. Sure, if the via wasn't minimum size it could be shrunk and if m1 would suffice then it would then resolve.
But yeah, needs better attribution of blame to the actual vertices that are too close.
@Leo Moser (mole99) your/ @Clyde Laforge 's work on the KLayout DRC refactor, does that touch the concept of attributing DRC violations to ALL the responsible source vertices, or is it orthogonal to introduction of such a concept?

via.5a: via.5a : min. m1 enclosure of 0.15um via of 2 adjacent edges : 0.085um aren't as easy because e.g. that one seems to only blame the via's perimeter for that rule violation, despite it actually being the surrounding geometry on m1 that is too close. Sure, if the via wasn't minimum size it could be shrunk and if m1 would suffice then it would then resolve.
But yeah, needs better attribution of blame to the actual vertices that are too close.
@Leo Moser (mole99) your/ @Clyde Laforge 's work on the KLayout DRC refactor, does that touch the concept of attributing DRC violations to ALL the responsible source vertices, or is it orthogonal to introduction of such a concept? via.5a with KLayout though as that just blames the edges of the via not mentioning the metal to put/extend there.
Does work for e.g. m2.2 : min. m2 spacing : 0.14um though, at least the ones that are min-distance-between-EdgePair's.


1
1













































































































1
















1












<t:1777636740:R> <t:1777636740:F> it's <t: followed by the unix timestamp then : then a letter that changes the format (R for Relative, F for full, ...) and finally close it > (edited)




2














