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: Enable fully coupled mode for CompositionalMultiphaseReservoirPoromechanics and SinglePhaseReservoirPoromechanics #3388

Open
wants to merge 7 commits into
base: pt/set-mgr-strategy
Choose a base branch
from

Conversation

paveltomin
Copy link
Contributor

should go after #3383 and #3386

  • works equivalent to MultiphasePoromechanicsReservoir and SinglePhasePoromechanicsReservoir, just more convenient to switch between FIM and SEQ within the same solver
  • can use the same MGR recipe (order of block is actually the same: mechanics, flow, wells)

@paveltomin
Copy link
Contributor Author

need review please

@CusiniM
Copy link
Collaborator

CusiniM commented Oct 14, 2024

I am lost. What are these? What s the difference between these and MultiphasePoromechanicsReservoir and SinglePhasePoromechanicsReservoir ?

@paveltomin
Copy link
Contributor Author

I am lost. What are these? What s the difference between these and MultiphasePoromechanicsReservoir and SinglePhasePoromechanicsReservoir ?

CompositionalMultiphaseReservoirPoromechanics and SinglePhaseReservoirPoromechanics were created for sequential since MultiphasePoromechanicsReservoir and SinglePhasePoromechanicsReservoir are designed differently: they are flow/mech + wells so when one runs them in sequential they will do flow/mech solve and wells solve iteratively.
CompositionalMultiphaseReservoirPoromechanics and SinglePhaseReservoirPoromechanics were not be able to run in FIM mode which is addressed in this PR.
I know this is confusing and ultimately we should clean this up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants