Application Readiness Checker Form

Use the Application Readiness Checker form to run the application readiness check and updates for the specified applications.

Application Readiness Checker improves the process of checking and updating the layout from the schematic and provides a one-to-one correspondence between the checks and updates. You can choose the checks you want for different applications. You can also extend the checks by registering SKILL-based check and update tests. The custom functions can return markers that can be annotated and displayed in Annotation Browser. The messages in the markers are included in the Application Readiness Checker report.

For LVS-complete designs, the tool automatically updates the schematic and layout correspondence to the best match before running the checks and updates.

Field	Description
Cellview	Name of the target library or layout cellview to check and update.
	Opens the Save Preset form that lets you save the Application Readiness Checker form data in a file at the specified path.
	Opens the Load Preset form that lets you load the file that has the Application Readiness Checker form data saved.
This section lists the applications to check and update. You can choose to only check or check and update.
Application	Name of the application to check and update. Schematic v layout check is selected by default. Environment variable: lxcuApp
Check	Specifies whether to check the specified application. Supported applications: Design Planner, Electrical Aware Design, Innovus, RF Solution, Schematic vs Layout, Voltage Dependent Rules. The default in Schematic vs Layout.
Update	Specifies whether to update the specified application. Supported applications: Design Planner, Electrical Aware Design, Innovus, RF Solution, Schematic vs Layout, Voltage Dependent Rules. The default in Schematic vs Layout. Environment variable: lxcuUpdate
This section lists the check and update options.
Binder	Specifies the type of binding to perform during update. Rebind lets you reconsider the current binding and check if it is possible to get a better result by starting from scratch. Current uses the existing binding. This is the default. LVS rebinds using the binding information in the `svdb` directory. Environment variable: lxcuBinder
Layout State	Specifies the type of rebinding and layout update to perform. Partial does not clear logical connectivity during rebinding. This is the default. Complete performs hierarchical rebinding and clears all the logical connectivity. Unbound or ungenerated instances, terminals, or nets are not updated. LVS binding is allowed only when this option is specified. Environment variable: lxcuLayoutComplete
Cross Reference	Specifies the path to the instance cross-reference file (`.ixf`) that is created in the `svdb` directory of the LVS run directory. In PVS, you need to enable the `svdb` creation using Create Quantus Input Data option. If the LVS instance cross-reference file is specified, the binder uses the specified file to improve the bindings across the schematic and the layout. If any mismatched instances are encountered while parsing the`.ixf` file, the instances are ignored. Environment variable: lxcuSvdbPath
Netlist	Specifies the path to the LVS `.net` or `.spi` extracted netlist file from the layout that is created in the `svdb` directory of the LVS run directory. In PVS, you need to enable the `svdb` creation using Create Quantus Input Data option.
LVS Scale	Specifies the input scale. The rules file input_scale is required only if input_scale is different from the layout DBUPerUU. The input_scale value can be found in the `Gds_Map` statement of the `.gds.map` file in the `svdb` directory. This value is the key for device correspondence. Environment variable: lxcuSvdbScale
Extract	Specifies whether the layout needs to be extracted. This option is deselected by default. Environment variable: lxcuExtract
This section lets you specify the scope of the check and update operation.
Scope	Specifies the scope of the check and update operation. Current cellview runs the checks and performs an update on the current cellview. This is the default. Selected set runs the checks and performs an update on the objects in the selected set. All cells in design runs the checks and performs an update on all cells in the specified cellview. Environment variable: lxcuAllCellsInDesign All cells in library runs the checks and performs an update on all cells in the specified library. Environment variable: lxcuAllCellsInLibrary
Cells without schematic	Runs the checks and performs an updates on layout cells without a schematic connectivity reference. This option is deselected by default. Environment variable: lxcuWithoutSchematic
Exclude Cells	List of cells to be excluded when the All cells in design or All cells in library option is specified. Environment variable: lxcuExcludeCells
Include Cells	List of cells to be included when the All cells in design or All cells in library option is specified. Environment variable: lxcuIncludeCells
Leaf Cells	List of cells to be treated as leaf cells. Only the terminals of leaf cells are checked when the All cells in design or All cells in library option is specified. Environment variable: lxcuLeafCells
Filter Messages	List of messages to be filtered from the check and update report. Environment variable: lxcuFilterMessage
This section provides reporting options.
Open CAS workspace	Specifies whether to open the CAS workspace. This option is selected by default. See Workspaces in Layout XL. Environment variable: lxcuOpenWorkspace
Create HTML report	Specifies whether to create an HTML report. This option is selected by default. Environment variable: lxcuCreateHTMLReport
Open HTML report	Specifies whether to open the HTML report in the default browser or to issue the messages in the CIW. This option is deselected by default. Environment variable: lxcuOpenHTMLReport
Log file	Specifies whether to save the report to a text log file. This option is deselected by default. Environment variable: lxcuLogFile
Log File Directory	Specifies a directory for the log file. Environment variable: lxcuLogFileDirectory
	Expands the Application Readiness Checker form to display the Check and Update pane.

