Circuit Check Scoping

Most circuit checks can be applied either globally to the entire design, or locally to specific blocks of a design. The scoping options are available to define the scope of each circuit check. The circuit checks can be applied to a specific subcircuit instance (inst), or all instances of a subcircuit definition (subckt). Exclusion of a specific subcircuit instance (xinst), or all instances of a subcircuit (xsubckt) is supported. All scoping options support wildcards, and the hierarchy level of the scope can be defined by the depth option.

`node`	Non-hierarchical node name. The default value is none.
`net`	Hierarchical node names between which the leakage path is checked. Wildcards are not supported. The default value is none.
`dev`	Non-hierarchical element name. The default value is none.
`model`	Non-hierarchical model name. The default value is none.
`inst`	Subcircuit instances to which the circuit check is applied. The default value is `inst=*`.
`xinst`	Subcircuit instances that are excluded from the circuit check. The default value is none.
`subckt`	Instances of the specified subcircuit to which the circuit checks are applied. The default value is `subckt=*`.
`xsubckt`	Instances of the specified subcircuit that are excluded from the circuit checks. The default value is none.
`depth`	Hierarchy level (from the top level) to be checked. For example, `depth=3` reports errors from top level plus 3 sublevels. The default value is 8.

The inst and xinst arguments can be used only to specify subcircuit instances and not device instances. Combination of inst/xinst and subckt/xsubckt is not allowed.

The following wildcards are allowed for node, dev, model, inst, xinst, subckt, and xsubckt:

* – matches any character including an empty string and . (dot)

? – matches any single character including space and . (dot)

Spectre FX Circuit Simulator User Guide
Product Version 23.1, September 2023