Hello;
following the discussion of how to best implement transmissibility multipliers,
I have thought briefly of how we could support MULT(???) transmissibility
modifier keywords in the Schedule section. Now I still strongly believe we
should not think seriously about this on the current side of 2015, but my
thoughts on the topic might be interesting and applicable also for more
standard Schedule event like new wells and completions:
I suggest that we update an integer flags mask during the Schedule parse
process which the consumer can consult to determine which changes have
occurred, and which simulator internal quantities must be recalculated. I.e.
the consumer could have code like this:
if (scheduleFlags(WELL_RATES_CHANGED))
updateWellRates();
if (scheduleFlags(WELL_TOPOLOGY_CHANGED))
updateWellTopology();
if (scheduleFlags(WELL_COMPLETIONS_CHANGED))
updateCompletions();
In 95% of the timesteps only the first test will return True. Something to
think about?
Jaokim
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
