Comment 5 for bug 1155271

On 28 March 2013 06:27, Jan Blechta <email address hidden> wrote:
> I guess this bug also affects mesh moving facility in
> dolfin/ale/*
> dolfin/mesh/MeshSmoothing
> something else ?
>
> I guess something like
> mesh.intersection_operator().clear();
> should be added to the end of every routine which moves mesh by writing to array
> std::vector<double>& x = mesh.geometry().x();
> (which they do)
>

I suggested a while go that the intersection code should be removed
from Mesh to keep Mesh simple (just a data structure, limited
algorithms). The user can create an intersection object. This would
fix this caching issue and make the user responsible for managing the
updating/clearing of the intersection object if the user changes the
Mesh.

Issue with Jan's proposal is that it is very likely that code will be
added in the future and the necessary clear() won't be added. This
isn't good for code maintainability.

Garth

> --
> You received this bug notification because you are a member of DOLFIN
> Core Team, which is subscribed to DOLFIN.
> https://bugs.launchpad.net/bugs/1155271
>
> Title:
> function does not evaluate as expected after modifying mesh
> coordinates
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dolfin/+bug/1155271/+subscriptions