Skip to content

feat: Add enthalpy to PVT Driver output #3704

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

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

dkachuma
Copy link
Contributor

Adds the enthalpy to the output of the PVTDriver if the fluid is thermal.

@dkachuma dkachuma self-assigned this Jun 13, 2025
@dkachuma dkachuma added ci: run CUDA builds Allows to triggers (costly) CUDA jobs ci: run integrated tests Allows to run the integrated tests in GEOS CI flag: no rebaseline Does not require rebaseline ci: run code coverage enables running of the code coverage CI jobs labels Jun 13, 2025
@dkachuma dkachuma marked this pull request as ready for review June 13, 2025 15:15
Copy link

codecov bot commented Jun 13, 2025

Codecov Report

Attention: Patch coverage is 71.42857% with 6 lines in your changes missing coverage. Please review.

Project coverage is 57.80%. Comparing base (7331a30) to head (d35cbdd).

Files with missing lines Patch % Lines
...constitutiveDrivers/fluid/multiFluid/PVTDriver.cpp 40.00% 6 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #3704   +/-   ##
========================================
  Coverage    57.80%   57.80%           
========================================
  Files         1248     1248           
  Lines       107846   107862   +16     
========================================
+ Hits         62342    62354   +12     
- Misses       45504    45508    +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dkachuma dkachuma requested a review from MelReyCG June 24, 2025 18:19
Copy link
Contributor

@corbett5 corbett5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not much for me to review here, but looks fine.

Comment on lines 81 to 86
integer const PHASE_FRACTION = TEMP + 2 + (outputCompressibility ? 1 : 0);
integer const PHASE_DENSITY = PHASE_FRACTION + numPhases;
integer const PHASE_VISCOSITY = outputMassDensity ? PHASE_DENSITY + 2*numPhases : PHASE_DENSITY + numPhases;
integer const PHASE_COMP = PHASE_VISCOSITY + numPhases;
integer const PHASE_MASS_DENSITY = PHASE_DENSITY + (outputMassDensity ? numPhases : 0);
integer const PHASE_VISCOSITY = PHASE_MASS_DENSITY + numPhases;
integer const PHASE_ENTHALPY = PHASE_VISCOSITY + (outputEnthalpy ? numPhases : 0);
integer const PHASE_COMP = PHASE_ENTHALPY + numPhases;
Copy link
Contributor

@MelReyCG MelReyCG Jun 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As this code passes unit tests I may be wrong, but I still have the feeling that PHASE_ENTHALPY and PHASE_COMP are not well defined. If those variables are the start indexes, shouldn't PHASE_ENTHALPY only be offset by the end of viscosity values? (PHASE_VISCOSITY + numPhases?)
And by the same design, shouldn't PHASE_COMP be at the end of enthalpies, which are enabled by outputEnthalpy? (which would give PHASE_ENTHALPY + (outputEnthalpy ? numPhases : 0))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci: run code coverage enables running of the code coverage CI jobs ci: run CUDA builds Allows to triggers (costly) CUDA jobs ci: run integrated tests Allows to run the integrated tests in GEOS CI flag: no rebaseline Does not require rebaseline
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants