For assembly, we can have coefficients (Functions) defined over other meshes so that the cells are not known.
-- Anders tis 23 juni 2015 kl 16:38 skrev Chris Richardson <[email protected]>: > > On 23/06/2015 15:31, Martin Sandve Alnæs wrote: > >> Both assemble and interpolate have loops over all cells in the mesh, > >> so at least for single-mesh situations the cell will be known. > >> > >> Looking at this from another angle: > >> what exactly is the problem with a Mesh owning its related BBTree? > >> Is it only a matter of making updates safe or is there something else? > >> > >> If we get rid of unsafe ways to modify the Mesh (e.g. > >> MeshGeometry::x()), > >> and add safe ways to modify the Mesh that mark the BBTree as > >> invalidated, > >> > >> does that make all issues go away? > >> > >> Martin > >> > > Yes, and there are other good reasons to deprecate MeshGeometry::x(). > > Chris > > -- > Chris Richardson > BP Institute > Madingley Road > Cambridge CB3 0EZ > _______________________________________________ > fenics mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics >
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
