flownet-testdata's Introduction

Testdata for `flownet`

This repository contains some open example data to be used by https://github.com/equinor/flownet

If you only want to download the data, you can run

git clone --depth 1 https://github.com/equinor/flownet-testdata

That will download the content to a folder called flownet-testdata.

Upload of data

Remember that GitHub does not allow files larger than 100 MB, and will give a warning when pushing files larger that 50 MB. There is also a repository limit on 100 GB.

You can find files larger than e.g. 50 MB, recursively from your current directory, by running

find . -type f -size +50M

Occasionally it might be decided to remove repository history and "start fresh" to keep repository size as small as possible.

License / Acknowledgements

The Norne input model comes from the OPM project, where it is available under the Open Database License.
The Egg input model comes from 4TU.Centre for Research Data, where it is available under the General terms of use for4TU.CentreforResearch Data.

flownet-testdata's People

Contributors

Stargazers

Watchers

flownet-testdata's Issues

Necessary changes in Brugge reference simulation

In order to be able to better analyze FlowNet results in the Brugge example, the reference simulation should output some additional summary vectors. A few ones that I noticed to be missing are: FOPT, FWPT, FWIT, FOIP, FPR
The report dates are monthly during the first years of the reference simulation and every 6 months towards the last years. This causes the frequency of observations extracted from the reference simulation for the FlowNet runs to vary too much, which ends up giving too much weight on matching the reference simulation at earlier dates. We should enable monthly report dates throughout the entire simulated period. This will also improve the use of the resampling option to vary the frequency of the observations used for training the FlowNet ensemble

Test run fails with message "ERT workflow failed, check the ERT log for more details"

After execution of flownet in assisted history matching mode, using

flownet ahm assisted_history_matching.yml flownet_output/egg_8_9_10_16

the execution stops with the following traceback

    Traceback (most recent call last):
      File "/home/as/miniconda3/bin/flownet", line 8, in <module>
        sys.exit(main())
      File "/home/as/.local/lib/python3.8/site-packages/flownet/_command_line.py", line 295, in main
        args.func(args)
      File "/home/as/.local/lib/python3.8/site-packages/flownet/_command_line.py", line 90, in flownet_ahm
        run_flownet_history_matching(config, args)
      File "/home/as/.local/lib/python3.8/site-packages/flownet/ahm/_run_ahm.py", line 969, in run_flownet_history_matching
        _set_up_ahm_and_run_ert(network, schedule, parameters, config, args)
      File "/home/as/.local/lib/python3.8/site-packages/flownet/ahm/_run_ahm.py", line 68, in _set_up_ahm_and_run_ert
        ahm.run_ert(weights=config.ert.ensemble_weights)
      File "/home/as/.local/lib/python3.8/site-packages/flownet/ahm/_assisted_history_matching.py", line 104, in run_ert
        run_ert_subprocess(
      File "/home/as/.local/lib/python3.8/site-packages/flownet/ert/_run_subprocess.py", line 70, in run_ert_subprocess
        raise subprocess.SubprocessError(
    subprocess.SubprocessError: The ERT workflow failed. Check the ERT log for more details.

Kindly suggest steps to successfully demonstrate functionalities of the flownet, with test data.

Thank-you

Recommend Projects