Hi all,
I'm running the PIMD simulation of bulk water with 216 water molecules via lammps.
However, after 100,000 - 400,000 timestep, the lammps shows the error as "ERROR: Lost atoms: original 648 current 647 (../thermo.cpp:481)"
As I understand, this error usually occurs in lammps where the system is too unstable, but I couldn't find any system instability from trajectory or energy with time. It seems that one hydrogen atom suddenly disappears and the simulation is crashed. Shorter timestep, low number of CPUs, different neighbor atom settings, and different bead numbers show the same problem.
Do you have any idea about this error?
Here is the XML file for i-pi simulation.
<simulation verbosity="medium">
<!-- specification of output files. property(options){units}, format, stride, etc. -->
<output prefix="base_p-1">
<properties stride="100" filename="out"> [ step, time{femtosecond}, conserved{kilocal/mol}, temperature{kelvin}, kinetic_cv{kilocal/mol}, potential{kilocal/mol}] </properties>
<trajectory filename="pos" stride="1000" cell_units="angstrom" format="pdb"> positions{angstrom} </trajectory>
<checkpoint filename="chk" stride="100000" overwrite="true"/>
</output>
<total_steps> 2000000 </total_steps>
<prng>
<seed>32345</seed>
</prng>
<!-- "forcefield" section. will use an external driver communicating over a UNIX socket -->
<ffsocket name="lmpserial" mode="unix" matching="lock">
<address> water566 </address> <latency> 0.001 </latency>
</ffsocket>
<!-- system specifications. this defines the physical system and the evolution "rules" (i.e. the integrator) -->
<system>
<!-- initialize from an external file, the nbeads attribute determines the size of the ring polymer -->
<initialize nbeads="4">
<file mode="pdb"> ./water-216.pdb </file>
<velocities mode="thermal" units="kelvin"> 600 </velocities>
</initialize>
<!-- the <force> section specifies which ff should be used to describe interactions. as we will see,
here one can combine multiple force providers, if desired -->
<forces>
<force forcefield="lmpserial"> </force>
</forces>
<!-- how will we evolve the system? with MD, of course! -->
<motion mode='dynamics'>
<dynamics mode="nvt"> <!-- constant temperature integrator - will use a simple PILE-G for the moment -->
<thermostat mode="pile_g">
<tau units="femtosecond"> 50 </tau>
<pile_lambda> 0.5 </pile_lambda>
</thermostat>
<timestep units="femtosecond"> 0.25</timestep> <!-- this is a conservative choice for MD, but it is safe also with PIMD 300K -->
</dynamics>
</motion>
<ensemble> <!-- ensemble specification. here we basically just state what is the temperature -->
<temperature units="kelvin"> 300 </temperature>
</ensemble>
</system>
</simulation>
Thank you,
Minho