-
Notifications
You must be signed in to change notification settings - Fork 112
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
Activate WELPI for use in PYACTION #4133
Conversation
jenkins is not ready, please don't. |
Ah ok :) - thanks! |
…the WELPI keyword and not only for ActionX but also for Pyaction
…ord from a Pyaction
e69f084
to
49c2386
Compare
jenkins build this opm-simulators=5463 opm-tests=1190 please |
mmh. Somehow this looks like the timestepping did change for the existing regression test mpi.compareParallelSim_flow+ACTIONX_WELPI
|
This is a test that I actually added, yet this should still pass.... |
@@ -1640,6 +1646,8 @@ File {} line {}.)", pattern, location.keyword, location.filename, location.linen | |||
|
|||
|
|||
SimulatorUpdate Schedule::runPyAction(std::size_t reportStep, const Action::PyAction& pyaction, Action::State& action_state, EclipseState& ecl_state, SummaryState& summary_state) { | |||
// Set welpi_action_mode to true, this is necessary for the keyword WELPI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you should explain why?
@blattms: I quickly checked: this test (which compares the parallel to the sequential run) also fails with the flow version I had compiled from the 2024.04 release ... |
I thought you added the PYACTION test PYACTION_WELPI_INSERT_KW.DATA, but here the comparison of ACTIONX_WELPI.DATA with the reference run fails. |
I've added three tests:
|
Thanks for clarifying, those tests might actually fail, I've removed them now. |
Closing, since #4136 contains everything relevant from this one |
Test is in opm-tests