<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; ">Hi Zoltan,<div><br></div><div> Unfortunately sessions don't save colors of a density map contour surface set by the Measure and Color Blobs dialog. It should. But here's the technical reason that it doesn't. With a density map contour surface one commonly changes the contour level and the surface changes shape. Methods for coloring the surface are responsible for updating the coloring. Sometimes this is possible, for example if the surface is colored by distance from the center (radial coloring), but other times it is not possible, for instance if you colored connected blobs, those blobs may have merged. If you change contour level the color blobs coloring simply disappears. Also the color blobs tool does not save its results in session files. Currently only coloring methods that know how to recolor a surface save their coloring in a session file. The reason for that is because the density map surface is not saved in the session file. It is simply recomputed when the density map is opened. Know doubt this was more than you wanted to know.</div><div><br></div><div> Let me suggest another way to do it where the coloring will be saved, and maybe you can even do better color annotation. Make your density map surface (say model #0), then use command "sop split #0". This will create a copy of the surface where each connected blob is a separate selectable piece. You can still use Measure and Color Blobs, or you can simply select a blob with the mouse (ctrl-click) and color it (e.g. Actions / Color / From Editor). Because you can select any blobs you want you can also hide or show whichever you like (Actions / Surface / Show or Hide. And any coloring or show/hide state for this model will be saved in the session file. The reason this one gets its colors saved is because the whole surface is saved in the session file because it is not a density map. It is simply a surface that was copied from a density map surface.</div><div><br></div><div> The drawback of this method is that Chimera may get very slow if you split a surface with 100,000 pieces. If that is your situation (likely for EM tomogram data unless you cut out a small region) then you can instead simply copy the density map surface with a command "sop finerMesh #0 spacing 100". This copies the surface but does not split it into selectable connected blobs. So then you will have to use Measure and Color Blobs to color individual blobs as you are doing now. This finer mesh command actually will not make a finer mesh if you choose the mesh spacing bigger than your density map grid spacing (e.g. 100 Angstroms) -- then it just copies the original mesh. Unfortunately there is not a copy surface command, so this is a trick to copy the surface. I need to add that command.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Tom</div><div><br></div><div><img height="554" width="505" apple-width="yes" apple-height="yes" id="2ad8a0a8-f0d7-446f-a67c-cfaaab19b63c" src="cid:757141A1-8DBA-422A-8F57-38B2E146D8EA@cgl.ucsf.edu"></div><div><br><div><div>On Aug 20, 2013, at 3:26 PM, Zoltan Metlagel wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div>Hi everyone,<br></div>I've been trying to color blobs of different sizes in a tomogram by un-hiding them in order of size using the "hide dust" tool and coloring as they become visible. This has been working well and given me some insight into the structure I'm looking for, but I'm unable to restore the session to it's previous state using the "save session"/"restore session" features. The maps open fine, but all the coloring is lost. I've tried this in Chimera 1.7 and 1.8, with the same results. Am I missing something? According to the online manual, colors should be saved in a session. I apologize if this has been asked before, but I haven't been able to find the solution in the archives either. I'm otherwise very happy with Chimera, thanks for all your efforts.<br>
<br>Thanks in advance,<br><br></div>Zoltan Metlagel, LBNL<br></div>
_______________________________________________<br>Chimera-users mailing list<br><a href="mailto:Chimera-users@cgl.ucsf.edu">Chimera-users@cgl.ucsf.edu</a><br>http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users<br></blockquote></div><br></div></body></html>