Product Documentation
Virtuoso ADE Assembler User Guide
Product Version IC23.1, November 2023

12

Working with the Simulation Setup

This chapter describes the following topics:

Directory Structure of a Maestro Cellview

The simulation setup in ADE Assembler is saved in a maestro cellview. The default name for this type of cellview is maestro.

A maestro cellview has the following directory structure:

The following table describes the contents of files and directories in the maestro cellview.

Table 12-1 Contents of a Maestro Cellview
Directory/File Description

documents

A directory containing the documents you created in the maestro view, including the specification summaries and datasheets you created in ADE Assembler.

results

A directory containing the results database (.rdb) and run log (.log) files for all the history checkpoints saved from the maestro view. The .rdb file contains the results of all the scalar outputs evaluated using the simulation results returned by the simulator. These details are used to populate the Results tab in the ADE Assembler environment window. The .log file contains the summary of the simulations run for the saved checkpoint.

Simulation results are not saved in the results directory. For information about the location of simulation results information, see Specifying Options for Saving Simulation Results.

You can specify a different location where you want the program to save the results database and run log files. For this, do one of the following:

If you do not specify a different location and open the maestro view in read-only mode or you do not have write permissions for the maestro view, the program writes this information to libraryName/cellName/viewName/maestro/data in the location specified using the asimenv.startup projectDir environment variable. The default setting for this environment variable is $HOME/simulation.

states

A directory containing the setup states you created in ADE Assembler. For every state, a .sdb file and a directory is saved.

active.state

XML state file that contains the details of all the tests in the currently active ADE Assembler setup.

maestro.sdb

The main setup database file that contains the setup details, other than test details, of the currently active ADE Assembler setup.

The history setup information for each history is saved in a .zip file in the history directory.

maestro.tag

Contains master information for the maestro cellview.

history

This directory contains history.sdb and .zip files for each history. Each zip file contains the setup information for a history. The compressed format of saving history setup saves space.

history.sdb maintains an inventory list of all history checkpoints saved for a cellview.

data.dm

The property bag file that contains the properties of the maestro cellview.

Additional Files or Directories Visible in a Maestro View Migrating from ADE XL

When you migrate an adexl view to a maestro view for ADE Assembler, the following additional files or directories are also visible inside the maestro view:

The setup states saved from the ADE XL view are copied to the state directory in the maestro view. While copying these setup states, the number of files are reduced and all the state information is condensed into a single XML file called active.state under the directory with same name as that of the state name.

Saving the Simulation Setup

To save the simulation setup, do the following

To save the simulation setup to a different maestro view, do the following:

  1. Choose File – Save A Copy.
    The Save A Copy form appears.
  2. Enter the name of the library, cell and view in which you want to save the setup.
  3. Click OK.
This action does not save history data, only the setup database.

See also

Copying a maestro Cellview

Do not copy maestro views using file system commands or a graphical file manager. This can result in loss of data from previous simulation runs.

You can use Library Manager to copy maestro views. Use one of the methods described in Table 12-1 when you:

This section describes only the procedures for copying a maestro view. The procedures for copying libraries or cells containing maestro views are similar. For more information about copying libraries and cells, see the Cadence Library Manager User Guide.

Table 12-2 Methods of Copying maestro Views

Method Purpose

Copy only the simulation setup, but not the results database, run log files, and simulation results for the history items.

Use this method if you only want to reuse the simulation setup existing in a maestro view, and do not want to view the simulation results, plot waveforms, or do other tasks that need access to simulation results in the new maestro view.

For more information, see Copying only the Simulation Setup in a maestro View.

If the results database exists within the maestro view that you are copying, you can view the simulation results in the new maestro view. However, you cannot plot waveforms or do other tasks that need access to simulation results in the new maestro view. For more information about the location of the results database, see Specifying Results Database Location.

Copy the simulation setup and the results database

Use this method if you want to reuse the simulation setup and view the simulation results, but do not want to plot waveforms or do other tasks that need access to simulation results in the new maestro view.

