I've been doing some production runs using the AXD module in charmm which have been running for some time without crashing with errors etc. But when I've gone to look at the progress of the runs through the axd files I have large sections where the trajectory hasn't been inverted when it hits the lower boundary and so it keeps going back on itself rather than being forced to carry on until the end boundary I've set.

An example is found at the bottom of the attached and file where the trajectory has gone from around 48 to 45A when there should be boundaries every 0.5A and so it should be confined by the boundary at 48A. I've attached the corresponding input file with the AXD command in too.

Thank you

Attached Images
1tit_01_006_axd.txt (73.77 KB, 228 downloads)
SHA1: 87ced82ab8c4390a22efc43f2be8d4b4f9b91b98
1tit_01_006_inp.txt (4.35 KB, 183 downloads)
SHA1: c17a8d22ead096e49656f5e4effe91f8ade29ef4