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

Get grid conformity when available from RMS using rmsapi #59

Open
oddvarlia opened this issue Feb 10, 2025 · 0 comments
Open

Get grid conformity when available from RMS using rmsapi #59

oddvarlia opened this issue Feb 10, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@oddvarlia
Copy link
Contributor

oddvarlia commented Feb 10, 2025

Purpose: Simplify APS job specification in AHM mode by retrieving the grid conformity per zone and zone names from the grid job linked to the grid the APS job is using. The api for that is available at least for RMS14.2 and newer. Example of how to get this info from the RMS project is shown below. Conformal mode is 0- Proportional, 1- Top conform, 2- Base conform

To make this work in APS plugin, the user have to supply the name of the RMS job that has created the grid. This can be done by a drop-down menu in the Job settings and the conformity selection fields in main window can be readonly fields in this case showing the actual settings read from RMS. For cases where RMS has imported the geomodel grid or the geomodel grid is created by external scripts, RMS don't know anything about the conformity and in this case the user may have to specify it like today. There are unfortunately no function in rmsapi to get the job name for the grid job that has created the current geomodel grid. But there are functionality to get a list of jobs and the user can select the correct job name from that list. That is the reason why the user have to select the job name (e.g. by a drop-down selection field in the Job settings window).

Image

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

Successfully merging a pull request may close this issue.

1 participant