<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Yes I do. I'm currently revising the manuscript that prompted this implementation to begin with. After that I will probably port it into a release branch if other developers think it's a good idea. Just to be clear: it's not ordinary distance/angle restraints, but a tweak to the pull code to make use of helical and circular reaction coordinates.<div><br></div><div>Erik<br><div><br><div><div>On 1 Jul 2013, at 22:48, David Mobley <<a href="mailto:dmobley@gmail.com">dmobley@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>Thanks. Do you have any interest in doing so?<br><br></div>Also, to
the developers more broadly: I believe the current code also doesn't
support lambda exchange with multiple cores per lambda value when using
distance restraints (via 'distance_restraints' in the topology file)
which is probably another argument towards trying to make the restraints
functionality in the pull code work better to replace the restraints
functionality currently in topology files, as right now I have several
different things I'd like to do that just can't be done without code
changes.<br>
<br>Thanks!<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jun 30, 2013 at 2:01 PM, Erik Marklund <span dir="ltr"><<a href="mailto:erikm@xray.bmc.uu.se" target="_blank">erikm@xray.bmc.uu.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">It's my personal copy. Also it was based on 4.5.5, but I would think that my changes should be fairly easy to port to 4.6.X.<span class="HOEnZb"><font color="#888888"><div>
<br></div><div>Erik</div></font></span><div><div class="h5"><br><div><div>On 29 Jun 2013, at 19:39, David Mobley <<a href="mailto:dmobley@gmail.com" target="_blank">dmobley@gmail.com</a>> wrote:</div><br><blockquote type="cite">
<div dir="ltr">Erik,<br><br>That's good to know. By "hacked", do you mean this is in your personal copy, or is it in the release?<br><br>Thanks.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Jun 24, 2013 at 2:28 AM, Erik Marklund <span dir="ltr"><<a href="mailto:erikm@xray.bmc.uu.se" target="_blank">erikm@xray.bmc.uu.se</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>Hi,</div><div><br></div><div>I hacked the pull code to work in the direction of a helical reaction coordinate. In the special case of helix pitch == 0 you get angular or torsional restraints. It could probably do with further generalisation, but at least it's a starting point if anyone's interested.</div>
<div><br></div><div>Erik</div><br><div><div><div>On 21 Jun 2013, at 22:44, David Mobley <<a href="mailto:dmobley@gmail.com" target="_blank">dmobley@gmail.com</a>> wrote:</div><br></div><blockquote type="cite">
<div><div dir="ltr">Hi,<br><br>Anyone have any insights on this? Do we need to think about implementing angle/torsional restraints in the pull code, or can we re-cast the restraints available within topology files to use absolute atom numbering?<br>
<br>Thanks.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 14, 2013 at 12:47 PM, David Mobley <span dir="ltr"><<a href="mailto:dmobley@gmail.com" target="_blank">dmobley@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi, devs,<br><br></div><div>I'm writing with an issue relating to the interplay of new free energy features with restraints.<br>
</div><div><br></div>I'm very much appreciating some of the new free energy features in gromacs, such as the 'couple-moltype' option which provides a way to set up decoupling or annihilation of a specific molecule via free energy calculations without having to edit the topology file directly. This is especially great when it comes to decoupling -- charge decoupling was not previously possible via topology file editing, and vdW decoupling took substantial manipulation of the topology file.<br>
<br>However, for binding free energies, my work employs orientational restraints between the protein and ligand. I need to be able to impose both dihedral and angle restraints on angles between the protein and ligand. Currently, I do this using angle-restraints and dihedral-restraints. This requires that both the protein and ligand be within the same logical 'molecule', which (unfortunately) means that I can't make use of the new free energy features above, since couple-moltype has to apply to a whole molecule, not just part of a molecule.<br>
<br></div>So, my I see two possible solutions to the problem, and hence have these questions:<br>1) Can dihedral and angle restraints be applied via the pull code? If not, are there any plans to add that?<br></div>2) Alternatively, what about modifying the restraints code so it uses (or at least optionally allows) absolute atom numbering, rather than numbering within a specific molecule, thus allowing restraints (angle-restraints and dihedral-restraints) to be applied between 'molecules'?<br>
<br></div>Thanks!<span><font color="#888888"><br>David<br><br clear="all"><div><br>-- <br>David Mobley<br><a href="mailto:dmobley@gmail.com" target="_blank">dmobley@gmail.com</a><br>
949-385-2436<br>
</div></font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>David Mobley<br><a href="mailto:dmobley@gmail.com" target="_blank">dmobley@gmail.com</a><br>949-385-2436<br>
</div></div><span><font color="#888888">
-- <br>gmx-developers mailing list<br><a href="mailto:gmx-developers@gromacs.org" target="_blank">gmx-developers@gromacs.org</a><br><a href="http://lists.gromacs.org/mailman/listinfo/gmx-developers" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-developers</a><br>
Please don't post (un)subscribe requests to the list. Use the <br>www interface or send it to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.</font></span></blockquote>
</div><br></div><br>--<br>
gmx-developers mailing list<br>
<a href="mailto:gmx-developers@gromacs.org" target="_blank">gmx-developers@gromacs.org</a><br>
<a href="http://lists.gromacs.org/mailman/listinfo/gmx-developers" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-developers</a><br>
Please don't post (un)subscribe requests to the list. Use the<br>
www interface or send it to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br><br clear="all"><br>-- <br>David Mobley<br><a href="mailto:dmobley@gmail.com" target="_blank">dmobley@gmail.com</a><br>
949-385-2436<br>
</div>
-- <br>gmx-developers mailing list<br><a href="mailto:gmx-developers@gromacs.org" target="_blank">gmx-developers@gromacs.org</a><br><a href="http://lists.gromacs.org/mailman/listinfo/gmx-developers" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-developers</a><br>
Please don't post (un)subscribe requests to the list. Use the <br>www interface or send it to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.</blockquote></div>
<br></div></div></div><br>--<br>
gmx-developers mailing list<br>
<a href="mailto:gmx-developers@gromacs.org">gmx-developers@gromacs.org</a><br>
<a href="http://lists.gromacs.org/mailman/listinfo/gmx-developers" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-developers</a><br>
Please don't post (un)subscribe requests to the list. Use the<br>
www interface or send it to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br><br clear="all"><br>-- <br>David Mobley<br><a href="mailto:dmobley@gmail.com" target="_blank">dmobley@gmail.com</a><br>
949-385-2436<br>
</div>
-- <br>gmx-developers mailing list<br><a href="mailto:gmx-developers@gromacs.org">gmx-developers@gromacs.org</a><br>http://lists.gromacs.org/mailman/listinfo/gmx-developers<br>Please don't post (un)subscribe requests to the list. Use the <br>www interface or send it to gmx-developers-request@gromacs.org.</blockquote></div><br></div></div></body></html>