MPhys is a package that standardizes high-fidelity multiphysics problems in OpenMDAO. MPhys eases the problem set up, provides straightforward extension to new disciplines, and has a library of OpenMDAO groups for multidisciplinary problems addressed by its standard.

While MPhys does provide these conventions, it is not absolutely necessary to follow these guidelines in order to solve these types of problems with OpenMDAO given its very general coupling capability. However, by following the MPhys conventions, the usage of OpenMDAO for multiphysics analysis will be modular across developer groups. This eases technology transfer and collaboration in this area of research. The standardization strives for modularity of multiphysics problems with large parallel physics codes.

Install

To install the latest release version of mphys:

pip install mphys

For developers, clone the mphys repository then in the root directory do:

pip install -e .

Documentation

Online documentation is available at https://openmdao.github.io/mphys/.

Building the Docs

The documentation includes N2 diagrams from the unit tests. Before building the docs, go into tests/unit_tests and run python -m unittest. Then go into the docs directory and run make html.

Solvers compatible with MPhys

Open-source codes with builders and components compatible with mphys:

Code	Recommended Version*	Analysis Type	Notes
ADflow	2.12.0	Aerodynamics	Structured multi-block and overset CFD.
DAfoam	3.2.0	Aerodynamics	Discrete Adjoint with OpenFOAM.
OpenAeroStruct	2.10.0	Aerodynamics	Vortex lattice aerodynamics written using OpenMDAO.
FunToFEM	0.3.8	Load and Displacement Transfer	Point cloud based transfer scheme. Part of the FUNtoFEM package.
pyCycle	4.3.0	Propulsion	Thermodynamic cycle modeling library for engines.
pyGeo	1.15.0	Geometric Parameterization	Wrapper for ESP, OpenVSP, and a free-form deformation parameterization.
TACS	3.8.0	Structures	Parallel Finite Element Analysis.

* Recommended version to run mphys examples. Older versions may still be supported.

Examples

As noted their README.md files, some of the examples use codes that are not widely available; however, they are still included in order to provide more illustrations of how mphys can be used.

For developers

Telecons

MPhys development is discussed in biweekly telecons that occur Mondays at 11AM Eastern Time. If you would like to participate, contact Kevin Jacobson (kevin.e.jacobson@nasa.gov).

Signed Commits

The MPhys main branch requires verified commits. See the instructions on how to sign commits here.

Tests

The test are written to use the testflo framework because it allows us to run tests with multiple cores. To run the tests you will need to install testflo.

Integration Tests

The integration tests check the interaction of mphys with several solvers. These python packages are required to run them:

adflow
tacs
funtofem
testflo
paramerized
openaerostruct

and these input files. They can be obtained by running get-input-files.sh

wingbox.bdf
wing_vol_L1.cgns
wing_vol_L2.cgns
wing_vol_L3.cgns
ffd.xyz

to run the tests execute in the root directory

testflo -v tests

Software Assurance Plan

MPhys has been deemed as Class-E software, according to the 7120.5D Specification. To maintain software quality and assure functionality, MPhys includes a unit and integration test suite. Before any pull requests are merged, all of those tests must pass. The tests are run as part of a continuous integration system, automatically upon pull request submission.

We require all commits to be signed to ensure that we know the "identity" (at least that the commit is actually coming from the account it claims to be). Unsigned commits will not be accepted.

The Bandit static analysis tool is run on the codebase to check for any "simple" security issues. This checks for basic vulnerabilities like having API keys, user names, or passwords in the repository. Bandit is run manually on the repository before any major releases are made.