dolfin team mailing list archive

[Ola Skavhaug <skavhaug@xxxxxxxxx>]

Anders Logg skrev den 02/06-2008 følgende:
> On Mon, Jun 02, 2008 at 09:05:30AM +0200, Ola Skavhaug wrote:
> > Hi,
> > 
> > I might have missed something on the email list regarding the reasons to
> > remove the boundary mesh constructor taking a couple of meshfunctions to get
> > the mapping from mesh to boundary mesh. We're using this feature a lot. Is
> > there a new logic for boundary meshes that deprecated the old code?
> 
> I removed it to simplify the interface and reduce the number of
> constructors.
> 
> The mappings are now generated automatically and stored as mesh data
> associated with the boundary. To get the mappings, simply do
> 
>   MeshFunction<uint>* vertex_map = boundary.data().meshFunction("vertex map");
>   MeshFunction<uint>* cell_map  = boundary.data().meshFunction("cell map");
> 
> A mesh can now have an arbitrary number of data associated with it,
> either MeshFunctions or Arrays, each associated with a string.

I hoped you had done something like this :)

Nice design.

Ola
 
> -- 
> Anders