savepos/reset problem with sessions and volumes

Hi Christopher, The problem is that Chimera does not preserve the model numbers of volume data sets when it restores a session. Restoring a saved position then moves the wrong models because it remembers the position associated with each model number. There are two Chimera bugs here. First the volume data restored from a session file should use the original model numbers. And secondly, even if the model numbers were to change, the savepos information should be updated to use the new model numbers. These problems exist in all versions of Chimera on all platforms. I'll work on fixing them and send you email if I get it working. I think I can fix the code so that your existing session files will restore correctly using the original model numbers. Tom Christopher Akey wrote:
Tom-
I am using a build of Chimera from 11/08/2006 for windows. This version is useful for us because the map to map correlation (fit map) and the transform as both work nicely.
However, I tried the savepos/reset within a session today. Set up a new session that I would not be changing or if so, only by adding additional files to the end of the listed files. The problem is that when I close the session and recall it, then the reset commands invariably leave one or two volumes out of alignment. The problem is that every time I open the same session, the model list changes order, ie it does not seem to be completely set in stone. If only one of your aligned images changes order (actually 2 then), then all your previous commands are for naught, unless you go ahead and realign them in the current session. Problem is you don't realize they are misaligned until after you use reset and must immediately undo move, or you are screwed. Also, you might have a mixture of brix and mrc files, such that you might not always be able to recover the right alignment for a file.
Is this a windows version feature? I have noticed my files not behaving properly before, but now have pinned it down.
Do the models and their assoc numbers absolutely remain the same for ALL MODELS in the linux version or in a newer windows version?
The savepos/reset is great, you can theoretically recall you previous figure positions and reshoot them after tweaking a color for a model or whatever.
cheers C Akey

Hi Christopher, I've changed Chimera code so that restoring a session with volume data will use the original model numbers from when the session was saved. This should fix the problem where using the "reset" command to return to a saved view point does not work correctly. The restored model numbers will be correct even with session files written with previous Chimera versions. Here is the new code: https://www.cgl.ucsf.edu/cgi-bin/chimera-get.py?file=prerelease/volumeviewer... This zip file contains a folder VolumeViewer that replaces the one in your current Chimera 1.2348 - 1.2352 in directory chimera/share or on the Mac in Chimera.app/Contents/Resources/share On the Mac you need to ctrl-click the Chimera icon and select "Show Package Contents" to see the folders hidden inside Chimera.app. The new code won't work with Chimera versions older than 1.2348. Tom
participants (1)
-
Thomas Goddard