<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi David,<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>An approach to make the playback faster is to define all your frame-attr data at once by make one big defattr file that is basically all your attribute files concatenated together, but with the attribute names changed to append the corresponding frame number, <i class="">i.e.</i> a file that defines <i class="">myattr1</i>, <i class="">myattr2</i>, etc. Then in your perframe command, use $1 to add the frame number to the end of the attr name.<br class=""><div 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>So while the defattr part of your process will be considerably slower, the playback will be faster. This approach has the additional advantage that if you save a session, all the attribute definitions will be preserved and you won’t need to redefine them.</div></div></div><div><br class=""></div><div>—Eric</div><div><br class=""></div><div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; 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><br class="Apple-interchange-newline">On Nov 26, 2018, at 8:49 PM, David Slochower <<a href="mailto:slochower@gmail.com" class="">slochower@gmail.com</a>> wrote:</div><blockquote type="cite" class=""><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; line-break: after-white-space;" class=""><div class="">Hi,</div><div class=""><br class=""></div><div class="">As a follow up to this thread (<a href="http://plato.cgl.ucsf.edu/pipermail/chimera-users/2009-March/003712.html" class="">http://plato.cgl.ucsf.edu/pipermail/chimera-users/2009-March/003712.html</a>) from 2009, I’d like to color a model by a custom attribute that changes from frame to frame. Using the workaround mentioned in that thread, we are able to use Per-Frame commands to load a new attribute file each frame, and then color the structure by the attribute, but this awfully slow (probably over 1 second per frame). </div><div class=""><br class=""></div><div class="">Is there a way to cache the attribute data? Or a way to improve the performance of defining the attributes and re-coloring the structure? I know that I could use a Python script to load each coordinate frame with its associated attribute data, save images, and then stitch them together for a movie, but the current goal is for data exploration.</div></div>_______________________________________________<br class="">Chimera-users mailing list: <a href="mailto:Chimera-users@cgl.ucsf.edu" class="">Chimera-users@cgl.ucsf.edu</a><br class="">Manage subscription: <a href="http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users" class="">http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users</a><br class=""></div></blockquote></div><br class=""></div></body></html>