[gmx-developers] high-precision TIP3P parameters?

Michael R Shirts Michael.Shirts at Colorado.EDU
Mon May 29 23:08:40 CEST 2017


I’ll raise the issue on the amber developer list about the provenance of the parameters there.

Best,
~~~~~~~~~~~~~~~~
Michael Shirts
Associate Professor
michael.shirts at colorado.edu<mailto:michael.shirts at colorado.edu>
http://www.colorado.edu/lab/shirtsgroup/
Phone: (303) 735-7860
Office: JSCBB C123
Department of Chemical and Biological Engineering
University of Colorado Boulder

From: <gromacs.org_gmx-developers-bounces at maillist.sys.kth.se> on behalf of Erik Lindahl <erik.lindahl at gmail.com>
Reply-To: "gmx-developers at gromacs.org" <gmx-developers at gromacs.org>
Date: Monday, May 29, 2017 at 1:45 AM
To: "gmx-developers at gromacs.org" <gmx-developers at gromacs.org>
Subject: Re: [gmx-developers] high-precision TIP3P parameters?

Hi,

I think Igor has a point that we should make our implementation of Amber as accurate as possible, but let's make sure we only change things once.

There has also been at least once instance where Amber changed they way they defined improper torsions internally without documentation, so we went from perfect matches in Amber ~8 to mismatching, and then back to matching.

1. I agree the Amber implementation should be our reference for Amber, but do the parameter files in the Amber package match the published force field exactly? Let's double-check that paper.

2. This If we should change, I would suggest making a quick audit of _all_ our Amber parameters and see if there are more rounding errors/deviations. If so, let's change all of them at the same time.

3. I also agree with Berk that this is only worth doing if we really get everything to match pretty close to perfectly. It's better to have a known insignificant discrepancy than a set of parameters that keeps changing!


Cheers,

Erik



On Mon, May 29, 2017 at 9:36 AM, Berk Hess <hess at kth.se<mailto:hess at kth.se>> wrote:
Hi,

My opinion is that we should minimize the number of time we change force field parameters, as this is confusing for users. The difference here is very small and the Coulomb constant also differs from Amber. I would only want to change this when we can get the total energy to match the Amber code up to all decimals.

Cheers,

Berk

--
Gromacs Developers mailing list

* Please search the archive at http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before posting!

* Can't post? Read http://www.gromacs.org/Support/Mailing_Lists

* For (un)subscribe requests visit
https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers or send a mail to gmx-developers-request at gromacs.org<mailto:gmx-developers-request at gromacs.org>.



--
--
Erik Lindahl <erik.lindahl at gmail.com<mailto:erik.lindahl at gmail.com>>
Professor of Biophysics, Dept. Biochemistry & Biophysics, Stockholm University
Science for Life Laboratory, Box 1031, 17121 Solna, Sweden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20170529/c1d51e2a/attachment.html>


More information about the gromacs.org_gmx-developers mailing list