<div dir="ltr">Hi Erik,<div><br></div><div>Yes, that should be fine.</div><div><br></div><div>On a wider note, I'm out of time to do 5.1-beta1 today, so I'll try again Monday afternoon.</div><div><br></div><div>Cheers,</div><div><br></div><div>Mark</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 13, 2015 at 3:46 PM, Erik Marklund <span dir="ltr"><<a href="mailto:erik.marklund@chem.ox.ac.uk" target="_blank">erik.marklund@chem.ox.ac.uk</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>Dear all,</div>
<div><br>
</div>
I’ve had a patch for review for a couple of weeks, being one +1 from being accepted. It concerns a periodicity issue with gmx hbond that causes problems for non-periodic systems. May I ask you to consider reviewing <a href="https://gerrit.gromacs.org/#/c/4350/" target="_blank">https://gerrit.gromacs.org/#/c/4350/</a> so
that it can make it for 5.1? Although most simulations use periodic boxes there is a growing number of gas-phase studies and it would be a shame to keep users waiting for a fully functioning analysis tool when there is a committed bug fix.
<div><br>
</div>
<div>Kind regards,</div>
<div>Erik</div>
<div><br>
</div>
<div><br>
<div>
<div style="color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div>
<div>Erik Marklund, PhD</div>
<div>Postdoctoral Research Fellow, Fulford JRF</div>
<div>
<div><br>
</div>
<div>Department of Chemistry</div>
<div>Physical & Theoretical Chemistry Laboratory</div>
<div>University of Oxford</div>
<div>South Parks Road</div>
<div>Oxford</div>
<div>OX1 3QZ</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div>
<blockquote type="cite"><div><div class="h5">
<div>On 10 Feb 2015, at 15:30, Magnus Lundborg <<a href="mailto:magnus.lundborg@scilifelab.se" target="_blank">magnus.lundborg@scilifelab.se</a>> wrote:</div>
<br>
</div></div><div><div><div class="h5">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi,<br>
<br>
Sounds good. It would be nice to get my latest TNG version patch in there, but it's on master, so perhaps it's already planned.<br>
<br>
Cheers,<br>
<br>
Magnus<br>
<br>
On 02/10/2015 04:00 PM, Mark Abraham wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>Sorry for quietness on the management front, I've had a bunch of non-code tasks lately. We're a few weeks behind on my original timeline for 5.1-beta1. Various people had expressed hopes of putting code on gerrit, but few things have actually
appeared, so I think we should pretty much regard the feature stuff on gerrit now as the maximum extent of 5.1. There's still a bunch of dead / experimental patches on gerrit that won't make the 5.1 cut, of course. Please speak up super-fast if that's a problem
- you should have had code in gerrit a month and more ago!</div>
<div><br>
</div>
<div>So I plan to roll 5.1-beta1 from master HEAD on Friday, and branch release-5-1 and Jenkins infrastructure at that time. Per my original suggestion, release-5-1 will be open for "feature"-type content for a few weeks while we deal with remaining
code review of things currently on master. Once we release 5.1-rc1 (perhaps after another beta if appropriate) then features are frozen. The gerrit cherry-pick feature should be good for people to make clear that they are proposing a "feature" patch for release-5-1.</div>
<div><br>
</div>
<div>I'd like to see a couple more of the new Sphinx-based docs commits at
<a href="https://gerrit.gromacs.org/#/q/status:open+project:gromacs+branch:master+topic:docs" target="_blank">
https://gerrit.gromacs.org/#/q/status:open+project:gromacs+branch:master+topic:docs</a> get merged, so that we can invite users to give feedback or contribute docs.</div>
<div><br>
</div>
<div>It would be great for our colleagues at StreamComputing if we get their OpenCL work out to the world in the first beta; I know Berk has given some feedback but is basically OK with the commit. Szilard has a few outstanding questions we can probably
resolve quickly. I have a reservation about whether using more than one Nvidia GPU works, but since that is in any case not a useful configuration for performance, we can hack a temporary fatal error in front of that and ship something usable.</div>
<div><br>
</div>
<div>Szilard's CUDA work needs to get in, but the remaining issues there are minor, I think.</div>
<div><br>
</div>
<div>Berk's halo-decomposition is not yet clearly useful (right, Berk?) so perhaps we will leave that on the shelf for now.</div>
<div><br>
</div>
<div>Erik's SIMD support patches need one more reviewer. It would be nice to be able to say to hardware devs that we already have preliminary support in released code when early-phase testing is on the cards.</div>
<div><br>
</div>
<div>Happy hacking!</div>
<div><br>
</div>
<div>Mark</div>
</div>
<br>
<fieldset></fieldset> <br>
</blockquote>
<br>
</div></div></div><span class="HOEnZb"><font color="#888888">
-- <br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" target="_blank">
http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">
http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to
<a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.</font></span></div>
</blockquote>
</div>
<br>
</div>
</div>
<br>--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br></div>