- Chimera-users - RBVI Mailing Lists

Re: [Chimera-users] printing "zone" search
by Ryan 15 Dec '07

15 Dec '07

Hi Eric, thanks for your help. I'm getting closer to achieving the results i'd like. So i've been able to properly select the residues within a specified radius of my ligand, but am a little confused as to how Chimera handles the selection list. If i try: print chimera.selection.currentResidues() i get a list like this: > [<_chimera.Residue object at 0x578d2020>, <_chimera.Residue object at 0x578cbfb0>, ... ] but if i try: for x in chimera.selection.currentResidues(): print x i get output that is much closer to what i'm looking for: > #0:499 > #0:496 > ... What is the reason for the difference between these two forms of output that seem to be accessing the same list? Also, is there a way i can get more detailed output with residue names and numbers, such as ['#0:TYR499','#0:TRP496',...]? Sorry if these questions are answered elsewhere, but i could not find the answers online. Is there a document out there that can teach me how to better master the Chimera Python modules for scripting? I'm no Python expert -- i've so far only been learning things as i need them. Thanks again, ryan

2 1

Multi-scale models and BIOMT
by Ken Jang 14 Dec '07

14 Dec '07

Hello, I work at Boston University working mostly with pili and helical reconstructions. Recently we have been trying to fit our subunit structures into maps generated from EM data. Because what we work with are helical in nature, we use BIOMT symmetry since it is the easiest to generate using readily available data. We wanted to see just how close our subunits get and wanted to use the MSC or Color Zone commands, but we have run into a problem with the Multi-Scale Models command. Since we are using the same BIOMT data, we assumed that Multi-Scale Models would use the same origin and orientation. This appears to be the case if we don't move the subunit structure after opening it, but after we move the subunit, the generated models don't seem to be in any relavent orientation. I have attached two pictures, both from the same view, and one showing the placement of the subunits using the 'sym' command and the other showing the surface models using Multi-Scale models. Both cases were generated off the same selected subunit. Any advice or clarification on how to use Mult-Scale Models and BIOMT information would be greatly appreciated. Be seeing you- Ken Jang -and all places are alike to me

2 1

Re: [Chimera-users] printing "zone" search
by Ryan 14 Dec '07

14 Dec '07

I am actually currently interested in doing something similar to Francesco's previous question about writing out a list of residue names within a certain zone of a ligand -- however i would like to do this from a Python script. I tried to find the zone selection command to use in a script, but could not. Would it be easiest to just use the runCommand('z<') function to select a zone? Also, when the zone is selected, are the selected residue names stored in a list? If so, how can i access this list to print out the residue names into an output file of my own? Thanks a lot, ryan

2 2

edges
by Vincent Racaniello 14 Dec '07

14 Dec '07

When I display a protein as an edged ribbon, sometimes they have a black line on the edges, other times none. There seems to be no consistency in this behavior. The same also happens with surfaces. Is there a way to regulate this appearance?

2 1

Morphing on small ligand
by Jean Didier Pie Marechal 14 Dec '07

14 Dec '07

Hi everyone, I have a " small" ligand with two substantially different conformations. Just for interest: could we use the morphing module to generate intermediate conformations between those two structures? Cheers, JD Dr. Jean-Didier Maréchal Professor Lector Unitat de Química Física Departament de Química Universitat Autònoma de Barcelona Edifici C.n. 08193 Cerdanyola (Barcelona) Tel: +34.935814936 e-mail: JeanDidier.Marechal(a)uab.es

2 1

printing "zone" search
by Francesco Pietra 13 Dec '07

13 Dec '07

I am looking at the protein residues "responsible" for docking a single-residue ligand. select protein & :ligandname z<# works for various values of #. I would like to print the list of residues instead of having to detect them from the screen, which may lead to errors. Also, which section of the manual concerns RMSD? (I would like to calculate RMSD at various stages of DOCK6.1 and Amber9 MD for the above, i..e. how the ligand adapts and the protein follows it, or vice-versa). Thanks francesco pietra ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1

