File Format certainity
 

I am looking at adding a reader to paraview for OpenFoam files. I wanted to find out how set the file format is. Is there any talk of changing the file format soon or even later?

Thanks.

Will your reader be any differ
 

Will your reader be any different from the paraFoam one?

There are no plans to change the file format any time soon. But if you use OpenFOAM functionality to read the mesh all this will be shielded from you.

Mattijs

Nothing is set in stone but I
 

Nothing is set in stone but I am looking at foregoing using the OpenFOAM package to read the files.

Not directly related: do you k
 

Not directly related: do you know whether VTK can handle polyhedral cells directly? We currently have to decompose anything which is more complex than a hex which is annoying.

Mattijs

You may want to take a look at
 

You may want to take a look at convexpointset. That should work although you may take a performance hit.

I was looking at you cell type
 

I was looking at you cell types and I see the following correlation in VTK:

Hexahedron vtkHexahedron
Wedge vtkConvexPointSet
Prism vtkWedge
Pyramid vtkPyramid
Tetrahedon vtkTetrahedon
Tet-Wedge vtkConvexPointSet

We use vtkTetrahedon vtkPyrami
 

We use vtkTetrahedon vtkPyramid vtkWedge vtkHexahedron

I tried convexPointSet and it does not do what I want. It triangulates a convex point cloud but does not see the difference between internal and external faces of the mesh so it shows all faces which makes it very slow.

What I would like is a generic vtk cell shape which implements all the needed functionality (cutting planes, derivatives etc) by on-the-fly decomposition.

Is it possible for you to add
 

Is it possible for you to add an empty .Foam file to the topmost directory in the case by default? This would call for adding one more file to the openfoam format but would not cause a need for changing any other files. It would just be a place holder for an entry point for readers as you did within your parafoam script. It could also be used to store some header info if desired at a later data.

How feasible would it be for you to add that?

Sorry, no intention of doing s
 

Sorry, no intention of doing so at the moment.

- you could change your paraFoam script not to delete the .foam file.
- you could set the extension of 'foam' files to be 'controlDict' instead of '.foam' (if vtk allows this) and click on the system/controlDict

"- you could set the extension
 

"- you could set the extension of 'foam' files to be 'controlDict' instead of '.foam' (if vtk allows this) and click on the system/controlDict" - this was one idea I had.

"- you could change your paraFoam script not to delete the .foam file." - I am planning on writing my own readers for paraview.

I figured I would give it a shot and ask if you could, no big deal I will work around it.