Say I have 2 fields, "temperature" and "humidity" (same positions component).
Each field initially has its own set of invalid positions, since it
independently contains out of range values which have been tagged as such by
Include. By saying that I only want to plot points that are valid in x and y,
I mean that I want to ignore (not plot) instances in which either temp or
humidity has been tagged invalid.
To make the plot, I create a field with humidity as positions and temp as data
(several ways this can be done, either start from the begining or Replace data
or positions components in one or the other of the original fields), and then
send to Plot. If careful at this step, I can preserve the invalid positions of
either temp or humidity, but not both. So this is why I think that I have to
tinker with the invalid positions array of the new field.
I suppose that I could do the Inlude's all over again on the new field (to now
account for invalids in positions (humidity) and invalids in data (temp) ), but
since I have the info already (two invalid positions arrays), why not use it.
Yes, I would appreciate an easier way altogether if I am making this too
complicated.
On Jan 16, 2:41pm, David Thompson wrote:
> Subject: Re: [opendx-users] invalid positions array type
> When sending something to plot, you should have a set of scalar
> positions with data values that will become the "y". So how do you
> know if something is valid in "y"? I think there might be an easier
> solution that playing with the "invalid positions" arrays, but I need
> to know more about what you are feeding into Plot.
>
> David
>
> >Anybody know of a way to force the invalid positions array which is
> >obtained by
> >Extract to always be given as bytes rather than (which is sometimes the
case)
> >integer ? I am doing x/y plots of two fields, and want to plot only
> >points that
> >are valid in both x and y. I believe that the inherent nature of the Plot
> >module is to plot points which are valid in x ("positions"), with no regard
to
> >validity in y ("data").
> >
> >So, I am tinkering with invalid positions arrays by extracting invalid
> >positions of each of 2 fields and then (assuming they are both type
> >byte) doing
> >a logical or operation to change some "0"s to "1"s. I then Replace the
result
> >as invalid positions into the field which is then plotted.
> >
> >Obviously, this will not work if the arrays are of different types and of
> >different lengths. Also, the form of the type int array that is returned
(the
> >actual positions of the invalid points, or something like that) seems to be
of
> >little use in this case. I'm aware that dx chooses which data type to return
> >depending on the number of invalids, because of memory issues. But this can
> >sure make some things unduly painful, no ?
> >
> >Someone mentioned that it took 10 hrs for her message to be posted. Although
I
> >haven't really timed it, the last few messages that I've posted (a few weeks
> >ago) seemed to take more like 24 hrs to register. Why so slow ? I don't
recall
> >this being an issue in the past.
>
> --
> .............................................................................
> David L. Thompson The University of Montana
> mailto:[EMAIL PROTECTED] Computer Science Department
> http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
> Work Phone : (406)257-8530
>-- End of excerpt from David Thompson
