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

Property filter: Use category labeling for property names starting with FIP #11355

Closed
hhgs opened this issue Apr 11, 2024 · 0 comments · Fixed by #11365
Closed

Property filter: Use category labeling for property names starting with FIP #11355

hhgs opened this issue Apr 11, 2024 · 0 comments · Fixed by #11365
Assignees
Labels
Enhancement An addition that can be observed by the user

Comments

@hhgs
Copy link
Member

hhgs commented Apr 11, 2024

For user defined FIP regions, naming will be FIP, not ending on NUM as standard region properties. Add "FIP*" to list of properties with category labeling in Property Filter.

@hhgs hhgs added the Enhancement An addition that can be observed by the user label Apr 11, 2024
@hhgs hhgs added this to the Maintenance 2024 - Sprint 04 milestone Apr 11, 2024
@magnesj magnesj self-assigned this Apr 12, 2024
magnesj added a commit that referenced this issue Apr 19, 2024
* Fix calculation for active cell values
Always allocate result data for active cells in destination case. Make sure that active cells is used for both population of expression variables and filtering of data. Improved naming to make it clear that we always work with active cell data.

* Check if scalar result index is valid
* Create the static scalar results once
addStaticScalarResult will clear already computed data, causing calculations to be triggered once more

* Early return if data already is available
If not checking if data is available, data is read from file and appended to result vector.

* Always check date for H5 files, and recreate if required

* Always recreate ESMRY if file exists and is older than SMSPEC

* #11355 Use category if result name starts with FIP or ends with NUM

* #11337 Summary import: Make sure ESMRY includes restart history

* #11334 Fix cvf::Viewport assert triggered for small contour map/2d intersection
Size of the overlay is could become negative, and would overflow for small views.

* #11310 Fix assert on single cell model.
Well pipe radius would become HUGE_VAL due to off-by-one error.
The assert could only happen on model with a single cell.

* Check equal grid size only when required
Equal grid size is required if there is more than one grid case in the expression. If a cell filter view is active, the visibility is based on one view and reused for all other grid models, and requires equal grid size.

* Remove obsolete log message

* Do not show dialog during regression tests

* Fix eclipse case contour map left click (#11378)

* Make sure we operate in the correct domain when picking points in the contour map

* Remove obsolete code causing grid to be loaded for all cases


* Bump version to 2024.03.1

---------

Co-authored-by: Kristian Bendiksen <kristian.bendiksen@gmail.com>
Co-authored-by: jonjenssen <69144954+jonjenssen@users.noreply.github.com>
@github-actions github-actions bot added the PendingRelease Issues is fixed and will be available in next release label Apr 19, 2024
@magnesj magnesj removed the PendingRelease Issues is fixed and will be available in next release label Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An addition that can be observed by the user
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants