copper module#
Collect copper: routed traces, pours, and deliberate cross-net bridges.
Vias and pads are opaque to the query here; their copper is padstacks.py’s. OverlappableCopper is opaque too, and for a different reason: it is not a Copper subclass but a SingleLayerFeature with a registered transformer to Copper, so a plain query flattens it and the exporter can no longer tell a declared net tie from a short. The distinction has to survive the query, because two separate decisions depend on it - whether a cross-net contact is an intentional bridge, and what net set the resulting copper declares.
- CONDUCTOR = ('.AperFunction', ('Conductor',))#
conductive copper, pours included. A region takes its aperture attributes from the dictionary as it stands at G36, which is how a pour carries one at all.
- Type:
5.6.10
- ETCHED_COMPONENT = ('.AperFunction', ('EtchedComponent',))#
copper that deliberately joins two nets, “the net names are different on both sides”. A net tie, exactly. It is the mechanism that changes the connectivity CAM computes, which is why a tie has to survive as its own object rather than being merged into what it bridges.
- Type:
5.6.13.1
- class CopperPlan(pieces=dict(), strokes=dict())[source]#
Bases:
objectPer-conductor copper, before the region analysis runs.
- Parameters:
- collect(design, model, nets)[source]#
Walk the design’s copper into a per-layer plan.
- Return type:
- Parameters:
design (RuntimeDesign)
model (LayerModel)
nets (NetResolver)