Run details

Open run details dialog

When a simulation run is complete, the Open run details dialog icon becomes available. Click this icon to open the Run Details dialog box.

Figure 277: Run Details

If there have been errors during the simulation, the information icon displays a warning symbol .

If the simulation failed, the symbol is displayed.

You can use the Warning/Errors and Info buttons to toggle the display of information and warning messages off and on.

Figure 278: Simulation log

Note

With small systems, CPU times are very small and very inaccurate. They can be considered meaningless. For larger systems CPU times are more meaningful.

A warning or error message indicates the submodel responsible, and you can click on the line in the Run Details dialog box to highlight the submodel in the sketch.

If you have performed a batch run, you can select individual runs to display their information/warning messages.

Note

In case of excessively slow simulations or errors see How do I speed up my simulation for solutions and tips.

Raise on first error

Raise on first error

When the Raise on first error checkbox is selected, the Run Details dialog box opens automatically as soon as a simulation warning or error is detected. This is the default option. You can de-select this checkbox to prevent the Run Details dialog box opening on detection of errors.

Export

Once a run is complete, you can export the info and warning/error messages to a file. When you click the Export button, the Export Simulation Details file browser opens, allowing you to save the file locally, in .txt or .xml format.

Record of discontinuities

Discontinuities Record of

Figure 279: Discontinuities printout

If Discontinuities printout is enabled in Dynamic run options, extra data are put into the .results file and in addition, a record of the discontinuity is displayed in the simulation log. You can use the Discontinuities button to filter the run details to show discontinuities.

Figure 280: Discontinuities list

You can use scroll bars to examine the complete log. You can also click on a line to identify the submodel in the sketch.

Figure 281: Locating a submodel

Warnings/Errors report

Stabilizing run diagnostics

Warnings/Errors report

This report contains description of incidents in runs where there may have been a problem.

Warning messages in a run

Error messages in a run

Submodels in Simcenter Amesim libraries check the parameters they are given. If they find some questionable data they will stop the simulation run or issue a warning message according to the level of severity.

Figure 282: Warning message

Panic step reduction error messages

Panic step reductions

In some Simcenter Amesim submodels a check is made to ensure that certain physical quantities do not achieve unrealistic values. Common examples are absolute pressures and absolute temperatures that become negative. Usually the integrator can fix the problem itself without you knowing any problem occurred. However, in some cases it cannot, and the problem persists (repeated requested for step reductions) to the extent that the run has to be stopped.

Figure 283: Click on the message to find the submodel in the sketch

The cause may be the following:

• The integrator is going too fast and needs to be restricted. Follow the advice by setting a much lower maximum step size, enabling the Cautious option or reducing the tolerance.

• There is a bad parameter data in a submodel.

• System physically impossible

The model is physically impossible and must be totally revised. Below is a very simple example which was used to create the message shown in the figure above. The component on the left is removing 1 L of fluid every minute from the pipe. The other end of the pipe is blocked. The simulation runs until all fluid is removed from the pipe and then it has to fail.

Figure 284: Physically impossible example

The report indicates the submodel where the problem occurs. If you have persistent problems:

1. Investigate the parameters of the submodel indicated.

2. Plot graphs of variables in this submodel.

3. Do a continuation run specifying a much smaller print interval and a final time just before the time the report indicates the problem occurred and then repeat step 2 above.