Filter	Specifies the criteria to filter the information for Category, Check, Update, and Severity columns. You can filter by typing in the text box of the respective column. You can use the right click shortcut menu to specify the criteria for filtering. For example, you can choose to filter All Of The Words, Any Of The Words, The Exact Phrase, or None Of The Words. The following image shows all the options available to specify the criteria for filtering.
	This option retains the history of your settings, which means that the filtering criteria you specify is retained next time you open the Application Readiness Checker form.
	Examples Filter by Category:
	Filter by Severity type Error.
Category	Specifies the focus areas of the design that need to be checked and updated for the selected application. Right-click in this column for the following options: Expand All to display all the categories. Collapse All to collapse all the categories. The following checks can be run when Schematic v Layout is selected: Complex checks if multiple-to-one or multiple-to-multiple devices bound together in the layout are corresponding to the multiple devices in the schematic. Example of such a device is mosaic, which is considered a single device. If the check returns true or confirms that the layout to schematic binding for such devices exists, it means that the devices are not mapped in a one-to-one correspondence. Connectivity checks for differences in logical connectivity between the schematic and layout views.
	Design Intent checks if the design intent is up-to-date. Direction checks if the terminals in the schematic and layout have the same direction (input, output, or inout). Dummy identifies the devices as a dummy (shorted drain source and gate to the same net). Master checks if the physical binding master specified in CPH is being used in the layout view. Name checks for name differences between the schematic and layout views. Net Expression checks for different or missing net expressions between the schematic and layout views. Opens checks for the incomplete nets in the layout, which are visible on the Connectivity tab of the Annotation Browser assistant. Parameter checks for the parameter differences between the schematic and layout devices. Shorts checks for shorts in the layout, which are visible on the Connectivity tab of Annotation Browser. Signal Type checks for different signal types, such as signal, analog, power, ground, tieHigh, and tieLow, between the schematic and layout nets. Unbound checks for the extra instances or terminals in the layout that do not have correspondence in the schematic. Ungenerated checks for the missing instances or terminals in the layout that exist in the schematic.
Check	Specifies whether to run the selected check on the application. Right-click in this column for the following options: Expand All to display all the categories. Collapse All to collapse all the categories. Set All On to select all the check and update options available. Set All Off to clear all the check and update options.
Update	Specifies whether to update the selected application. Right-click in this column for the following options: Expand All to display all the categories. Collapse All to collapse all the categories.
Severity	Specifies the severity level of any messages generated by the check. Right-click in this column for the following options: Expand All displays all the categories. Collapse All collapses all the categories. Set All as Error sets severity level of all checks to error. Set All as Warning sets severity level of all checks to warning. Set All as Info sets severity level of all checks to Info.

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