<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>I wasn’t saying that it was impossible to achieve the desired result if the selection were treated as if it were “cut out” of the larger sequence, just that it avoided possibly surprising results if you had only selected the domain on one of the structures. Convenience is an upside after all! Nonetheless, the slower matching is a definite downside. But like I said, the first thing I would do is speed up the underlying Needleman-Wunsch matching. It might make the issue moot.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>I have entered your other two suggestions into our Trac database as RFEs. They are both good ideas. As for the ChimeraX timeline, we are shooting for a beta release in the summer of next year.</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 class=""><br class=""></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Nov 24, 2015, at 2:41 AM, Oliver Clarke <<a href="mailto:olibclarke@gmail.com" class="">olibclarke@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Eric,</div><div class=""><br class=""></div><div class="">Thanks for the reply! Not sure I understand the upside - in your scenario, couldn’t you just also select the appropriate domain in the other structure and restrict selection for both target and reference to achieve the same thing? In any case, it would be definitely helpful for edge cases (5000 residue chains…) if this worked differently in ChimeraX. </div><div class=""><br class=""></div><div class="">Also, with regards to possible enhancements to matchmaker for ChimeraX, have you considered incorporating an option to force symmetric alignment for symmetric oligomers (e.g. ion channels)? This sort of happens by default if you leave the “iterate by pruning long atom pairs” option off, but it would be nice to take advantage of this option to improve the alignment while still enforcing symmetry. </div><div class=""><br class=""></div><div class="">Additionally, and I don’t know if this is practical, when I use the “prune long atom pairs” option, it might be helpful for reporting purposes if Chimera still wrote the RMSD calculated with respect to the original set of atom pairs to the reply log - I am thinking specifically in the case that I select all CAs and then restrict to selection, I would like to be able to say “the R.M.S.D. over all Ca pairs is x Å”, in addition to specifying the RMSD calculated with respect to the pruned set of atom pairs - does that make sense or am I misunderstanding something basic about the way matchmaker works that makes this idea impractical?</div><div class=""><br class=""></div><div class="">By the way, do you guys anticipate doing a beta release of ChimeraX at some point? Or you’re doing that internally and planning to just go straight to general release?</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Oliver.<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Nov 23, 2015, at 2:38 PM, Eric Pettersen <<a href="mailto:pett@cgl.ucsf.edu" class="">pett@cgl.ucsf.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div 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 domain restriction capability was added well after most of MatchMaker had been implemented and I might have done things differently if it was part of the initial design — and I might not have. The way it works is that it doesn’t completely ignore the non-selected part of the chain, it just pretends there is no structure associated with those parts and that the sequence composition (but not length) is unknown. Therefore the sequence-alignment isn’t speeded up by the factor that you would anticipate given the size of the domain vs. the whole sequence. There is <i class="">some</i> upside though. Let’s say you have a chain of two identical domains connected by a hinge and you have two conformations of that. If you select the second domain in one of the structures and turn on selection restriction, MatchMaker will always match it to the correct domain in the other structure, whereas if you were completely ignoring everything outside the restriction it would be a 50/50 shot as to whether it would match it against the correct domain.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>The MatchMaker code is pretty intricate, given all its options, and I would be hesitant to change how it works in order to address this. What I would probably do it translate the underlying Needleman-Wunsch sequence alignment code from Python to C++, which would likely make this problem mostly moot. I will undoubtedly do that for ChimeraX. I’m somewhat less likely to do it for Chimera “classic”, though I might back port the code once it’s written for ChimeraX.</div><div class=""><br class=""></div><div class="">—Eric</div><div class=""><br class=""><div apple-content-edited="true" class="">
<div style="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 class=""><br class=""></div></div>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Nov 21, 2015, at 5:15 PM, Oliver Clarke <<a href="mailto:olibclarke@gmail.com" class="">olibclarke@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi all,<br class=""><br class="">When using Matchmaker, the ‘Further restrict to matching selection’ option does not seem to improve the speed of alignment as much as expected under certain circumstances (when the selection is a subset of a larger chain, as opposed to being an individual chain in a multi chain structure). <br class=""><br class="">It seems to still restrict the selection correctly for the final alignment (it is still only aligned on the selected domain), but the “test match” step seems to be conducted on the entire chain, rather than the selection - this makes a big difference to speed for large proteins.<br class=""><br class="">For example - I tried aligning two conformations of a protein complex consisting of one chain A ~100 residues, and chain B ~5000 residues.<br class=""><br class="">If I select chain A of both structures, and then select ‘Further restrict to matching selection’ for both the reference and the structure to match, the alignment is almost instantaneous - less than 2s.<br class=""><br class="">If I perform the same operation, but this time selecting the first 100 residues of chain B in each structure, the alignment takes 3min20s, regardless of whether I leave automatic chain pairing on or select the specific chains to use for alignment manually. It takes only marginally longer - 5 min - if I select the entirety of chain B, a selection that is 50X the size.<br class=""><br class="">Incidentally I still get the “test match” message in the status bar even when the selection only contains one chain from each structure, or when I manually select (using the chain pairing options) which chains to align - maybe Chimera is still running test match on the whole chain when it should only do so on the selection (or not at all if the selection only includes one possible match).<br class=""><br class="">This seems like a bug? Or am I missing something?<br class=""><br class="">Cheers,<br class="">Oliver.<br class=""><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=""><a href="http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users" class="">http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users</a><br class=""><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>