Skip to content

Comp explicit swat init - #7453

Draft
GitPaean wants to merge 2 commits into
OPM:masterfrom
GitPaean:comp-explicit-swat-init
Draft

GitPaean wants to merge 2 commits into
OPM:masterfrom
GitPaean:comp-explicit-swat-init

Conversation

@GitPaean

Copy link
Copy Markdown
Member

No description provided.

@GitPaean GitPaean added the manual:new-feature This is a new feature and should be described in the manual label Sep 25, 2026
@GitPaean
GitPaean force-pushed the comp-explicit-swat-init branch from e0547d9 to 6454ef5 Compare September 25, 2026 09:10
@GitPaean
GitPaean force-pushed the comp-explicit-swat-init branch 3 times, most recently from 8f651a6 to 5c0ce22 Compare September 25, 2026 21:55
For water-active compositional runs initialized from ZMF, the initial
water saturation in the supplied reference output can be matched by
scaling the water-to-hydrocarbon saturation ratio by the ratio of
unflashed to flashed EOS molar volumes. Apply this correction only
for two-phase flashes and only with --compat-explicit-swat-init.

Keep the option disabled by default, preserving the existing literal
SWAT initialization. The well model is unchanged.
Run the no-well compositional deck from opm-tests with the default
initialization and with --compat-explicit-swat-init=true. After each
run, check the first middle-cell BSWAT summary value against disjoint
expected ranges. This verifies the option and its default behavior
without committing binary reference results.
@GitPaean
GitPaean force-pushed the comp-explicit-swat-init branch from 5c0ce22 to c69cc2a Compare September 25, 2026 21:56

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

manual:new-feature This is a new feature and should be described in the manual

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant