updateSchParamWithEvalValue

layoutXL updateSchParamWithEvalValue boolean { t | nil }

Description

Updates the schematic parameter value with the layout parameter value, when the two values are found to be different during evaluation. The mismatch is also reported by the Check – Against Source command.

The default is t. For information about the behavior of the environment variable when set to nil, see Additional Information.

GUI Equivalent

Command:

Options – Connectivity (Update tab)

Field:

Update schematic parameter expressions with evaluated value

(Connectivity Form)

Examples

envGetVal("layoutXL" "updateSchParamWithEvalValue")

envSetVal("layoutXL" "updateSchParamWithEvalValue" 'boolean t)

envSetVal("layoutXL" "updateSchParamWithEvalValue" 'boolean nil)

Additional Information

When the updateSchParamWithEvalValue environment variable is set to nil, the value of the schematic parameter is not updated to that of the layout parameter, even if the two evaluated values are found to be different and the schematic parameter is defined as an expression. The Check – Against Source command continues to report the parameter mismatch.

Let us consider an example. Let us assume that after an evaluation of the parameters, where needed, the schematic and the layout parameter values are found to be as displayed in the table below.

Schematic Parameters Layout Parameters

w = “3u”

w = “4u”*

* Value changed by the designer in the layout

width = iPar(“w”)

width = “3u”

With the updateSchParamWithEvalValue environment variable set to t (default), the schematic parameter values will be updated to match that of the layout:

w = “4u”

width = “3u”

To ensure that a schematic parameter value is not updated to match the corresponding layout value even when the updateSchParamWithEvalValue environment variable set to t, add the parameter to the list of parameters to ignore for check (paramsToIgnoreForCheck) or manually edit the parameters to match the layout counterparts.

With the updateSchParamWithEvalValue environment variable set to nil, the schematic parameter values will continue to be:
w = “3u”
width = iPar(“w”)
When updateSchParamWithEvalValue is set to nil and lxEvalCDFCallbacks is set to t, all the callbacks are fired as usual after the schematic parameters that need an update (other than the ones that are defined as expressions) are updated.
- It is assumed that the CDF callbacks are written such that they are compatible with any use of AEL expressions.

Conditions that Trigger Evaluation of Schematic Parameters

Schematic parameters (or properties) are considered for evaluation if:

The shell environment variable, CDS_Netlisting_Mode, is set to Analog. Else, the schematic parameter expression, such as iPar(“w”), is treated as a regular string and updated based on the value of the layout string, if the values across the two views are found to be different.
If the parameter is a CDF parameter and parseAsCEL is set to yes
- a schematic parameter that only has parseAsNumber = yes and parseAsCEL = no is not considered as an evaluated parameter.
If the parameter (or property) is an NLP expression, the parameter (or property) is always considered as evaluated, regardless of the value of the CDS_Netlisting_Mode environment variable.
If the property is a string (not a CDF parameter) and the evaluated value is different from the unevaluated value.
If the property is an ilExpr.

Virtuoso Layout Suite XL: Connectivity Driven Editing User Guide
Product Version IC23.1, November 2023