On Wed, Feb 05, 2014 at 03:26:27PM +0100, Martin Sandve Alnæs wrote: > The ufl multidomain infrastructure is finally ready for merging, > already in next and everything looks good. > > I want to deprecate some old syntax for cell related quantities, and use the > geometry constructors instead. In dolfin its also better to pass the mesh > instead of ufl cells. A few examples: > > mesh.ufl_cell().volume -> CellVolume(mesh) > cell.n -> FacetNormal(mesh) > triangle.x -> SpatialCoordinate(mesh) > ... etc. for all ufl geometry quantities. > > When running "cell.foo", ufl will output a deprecation warning which should be > sufficiently annoying for everyone to update quickly. Note that > SpatialCoordinate(cell) is backwards compatible, while SpatialCoordinate(mesh) > is future compatible. > > If you want to use multiple meshes in a form in the future when other features > get in place, you MUST replace use of cell with mesh, or the ambiguity will > trigger errors.
Very good. I have always felt that the cell.n, triangle.x etc variables are non-intuitive. They look like they are hiding inside the cell object. Better with FacetNormal etc. -- Anders _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
