CGAL users discussion list

[Sebastian Bachmann <>]

Hello,

I have a follow up question after I was playing around with the tet 
mesher. I tested Mesh_domain::create_gray_image_mesh_domain and 
Mesh_domain::create_labeled_image_mesh_domain and how it works with the 
polylines_to_protect function.

When using CGAL::polylines_to_protect on the former, it will create 
polylines for each and every gray value - which totally overconstraints 
the problem. Is it possible to find the intersections with the image 
boundary at the isosurface, that was defined in 
create_gray_image_mesh_domain? Or should polylines_to_protect only be 
used with binary/labeled images?

Best,
Sebastian

On 08.04.2022 09:41, Andreas Fabri wrote:
> Hello,
>
> you should use the tetrahedral mesher as surface mesher. The performance 
> is the same.
>
> Best,
>
> Andreas
>
> On 4/8/2022 9:02 AM, Sebastian Bachmann ( via cgal-discuss 
> Mailing List) wrote:
> > Hello!
> >
> > I played around with the surface meshing 
> > (https://doc.cgal.org/latest/Surface_mesher/index.html) and was able 
> > to replicate the example with the CGAL Swig bindings for python. I 
> > tested some of my images and so far, it works really great.
> > I now wanted to test this with images, where the image domain is "at 
> > the boundary", i.e. to produce surface meshes with sharp edges, as it 
> > is possible for 3D 
> > (https://doc.cgal.org/latest/Mesh_3/index.html#title34).
> > However, it seems like that this is not supported with the surface 
> > mesher. Is that correct or did I missed something?
> >
> > Best regards,
> > Sebastian