<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1526476328;
        mso-list-type:hybrid;
        mso-list-template-ids:452617324 -1530779754 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
        {mso-level-start-at:0;
        mso-level-number-format:bullet;
        mso-level-text:-;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;
        font-family:"Calibri","sans-serif";
        mso-fareast-font-family:SimSun;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal>Hi there,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>For the past few months, I’ve been adding a charge equilibration
model to GROMACS (to be specific, QTPIE – a refinement of QEq). For
the model to work properly, each atom must “see” each other atom in
the electrostatic interaction (it is a screened Coulomb interaction). This
is easy enough to do with pbc = no; I just set all the cutoffs to zero, and add
a new neighbor-list that includes excluded atom pairs.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Now I would like to run the simulation with PBC turned on,
which means either implementing Ewald summation or using cutoffs for the
electrostatic interaction. When cutoffs are turned on (with or without
PBC), the model goes haywire even with very long cutoff lengths. I haven’t
implemented Ewald summation for the screened Coulomb interaction, and I’m
not sure if it’s worth the effort if an easier fix is possible.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>As a quick fix, I changed the simple neighbor-searching code
to set rcut = 1000000 when QTPIE is turned on (normally forbidden under normal
GROMACS run conditions). This brings the charges back to normal in a
periodic box, plus I now get complete uniformity of the charges in crystalline systems
(e.g. in FCC NaCl, the charges on the Na atoms are all the same). I think
this works because simple neighbor-searching with an infinite cutoff length has
the effect of counting every neighbor once while still following the minimum
image convention. I have verified this by looping through the atoms in
the neighbor list, and counting the number of interactions as well as printing the
shifted interatomic distances for a water box. I consistently count
N*(N-1) interactions for a N-atom box, and the shifted interatomic distances
are consistently under half of the box diagonal.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I am worried about the other possible consequences of my change;
will this adversely affect the molecular dynamics or create artifacts in some
unexpected way? I am aware that this will lead to situations where a
solvent molecule may see both sides of a larger solute, but I can accept those
relatively small effects. My main goal is to run NPT dynamics on a QTPIE water
model and verify physical properties like density, dielectric constant, etc.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks a lot for your help!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Lee-Ping<o:p></o:p></p>
</div>
</body>
</html>