[Paraview] Exodus ii vs Xmdf for Paraview for finite elements post-processing

Dear All, This email is an echo of a previous one where I noticed that for XDMF format, Node Id and Element one are not explicitely provided (for performance issue I guess); writing an interface for renumbering topology (connectivity), datasets and so on is not a problem by itself (jus more

[Paraview] Mixed topology cell number

Dear all Where can I find the topology cell numbers for the xdmf format, especially for the finite elements (vertex, line, triangle, quad, hex, pyra, prism and so on)? If I have the VTK numbers, they are different from the VTK one. In the xdmf website site

[Paraview] 2 different behaviours with using GridType="Collection"

Hi Dear All To build an assembly with its subparts, I use "Collection", but when the file is imported into Paraview 5.5.0, I've met 2 behaviours: - using the xmf reader, the hierachy can be seen on the lower left corner - whereas using the xmf3 one, nothing appears (see the screenshots in

[Paraview] BaseOffset use

Dear All I'm trying to implement "BaseOffset" in my models in order to strat numbering from 1 rather than 0, but Paraview crashes whatever is the reader I use (xmf or xmf3): Am I doing something wrong? Thanks Paul 0. 0. 0. 1. 0. 0. 1. 1. 0. 0. 1. 0. 5 1 2 3 4 0. 0. 0.

[Paraview] Compiling Paraview on CentOS7

Dear All My colleagues and I would like to use Paraview to post-process FEA's results (mechanical and CFD and son on). I compilled the latest Paraview release on my CentOS 7 using mesa3D (from CentOS repository + Qt5 + openMPI + ...) to emulate openGL libraries, I still have a warning from