June 2014 - Chimera-users - RBVI Mailing Lists

Re: [Chimera-users] normalizing attributes through point mutant models
by Elaine Meng 05 Jun '14

05 Jun '14

Hello Ruben, If you were asking how to get consistent coloring for the atomic "overlap" attribute for the different complexes: Just make sure to use the same color for the same overlap value. For example, if you color the first complex with yellow for 0.5 overlap and red for 1.0 overlap, make sure to color the other complexes with yellow for 0.5 overlap and red for 1.0 overlap. You can control which color goes with which value in the Render by Attribute tool, as mentioned in the earlier reply: > in the Render by Attribute tool: you can move the colored bars on the histogram directly with the mouse or by typing in values, change the colors of the bars, etc. as explained here: > <http://www.rbvi.ucsf.edu/chimera/docs/ContributedSoftware/render/render.htm…> ... or if you use the "rangecolor" command, you specify which color goes with which value directly in the command: <http://www.rbvi.ucsf.edu/chimera/docs/UsersGuide/midas/rangecolor.html> Otherwise, I don't know what you are asking. If I haven't already answered your question, you would need to say more about which Chimera tool you are using to study these interfaces, what values you are trying to display (number of clashes? atomic overlap values?), how you are displaying them (with color? with lines?) and exactly what you mean by weighting or normalizing (are you trying to divide the values by some other values?). Since I already described all the related features I can think of, however, there probably isn't a Chimera tool that does exactly what you wanted. Elaine ----- Elaine C. Meng, Ph.D. UCSF Computer Graphics Lab (Chimera team) and Babbitt Lab Department of Pharmaceutical Chemistry University of California, San Francisco

1 0

warning: Ignored bad PDB record found on line
by Xiao-Bo Li 05 Jun '14

05 Jun '14

Hello, This morning I kept getting this error "warning: Ignored bad PDB record found on line nnn" whenever I use the python script to try to open a pdb file. The python script I'm using is the usual "chimera.openModels.open(pdbID, type='PDB')[0]". This function call is how I've always been using Chimera, and this morning is the first time I'm getting this issue. I dont see a problem with my internet connection, and I can open the PDB file using File->Fetch by ID, so it doesn't seem like the pdb file has any problems. Only the python script gives me problems. Is anyone else experiencing this problem? Best, XBL

2 2

normalizing attributes through point mutant models
by Rubén Marrero Diaz De Villegas 05 Jun '14

05 Jun '14

Hello I´m working with one antigen/antibody complexes and different point mutations at the interface. I can calculate and draw at the surface attributes like atomic clashes "overlap", but what I don´t know, is how to normalize the calculation output for 2 complexes, neither render such "normalized" attributes in the models. I have tried at Render attribute tool, the option "create corresponding color key", introducing specific clashes boundaries and their coloring values but there is no "apply" button, such the changes doesn't goes to the model. Any help or tip? Thanks in advance Ruben

2 3

Setting the vertex density in a script
by Hurt, Darrell (NIH/NIAID) [E] 05 Jun '14

05 Jun '14

Hi Chimera friends, To save memory and reduce exported geometry sizes, I want to use a script to automatically scale the vertex density of generated molecular surfaces by the size of the molecule. Is there a way to grab the size (number of atoms?) of the loaded molecule(s) and use that with some simple math to set the vertex density value? I know this will reduce surface fidelity, but for very large molecules, the mesh size becomes unwieldy. On a separate, but related note, when loading a volumetric file like electron microscopy data, the "step" size in the Volume Viewer automatically adjusts (1, 2, 4, 8, 16) to optimize visual performance and memory. I'm using a script to import volumetric data and then "Export Scene…". For that export, I want to drop down the step to the next lowest step to get a smoother mesh. I can just set the step value to the minimum with something like "volume #0 step 1 limitVoxelCount false", but this risks maxing out the memory and crashing for very large data sets. Is there a way to use a script to get the current step value and then lower by one step for my export? Thanks, Darrell -- Darrell Hurt, Ph.D. Section Head, Computational Biology Bioinformatics and Computational Biosciences Branch (BCBB) OCICB/OSMO/OD/NIAID/NIH 31 Center Drive, Room 3B62B, MSC 2135 Bethesda, MD 20892-2135 Office: 301-402-0095 Mobile: 301-758-3559 Web: BCBB Home Page<http://www.niaid.nih.gov/about/organization/odoffices/omo/ocicb/Pages/bcbb.…> Twitter: @niaidbioit<https://twitter.com/niaidbioit> Disclaimer: The information in this e-mail and any of its attachments is confidential and may contain sensitive information. It should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage devices. National Institute of Allergy and Infectious Diseases shall not accept liability for any statements made that are sender's own and not expressly made on behalf of the NIAID by one of its representatives.

