Managing Modelica Versions and Dependencies for Libraries and Behaviors

You can use the command Modelica Version and Dependencies to modify, for Dymola behavior libraries, the Modelica attribute Library Version, and the dependencies (libraries used). The dependencies can also be managed for functional and logical Modelica behaviors.

For dependencies, more precisely, you can:

  • Change versions of libraries used, that is, the 'uses' Modelica clause
  • Add libraries used
  • Remove libraries used

Important: If you want to store the changes as a new library revision with a new Modelica version, you must first create a new revision by the command New Library PLM Revision. If you use only the command Modelica Version and Dependencies, the previous file is overwritten in the database when saving the new file.
Tip: If you have versioning issues in a Modelica library or behavior, consider using the Versioning Assistant. The Versioning Assistant includes also this command.

This task shows you how to:

See Also
About Versioning and Dependencies of Behavior Libraries and Modelica Behaviors
Working with the Versioning Assistant
Creating a New Library PLM Revision with a New Modelica Version

Select Behavior Libraries or Modelica Behaviors to Manage

You can manage behaviors or libraries, whether they are loaded or not loaded in your session.

Select Libraries from Your Session

You can select libraries from your session.

  1. From your session, select libraries from the Package Browser or from the Component Browser

    Notes:
    • You can select libraries by selecting them in the top level, but also by selecting classes in them.
    • You can multiselect by pressing Ctrl on the keyboard when selecting.

  2. From the Behavior Authoring section of the action bar, click Modelica Versions and Dependencies .
    The Versioning dialog box appears, displaying the selected libraries.

Select Behavior Libraries or Dynamic Behaviors from the Database

You can select behavior libraries or dynamic behaviors from the database.

Before you begin: No component should be selected.
  1. From the Behavior Authoring section of the action bar, click Modelica Versions and Dependencies .
    An empty Versioning dialog box appears.
  2. Depending on what you want to add, click Behavior Library or Functional or Logical Behavior.
    The Content Chooser dialog box is displayed.
  3. Use the Content Chooser to do any of the following:

    For more about the Content Chooser, see Selecting Objects Using the Content Chooser.

    • Select or multiselect from the tree.

      To multiselect, you must activate Multiselection.

      Important: You cannot select from the Package Browser.
    • Use the Search box of the top bar to search and then select or multiselect from the result.

      To multiselect, you must activate Multiselection.

      Tip: Enter the name of the library in the Search box and press Enter to search. The wildcard * can be used.

      For general information about search, see About 3DSearch Queries.

    Important: This selection does not open the functional or logical behaviors or behavior libraries.

The Versioning dialog box displays the selected libraries or behaviors, like in the figure above.

Modify the Modelica Version of Selected Behavior Libraries

You can modify the Modelica attribute Library version of behavior libraries.

Important: If you want to store the changes as a new library revision with a new Modelica version, you must first create a new revision by the command New Library PLM Revision. If you use only the command Modelica Version and Dependencies, the previous file is overwritten in the database when saving the new file.

Before you begin: Display components in the Versioning dialog box according to the selection section above.
  1. To modify the Modelica version of a library, edit the Modelica Version box from the Selected Libraries area.

    Important:
    • This box modifies the Modelica text (the "uses" clause).
    • This box is only available for editable libraries.

  2. Optional: To specify additional information, right-click any column header and select Show All Columns.
    Additional columns appear.
    • Version Build Number: specifies the minimum version that should be used for the library. However, this information has no impact on the usage of the library.

      For example, if you recommend "LibToUse version 1.0" version build 3 or above, you can specify the value of the Version Build column to 3 in the list of used libraries. However, any version build can be used.

    • Version Date: specifies the date of the version.
    • Date Modified: specifies the modification date of the version.
    • Revision: specifies an identifier for the revision.
  3. Optional: Enter values in the relevant boxes.
  4. If relevant, consider changing dependencies before going to the next step. See below section.
  5. Click OK to validate the changes.
    Note: If the version build number does not correspond to that of the linked library, a warning message appears. You can close the warning message and use the not recommended version build, or reopen the dialog box and change the version build number.
  6. Select Share > Save to save the changes.

Modify the Dependencies of Behavior Libraries or Functional or Logical Dynamic Behaviors

You can modify dependencies (library versions used) by changing versions of libraries used, adding library dependencies, or removing library dependencies.

Important: If you want to store the changes as a new library revision with a new Modelica version, you must first create a new revision by the command New Library PLM Revision. If you use only the command Modelica Version and Dependencies, the previous file is overwritten in the database when saving the new file.

Before you begin: Display components in the Versioning dialog box according to the selection section above.
  1. To modify the library version of a library used by the selected library or behavior, do the following:
    1. If the library is indicated by a padlock in the Status column, the library with this version is loaded in session and you cannot change the version. Right-click and select Unload uses.
      The result is:
      • The library is unloaded from session.
      • The library is unlocked in the dialog box and you can change the version.
    2. Select another library version from the list in the Libraries used in the selected component area (see figure above).

    • You can select:
      • Any library version from the database, provided that a version of the library is not loaded in session.
      • The current library version for a library that is loaded in session.
    • You must have license for a library to be able to select it. If you do not, this is indicated by the icon in the Status column.

    Once a new library version for the library to be used is selected, a conversion script might be proposed from the Conversion Script column.
    Warning: We strongly advise not to clear the Conversion Script option. If you convert the library without using this conversion script, important changes could be lost. Clearing the Conversion Script option is for an advanced user only.
  2. To add a dependency of a library version for the selected components, do the following:

    Important: The dependency (uses clause) is used when loading the library, to specify what version to be loaded. If there is no demand for a specific version of a library for any of the selected components, do not add any dependency (uses clause) for that library.

    1. Click the Add a library to use: box.
    2. Select a library in the Package Browser

      You cannot add a library that is not loaded in the Package Browser.

    3. Click Add.
      The library is displayed in the Libraries used in the selected component area, with a plus in the Status column.
  3. To remove a dependency of a library version for selected components, clear it in the Libraries used in the selected component area, the Status column.

    Clearing a library only means that you remove the demands for a specific version of that library when loading it for any of the selected components.

  4. For behavior libraries, if relevant, consider changing the Modelica version before going to the next step. See above and below section.
  5. Click OK to validate the changes.
  6. If you have unloaded any library to be able to change the version, reload the library.
  7. Select Share > Save to save the changes.