new mdp option "nstlist=-1" doesn't work with parallel runs
Created an attachment (id=347)
The fowllowing is my post in the gmx-user mailing-list:
Again I have a problem regarding the "nstlist=-1" option and this time it's related to parallel runs.
With the help from Berk, I can run my system with nstlist=-1 option and 1 cpu without any problem. However, each time when I run it using more than one cpu under MPI, the run crashes immediately. The input files are the same for both serial and parallel runs. I tried to change to nstlist=1 and this time it run OK both serial and parallel. So it seems to me there is a problem for the automatic neighbor list updating with parallel runs. I tried both domain decomposition and particle decompostion with "nstlis=-1" and in both cases the run crashed.
Could Berk or anyone else have a look at it?
Thanks very much.
The attachement contains input files for the test. The commands are:
grompp -f sample.mdp -c system.pdb -p A8H.top -o a.tpr -n index.ndx
mpirun -np 2 -machinefile host mdrun -s a.tpr -table table.xvg
In my MPI environment I got:
"mdrun:31199 terminated with signal 11 at PC=6115d6 SP=7fbfffc520. Backtrace:
Thanks very much for your help!
#1 Updated by Berk Hess about 11 years ago
For me it seems to run also in parallel.
But I get warnings like this for all table files:
WARNING: For the 2398 non-zero entries for table 1 in table_CGW_CGW.xvg the forces deviate on average 126% from minus the numerical derivative of the potential
Did you not get these, or did you just ignore them?
You should first make your tables potential and forces consistent,
this will probably fix you problems.
PS I would use 10 times wider spaced tables, this saves disk space
and make mdrun run slightly more efficient. These is no detail in your
potential (you could even use 100x less points).