restarted run produces different results

I noticed that the results I get by using a restart file and without it (which produced the restart file) are different. For example:

In one case, without using a restart file, I get these results for the radius of gyration:


7999500 18.2339
8000000 18.2174
8000500 18.3504
8001000 18.4655
8001500 18.558
8002000 18.6205
8002500 18.6589
8003000 18.6043
8003500 18.5124
8004000 18.4614




but, when running by a restart file from step 8000000, I get the following results:

8000500 18.3504
8001000 18.4655
8001500 18.5594
8002000 18.6908
8002500 18.7263
8003000 18.696
8003500 18.719
8004000 18.7851




I’m using version lammps/28Jun14. The simulation is at a constant temperature of 290. I use this input file for restarting:

boundary p p p
units real
atom_style full
bond_style class2
angle_style class2
dihedral_style class2
improper_style class2
pair_style soft 10
pair_style lj/class2/coul/long 10
pair_modify tail yes table 12
newton on

kspace_style ewald 1e-4
special_bonds dreiding
neighbor 1 bin
neigh_modify delay 0 every 1 check yes page 1000000
comm_modify mode single cutoff 10 vel no

read_restart restart-eq2.8000000

fix Main all nvt temp 290 290 100 tchain 1

compute g Chain gyration
fix gr Chain ave/time 1 500 500 c_g file tmp.gr

thermo 500
thermo_style custom step temp press vol density etotal ke pe time
thermo_modify lost warn flush yes
timestep 1
restart 500000 restart-main.*
run 5000000

Can you please help me find the problem? Thank you

There is no problem here and what you see is perfectly normal. At 8000500 step you have the same results, then they slowly diverge - which is a well documented bevaviour of MD. Please pick up a MD textbook for more details.

Ray

Can you please help me find the problem? Thank you

Please read the read_restart doc page for various reasons

a restarted run will not duplicate the original for long timescales.

Steve

Dear Steve and Ray,

Thank you for your responses. Unfortunately, I could not find the reasons in manual, and this is why I sent email to get some help :slight_smile:

The fact is that sometimes, the results achieved by using a restart file are significantly different from those obtained without it, or are even contrary to each other. I think this may be due to the instability of the system or my simulation.

MD is essentially stochastic. If you system is small, you really need a number of trajectories to obtain statistically meaningful results.

That being said, you might want to move your read_restart command as top as possible.

Ray

Dear Steve and Ray,

Thank you for your responses. Unfortunately, I could not find the reasons
in manual, and this is why I sent email to get some help :slight_smile:

​please think about this statement for a little bit. you are essentially
telling the people WHO WROTE THE MANUAL, that what they say they did, and
*know* they did, isn't there. how likely is that?? how much more likely is
that you didn't look properly. answers don't always appear in the way that
you want them to be and jump right at you, but you need to *work* to obtain
them.

The fact is that sometimes, the results achieved by using a restart file
are significantly different from those obtained without it, or are even
contrary to each other. I think this may be due to the instability of the
system or my simulation.

​this very topic has been discussed many times on the mailing list, and is
also discussed in the text book literature,​ and is something that any
practitioner of MD should have some fundamental knowledge about. so please
make an effort and do your homework on that.

you will find much less friendlier answers then when insisting on thing not
being the way they are.

axel.