Understanding Simulation Logs
Helping you get familiar with simulation and compilation logs and errors
If everything ran smoothly, you may see some statistics and other informational logs:
If the model could not be compiled, you might see error logs at the “Compiler” level. In this case, the simulation will not run and no visualizer data will be available.
Quite often, these logs will come from the model compiler itself. While the errors can be quite hard to decipher, they will usually carry some information that might help you debug your models.
Each message contains a timestamp, the context in which it appeared (Compiler or Simulator), a log level that is one of INFO, WARNING or ERROR, and a human-readable message. Below the message you may see more detailed information about the error itself that might help in debugging the model.
Once compiled, the model runs as the “Simulator” and can emit various logs. In general, no special message gets emitted, but if the solver failed to converge, some warnings or error messages may appear under Simulator logs.
In the below example, the solver failed to find a solution with a function that diverged towards infinity: