<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Oliver,<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>The tremendous slowness is due to Chimera considering hydrogen bonding interactions for choosing which rotamer to use. So this means a donor/acceptor calculation for each <i class="">possible</i> rotamer at each position. I don’t think this can be avoided without a significant hit to the quality of the rotamer choice. However, it <i class="">is</i> doing something inefficient in your case. It isn’t ignoring other models when looking at rotameric hydrogen bonding interactions. Therefore the fact that that you have several models open at once is slowing you down. I’ve just changed the code so that when Dock Prep calls the rotamer code it tells it to consider each model in isolation. I’ve done the same for Dock Prep calling the add-hydrogen code (only matters in nogui mode since the GUI dialog offers explicit control over that setting). I don’t know that it would help enough in your case (or similar cases since you’ve already dealt with your structures) but it’s something.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>I hope to move the H-bond finding code from Python to C++ for ChimeraX, but the code is complicated and relies on some underlying chemical group-finding code, so it’s not 100% settled if the code will move or not.</div><div class=""><br class=""></div><div class="">—Eric</div><div class=""><br class=""></div><div class=""><br class=""><div apple-content-edited="true" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Eric Pettersen</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>UCSF Computer Graphics Lab</div></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Nov 20, 2015, at 11:35 AM, Oliver Clarke <<a href="mailto:olibclarke@gmail.com" class="">olibclarke@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">As an addendum to this for anyone who encounters the same situation - I gave up and used SCWRL4 instead, with the -v flag for increased speed. Perhaps not as good, but for multiple large structures it might be the only time-efficient way of filling partial rotamers in a sensible way.<br class=""><br class="">Cheers,<br class="">Oliver.<br class=""><blockquote type="cite" class="">On Nov 20, 2015, at 7:54 AM, Oliver Clarke <<a href="mailto:olibclarke@gmail.com" class="">olibclarke@gmail.com</a>> wrote:<br class=""><br class="">Hi,<br class=""><br class="">Would it be possible to add a progress bar (with ETA) for Dock prep at some point? I ran it overnight to fill partial sidechains on six structures (each ~6000aas), and it still isn’t finished, but I can’t tell whether it is just taking a really long time or whether something has gone wrong. The status bar is still updating with “Matching donors”, “finding acceptors” and “building search tree” messages, but it seems to be giving these messages multiple times for each structure - is that normal?<br class=""><br class="">Cheers,<br class="">Oliver.<br class=""></blockquote><br class=""><br class="">_______________________________________________<br class="">Chimera-users mailing list<br class=""><a href="mailto:Chimera-users@cgl.ucsf.edu" class="">Chimera-users@cgl.ucsf.edu</a><br class="">http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users<br class=""><br class=""></div></blockquote></div><br class=""></div></body></html>