<div dir="ltr">Thanks for the tip Christophe! <br><div>"Mesh.Algorithm3D = 10;" is indeed faster and produces less elements.<br></div><div><br></div><div>Nicolas</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 12 mai 2020 à 13:28, Christophe Geuzaine <<a href="mailto:cgeuzaine@uliege.be">cgeuzaine@uliege.be</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
> On 12 May 2020, at 11:49, Karin&NiKo <<a href="mailto:niko.karin@gmail.com" target="_blank">niko.karin@gmail.com</a>> wrote:<br>
> <br>
> Dear Gmsh Gurus,<br>
> <br>
> I am facing some troubles with a brep CAD I am trying to mesh with Gmsh. <br>
> If I try the meshing default settings, the mesh is being built and Gmsh is proud to announce that no illegal tet stand in the mesh. *But* if I simply run "gmsh -check", Gmsh admits that zero volume tets stay in the mesh. So it is unusable for computation.<br>
<br>
There maybe too many messages, but the optimizer indeed reports that there are 6 tets below the quality threshold in volume 2 with the default algo (we should issue a warning if the quality is indeed approaching zero):<br>
<br>
Info : Optimizing volume 2<br>
Info : Optimization starts (volume = 3.52969e+07) with worst = 0 / average = 0.757222:<br>
Info : 0.00 < quality < 0.10 : 212 elements<br>
Info : 0.10 < quality < 0.20 : 362 elements<br>
Info : 0.20 < quality < 0.30 : 166 elements<br>
Info : 0.30 < quality < 0.40 : 222 elements<br>
Info : 0.40 < quality < 0.50 : 287 elements<br>
Info : 0.50 < quality < 0.60 : 765 elements<br>
Info : 0.60 < quality < 0.70 : 3802 elements<br>
Info : 0.70 < quality < 0.80 : 7720 elements<br>
Info : 0.80 < quality < 0.90 : 4721 elements<br>
Info : 0.90 < quality < 1.00 : 4214 elements<br>
Info : 321 edge swaps, 0 node relocations (volume = 3.52969e+07): worst = 0 / average = 0.765757 (Wall 0.022079s, CPU 0.022s)<br>
Info : 338 edge swaps, 0 node relocations (volume = 3.52969e+07): worst = 0 / average = 0.765884 (Wall 0.0357411s, CPU 0.035583s)<br>
Info : 339 edge swaps, 0 node relocations (volume = 3.52969e+07): worst = 0 / average = 0.765909 (Wall 0.0503662s, CPU 0.050068s)<br>
Info : 6 ill-shaped tets are still in the mesh<br>
<br>
<br>
> I have succeeded in producing a correct mesh by using the Frontal 3D algorithm (Mesh.Algorithm3D = 4;). <br>
> Perhaps a check of the presence of zero volume elements could be an interesting enhancement. <br>
<br>
You can also try<br>
<br>
Mesh.Algorithm3D = 10;<br>
<br>
which is (here a bit) faster.<br>
<br>
Christophe<br>
<br>
<br>
> You'll find all necessary files in the attached archive.<br>
> <br>
> Regards,<br>
> Nicolas<br>
> <foo.tar.gz>_______________________________________________<br>
> gmsh mailing list<br>
> <a href="mailto:gmsh@onelab.info" target="_blank">gmsh@onelab.info</a><br>
> <a href="http://onelab.info/mailman/listinfo/gmsh" rel="noreferrer" target="_blank">http://onelab.info/mailman/listinfo/gmsh</a><br>
<br>
— <br>
Prof. Christophe Geuzaine<br>
University of Liege, Electrical Engineering and Computer Science <br>
<a href="http://www.montefiore.ulg.ac.be/~geuzaine" rel="noreferrer" target="_blank">http://www.montefiore.ulg.ac.be/~geuzaine</a><br>
<br>
<br>
<br>
</blockquote></div>