View scale and brix output

Hi Christopher, If I understand your request you want to be able to easily return to a standard view magnification for making figures. There are 3 parameters that determine the apparent size of models seen in the Chimera window: the distance of the models from the eye position, the angular field of view, and the scale parameter which relates the screen pixels to physical units (Angstroms). With orthographic projection only the scale parameter matters. Chimera can use orthographic projection (activated in Camera tab of Side View dialog) but the default is perspective projection where all 3 parameters matter. Assuming you don't change the distance between the eye (i.e. camera) and the models, and you don't change the field of view then setting the scale alone would be sufficient to return to standard magnification settings. In the Side View dialog (menu entry Favorites / Side View) under the Camera tab there is an entry field for the scale factor. It gives the current absolute scale factor and can be changed to whatever value you like. It starts out as 1.0 in a new Chimera session. But if you open a session file it is set to whatever it was in the original session. If you open a session for a figure, then modify it, changing the scale as you go, then want to return to the original session scale factor you could use the command "reset session-start". This not only resets the scale but also the positions and orientations of all the models. Maybe that is not what you want because the new figure is perhaps showing the models from a different direction (e.g. rotated by 90 degrees). So perhaps you need a command like "resetscale session-start". That resetscale command does not exist but I could probably add it if you think it is what you need. Regarding writing BRIX map files, I agree it would be handy if Chimera could output more map formats. I think BRIX format is well enough documented that it could be done (writing files requires better understanding of the format than reading them). That format only saves unsigned 8-bit data values though. So going from float values in MRC to BRIX will lose information. Maybe Chimera would issue a warning about that. Tom Christopher Akey wrote:
Tom-
A few more issues that have come up for user friendliness.
1. It would be useful to have a box where the user can specify the absolute scale for the session, the first time it is opened, this could be set at 1.0 for example after loading a ribosome map and the atomics and putting them to a good size.
Then the program should keep track of the changes made during the session using the scale command (I guess you can't track changes made with the mouse so one generally would avoid this, or even better one should be able to turn off the mouse scale feature!).
This way one could always look at the pull down for the current scale value when you capture a particular view for a figure.
One could then return to the original scale of 1.0 at the end of session or write down the current scale value, which could be kept in the ssesion. So upon reopening the session at a later date, one can always get back to the correct scale to recapture a panel for a figure. This is currently a real problem, as far as I can tell.
2. We often want to import a brix file with aligned pdbs, since we dock and look at them in 'O', which is better in some ways for looking at these maps, but not so good as Chimera for figure making obviously....then in Chimera we may continue to trim or segment a map, and then we want to take it back out, presumably as an MRC file, to be converted into a brix by a conversion program (for us its SPIDER). Then one can do another cycle of docking in 'O' using the refined/cleaned up sub map from Chimera.
While I can think of one way to do this without losing the relative origins and thus, the map alignments, it is pretty tedious. If one could write the zoned or volume erased brix volume back out as a new brix file, with the correct dimensions and origin, relative to the brix file brought into Chimera, this would allow you to cycle back and forth using the best of both programs.
cheers C Akey

Hi Christopher, Tom did mention "reset," but I thought I'd expand on that topic a bit. You can actually save multiple named positions, which will then be included in a single saved session. When I make a set of figures that differ in view and scale but with basically the same display/coloring setup, I use the "savepos" command to save the position for each figure, and then save the session. It doesn't matter what position everything is in when you save the session, because you will still be able to get back to any of those saved positions with "reset." The saved positions include scale. If you really only want to restore scale, currently you could note the value shown in the Camera tool (as mentioned by Tom), and later type that into the Camera tool to restore it. more about savepos and reset: http://www.cgl.ucsf.edu/chimera/1.2304/docs/UsersGuide/midas/ savepos.html http://www.cgl.ucsf.edu/chimera/1.2304/docs/UsersGuide/midas/reset.html Elaine ----- Elaine C. Meng, Ph.D. meng@cgl.ucsf.edu UCSF Computer Graphics Lab and Babbitt Lab Department of Pharmaceutical Chemistry University of California, San Francisco http://www.cgl.ucsf.edu/home/meng/index.html Christopher Akey wrote:
Tom-
A few more issues that have come up for user friendliness.
1. It would be useful to have a box where the user can specify the absolute scale for the session, the first time it is opened, this could be set at 1.0 for example after loading a ribosome map and the atomics and putting them to a good size.
Then the program should keep track of the changes made during the session using the scale command (I guess you can't track changes made with the mouse so one generally would avoid this, or even better one should be able to turn off the mouse scale feature!).
This way one could always look at the pull down for the current scale value when you capture a particular view for a figure.
One could then return to the original scale of 1.0 at the end of session or write down the current scale value, which could be kept in the ssesion. So upon reopening the session at a later date, one can always get back to the correct scale to recapture a panel for a figure. This is currently a real problem, as far as I can tell.
2. We often want to import a brix file with aligned pdbs, since we dock and look at them in 'O', which is better in some ways for looking at these maps, but not so good as Chimera for figure making obviously....then in Chimera we may continue to trim or segment a map, and then we want to take it back out, presumably as an MRC file, to be converted into a brix by a conversion program (for us its SPIDER). Then one can do another cycle of docking in 'O' using the refined/cleaned up sub map from Chimera.
While I can think of one way to do this without losing the relative origins and thus, the map alignments, it is pretty tedious. If one could write the zoned or volume erased brix volume back out as a new brix file, with the correct dimensions and origin, relative to the brix file brought into Chimera, this would allow you to cycle back and forth using the best of both programs.
cheers C Akey
_______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu http://www.cgl.ucsf.edu/mailman/listinfo/chimera-users

Hi Christopher, David Morgan at UC Davis reports that the SPIDER command to write a BRIX file accepts an origin option that may help getting the MRC and BRIX maps to align in Chimera. Tom David Morgan wrote:
Tom,
I just saw your comments to Chris Akey about chimera, SPIDER, O, BRIX, etc. If you can tell Chris how to set the origin properly, the SPIDER command to write the BRIX file has an option for setting the origin. I've never used anything but the default, so I can't even tell you what sorts of values it can take. But this sounds like there is a simple solution.
participants (3)
-
Elaine Meng
-
Thomas Goddard
-
Tom Goddard