Eduardo Gonçalves Dias de Barros
Eduardo Gonçalves Dias de Barros
*Enables `flownet ahm` to run ERT in `ensemble_experiment` mode to facilitate evaluation of prior ensemble only* --- ### Contributor checklist - [x] :tada: This PR closes #447. - [x] :scroll:...
In preparation for upcoming runs in large models, we need to verify if FlowNet still runs smoothly with the LSF job scheduler on Equinor computational environment.
When inspecting the SCHEDULE file generated by FlowNet, it can be hard to know which well connections in the COMPDAT section are associated with each flow tubes and respective layers...
I have tried to run the Norne reference simulation from https://github.com/equinor/flownet-testdata with OPM-Flow enabling the tracer model option: `flow NORNE_ATW2013.DATA --enable-tracer-model=true` And I ran into the following issues: 1. The...
During our FlowNet discussions this week, we saw examples by @tayloris where estimating well connection factors through HM (besides the other tube flow properties) helped to better constrain BHP response...
Proposed list of experiments with the simplified Norne model to verify the impact of the latest geometry-related FlowNet features (**_still missing what we could enable / disable in terms of...
Currently FlowNet simulations in prediction mode are only performed for the ensemble of the last completed iteration of the history matching results provided as input. However, there may be cases...
I was trying to set up an example using both the `layer` and `aquifer` functionalities when I realized that I do not know how the aquifer nodes are being added...
Currently, for every FlowNet run, an empty file called `SCHEDULE.inc` is created. I think this file was originally intended to allow for a static file to be provided with prescribed...
A couple of questions to think about: - Are BHP observations during shut-in periods being matched? - Does it make sense to match these observations? - Are they helping to...