Hi Bob,

I see. Actually I forgot to use the MAP keyword (actually it seems to be implied when I use property_xxx).

and I can also confirm that 

ISOSURFACE my_iso1 VDW COLORSCHEME bwr COLOR RANGE -1.0 1.0 property_xxx

works (even without "MAP") but

ISOSURFACE my_iso1 VDW property_xxx COLORSCHEME bwr COLOR RANGE -1.0 1.0

ignores the COLOR RANGE.

The documentation misled me in that regard as the MAP options are explained before the COLOR options.
And as I am writing this Bob moved the COLOR part a bit higher. ;-) Great!


On Thu, May 24, 2012 at 4:29 PM, Robert Hanson <hansonr@stolaf.edu> wrote:
Well, I see what the problem is. First, the original design was for the color options to precede the mapping object.

isosurface <options1> <surface1> MAP <options2> <surface2> <display options>

I realize that's very unclear from the documentation. The command should be:

isosurface vdw map color range -1.0 1.0 mep

That said, there is a rather unexpected twist. If the command includes the colorScheme option, this ordering does not matter.

isosurface vdw map mep color range -1.0 1.0 colorScheme "rgb"

happens to work. That's unfortunate, of course, and I'm not sure I really want to document that. 


Robert M. Hanson
Professor of Chemistry
St. Olaf College
1520 St. Olaf Ave.
Northfield, MN 55057
phone: 507-786-3107

If nature does not answer first what we want,
it is better to take what answer we get.

-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900

Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Jmol-users mailing list