<div class="gmail_quote">I am having the following issue with Gromacs 4.0.2:<br><br><br>I run a simulation with pbc=xyz. By the end of the simulation my molecule is split by the boundary (half of the molecule appears on one side and the other half on the opposite side). This is not a problem. The problem occurs when I use tpbconv to extend my run. Then, within the first few steps (<100 steps) of the extended run I get messages like<br>
<br>Warning: 1-4 interaction between 1251 and 962 at distance 69.927 which is larger than the 1-4 table size 51.500 nm<br>These are ignored for the rest of the simulation<br>This usually means your system is exploding,<br>
if not, you should increase table-extension in your mdp file<br>or with user tables increase the table size<br><br>-------------------------------------------------------<br>Program mdrun, VERSION 4.0<br>Source code file: nsgrid.c, line: 357<br>
<br>Range checking error:<br>Explanation: During neighborsearching, we assign each particle to a grid<br>based on its coordinates. If your system contains collisions or parameter<br>errors that give particles very high velocities you might end up with some<br>
coordinates being +-Infinity or NaN (not-a-number). Obviously, we cannot<br>put these on a grid, so this is usually where we detect those errors.<br>Make sure your system is properly energy-minimized and that the potential<br>
energy seems reasonable before trying again.<br><br>Variable ci has value -2147483648. It should have been within [ 0 .. 1331 ]<br><br>-------------------------------------------------------<br><br><br>What appears to be happening is that when the run is extended, the pbc is not imposed correctly, and the system explodes from all of the covalent bonds being stretched across the length of the box. This also occurs if I take the final gro structure from the previous run and use grompp instead of tpbconv. This occured in 20 different trajectories, all of which had run successfully with no issues for millions of time steps immediately before.<br>
<br>Any ideas what is going on? I did not have this issue with the cvs version, but once 4.0 was released I started having this trouble.<br><br>Thanks in advance<br><font color="#888888"><br>-Paul<br>
</font></div><br>