November 2013 - Chimera-users - RBVI Mailing Lists

Changing default max number of histograms shown
by Joel Meyerson 18 Nov '13

18 Nov '13

Hi, By default, Chimera displays up to 3 histograms in the "Volume Viewer". I know that this number can be increased manually in the "Data display options" after launching the program, but I would like to change the default number. Is there a built-in Chimera preference to set the default number to something higher? If not, can you perhaps suggest how this might be scripted to happen upon launching the program? Thanks, Joel

2 2

Multi-fragment fit in map
by Paolo Swuec 18 Nov '13

18 Nov '13

Good morning, I am EM user and I was wondering wether is possible in Chimera to fit multiple pdb in the same volume (e.g. Fitting two monomers into a dimer map without overlaps and clashes). I am using Situs and the collage command, but I was wondering if there was an easy way of doing it in Chimera. Thank you very much, Paolo Paolo Swuec, Ph.D. Student Architecture and Dynamics of Macromolecular Machines London Research Institute Clare Hall Laboratories Cancer Research UK South Mimms Herts EN6 3LD, UK E-mail: paolo.swuec(a)cancer.org.uk<mailto:alessandro.costa@cancer.org.uk> NOTICE AND DISCLAIMER This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. Cancer Research UK Registered charity in England and Wales (1089464), Scotland (SC041666) and the Isle of Man (1103) A company limited by guarantee. Registered company in England and Wales (4325234) and the Isle of Man (5713F). Registered Office Address: Angel Building, 407 St John Street, London EC1V 4AD.

2 1

Question on labeling residues on a single-chain protein
by J. David Puett 15 Nov '13

15 Nov '13

I wish to label certain residues and have these appear along with the structure. I have used the Command line to enter the following. rlabel Met_71.A What other Command(s) is required to display and later print the labeled structure? Many thanks!

2 2

Measure buried area
by Jian Guan 15 Nov '13

15 Nov '13

Hi all, I use measure command to calculate the buried area between capsomer and Fab. My input file is pentamer.pdb and Fab.pdb. I made surface model for them respectively and use the command line as shown below: measure buriedArea #3 #2 probeRadius 1.4 However, it replied as "Surface calculation failed" I tried also delete all non-binding units in the pentamer, it still can not work. Does anyone know how to deal with that? Thank you so much. Sincerely yours, Jian

3 2

Re: [Chimera-users] Residue selection
by Mark Girvin 14 Nov '13

14 Nov '13

