.. index:: mdi/engine mdi_engine command ================== Syntax """""" .. parsed-literal:: mdi_engine Description """"""""""" This command is used to have LAMMPS act as a server with another client code to effectively couple the two codes together in client/server mode. More specifically, this command causes LAMMPS to begin using the `MDI Library `_ to run as an MDI engine (server), responding to commands made by an external MDI driver code (client). See the :doc:`Howto mdi ` page for more information about how LAMMPS can work as both an MDI driver or engine. General information about launching codes that communicate using the MDI Library can be found in the `corresponding page `_ of the MDI Library's documentation. ---------- This command should typically be used in an input script after LAMMPS has setup the system it is going to model in collaboration with the driver code. Depending on how the driver code tells the LAMMPS engine to exit, other commands can be executed after this command, but typically it should be used at the end of the LAMMPS input script. To act as a MD-based MDI engine, this is the list of MDI commands from a driver code which LAMMPS currently recognizes. See more details about these commands in the `MDI library documentation `_ .. NOTE: Taylor - is this the best link for this info? Can we flesh this .. out with the full list of supported commands? Maybe the distinction .. of what "node" the commands refer to is not needed in this table? .. list-table:: :widths: 20 80 :header-rows: 1 * - Command name - Action * - >NATOMS - Driver sends the number of atoms in the system * - FORCES - Driver sends 3*N double-precision atom forces * - ` page for more info. Related commands """""""""""""""" :doc:`fix mdi/engine ` Default """"""" None