[DualPorosity] (1/5) Add dual-continuum RUNSPEC run modes - #5316
Draft
arturcastiel wants to merge 1 commit into
Draft
[DualPorosity] (1/5) Add dual-continuum RUNSPEC run modes#5316arturcastiel wants to merge 1 commit into
arturcastiel wants to merge 1 commit into
Conversation
Co-authored-by: AXON <axon@arturcastiel.github.io>
arturcastiel
changed the title
arturcastiel
added
the
manual:enhancement
Member
Author
|
jenkins build this please |
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.
What this does
Teaches the input layer the three dual-continuum run modes:
DUALPORO,DUALPERM(whichimplies
DUALPORO) andNODPPM. Adds the RUNSPEC members, their accessors and theirserialization, so everything downstream asks one place what kind of run this is.
Why
First of a short series adding a dual-continuum capability to Flow. A dual-continuum deck
declares twice the layers: the first half in K are matrix cells, the second half their
co-located fracture twins. Nothing can interpret that layout before the run mode is known,
so this lands first.
Behavior impact
None. Flow still rejects every dual-continuum keyword; this only adds the accessors and the
per-cell coupling keyword's registration.
Testing
Run-mode parsing,
DUALPERMimplyingDUALPORO,NODPPMnarrowed to RUNSPEC, and theserialization round-trip.
Requirements and limitations
Nothing consumes these accessors yet — the code that does follows in the next pull request.
Gravity-drainage run modes are deliberately not included; that work is separate and later.