[OpenFOAM] Binary vtk data problem

oevermann · October 14, 2005, 03:06

Hello all,

I am having problems reading binary VTK data (UNSTRUCTURED_GRID) with
paraview 2.2.1 (build from source on an Apple G5 running Debian Linux). The data has been created with the foamToVtk on the cavity tutorial case.
Loading the data-file, paraview responds with an unmotivated "Segmentation fault".
However, I can read the same binary data with version 1.8.5 and I can read the
same data as ASCII with 2.2.1 and 1.8.5 as well.
Does anyone has an idea what's going wrong here?

Thanks for help, Michael

mattijs · October 14, 2005, 04:16

You writing the data (i.e. foamToVTK) on the same machine as reading it? Can it be a little endian / big endian problem?

oevermann · October 14, 2005, 06:08

The data is written and read on the same
machine. I also had the little/big endian problem in
mind. Does foamToVTK need any of the vtk libraries or headers? I checked the source and could't find a dependency.
Was there any change in the VTK data format between paraview 1.8 and 2.0?

mattijs · October 16, 2005, 09:53

No change as far as I know. No vtk functions are used to write the files in foamToVTK.

little/big endian is handled in foamToVTK/writeFuns.C but never tested.

Can you let us know if there are any changes to be made?

October 14, 2005, 03:06	Binary vtk data problem	#1
oevermann New Member Michael Oevermann Join Date: Mar 2009 Posts: 15 Rep Power: 17	Hello all, I am having problems reading binary VTK data (UNSTRUCTURED_GRID) with paraview 2.2.1 (build from source on an Apple G5 running Debian Linux). The data has been created with the foamToVtk on the cavity tutorial case. Loading the data-file, paraview responds with an unmotivated "Segmentation fault". However, I can read the same binary data with version 1.8.5 and I can read the same data as ASCII with 2.2.1 and 1.8.5 as well. Does anyone has an idea what's going wrong here? Thanks for help, Michael

October 14, 2005, 04:16	You writing the data (i.e. foa	#2
mattijs Senior Member Mattijs Janssens Join Date: Mar 2009 Posts: 1,419 Rep Power: 26	You writing the data (i.e. foamToVTK) on the same machine as reading it? Can it be a little endian / big endian problem?

October 14, 2005, 06:08	The data is written and read o	#3
oevermann New Member Michael Oevermann Join Date: Mar 2009 Posts: 15 Rep Power: 17	The data is written and read on the same machine. I also had the little/big endian problem in mind. Does foamToVTK need any of the vtk libraries or headers? I checked the source and could't find a dependency. Was there any change in the VTK data format between paraview 1.8 and 2.0?

October 16, 2005, 09:53	No change as far as I know. No	#4
mattijs Senior Member Mattijs Janssens Join Date: Mar 2009 Posts: 1,419 Rep Power: 26	No change as far as I know. No vtk functions are used to write the files in foamToVTK. little/big endian is handled in foamToVTK/writeFuns.C but never tested. Can you let us know if there are any changes to be made?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[OpenFOAM] How to get the coordinates of velocity data at all cells and at all times	vidyadhar	ParaView	9	May 20, 2020 20:06
CFD by anderson, chp 10.... supersonic flow over flat plate	varunjain89	Main CFD Forum	18	May 11, 2018 07:31
[Resolved] GPU on Fluent	Daveo643	FLUENT	4	March 7, 2018 08:02
Binary gives significant performance advantage (Mesh & Solve)	glypo	OpenFOAM	18	January 1, 2015 13:41
How to update polyPatchbs localPoints	liu	OpenFOAM Running, Solving & CFD	6	December 30, 2005 17:27