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

Long connections across Norne separate regions to be removed #282

Closed
edubarrosTNO opened this issue Dec 4, 2020 · 2 comments · Fixed by #298
Closed

Long connections across Norne separate regions to be removed #282

edubarrosTNO opened this issue Dec 4, 2020 · 2 comments · Fixed by #298
Assignees
Labels
bug Something isn't working

Comments

@edubarrosTNO
Copy link
Contributor

edubarrosTNO commented Dec 4, 2020

While inspecting the grid of one of the FlowNet realizations of Norne, it was observed that extremely long connections are appearing between well nodes in the two "tentacles" of the model. A fixed maximum distance value should be used to determine connections to be removed instead of a fraction as it is currently set up

image

@edubarrosTNO edubarrosTNO added the bug Something isn't working label Dec 4, 2020
@wouterjdb
Copy link
Collaborator

Already supported!

"max_distance": {MK.Type: types.Number, MK.Default: 1e12},

@wouterjdb
Copy link
Collaborator

wouterjdb commented Dec 4, 2020

I actually think that what is the problem is that we should remove connections that go through non-reservoir as just setting the max distance is not enough:

The distance over the tentacles is ~2400m; whereas the distance from the tentacle to the F-4H injector is ~2500m. That would mean that in this way of defining what needs to be removed there will never be communication between the injector and the producer in the tentacle. This problem only occurs if we do not add any additional nodes. If you add a few extra nodes you'd most likely end up with nodes being place between the injector and producer in the tentacle as the distances are large there.

Another potential solution could be to recognize that part of the model is a completely different (disconnected) area and could be its own FlowNet? 🤔

@wouterjdb wouterjdb reopened this Dec 4, 2020
@wouterjdb wouterjdb self-assigned this Jan 7, 2021
@wouterjdb wouterjdb mentioned this issue Jan 7, 2021
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants