On Mon, 23 Jul 2001, Chris Pelkie wrote:
Thanks for the quick reply.
I've seen weirdness in this op before also. Do an experiment and
Remove('invalid positions') from IH before Replace and see if that
helps. I presume you're using the byte form of invalids (byte values
of 00 and 01) rather than the indexed (ref) form.
yup.
I then tried displaying the data without draping it, the points where
excluded as expected, so it's seems the problem is with drape (or rather
strange). I resolved the problem by using compute on the colour component,
which did the trick.
BTW, it's quite annoying when I close a DX program my windowmanager
crashes (WindowMaker 0.65.0 on XFree86 4.1.0 running on Linux).
Cheers
magi
You could also just Compute the heights; I bet you know how so I
won't tell you unless you ask. As a mapmaker, you'd probably be
happier with a Compute that you could scale X, Y, Z to real world
coords instead of relying on the sometimes obtuse Rubbersheet
scaling. I would expect then the invalids would behave.
If not, one more trick to try:
Mark("invalid positions")
Include (range 0 to 0.5, set cull to true, set pointwise to true)
Unmark
This should really eradicate the little buggers. However, it will
make your regular (therefore compact and more memory efficient) grid
irregular which bloats up the memory requirement.
Frankly, the Colormap trick is fine. Internally it's creating
invalids (presumably cleaning house while doing so since it works).
It's a bit trickier if the range to invalidate is not outside the
range to include.
Chris Pelkie
Vice President/Scientific Visualization Producer
Conceptual Reality Presentations, Inc.
30 West Meadow Drive
Ithaca, NY 14850
[EMAIL PROTECTED]
