Sounds good. It would be nice if we could read/write functions without cheating.
-- Anders On Tue, Jan 06, 2009 at 03:51:09PM -0500, Shawn Walker wrote: > Alright, I will look into first being able to write and read a Function > and FunctionSpace. > > - Shawn > > On Mon, 5 Jan 2009, Anders Logg wrote: > >> On Mon, Jan 05, 2009 at 03:26:14PM -0500, Shawn Walker wrote: >>> ok, then this higher order mesh data should definitely have it's own >>> function space. Is it possible to have a FunctionSpace variable (for the >>> mesh) within the usual FunctionSpace variable for the variational >>> problem? It's either that or have two separate FunctionSpace variables >>> floating around and pass them to the bilinear form everytime. >>> >>> - Shawn >> >> I imagine something like this: >> >> A FunctionSpace V has a variable coordinates (a Function). >> >> That Function in turn has a FunctionSpace W (as all other Functions). >> >> V does not have to be the same as V, but it can (for isoparametric >> elements). >> >>
signature.asc
Description: Digital signature
_______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
