Preparing libraries of Simcenter Amesim supercomponents

The aim of this section is to prepare the libraries of supercomponents that will be used in Simcenter System Analyst for configuring the architecture models.

Supercomponents must be saved in one or several Simcenter Amesim libraries. Save these libraries within the "libraries" folder of the Simulation Environment and into a subfolder dedicated to the Simcenter Amesim native tool. This will make it easier to extend your Simulation Environment to other simulation tools. The administrator must set this path in the cz.xml using the Tool_Directory tag.

Figure 485: cz.xml flags

We also recommend that you store your libraries of configurable supercomponents and the libraries of resource supercomponents or specific submodels in distinct libraries. This will make it simple to exclude resource components from the Simcenter System Analyst model import process. Use folders named private to store the resource libraries that do not need to be handled by the model import.

In most cases, your configurable supercomponents can have dependencies on other components or on files used as parameters (data files for example). If these dependencies are defined through file paths, these file paths must be valid no matter where the Simulation Environment local folder is, and no matter what the context of the supercomponent is (in a library or model).

Figure 486: Example of supercomponents saved in a Simcenter Amesim library

Note

We advise you to give meaningful names to supercomponent icons, the submodels of the supercomponents, parameters and variables since all these can be directly reused in Simcenter System Analyst, after model import.

Warning

Supercomponent icons names cannot start with a number.

If the architect wants to propose several levels of model to the Analyst to perform different types of analysis for a single supercomponent, several submodels can be proposed with each supercomponent.

Figure 487: Example of a Simcenter Amesim supercomponent with 4 levels of submodel

For each submodel of supercomponent, you can expose the following through the supercomponent Simcenter Amesim interface:

• all parameters that will be provided to the Analyst for set-up,

• all variables needed by the Analyst for post-processing.

Figure 488: Example of a submodel with exposed parameters

Figure 489: Example of a submodel with exposed variables

Note

If a submodel exposes table parameters, the related datafile should be stored into the related submodel library and referenced with ${SC_library_node} keyword. For example: ${SC_library_node}\data\file.data

In case of model table parameter, the related datafile should be stored within the .ame file and referenced by ${full_circuit_name}keyword. For example ${full_circuit_name}\file.data

Before launching a model import, you must verify that the supercomponents do not contain any of the following:

• References to relative paths.

• References to absolute paths towards a specific user's computer. All the paths of dependent submodels must start with $GREENCZ or $AME. To do this, set the environment variable GREENCZ to the root folder of the Simulation Environment. For example: set GREENCZ=D:\SystemAnalyst\SE\InternalProjects\Automotive1\trunk. Warning Make sure that in Simcenter Amesim all paths in the category path list start either with $GREENCZ or $AME.

The use of specific submodels within supercomponents or not contained within a supercomponent is supported. In this case the libraries of specific submodels must be added to the Simulation Environment, in a “private” directory, next to the Simcenter Amesim libraries.