Cloud integration

AnyLogic 9 works closely with AnyLogic Cloud, borrowing its version control and model execution functionality.

When you work with your model in the AnyLogic editor, all changes you make to the model are periodically saved in AnyLogic Cloud in the corresponding model version. To command the editor to upload the changes explicitly, click the Unsaved changes label on the toolbar.

To run the AnyLogic 9 model via Cloud

1. On the AnyLogic 9 toolbar, click .
2. The dialog window will open up, showing the model’s animation in vector graphics. You can then control the execution flow, using the buttons on the bottom toolbar of the window.
   To learn more, see Model animation in AnyLogic Cloud in Cloud documentation.

To create Cloud-based experiments for the AnyLogic 9 model

1. On the AnyLogic 9 toolbar, click the arrow icon on the right of the icon to open the drop-down menu.
2. Click Open experiments.
3. The experiment dashboard will open up, allowing you to customize the model’s inputs and outputs to your liking.
   • In Inputs, modify the model version’s parameters and their values.
   • In Outputs, set up the graphical charts and their layout on the experiment screen.

By default, Cloud creates a basic simulation experiment for each model automatically. Consider creating additional, more complex experiments: for example, a parameter variation or Monte-Carlo 1^st order experiment.

To learn more about experiments in Cloud, see Experiments.

When you perform an action in AnyLogic Cloud, it can trigger either an outbound or inbound update between Cloud and the model editor, depending on the type of action.

• Outbound update (synchronization): When a user with the necessary access level makes changes to a model, AnyLogic Cloud instructs the editor to save, build, and store the updated version of the model.
• Inbound update (database update): Before performing an action, AnyLogic Cloud ensures that it is using the latest version of the model. If the model is outdated, Cloud will automatically switch to the latest version before proceeding.

This ensures that changes are properly synchronized between the Cloud and the model editor.

As a rule of thumb, to trigger the synchronization, you must be a model developer or the administrator of the Private Cloud instance. For generic users and guests, the database update is triggered when they run the model, start the model animation, or download the model sources.

For the following actions, neither type of update is triggered and you will work with the same state of the model which was effective at the moment the AnyLogic Cloud screen was opened: downloading results (either completed runs or individual experiment results), comparing runs, changes in Cloud experiment or version metadata (for example, renaming).

How can we improve this article?

Send