Model execution logs

AnyLogic automatically writes all essential statistics about the model execution in the log files. While the model runs, all information about agents, their parameters, movement, event occurrences, message arrivals, statechart, and flowchart activities, resource usage, etc. is written into the model execution log. See the detailed description of all standard AnyLogic logs here.

To make the model write information into the log, you have just to turn logging on.

Resources utilization log

To command the model to write information to the log

1. In the Projects view, click the model’s  Database item.
2. In the Properties view, expand the Log section, and select the option Log model execution.

   

AnyLogic enables the user to see the logs in a common table form, using the built-in database table editor.

To view the log

1. Stop the model execution and close the model window. It may take some time to dump the information and refresh the model tree in the Projects view.
2. In the Projects view, expand the  Database branch.
3. Expand the  Log item’s branch in the tree. You will see the list of logs in the Log branch.

   

4. Double-click the log to view its data. The log contents will be shown in the table form in the database table editor. AnyLogic logs are shown in read-only mode. You cannot modify the log data.

   

If the simulation takes significantly more time with the logging being turned on, you can disable data collection for some logs that you do not need.

To disable data collection for a log

1. After you simulated your model at least once and got the logs collected, expand the  Database branch in the Projects view.
2. Expand the  Log item’s branch in the tree. You will see the list of logs in the Log branch.
3. In the Projects tree, select the log you do not need, and select the I do not need this type of log checkbox in the properties.

Each predefined log requires some particular raw data to be collected. In the Projects tree, you can see them in the Raw data branch of the database’s Log. The more logs you need, the more related raw data will be collected.

Each log is in fact AnyLogic database view. If you want to create a similar log, you can create a copy of the predefined AnyLogic log, and modify its SQL query.

To create your own log based on a predefined log

1. Click the log in the Projects tree to open its properties.

   

2. In the Properties, click the link Create an editable copy of this view.
3. In the Projects view you will see a new database view created. It will be put in the  Database branch, but not in the  Log branch (where only AnyLogic predefined and non-editable views are placed).

   

4. The SQL query of this view is editable, so you can open the new view properties and customize its query as you need in the View definition field.

The log is stored in the model folder, in the sub-folder database storing all the data for the model’s built-in database.

In some cases you may want to delete the log. For instance, you are distributing your model by copying the model folder, and want to optimize the folder size. You should not delete the files in the file manager, because this will delete all the input and output data from the model database. To delete just the model execution logs, please follow this way:

To delete all model execution logs

1. In the Projects view, right-click the  Database branch, and choose Delete log from the context menu.

You can delete the logs programmatically at the model runtime using the deleteExistingLogObjects(java.sql.Connection connection) function.

The function is defined in the model database's ModelDatabase class. It deletes all the model log data (if any logs were turned on) from the model database. You should pass the database connection as its argument. Below we provide the code sample, which deletes the model execution logs. Since the function may throw java.sql.SQLException exception, you have to handle it with the try — catch operator:

try 
{
  getEngine().getModelDatabase().deleteExistingLogObjects(getDatabaseConnection());
}
catch (SQLException e)
{
  error("Error occurred while deleting the model execution logs: " + e);
};

When the model is exported to AnyLogic Cloud or the standalone Java application, the log is deleted automatically.

How can we improve this article?

Send