Noel O'Boyle wrote:
>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.
>
>
>
print {model=1.1}.property_d.all
otherwise you just get the average value.
> From: Bob Hanson <[EMAIL PROTECTED]>
> Subject: Re: [Jmol-users] General queries about slabs, arrays and
> mapping
> To: jmol-users@lists.sourceforge.net
> 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
Dear all,
I've been having a lot of success with Jmol now that I've gotten over
the inital activation energy. Before I write a blog post recording
what I've done and posting some pictures, I thought I might ask a
raise a few questions about random things that I came up against.
(1) Slabs appear t
4 matches
Mail list logo
