[Paraview] (Fwd) Re: Paraview Ensight Reader
pte at nexgo.de
pte at nexgo.de
Thu May 28 04:38:21 EDT 2009
Hello Zhanping,
thanks, it's working now!
The files I uploaded have been in Ensight6 case file format and actually the ens_checker said the files are valid when checking only one timestep. However, I have taken your hint and changed my script to ensight gold case format. Again ens_checker said the resulting files were ok, but Paraview still didn't load the data. I could not find the file Test.case so I started to compare my files with the elements.case in the VTKData/Data/EnSight/ directory. It turned out that I had a few leading blanks in front of some keywords (e.g. ' part' instead of 'part') and also the second comment line in the .geo-file was blank. After changing both issues, Paraview now runs perfectly fine.
Thanks again for your help!
Regards,
Peter
Hi Peter:
A sample EnSight Gold dataset involving ASCII-based geometry, 'scalar per
element', and 'vector per element' files may be found through
VTKData/Data/EnSight/TEST.case. This CASE file references some associated
files:
======
geometry: test.geo
scalar per element: test.pressure.0001
vector per element: test.velocity.0001
.....
======
You may update your CASE dataset based on this sample one.
-Zhanping
On Wed, May 27, 2009 at 12:30 AM, Zhanping Liu <zhanping.liu at kitware.com>wrote:
> Hi Peter:
>
> The format of your geometry files (e.g., example0001.geo) is invalid.
> Please go to pp.489 (the lower section), EnSight Manual v8.2 (
> http://vis.lbl.gov/NERSC/Software/ensight/docs82/UserManual.pdf) to find
> the valid format for ASCII-based geometry files. Simply put, the part index
> needs to be provided in a geometry file (e.g., example0001.geo), as
> indicated in pp.490 (the upper section), which is registered via
> vtkEnSightGoldReader::ReadGeometryFile(const char* fileName, int timeStep,
> vtkMultiBlockDataSet *output), specifically by
> vtkEnSightGoldReader::CreateUnstructuredGridOutput(int partId, charline[256],
> const char* name, vtkMultiBlockDataSet *compositeOutput). This part-index
> is later accessed in vtkEnSightGoldReader::ReadScalarsPerElement(const
> char* fileName, const char* description, int timeStep,
> vtkMultiBlockDataSet *compositeOutput, int numberOfComponents, intcomponent).
>
> Please note that the EnSight Manual also mandates that coordinates be
> listed one value per line in an ASCII-based geometry file (e.g.,
> example0001.geo) and it is also the case with scalar values (e.g.,
> example0001.temp, and example0001.o2). Also note that "part 1" is invalid
> and the two words need to be placed in two separate lines.
>
> Please double-check all of your files, make them compliant with valid
> EnSight file formats, and upload the resulting files to Mantis in case you
> still encounter any problems.
>
> Thanks.
>
> -Zhanping
>
> Zhanping Liu, PhD
> Kitware, Inc.
> 28 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-371-3971 x 138
> http://www.zhanpingliu.org
>
>
> On Sun, May 24, 2009 at 1:52 PM, Peter Eckert <pte at nexgo.de> wrote:
>
>> Hello Ricardo, hello Samuel,
>>
>> thanks for the ens_checkers!
>> Unfortunately, I could not get the one for linux to work, because of
>> a libstdc++.so.5 missing. The windows version gives indeed an error
>> for my ensight case file (see below), which I do not fully understand
>> however. Ens_checker is expecting 1395 entries in the variable file
>> example0002.temp. However, from the geometry file example0002.geo it
>> should expect 1719. Shouldn't it?
>> BTW, the checker gives the same error for my case file when I use
>> "per node" data and these are read in fine in Paraview?
>>
>> Anything else that I might have wrong in my case files?
>>
>> Thanks and best regards,
>>
>> Peter
>>
>>
>>
>> *****************************************************************
>> * EnSight Data Format Checker *
>> * =========================== *
>> * Currently, *
>> * 1. Must be run from directory in which casefile is located. *
>> * 2. Handles EnSight6 and EnSight Gold formats only. *
>> * 3. Does not process SOS casefiles. *
>> *****************************************************************
>> <Version: 1.206>
>>
>> <Enter casefile name (must be in directory containing it!) >
>> example.case
>>
>> Casefile to Process:
>> --------------------
>> example.case (Opened successfully)
>>
>> ---------------------
>> Major Sections Found:
>> ---------------------
>> Required FORMAT section (at line 1)
>> Required GEOMETRY section (at line 4)
>> Optional VARIABLE section (at line 8)
>> Optional TIME section (at line 16)
>>
>> ---------------
>> FORMAT Section:
>> ---------------
>> EnSight 6 Format (set at line 2)
>>
>> -------------
>> TIME section:
>> -------------
>> Info for timeset number: 1
>> ----------------------------
>> Time set: 1 (at line 17)
>> No description provided
>> Number of steps: 5 (at line 18)
>> Filename start number: 1 (at line 19)
>> Filename increment: 1 (at line 20)
>> Time values: (starting on line 21)
>> time values[1] = 379.03
>> time values[2] = 389.02
>> time values[3] = 399.05
>> time values[4] = 409.03
>> time values[5] = 415
>>
>> >-------------------<
>> > TIME section OKAY <
>> >-------------------<
>>
>> -----------------
>> GEOMETRY Section:
>> -----------------
>>
>> --------
>> Model filename is: example****.geo (at line 5)
>>
>> Changing connectivity geometry
>> Associated time set is: 1
>>
>> --------
>> Opened example0001.geo successfully
>>
>> File type is: ASCII
>> Description 1: Geometry file
>> Description 2:
>> node ids: assign
>> element ids: assign
>>
>> Global section:
>> Number of nodes: 1840
>> Coordinates for (1840) nodes found
>>
>> Part 1:
>> Description is: Cell data
>> Unstructured Part
>> Number of hexa8 elements in section is: 1395
>> Connectivities for (1395) hexa8 elements found
>>
>> --------
>> Opened example0002.geo successfully
>>
>> File type is: ASCII
>> Description 1: Geometry file
>> Description 2:
>> node ids: assign
>> element ids: assign
>>
>> Global section:
>> Number of nodes: 2220
>> Coordinates for (2220) nodes found
>>
>> Part 1:
>> Description is: Cell data
>> Unstructured Part
>> Number of hexa8 elements in section is: 1719
>> Connectivities for (1719) hexa8 elements found
>>
>> --------
>> Opened example0003.geo successfully
>>
>> File type is: ASCII
>> Description 1: Geometry file
>> Description 2:
>> node ids: assign
>> element ids: assign
>>
>> Global section:
>> Number of nodes: 2600
>> Coordinates for (2600) nodes found
>>
>> Part 1:
>> Description is: Cell data
>> Unstructured Part
>> Number of hexa8 elements in section is: 2043
>> Connectivities for (2043) hexa8 elements found
>>
>> --------
>> Opened example0004.geo successfully
>>
>> File type is: ASCII
>> Description 1: Geometry file
>> Description 2:
>> node ids: assign
>> element ids: assign
>>
>> Global section:
>> Number of nodes: 2790
>> Coordinates for (2790) nodes found
>>
>> Part 1:
>> Description is: Cell data
>> Unstructured Part
>> Number of hexa8 elements in section is: 2205
>> Connectivities for (2205) hexa8 elements found
>>
>> --------
>> Opened example0005.geo successfully
>>
>> File type is: ASCII
>> Description 1: Geometry file
>> Description 2:
>> node ids: assign
>> element ids: assign
>>
>> Global section:
>> Number of nodes: 2980
>> Coordinates for (2980) nodes found
>>
>> Part 1:
>> Description is: Cell data
>> Unstructured Part
>> Number of hexa8 elements in section is: 2367
>> Connectivities for (2367) hexa8 elements found
>>
>> --------
>> Measured filename is: example****.dpg (at line 6)
>>
>> Changing connectivity geometry
>> Associated time set is: 1
>>
>> --------
>> Opened example0001.dpg successfully
>>
>> File type is: ASCII
>> Description 1: Fuel droplets
>> Number of particles: 92
>> Particle ids and coords found for 92 nodes
>>
>> --------
>> Opened example0002.dpg successfully
>>
>> File type is: ASCII
>> Description 1: Fuel droplets
>> Number of particles: 0
>> Particle ids and coords found for 0 nodes
>>
>> --------
>> Opened example0003.dpg successfully
>>
>> File type is: ASCII
>> Description 1: Fuel droplets
>> Number of particles: 0
>> Particle ids and coords found for 0 nodes
>>
>> --------
>> Opened example0004.dpg successfully
>>
>> File type is: ASCII
>> Description 1: Fuel droplets
>> Number of particles: 0
>> Particle ids and coords found for 0 nodes
>>
>> --------
>> Opened example0005.dpg successfully
>>
>> File type is: ASCII
>> Description 1: Fuel droplets
>> Number of particles: 0
>> Particle ids and coords found for 0 nodes
>>
>> >-----------------------<
>> > GEOMETRY section OKAY <
>> >-----------------------<
>>
>> -----------------
>> VARIABLE Section:
>> -----------------
>>
>> scalar per element: temp (at line 9)
>> Filename is: example****.temp
>> Transient variable
>> Associated time set is: 1
>>
>> --------
>> Opened example0001.temp successfully
>>
>> Description: Scalar
>>
>> Part 1:
>> (1395) Per_element scalar values for hexa8 elements found
>>
>> --------
>> Opened example0002.temp successfully
>>
>> Description: Scalar
>>
>> Part 1:
>>
>> ===> Problem:
>> -------------
>> Previous lines end with 2 extra chars on the line,
>> but line 233 has 38 extra chars. The lines must be consistent
>> or EnSight will have trouble reading it.
>> |0.90136E+03 0.90671E+03 0.91014E+03 0.91360E+03 0.92050E+03
>> 0.94085E+03
>> -----------^-----------^-----------^
>> Looking for: (3) numbers per line
>> field width of (12) per number
>>
>>
>> ===> Problem:
>> -------------
>> Not successful reading (1395) per_element scalar values for hexa8
>> elements
>>
>> >-------------------------<
>> > VARIABLE section FAILED <
>> >-------------------------<
>>
>>
>> >-*-*-*-*-*-* bummer! *-*-*-*-*-*-<
>> > <
>> > Verification of the data FAILED <
>> > <
>> >-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-<
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>
>
>
> --
>
--
Zhanping Liu, PhD
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x 138
http://www.zhanpingliu.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20090527/2d8a235f/attachment.htm>
--------------------------------------------------------------------------------
Previous message: [Paraview] (Fwd) Re: Paraview Ensight Reader
Next message: [Paraview] ParaView Python users please read
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
--------------------------------------------------------------------------------
More information about the ParaView mailing list
Jetzt klicken und gucken! Das Arcor.de Fotoalbum mit tausenden von öffentlich einsehbaren Privatfotos!
Wir empfehlen die Kategorie Singles!
http://www.arcor.de/rd/palb
More information about the ParaView
mailing list