Compatibility to PythonOCC
Hi, I am currently using the Gmsh-Python-API to automatically generate meshes for finite element simulations. For the visualization of only the model geometry, I wanted to make use of pythonocc. Used independently, both - gmsh as well as pythonocc - do their job, i.e. I can visualize a geometry of an stl/brep-file generated with Gmsh and I can save model information, especially the mesh, from python to one of the various output formats. However, when I try to generate a mesh, after i visualized the model geometry using pythonocc, Gmsh/Gmsh-Python-API seems to change its behavior: when I try to generate a mesh, after the geometry visualization, I get an error that there was a binary-divide by zero. When I try to write a mesh, that I generated befor I visualized my geometry, to a binary .msh-file, The file is unusable, since Gmsh mixes up commas and dots (e.g. it says MeshFileVersion 4,1 in the header). This behavior seems strange to me and I cannot find the reason for it. Do you have any idea what happens? Is it maybe the simultaneous use of opencascade by both python modules that messes something up?
Currently I am running Gmsh version 4.5.5 (compiled from source with OpenCascade 7.4.0 and PythonAPI enabled) and the latest version of PythonOCC (also for Opencascade version 7.4.0) on a 64bit Linux machine with Debian bullseye.
I attached the file, where the problem occurs: the change of Gmsh-API behavior happens directly after I call the initialization method of the renderer (line 80)geometryVisualization.py