14484 orion events data filter - #14500
Merged
Merged
Conversation
Add a typed FILTER declaration to the ORIONEVENTS 2.0 grammar, e.g. FILTER POROPERM = "PORO > 0.4 AND PERMX > 100.0". A PERFORATION event references it with FILTER=POROPERM or supplies an inline quoted expression. When applied, each used filter is materialized as a case-level combined data filter (one property filter per term, one-sided inclusive bounds, AND/OR combine mode) and attached to the perforation. Unqualified result names are searched in STATIC_NATIVE, DYNAMIC_NATIVE then GENERATED results; a TYPE. qualifier restricts the search. Missing results raise before any event is applied. apply_orion_document gains an optional case= parameter defaulting to the project's first case. RimWellEventPerf carries a RimCellFilter ptr-field with scriptable AddFilter/cell_filter methods, and the filter is copied onto the RimPerforationInterval when the timeline materializes completions.
Add a FILTER declaration (referenced by two perforations) and an inline filter expression to the shipped well_events.orion sample, and extend import_orion_events.py to pass case= to the applier and list the combined data filters created from the declarations. Skip schedule generation gracefully when no events were applied, and give FilterExpr a __str__ returning the raw expression so variable listings stay readable.
Declare FILTER HIPORO with a qualified result name (static.PORO) and reference it from the first perforation, passing case= to the applier and printing the attached filter per materialized perforation interval. The FILTER parts are included only when the project has a loaded case, so the example keeps working in caseless projects.
kriben
force-pushed
the
14484-orion-events-data-filter
branch
from
August 10, 2026 09:33
cdf0569 to
696cf77
Compare
kriben
marked this pull request as ready for review
August 10, 2026 10:21
magnesj
approved these changes
Aug 10, 2026
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
2 participants
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.
Fixes #14484.