An error notification in CONVERGE is usually followed by termination of the simulation. Errors typically fall into three categories. Table 5 below lists these types and gives examples for each type.
Table 5: Most common causes of errors in CONVERGE with examples.
Error Type |
Example |
Explanation of example |
Missing inputs
|
initialized species not found in mech.dat |
This error means that 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 |
This error means that 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 |
This error means that 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 |
This error means that 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 |
This error means that the specified models or submodels did not converge to specified tolerances. |