Skip to main content

Module layermap

Module layermap 

Source
Expand description

Layer mapping file (.layermap / .map / .lyp shorthand).

IP integration always goes through a layer-name translation step: foundry A’s “M1” might be (layer=10, datatype=0) while foundry B ships the same metal as (layer=68, datatype=20). A LayerMap captures the mapping so layouts can be re-keyed without manual editing.

The format we read/write is the de-facto industry plaintext form:

# comment
METAL1   drawing  10  0
METAL1   pin      10  1
METAL1   label    10  2
VIA12    drawing  68  0

Each entry is <name> <purpose> <layer> <datatype>. purpose is a free-form string (drawing, pin, label, text, boundary, …); convention varies by foundry. Unknown purposes are preserved.

Calibre/SVRF style maps and KLayout .lyp XML files are not v1 targets — those carry display metadata (color, fill) on top of the mapping and would warrant their own crates.

Structs§

LayerMapEntry
LayerMapping

Enums§

LayerMapError

Functions§

parse_layermap
write_layermap