Compilation

System compilation

Compilation / Parameters

Preferences Compilation/Parameters

This tab gives access to compilation settings.

Figure 326: Compilation

Automatic window close on successful compilation

Automatic window close on successful compilation: The status of this checkbox determines the behavior of the System Compilation dialog box which appears when the executable for the model is being created. If the box is enabled (ticked), the dialog box disappears when the executable is successfully created. If it is disabled, you must click on the Close button.

Debug by default

For most people this checkbox should stay disabled (unticked). People who know how to use a source code debugger can select this checkbox to ensure the executable is created in debug mode.

Automatically add missing libraries in path list

Compilation, Missing Path list or Libraries

If your Category path list does not contain all the libraries necessary to compile your model, the following dialog box appears when you switch to Parameter or Simulation mode:

This dialog box lists any libraries necessary to the model which are not currently in your Path List. Click Yes to automatically add those libraries to your Path List. If you click No, Simcenter Amesim will attempt to compile the model, but compilation will probably fail. If you click Cancel, the dialog box closes, and you remain in Sketch or Submodel mode.

Note

You can deselect any of the libraries in the list in order not to add them to the path list, but compilation of the model may fail.

If you select the Automatically add missing libraries in path list checkbox, the Compilation: libraries used in the model vs. Path List dialog box no longer appears when missing libraries are detected, and those libraries are automatically added to the path list when necessary.

Warning

This option requires that you have enough licenses for each library to be added. Adding libraries to the path list is under the control of the licensing policy. If you have a limited number of licenses for a library, this might prevent its addition to the path list.

If a user library is not available, the dialog box displays a warning message:

In the above screenshot, we see that in addition to the Mechanical library not being present in the Path List, a user library C:\AMETest\submodels is unavailable.

Note

Path list updates are saved between Simcenter Amesim sessions. If a library is added to the path list by the automatic mechanism, the path list will be saved containing the new library.

Use reduced code compilation

This feature utilizes enhancements from the new submodel signature (code version 2.0) by which you can minimize the size of compiled C code and other artifacts. By default, this option is enabled, providing you with faster compilation times if all submodels in the system are compatible. If any submodel is incompatible, the system reverts to the previous compilation routines. If the option is disabled and all submodels are compatible, the legacy code generation process is used.

Active compiler

Simcenter Amesim needs a compiler to produce the executable file of your system.

The compiler allows you to enter Parameter mode. At this stage, Simcenter Amesim produces a .exe file to run the system.

Active compiler - Windows	Active compiler - Linux

Windows Three compilers may be used with Simcenter Amesim: Microsoft Visual C++, the GCC compiler and the Intel oneAPI compiler. GCC is under the GNU general public license. Naturally your choice depends on which of these is installed. You must at least have one of these installed. Linux Two compilers may be used with Simcenter Amesim: the GCC compiler and the Intel oneAPI compiler. GCC is under the GNU general public license. Naturally your choice depends on which of these is installed. You must at least have one of these installed. Both You should ask your administrator which compilers are installed for Simcenter Amesim. Then you can set your current compiler in the Preferences. If you want to change the active compiler, you must check if any of your previous systems used home-made submodels or libraries. If this is the case, you must recompile these submodels by using Submodel Editor with the new active compiler and libraries with batch command files.

Intel oneAPI Compiler

The Intel oneAPI compiler generates binaries that are optimized for Intel oneAPI processors. Windows and Linux users having processors can expect simulation time reductions of twenty per cent (20%) on all models by using this compiler. Please note also that similar speedups may be obtained on other processors such as AMD.

Using Submodels written in Fortran under Windows

Intel Visual Fortran is no longer supported as of Simcenter Amesim 2504. Please use GCC’s Fortran compiler if you want to compile Fortran submodels.

Using Submodels written in Fortran under Linux

If you have a submodel written in Fortran you must configure Simcenter Amesim so that it can use submodels compiled with the Fortran compiler dedicated to your operating system:

Procedure

1. Make a copy of the AME.make file (which is located in the Simcenter Amesim installation directory), copy it to a working directory and modify it as follows.

2. Change the AME.make file as follows:

For Sun (Solaris 2.6 or higher): Copy$(CC) -I$(AME)/lib -c $(CC) -lF77 -lsunmath

For Linux:

For g77 Copy$(CC) -I$(AME)/lib -c $(CC) -lg2c

For f77 Copy$(CC) -I$(AME)/lib -c $(CC) -lf2c

3. Add the working directory containing your modified AME.make file to the path list in Simcenter Amesim.

Encrypted supercomponents

The supercomponent encryption mechanism has evolved greatly since Rev 11 in comparison with older versions of Component Customization and Simcenter Amesim. The major change concerns the compilation of constituent submodel code in a dedicated library.

This new method has been judged far more robust against reverse engineering. However, it is still possible to use the former encryption mechanism in Simcenter Amesim by selecting the Use old encryption method checkbox.

Figure 327: Use old encryption mechanism checkbox

Selecting this option is reversible: a supercomponent encrypted with the new method can be ‘downgraded’ to the old method by saving it again after the Use old encryption method checkbox has been selected.

If the supercomponent is already being used in a model, the Model update assistant must be applied to update the model. The Model update assistant facility will detect the encryption method and update the supercomponent concerned.

Click the Compiler Settings button to open the corresponding dialog box:

Figure 328: Compiler Settings dialog box

During each save operation, the encrypted supercomponent is recompiled. Note that it can be compiled for more than one compiler at the same time. The list of compilers to be used is available in Compiler Settings dialog box (see figure above).

The list of possible compilers depends on the platform.

Note

No check as to the presence of a compiler is performed at this stage. It is the responsibility of the user to ensure that the required compilers are correctly installed on the machine.