> For other geometries where I had this problem, playing a bit with the mesh element sizes helped, but I could not find good numbers for this case. dist=2.1) this problem does not occur, but for larger distances (and these are the ones that I want to study), I always get this error. I attached a simple geometry file that shows this problem.

> Warning : Perfect Match Failed in Quadrangulation, Applying Graph Splits However Blossom almost always fails with the message: > However I run into a probem when I try to create a 2D quad mesh with the outline of two superimposed disks embedded. It is a really great tool and has helped me a lot in my research. > first I want to thank everybody involved in the development of gmsh. > On, at 13:32, Johannes Reinhardt wrote: > Does it happen with all the triangulation methods (MeshAdapt, Delaunay, Frontal, Delaunay for quads)? I will test it on our Linux machine when I have the time. > That's weird - it seems to work fine over here (cf screenshot). > On 02:11 PM, Christophe Geuzaine wrote: > It fails with all the triangulation methods, and the resulting triangulation always shows weird artifacts (see attached screenshot), but at different places depending on the triangulation method. > sorry, that was unfortunate: I had accidentally attached the case for dist = 2.1, which works also here. Indeed: the problem comes from the 'Line in Surface' command, which is still a bit experimental.ДЇor your geometry you should really define two surfaces that would be more 'natural'.

Next message: 'Perfect Match Failed' Problem with Blossom.

Previous message: 'Perfect Match Failed' Problem with Blossom.'Perfect Match Failed' Problem with Blossom Christophe Geuzaine cgeuzaine at ulg.ac.be 'Perfect Match Failed' Problem with Blossom

Gmsh blossom