-
Notifications
You must be signed in to change notification settings - Fork 44
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
anything in parser changed recenlty causes the folllowing problem? #876
Comments
Nothing new - it is just printing 'old news'; however we should probably print a bit more selectively. |
This is one important keyword though. It causes the simulation broken. |
Okay. It is not something related to parser, I will check that PR. |
Then it was never working. |
I will check about it. NOT sure about that. The simulation has been working for more than one year. |
If so, then it's despite PLMIXPAR not being supported. As @joakim-hove points out, OPM/opm-simulators#756 doesn't add anything new. edit: actually, the message itself might be wrong. opm/polymer/PolymerProperties picks up on it. |
The PR in question was PURELY cosmetic, you are looking at a false positive. |
I am not sure where to look at now. I will test a little to find out. Thanks for the information. If you have some other places to suggest, please let me know. It should be something very recently. |
Please - the only ting you should do is to submit a PR where you remove the PLMIXPAR keyword from the list of not supported keywords. |
Yes. You arre right. I will correct that list. Something else happened after the recent relese changed the iteration behavior, generating some too large residual and causes the simulation restart for the first step, I will take a look at that later. |
I did not see this problem before. There are some useful keywords are claimed
not supported
.The text was updated successfully, but these errors were encountered: