-
Notifications
You must be signed in to change notification settings - Fork 244
Closed as not planned
Labels
Type: Errorabandonedabandoned issue/PR as determined by actions botabandoned issue/PR as determined by actions botstalestale issue/PR as determined by actions botstale issue/PR as determined by actions bot
Description
I am trying to run two separate hydrocarbon oxidation simulations, which run fine by themselves. Upon adding a phenolic species to each job, I get DASPK errors for both jobs after ~160 species. Both errors look like this:
Error: Trying to step from time 0.0 to 100000.0 resulted in a solver (DASPK) error
Resurrecting Model...
Error: Model Resurrection has failed
[...]
Traceback (most recent call last):
File "/data1/cgrambow/Code/RMG-Py/rmg.py", line 173, in <module>
main()
File "/data1/cgrambow/Code/RMG-Py/rmg.py", line 167, in main
rmg.execute(**kwargs)
File "/data1/cgrambow/Code/RMG-Py/rmgpy/rmg/main.py", line 702, in execute
simulatorSettings = simulatorSettings,
File "rmgpy/solver/base.pyx", line 498, in rmgpy.solver.base.ReactionSystem.simulate (build/pyrex/rmgpy/solver/base.c:24537)
File "rmgpy/solver/base.pyx", line 678, in rmgpy.solver.base.ReactionSystem.simulate (build/pyrex/rmgpy/solver/base.c:15263)
ValueError: invalidObjects could not be filled during resurrection process
DASPK-- AT T (=R1) AND STEPSIZE H (=R2) THE
In above, R1 = 0.7945984920517D+05 R2 = 0.1598236102956D-04
DASPK-- NONLINEAR SOLVER FAILED TO CONVERGE
DASPK-- REPEATEDLY OR WITH ABS(H)=HMIN
Evidently, model resurrection was not able to fix the simulation. Any ideas on how to avoid the error?
Metadata
Metadata
Assignees
Labels
Type: Errorabandonedabandoned issue/PR as determined by actions botabandoned issue/PR as determined by actions botstalestale issue/PR as determined by actions botstale issue/PR as determined by actions bot