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

Warning on nested MPI #1025

Merged
merged 8 commits into from
Jul 12, 2023
Merged

Warning on nested MPI #1025

merged 8 commits into from
Jul 12, 2023

Conversation

jlnav
Copy link
Member

@jlnav jlnav commented Jun 14, 2023

Addresses #1015 .

@jlnav jlnav marked this pull request as ready for review June 19, 2023 19:01
@jlnav jlnav requested a review from shuds13 June 21, 2023 20:12
@shuds13
Copy link
Member

shuds13 commented Jul 10, 2023

Is it feasible to do this when we have detected OpenMPI, which we already do.

That said there could be other OpenMPI based implementations, but usually I've found everything else works okay.

Comment could say MPICH/MPICH-derived as many implementations like Intel MPI are based on MPICH. Better probably, turn it around and say nesting will not work if using Open MPI.

@@ -386,6 +387,13 @@ def libE_mpi_manager(mpi_comm, sim_specs, gen_specs, exit_criteria, persis_info,
"""Manager routine runs on rank 0."""
from libensemble.comms.mpi import MainMPIComm

if Executor.executor is not None:
if isinstance(Executor.executor, MPIExecutor) and libE_specs["comms"] == "mpi":
Copy link
Member

Choose a reason for hiding this comment

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

As inside libE_mpi_manager - I don't think need to test for comms being "mpi" here.

Copy link
Member

Choose a reason for hiding this comment

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

Also move below logger set up (which is just below).

Copy link
Member

@shuds13 shuds13 left a comment

Choose a reason for hiding this comment

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

I have updated to only give the message when using Open MPI. We should squash merge this. And make sure commit message is simplified.

@jlnav jlnav merged commit 62a7e93 into develop Jul 12, 2023
@jlnav jlnav mentioned this pull request Jul 19, 2023
@jmlarson1 jmlarson1 deleted the feature/warn_on_nested_mpi branch July 20, 2023 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants