[Paraview] Ensight reader

2013-04-22 Thread Prof. Cirrottola
Hy to everyone. I'm trying to load Ensight .case files generated by last rel. of  ADINA. While Ensight 10.00 (free version) reads perfectly Adina .case files,  Paraview 3.98.1  always crashes, using both ascii or b

Re: [Paraview] Ensight Reader

2010-04-28 Thread Zhanping Liu
Hi Werner: The problem is due to the inconsistency between the geometry files and the 'measured geometry' files in terms of ASCII / Binary format. Currently the VTK EnSight reader assumes that these two kinds of geometry files (and their respective data attributes --- pressure, temperature, an

Re: [Paraview] Ensight Reader

2010-04-28 Thread Zhanping Liu
Hi Werner: The VTK EnSight reader is able to load measured geometry files. Could you please send me your dataset for me to debug the problem? Thanks. -Zhanping On Wed, Apr 28, 2010 at 10:27 AM, wrote: > I have some trouble with reading Ensight-Data into Paraview. When I read

[Paraview] Ensight Reader

2010-04-28 Thread Werner . Willems
I have some trouble with reading Ensight-Data into Paraview. When I read the Ensight-case-file the following error occurs: ERROR: In ..\..\..\src\Servers\Filters\vtkEnSightGoldBinaryReader2.cxx, line 1112 vtkEnSightGoldBinaryReader2 (0EFC3ED8): This is not a binary data set. Try vtkEnSightGoldR

Re: [Paraview] Ensight Reader: Invalid number of unstructured points read; check that ByteOrder is set correctly

2009-09-03 Thread Zhanping Liu
The number of points (numPts, on line 2502) returned by vtkEnSightGoldBinaryReader::ReadInt(int *result) is of type int, whereas the file size (2.2GB) is beyond the valid range. I will fix it. Thanks. -Zhanping On Thu, Sep 3, 2009 at 2:40 PM, bastil2...@yahoo.de wrote: > Zhanping, all: > > I h

Re: [Paraview] Ensight Reader: Invalid number of unstructured points read; check that ByteOrder is set correctly

2009-09-03 Thread bastil2...@yahoo.de
Zhanping, all: I have gone forward with this problem today. Uncommenting all the checks in vkEnSightGoldBinaryReader.cxx makes paraview reading the file without any problem. I think the problem with the checks are related to a 64Bit issue. It seems to me as this->FileSize is incorrect for this cas

Re: [Paraview] Ensight Reader: Invalid number of unstructured points read; check that ByteOrder is set correctly

2009-09-02 Thread bastil2...@yahoo.de
Hallo Renato, no these are Ensight-Files that have been written by the commerical FLUENT CFD solver. I can read some of them but not all. Regards BastiL Renato Elias schrieb: > Are you writting your files from Fortran codes using unformatted > "binaries"? > > Renato. > > On Tue, Sep 1, 2009 at 2

Re: [Paraview] Ensight Reader: Invalid number of unstructured points read; check that ByteOrder is set correctly

2009-09-01 Thread bastil2...@yahoo.de
Hi Zhanping, I don't really understand what you mean by "divided into multiple files"? It is an export from the FLUENT CFD code and it consists of an case, geo and several scalar files. What can I do to support you further finding the problem? Regards BastiL Zhanping Liu schrieb: > Hi BastiL: >

Re: [Paraview] Ensight Reader: Invalid number of unstructured points read; check that ByteOrder is set correctly

2009-09-01 Thread Zhanping Liu
Hi BastiL: As you know, Line #2502 (see below) is used to check whether or not the (total) number of points is valid in relation to the file size. I feel that this is a reasonable as well as necessary check. A valid EnSight file is supposed to pass this check. Is your Ensight dataset divided in

Re: [Paraview] Ensight Reader: Invalid number of unstructured points read; check that ByteOrder is set correctly

2009-09-01 Thread Renato Elias
Are you writting your files from Fortran codes using unformatted "binaries"? Renato. On Tue, Sep 1, 2009 at 2:50 PM, bastil2...@yahoo.de wrote: > Hi all, > > I get this error when reading in a (large) Ensight binary case that can > be read by Ensight. ens_checker also reports no errors. > > The

[Paraview] Ensight Reader: Invalid number of unstructured points read; check that ByteOrder is set correctly

2009-09-01 Thread bastil2...@yahoo.de
Hi all, I get this error when reading in a (large) Ensight binary case that can be read by Ensight. ens_checker also reports no errors. The problem is reported from line 2502 from vkEnSightGoldBinaryReader.cxx (revision 1.83). It seems that Ensight Cases can be ok even if this check fails I

Re: [Paraview] EnSight Reader problems

2009-06-15 Thread Zhanping Liu
Hi Adam: Below is some excerpted info (courtesy of Ricardo Reis) on how to check EnSight file formats using 'ens_checker'. ===excerption In this links you (and everyone else) can find the program ens_checker which checks if your files are properly formated for the ensight layout. It che

Re: [Paraview] EnSight Reader problems

2009-06-15 Thread Zhanping Liu
Hi Adam: The error message is now on line 259, vtkEnSightGoldBinaryReader.cxx (as of the version of May 14, 2009), as opposed to line 242 that you report. Does it mean that you are using an out-dated version of the reader? Please update your ParaView/VTK (at least class vtkEnSightGoldBinaryRea

[Paraview] EnSight Reader problems

2009-06-15 Thread Adam Wiktor
Hi, I'm trying to read an EnSight .case file into paraview, but I get the following error message: ERROR: In /tmp/Kitware/ParaView3/VTK/IO/vtkEnSightGoldBinaryReader.cxx, line 242 vtkEnSightGoldBinaryReader (0x164df40): Invalid part id; check that ByteOrder is set correctly. ERROR: In /tmp/Kitw

Re: [Paraview] (Fwd) Re: Paraview Ensight Reader

2009-05-28 Thread pte
alar 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 c

Re: [Paraview] (Fwd) Re: Paraview Ensight Reader

2009-05-27 Thread Zhanping Liu
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 v

Re: [Paraview] (Fwd) Re: Paraview Ensight Reader

2009-05-26 Thread Zhanping Liu
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 ne

[Paraview] (Fwd) Re: Paraview Ensight Reader

2009-05-24 Thread Peter Eckert
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 expect

Re: [Paraview] Paraview Ensight Reader

2009-05-19 Thread Zhanping Liu
Hi Ricardo: Thank you so much. This will help figure out quickly whether a problem is simply due to the invalidity of the file format or a real bug with ParaView's EnSight Reader. -Zhanping On Tue, May 19, 2009 at 12:00 PM, Ricardo Reis wrote: > > In this links you (and everyone else)

Re: [Paraview] Paraview Ensight Reader

2009-05-19 Thread Ricardo Reis
In this links you (and everyone else) can find the program ens_checker which checks if your files are properly formated for the ensight layout. It checks for binary and ASCII files. ens_checker.32 is for 32 bit platforms, ens_checker.64 for 64 bit. Linux off course. http://aero.ist.utl.pt/

Re: [Paraview] Paraview Ensight Reader

2009-05-18 Thread Zhanping Liu
Hi Peter: Would you please create a bug report via Mantis system ( http://paraview.org/Bug/my_view_page.php)? Also please upload to Mantis whatever necessary files used for re-producing the problem. Then I will look into it. BTW, zip files are preferred (to bz2, just in case). Thanks. -

[Paraview] Paraview Ensight Reader

2009-05-18 Thread pte
Hi, I am trying to import some data in Ensight case format into ParaView. Among others (e.g. "vector per node"), my data contains "scalar per element data". The files are ASCII-files. Opening the case file in Paraview does not result in any error and the cell data appears with the other data membe