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

Option for wells to display well head above first connection #10613

Open
EdmundStephens opened this issue Sep 15, 2023 · 3 comments
Open

Option for wells to display well head above first connection #10613

EdmundStephens opened this issue Sep 15, 2023 · 3 comments

Comments

@EdmundStephens
Copy link

EdmundStephens commented Sep 15, 2023

[v2023.06.0] Please can there be an option added in the properties to display the well head above the first connection. This can follow the existing interface in terms (e.g. Spheres etc.)

  • Simulation Wells / Visibility / WH Above First Connection ... all wells
  • Well objects / Visibility / WH Above First Connection ... individual wells

The main reason is that some products, e.g. tNavigator below, seem to wrongly export the 'IWEL' record for some wells, leading to this sort of view:
image
To be clear this is essentially a bug in those products, I have checked in the ascii format of FUNRST the 'IWEL' data for the well shows starts with {1, 1, 1, ...}, while the 'ICON' connection data starts {1, 148, 82, 44, ...}.

Another key situation when this would be useful arises when all wells have trajectories leading back to a platform or drill pad and then all the well heads appear together, unreadable names etc.

@magnesj
Copy link
Member

magnesj commented Sep 15, 2023

Thanks for the suggestion. We also have an improved concept for label display that could be used for well path labels.
#10597

@EdmundStephens
Copy link
Author

Great. Hopefully this mod not too difficult to arrange and may improve well display a lot in some models

@EdmundStephens
Copy link
Author

More information on this. The issue is coming from the tNav Model Designer, where they want to export the wells in a grid independent manner, so their WELSPECS has arguments 3-4 (IW,JW) defaulted. Then they define the trajectory and completion via WELLTRACK and COMPDATMD ... all independent of the grid IJK assumptions.

Example:

-- This file has been generated by tNavigator v19.1-1156-gec9e62b1325
-- Copyright (C) Rock Flow Dynamics 2003-2019.
-- All rights reserved.
WELSPECS
-- wname gname iw jw ref.depth phase radius inflow_flag shut-in_flag crossflow_ability_flag PVT_n density_type filt.tbl reserved reserved well_model_type polymer_mixing_tbl.n
'J01P' P_M1WEST 2* /
/
-- wname list: X Y Z MD
WELLTRACK 'J01P'
1664991.4698162729 1643475.3280839895 4432.414698162729 4514.435695538057
1664994.4549212596 1643475.9947834644 4797.653513779527 4879.691601049868

The tNav guys have this bug reported, and hopefully they will set a sensible default on IW,JW such as the I,J of the first connection. (For reference in Eclipse defaulting of the WELSPECS arguments 3-4 is not allowed and results in an error).

I do still think ResInsight could benefit from a 'Show WH Above First Connection' option, which would also be useful in some situations e.g. when all wells have trajectories leading back to a platform or drill pad and then all the well heads appear together, unreadable names etc.

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

No branches or pull requests

2 participants