Skip to content
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

Experiments with simplified Norne model #333

Open
6 tasks
edubarrosTNO opened this issue Feb 18, 2021 · 2 comments · May be fixed by equinor/flownet-testdata#38
Open
6 tasks

Experiments with simplified Norne model #333

edubarrosTNO opened this issue Feb 18, 2021 · 2 comments · May be fixed by equinor/flownet-testdata#38
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@edubarrosTNO
Copy link
Contributor

edubarrosTNO commented Feb 18, 2021

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 fault handling):

  • Base case: perforation_strategy: bottom_point, disabling removal of connections through non-reservoir (can we easily disable that?), no layers, additional_flow_nodes: 50
  • Base case + perforation_strategy: multiple_based_on_workovers
  • Base case + perforation_strategy: multiple_based_on_workovers + removal of connections through non-reservoir
  • Base case + perforation_strategy: multiple_based_on_workovers + removal of connections through non-reservoir + additional_flow_nodes: 100
  • Base case + perforation_strategy: multiple_based_on_workovers + removal of connections through non-reservoir + layers: [[1, 4], [5, 22]]
  • Base case + perforation_strategy: multiple_based_on_workovers + removal of connections through non-reservoir + layers: [[1, 4], [5, 10], [11, 22]]
@edubarrosTNO edubarrosTNO added help wanted Extra attention is needed question Further information is requested labels Feb 18, 2021
@olwijn
Copy link
Collaborator

olwijn commented Feb 18, 2021

Any reason to choose this particular division between the 2nd and 3rd layer (we proposed k=15 before as lowest index for layer 2)? I suggest to explicitly define also other aspects of the base case: 100 additional nodes, BHP data with 0.1% error, minimum of 5 bar?, all instantaneous rates with 1% relative error and minimum error of ??, no resampling, ensemble size 1000 (or whatever we think we can afford), 10 iterations with weights 4,2,1,1,etc., schedule with constant rates, no gas injection, simulation period until ??, parameter type individual, no use of the region option, and some fixed initial distributions (use uniform permeability!), no aquifer. Since the distribution parameters are a bit difficult to list, we should store and distribute the base case config for reference. Do we use the "constraining" functionality at all? Also the number of additional nodes could be tested as part of the "geometry" experiments. Is there anything related to the treatment of faults and removal of connections that is relevant here?

@edubarrosTNO
Copy link
Contributor Author

No particular reason for the layering setting, it can be k = 15 (just changed it in the list above). Also added one experiment with variation of number of additional nodes (base case = 50, then 100). For the other settings, I think it is better to do as you say (distribute the base case config), my intention here was to focus on geometrical aspects for now. For the faults, I guess it would be interesting to see the impact of removing connections across sealing faults.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants