-
Notifications
You must be signed in to change notification settings - Fork 238
DASPK error after attempted model resurrection #1258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So if you have the latest model resurrection related commit this should only happen if your edge is entirely empty. Is that the case? |
Maybe? Two lines above the traceback, it prints
but the latest log about the edge after model enlargement was
|
Ok, this may be related to how I fill variables before the first time step, although I'm pretty sure I tested failures on the first time step pretty well. Perhaps a more useful question might be why is it trying to go from 0.0 to 100000 sec in one step?...What time did that last simulation end at? What's the context of the last species it added? To my understanding it should try to step 1e-12 and then shrink it if necessary for the first step. |
This is what I have before the error for one of the simulations:
and this is what I have for the other simulation:
No idea why it's trying to step that far. |
Do you have filterReactions=True? Is this the first time it tried model resurrection in the run? Model resurrection seems to be behaving oddly here. Can you run the MR_test example (shouldn't take long ~2 min) and tell me if it ends with model resurrection failing? The DASPK error is probably a result of you having bad thermo. I should also note that model resurrection even when it succeeds does not always fix your run...if the thermo is bad enough the model will continue to get DASPK errors each run causing it to resurrect again, which means you're really just adding the highest flux edge species at t=0 each iteration. Sometimes it will go through 5 or so of these cycles and then recover, other times it never recovers. |
Yes, Most thermo is group additivity so it's totally possible that there is bad thermo in there; however, I don't really understand why I should suddenly be getting significantly worse thermo after adding phenol when the simulations run fine without it. |
Hmm...so MR_test was design to test an issue that looks very similar to this. If it isn't that issue in order to debug it I need to be able to reproduce it. Do you have the core and edge seed mechanisms for one of these runs? I've only seen DASPK errors avoid in two ways: get rid of the offending reactor or improve your thermo estimates. Why DASPK errors occur as a function of an RMG job is not particularly well understood, but I think adding the phenol could do it if its concentrated enough. |
I don't have the seed mechanisms right now. I just started a job in which I generate those, so I'll get those to you once the error occurs again. Phenol is present at a concentration of 1%. How would I tell which thermo estimates are causing the issue? |
Ok, send it to me when you get it and I'll take a look at the issue. In my experience it's usually the thermo you would expect to be sensitive. In this case since you've added phenol I think its likely the problem is the thermo involved in reactions with phenol, but it could still be something else. In my experiences it was just a matter of not using thermo libraries I should have been using, your case is significantly trickier. To be honest you might want to consider changing surrogates rather than trying to fix this problem. |
It seems the model does not crash when running it without |
I also got the similar error in few runs these day. The unexpected thing was that after the error showed up, RMG seemed to stay on for few reaction systems until system 16 (the last line). Even though the last time said "surface initialization complete", the RMG job basically froze. Log file was not updated anymore, but the RMG server showed that the job is still active. The last lines on log files are shown below: Conducting simulation of reaction system 9... Conducting simulation of reaction system 10... Conducting simulation of reaction system 11... Conducting simulation of reaction system 12... Conducting simulation of reaction system 13... Conducting simulation of reaction system 14... Conducting simulation of reaction system 15... Conducting simulation of reaction system 16... |
@jimchu10 it looks like resurrection functioned properly for your system, I'm not sure what's causing it to hang on system 16, but you aren't getting a model resurrection failure. |
@mjohnson541 Thank you for the comment. I will look into the problem in detail to see if the source can be identified. This problem happens when I set the tolerance to be very low, but not sure whether it is related. |
This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days. |
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:
[...]
Evidently, model resurrection was not able to fix the simulation. Any ideas on how to avoid the error?
The text was updated successfully, but these errors were encountered: