Adam McCaughan

Interesting, if it works flattened that suggests it's not an issue with the routing, but just a more common integer-precision error. If you save the GDS with a precision of...

How do you avoid this exactly? I assume you can snap the port itself to the grid, but when you allow arbitrary rotations (e.g. not just 90/180/270 manhattan rotations), integer...

Unless I'm mistaken, these types of rounding errors are entirely unavoidable when working with floating point (as in gdspy/phidl)->integer conversions (as in the .gds format). Changing the amount of rounding...

That's an interesting point, I see how it could be bad that you're essentially doing a 2-stage rounding process when you convert local polygons *and then* references to integer units....

I like the idea of a more robust hashing algorithm, but can you explain what's different here? As far as I can tell, the only difference is that it's using...

Hey @joamatab , I finally got around to looking at this. Can you explain the concept behind allowing the orientation to be None? Is it just for cases where you...

This fails for the following code: ```python from phidl import Device D = Device() D.add_port(name = 1, orientation = None) D2 = Device() d1 = D2

Yes, in [phidl](https://github.com/amccaugh/phidl/) the default font used is DEPLOF (originally made by David Elata at Technion to avoid issues like this, and also prevent any floating islands which causes issues...

Thanks for taking a look at this @tvt173 ! Just as a warning, I'm not likely to have a lot of time to work on this myself in the near...

That's good to hear about the reading/writing GDSII files, I could definitely imagine that being a whole lot faster. What's really interesting to me though is the possibility of speeding...