Output

The dock button and the Text Editor write violations into the violation list. output adds extra geometry layers. check … -> gds, dt also writes that check onto a GDS layer.

← Language overview

check … -> gds, dt

Available · yields marker GDS

check "W" "min width" : width(m1) < 0.14 um -> 200, 0

In addition to the standard marker layers of this check: output on GDS layer/datatype. Pairs become polygons.

Point markers (ongrid, dummy): a 2×2 dbu box around the point when there are fewer than 3 unique vertices. Several checks on the same gds,dt: overlay, no automatic merge in the result.

output name gds, dt

Available · yields GDS layer

output dummy 99, 0
output m1 gds, dt
output dummy gds 99, dt 0

Writes the layer (fill, helper geometry) into the result GDS, not as a violation, as long as no check runs on it. Bare numbers set layer and datatype. gds, dt copies both from the input() of that layer. gds 99, dt 0 is the same pair with labels.

output m1 gds, dt needs a binding that goes back to input(gds, dt), otherwise a parse error. An empty layer: no shapes on the target layer. Edges are polygonized like other outputs.

output name "kat" "text"

Available · yields report

output nar "width" "too narrow"

Report category for a layer (text). The geometry stays the layer.

Without a check this is not a violation record, only an annotated layer.

report / target

Available · yields files

report "file.rdb"
target "out.gds"

report and target write a marker GDS (result layers plus violation polygons), except when the path ends in .rdb: then KLayout RDB XML (µm coordinates, one category per rule). Relative paths are resolved against the deck baseDir.

Both paths may be set; an identical path is written once. .rdb (any case) selects the RDB format; any other extension stays marker GDS.