For more information, see Copying the Simulation Setup and the Results Database in a maestro Cellview.

Copy everything (the simulation setup, results database, run log files and the simulation results) in the maestro view

Use this method if you want to make a complete copy of an maestro view, or create a backup of an maestro view.

For more information, see Copying Everything Contained in a maestro Cellview.

Copying only the Simulation Setup in a maestro View

To copy only the simulation setup in a maestro cellview, do the following.

  1. (Optional) If you want to run triggers set for the copy operation, set the following environment variables in the .cdsenv file:
    • ddserv.lib enableCopyInDFII: Specifies that the command to copy cellview is to be run within the DFII session instead of Library Manager. This allows the command to run the triggers registered for it.
    • cdsLibManager.copyGlobals mpsRadio: Specifies whether the copy operation uses the copy service of the session, when available, or the local copy engine in Library Manager. This also allows the Copy command of Library Manager to run the triggers.
  2. Start the Virtuoso design environment.
  3. In the CIW, choose Tools – Library Manager.
    The Library Manager form appears.
  4. In the Library column, select the library in which the maestro view exists.
  5. In the Cell column, select the cell in which the maestro view exists.
  6. In the View column, select the maestro view.
  7. Choose Edit – Copy.
    The Copy View form appears.
  8. In the To group box, type specify the destination library, cell and view name.
  9. Click OK to copy the maestro view.

Copying the Simulation Setup and the Results Database in a maestro Cellview

To copy the simulation setup and the results database in an maestro view, do the following:

  1. Perform steps 3 to 8 described in Copying only the Simulation Setup in a maestro View.
  2. Select the Update Instances check box.
    The drop-down list becomes active.
  3. From the drop-down list, select Of New Copies Only.
  4. Click OK to copy the maestro view.

See also:

Copying Everything Contained in a maestro Cellview

To copy everything that is contained in a maestro cellview, do the following:

  1. If you have used the asimenv.startup projectDir environment variable to specify the location for storing simulation results, ensure that the variable is set in your .cdsenv file.
    For more information about specifying the location for storing simulation results, see the following topics:
  2. Set the adexl.cpupdtr copyResultsData environment variable in the .cdsenv file.
    The copyResultsData variable is used by both Virtuoso and a supporting utility. Therefore, it is recommended to set it in the ~/.cdsenv file that is read by both. It is not sufficient to set the variable in .cdsinit.
  3. Launch Virtuoso.
  4. Copy the maestro view using the procedure described in Copying the Simulation Setup and the Results Database in a maestro Cellview.

See also:

How is the Results Database Copied for a maestro Cellview?

You can copy the results database contained in an maestro cellview using one of the following procedures:

The results database can be located inside or outside the maestro view. For more information about the location of the results database, see Specifying Results Database Location.

How are Simulation Results Copied for a maestro Cellview?

Simulation results are always located outside the maestro view. For more information about the location of simulation results, see Specifying Options for Saving Simulation Results.

When an maestro view is copied using the procedure described in Copying Everything Contained in a maestro Cellview, simulation results will not be copied into the new maestro view. Instead, a copy of the simulation results is created in the specified simulation results location. For example, if the simulation results for the maestro view in the myCell cell of the myLib library is located outside the maestro view at:

$HOME/mySimulationResults/myLib/myCell/maestro/results/data/<history_item>

and you copy the maestro view to a new view called maestro_copy, the simulation results for the maestro_copy view will be located at:

$HOME/myResultsDatabase/myLib/myCell/maestro_copy/results/data/<history_item>

Deleting a maestro View

To delete an maestro view, do the following:

  1. In the CIW, choose Tools – Library Manager.
    The Library Manager form appears.
  2. In the Library column, select the library in which the maestro view exists.
  3. In the Cell column, select the cell in which the maestro view exists.
  4. In the View column, select the maestro view.
  5. Choose Edit – Delete.
    The Delete Cell Views form appears.
  6. Click OK.

