dolfin team mailing list archive

[Andre Massing <massing@xxxxxxxxx>]

> Has this been fixed?

Yes and no. It turned out that it was not really a wrong calculation but a
degenerate surface which gave a zero surface. That why I opened a
blueprint to improve the class a bit such the user will be told if such
case occurred. I have a slightly improved version here on my machine but I
have to clean it up a bit. Should link it to the blueprint and add
comment. Not sure about the appropriate status of the bug...

>
> --
> BarycenterQuadrature gives wrong results for tetrahedron triangle
> intersection
> https://bugs.launchpad.net/bugs/575493
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in DOLFIN: New
>
> Bug description:
> If a tetrahedron and triangle (converted from MeshEntities to CGAL
> Nef_polyhedron_3) are intersected and resulting polygon has non-vanishing
> area, BarycenterQuadrature computes quadrature wrong. Actually it gives
> zero area, since some loops are not entered in the
> BarycenterQuadrature::compute_quadrature function. (Such a intersection
> object has surprisingly *NO* half_facets). Check against CGAL is needed.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/dolfin/+bug/575493/+subscribe
>

-- 
BarycenterQuadrature gives wrong results for tetrahedron triangle intersection
https://bugs.launchpad.net/bugs/575493
You received this bug notification because you are a member of DOLFIN
Team, which is subscribed to DOLFIN.

Status in DOLFIN: New

Bug description:
If a tetrahedron and triangle (converted from MeshEntities to CGAL Nef_polyhedron_3) are intersected and resulting polygon has non-vanishing area, BarycenterQuadrature computes quadrature wrong. Actually it gives zero area, since some loops are not entered in the BarycenterQuadrature::compute_quadrature function. (Such a intersection object has surprisingly *NO* half_facets). Check against CGAL is needed.