Re: Displaying 3-D vector fields [message #32827 is a reply to message #32726] |
Thu, 14 November 2002 09:03   |
jim.blackwell
Messages: 11 Registered: November 2002
|
Junior Member |
|
|
"Rick Towler" <rtowler@u.washington.edu> wrote in message news:<aqu1qc$28se$1@nntp6.u.washington.edu>...
> "Jim" <jim.blackwell@gsfc.nasa.gov> wrote
>>
>> forgive me for being such a doofus, but shouldn't the mag and loc
>> arrays be 3-D ?
>
> You tell me... Well I guess you just did. The 3rd dimension is time, I
> presume. That doesn't change anything except how you subscript your data.
>
> Say you have 100 samples from 100 data points. Your array will be in a form
> similar to [point,sample,values] or [100,100,3] where the last dimension is
> your x,y,z or u,v,w depending on if we're talking about your location array
> or magnitude array. Is that correct?
>
> In my example, I assumed 1 sample from 100 points [100,1,3] which I
> simplified to [100,3]. You can change the subscripts in the example to work
> with your data set. [n,*] would become something like [n,0,*] for your
> first sample, [n,1,*] for your second and so on.
>
>
>
>> Would it be as simple as just adding this code to the
>> existing code set for creating the vector object ?
>
> I don't understand what you are asking. But if you are asking if you should
> add this code to the vector object. No. Stick with my example.
>
> -Rick
Rick,
Okay I get it now Thank God ! I seem to be running into a memory
problem in trying to display 18K vectors at a time though ? I don't
get any indication of this, but it bombs after some number less than
that number of vectors
Jim
|
|
|