Working with Read-Only or Editable maestro Views

Read a blog related to this feature at Virtuosity: Read Mode Done Right.

When working with a read-only maestro cellview, you can modify the setup and run simulations, but you cannot save the changes at the same locations as you can do for an editable cellview.

The following sections describe how you can work with read-only maestro views:

Opening maestro Views in Read-Only Mode

There are two ways to open a maestro view in read-only mode.

In addition to the ADE Explorer or ADE Assembler license, you need a VSE L/XL license to open a maestro view in read-only mode.

Opening maestro Views in Edit mode

By default, a maestro view is opened in edit mode, but if you want to make a read-only maestro view editable,

While switching from a read-only maestro view to an editable maestro view,

If a maestro cellview is DM-managed, the following case are possible:

In edit mode, the Save button is enabled whenever there are any unsaved changes. However, in certain design management systems, you might observe that Save is not enabled. In such scenarios, you can set the alwaysEnableSaveButton environment variable to t to always keep the Save button enabled in edit mode.

Viewing the DM Status of a Cellview

If a cellview is managed by a Design Management (DM) system, you can view the status and version number of the cellview in the title bar.

There are three possible values:

The behavior of this feature can vary according to the used DM system.

Opening maestro Views for which You Do Not Have Write Permissions

When you open a maestro view for which you do not have write permissions, the following message appears:

Could not open <library_name> <cell_name> <view_name> for edit (no data or lock available). Would you like to open it for read?

Click Yes to open the view in read-only mode.

For more information about opening maestro views, see Opening an Existing Setup.

Important Points to Note

Running Simulations from Read-Only maestro Views

When you open a cellview in read-only mode, you can make changes in the setup and run simulations. The simulation results use the updated setup information, but you cannot save the changes in the original maestro cellview. If it is important to save the changes, you need to use another cellview name or make the current cellview editable before saving the changes.

When a simulation is run for a read-only cellview in ADE Assembler, a history checkpoint is saved with a.RO suffix in the name. Also, on the History tab, a different icon is used for such a history, as shown below.

Use the View Results or Load Setup to Active history commands to view the results or the setup used for the history with the .RO suffix.

To save the setup changes from a .RO history into a maestro view, open the view in the edit mode, load the read-only history setup to active, and save the cellview. You can also convert a read-only history into an editable history by using the Move to View History command from the context-sensitive menu of a history item. For more details, refer to Saving a Read-Only History Inside the maestro View.

Important Points to Note

The following sections provide more details about the histories saved from a read-only maestro view:

Location of Simulation Results and Results Database Information for Read-Only maestro Views

By default, ADE Assembler writes the simulation results and setup information for a checkpoint run from a read-only maestro view to the libraryName/cellName/viewName/results/data/<history_item> path in the location specified using the asimenv.startup projectDir environment variable. The default setting for this environment variable is $HOME/simulation.

The results database information is also saved to libraryName/cellName/viewName/results/data in the same location specified using the asimenv.startup projectDir environment variable.

Since ADE Assembler needs to write data while in the path set by asimenv.startup projectDir, it is important that you have write permission for this location.

You can specify a different location for storing simulation results using the procedure described in Specifying Options for Saving Simulation Results.

Saving a Read-Only History Inside the maestro View

By default, the histories of simulations run from a read-only cellview are saved. If you do not want to save the histories, set the readOnlyHistorySupport environment variable to nil.