Writing alignment and RMSD out
by shengzhiya＠nibs.ac.cn 11 Dec '07

11 Dec '07

Dear all, I would like to write both the sequence alignment and RMSD out after run “mmaker”, but I do NOT want to do this interactively because I have a batch of structures to deal with. I found Eric’s python script: structAlign.py, which is gui-only, but I do not know how to extract RMSD from the Reply Log in gui mode. Any help would be appreciated. Thanks a lot! Btw, may I know how to run structAlign.py? Is there any command like “chimera structAlign.py” and where should I put the input file structList? I can not run this script right now and here is the error message I got after run “chimera structAlign.py”: Traceback (most recent call last): File "/home/sheng/local/bin/chimera/share/__main__.py", line 59, in ? value = chimeraInit.init(sys.argv) File "CHIMERA/share/chimeraInit.py", line 298, in init chimera.openModels.open(a, prefixableType=1) File "CHIMERA/share/chimera/__init__.py", line 1253, in open File "CHIMERA/share/chimera/__init__.py", line 746, in _openPython File "/home/sheng/local/bin/chimera/from_mailinglist/structAlign.py", line 18, in ? pdb1, pdb2, output = line.strip().split() ValueError: need more than 2 values to unpack Error while processing structAlign.py: ValueError: need more than 2 values to unpack (see reply log for Python traceback info) Best wishes, Zhiya

3 5

how to export the volume data which is stored in the memory?
by Zhiheng Yu 05 Dec '07

05 Dec '07

Hi, I loaded some volume data (mrc files) into Chimera remotely from a network hard drive. Unfortunately, the network hard drive crashed so I can not access those mrc files anymore. But in Chimera which was started before the drive crash, I still have the volume data and am still able to manipulate them. Apparently, these are stored in the memory. Does anyone know how can I export these data onto a hard drive. I tried "save as" but there is an I/O error since the computer was simply trying to duplicate data from the crashed drive. Any suggestion is appreciated. Thanks, Zhiheng

4 7

Re: [Chimera-users] how to export the volume data which is stored in the memory?
by Tom Goddard 05 Dec '07

05 Dec '07

Hi Zhiheng, Here is a script to write out the maps in memory using Chimera 1.2199. You open this script with menu entry File / Open... from the main Chimera window. It will write the files to /tmp. Of course be sure to check those files before closing Chimera. Tom Zhiheng Yu wrote: > Hi Tom, > > I got the following information: > > Beta Version 1 build 2199 2006/01/24 > Platform: linux 2. Windowing system:x11. > > Apparently, it is an older version. > > Thank you very much for your generous help. I really appreciate it. > > Zhiheng > > Tom Goddard wrote: >> Hi Zhiheng, >> >> You must be using an older version of Chimera. Old versions read >> the original file even if the map was in memory when writing out the >> data. Maybe I can give you a script that will write the maps out >> from memory if you tell me what version of Chimera you are running >> (menu entry Help / About UCSF Chimera). >> >> Tom >> # # Write maps to files. For Chimera 1.2199. Only use in-memory copy. # Written for Zhiheng Yu to recover maps lost to failed disk. # from VolumeData import Array_Grid_Data from VolumeData.mrc.writemrc import write_mrc2000_grid_data from VolumeViewer import volume_dialog from os.path import join dir = '/tmp' # Location to write maps. d = volume_dialog() for v in d.data_regions: m = v.full_matrix(read_matrix = False) if not m is None: a = Array_Grid_Data(m, v.data.origin, v.data.step) path = join(dir, v.data.name) write_mrc2000_grid_data(a, path)

1 0

(no subject)
by Julien Orts 04 Dec '07

04 Dec '07

Dear Chimera people, I would like to save a lot of pdb. I have for example 500 pdb. Each saved pdb file should contains 2 pdbs of these 500 pdbs. I can write a script for this but the command write does not work for more than two pdb. Is there any other way? thank you Julien

2 1