Repository navigation
Conversation
The cell result of a geomechanical view could not be read or set from
Python. Make RimGeoMechResultDefinition (position, field and component)
and the view's cell result scriptable, as for grid views:
cr = geomech_view.cell_result()
cr.result_position_type = "ELEMENT_NODAL"
cr.result_field_name = "SE"
cr.result_component_name = "S1"
cr.update()
On update the UI fields are synced and the result loaded, as for the
grid result definition. rips View.case() now also works for
geomechanical views, so View.export_snapshot() does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kriben
requested changes
Oct 16, 2026
kriben
left a comment
kriben
left a comment
Collaborator
There was a problem hiding this comment.
Looks mostly good, Halvor! See the review for two small nitpicks before merging.
Comment on lines
+205
to
209
| # Geomechanical views are children of their case | ||
| if not hasattr(self, "eclipse_case"): | ||
| return self.ancestor(rips.case.Case) | ||
|
|
||
| project = self.ancestor(rips.project.Project) |
Collaborator
There was a problem hiding this comment.
I think I would prefer match on the type of self instead of checking for attributes it does have?
Comment on lines
+547
to
+549
|
|
||
| m_timeLapseBaseTimestep.uiCapability()->setUiReadOnly( resultPositionType() == RIG_WELLPATH_DERIVED ); | ||
| } |
Collaborator
There was a problem hiding this comment.
Why is this line not part of the updateUiFieldsFromActiveResult method?
Member
|
I did some minor changes to your PR. Created a new PR in the main repo here #14985 |
magnesj
added a commit
that referenced
this pull request
Oct 21, 2026
Make RimGeoMechResultDefinition (position, field and component) and the view's cell result scriptable, as for grid views.
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
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.
The cell result of a geomechanical view could not be read or set from Python. Position, field and component of
RimGeoMechResultDefinitionand the view's cell result are now scriptable, and the gRPC update syncs the UI fields and loads the result as for grid results:rips
View.case()now also works for geomechanical views, soexport_snapshot()does.🤖 Generated with Claude Code