> So, it seems that the two of you have been helpful in remedying my
> ignorance. Thanks.
Glad to help. I'd also suggested grabbing the free ParaVIew Guide PDF
to get a handle of some of the pipeline concepts in ParaView.
http://www.paraview.org/paraview-guide/
Utkarsh
__
I was able to properly load the file you posted and the values posted by
Scott. I am not certain why it did not work before, perhaps I did not have
the "Merge Consecutive Delimiters" selected, but thought for sure I had
toggled it.
It also seems that after playing around with the "Calculator" I am
I think there may be two spaces, but whitespace is whitespace. Not even
Excel gets confused by the spacing. I've tried the sample case above, but
PV still did not recognize the delimit.
I have 4 columns:
x-coord y-coord u-velocity v-velocity
The x, y, z, scalar doesn't achieve what I want.
I ne
Just guessing here – you may have more spaces in the file than you think? Or,
PV may be looking for a space, and you have two? That’s the reason I recommend
commas.
Try this little toy problem that I use all the time:
x-coord y-coord z-coord scalar
0 0 0 0
1 0 0 1
0 1 0 2
1 1 0 2
-0.5 -0.5 1
Alan,
I have tried the " ", and it didn't have the effect I had hoped for.
Yes, table to point makes points at the coordinates. I have vectors at
certain pixel coordinates - processed PIV images. I have (x,y) location
with a vector of velocity components (Ux, Uy) at those coordinates. The
table t
Zach,
Please keep this reply on list, so we all get to learn (and I get to be
corrected when I mess up).
Try changing the Field Delimiter Characters string to be “ “
Table to point makes points (or dots). I don’t understand your comment about
vectors.
Alan
From: Zach [mailto:zach...@gmail.c
I’m not sure if white space works – but comma’s do work.
For instance, X, Y, Z, Var does work.
Then, use the Table to Point filter.
There is more information here: http://www.paraview.org/Wiki/Data_formats
Does that answer the question?
Alan
From: ParaView [mailto:paraview-boun...@paraview.o
