Conversation
RimDataView shows well paths, surfaces, polygons and annotations without requiring an Eclipse or GeoMech case. Scene extent and the well pipe radius are derived from the visualized data rather than from grid cells, since there is no case to ask for a characteristic cell size. Importing well paths or surfaces creates the view on demand, so data objects become visible without first opening a case.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
RimDataView, a 3D view that shows well paths, surfaces, polygons and annotations without requiring an Eclipse or GeoMech case.Without a case there is no characteristic cell size to scale the scene by, so the view derives its extent and the well pipe radius from the bounding box of the data it visualizes.
Importing well paths or surfaces creates the view on demand, so imported data objects become visible without first opening a case. Seismic import still gets its own view — the auto-created data view is ignored when deciding whether a seismic view is needed.
Data views are excluded from comparison-view candidates.