Warning/error messages when running MPI jobs

[chrislupp]

I've been running the MACH tutorials in the example folder for both the aero and aerostructural analyses. In serial execution, they behave pretty much as I would expect them to. However, when running in parallel, I get a bunch of warnings (maybe even errors, I can't tell) that look something like this:

[e09065d05ca4:00096] Read -1, expected 520704, errno = 1

I suspect that this is a message from ADflow, as it is output during CFD iterations, although I can't pinpoint where it comes from within ADflow.

After the analysis completes another series of warnings, this time for OpenMDAO, is put out that looks something like this (there are a lot more of them):

DeprecationWarning:'mp_group.s0.solver_group.struct.solver' <class TacsSolver>: Passing `src_indices` as an arg to `add_input` isdeprecated and will become an error in a future release.  Add `src_indices` to a `promotes` or `connect` call instead.

The questions that arise (for me), are:
Are these warnings (the ADflow ones, in particular) concerning/potentially an issue, even if my solutions have completed so far? If so, does anyone have any pointers how to resolve the first set ADflow messages? And is there a recommended version of OpenMDAO to use with mphys at this point, to avoid deprecation issues?

Thanks in advance for your inputs!

[anilyil]

@chrislupp see OpenMDAO poem about this change here: https://github.com/OpenMDAO/POEMs/blob/master/POEM_035.md

The deprecation warnings are from openmdao. I believe the warnings are added with this PR: OpenMDAO/OpenMDAO#1760.

For now, 3.6.0 works. We will update the MPhys code with the new OpenMDAO API for src_indices, which should resolve these warnings. I am not sure about the first error-like thing you posted. I have not seen anything like that from our code but I also dont have a lot of experience with aerostructural.

Hope this helps.

[chrislupp]

Thanks for the OpenMDAO version pointer. BTW, I figured out the first warning/error: apparently this can happen when running docker containers and supposedly the warnings are harmless.

[chrislupp]

as discussed in the telecon today, to get openmpi and docker running without those annoying messages, you can deactivate Vader (for reference, here the OpenMPI issue: open-mpi/ompi#4948) by setting the environment variable:

export OMPI_MCA_btl_vader_single_copy_mechanism=none

with Docker, I tend to set this in the Dockerfile.