Re: [Gmsh] Strange meshing behaviour

2020-03-11 Thread Christophe Geuzaine
Hi Peter, Interesting. This seems to be a problem with the generation of the geometry, not the meshing. Attached is the .brep file of the buggy surface (debugSurface.brep): - the OpenCASCADE representation is wrong (see attached picture of the OpenCASCADE-produced STL triangulation), which

[Gmsh] R: R: Slice 3D to get 2D geometry

2020-03-11 Thread Vicini Alessandro
Right, I have "sew faces" active, which kills the volume A. -Messaggio originale- Da: gmsh Per conto di Jeremy Theler Inviato: mercoledì 11 marzo 2020 10:22 A: gmsh@onelab.info Oggetto: Re: [Gmsh] R: Slice 3D to get 2D geometry No, the problem is that Gmsh does import the volume

Re: [Gmsh] R: Slice 3D to get 2D geometry

2020-03-11 Thread Jeremy Theler
No, the problem is that Gmsh does import the volume but after it you ask it to perform either one or more of the OCC "healing" procedures and for some reason these procedures remove the volume. See if you have something like Geometry.OCCFixDegenerated Geometry.OCCFixSmallEdges

[Gmsh] R: Slice 3D to get 2D geometry

2020-03-11 Thread Vicini Alessandro
Ok, the problem is that gmsh does not import a volume from component8.step, only surfaces and lines, so "BoundingBox Volume{v()}" fails. I need to manually generate the volume after import of the step file, and then the rest of the script works. A. Da: gmsh Per conto di Don Van Kerkhoven