Uploading a model

Instead of saving your files locally, you can use the Simcenter System Simulation Client for Git. When you open or save a file, you can select the Client for Git tab.

Figure 453: Client for Git tab

1. Set the following information in the corresponding fields:

Collection Name: Modify the filename as required. The default name is the current model name.

Branch Name: Enter a branch name as required. The default name is your user name

Classification: Select a classification from the drop-down list.

Local collection path: Click the browse button to modify the local collection path as required. If this path has not been defined in the Workspace Path field in the Simcenter Amesim Preferences > Model Management tab, you are obliged to specify a path here in order to be able to publish the model.

Message: This field is not editable. It displays any important messages to the user, such as if any required files are missing:

2. Click Create Collection.

The Collection Editor opens. Figure 454: Collection Editor

When a user clicks Create Collection, a local collection is created so that the user can view the collection structure, add attributes if needed, and then upload to the Client for Git server.

3. Click Upload Model.

Library dependencies

If your model has library dependencies, you can publish your model together with its libraries in the same process.

Figure 455: Model with library dependencies

Uploading a model with encrypted supercomponents

If your model contains encrypted supercomponents, the libraries they are saved in will be uploaded along with the model.

If the child library of an encrypted supercomponent has no dependencies on internal static or dynamic libraries (.lib, .a, .dll), it will not be uploaded to Client for Git as a dependent library, because the information of this library has been embedded in the encrypted supercomponent.

However, if there are dependencies on internal static or dynamic libraries (.lib, .a, .dll), the child library will be uploaded to Client for Git as these libraries are necessary for simulation.

To correctly handle your library internal dependencies, make sure you use the .make file to declare the dependencies and put the library files into the lib folder. For more information, refer to the The AME.make file section.

For information on how to upload libraries independently, refer to Uploading a library.