On Wednesday, Jun 4, 2003, at 15:30 America/New_York, Veera Pollard wrote:
I'm trying to visualize some velocity(vector) data and getting wierd
pictures.
First of all, do we need to use the compute module to make a vector?
Only if the data is not already vector after upstream operations, like Import. Use Print("rd") to determine this.
Also, is it important to viz this on top of another isosurface as in theNo. You could have a vector based at each point in a 3D grid of positions, if you wanted. The example shows a clever ability to show only an 'arbitrary' subset of an otherwise very crowded grid of vectors.
tutorial? When do we need map? Map does not seem to work for me,
not sure why not...
I've tried autoglyph and i often get out of memory error messages...Set glyph type to "0" or needle for vector. You are probably dying rendering too many polygons, as each glyph has many polygons.
I'm thinking AutoGlyph3DVector.net in the tutorial is most akin to mySounds OK to me. Check to see after Import that you have a "positions" component which is float 3-vector and a "data" component which is (I assume) also float 3-vector (depends on your data). If you have the same number of data vectors as positions and the attribute "dep" "positions" is set on the "data" component, you should be good to go.
problem but this doesn't seem to work for me....
Basically I have vector data in a series called "total velocity" (vtot).
The positions
it is taken on are called "vgrid3" which are the 3D velocity grid
positions...
Remember that a series file attempts to open all members, unless you constrain the Import with its start and end parameters. So you could be very nearly out of memory after Import, even before rendering begins. The Message window option to "Show Memory Use" which can be invoked whenever you like, will help determine this.
_______________________________
Chris Pelkie
Scientific Visualization Producer
622 Rhodes Hall, Cornell Theory Center
Ithaca, NY 14853