Thanks for the info Eric, - Mark ________________________________ From: Eric Pettersen [pett(a)cgl.ucsf.edu] Sent: Thursday, November 14, 2013 3:43 PM To: Mark Girvin Cc: George Tzotzos ‎[gtzotzos@me.com]‎ Subject: Re: [Chimera-users] Residue selection Yeah, waters with a blank chain ID are put in chain "water" and similarly residues in HETATM records with a blank chain ID are put in chain "het". If the chain ID is non-blank, both get assigned the given chain ID rather than "water" or "het". --Eric On Nov 14, 2013, at 12:22 PM, Mark Girvin <mark.girvin(a)einstein.yu.edu<mailto:mark.girvin@einstein.yu.edu>> wrote: Got it. And no problem - just not quite expected. So then chimera sets up internal chain names (like "water") for some entries in PDB files? I don't think George's file had any internal chain entries, or HETATM lines. - Mark ________________________________ From: Eric Pettersen [pett(a)cgl.ucsf.edu<mailto:pett@cgl.ucsf.edu>] Sent: Thursday, November 14, 2013 2:50 PM To: Mark Girvin Cc: George Tzotzos; chimera List Subject: Re: [Chimera-users] Residue selection Yeah, the :127@O behavior is deliberate. If you omit the chain ID, it only matches single-character chain IDs (i.e. not chain ID "water" or "het"). This choice was made so that if your structure has a bunch of waters that so happen to have the same numbers as various polymeric residues, :127 will get the polymeric residue(s) but not the waters. This behavior was more important before the PDB remediation a few years back where such occurrences were commonplace. Now, in standard PDB files waters are frequently assigned specific chain IDs and therefore have different numbers than the polymeric residues. Chimera's behavior still matters for non-standard PDB files generated by various programs. If I were making the decision about Chimera's behavior today, given that the issue no longer affects standard PDB files, it might go the other way (it might not), but I don't feel strongly enough to change anything. A bunch of complaining could change my mind. :-) --Eric Eric Pettersen UCSF Computer Graphics Lab http://www.cgl.ucsf.edu<http://www.cgl.ucsf.edu/> On Nov 14, 2013, at 7:44 AM, Mark Girvin <mark.girvin(a)einstein.yu.edu<mailto:mark.girvin@einstein.yu.edu>> wrote: I don't know why that doesn't work, but: select :WAT@O seems to (if you only have the one water in your pdb file), as does: select :127.water@O (which would presumably limit the selection to the one water molecule) - Mark ________________________________ From: chimera-users-bounces(a)cgl.ucsf.edu<mailto:chimera-users-bounces@cgl.ucsf.edu> [chimera-users-bounces(a)cgl.ucsf.edu<mailto:chimera-users-bounces@cgl.ucsf.edu>] on behalf of George Tzotzos [gtzotzos(a)me.com<mailto:gtzotzos@me.com>] Sent: Thursday, November 14, 2013 8:08 AM To: chimera List Subject: [Chimera-users] Residue selection I'm attaching a pdb file of a protein ligand complex with a single conserve water molecule. The pdb file was constructed with Antechamber Leap. The water molecule is numbered as residue 127. When I try to select using: select :127 nothing happens. Selection works with: select :WAT The problem is that I need to monitor the distance between :127@O and a particular atom in the binding site of the protein during an MD trajectory. My question is if I'm doing something wrong with the residue selection. Many thanks in advance for your help Regards George _______________________________________________ Chimera-users mailing list Chimera-users(a)cgl.ucsf.edu<mailto:Chimera-users@cgl.ucsf.edu> http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users _______________________________________________ Chimera-users mailing list Chimera-users(a)cgl.ucsf.edu<mailto:Chimera-users@cgl.ucsf.edu> http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users

1 0

Residue selection
by George Tzotzos 14 Nov '13

14 Nov '13

I'm attaching a pdb file of a protein ligand complex with a single conserve water molecule. The pdb file was constructed with Antechamber Leap. The water molecule is numbered as residue 127. When I try to select using: select :127 nothing happens. Selection works with: select :WAT The problem is that I need to monitor the distance between :127@O and a particular atom in the binding site of the protein during an MD trajectory. My question is if I'm doing something wrong with the residue selection. Many thanks in advance for your help Regards George

3 3

Re: [Chimera-users] Issues with characters on command line (OS X 10.9)
by Mario Dejung 14 Nov '13

14 Nov '13

Hi Andreas, have you tried copy/paste the character from somewhere, for example Terminal, to the command line? I have “the same” problem with German keyboard layout. I am not able to type the ~ character within the command line of Chimera… But with copy paste, the character is visible and it works… Not a good workaround… by the way… Mario

2 1

Speed problems under Mavericks
by Mario Dejung 14 Nov '13

14 Nov '13

I found Tom Goddard's post about the Mavericks bug and the change on the daily build with the disabled advanced graphics. So I am not sure, if my problem is related to the crashing of chimera. My problem is the speed of chimera under Mavericks. I work with molecules of about 20000 Atoms and rotating a PDB of this size is very painful. I didn’t had problems with Lion. I am wondering now, if I am the only person with speed problems under Mavericks, or if other people have similar issues. Is there a way to improve the speed of chimera under Mavericks? Kind regards Mario

2 1

Re: [Chimera-users] Using runCommand outputs
by Tom Goddard 14 Nov '13

14 Nov '13

