Simulation errors usually cause the simulation to crash. Table 8 below lists common types of these errors and gives examples for each type.
If a crash occurs in CONVERGE 3.2, a detailed stack trace is written to CONVERGE_error_rank<number>.log, where <number> indicates the processor rank on which the error occurred. If you need help resolving an error, send this file along with the main log file to the support team for your region.
Table 8: Common types of simulation errors with examples.
Error Type |
Example |
Explanation of example |
Missing inputs
|
initialized species not found in mech.dat |
A species with an initialized value in initialize.in is not part of the reaction mechanism specified in file mech.dat. |
must provide a file for an arbitrary moving boundary |
You have not supplied a motion file (e.g., arbitrary_motion.in) for an arbitrarily moving boundary. |
|
A mismatch between the specified input and the input CONVERGE expects based on the specified type of simulation |
boundary between disconnect regions can only translate or rotate |
You have specified a motion type for a boundary between two disconnected regions other than TR (Translating) or RO (Rotating). |
disconnect group between regions 0 1: CLOSED while attached boundary region 1 is moving |
A disconnect group between two regions has been defined as CLOSED while a boundary in region 1 is actually moving. All OPEN/CLOSE events must occur only when the boundaries adjacent to the disconnect triangles are stationary. |
|
Computational errors |
equilibrium solver did not converge |
The specified models or submodels did not converge to specified tolerances. |
Kill/termination signals |
Signal 9 |
The operating system has killed your simulation. This commonly occurs when you run out of memory. Try getting more memory, making the case smaller, or running the case on more nodes. |
Signal 15 |
Another program has terminated your simulation. This commonly occurs when a scheduled job runs out of time and is killed by the scheduler. |