[Paraview] Input text

[Gerald Labedz]

Kent
  Show stopper is right. I just spent a bunch of time on the .vtk legacy to
find out that there are several fields required, not just a list of points.
Weird thing, in the vtk book, the set of fields shown in the description of
the UNSTRUCTURED_GRID definition is different from the example below it.
It's also weird because when it shows the data are float, well, those look
like integers to me. I get the ugly feeling I have to read a lot of this
book just to interpret the examples. Ugh, not too helpful.
  Thanks for the link, I'll check it out.
Gerry
Motorola


On 3/23/07 10:20 AM, "Kent Eschenberg" <eschenbe at psc.edu> wrote:

> Gerald,
> 
> Gerald Labedz wrote:
>> I THOUGHT I was following the format in the vtk book
>> (brand new, about v 5.0). Seems simple enough, but
>> that, too, crashed. ... it would be great if somebody has
>> a simple n-tuple ASCII file that WORKS that I could
>> examine.
> 
> My ParaView tutorial is temporarily unavailable but I've
> attached a page from it where I show a very simple file in
> the VTK legacy format. It plus the document on VTK formats
> 
>     http://public.kitware.com/VTK/pdf/file-formats.pdf
> 
> should get you started. If you create a program that
> converts csv files to a VTK format please consider letting
> us all have a copy!
> 
> My example defines only 1-tuple scalars, for points and
> cells. Change the last number on the "SCALARS" lines from 1
> to N for n-tuple scalars. If you have 3-tuple scalars, and
> want it treated a vector, you should probably switch to the
> "VECTORS" keyword. You could leave out either the
> "POINT_DATA" section and/or the "CELL_DATA" section.
> 
> I have worked with enough of our users to know that what
> seems obvious to me can be a show stopper. Please ask!
> 
> Kent
> Pittsburgh Supercomputing Center