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

feat: well time step selector based on rates/bhp tables and clarify well rates logic #3427

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

Conversation

paveltomin
Copy link
Contributor

@paveltomin paveltomin commented Nov 6, 2024

Two things in this PR:

  1. Implement setNextDt in well solver which looks at all rates/bhp/status tables and makes sure time step is selected so that we honor table intervals. Can be enabled by timeStepFromTables flag in well solver.
  2. Change logic for well rates - currently inputted and outputted from t_n+dt (end of time step) - switch to t_n (beginning of time step) - this should be more consistent with lower interpolation method that is used and prevent grabbing "future" rate from tables and avoid weird behavior when time step cut can lead to shutting of wells.

@@ -377,4 +377,73 @@ WellControls const & WellSolverBase::getWellControls( WellElementSubRegion const
return this->getGroup< WellControls >( subRegion.getWellControlsName());
}

real64 WellSolverBase::setNextDt( real64 const & currentTime, const real64 & lastDt, geos::DomainPartition & domain )
Copy link
Contributor Author

Choose a reason for hiding this comment

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

main thing is in this function

@paveltomin paveltomin changed the title feat: well time step selector based on rates/bhp tables feat: well time step selector based on rates/bhp tables and clarify well rates logic Nov 6, 2024
@paveltomin

This comment was marked as resolved.

@paveltomin

This comment was marked as resolved.

@paveltomin
Copy link
Contributor Author

@paveltomin paveltomin added the ci: run integrated tests Allows to run the integrated tests in GEOS CI label Dec 4, 2024
@paveltomin paveltomin added the flag: requires rebaseline Requires rebaseline branch in integratedTests label Dec 4, 2024
@paveltomin paveltomin removed the ci: run integrated tests Allows to run the integrated tests in GEOS CI label Dec 9, 2024
@paveltomin
Copy link
Contributor Author

@paveltomin
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flag: ready for review flag: requires rebaseline Requires rebaseline branch in integratedTests type: feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants