dolfin team mailing list archive

["Garth N. Wells" <gnw20@xxxxxxxxx>]

DOLFIN wrote:
> One or more new changesets pushed to the primary dolfin repository.
> A short summary of the last three changesets is included below.
>
> changeset:   5080:89eb83718857c7d9dbee0003a50983e28533243e
> tag:         tip
> parent:      5079:34987a77383c6b8a37a9c73d40ba4dc38115ca97
> parent:      5078:1182f3401713488f72e0bc52f8031530bf192bd9
> user:        Anders Logg <logg@xxxxxxxxx>
> date:        Mon Nov 03 13:57:42 2008 +0100
> files:       dolfin/fem/DirichletBC.cpp
> description:
> merge

Beat me to it.

I'm running into an issue with DirichletBC and mixed elements because 
BoundaryCondition, from which DirichletBC inherits, creates a new 
FunctionSpace which messes up tests for equivalence and breaks the 
sharing of function spaces paradigm.

Is there a problem if we remove SubDomain from the argument list for 
DirichletBC and just pass the corerct FunctionSpace? One can easily 
extract the necessary sub element FunctionSpace and send it to 
DirihcletBC. To me this is more intuitive.

Garth


> changeset:   5079:34987a77383c6b8a37a9c73d40ba4dc38115ca97
> parent:      5076:8b0e7b0cb07493993a860425be3a6e3ebdd69303
> user:        Anders Logg <logg@xxxxxxxxx>
> date:        Mon Nov 03 13:57:08 2008 +0100
> files:       demo/nls/nonlinearpoisson/cpp/main.cpp dolfin/fem/BoundaryCondition.h dolfin/fem/DirichletBC.cpp dolfin/fem/DirichletBC.h dolfin/fem/PeriodicBC.cpp dolfin/fem/PeriodicBC.h
> description:
> Make apply() functions in BC const
>
>
> changeset:   5078:1182f3401713488f72e0bc52f8031530bf192bd9
> parent:      5077:619c507db3f2674f3e224e12fb9f48503cbdb03d
> parent:      5076:8b0e7b0cb07493993a860425be3a6e3ebdd69303
> user:        "Garth N. Wells <gnw20@xxxxxxxxx>"
> date:        Mon Nov 03 12:40:34 2008 +0000
> files:       
> description:
> merge.
>
> ----------------------------------------------------------------------
> For more details, visit http://www.fenics.org/hg/dolfin
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev