-
Notifications
You must be signed in to change notification settings - Fork 92
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
Comments
Thanks for the suggestion. We also have an improved concept for label display that could be used for well path labels. |
Great. Hopefully this mod not too difficult to arrange and may improve well display a lot in some models |
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:
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. |
[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.)
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:
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.
The text was updated successfully, but these errors were encountered: