dolfin team mailing list archive

["Garth N. Wells" <g.n.wells@xxxxxxxxxx>]

On Thu, 2006-06-22 at 15:01 +0200, Anders Logg wrote:
> Boundaries have now been added to the new mesh library. The name has
> changed from Boundary to BoundaryMesh, for two reasons: 
> 
>     1. We may want to add a new class Boundary later (and a class Domain)
>        that represents a geometry (like a CAD model) rather than a mesh
>        of a geometry.
> 
>     2. A BoundaryMesh is also a Mesh (NewMesh until we port everything
>        to the new mesh library).

Great! Can we think now about distinguishing between spatial and
topological dimension in FFC? Then boundary conditions functions can be
defined on elements one topological dimension lower. 

> 
> Just as before, the boundary mesh is created as follows:
> 
>     BoundaryMesh boundary(mesh);
> 
> Note that a new boundary mesh is computed every time and that the
> boundary mesh is separate from the interior mesh. The connection
> between the two will be through a MeshFunction (not added yet).
> 

Is this all that's needed for integration of boundary conditions with
the new mesh library?

Garth 

> In the old mesh library, a Boundary was a special object which shared
> its data with the interior mesh.
> 
> Since a BoundaryMesh is just as much a mesh as the interior mesh (but
> embedded in a higher dimension), it's perfectly ok to do things like
> 
>     BoundaryMesh boundary(mesh);
>     boundary.refine();
> 
> I probably won't push any more major updates to the new mesh library
> before the next release. Let's try to get 0.6.2 ready and then go on
> vacation. Garth has been doing a good job cleaning out a lot of PETSc
> ifdefs but some remain.
> 
> /Anders
> 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/cgi-bin/mailman/listinfo/dolfin-dev