Home Forums Nazca Avoiding/fixing waveguide mismatch warnings on GDS layer 1500

Tagged: ,

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #6574


    I often get errors marked on GDS layer 1500/0 or 1500/2 from interconnected waveguides.  I think this is supposed to flag errors, but I get so many that are actually fine that I wind up turning off the GDS layer and ignoring it.  It happens the most when I draw waveguides with a cross-section instead of just a single layer.

    Some of this is when I have tapers converting from one type of cross-section to another but I don’t think that covers all of the cases.

    Is there documentation on how these warnings in the GDS work, and is there a good coding style to clean up or avoid the errors that aren’t real, so that the warnings become useful when there are only a few to sort through?

    Thanks, Jon



    Dear Jon,

    The interconnect error flags in layer 1500 can be fine tuned to have zero false positives. They are essential for design validation in my experience. That said, there is no full description I can point to yet.

    Basically, the interconnection DRC can check in pin2pin connections for xs, width, angle, radius and symmetry violations. Each of those can be fine tuned, e.g. for metal xsections it is safe to switch of width DRC, or to allow metal of xsection type-1 to connect to metal of xsection type-2.

    In case you connect two different xsections or widths on purpose, like the tapers you mention, you can use the move() method on a pin to indicate this is desired, e.g. for a Node (pin) variable p you can do p.move(width=7.0) and set up a new pin width of 7.0 for the DRC, or, similarly p.move(xs=’newxs’). This “moves” pin properties in a similar (syntax) way as moving x, y and a coordinates. A quick and dirty way is to silence all pin2pin DRC in a specific placement is to use .put(…, drc=False), but you may now hide true positives as well.


Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.