envSetVal("adexl.simulation" "readOnlyHistorySupport" 'boolean nil)

To save the history as a part of the maestro view, do this:

  1. Open the maestro cellview in the edit mode.
  2. Right-click the history name on the History tab of the Data View pane and choose Move to Cellview (Make Writable).
    The setup information and history results are moved from the project directory to the location where the maestro view results are saved, that is, to libraryName/cellName/viewName/results/maestro/<history_item>.

You can revert this change by using the Move to Project Directory (Make Read Only) History command in the context-sensitive menu for a history on the History tab.

Number of History Entries Saved for Read Only maestro Views

You can set the maximum number of histories to be saved in read-only mode by setting the saveLastNROHistoryEntries environment variable. The default value of this variable is 10.

envSetVal("adexl.simulation" "saveLastNROHistoryEntries" 'int 10)

Saving Setup Changes in Read-Only maestro Views

If you make any changes to the setup in a read-only maestro view, the Save As form appears when you save or close the maestro view. You can save the changes to a new maestro view in a location where you have write permissions.

Alternatively, you can perform the following steps to save the setup changes without creating a new cellview:

  1. Make changes in the setup of a read-only cellview.
  2. Run a simulation. A history is saved with the .RO suffix.
  3. Open the cellview in edit mode.
  4. Right-click the .RO history and choose the Load Setup to Active command to load the setup from the read-only history.
  5. Save the setup. The changes are saved in the original maestro cellview.

For information about using the Save As form, see Saving the Simulation Setup.

Importing the Simulation Setup

You can import the complete simulation setup or only specific simulation settings

In a SKILL script, you can use thes maeConvertAndCombineMultiADELToAssembler function to import setup.

To import the simulation setup from one or more existing adexl or maestro cellviews to the current maestro view, do the following:

  1. Choose File – Import.
    The Import Setup form appears.
    Select appropriate options on this form to specify the names of cellviews and the settings to be imported.
  2. By default, the Import single view option is selected. This indicates that setup can be imported from a single cellview selected on the form. If you want to import details from multiple cellviews, select the Import multiple views option.
  3. In the Select design section, select the name of a library and cell that contain the cellviews from which you need to import setup.
  4. Select the names of one or more views in the View list. These are the cellviews from which you need to import the setup details.
    You can import setup details from one or more ADE L, ADE XL, or ADE Assembler cellviews.
  5. In the History drop-down list, select the history item from which you want to import the setup. By default, the components from the active simulation setup of the selected view are imported.
  6. In the What to Import section, select the check box next to the settings you want to import.
    Only the check boxes corresponding to the settings available in the setup to be imported are enabled. If any check box is not enabled, it implies that the corresponding setting is not available in the selected history or active setup of the view.
    By default, all the enabled settings are selected for import. You can click Clear All to clear all the selections or click Select All to select all the enabled check boxes for import.
    The following table describes the use of all the available check boxes in this section:
    Select To

    Tests

    Import the test definitions in the Data View pane. The simulation state of each test is also saved in the subdirectories.

    Variables

    Import the global variable definitions, including their enabled status and values, in the Data View pane.

    Parameters

    Import the definitions of parameters, including their enabled status and values, in the Data View pane.

    Run Mode

    Import the active run mode and set it on the Run toolbar.

    Run Options

    Import the following settings:

    • Options in the Run Options form.
    • Simulation options for all the customized run modes. For example, if you changed the default simulation options of the Monte Carlo, Global Optimization, and Local Optimization run modes before saving the state, the tool will import the settings for all the three run modes.

    Specifications

    Import the specifications defined in the Outputs pane. This includes the details of the specification type and their target values.

    Corners

    Import the corner definitions defined in the Corners Setup form.

    Model Groups

    Import the model groups defined in the Corners Setup form.

    Extensions

    Import the parasitic details in the Parasitic Setup form.

    Reliability Analysis

    Import the settings for reliability analysis.

    Checks/Asserts

    Import the settings for Checks/Asserts analysis.

    Fault Setup

    Import the settings for the fault setup assistant.

    Run Plan

    Import the run plan setup.

    Stimuli

    Import the setup for the Stimuli Assignment form for the tests that match

    Plotting Templates

    Import plotting templates
  7. In the Operation drop-down list, select the import mode.
    The following table describes the use of each import mode:
    Select To

    retain

    Retain the current setup information and append other setup information for each setting selected in the What to Import group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.

    merge

    Overwrite the current setup information for items that have the same name and append other setup information for each setting selected in the What to Import group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.

    overwrite

    Overwrite the current setup information for each setting selected in the What to Import group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.
  8. Click OK to import the setup into the current maestro view.

Working with Setup States

ADE Assembler supports different run modes like Single Run, Sweeps and Corners, Monte Carlo Sampling, Local Optimization, Global Optimization, and so on. For more information about run modes, see Specifying the Run Mode.

For each run mode, you may need a different simulation setup. For example, you may need different parameter specifications for running Monte Carlo analysis, optimization and sensitivity analysis. Similarly, you may need a different set of global variable values for running local and global optimization. Even for the same run mode, you may need a different simulation setup. For example, you may want to run Single Run, Sweeps and Corners with a different set of global variables.

ADE Assembler allows you to create setup states that contain all or part of the simulation setup. You can later restore the simulation setup from the setup state by loading all or part of the settings in the setup state. This allows you to avoid modifying the simulation setup every time you need to run simulation using a different setup. The following examples describe the use of setup states:

Example 12-1 Different Setup States for Different Run Modes

To have a different setup for Single Run, Sweeps and Corners runs and Monte Carlo analysis, do the following:

  1. Define the settings required for Single Run, Sweeps and Corners runs and save the settings in a setup state named SweepsCornersSetup.
    For more information about creating a setup state, see Creating or Updating a Setup State.
  2. Modify the settings as required for Monte Carlo analysis, and save the settings in a setup state named MonteCarloSetup.
  3. Do the following:
    • Before you run Single Run, Sweeps and Corners, load the SweepsCornersSetup setup state using the Overwrite option.
      For more information about loading a setup state, see Loading a Setup State.
    • Before you run Monte Carlo analysis, load the MonteCarloSetup setup state using the Overwrite option.

Example 12-2 Different Setup States for Different Set of Global Variables

To run Single Run, Sweeps and Corners with a different set of global variables, do the following:

  1. Create the first set of global variables and save the variables in a setup state named SetupGlobalVars_1.
    For more information about creating global variables, see Creating a Global Variable. For more information about creating a setup state, see Creating or Updating a Setup State.
  2. Delete the first set of global variables.
  3. Create the second set of global variables and save the variables in a setup state named SetupGlobalVars_2.
  4. Do one of following before you run Single Run, Sweeps and Corners:
    • To run Single Run, Sweeps and Corners using the global variables in the setup state named SetupGlobalVars_1, load the SetupGlobalVars_1 setup state using the Overwrite option.
      For more information about loading a setup state, see Loading a Setup State.
    • To run Single Run, Sweeps and Corners using the global variables in the setup state named SetupGlobalVars_2, load the SetupGlobalVars_2 setup state using the Overwrite option.

See the following topics for more information:

Creating or Updating a Setup State

To create a new setup state, or update an existing setup state, do the following:

  1. Choose File – Save Setup State.
    The Save Setup State form appears.
  2. Do one of the following:
    • To create a new setup state, enter the name of the setup state in the State field.
    • To update an existing setup state, select an existing state in the Existing list.
  3. In the What to Save group box, select the check box next to the settings you want to save.
    By default, all the settings existing in the maestro view are selected for saving. You can click Select All to select all the settings for saving, or click Clear All to clear all the selections.

    Select To

    Tests

    Save the test definitions in the Data View pane. The simulation state of each test is also saved in the subdirectories.

    Variables

    Save the global variable definitions, including their enabled status and values, in the Data View pane.

    Parameters

    Save the definitions of parameters, including their enabled status and values, in the Data View pane.

    Run Mode

    Save the active run mode that is currently selected on the Run toolbar.

    Run Options

    Save the following settings:

    • Options from the Run Options form.
    • Simulation options for all the customized run modes. For example, if you have changed the default settings of the Monte Carlo and Local Optimization run modes, but the currently active run mode is Global Optimization, the tool will save the settings for all three run modes.

    Specifications

    Save the specifications defined in the Outputs pane. This includes the details of the specification type and their target values.

    Waveform Compare

    Save the wave specs added in the Outputs pane.

    Corners

    Save the corner definitions defined in the Corners Setup form.

    Model Groups

    Save the model groups defined in the Corners Setup form.

    Extensions

    Save the parasitic details set by using the Parasitic Setup form.

    Reliability Analysis

    Save the details set by using the Reliability form.

    Checks/Asserts

    Save the enabled or disabled status of the Checks/Asserts check box specified in the Data View assistant pane. It also saves the enabled or disabled status of this feature for each test.

    Outputs of type violation are saved in test state.
  4. Click OK.
    By default, the maestro state is saved in XML file format, which saves fewer files as compared to the number of files saved in an ADE state.

Loading a Setup State

To load a setup state, do the following:

  1. Choose File – Load Setup State.
    The Load Setup State form appears.
  2. In the State Name group box, select the name of the state you want to load.
  3. In the What to Load group box, select the check box next to the settings you want to restore to the current simulation setup.
    By default, all the settings existing in the setup state are selected for restore. You can click Select All to select all the settings for restoring, or click Clear All to clear all the selections.

    Select To

    Tests

    Restore the test definitions in the Data View pane. The simulation state of each test is also saved in the subdirectories.

    Variables

    Restore the global variable definitions, including their enabled status and values, in the Data View pane.

    Parameters

    Restore the deifinitions of parameters, including their enabled status and values, in the Data View pane.

    Run Mode

    Restore the active run mode and set it on the Run toolbar.

    Run Options

    Restore the following settings:

    • Options in the Run Options form.
    • Simulation options for all the customized run modes. For example, if you changed the default simulation options of the Monte Carlo, Global Optimization, and Local Optimization run modes before saving the state, the tool will restore the settings for all the three run modes.

    Specifications

    Restore the specifications defined in the Outputs pane. This includes the details of the specification type and their target values.

    Waveform Compare

    Restore the wave specs to the outputs in the Outputs pane.

    Corners

    Restore the corner definitions and their enable status defined in the Corners Setup form.

    Model Groups

    Restore the model groups defined in the Corners Setup form.

    Extensions

    Restore the parasitic details set by using the Parasitic Setup form.

    Reliability Analysis

    Restore the details set by using the Reliability form.

    Checks/Asserts

    Restore the enabled or disabled status of the Checks/Asserts check box specified in the Data View assistant pane, and the enabled or disabled status of this feature for each test.

    Outputs of type violation are restored from test state.
  4. In the Operation drop-down list, select the restore mode.
    Select To

    retain

    Retain the current setup information and append other setup information for each setting selected in the What to Load group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.

    merge

    Overwrite the current setup information for items that have the same name and append other setup information for each setting selected in the What to Load group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.

    overwrite

    Overwrite the current setup information for each setting selected in the What to Load group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.
  5. Click OK to load the selected setup state.

Renaming a Setup State

To rename a setup state, do the following:

  1. Expand the Setup States tree in the Data View assistant.
  2. Double-click the setup state name that you want to change.
    The setup state name is enabled for change.
  3. Type a new name and press Enter.
    The setup state is renamed.

Deleting a Setup State

To delete a setup state, do the following:

  1. Choose File – Remove Setup State.
    The Remove Setup State form appears.
  2. In the State Name group box, select the name of the setup state you want to delete.
  3. Click OK to delete the setup state.

How the Simulation Setup is Updated When You Load Setup States

When you load a setup state, you can specify the type of settings to be loaded in the What to Load group box.

You can also choose the operating mode to be set while loading the setup state information. The operating mode describes how the current simulation setup is updated when you load a setup state in retain, merge or overwrite mode.

The following example shows how the different operating modes load the information:

The current simulation setup in a maestro cellview has the following global variables:

Choose to load variables from a setup state that has the following global variables:

See the following sections to understand how the current simulation setup is updated when you load the setup state in retain, merge or overwrite mode:

Results of Loading a Setup State in Retain Mode

The updated simulation setup after loading the setup state in retain mode will have the following global variables:

Note the following:

Results of Loading a Setup State in Merge Mode

The updated simulation setup after loading the setup state in merge mode will be:

Note the following:

Results of Loading a Setup State in Overwrite Mode

The updated simulation setup after loading the setup state in overwrite mode will be:

All the global variables in the current simulation setup are deleted and the global variables in the setup state are added when you load the setup state in overwrite mode.

Running a Simulation Using a Setup State

You can run a simulation based on the settings in a setup state.

To run a simulation using a setup state, do the following:

The history item for the simulation run will have a name starting with the name of the setup state. For example, if the name of the setup state is myCorners, the history item will have the name myCorners.seqNum, where seqNum is 0 (zero) for the first history item, then 1+(the largest existing seqNum for that setup state). For more information about history items, see Chapter 20, “Working with History Checkpoints.”

Creating a Plan Using Setup States

A plan is a sequence of steps required to complete a particular task. For example, characterizing a design might involve running several tests or sweeps. These tasks can be grouped together to form a characterization plan.

The Run Plan assistant in ADE Assembler provides a convenient way to set up runs, apply conditions between runs, and save regression scripts. Use that assistant to create run plans that involve a common set of tests and their setup. If your run plan needs to use a different set of tests or different setups of a particular test, create a plan using setup states. However, such plans will be run from OCEAN and will create OCEAN histories.

To create a plan by using setup states, you need a separate setup state for each task in the plan that you link, in the order they need to be run, to an OCEAN script file. When you run the OCEAN script file, ADE Assembler does the following for each setup state, in the order in which the setup states are linked to the OCEAN script file:

  1. Loads the current simulation setup to memory.
  2. Loads the setup state to update the simulation setup in memory.
  3. Runs simulation using the updated simulation setup in memory.
  4. Clears the simulation setup in memory.

For example, if you have two tasks in a plan, create two setup states—say, myTask1 and mytask2—that contain the simulation settings required to run the simulations corresponding to each task in the plan. Then link the setup states to an OCEAN script file named myPlan.ocn, in the order in which they need to be run. When you run the myPlan.ocn OCEAN script file, ADE Assembler does the following:

  1. Loads the current simulation setup to memory.
  2. Loads the myTask1 setup state to update the simulation setup in memory.
  3. Runs simulations using the updated simulation setup in memory.
  4. Clears the simulation setup in memory.
  5. Loads the current simulation setup to memory.
  6. Loads the myTask2 setup state to update the simulation setup in memory.
  7. Runs simulations using the updated simulation setup in memory.
  8. Clears the simulation setup in memory.

To create a plan, do the following:

  1. Create setup states that contain the simulation settings required to run the simulations corresponding to each task in the plan. For more information, see Creating or Updating a Setup State.
  2. Right-click a setup state in the expanded Setup States tree on the Data View pane and choose Link to OCEAN XL Script.
    The Choose an OCEAN XL File form appears.
  3. Do one of the following:
    • To link a setup state to a new OCEAN script file, type the name of the OCEAN script file in the File Name field, and click Open.
    • To link a setup state to an existing OCEAN script file, select the OCEAN script file, and click Open. The following message appears:
      File <filename> already exists. How do you want to link to it.
      Do one of the following:
      • Click Append to add the OCEAN XL commands required to link the setup state in the end of the file.
      • Click Overwrite to delete the contents of the file and add only the OCEAN XL commands required to link the setup state.

    The Link Setup State form appears.
  4. In the State Name group box, select the name of the setup state you want to link to the OCEAN XL script file.
  5. In the What to Link group box, select the check box next to the settings you want to be restored to the simulation setup in memory.
    By default, all the settings existing in the setup state are selected. You can click Select All to select all the settings, or click Clear All to clear all the selections.
    Select To

    Tests

    Restore tests

    Run Mode

    Restore run mode settings

    Corners

    Restore corners

    Variables

    Restore global variables

    Run Options

    Restore run options

    Model Groups

    Restore model groups

    Parameters

    Restore parameters

    Specifications

    Restore specifications

    Extensions

    Restore extensions
  6. In the Operation drop-down list, select the restore mode.
    Select To

    retain

    Retain the setup information in memory and append other setup information for each setting selected in the What to Link group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.

    merge

    Overwrite the setup information in memory for items that have the same name and append other setup information for each setting selected in the What to Link group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.

    overwrite

    Overwrite the setup information in memory for each setting selected in the What to Link group box.

    For more information, see How the Simulation Setup is Updated When You Load Setup States.
  7. Click OK to link the setup state to the OCEAN script file.
    The OCEAN script file is opened in a text editor. The OCEAN script file contains the OCEAN XL commands required to required to link the setup state.
    ;----------------- Setup State "myStep1" ---------------
ocnSetXLMode(Assembler)
ocnxlTargetCellView( "workshopLib" "MSPS_DUT" "maestro" )
ocnxlLoadSetupState( "myStep1" ’retain ?tests t ?vars t ?parameters t ?currentMode t 
 ?runOptions t ?extensions t ?specs nil ?corners nil 
 ?modelGroups nil )
ocnxlRun()
ocnxlOutputSummary()
ocnxlEndXLMode(Assembler)
  8. Repeat steps 2 to 7 to link more setup states to the OCEAN script file. The OCEAN XL commands required to required to link the setup states are appended in the order in which they are linked to the OCEAN script file.
    The following example shows how three setup states named myTask1, mytask2 and myTask3 are linked to an OCEAN script file. 
    ;----------------- Setup State "myStep1" ---------------
ocnSetXLMode()
ocnxlTargetCellView( "workshopLib" "MSPS_DUT" "maestro" )
ocnxlLoadSetupState( "myStep1" ’retain ?tests t ?vars t ?parameters t ?currentMode t 
 ?runOptions t ?extensions t ?specs nil ?corners nil 
 ?modelGroups nil )
ocnxlRun()
ocnxlOutputSummary()
ocnxlEndXLMode()
    ;----------------- Setup State "myStep2" ---------------
ocnSetXLMode()
ocnxlTargetCellView( "workshopLib" "MSPS_DUT" "maestro" )
ocnxlLoadSetupState( "myStep2" ’retain ?tests t ?vars t ?parameters t ?currentMode t 
 ?runOptions t ?extensions t ?specs nil ?corners nil 
 ?modelGroups nil )
ocnxlRun()
ocnxlOutputSummary()
ocnxlEndXLMode()
    ;----------------- Setup State "myStep3" ---------------
ocnSetXLMode()
ocnxlTargetCellView( "workshopLib" "MSPS_DUT" "maestro" )
ocnxlLoadSetupState( "myStep3" ’overwrite ?tests t ?vars t ?parameters t ?currentMode t 
 ?runOptions t ?extensions t ?specs nil ?corners nil 
 ?modelGroups nil )
ocnxlRun()
ocnxlOutputSummary()
ocnxlEndXLMode()
  9. Load and run your OCEAN script file in the Command Interpreter Window (CIW).
    For more information, see the OCEAN Reference.
    You must not load and run your OCEAN XL script in the CIW while ADE Assembler is still running for the same cellview.

    When you run the OCEAN XL script, the program reports the following information:
    • Sweep parameters and their values
    • Number of tests, sweep points, and corners
    • Points completed and job status information
    • Results location to the output area of the CIW

    For example:
    1/1 completed.
*Info*    The result of this OCEAN XL run are saved in "Interactive.3" in library "workshopLib", cell "MSPS_DUT", view "adexl".
    The results location corresponds to the lib/cell/view specified in the ocnxlTargetCellView call, such as
    ocnxlTargetCellView( "workshopLib" "MSPS_DUT" "maestro" )
    See “OCEAN Commands in XL Mode” in the OCEAN Reference for information about OCEAN script commands for ADE Assembler.

Return to top
 ⠀
X