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

Add well connection factors as HM parameter #419

Open
edubarrosTNO opened this issue Jun 24, 2021 · 4 comments
Open

Add well connection factors as HM parameter #419

edubarrosTNO opened this issue Jun 24, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@edubarrosTNO
Copy link
Contributor

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 of flow network models. Given recent difficulties of matching pressures in the Norne case, enabling the estimation of well connection factors within the FlowNet framework is expected to contribute to an improved match

@edubarrosTNO edubarrosTNO added the enhancement New feature or request label Jun 24, 2021
@edubarrosTNO edubarrosTNO added this to the HM open Norne Model milestone Jun 24, 2021
@tayloris
Copy link
Collaborator

Yes, the well productivity index WI has a direct impact on good BHP prediction.
So I think one the first task would be to create a WI class, similar to _porv_poro_trans.py to do the rendering of the parameter values.

@tayloris
Copy link
Collaborator

I think that the sections WELSPECS and COMPDAT from HISTORY_SCHEDULE should be indluded in a separate file SCHEDULE to facilitate the rendering of the CONFACT parameters.

@edubarrosTNO
Copy link
Contributor Author

I completely agree with you, @tayloris . I made the same suggestion in the past, to split SCHEDULE and COMPDAT files but the issue didn't get prioritized - back then it was just to improve readability of the generated SCHEDULE file, but now it looks like it would help code-wise.

A question that comes up then is how to approach this estimation of well connection factor parameters when we have multiple instances of the COMPDAT keyword for the same well in the schedule, i.e. workover in time throughout the simulation. Any thoughts here? I guess that in your Egg model example the well connections were kept fixed through the simulation, right?

@tayloris
Copy link
Collaborator

Yes, in the case of workover you increase the numbers of connection factor parameters by the number of workovers.
This can make it complicated because we may need to render COMPDAT and WELLSPEC at each time step. Does Norne have workovers in some wells?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants