pdaOPSoffsetLayer
Offset layer.This is a complex operation that creates an offset contour for the list of In layers. Different grow shapes can be used, detault is ellipse.
You can use the elements doc and tex to document the operation. This is often useful for later changes as the logic behind complex chains of operations is often not easy to follow by colleques and/or partners.
Sub elements:
In is the list of input layers.
dist is the distance for the offset (in um), default 0.1.
how defines the style (ellipse, miter, rectangle).
Structure
This element does not have attributes. The elements are shown below, in a sorted per type fashion.In case a list is printed after an element, it indicates that you can have many, otherwise it should be a single element. With a optional it tells the element is not required.
<pdaOPSoffsetLayer> ...
<In> ... </In>
<dist> ... </dist> optional
<doc> ... </doc> optional
<groupRef> ... </groupRef> list
<how> ... </how> optional
<markup> ... </markup> list
<tex> ... </tex> list
<ticket> ... </ticket> list
</pdaOPSoffsetLayer>
XSD The schema file can be downloaded or viewed at xPDK_Layout.
Details
In
Reference a list of gds/app layers. This list is used as input for the operation. Type pdaGDSlayerReferenceList documentation:dist
Define the offset in um.doc
Type pdaDocumentation documentation:This field allows some (short, single line) documentation to be written. It can be a long string, but the idea is not to replace a design manual.
This field is like
tex
which allows documentation in LaTex format; doc
is restricted to plain text.groupRef
Type groupRef documentation:how
Different grow shapes determine the outer contour. Type pdaOPSoffsetLayerSelection documentation: Define the offset operation.markup
Type pdaMarkupDocumentation documentation: actual html.tex
Type pdaTexDocumentation documentation:doc
, but tex can be a long text in LaTex format to
document the layer in more detail if needed.You can document anything relevant for the topic you want to define.
Multiple paragraphs is fine. Format is Latex, so more complex content is possible.