RE: [gmx-users] anomalous free energy dgdl.xvg values every nstlist steps while using a twin-range cutoff

2009-02-18 Thread Berk Hess
Hi, This was a new issue in 4.0, 3.3 was fine. Berk > Date: Wed, 18 Feb 2009 13:26:39 -0500 > From: chris.ne...@utoronto.ca > To: gmx-users@gromacs.org > Subject: [gmx-users] anomalous free energy dgdl.xvg values every nstlist > steps while using a twin-range cutoff &

[gmx-users] anomalous free energy dgdl.xvg values every nstlist steps while using a twin-range cutoff

2009-02-18 Thread chris . neale
release notes) to the download page. Berk Date: Tue, 17 Feb 2009 17:50:17 -0500 From: chris.neale at utoronto.ca To: gmx-users at gromacs.org Subject: [gmx-users] anomalous free energy dgdl.xvg values every nstlist steps while using a twin-range cutoff Hello, I believe that the free-energy code

RE: [gmx-users] anomalous free energy dgdl.xvg values every nstlist steps while using a twin-range cutoff

2009-02-17 Thread Berk Hess
ris.ne...@utoronto.ca > To: gmx-users@gromacs.org > Subject: [gmx-users] anomalous free energy dgdl.xvg values every nstlist > steps while using a twin-range cutoff > > Hello, > > I believe that the free-energy code dgdl contribution from the > twin-range cutoff is b

[gmx-users] anomalous free energy dgdl.xvg values every nstlist steps while using a twin-range cutoff

2009-02-17 Thread Chris Neale
Hello, I believe that the free-energy code dgdl contribution from the twin-range cutoff is being calculated incorrectly in gromacs 4.0.3 (and probably other versions as well). Specifically, I notice that the dgdl values spike at nstlist intervals. This can be seen directly from my dgdl.xvg a