fix typo. more clarifications

This commit is contained in:
Axel Kohlmeyer
2022-12-24 01:16:51 -05:00
parent 8a2257f568
commit 93cfa6ef30

View File

@ -33,12 +33,18 @@ depending on how LAMMPS was configured and whether the LAMMPS library
:doc:`was compiled as a static or dynamic library <Build_link>`. :doc:`was compiled as a static or dynamic library <Build_link>`.
If the LAMMPS library itself has been compiled with MPI support, the If the LAMMPS library itself has been compiled with MPI support, the
resulting executable will still be able to run LAMMPS in parallel with resulting executable will be able to run LAMMPS in parallel with
``mpirun``, ``mpiexec``, or equivalent. Please also note that the order ``mpirun``, ``mpiexec``, or equivalent. This may be either on the
of the source files matters: the ``lammps.f90`` file needs to be "world" communicator or a sub-communicator created by the calling
compiled first, since it provides the :f:mod:`LIBLAMMPS` module that Fortran code. If, on the other hand, the LAMMPS library has been
would need to b imported by the Fortran code that uses the interface. A compiled **without** MPI support, each LAMMPS instance will run
working example can be found together with equivalent examples in C and independently using just one processor.
Please also note that the order of the source files matters: the
``lammps.f90`` file needs to be compiled first, since it provides the
:f:mod:`LIBLAMMPS` module that would need to be imported by the calling
Fortran code in order to uses the Fortran interface.
A working example can be found together with equivalent examples in C and
C++ in the ``examples/COUPLE/simple`` folder of the LAMMPS distribution. C++ in the ``examples/COUPLE/simple`` folder of the LAMMPS distribution.
.. versionchanged:: TBD .. versionchanged:: TBD