CVODE EEROR #713
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
This type of CVODE error often is a symptom of problems that are unrelated to chemistry integration, but that cause CVODE to crash when it gets passed a bad state. As a first debugging step, I'd recommend dumping a plot file at the time step immediately before it crashes and looking for any issues in the state at that time (unexpectedly high or low temperatures, out of bounds mass fractions, etc), particularly near an EB surface if you have one. The issue may be related to the chemistry integration process, particularly for large/stiff mechanisms. In that case, adding refinement or reducing the CFL is sometimes sufficient. You can also try using a different solver within CVODE using the |
Beta Was this translation helpful? Give feedback.
-
Of all the chemistry mechanisms provided with Pele, the LiDryer is probably the most tested and one of the least stiff. To me, your symptoms really suggest that something is wrong elsewhere. I would carefully scan the run log information written to stdout, with particular attention on the temperature profiles and near the walls, and also simply plot the plot files leading up to the failure, looking especially near physical and coarse-fine boundaries. If you don't find anything obvious, you could try forking a copy of PeleC and pushing the complete setup of your case from scratch, then adding a note here on how we can reproduce what you see. Once you've done this, you may also want to find a different machine to see if you can reproduce the errors on - some times this can be helpful as well. |
Beta Was this translation helpful? Give feedback.
-
A couple other tips: When plotting T, e.g., and searching for weirdness, set the max in the color bar to 298 or something, as it makes it super easy to see low temperature cells. Also, try to isolate the exact time step where the temperature drops below ambient - ultimately, we're trying to diagnose whether it happens in a chemistry solve, or with the CFD part, and to do this, we need to narrow down which exact operation goes bad. |
Beta Was this translation helpful? Give feedback.
A couple other tips: When plotting T, e.g., and searching for weirdness, set the max in the color bar to 298 or something, as it makes it super easy to see low temperature cells. Also, try to isolate the exact time step where the temperature drops below ambient - ultimately, we're trying to diagnose whether it happens in a chemistry solve, or with the CFD part, and to do this, we need to narrow down which exact operation goes bad.