2 5

Re: [Chimera-users] Missing cavities
by Eric Pettersen 05 Jun '14

05 Jun '14

On Jun 5, 2014, at 7:38 AM, sapeptides <sapeptides(a)gmail.com> wrote: > Hi Erik, > > I'm writing because I have noticed that in the new versions of chimera when I create a surface and then try to "cut" it (with the side view tool) to see inside the model I obtain this weird picture (attached), whereas in the old versions (how old I do not remember but I created a stunning images of various active sites) it was possible to check all the cavities inside the molecular structures. > I was wondering if you could suggest how to visualize pockets and clefts when the vdw or solvent accessible surface is present. > > Thanks a lot! > Susanna Hi Susanna, It's best to send questions like this to the chimera-users list rather than me directly so that others can benefit from the answer and since I may not actually be the best person to answer the question. For instance, I have no good ideas about showing cavities effectively with VDW or solvent-accessible surfaces and hope someone else can chime in there. As for the lack of cavities in your image, did Chimera issue a warning when it computed the surface saying that "[c]alculation of some surface components failed" and that "[a] single component of the surface was calculated"? If so, that means that calculation of interior cavities failed and Chimera is showing the exterior surface only (which the error message does say if you read it in its entirety). That would produce the lack of interior cavities you observed. If you didn't get such a message, can you supply the PDB ID for this structure (or PDB file) so I can investigate? Thanks! --Eric Eric Pettersen UCSF Computer Graphics Lab http://www.cgl.ucsf.edu

3 2

"ligand" category for selection
by Hurt, Darrell (NIH/NIAID) [E] 05 Jun '14

05 Jun '14

Hi Chimera friends, I'm trying to use the attached MOL file (dopamine) in Chimera and I want to run a Python script on it. My script does some things to the molecule using selection categories. I'm trying to select this molecule as "ligand", but I get a "No atoms specified" error. Alternatively, is there a way in Python to ignore the error if I get it and keep processing the rest of the script? Thanks, Darrell -- Darrell Hurt, Ph.D. Section Head, Computational Biology Bioinformatics and Computational Biosciences Branch (BCBB) OCICB/OSMO/OD/NIAID/NIH 31 Center Drive, Room 3B62B, MSC 2135 Bethesda, MD 20892-2135 Office: 301-402-0095 Mobile: 301-758-3559 Web: BCBB Home Page<http://www.niaid.nih.gov/about/organization/odoffices/omo/ocicb/Pages/bcbb.…> Twitter: @niaidbioit<https://twitter.com/niaidbioit> Disclaimer: The information in this e-mail and any of its attachments is confidential and may contain sensitive information. It should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage devices. National Institute of Allergy and Infectious Diseases shall not accept liability for any statements made that are sender's own and not expressly made on behalf of the NIAID by one of its representatives.

2 2

Chimera display problem
by sea 03 Jun '14

03 Jun '14

Hi, I recently changed graphics card. This caused a problem to display image properly in Chimera (see attached screenshot). My new graphics card is MSI RADEON R7 240, chimera version 1.9. Does anyone encounter similar problem, or know how to fix it? Best regards Pu Qian

2 1

Asking Help: Academic User
by Robin Parmar 03 Jun '14

03 Jun '14

