[Chimera-users] v1.1951 save session not reopening grasp surfaces that were there before i saved session

Hi, I had to resort to using grasp surfaces because MSMS doesn't behave "nicely" when dealing with multiple free floating residues that come directly from a PDB file. Although grasp surfaces are lower in visual quality than MSMS, grasp rendered all the areas I wanted whereas the MSMS plugin could not. So, after I did save session and re-opened the session the grasp surfaces did not reappear. Is there anyway to add functionality so that the grasp surfaces, colors, and the corresponding locations can be recalled when I load the saved session file? This saves time especially when there are many grasp surface components each with different colors. One more minor detail/UI glitch I noticed?: Color Editor -> click opacity : the "A" row along with slider appears -> unclick opacity : the sliders disappear but the "A" along with row space remains ...don't know if that was done on purpose. Thanks for the great program!

Hi Sabuj, If I understand correctly you display GRASP surfaces in Chimera using the DelphiViewer extension and color them using an electrostatic potential. You are right that that information is not saved in Chimera sessions. Unfortunately many Chimera extensions do not save what they do when you save a session. Two ways of adding the GRASP session saving you want are possible but both require significant work for us to implement. It would help to know which method would be best for you. Then we can put it on our requested features list and evaluate how hard it is and what priority it has relative to other new features. The first method is for the DelphiViewer to remember all it's settings and surfaces it made. It would remember the potential files you used, the GRASP surface files and the thresholds and colors you set. Then when reloading a session it would reread those files and recalculate the colors for the surface. The other approach is that sessions would just remember the colored surface directly but would not remember how DelphiViewer created it. You wouldn't need to have the potential file around, but you also wouldn't get back the threshold and color settings you originally used. Thanks for reporting the color editor opacity bug. It will go into our bug database and should be fixed in the next release. If you can't find a bigger bug than that (not counting missing features) then we are doing pretty good. Tom
participants (2)
-
Pattanayek, Sabuj
-
Thomas Goddard