-
Notifications
You must be signed in to change notification settings - Fork 122
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 and WPIMULT for use in PyAction #5467
base: master
Are you sure you want to change the base?
Activate WELPI and WPIMULT for use in PyAction #5467
Conversation
8d29f0f
to
ef10afa
Compare
ef10afa
to
fa911bd
Compare
fa911bd
to
5157e95
Compare
ea366df
to
955db92
Compare
I am not sure how the performance implications of this are. It seems like we now always get all the WELPI of all wells even without any PYACTION if there is an actionx (even without WELPI). This is more information/computation then we need. Do you see a possibility to get only the needed ones if there is no PYACTION? I think getting them at once is an improvement. |
Should we reset the welpimap in the schedule somewhen? |
7c8173d
to
91338bd
Compare
91338bd
to
465b895
Compare
…to a pyaction call; fetch the wellPImap once, before the execution of potential PyActions and ActionXs
465b895
to
83f2485
Compare
For the reference manual: With this PR and OPM/opm-common#4136, the keywords WELPI and WPIMULT can be used in the "insert keywords"-function in Pyaction.