Hello, Warm Greetings! Thank you for Allowing me to use Chimera through academic license. Yesterday(June 2nd) I was prompted to update Chimera to 1.9 version. I accepted and installed it successfully on my system (windows7pro). Before that I had removed Chimera 1.8.8. The problem I face is, I can not open certain .pdb/.pdbqt fies saved in my comuter. such files even do not exhibit chimera logo which earlier version did. Even with "choose default program" system can not open these files insted other program (like spdbv) open them. I have not made any change in my system after installing new version. Can I reinstall earlier vrsion(1.8)? Kindly suggest me what best I should do to avail service (Academic Research) of chimera again. Regards. -Robin

2 1

Re: [Chimera-users] Chimera-users Digest, Vol 134, Issue 4
by Boaz Shaanan 03 Jun '14

03 Jun '14

Thanks a lot Tom, This is wonderful. I'll try it as soon as it's on the site. Boaz Boaz Shaanan, Ph.D. Dept. of Life Sciences Ben-Gurion University of the Negev Beer-Sheva 84105 Israel E-mail: bshaanan(a)bgu.ac.il Phone: 972-8-647-2220 Skype: boaz.shaanan Fax: 972-8-647-2992 or 972-8-646-1710 Message: 7 Date: Tue, 3 Jun 2014 11:52:46 -0700 From: Tom Goddard <goddard(a)sonic.net> To: Boaz Shaanan <bshaanan(a)bgu.ac.il>, "Hurt, Darrell (NIH/NIAID) [E]" <darrellh(a)niaid.nih.gov> Cc: "chimera-users(a)cgl.ucsf.edu" <chimera-users(a)cgl.ucsf.edu> Subject: Re: [Chimera-users] About direct fetching biological assemblies into Chimera Message-ID: <2FF03268-945D-4B45-B2BE-1A7B17370069(a)sonic.net> Content-Type: text/plain; charset=windows-1252 Hi Darrell, Boaz, I made a few improvement to the fetching of PDB biological unit files that will be in tonight?s daily build. 1) Made fetching biounit give each assembly a separate top level model id number and separate color. Before all the assemblies were grouped together in Model Panel, and now each assembly is on a separate line in Model Panel. 2) Renamed biounit file type and prefix from pdbbuID to biounitID. So use Chimera command ?open biounitID:1hho?. 3) Allowed specifing a specific biounit by number using pdb id plus "." followed by number, eg. 3fad.2. This works in the Fetch by Id dialog and on the command-line. Also to fetch a few different biounits you can use 3xyz.1.3.8 with each . specifying another assembly number. Used "." instead of comma since commas separate multiple identifiers in the fetch dialog. Tom On Jun 3, 2014, at 5:52 AM, Boaz Shaanan <bshaanan(a)bgu.ac.il> wrote: > Hi Tom, > > This is a nice addition but can you ALSO give the option of fetching just one of the biological assemblies? It is my experience that biological assemblies for a particular pdb entry consist of one correct assembly, in the sense of biological function corresponding to the description given by the depositors and other assemblies. I usually flip between the assemblies on the RCSB website before deciding which one to fetch. With your new addition this of course can all be done now in Chimera but if possible, I'd rather not waste time and disk space with meaningless assemblies. What do you think? > > Cheers, > > Boaz ------------------------------ _______________________________________________ Chimera-users mailing list Chimera-users(a)cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users End of Chimera-users Digest, Vol 134, Issue 4 *********************************************

1 0

<< creating MOL2 files with different SET records >>
by Hatuey Hack 03 Jun '14

03 Jun '14

Hello, I will like to know if it is possible with Chimera to create MOL2 files that include other MOL2 records like these: @<TRIPOS>SET ATOM$BY_TYPE STATIC ATOMS COLORGROUP SYSTEM 5 1 2 3 4 5 LINK_HS STATIC ATOMS <user> **** 4 2 3 4 5 @<TRIPOS>NORMAL @<TRIPOS>FF_PBC FORCE_FIELD_SETUP_FEATURE Force Field Setup information v1.0 0 0.000000 0.000000 0.000000 0.000000 0.000000 0.000000 NONE 2 0 0 0 0 0 0 0 0 0 0 0 0 Best regards, Hatuey

2 1