Re: [PyMOL] RE: povray image mapping and default pigments

[Tsjerk W. <ts...@gm...>]

Hi,

Actually, one of the first of these images I made was of conotoxin floating
above a see. Will that do? I'd still have to add the sunset though ;) O, an=
d
the checkered beach...

In regards the problem of Seth, it's good you've solved it. It is possible
though to remove all statements about textures from a mesh2 object. You hav=
e
to remove both the texture_list as well as the references to the textures.
If you don't know what I'm talking about, you can check out the povray
manual on mesh2. Besides, you may be better off using statements like

union { #include "moleculedef.inc" pigment {image_map{ " mypicturehere.gif"
}} }

rather than changing the #default for that. Especially handy if you can fin=
d
a snowboarder object you want to merge with your kinase piste...

By the way, I may try to write a script to process the mesh2 file from Pymo=
l
to strip out texture statements (and add them as #declares) if I can find
some time. Also, it would be so nice to have a tidied up mesh2 file, rather
than an endless set of triangles. mesh2 can be so much better (smaller, mor=
e
efficient, easier to handle).

Cheers,

Tsjerk

On 4/19/06, Thomas Stout <ts...@ex...> wrote:
>
>
>
> I'm glad you solved your problem, but more importantly when are we going
> to get to see this picture of an easter bunny on some wood-textured
> rendition of a half-submerged albumin glowing softly in the warm lights o=
f a
> double sunset over an infinite lake lapping at the shores of a checkered
> beach???
>
> :)
>
> -Tom
>
>
> -----Original Message-----
> From: pym...@li... on behalf of Seth Harris
> Sent: Tue 4/18/2006 2:45 PM
> To: pym...@li...
> Subject: [PyMOL] RE: povray image mapping and default pigments
>
> To answer my own question...instead of entirely taking out the
> pigment{blah
> blah blah} statements from the texture_lists in the povray input as used
> to
> work, I found that in this case replacing them with "pigment {}"
> statements
> was still a permissible syntax and also allowed a #default pigment
> declaration in the header file to override the molecular scene
> descriptions.
>
> If you have no idea what I'm talking about, it's probably for the best.
>
> Funny how often just describing your problem to someone else allows you t=
o
> lay it out logically enough to lead you to a solution...thanks for
> listening!
>
> -Seth
>
> ---------- Forwarded message ----------
> From: Seth Harris <se...@gm...>
> Date: Apr 18, 2006 2:18 PM
> Subject: povray image mapping and default pigments
> To: pym...@li...
>
>
>  This is for the povray gurus out there...
>
> Occasionally I muck around with the time-consuming practice of trying to
> map
> pictures onto molecular surfaces with povray.
>
> I had this working to some extent, but something has changed (I think wit=
h
> the povray file format produced by pymol & make_pov where now there are
> fancy texture_list texture and pigment statements, rather than simple
> "pigment" ones.)
>
> In the past, I set it up so that the povray file has a header (cameras,
> lights, etc.) separate from the molecular scene description. Then I would
> usually edit the header to apply some #default texture or pigment to use
> the
> povray parlance. So the approach I used to use was to strip out all the
> pigment {} statements from the molecular scene descriptor povray input
> with
> a perl script, and then use the #default pigment {image_map{ "
> mypicturehere.gif" }} syntax in the header to map the image on to the
> surface...the practical uses of having a picture of someone, say,
> snowboarding down a mountain mapped onto the surface of some kinase are
> just
> endless. But that aside, the problem now is that these newer texture_list
> statements aren't so amenable to this global pigment removal thing, and I
> haven't quite figured out how best to get around this. (Couldn't remove
> them
> entirely and putting in the image_map pigment thing didn't seem to work,
> although maybe I just didn't get the right combination of open and closed
> brackets {?}}})
>
> Anyone have any experiences along these lines? As near as I can tell,
> there
> was some switch in smooth triangle definitions with Povray 3.5 which was
> capitalized on by some pymol 0.98 edition. Perhaps I have to go back to a=
n
> old archived version of pymol? Or, more sensibly, perhaps I should
> recognize
> that pictures of easter bunnies or whatever don't belong on some
> wood-textured rendition of a half-submerged albumin, glowing softly in th=
e
> warm light(s) of a double sunset over an infinite lake lapping at the
> shores
> of a checkered beach. But for some reason journal editors seem to enjoy
> this.
>
> Thanks,
>  Seth
>
>  This email (including any attachments) may contain material
> that is confidential and privileged and is for the sole use of
> the intended recipient. Any review, reliance or distribution by
> others or forwarding without express permission is strictly
> prohibited. If you are not the intended recipient, please
> contact the sender and delete all copies.
>
>
> Exelixis, Inc. reserves the right, to the extent and under
> circumstances permitted by applicable law, to retain, monitor
> and intercept e-mail messages to and from its systems.
>
>


--

Tsjerk A. Wassenaar, M.Sc.
Groningen Biomolecular Sciences and Biotechnology Institute (GBB)
Dept. of Biophysical Chemistry
University of Groningen
Nijenborgh 4
9747AG Groningen, The Netherlands
+31 50 363 4336