Hi Ahir, Every Chimera command has an equivalent Python function. I just didn't tell you all the places you would have to look to find them. Commands that have a separate dialog (graphical user interface) usually have their own code directory and are not in Midas/__init__.py. So for example the findclash command has the equivalent Python function "detectClash()" in directory chimera/share/DetectClash (On Mac the directory is Chimera.app/Contents/Resources/share/DetectClash). So it can be a bit tricky to find the Python. Here's what I do when I can't find the Python code. Each command is registered in Chimera code with the routine addCommand(). So I search for addCommand in all the share directories. Below is a list for Chimera 1.8. You are right that trying to save reply log output instead of directly running Python functions is not feasible for more complex scripts. Tom $ cd Chimera-1.8.app/Contents/Resources/share $ grep "addCommand(" */*.py Accelerators/ChimeraExtension.py:addCommand('ac', accel_cmd, None, help = True, changesDisplay = True) AddAttr/ChimeraExtension.py:addCommand("defattr", cmdAddAttr, help=True, changesDisplay=False) AddCharge/ChimeraExtension.py:addCommand("addcharge", cmdAddCharge, help=True, changesDisplay=False) AddH/ChimeraExtension.py:addCommand("addh", cmdAddH, help=True) Addions/ChimeraExtension.py:addCommand("adions", cmdAddions, help=True) Animate/ChimeraExtension.py:# addCommand(command, cmdFunc, revFunc=None, help=None, changesDisplay=True) Animate/ChimeraExtension.py:addCommand('scene', Animate/ChimeraExtension.py:#addCommand('transition', Animate/ChimeraExtension.py:#addCommand('animate', Animate/ChimeraExtension.py:addCommand('kfadd', Animate/ChimeraExtension.py:addCommand('kfclear', Animate/ChimeraExtension.py:addCommand('kfdel', Animate/ChimeraExtension.py:addCommand('kfmove', Animate/ChimeraExtension.py:addCommand('kfmovie', Animate/ChimeraExtension.py:addCommand('kfsave', Animate/ChimeraExtension.py:addCommand('kfshow', Animate/ChimeraExtension.py:addCommand('kfstatus', Animate/ChimeraExtension.py:addCommand('kftrans', Aniso/ChimeraExtension.py:addCommand("aniso", cmdAniso, revFunc=cmdUnaniso, help=True) BuildStructure/ChimeraExtension.py:addCommand("invert", cmdInvert, help=True) ChangeChainIDs/ChimeraExtension.py:addCommand("changechains", cmdChangeChains, help=True, changesDisplay=False) Combine/ChimeraExtension.py:addCommand("combine", cmdCombine, help=True) CrystalContacts/ChimeraExtension.py:addCommand('crystalcontacts', crystal_contacts_command, help = True) DetectClash/ChimeraExtension.py:addCommand("findclash", cmdDetectClash, revFunc=cmdUndetectClash, help=True) ESP/ChimeraExtension.py:addCommand("coulombic", wrapper, help=True) EnsembleMatch/ChimeraExtension.py:addCommand('tile', tile_cmd, tile_cmd, help = True) EnsembleMatch/ChimeraExtension.py:addCommand('cluster', cluster_cmd, None, help = True) FindHBond/ChimeraExtension.py:addCommand("hbonds", cmdHBonds, revFunc=cmdUnHBonds, help=True) FindHBond/ChimeraExtension.py:addCommand("findhbond", cmdHBonds, revFunc=cmdUnHBonds, help=True) FitMap/ChimeraExtension.py:mt.addCommand('fitmap', fit_map, unfit_map, help = True) Fly/ChimeraExtension.py:addCommand('fly', fly_cmd, help = True) IcosahedralCage/ChimeraExtension.py:Midas.midas_text.addCommand('hkcage', hkcage, help = True) Ilabel/ChimeraExtension.py:addCommand("2dlabels", doLabel2DCmd, help=True) Intersurf/ChimeraExtension.py:midas_text.addCommand("intersurf", emo.commandLine) Lighting/ChimeraExtension.py:addCommand('lighting', lighting, help=True) ListInfo/ChimeraExtension.py:addCommand("list", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("listmodels", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("listchains", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("listresidues", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("listatoms", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("listselection", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("listphysicalchains", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("listen", emo.command, help=True, changesDisplay=False) ListInfo/ChimeraExtension.py:addCommand("sequence", emo.command, help=True, changesDisplay=False) MMMD/ChimeraExtension.py:addCommand("minimize", emo.cmdMMMD, help=True) MMMD/ChimeraExtension.py:#addCommand("dynamics", emo.cmdMMMD, help=True) Mask/ChimeraExtension.py:Midas.midas_text.addCommand('mask', mask_cmd, help = True) MatchMaker/ChimeraExtension.py:addCommand("mmaker", cmdMatchMaker, help=True) MatchMaker/ChimeraExtension.py:addCommand("matchmaker", cmdMatchMaker, help=True) Measure/ChimeraExtension.py:addCommand('measure', measure_cmd, help = True) MeshToMolecule/ChimeraExtension.py:addCommand('meshmol', mesh_to_molecule, help = True) Midas/midas_text.py:def addCommand(command, cmdFunc, revFunc=None, help=None, changesDisplay=True): ModelClip/ChimeraExtension.py:addCommand('mclip', mclip_command, unclip_command, help = True) MoleculeCopy/ChimeraExtension.py:addCommand('mcopy', mcopy_cmd, help = True) MoleculeMap/ChimeraExtension.py:addCommand('molmap', molmap_cmd, help = True) Morph/ChimeraExtension.py:addCommand("morph", emo.cmdMorph, help=True) Movie/ChimeraExtension.py:addCommand('coordset', coordset, help = True) MovieRecorder/ChimeraExtension.py:addCommand("movie", doMovieCmd, help=True, changesDisplay=False) MultiscaleColor/ChimeraExtension.py:Midas.midas_text.addCommand('msc', msc_command, msc_undo_command, help = True) NucleicAcids/ChimeraExtension.py:addCommand('nucleotides', nucleotides, revFunc=unnucleotides, help=True) Play/ChimeraExtension.py:addCommand('play', play, reverse_play, help = ('play.html', 'Play')) RNALayout/ChimeraExtension.py:addCommand('rna', rna_cmd, help = True) Ramachandran/ChimeraExtension.py:addCommand("ramachandran", emo.cmdLine, help=True) ResRenumber/ChimeraExtension.py:addCommand("resrenumber", cmdResRenumber, help=True, changesDisplay=False) Rotamers/ChimeraExtension.py:addCommand("swapaa", cmdRotamers, help=True) Segger/ChimeraExtension.py:Midas.midas_text.addCommand('segment', segment, None, help = True) Shape/ChimeraExtension.py:addCommand('shape', shape_cmd, help = True) Solvate/ChimeraExtension.py:addCommand("solvate", cmdSolvate, help=True) SplitMolecule/ChimeraExtension.py:Midas.midas_text.addCommand('split', split_molecules, help = True, changesDisplay=False) StructureDiagram/ChimeraExtension.py:addCommand("struct2d", emo.cmdLine, help=True, changesDisplay=False) Surface/ChimeraExtension.py:addCommand('sop', sop_cmd, unsop_cmd, help = True) SurfaceColor/ChimeraExtension.py:addCommand('scolor', scolor_cmd, scolor_cmd, help = True) SurfaceColor/ChimeraExtension.py:addCommand('scolour', scolor_cmd, scolor_cmd, help = True) SurfaceZone/ChimeraExtension.py:Midas.midas_text.addCommand('bondzone', bzone, no_bzone, help = True, changesDisplay=False) SymmetryCopies/ChimeraExtension.py:Midas.midas_text.addCommand('sym', symmetry_copies, undo_symmetry_copies, Topography/ChimeraExtension.py:addCommand('topography', topo, help = True) ViewDock/ChimeraExtension.py:addCommand("viewdock", emo.cmdViewdock, help=True) VolumeFilter/ChimeraExtension.py:addCommand('vop', vop_cmd, help = True) VolumeSeries/ChimeraExtension.py:addCommand('vseries', vseries_cmd, help = True) VolumeViewer/ChimeraExtension.py:addCommand('volume', volume_cmd, help = True) Zone/ChimeraExtension.py:Midas.midas_text.addCommand('zonesel', zone_cmd, help = True) apbs/ChimeraExtension.py:addCommand("apbs", emo.cmdLine, help=True) blastpdb/ChimeraExtension.py:addCommand("blast", emo.cmdLine, help=True, changesDisplay=False) blastpdb/ChimeraExtension.py:addCommand("psiblast", emo.cmdLine, help=True, changesDisplay=False) chimera/writeSel.py:addCommand("writesel", midasCmd, help=True) pdb2pqr/ChimeraExtension.py:addCommand("pdb2pqr", emo.cmdLine, help=True) vina/ChimeraExtension.py:addCommand("vina", vinaEmo.cmdLine, help=True) $ On Nov 14, 2013, at 1:21 AM, wrote: > Thanks for the prompt reply Tom, that explains things! I took a look at the init.py file, and I can see that it's not as straight forward and as you said, some runcommand functionality is not represented by midas commands too right? For example, I cant find findclash for example. I am not beyond using runcommand ("findclash" blah blah log/savefile True) etc, but what is the easiest way to feed the output of runcommand that does not have a savefile option , i.e if the ouput goes not to the reply log but rather to IDLE, is there any way of getting this data back to a file, without manually cut and pasting it into a file and saving it? Because the saveReplyLog from tkgui does not save anything if I am running IDLE, because the output goes to IDLE (and I am using IDLE during writing/testing the script). If there is a way of doing this, then its a suitabe workaround for me! > > Thanks again > Ahir > > One thing, > > Quoting Tom Goddard > >> Hi Ahir, >> >> Unfortunately runCommand() does not return any Python objects resulting from the command -- would be convenient if it worked that way. If you want return values from a command you need to call the Python function that does that command. Most of those are in file >> >> chimera/share/Midas/__init__.py >> >> with the function name matching the command name, e.g. rmsd() for the "rmsd" command, or match() for the "match" command. So open that file in a text editor and search for the command you want. We unfortunately don't have documentation on the Python functions so this can be troublesome and I'm sure is why you prefer runCommand(). We will provide documentation for all the Python functions in our next generation Chimera that we are working on now. >> >> Tom >> >> >> On Nov 13, 2013, at 8:40 AM, wrote: >> >>> Hello all, I am getting confused by the runCommand() functionality when I am trying to run scripts. When I run my python script through IDLE(From Tools-General), the ouput of runcommand commands like rmsd etc are given the IDLE. I want to store the output from runcommand into a variable dynamically. I dont want to save from the ReplyLog (by running program without IDLE) or output to file, is there something in python itself that I am not understanding and hence, not using, or is it not possible to store the output of runcommand into a variable/list etc, as it is possible for the midas.rmsd function for example. I only ask because I prefer to use the command line functionality over the midas command. If it is only possible with the direct midas, how do I find out the equivalent command of the runcommand for the midas python formatting? >>> >>> Thank you >>> Sorry if my question is a bit confusing! >>> >>> Ahir >>> >>> ---------------------------------------------------------------- >>> This message was sent using IMP, the Internet Messaging Program. >>> >>> _______________________________________________ >>> Chimera-users mailing list >>> Chimera-users(a)cgl.ucsf.edu >>> http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users >>> >> >> > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. >

1 0

Query related to chimera downloading
by akhilesh verma 14 Nov '13

14 Nov '13

Dear Sir/Madam, I am a research scholar from Cachar Cancer Hospital, India. I tried to download Chimera V-1.8.1. but could not download. It is showing insufficient permission. Kindly tell me how to set up this problem. Thanking you n anticipation -- Yours sincerely, *Dr. Akalesh Kumar Verma* *Post-Doc Research Associate* *Department of Molecular Oncology* *Cachar Cancer Hospital & Research Centre* *Mobile : +91-8471956679* *____________* *Personal Disclaimer:--* *Any information contained in this e-mail and/or any attachments is confidential and only intended for reception and use by the specified person. If you are not the intended recipient, please return the email to the sender and delete it afterwards. In this case any copying, forwarding, printing, disclosure and use is strictly prohibited.* *_____________________________*

2 1