Many thanks for your response. I ran the simulation again at time
step of 0.05fs and still got the error :
ERROR: Lost atoms: original 7577 current 7574 (../thermo.cpp:427)
When I looked at the log file, I found that the temperature and
kinetic energy (of the rigid bodies) was fluctuating wildly. I am
please define "wildly". please also recall, that the magnitude of
temperature fluctuations varies with the number of particles.
I have 2 options in my mind
(1) should I use pair_style soft in the beginning of the simulation. Is it
possible to change the pair_style later doing the simulation.
switching pair styles is possible during a simulation. whether this is
useful in this case, i am unable to say.
(2) Is it correct to change the force to a smaller value (say to a
maximum of 100.0) for small distances. Will it affect the dynamics in
the long run.
this is a change in the force field and thus affect the validity of your
please recall, that i mentioned that the symptoms you are seeing can also
be cause by incorrect force field input.
since a see, that you have both, coulomb and lj interactions, your "force
spikes" could for example be caused by incorrect parameters, where atoms
get too close due to the coulomb forces becoming very strong at short
distance due to errors in the lennard jones resulting in it not repulsive
enough. if this hypothesis is true, through capping the force, you would
achieve the exact opposite of what you intend.
Below is the input script :
this input is a mess!! it is full of commented out stuff and commands that
are not needed to debug and commands that make no sense.
overall, it is not something that inspires confidence in that you are doing
a good job here. if i was your adviser (which i am *not*), i would
encourage you to start over and build your system in small increments and,
e.g., figure out the correct settings for a stable and correct simulation
reproducing results of a pure CO2 system first. in fact, i would recommend
you find yourself a competent local(!) tutor, as none of us on this list
has the time to debug your input deck for you or teach you in detail how to