B

---

Verifier Environment Variables

---

This topic describes the Virtuoso ADE Verifier (Verifier) environment variables that are supported for public use and can help in customizing the default settings using the .cdsenv or .cdsinit file, or the Virtuoso CIW for a session.

To set an environment variable in the .cdsenv file, use the following format:

verifier.preferences createbatchlogfile string "YES"

To set an environment variable in the .cdsinit file or Virtuoso CIW, use the following format:

envSetVal("verifier.preferences" "createbatchlogfile" 'string "YES")

Verifier environment variables are grouped under the following family.partition:

Family.partition
Environment Variables to Set Preferences	Environment Variables to Manage Results
Environment Variables to Manage Custom Fields	Environment Variables to Manage Requirements
Environment Variables to Manage File Export	Environment Variables to Manage Verifier Runs
Environment Variables to Manage Verifier GUI Settings	Environment Variables to Manage Snapshots
Environment Variables to Manage HTML Reports	Environment Variables to Manage Session Windows
Environment Variables to Manage Implementations	Environment Variables to Manage vManager Settings

Environment Variables to Set Preferences

The following table lists the environment variables grouped under the verifier.preferences family.partition:

allowEditingDisabledState	enablecrossselection
appendDate	estRunTimeDisplayFormat
appendTime	evaluateMetricPrefix
autoCreateDataSheet	historyNamePrefix
autocreatereports	htmlReportDirectory
autoUpdateAll	impJobControlMode
batchhtmlreport	impjobpolicy
binaryName	impNetlistingJobPolicy
checkdesigninreportidenticalhistory	importDisabledTests
checksimfilesinreportidenticalhistory	impresexpperiod
createbatchhtmlreport	impuimode
createRequirementsWithNoSpec	linkdatasheets
dateTimeSuffixFormat	mappingonetoone
displayAge	numberOfRetries
displaycpk	overwritereports
displayFresh	retryTimeThreshold
displaymax	reqspecs
displaymean	reqspecscheckunits
displaymin	resultForSpaceCoverage
displayRelOutputAges	simparallelcount
displaysigmatotarget	tagsToOverrideWithVerificationSpace
displaystandarddeviation	usereportidenticalhistory
displayStress	weightedAverageForCoverage
displayyield

allowEditingDisabledState

verifier.preferences allowEditingDisabledState boolean { t | nil }

Description

Allows editing the enabled or disabled state of implementation runs or tests.

The default is nil.

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Allow editing the enabled or disabled state for implementation run or test

Examples

envGetVal("verifier.preferences" "allowEditingDisabledState")

envSetVal("verifier.preferences" "allowEditingDisabledState" 'boolean t)

Related Topics

Allow editing the enabled or disabled state for implementation run or test

appendDate

verifier.preferences appendDate boolean { t | nil }

Description

Adds the current date as a suffix to the history name.

The default is t.

GUI Equivalent

Command	Edit – Preferences – Run
Field	Append date

Examples

envGetVal("verifier.preferences" "appendDate")

envSetVal("verifier.preferences" "appendDate" 'boolean nil)

Related Topics

Append date

appendTime

verifier.preferences appendTime boolean { t | nil }

Description

Adds the current time as a suffix to the history name.

The default is t.

GUI Equivalent

Command	Edit – Preferences – Run
Field	Append date

Examples

envGetVal("verifier.preferences" "appendTime")

envSetVal("verifier.preferences" "appendTime" 'boolean nil)

Related Topics

Append time

autoCreateDataSheet

verifier.preferences autoCreateDataSheet boolean { t | nil }

Description

Creates an ADE Assembler datasheet during run or reload implementation, when it is set to t. It saves the datasheet file name with the tag dataSheetFile in the run summary data files. If the datasheet already exists, it only creates a link to the datasheet during the HTML report generation.

The default is nil, which means that the implementation datasheet does not exist and  is recreated during the HTML report generation.

GUI Equivalent

Command	Edit – Preferences – Run
Field	Create ADE Assembler datasheet at run or reload time

Examples

envGetVal("verifier.preferences" "autoCreateDataSheet")

envSetVal("verifier.preferences" "autoCreateDataSheet" 'boolean t)

Related Topics

Create ADE Assembler datasheet at run or reload time

autocreatereports

verifier.preferences autocreatereports string { "NO" | "YES" }

Description

When set to "YES", Verifier creates all the enabled reports automatically after each interactive run is completed, or when a data update process is completed after external changes were found.

The default is NO.

GUI Equivalent

Command	Edit – Preferences – Reporting
Field	Auto-create all enabled reports

Examples

envGetVal("verifier.preferences" "autocreatereports")

envSetVal("verifier.preferences" "autocreatereports" 'string "YES")

Related Topics

Auto-create all enabled reports

autoUpdateAll

verifier.preferences autoUpdateAll boolean { t | nil }

Description

Automatically updates the implementations to match the updates in the cellviews.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.preferences" "autoUpdateAll")

envSetVal("verifier.preferences" "autoUpdateAll" 'boolean t)

Related Topics

Simulation Runs Using Auto-Synced Requirements

batchhtmlreport

verifier.preferences batchhtmlreport string { "string value" }

Description

Specifies the name and location of the verification report in HTML format. If you do not specify the filename and location, and createbatchhtmlreport is set to "YES", Verifier saves the report as VerifierCellName.html in the current directory.

The default is YES.

GUI Equivalent

Command	Edit – Preferences – Reporting
Field	Create HTML Report File

Examples

envGetVal("verifier.preferences" "batchhtmlreport")

envSetVal("verifier.preferences" "batchhtmlreport" 'string "./mySimDir/latestReport.html")

Related Topics

Create HTML Report File

binaryName

verifier.preferences binaryName string { "program_name" }

Description

Specifies the external program to use when running Virtuoso with Batch Run.

The default is virtuoso.

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Executable or script for batch runs

Examples

envGetVal("verifier.preferences" "binaryName")

envSetVal("verifier.preferences" "binaryName" 'string "virtuoso")

Related Topics

Executable or script for batch runs

checkdesigninreportidenticalhistory

verifier.preferences checkdesigninreportidenticalhistory string { "NO" | "YES" }

Description

When set to "NO", Verifier does not check the schematic and configuration views of each test to detect changes. It runs the test only if changes were detected.

The default is NO.

GUI Equivalent

Command	Edit – Preferences – Run
Field	Detect design changes

Examples

envGetVal("verifier.preferences" "checkdesigninreportidenticalhistory")

envSetVal("verifier.preferences" "checkdesigninreportidenticalhistory" 'string "YES")

Related Topics

Detect design changes

checksimfilesinreportidenticalhistory

verifier.preferences checksimfilesinreportidenticalhistory string { "NO" | "YES" }

Description

When set to "NO", Verifier does not check the simulation files in the nominal run for Spectre. It runs the associated tests only if changes were detected. This check is not considered if the nominal corner is disabled.

The default is NO.

GUI Equivalent

Command	Edit – Preferences – Run
Field	Detect simulation file changes in nominal run

Examples

envGetVal("verifier.preferences" "checksimfilesinreportidenticalhistory")

envSetVal("verifier.preferences" "checksimfilesinreportidenticalhistory" 'string "YES")

Related Topics

Detect simulation file changes in nominal run

createbatchhtmlreport

verifier.preferences createbatchhtmlreport string { "NO" | "YES" }

Description

When set to "YES", Verifier generates the verification report in HTML.

The default is YES.

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Create HTML Report File

Examples

envGetVal("verifier.preferences" "createbatchhtmlreport")

envSetVal("verifier.preferences" "createbatchhtmlreport" 'string "YES")

Related Topics

Create HTML Report File

createRequirementsWithNoSpec

verifier.preferences createRequirementsWithNoSpec boolean { t | nil }

Description

When set to t, Verifier creates requirements without any specifications.

When set to nil, the Verifier Preferences option Create requirements for outputs with no specification values is turned off. Requirements are not created for expressions without any specs in the implementations pane. Additionally, no requirements are added when the shortcut menu option Create Requirement is selected in the implementations pane.

The default is t.

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Create requirements for outputs with no specification values

Examples

envGetVal("verifier.preferences" "createRequirementsWithNoSpec")

envSetVal("verifier.preferences" "createRequirementsWithNoSpec" 'boolean nil)

Related Topics

Create requirements for outputs with no specification values

dateTimeSuffixFormat

verifier.preferences dateTimeSuffixFormat string "yyyyMMdd_HHmmss"

Description

Specifies the customizable suffix format appended to the report directory name.

The suffix indicates the date and time the report is created and supports only alphanumeric characters, '.', ':', ' - ', or '_'.

The default format is yyyyMMdd_HHmmss, meaning that <currentDate_currentTime> is appended to the directory name. For example, if the current date is November 20, 2021, and the current time is 10:20:30, the dateTime suffix will be 20211120_102030.

GUI Equivalent

Command	Edit – Preferences – Reporting – HTML Report
Field	Datetime suffix format

Examples

envGetVal("verifier.preferences" "dateTimeSuffixFormat")

envSetVal("verifier.preferences" "dateTimeSuffixFormat" 'string "yyyyMMdd_HHmmss")

Related Topics

HTML Reports in Interactive Format

Reporting

displayAge

verifier.preferences displayAge boolean { t | nil }

Desciption

Enables displaying the reliability outputs for aged tests.

The default is t.

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Show reliability outputs

Examples

envGetVal("verifier.preferences" "displayAge")

envSetVal("verifier.preferences" "displayAge" 'boolean nil)

Related Topics

Show reliability outputs

displaycpk

verifier.preferences displaycpk string { "YES" | "NO" }

Description

Displays Cpk in the implementations hierarchy.

The default is "YES".

GUI Equivalent

Command	Edit – Preferences – Planning – Monte Carlo Statistical Outputs
Field	Cpk

Examples

envGetVal("verifier.preferences" "displaycpk")

envSetVal("verifier.preferences" "displaycpk" 'string "NO")

Related Topics

Monte Carlo Statistical Outputs

displayFresh

verifier.preferences displayFresh boolean { t | nil }

Description

Displays the reliability outputs for fresh tests.

The default is t.

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Show reliability outputs

Examples

envGetVal("verifier.preferences" "displayFresh")

envSetVal("verifier.preferences" "displayFresh" 'boolean t)

Related Topics

Show reliability outputs

displaymax

verifier.preferences displaymax string { "NO" | "" }

Description

Displays the Max value in the implementations hierarchy.

The default is "NO".

GUI Equivalent

Command	Edit – Preferences – Planning – Monte Carlo Statistical Outputs
Field	Max

Examples

envGetVal("verifier.preferences" "displaymax")

envSetVal("verifier.preferences" "displaymax" 'string "")

Related Topics

Monte Carlo Statistical Outputs

displaymean

verifier.preferences displaymean string { "NO" | "YES" }

Description

Displays mean in the implementations hierarchy.

The default is "YES".

GUI Equivalent

Command	Edit – Preferences – Planning – Monte Carlo Statistical Outputs
Field	Mean

Examples

envGetVal("verifier.preferences" "displaymean")

envSetVal("verifier.preferences" "displaymean" 'string "NO")

Related Topics

Monte Carlo Statistical Outputs

displaymin

verifier.preferences displaymin string { "NO" | "" }

Description

Displays the Min value in the implementations hierarchy.

The default is "NO".

GUI Equivalent

Command	Edit – Preferences – Planning – Monte Carlo Statistical Outputs
Field	Min

Examples

envGetVal("verifier.preferences" "displaymin")

envSetVal("verifier.preferences" "displaymin" 'string "")

Related Topics

Monte Carlo Statistical Outputs

displayRelOutputAges

verifier.preferences displayRelOutputAges cyclic { "All" | "Last" }

Description

Displays the reliability outputs for specified ages.

• "All" : The reliability outputs are displayed for all age points.
• "Last" : The reliability outputs are displayed for the last age point.

The default is "All".

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Show outputs for ages

Examples

envGetVal("verifier.preferences" "displayRelOutputAges")

envSetVal("verifier.preferences" "displayRelOutputAges" 'cyclic "Last")

Related Topics

Show outputs for ages

displaysigmatotarget

verifier.preferences displaysigmatotarget string { "NO" | "" }

Description

Displays the sigma to target value in the implementations hierarchy.

If there is no specification defined for the output in the maestro cellview, Verifier is not able to get the results for this SigmaToTarget value.

The default is "NO".

GUI Equivalent

Command	Edit – Preferences – Planning – Monte Carlo Statistical Outputs
Field	Sigma to Target

Examples

envGetVal("verifier.preferences" "displaysigmatotarget")

envSetVal("verifier.preferences" "displaysigmatotarget" 'string "")

Related Topics

Monte Carlo Statistical Outputs

displaystandarddeviation

verifier.preferences displaystandarddeviation string { "Yes" | "NO" }

Description

Displays standard deviation in the implementations hierarchy.

The default is "YES".

GUI Equivalent

Command	Edit – Preferences – Planning – Monte Carlo Statistical Outputs
Field	Standard Deviation

Examples

envGetVal("verifier.preferences" "displaystandarddeviation")

envSetVal("verifier.preferences" "displaystandarddeviation" 'string "NO")

Related Topics

Monte Carlo Statistical Outputs

displayStress

verifier.preferences displayStress boolean { t | nil }

Description

Displays the reliability outputs for stress tests.

The default is t.

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Show reliability outputs

Examples

envGetVal("verifier.preferences" "displaystress")

envSetVal("verifier.preferences" "displayStress" 'boolean nil)

Related Topics

Show reliability outputs

displayyield

verifier.preferences displayyield string { "YES" | "NO" }

Description

Displays yield in the implementations hierarchy.

The default is "YES".

GUI Equivalent

Command	Edit – Preferences – Planning – Monte Carlo Statistical Outputs
Field	Yield

Examples

envGetVal("verifier.preferences" "displayyield")

envSetVal("verifier.preferences" "displayyeild" 'string "NO")

Related Topics

Monte Carlo Statistical Outputs

enablecrossselection

verifier.preferences enablecrossselection string { "Yes" | "NO" }

Description

When set to "YES", you can highlight the implementation mapped with a requirement by placing the pointer over the requirement. Similarly, you can place the pointer over the implementation to highlight the mapped requirement.

The default is "YES".

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Show cross mapping at cursor

Examples

envGetVal("verifier.preferences" "enablecrossselection")

envSetVal("verifier.preferences" "enablecrossselection" 'string "NO")

Related Topics

Show cross mapping at cursor

estRunTimeDisplayFormat

verifier.preferences estRunTimeDisplayFormat cyclic { "Seconds" | "Formatted Time" }

Description

Sets the Display Estimated Run Time as option to Seconds or Formatted Time.

The default is "Seconds".

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Display Estimated Run Time

Examples

envGetVal("verifier.preferences" "estRunTimeDisplayFormat")

envSetVal("verifier.preferences" "estRunTimeDisplayFormat" 'cyclic "Formatted Time")

Related Topics

Simulation Runs based on Priority and Estimated Run Time

evaluateMetricPrefix

verifier.preferences evaluateMetricPrefix boolean { t | nil }

Description

When set to t, Verifier checks the metric prefixes for requirements. This option is hidden when the Specification Search Order is set to Implementation Specification.

The default is nil.

GUI Equivalent

Command	Edit – Preferences – General
Field	Evaluate Metric Prefix

Examples

envGetVal("verifier.preferences" "evaluateMetricPrefix")

envSetVal("verifier.preferences" "evaluateMetricPrefix" 'boolean t)

Related Topics

Evaluate Metric Prefix

historyNamePrefix

verifier.preferences historyNamePrefix string "prefix_text"

Description

Adds the specified prefix to the ADE Assembler history name.

The default is "verifier".

GUI Equivalent

Command	Edit – Preferences – Run
Field	Prefix

Examples

envGetVal("verifier.preferences" "historyNamePrefix")

envSetVal("verifier.preferences" "historyNamePrefix" 'string "verifier")

Related Topics

Prefix

htmlReportDirectory

verifier.preferences htmlReportDirectory string "./lib_cell_view"

Description

Specifies the path to the directory where the HTML report is saved.

The path can contain shell environment variables ($) and the home alias (~/).

The default is an empty string, meaning that the path is automatically set to ./lib_cell_view.

GUI Equivalent

Command	Edit – Preferences – Reporting – HTML Report
Field	Directory

Examples

envGetVal("verifier.preferences" "htmlReportDirectory")

envSetVal("verifier.preferences" "htmlReportDirectory" 'string "myVDRLppCg")

Related Topics

HTML Reports in Interactive Format

Reporting

impJobControlMode

verifier.preferences impJobControlMode cyclic { "" | "LSCS" | "ICRP" }

Description

Specifies the job control mode that must be used for all the implementation cellviews.

The valid values are:

• "" does not make any changes to the job control mode.
• "LSCS" sets the job control mode to LSCS mode.
• "ICRP" sets the job control mode to ICRP mode.

The default is "".

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Override job control mode

Examples

envGetVal("verifier.preferences" "impJobControlMode")

envSetVal("verifier.preferences" "impJobControlMode" 'cyclic "LSCS")

envSetVal("verifier.preferences" "impJobControlMode" 'cyclic "ICRP")

Related Topics

Override job control mode

impjobpolicy

verifier.preferences impjobpolicy string { "" | "Maestro Default" }

Description

Specifies the run job policy that must be used for all the implementation cellviews.

The valid values are:

• "" does not make any changes to the job policy.
• "Maestro Default" sets the run job policy to the default specified in the ADE Assembler cellview.
  
  You can define a job policy in ADE Assembler and use it as the default policy in ADE Verifier.

The default is "".

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Override simulation job policy

Examples

envGetVal("verifier.preferences" "impjobpolicy")

envSetVal("verifier.preferences" "impjobpolicy" 'string "Maestro Default")

Related Topics

Override simulation job policy

impNetlistingJobPolicy

verifier.preferences impNetlistingJobPolicy string { "" | "user_defined_job_policy" | "Netlisting Default" }

Description

Specifies the netlisting job policy that must be used for all the implementation cellviews that use the LSCS job control mode.

The valid values are:

• "" does not make any changes to the netlisting job policy.
• "user_defined_job_policy" sets the netlisting job policy that you create and specify in ADE Assembler.
• "Netlisting Default" sets the netlisting job policy to the default specified in the ADE Assembler cellview.

The default is "".

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Override netlisting job policy

Examples

envGetVal("verifier.preferences" "impNetlistingJobPolicy")

envSetVal("verifier.preferences" "impNetlistingJobPolicy" 'string "user_defined_job_policy")

envSetVal("verifier.preferences" "impNetlistingJobPolicy" 'string "Netlisting Default")

Related Topics

Override netlisting job policy

importDisabledTests

verifier.preferences importDisabledTests boolean { t | nil }

Description

Includes disabled tests, runs, or outputs while importing implementations.

The default is nil.

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Include disabled run, reliability, test, or output for implementation

Examples

envGetVal("verifier.preferences" "importDisabledTests")

envSetVal("verifier.preferences" "importDisabledTests" 'boolean t)

Related Topics

Include disabled run, reliability, test, or output for implementation

impresexpperiod

verifier.preferences impresexpperiod string { "numeric_value"}

Description

When set to any numeric value greater than 0, identifies an implementation as outdated if the results are older than the specified expiration period.

The default is "0".

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Expiration Period of Implementation Results (in days)

Examples

envGetVal("verifier.preferences" "impresexpperiod")

envSetVal("verifier.preferences" "impresexpperiod" 'string "50")

Related Topics

Expiration Period of Implementation Results (in days)

impuimode

verifier.preferences impuimode string { "NO" | "YES" }

Description

When set to "YES", Verifier runs the implementations in debug mode, where the implementation interface, such as ADE Assembler, is displayed to monitor the runs.

The default is "NO".

GUI Equivalent

Command	Edit – Preferences – Run
Field	Debug mode, open implementation interface

Examples

envGetVal("verifier.preferences" "impuimode")

envSetVal("verifier.preferences" "impuimode" 'string "YES")

Related Topics

Debug mode, open implementation interface

linkdatasheets

verifier.preferences linkdatasheets string { "YES" | "NO" }

Description

When set to "YES", Verifier creates the ADE Assembler datasheets of the implementation cellviews from their history and links the datasheets to the HTML report generated by Verifier. You can click the links in the HTML report to access the datasheets.

The default is NO, which means that the datasheets are not linked to the HTML reports.

The CDS environment variable settings are applicable only for a new Verifier cellview. For the existing Verifier cellview, Verifier reads the preferences option value from the saved cellview and not from the specified CDS environment variable.Therefore, you can enable the Link implementation datasheets to the created HTML report check box, and save the Verifier cellview to ensure that the settings are saved for reference in future.

When the linkdatasheets and useTemplate environment variables are enabled, the datasheets are saved in a new directory assembler_datasheets, which is created in the same directory as the interactive HTML report.

GUI Equivalent

Command	Edit – Preferences – Reporting
Field	Link implementation datasheets to the created HTML report

Examples

envGetVal("verifier.preferences" "linkdatasheets")

envSetVal("verifier.preferences" "linkdatasheets" 'string "YES")

Related Topics

Link implementation datasheets to the created HTML report

mappingonetoone

verifier.preferences mappingonetoone string { "YES" | "NO" }

Description

When set to "YES", Verifier ensures that a requirement can be mapped to only one implementation.

The default is "NO".

GUI Equivalent

Command	Edit – Preferences – Planning
Field	Map only one requirement to one implementation

Examples

envGetVal("verifier.preferences" "mappingonetoone")

envSetVal("verifier.preferences" "mappingonetoone" 'string "YES")

Related Topics

Map only one requirement to one implementation

numberOfRetries

verifier.preferences numberOfRetries int numeric_value

Description

Specifies the number of times a failed simulation must be retried during a run within the range 0-10.

The default is 0.

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Number of retries

Examples

envGetVal("verifier.preferences" "numberOfRetries")

envSetVal("verifier.preferences" "numberOfRetries" 'int 10)

Related Topics

Number of retries

overwritereports

verifier.preferences overwritereports string { "NO" | "YES" }

Description

When set to "YES", Verifier overwrites the HTML reports without any prompts for confirmation.

The default is "YES".

GUI Equivalent

Command	Edit – Preferences – Reporting
Field	Overwrite reports

Examples

envGetVal("verifier.preferences" "overwritereports")

envSetVal("verifier.preferences" "overwritereports" 'string "NO")

Related Topics

Overwrite reports

retryTimeThreshold

verifier.preferences retryTimeThreshold int numeric_value

Description

Specifies the threshold time for a simulation rerun as an integer value greater than or equal to 0.

The default is 0.

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Retry time threshold

Examples

envGetVal("verifier.preferences" "retryTimeThreshold")

envSetVal("verifier.preferences" "retryTimeThreshold" 'int 5)

Related Topics

Retry time threshold

reqspecs

verifier.preferences reqspecs string { "Use Requirement Spec and Check" | "Use Requirement Spec" | "Use Implementation Spec" }

Description

Sets the search order to identify the specifications that Verifier must use.

• "Use Requirement Spec and Check": Default. Checks if the specification values set in the requirements match the specification values set in the corresponding implementations. If the values match, Verifier uses those values to determine the verification status of the requirement. Otherwise, the specification check for that requirement fails.
• "Use Requirement Spec": Uses the requirement specification. If it is missing, use the implementation specification.
• "Use Implementation Spec": Uses the specification values set in the implementations to determine the verification status of the mapped requirements. If an implementation does not have any specification value, use the values set in the requirement mapped to that implementation.

GUI Equivalent

Command	Edit – Preferences – General – Specifications Search Order
Field	Requirement specification and check to implementation Requirement specification Implementation specification

Examples

envGetVal("verifier.preferences" "reqspecs")

envSetVal("verifier.preferences" "reqspecs" 'string "Use Requirement Spec")

envSetVal("verifier.preferences" "reqspecs" 'string "Use Implementation Spec")

Related Topics

Specifications Search Order

reqspecscheckunits

verifier.preferences reqspecscheckunits string { "YES" | "NO" }

Description

When set to "YES", Verifier checks if the specification unit set in the requirements and their corresponding implementations match. Set this variable when reqspecs is set to "Use Requirement Spec and Check".

The default is "NO".

GUI Equivalent

None

Examples

envGetVal("verifier.preferences" "reqspecscheckunits")

envSetVal("verifier.preferences" "reqspecscheckunits" 'string "YES")

Related Topics

reqspecs (Environment variable)

resultForSpaceCoverage

verifier.preferences resultForSpaceCoverage boolean { t | nil }

Description

Enables result reporting for verification space parameter conditions.

The default is t.

GUI Equivalent

Command	Edit – Preferences – General
Field	Show results for Verification Space parameter conditions

Examples

envGetVal("verifier.preferences" "resultForSpaceCoverage")

envSetVal("verifier.preferences" "resultForSpaceCoverage" 'boolean nil)

Related Topics

Show results for Verification Space parameter conditions

simparallelcount

verifier.preferences simparallelcount string { "number_of_parallel_runs" }

Description

Specifies the maximum number of simulations that can run in parallel.

The default is "1".

GUI Equivalent

Command	Edit – Preferences – Distribution
Field	Maximum implementations to run in parallel

Examples

envGetVal("verifier.preferences" "simparallelcount")

envSetVal("verifier.preferences" "simparallelcount" 'string "3")

Related Topics

Maximum implementations to run in parallel

tagsToOverrideWithVerificationSpace

verifier.preferences tagsToOverrideWithVerificationSpace string { "corners" | "sweeps" | "corners sweeps" }

Description

When you select the Local Run or Batch with Space run modes and run simulations, Verifier merges the corners and sweeps in the active setup with corners and sweeps defined in the Verification Space.

• corners (default) specifies that corners from the active setup are overridden by the corners from the verification space during simulation.
• sweeps specifies that sweeps from the active setup are overridden by the sweeps from the verification space during simulation.
• corners sweeps specifies that corners and sweeps from the active setup are overridden by the corners and sweeps from the verification space during simulation.

To reset the variable to the default behavior:

envSetVal("verifier.preferences" "tagsToOverrideWithVerificationSpace" 'string " ")

Suppose you have an active setup with corners C0,C1,C2 and a verification space with corners C0,C1, and C3. Here, tagsToOverrideWithVerificationSpace set to corners overrides the corners from the active setup. It runs C0, C1, C3 from the verification space, and does not run corner C2.

The default behavior of tagsToOverrideWithVerificationSpace is not overriding, but merging the corners from the active setup and the verification space. It will merge the corners C0, C1, C2, and C3.

GUI Equivalent

None

Examples

envGetVal("verifier.preferences" "tagsToOverrideWithVerificationSpace")

envSetVal("verifier.preferences" "tagsToOverrideWithVerificationSpace" 'string "sweeps")

envSetVal("verifier.preferences" "tagsToOverrideWithVerificationSpace" 'string "corner sweeps")

Related Topics

Importing Sweeps and Corners in the Setup Library

Running Simulations with Verification Spaces

Modification of the Setup Library Cellview

usereportidenticalhistory

verifier.preferences usereportidenticalhistory string { "NO" | "YES" }

Description

When set to "YES", Verifier performs interactive runs in incremental mode.

The default is "NO".

GUI Equivalent

Command	Edit – Preferences – Run
Field	Report identical histories before run

Examples

envGetVal("verifier.preferences" "usereportidenticalhistory")

envSetVal("verifier.preferences" "usereportidenticalhistory" 'string "YES")

Related Topics

Report identical histories before run

weightedAverageForCoverage

verifier.preferences weightedAverageForCoverage boolean { t | nil }

Description

When set to t, Verifier calculates the weighted average for coverage.

The default is t.

GUI Equivalent

Command	Edit – Preferences – General
Field	Weighted average for hierarchical coverage

Examples

envGetVal("verifier.preferences" "weightedAverageForCoverage")

envSetVal("verifier.preferences" "weightedAverageForCoverage" 'boolean nil)

Related Topics

Weighted average for hierarchical coverage

Environment Variables to Manage Results

The following table lists the environment variables grouped under the verifier.results family.partition:

allowLoadingIncompleteHistory

autoMergeDefault

calcStatisticsAcrossCorners

calcStatisticsForNonMC

ignoreError

maxFailures

allowLoadingIncompleteHistory

verifier.results allowLoadingIncompleteHistory boolean { t | nil }

Description

By default, Verifier does not load external results from an incomplete history. However, when allowLoadingIncompleteHistory is set to t, Verifier allows loading results of incomplete or in-progress simulations.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.results" "allowLoadingIncompleteHistory")

envSetVal("verifier.results" "allowLoadingIncompleteHistory" 'boolean t)

Related Topics

Viewing Results from an Incomplete History

autoMergeDefault

verifier.results autoMergeDefault cyclic { "None" | "Merge" | "Compare" }

Description

Specifies the default behavior when requirements from a file are being imported.

The default is "None".

GUI Equivalent

None

Examples

envGetval("verifier.results" "autoMergeDefault")

envSetval("verifier.results" "autoMergeDefault" 'cyclic "Merge")

envSetval("verifier.results" "autoMergeDefault" 'cyclic "Compare")

Related Topics

Copy Requirements from File

calcStatisticsAcrossCorners

verifier.results calcStatisticsAcrossCorners boolean { t | nil }

Description

When calcStatisticsAcrossCorners is set to t, Verifier calculates the Min or Max values of statistical outputs from the list of statistical values for each sweep and corner in ADE Assembler.

The default is nil, which means that Verifier calculates the Min or Max values of statistical outputs from the list of statistical values for each sweep "xxx(summary)" in ADE Assembler.

GUI Equivalent

None

Examples

envGetVal("verifier.results" "calcStatisticsAcrossCorners")

envSetVal("verifier.results" "calcStatisticsAcrossCorners" 'boolean t)

Related Topics

Verification Status of Requirements

calcStatisticsForNonMC

verifier.results calcStatisticsForNonMC boolean { t | nil }

Description

By default, Verifier shows all statistical data such as Yield, Min, Max, StandardDeviation, SigmaToTarget, and CPK for Monte Carlo simulations. However, in some cases it might be useful to calculate such statistical values for other types of simulations. When calcStatisticsForNonMC is set to t, Verifier calculates, saves, or loads the statistical values to or from the run summary data file for any type of simulation.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.results" "calcStatisticsForNonMC")

envSetVal("verifier.results" "calcStatisticsForNonMC" 'boolean t)

Related Topics

Verification Status of Requirements

ignoreError

verifier.results ignoreError boolean { t | nil }

Description

Ignores or includes any kinds of errors, such as simulation, netlist, or evaluation errors, during evaluation of requirements.

The default is t, which means that the errors are ignored while evaluating requirement.

GUI Equivalent

None

Examples

envGetVal("verifier.results" "ignoreError")

envSetVal("verifier.results" "ignoreError" 'boolean nil)

Related Topics

Factors that Impact Verification Status

maxFailures

verifier.results maxfailures int numeric_value

Description

Controls the maximum number of failed tests or outputs that are allowed. The allowed range is any number between 1 and 1000.

The default is 1.

GUI Equivalent

None

Examples

envGetVal("verifier.results" "maxfailures")

envSetVal("verifier.results" "maxfailures" 'int 1000)

Related Topics

Results of Failed Outputs or Tests

Environment Variables to Manage File Export

The following table lists the environment variables grouped under the verifier.export family.partition:

addSummaryInformation

fields

addSummaryInformation

verifier.export addSummaryInformation boolean { t | nil }

Description

Specifies if the Summary Information field is exported or not in the CSV and Excel files.

The default is nil.

GUI Equivalent

Command	File – Export – CSV File – Export – Excel File – Export – Imported File
Field	Summary Information

Examples

envGetVal("verifier.export" "addSummaryInformation")

envSetVal("verifier.export" "addSummaryInformation" 'boolean t)

Related Topics

Exporting Requirements

fields

verifier.export fields string "comma_separated_list_of_fieldNames"

Description

Specifies the predefined fields to be exported in the CSV and Excel files. This set of fields does not include the Summary Information field.

The default is "Parent,ID,Title,Type,MinSpec,MaxSpec,Unit,Owner,Scope,Domain,Description,Deadline,Overall Status,Mapping,History,Result Data Age,Min Value,Typical Value,Max Value,Passed,Failed,No Results,Unmapped,Verification Space,Coverage".

GUI Equivalent

Command	File – Export – CSV File – Export – Excel File – Export – Imported File
Field	Various

Examples

envGetVal("verifier.export" "fields")

envSetVal("verifier.export" "fields" 'string "ID,Title,Type,MinSpec,MaxSpec,Unit,Owner,Scope,Description,Deadline,Overall Status,Mapping,History,Result Data Age,Min Value,Typical Value,Max Value,Passed,Failed,No Results,Unmapped")

Related Topics

Exporting Requirements

Environment Variables to Manage Requirements

The following table lists the environment variables grouped under the verifier.requirement family.partition:

changeParentOnMerge

columnHeadersForImport

deadlineFormat

extRefPrefix

idCreationFunction

updateInheritedMappings

changeParentOnMerge

verifier.requirement changeParentOnMerge boolean { t | nil }

Description

Controls if the hierarchy is considered when comparing or merging an imported file.

The default is nil, which means that the hierarchy is ignored while comparing or merging an imported file.

GUI Equivalent

None

Examples

envGetVal("verifier.requirement" "changeParentOnMerge")

envSetVal("verifier.requirement" "changeParentOnMerge" 'boolean t)

Related Topics

Copy Requirements from File

columnHeadersForImport

verifier.requirement columnHeadersForImport string { "comma-separated-list-of-column-names" }

Description

Replaces the default column headers with the user-defined column headers for importing requirements from CSV or Excel file in the Import Requirements form.

The defaults are "Parent,ID,Title,Type,MinSpec,MaxSpec,Unit,Owner,Description".

GUI Equivalent

None

Examples

envGetVal("verifier.requirement" "columnHeadersForImport")

envSetVal("verifier.requirement" "columnHeadersForImport" 'string "ID,Title,Type,Unit,Owner,Description")

Related Topics

Header Columns

deadlineFormat

verifier.requirement deadlineFormat string { "date_format" }

Description

Specifies the date format used to display the deadline of a requirement as a string. For example, dd:mm:yy or dd:mm:yyyy.

The default is "".

GUI Equivalent

None

Examples

envGetVal("verifier.requirement" "deadlineFormat")

envSetVal("verifier.requirement" "deadlineFormat" 'string "dd:mm:yyyy")

Related Topics

Deadline

extRefPrefix

verifier.requirement extRefPrefix string { "prefix_string" }

Description

Specifies the prefix that is added to the referenced requirement IDs and implementation names to differentiate them from local requirements and implementations.

The default is "r".

GUI Equivalent

None

Examples

envSetVal("verifier.requirement" "extRefPrefix")

envSetVal("verifier.requirement" "extRefPrefix" 'string "refx")

Related Topics

Hierarchy for Referenced Cellviews

idCreationFunction

verifier.requirement idCreationFunction string { "name_of_function" }

Description

Specifies a function that can be used to create the requirement ID when you add a new requirement or import the requirement without a defined ID in Verifier. The function name must not have any arguments and must return a string value.

The default is "".

GUI Equivalent

None

Examples

envGetVal("verifier.requirement" "idCreationFunction")

envSetVal("verifier.requirement" "idCreationFunction" 'string "createMyNewID")

updateInheritedMappings

verifier.requirement updateInheritedMappings cyclic { "Popup" | "Never" | "Always")" }

Description

Controls the display of popup messages when mappings of composite requirement are deleted or modified.

• "Popup" displays a popup message that requires a Yes or No input.
  When you modify or delete the mappings of the composite requirement:
  If you select Yes, the same operation is done for those child requirements that have the same mappings as that of the composite parent.
  If you select No, the mappings of the child requirements are retained.
• "Never" displays no popup, and deletes or modifies only the mappings of the composite parent. This behavior is similar to selecting No for the Popup value.
• "Always" displays no popup, and deletes or modifies the mappings of both the composite parent as well as it child requirements that have the same mappings as the parent. This behavior is similar to selecting Yes for the Popup value.

The default is "Popup".

GUI Equivalent

None

Examples

envGetVal("verifier.requirement" "updateInheritedMappings")

envSetVal("verifier.requirement" "updateInheritedMappings" 'cyclic "Never")

envSetVal("verifier.requirement" "updateInheritedMappings" 'cyclic "Always")

Related Topics

Overwriting Mappings in Composite Requirements

Environment Variables to Manage Session Windows

The following table lists the environment variables grouped under the verifier.window family.partition:

height

width

height

verifier.window height integer numeric_value

Description

Controls the default session window height. The acceptable value is a numeric value greater than 0.

The default is "".

GUI Equivalent

None

Examples

envGetVal("verifier.window" "height")

envSetVal("verifier.window" "height" 'int 1050)

Related Topics

Workspaces

width

verifier.window width int 1

Description

Controls the default session window width. The acceptable value is a numeric value greater than 0.

The default is 1200.

GUI Equivalent

None

Examples

envGetVal("verifier.window" "width")

envSetVal("verifier.window" "width" int 1680)

Related Topics

Workspaces

Environment Variables to Manage Verifier Runs

The following table lists the environment variables grouped under the verifier.run family.partition:

clearAllTestJobPolicies

distributeImpSet

envVarConfigFile

impReportDirectory

impTimeoutScaleFactor

retryUnfinishedOrErrorPoints

simMode

simulationTimeout

stopBatchRunOnServerClose

stopBatchRunOnServerClose

clearAllTestJobPolicies

verifier.run clearAllTestJobPolicies boolean { t | nil }

Description

Clears all the test level job policies for an implementation before running a simulation.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.run" "clearAllTestJobPolicies")

envSetVal("verifier.run" "clearAllTestJobPolicies" 'boolean t)

Related Topics

impJobControlMode (Environment variable)

impjobpolicy (Environment variable)

impNetlistingJobPolicy (Environment variable)

Simulation of Implementations

distributeImpSet

verifier.run distributeImpSet boolean { t | nil }

Description

Distributes all implementations within an implementation set when the simulation is run in Batch Run mode. All implementations are distributed according to the preference options Maximum implementations to run in parallel and Maximum batch runs to start in parallel. Additionally, the implementation set must be without any hierarchy or dependencies.

The default is t.

GUI Equivalent

None

Examples

envGetVal("verifier.run" "distributeImpSet")

envSetVal("verifier.run" "distributeImpSet" 'boolean nil)

Related Topics

Maximum implementations to run in parallel

Maximum batch runs to start in parallel

envVarConfigFile

verifier.run envVarConfigFile string { "CSV_file_name" }

Description

Defines the CSV file name and path for environment variable configuration.

The default is "".

GUI Equivalent

Command	Edit – Preferences – Run
Field	Environment Variables

Examples

envGetVal("verifier.run" "envVarConfigFile")

envSetVal("verifier.run" "envVarConfigFile" 'string "./myEnvVars.csv")

Related Topics

Environment Variables

impReportDirectory

verifier.run impReportDirectory string "directory_name"

Description

Specifies the path to the directory where the datasheet is saved when the useTemplate and autoCreateDataSheet environment variables are enabled.

The path can contain shell environment variables ($) and the home alias (~/).

The default is an empty string, meaning that the path is automatically set to impReportDirectory/assembler_datasheets and the datasheet is copied to the same directory as the interactive HTML report.

GUI Equivalent

Command	Edit – Preferences – Reporting – HTML Report
Field	Directory

Examples

envGetVal("verifier.run" "impReportDirectory")

envSetVal("verifier.run" "impReportDirectory" 'string "myDir")

Related Topics

HTML Reports in Interactive Format

Reporting

impTimeoutScaleFactor

verifier.run impTimeoutScaleFactor int numeric_value

Description

Specifies the implementation timeout scale factor, where the timeout is based on the EstRunTime for each implementation. To enable the timeout, set this environment variable to a numeric value and the EstRunTime to a time value greater than zero. The value must be a number between 0 and 1000.

If the implementation continues to run beyond the specified time, which is the product of the values of impTimeoutScaleFactor and EstRunTime, the implementation is stopped. This check is started when the run status of the implementation changes to Running.

This environment variable is useful to stop unresponsive simulation runs in regressions, so that the regressions can complete without delays. The following are some cases when the simulation runs must be stopped:

• When the simulation is taking an unusual amount of time to complete because of a convergence issue.
• When the simulation cannot complete because of a blockage caused by a firewall or insufficient memory.

By setting this environment variable, you can stop such simulation runs so the whole regression is not delayed because of a single implementation that is not responding anymore.

GUI Equivalent

None

Examples

envGetVal("verifier.run" "impTimeoutScaleFactor")

envSetVal("verifier.run" "impTimeoutScaleFactor" 'int 4)

Related Topics

EstRunTime

Simulation Runs based on Priority and Estimated Run Time

retryUnfinishedOrErrorPoints

verifier.run retryUnfinishedOrErrorPoints boolean { t | nil }

Description

Reruns only the unfinished or error points for a failed simulation. Setting this variable to t adds the following to the Batch Mode script:

;; Set batch run options
     _verifBatchRunOptions = list(nil 'numRetries 1 'maxRetries 2 'resHistory "verifier_srsc_20210120_173238.0.RO")
     ;; Other command lines to run simulation ;;
     ;; Clear batch run options
     _verifBatchRunOptions = 'unbound

The default is t.

GUI Equivalent

None

Examples

envGetVal("verifier.run" "retryUnfinishedOrErrorPoints")

envSetVal("verifier.run" "retryUnfinishedOrErrorPoints" 'boolean t)

Related Topics

Number of retries

Retry time threshold

simMode

verifier.run simMode cyclic { "Local Run" | "Batch Run" | "Local with SPACE" | "Batch with SPACE" }

Description

Specifies the default run mode when you open a cellview. This run mode is saved or loaded to and from the settings.v3 file.

• "Local Run" specifies that the simulation is run in the local mode.
• "Batch Run" specifies that the simulation is run in the batch mode.
• "Local with SPACE" specifies that the simulation is run in the local mode with verification spaces.
• "Batch with SPACE" specifies that the simulation is run in the batch mode with verification spaces.

The default is "Local Run".

GUI Equivalent

Command	Run
Field	Run Mode

Examples

envGetVal("verifier.run" "simMode")

envSetVal("verifier.run" "simMode" 'cyclic "Batch Run")

envSetVal("verifier.run" "simMode" 'cyclic "Local with SPACE")

envSetVal("verifier.run" "simMode" 'cyclic "Batch with SPACE")

Related Topics

Simulation of Implementations

Running Simulations with Verification Spaces

simulationTimeout

verifier.run simulationTimeout int number_of_seconds

Description

Specifies the simulation as finished with an error message if no update is received from ADE Assembler within the specified simulationTimeout seconds, which can be any numeric value between 0 and 1000. If the simulation continues to run, it is not disturbed or aborted.

The default is 0, which means that there is no timeout.

GUI Equivalent

None

Examples

envGetVal("verifier.run" "simulationTimeout")

envSetVal("verifier.run" "simulationTimeout" 'int 200)

Related Topics

Simulation of Implementations

Running and Stopping Simulations

stopBatchRunOnServerClose

verifier.run stopBatchRunOnServerClose boolean { t | nil }

Description

Specifies whether to stop all batch run simulations if the Virtuoso session that launched the batch run is closed.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.run" "stopBatchRunOnServerClose")

envSetVal("verifier.run" "stopBatchRunOnServerClose" 'boolean t)

Related Topics

Simulation of Implementations

Running and Stopping Simulations

Running and Stopping Implementations in Batch Mode

stopTimeout

verifier.run stopTimeout int numeric_value

Description

Specifies the timeout limit for stopping simulation runs. After this stop time, the simulation is considered to have failed. The acceptable range of stopping timeout is 0-100000 , and the unit is seconds.

The default value is 300.

GUI Equivalent

None

Examples

envGetVal("verifier.run" "stopTimeout")

envSetVal("verifier.run" "stopTimeout" 'int 10000)

Related Topics

Simulation of Implementations

Running and Stopping Simulations

Running and Stopping Implementations in Batch Mode

Environment Variables to Manage Verifier GUI Settings

The following table lists the environment variables grouped under the verifier.gui family.partition:

displayReqHierId

filterOptions

impColumnOrder

impHiddenColumns

impHiddenColumns

resColumnOrder

resHiddenColumns

reqColumnOrder

reqHiddenColumns

runColumnOrder

runHiddenColumns

significantDigits

snapEdColumnOrder

snapEdHiddenColumns

displayReqHierId

verifier.gui displayReqHierId boolean { t | nil }

Description

Controls the display of hierarchical numbers of requirements in the Setup tab.

The default is t.

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "displayReqHierId")

envSetVal("verifier.gui" "displayReqHierId" 'boolean nil)

Related Topics

Exporting Requirements

filterOptions

verifier.gui filterOptions string { "comma-separated-list-of-filter-names" }

Description

Enables the default set of filters for new Verifier cellviews.

The default is "Mapped,Unmapped,Spec Check Fail,Passing,Non Analog,Other Cellviews".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "filterOptions")

envSetVal("verifier.gui" "filterOptions" 'string "Unmapped,Spec Check Fail,Non Analog,Other Cellviews")

Related Topics

Filters in the Requirements Hierarchy

Filtering Requirements Based on Text Criteria

Filtering Requirements Based on Status

Filters in the Implementation List

Filtering Implementations Based on Text Criteria

Filtering Implementations Based on Status

impColumnOrder

verifier.gui impColumnOrder string { "comma-separated-list-of-column-names" }

Description

Specifies the order in which columns appear in the Implementations pane of the Setup tab

The default is "Hier,Run,Output,Library,Cell,View,History,RunPlan,Test,Specification,Unit,Mapped,MappedHier".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "impColumnOrder")

envSetVal("verifier.gui" "impColumnOrder" 'string "Hier,Run,View,History,RunPlan,Test,Mapped,MappedHier")

Related Topics

Details of an Implementation

impHiddenColumns

verifier.gui impHiddenColumns string { "comma-separated-list-of-column-names" }

Description

Specifies the columns that are hidden by default in the Implementations pane of the Setup tab.

The default is "Library,Cell,View,Test,Mapped".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "impHiddenColumns")

envSetVal("verifier.gui" "impHiddenColumns" 'string "Cell,View,Test,Mapped")

Related Topics

Details of an Implementation

resColumnOrder

verifier.gui resColumnOrder string { "comma-separated-list-of-column-names" }

Description

Specifies the order in which columns appear in the Results tab.

The default is "Hier,ID,Title,Type,MinSpec,MaxSpec,Unit,VerificationSpace,Owner,CellviewHolder,Scope,Domain,Deadline,Description,ReadOnly,OverallStatus,MinValue,TypicalValue,MaxValue,Coverage,Yield,Min,Max,Mean,StandardDeviation,SigmaToTarget,Cpk,Output,ImpSpec,ImpUnit,History,Status".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "resColumnOrder")

envSetVal("verifier.gui" "resColumnOrder" 'string "Title,Type,MinSpec,MaxSpec,Unit,VerificationSpace,Owner,Deadline,Description,OverallStatus,MinValue,TypicalValue,MaxValue,Coverage,Output,ImpSpec,ImpUnit,History,Status")

Related Topics

Verification Status of Requirements

resHiddenColumns

verifier.gui resHiddenColumns string { "comma-separated-list-of-column-names" }

Description

Specifies the columns that are hidden by default in the Results tab.

The default is "ID,Type,VerificationSpace,Owner,CellviewHolder,Scope,Domain,Deadline,Description,ReadOnly,Yield,Min,Max,Mean,StandardDeviation,SigmaToTarget,Cpk".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "resHiddenColumns")

envSetVal("verifier.gui" "resHiddenColumns" 'string "ReadOnly,Yield,Min,Max,Mean,StandardDeviation,SigmaToTarget,Cpk")

Related Topics

Verification Status of Requirements

reqColumnOrder

verifier.gui reqColumnOrder string { "comma-separated-list-of-column-names" }

Description

Controls the display order of the columns in the Requirements pane of the Setup tab.

The default is "Hier,ID,Title,Type,MinSpec,MaxSpec,Unit,VerificationSpace,Owner,CellviewHolder,Scope,Domain,Deadline,Description,ReadOnly,Mapped".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "reqColumnOrder")

envSetVal("verifier.gui" "reqColumnOrder" 'string "Title,Hier,ID,Type,Description,Mapped,MinSpec,MaxSpec,Unit,VerificationSpace,Owner,CellviewHolder,Scope,Domain,Deadline,ReadOnly")

Related Topics

Details of a Requirement

reqHiddenColumns

verifier.gui reqHiddenColumns string { "comma-separated-list-of-column-names" }

Description

Specifies the columns that are hidden in the Requirements pane of the Setup tab.

The default is "ID,Owner,CellviewHolder,Scope,Domain,Deadline,ReadOnly,Mapped".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "reqHiddenColumns")

envSetVal("verifier.gui" "reqHiddenColumns" 'string "CellviewHolder,Scope,Domain,Deadline,ReadOnly")

Related Topics

Details of a Requirement

runColumnOrder

verifier.gui runColumnOrder string { "comma-separated-list-of-column-names" }

Description

Specifies the order in which columns appear in the Run tab.

The default is "Hier,Library,Cell,View,History,RunName,Run,Go,Stop,Status,ID,Title,VerificationSpace,PreRunScript".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "runColumnOrder")

envSetVal("verifier.gui" "runColumnOrder" 'string "ID,Hier,Title,Status,RunName,Run,Library,Cell,View,History,Go,Stop,VerificationSpace,PreRunScript")

Related Topics

Implementation Runs in ADE Verifier

runHiddenColumns

verifier.gui runHiddenColumns string { "comma-separated-list-of-column-names" }

Description

Specifies the columns that are hidden by default in the Run tab.

The default is "Library,Cell,View,History,RunName,Priority,EstRunTime".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "runHiddenColumns")

envSetVal("verifier.gui" "runHiddenColumns" 'string "RunName,Priority,EstRunTime")

Related Topics

Implementation Runs in ADE Verifier

significantDigits

verifier.gui significantDigits int numeric_value

Description

Sets the default rounding off schema for the significant digits to calculate overall status and progress. The acceptable value is any numeric value greater than 2.

The default is 4.

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "significantDigits")

envSetVal("verifier.gui" "significantDigits" 'int 3)

Related Topics

Overall Progress, Coverage, and Overall Coverage

snapEdColumnOrder

verifier.gui snapEdColumnOrder string { "comma-separated-list-of-column-names" }

Description

Specifies the column order in the Snapshots Editor assistant.

The default is "Visible,Name,Comment,Created,User,Locked".

GUI Equivalent

None

Examples

envGetVal("verifier.gui" "snapEdColumnOrder")

envSetVal("verifier.gui" "snapEdColumnOrder" 'string "Name,Comment,Visible,Created,User,Locked")

Related Topics

Snapshots User Interface in ADE Verifier

snapEdHiddenColumns

verifier.gui snapEdHiddenColumns string { "comma-separated-list-of-column-names" }

Description

Specifies the hidden columns in the Snapshots Editor assistant.

The default is "Created,User".

GUI Equivalent

None

Examples

envSetVal("verifier.gui" "snapEdHiddenColumns")

envSetVal("verifier.gui" "snapEdHiddenColumns" 'string "Comment,User,Locked")

Related Topics

Snapshots User Interface in ADE Verifier

Environment Variables to Manage HTML Reports

The following table lists the environment variables grouped under the verifier.html family.partition:

includeReferenceIDPrefix

includeRequirementId

useTemplate

templateName

includeReferenceIDPrefix

verifier.html includeReferenceIDPrefix boolean { t | nil }

Description

Hides the ExtRef IDs of referenced cellviews in the HTML reports of Verifier cellviews.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.html" "includeReferenceIDPrefix")

envSetVal("verifier.html" "includeReferenceIDPrefix" 'boolean t)

Related Topics

HTML Reports in Interactive Format

includeRequirementId

verifier.html includeRequirementId boolean { t | nil }

Description

Shows the requirement ID in the Result Information section of the HTML report.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.html" "includeRequirementId")

envSetVal("verifier.html" "includeRequirementId" 'boolean t)

Related Topics

HTML Reports in Interactive Format

useTemplate

verifier.html useTemplate boolean { t | nil }

Description

Displays the HTML report in a template-based interactive format.

The default is t. Setting this variable to nil displays the HTML report in the basic format.

GUI Equivalent

None

Examples

envGetVal("verifier.html" "useTemplate")

envSetVal("verifier.html" "useTemplate" 'boolean nil)

Related Topics

HTML Reports in Interactive Format

HTML Reports in Basic Format

templateName

verifier.html templateName string "report-file-names"

Description

Specifies the name of the template file used for report generation. It is also the name of the output file.

The default is index.html.

GUI Equivalent

None

Examples

envGetVal("verifier.html" "templateName")

envSetVal("verifier.html" "templateName" 'string "myFile.txt")

Related Topics

HTML Reports in Interactive Format

HTML Reports in Basic Format

Customization of HTML Reports in Interactive Format

Customizing the Interactive HTML Report Template

Examples of Interactive HTML Report Customization

Environment Variables to Manage Custom Fields

The following table lists the environment variables grouped under the verifier.customField family.partition:

csvfile (customFieldConfig)

csvfile (customReqFieldConfig)

csvfile (customFieldConfig)

verifier.customFieldConfig csvfile string { "filename-and-location" }

Description

Specifies the CSV filename and location that contains the custom project fields.

The default is "".

GUI Equivalent

None

Examples

envGetVal("verifier.customFieldConfig" "csvfile")

envSetVal("verifier.customFieldConfig" "csvfile" 'string "./myProjCustomFields.csv")

Related Topics

Custom Fields

csvfile (customReqFieldConfig)

verifier.customReqFieldConfig csvfile string { "filename-and-location" }

Description

Specifies the CSV filename and location that contains the custom fields for the requirements in a verification project.

The default is "".

GUI Equivalent

None

Examples

envGetVal("verifier.preferences" "csvfile")

envSetVal("verifier.preferences" "csvfile" 'string "./myReqCustomFields.csv")

Related Topics

Custom Fields

Environment Variables to Manage Snapshots

The following table lists the environment variables grouped under the verifier.snapshots family.partition:

ignoreDisabledElements

ignoreImpSetupElements

ignoreImpStateElements

impElementOrderSensitivity

includeImplementations

toleranceProperties

ignoreDisabledElements

verifier.snapshots ignoreDisabledElements boolean { t | nil }

Description

Specifies whether disabled elements must be ignored during the comparison of implementations from snapshots.

When set to t, the disabled elements, such as tests, runs, or corners are ignored. These elements can include the tests that are enabled in the source or the reference cellview but disabled in the destination as well as during comparison. Also, they can include the tests that are disabled in the source or the reference cellview but enabled in the destination or during comparson. During comparison, the corners and runs are marked as different with their enabled or disabled state at the top level. All the different child elements from disabled tests, corners, and runs are ignored.

The default is t.

GUI Equivalent

None

Examples

envGetVal("verifier.snapshots" "ignoreDisabledElements")

envSetVal("verifier.snapshots" "ignoreDisabledElements" 'boolean nil)

Related Topics

Ignoring Elements or their Order when Comparing Implementations from Snapshots

ignoreImpSetupElements

verifier.snapshots ignoreImpSetupElements string { "comma-separated-list-of-setup-elements" }

Description

Specifies the elements to be ignored during the comparison of *.sdb files.

The default is "plottingoptions,sortVariableValues,overwritehistoryname,uuid".

GUI Equivalent

None

Examples

envGetVal("verifier.snapshots" "ignoreImpSetupElements")

envSetVal("verifier.snapshots" "ignoreImpSetupElements" 'string "sortVariableValues,overwritehistoryname")

Related Topics

Ignoring Elements or their Order when Comparing Implementations from Snapshots

ignoreImpStateElements

verifier.snapshots ignoreImpStateElements string { "comma-separated-list-of-state-elements" }

Description

Specifies the elements to be ignored during the comparison of *.state files.

The default is "".

GUI Equivalent

None

Examples

envGetVal("verifier.snapshots" "ignoreImpStateElements")

envSetVal("verifier.snapshots" "ignoreImpStateElements" 'string "Locked,Status")

Related Topics

Ignoring Elements or their Order when Comparing Implementations from Snapshots

impElementOrderSensitivity

verifier.snapshots impElementOrderSensitivity cyclic { "Insensitive" | "Sensitive" | "SameAsReportIdenticalhistory" }

Description

Controls the sensitivity of the order of differences in the XML files that are created during snapshot comparison.

• SameAsReportIdenticalHistory considers only those differences in order elements that are reported by identical histories in maestro cellviews.
• Sensitive considers all differences in element order during comparison.
• Insensitive ignores all differences in element order during comparison.

The default is "SameAsReportIdenticalHistory".

GUI Equivalent

None

Examples

envGetVal("verifier.snapshots" "impElementOrderSensitivity")

envSetVal("verifier.snapshots" "impElementOrderSensitivity" 'cyclic "Sensitive")

envSetVal("verifier.snapshots" "impElementOrderSensitivity" 'cyclic "Insensitive")

Related Topics

Ignoring Elements or their Order when Comparing Implementations from Snapshots

includeImplementations

verifier.snapshots includeImplementations boolean { t | nil }

Description

Controls whether the design and simulation setup data from the maestro cellview must be saved within snapshots by including implementations.

The default is t.

GUI Equivalent

None

Examples

envGetVal("verifier.snapshots" "includeImplementations")

envSetVal("verifier.snapshots" "includeImplementations" 'boolean nil)

Related Topics

Adding or Removing a Snapshot

toleranceProperties

verifier.snapshots toleranceProperties string { "comma-separated-list-of-properties" }

Description

Controls the properties to which the tolerance values are applied. The possible values are Passed,Failed,Unmapped,NoResults,MinSpec,MaxSpec,MinValue,TypicalValue,MaxValue,OverallStatus.

The defaults are "MinValue,TypicalValue,MaxValue".

GUI Equivalent

Command
Field	Applying Tolerance Value

Examples

envGetVal("verifier.snapshots" "toleranceProperties")

envSetVal("verifier.snapshots" "toleranceProperties" 'string "MinValue,TypicalValue,MaxValue,")

Related Topics

Application of Tolerance Values in Snapshots

Environment Variables to Manage Implementations

The following table lists the environment variables grouped under the verifier.implementation family.partition:

additionalProjectDirectory

autoCreateRanOkRequirement

autoSyncOutputFilter

customCell

customHistory

customLib

customView

includeOnlyMappableOutputsInCount

loadToActiveWhileViewAndReuseSession

additionalProjectDirectory

verifier.implementation additionalProjectDirectory string { "comma-separated-paths of-project-directories" }

Description

Creates the additional project directories.

You can specify multiple paths as a comma-separated list of values. If a path contains special characters, such as white spaces, you do not need to escape the special characters by using the '\' character. For example, the path /path/with/white\ space/ can be specified as /path/with/white space/.

To add a project directory, you must specify a non-empty project directory while ensuring that the directory path is readable and valid. For this, you can also use the UNIX environment variables ($) and home directory (~).

For paths including white spaces (such as "ab c"), you do not need to escape the character ' '.

The default is "".

GUI Equivalent

Command
Field	Project Directory Setup

Examples

envGetVal("verifier.implementation" "additionalProjectDirectory")

envSetVal("verifier.implementation" "additionalProjectDirectory" 'string "$HOME/simulation,simulation,./abc/simulation")

Related Topics

Project Directory Setup

autoCreateRanOkRequirement

verifier.implementation autoCreateRanOkRequirement string { "comma-separated-list-of-implementation-elements" }

Description

Creates the RanOk requirements automatically with the specified elements.

The default is s are "Implementation,Run,Reliability,Test".

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "autoCreateRanOkRequirement")

envSetVal("verifier.implementation" "autoCreateRanOkRequirement" 'string "Implementation,Run")

Related Topics

Creating Requirements from Implementations

autoSyncOutputFilter

verifier.implementation autoSyncOutputFilter string { "regular-expression-format-string" }

Description

Filters the outputs in auto-synced implementations based on the specified criteria, which can be specified using regular expression format strings.

Some regular expression format strings and their results are as follows:

• ".*DCGain.*" - Filters any output that contains DCGain in the name
• "^DCGain.*" - Filters any output whose name begins with DCGain
• "C?DCGain" - Filters outputs whose name is CDCGain or DCGain
• "DCGain1|DCGain2" - Filters the output whose name is "DCGain1" or "DCGain2"
• "DCGain Bandwidth" - Filters the output whose name is "DCGain Bandwidth"

The default is "".

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "autoSyncOutputFilter")

envSetVal("verifier.implementation" "autoSyncOutputFilter" 'string "DCGain1|DCGain2")

envSetVal("verifier.implementation" "autoSyncOutputFilter" 'string "DCGain, DCGain1")

Related Topics

Simulation Runs Using Auto-Synced Requirements

customCell

verifier.implementation customCell string { "cell-name" }

Description

Defines the cell for a new custom implementation.

The default is "C".

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "customCell")

envSetVal("verifier.implementation" "customCell" 'string "myCell")

Related Topics

Custom Implementations

customHistory

verifier.implementation customHistory string { "history-name" }

Description

Defines the history for a new custom implementation.

The default is "H".

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "customHistory")

envSetVal("verifier.implementation" "customHistory" 'string "Created1Jan2022")

Related Topics

Custom Implementations

customLib

verifier.implementation customLib string { "library-name" }

Description

Defines the library for a new custom implementation.

The default is "CustomL".

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "customLib")

envSetVal("verifier.implementation" "customLib" 'string "myCustomLib")

Related Topics

Custom Implementations

customView

verifier.implementation customView string { "view-name" }

Description

Defines the view for a new custom implementation.

The default is "V".

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "customView")

envSetVal("verifier.implementation" "customView" 'string "myNewView")

Related Topics

Custom Implementations

includeOnlyMappableOutputsInCount

verifier.implementation includeOnlyMappableOutputsInCount boolean { t | nil }

Description

Ignores the tests, runs, reliability setups, and cellview, and only considers the implementation outputs for counting the mapped items or the mapping percentage.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "includeOnlyMappableOutputsInCount")

envSetVal("verifier.implementation" "includeOnlyMappableOutputsInCount" 'boolean t)

Related Topics

MappedHier

loadToActiveWhileViewAndReuseSession

verifier.implementation loadToActiveWhileViewAndReuseSession boolean { t | nil }

Description

Loads the history of the currently opened ADE Assembler cellview to the active setup and enables running simulations with the modified setup in the Local Run mode. The ADE Assembler cellview remains open during this custom simulation.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("verifier.implementation" "loadToActiveWhileViewAndReuseSession")

envSetVal("verifier.implementation" "loadToActiveWhileViewAndReuseSession" 'boolean t)

Related Topics

Customizing Simulations with ADE Assembler Cellviews

Environment Variables to Manage vManager Settings

The following table lists the environment variables grouped under the verifier.vmgr family.partition:

itemLimit

hostname

lookupHostnameTimeout

password

port

project

timeout

username

vPlan

itemLimit

verifier.vmgr itemLimit int numeric-value

Description

Controls the number of requirements that Verifier can load as one block from vManager during a query to retrieve requirements. If the number of requirements to be downloaded is higher that this number, the download request is split into multiple requests. The acceptable value is a number between 100 and 100000.

The default is 1000.

GUI Equivalent

None

Examples

envGetVal("verifier.vmgr" "itemLimit")

envSetVal("verifier.vmgr" "itemLimit" 'int 2000)

Related Topics

Setting Up the vManager Connection

hostname

verifier.vmgr hostname string { "server-host-name" }

Description

Specifies the hostname of the vManager server.

The default is nil.

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	Hostname

Examples

envGetVal("verifier.vmgr" "hostname")

envSetVal("verifier.vmgr" "hostname" 'string "myVManagerServer")

Related Topics

vManager Setup Form

lookupHostnameTimeout

verifier.vmgr lookupHostnameTimeout int numeric-value

Description

Controls the maximum time after which lookup for the specified host name of the vManager server aborts. When set to 0, skips the lookup for the host name and requires you to specify the correct host name. The acceptable value is a number between 0 and 240.

The default is 5.

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	Hostname

Examples

envGetVal("verifier.vmgr" "lookupHostnameTimeout")

envSetVal("verifier.vmgr" "lookupHostnameTimeout" 'int 10)

Related Topics

vManager Setup Form

password

verifier.vmgr password string { "password-string" }

Description

Specifies the password for logging onto the vManager server.

The default is "".

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	Password/Token

Examples

envGetVal("verifier.vmgr" "password")

envSetVal("verifier.vmgr" "password" 'string "abcd")

Related Topics

vManager Setup Form

port

verifier.vmgr port int numeric-value

Description

Specifies the port settings of the vManager server. The acceptable value is a number between 0 and 100000.

The default is 0.

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	Port

Examples

envGetVal("verifier.vmgr" "port")

envSetVal("verifier.vmgr" "port" 'int 5000)

Related Topics

vManager Setup Form

project

verifier.vmgr project string { "project-name" }

Description

Specifies the name of the project to use on the vManager server.

The default is "".

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	Project

Examples

envGetVal("verifier.vmgr" "project")

envSetVal("verifier.vmgr" "project" 'string "myProjectName")

Related Topics

vManager Setup Form

timeout

verifier.vmgr timeout int numeric-value

Description

Controls the time after which the vManager connection is terminated if the vManager server is unresponsive. This time should be set to a duration long enough where the vManager server is highly loaded and responses are slow. The acceptable value is a number between 0 and 100000.

The default is 120.

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	Timeout

Examples

envGetVal("verifier.vmgr" "timeout")

envSetVal("verifier.vmgr" "timeout" 'int 240)

Related Topics

vManager Setup Form

username

verifier.vmgr username string { "user-name" }

Description

Specifies the username for logging onto the vManager server.

The default is "".

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	User

Examples

envGetVal("verifier.vmgr" "username")

envSetVal("verifier.vmgr" "username" 'string "user1")

Related Topics

vManager Setup Form

vPlan

verifier.vmgr vPlan string { "plan-name" }

Description

Specifies the vPlan file associated with the Verifier cellview.

The default is "".

GUI Equivalent

Command	Tools – vManager – Setup vManager
Field	vPlan

Examples

envGetVal("verifier.vmgr" "vPlan")

envSetVal("verifier.vmgr" "vPlan" 'string "myPlan")

Related Topics

vManager Setup Form

Return to top