RE: [PyMOL] creating new colors
Craig, To color residue 115 with a custom RGB triple... set_color smith,[0.2,0.5,0.9] color smith,115/ Cheers, Warren -- mailto:war...@delanoscientific.com Warren L. DeLano, Ph.D. Principal DeLano Scientific LLC Voice (650)-346-1154 Fax (650)-593-4020 -Original Message- From: pymol-users-ad...@lists.sourceforge.net [mailto:pymol-users-ad...@lists.sourceforge.net] On Behalf Of Craig Smith Sent: Tuesday, April 15, 2003 2:00 PM To: pymol-users@lists.sourceforge.net Subject: [PyMOL] creating new colors Hey All, Is there a way to color a residue by defining its rgb? Dr. Craig L. Smith Postdoctoral Fellow Dept. of Molecular Microbiology Washington University School of Medicine voice: (314) 362-7042 fax: (314) 362-1232
[PyMOL] creating new colors
Hey All, Is there a way to color a residue by defining its rgb? Dr. Craig L. Smith Postdoctoral Fellow Dept. of Molecular Microbiology Washington University School of Medicine voice: (314) 362-7042 fax: (314) 362-1232
Re: [PyMOL] POVRay output
* Armand Tepper [2003-04-15 04:09] wrote: > Dear all, > > 1) In a future version of Pymol, would it be possible > to parametrize the POVray output such that all > textures, finishes etc. are declared once as variables > (e.g. something like #declare carbon_texture = > texture) ? Now the textures are defined for every > primitive (atoms, bonds, triangles) individually, > making changing image appearance a heavy search and > replace job. I'd like to second this. It would make editing easier, although I have found it possible to do with vim as long as I pick easily distinquishable colours for the different parts of the image. > 2) when the Pymol built-in image rendering is used, > the slab/clipping of the current view is used for the > rendering. Instead, the POVray output includes the > whole object regardless of the part that is clipped in > the Pymol view. Are there any workarounds for this? I'm not sure that I agree with this, but then when I want to use POVray I'm not simply wanting to render what I can see in the PyMOL view, since I find the PyMOL rendering sufficient for most "normal" images. But this is simply my opinion. :) Cheers, Robert -- Robert L. Campbell, Ph.D. Senior Research Associatephone: 613-533-6821 Dept. of Biochemistry, Queen's University, fax: 613-633-2497 Kingston, ON K7L 3N6 Canada http://adelie.biochem.queensu.ca/~rlc PGP Fingerprint: 9B49 3D3F A489 05DC B35C 8E33 F238 A8F5 F635 C0E2
[PyMOL] POVRay output
Dear all, I am a new user of both pymol and this email list so I apologize when the items below already have been discussed earlier. I like the graphic output of the program very much! I am mainly interested in generating POV output files from Pymol instead of using the built-in renderer. Regarding this, I have two comments: 1) In a future version of Pymol, would it be possible to parametrize the POVray output such that all textures, finishes etc. are declared once as variables (e.g. something like #declare carbon_texture = texture) ? Now the textures are defined for every primitive (atoms, bonds, triangles) individually, making changing image appearance a heavy search and replace job. 2) when the Pymol built-in image rendering is used, the slab/clipping of the current view is used for the rendering. Instead, the POVray output includes the whole object regardless of the part that is clipped in the Pymol view. Are there any workarounds for this? Thanks for the help, Armand __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com