I don't think it's a "bug"; it's just the way it works:
To the best of my knowledge, and from a bit of
experimentation:
If you set validity to 0, then ShowBoundary constructs
a boundary of the entire data set, *BUT* then also passes
through the invalid/valid information to the resulting output
field (just as most modules do with invalidity information)
If you set validity to 1, then you get little patches of boundaries
around valid regions.
Thus to get the result you want, you can do one of two things:
you can either Remove("invalid positions" "invalid connections")
before ShowBoundary, or you can do it after (assuming in
the second case that you set validity to 0)
_________________________________
Donna L. Gresh
Visual Analysis Group
IBM T.J. Watson Research Center
(914) 784-5049
[EMAIL PROTECTED]
"Sharon Cady" <[EMAIL PROTECTED]>@watson.ibm.com on 11/19/99
12:33:44 PM
Please respond to [email protected]
Sent by: [EMAIL PROTECTED]
To: [email protected]
cc:
Subject: [opendx-users] ShowBoundary validity bug ?
I'm using ShowBoundary to render the bounding region of scattered satellite
scanner data with longitude/latitude positions. The data form a "swath" in
2-d
space. Sometimes the data will have invalid positions. I have validity=0
set
to bound "all data", but the resulting boundary is not contiguous. The
boundary
is apparently rendered in 4 segments, but only 2 of them are visible (the
mostly vertical "sides" of the swath). If I eliminate all of the invalid
positions manually (set the invalid positions array = 0B) prior to
ShowBoundary, then the boundary will be rendered contiguously, and there is
no
problem.
Has anyone seen anything occur similar to this ? For me, this happens both
in
Open DX and the version 3.1.4 that I have access to.
