Hello,
I would like to ask the possibility of adding the .mesh and .ovm formats to the readable/writable formats of paraview. the .mesh format is from geogram software and .ovm for openFlipper, two meshing processing formats.
Both .mesh and .ovm formats do not seem to be specified in the links you shared. Is there proper spec ? I dont think we want to add a geogram or OVM dependencies (but we could if needed)
In regards to OVM, i found also this information (it is almost vtk 4.2 legacy with some slight differences): OpenVolumeMesh: File Format
there is also a fork of meshio that had support for it: WIP OpenVolumeMesh read/write support · mheistermann/meshio@a9219d0 · GitHub
for .mesh just this Documentation de Medit but I contacted the developer of geogram, to see if he has any more complete documentation EDIT: he pointed me to this document: libMeshb/Documentation/libMeshb7.pdf at master · LoicMarechal/libMeshb · GitHub . It is worth noticing that .mesh is redable by gmsh.
In regards to OVM, i found also this information (it is almost vtk 4.2 legacy with some slight differences): OpenVolumeMesh: File Format
Indeed, should be simple enough
pointed me to this document: libMeshb/Documentation/libMeshb7.pdf at master · LoicMarechal/libMeshb · GitHub . It is worth noticing that .mesh is redable by gmsh.
Ha nice, using gmsh is more reasonnable as we alread have it as a dependency
Gmsh can indeed open the GAMMA Mesh Format (libMeshb), but it is quite slow for large meshes.
As for dependencies, libMeshb is a C99 library with no additional dependencies. It has a CMake build system, so I could easily integrate it into my ParaView custom application. It is MIT licensed.
I am working on a ParaView reader that uses the libMeshb API to read a .mesh (ASCII) or a .meshb (the binary version) and create a vtkUnstructuredGrid object without making copies (just passing pointers).
Let me know if you are interested.
That would probably be a welcome addition to ParaView, yes.