Changes for parallel runs with multisegment wells that have shut perforations #6104
+213
−87
Conversation
This file contains 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
|
jenkins build this opm-tests=1310 please |
|
jenkins build this opm-tests=1310 please |
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
998a1e9 to
dab5bcd
Compare
|
jenkins build this opm-tests=1310 please |
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
dab5bcd to
c27cb32
Compare
|
jenkins build this opm-tests=1310 please |
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
c27cb32 to
1ca53fd
Compare
|
jenkins build this opm-tests=1310 please |
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
1ca53fd to
1900d42
Compare
|
jenkins build this opm-tests=1310 please |
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
1900d42 to
b85f25b
Compare
…se of only shut perforations on one process
…Well_impl With this change, parallel cases where one rank contains only SHUT perforations can be run
…ultisegmentWell_impl for parallel runs with MSWells where one rank contains only shut perforations
… part for ranks with only shut perforations
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
b85f25b to
506b474
Compare
…ation on a rank Before, when the local_indices_ object was empty, a sequential run was assumed, yet that can also mean that there are no local_indices_ on this rank. Now, a sequential run is assumed only if the size of the communiator is 1.
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
2 times, most recently
from
28cd763 to
170bce3
Compare
|
jenkins build this opm-tests=1310 please |
lisajulia
changed the title
This is needed for cases with SHUT perforations, since the structure std::vector<std::vector<int>> perforations_ of MultisegmentWellSegments works with only OPEN perforations
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
170bce3 to
7c8f100
Compare
|
jenkins build this opm-tests=1310 please |
… processes and have shut perforations
lisajulia
force-pushed
the
feature/ms-wells-shut-perforations
branch
from
7c8f100 to
5f826b2
Compare
|
jenkins build this opm-tests=1310 please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes parallel runs with multisegment wells that have SHUT perforations.
The test added in the last commit of this PR fails without the changes before (#6139).
In order to address such simulations, I've changed the behavior when accessing structures that work with only the OPEN perforations, like std::vector<std::vector> perforations_ of MultisegmentWellSegments.
For this, I've added the construction of a activeToLocal map in the function WellState::initWellStateMSWell and then added this map and its conteraprt localToActive to the ParallelWellInfo class.