1.4.5.1. MPI Setup

The following configuration must be done on all hosts:

  • Install nCode DesignLife on each system.

  • Install MPI on the system that runs the distributed application (known as the run time system). MPI requires a run time system to support the remote invocation of processes and to set up communication.

    • The Intel MPI runtime installer for Windows is included in nCode distributions in the extras folder. This runtime is not part of the nCode installation but can be installed separately by running the Intel installer, which is typically named w_mpi-rt_p_2018.1.156.exe.

    • The runtime must be installed on all the computers that will be used for running the distributed application. Installing the runtime will install a service which enables start-up of remote applications. It will also add the runtime binaries folder to the system path.

    • Ensure that the MPI application installed is one that is supported by the nCode solver.

  • Launch the hydra service and mpiexec register so that credentials are saved:

    hydra_service -install

    hydra_service -start

    mpiexec -register

  • Check the firewall permissions and configurations in the DesignLife Documentation and add the following applications to the firewall:

    • From the nCode bin folder allow the dt* executables.

    • From the Intel distribution folder allow Mpiexec.exe​

To make sure MPI is correctly set up on every host, you can test communications by using dtdistrib.exe within nCode installation directory.


Note:  Check your MPI setup carefully if the results retrieved are zero when using an MPI configuration. You can check the configuration is working as expected using the executable above.


To output log messages, run ncpref from the nCode bin directory and change /Libraries/MPI/LogMessages to All.