> From: Bob Hanson <[EMAIL PROTECTED]>
> Subject: Re: [Jmol-users] General queries about slabs, arrays and
>         mapping
> To: [email protected]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Noel,
>
> slab:
>
> Jmol 11.3.55 cleans this up. There was a bug in how slab set operated;
> it is immensely cleaner now, and as a bonus we have
>
> _slabPlane
> _depthPlane
>
> defined. So at any time -- whether slab is on or not -- you can do
> something like this:
>
>   isosurface plane @{_slabplane}
>
> or
>
>   color (within(0.2, @{_slabPlane}) yellow

That's excellent - I await its pre-release.

> >(1) Slabs appear to cut through all models. It would be great if a
> >slab could just be applied to one model or the selected models. (Use
> >case: I want to see the whole ligand in the active site, but I need to
> >cut back the isosurface.)
> >
> >
> >
> they do have to cut through all models. But note that now you can use
> the slab plane to select a set of atoms, and you can include a model in
> that:
>
> slab 60;
> select within(-999, @{_slabPlane}) and model=2.1
> display selected

Understood. I will be using this.

> >(4) Loading property data using {*}.property_d = load("myfile.txt")
> >worked fine in the applet. However, I couldn't get it to work in the
> >application, where I wanted to load a file from a different folder.
> >Surely the applet isn't restricted by security to particular folders?
> >Also, I wasn't sure how to test whether the data was actually loaded
> >correctly. "print property_d" doesn't appear to do anything useful
> >even when property_d contains information.
>
> These all worked for me:
>
> print load("t.spt")
> print load("/temp/writevar.txt")
> print load("e:/temp/readme.txt")
> print load("../../log.txt")
>
> That uses the same method as above, so it should be working. Use print
> to test.
>
> (Make sure you you use forward slash, /, even if you are on a PC.)

Ok - must be my mistake. I think the problem was that I was trying to
print {model=1.1}.property_d but nothing was happening, instead of
directly printing the load command as you suggest.

> >(6) I found that mapping property data onto an isosurface worked fine
> >except that you need to have property data for every atom in every
> >model up to the model for which you are actually drawing the
> >isosurface. I think this is undocumented, and doesn't really seem to
> >be a useful feature. (The documentation just says that property data
> >is required for every atom in the model, which seems more reasonable.)
> >
> >
> >
> Not if you load the data a different way. For example, you could use
>
> {model=2.1}.property_mydata = array(2,3,4,5,6,6,7);

Right. I didn't really understand what the {xxxx} was about, and so
just blindly used the {*} in the original email.

> >(7) jmolScriptWait is a good idea. But it'd be great to have something
> >similar for jmolInitialize, either a Wait version, or a callback to a
> >javascript function (e.g. onload="myfunction"). At the moment, I stuff
> >everything into the call to jmolInitialize, but it's not really the
> >best way to do it, and if I want to do some javascript to process some
> >feature of the model after it has been loaded, it's not very
> >convenient.
> >
> >
> >
> nothing should be in jmolInitialize -- you mean jmolApplet ? That is
> really the way to go, because then Jmol runs the script immediately
> after file loading.
> Still, you can use:
>
> jmolSetCallback("loadStructCallback", "myfunc")

That sounds what I'm looking for. I'll check it out.

> You're doing great! A pro already!
I appreciate the help. The first applet is always the most difficult...

Noel

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to