dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

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).

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).

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