dolfin team mailing list archive

[Johan Hake <hake@xxxxxxxxx>]

On Thursday 10 September 2009 10:35:12 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:   7000:c2dd266803ab128e594145ee13cf60d664b9f2f5
> tag:         tip
> user:        Anders Logg <logg@xxxxxxxxx>
> date:        Thu Sep 10 10:35:07 2009 +0200
> files:       dolfin/log/log.h site-packages/dolfin/functionspace.py
> description:
> Allow access to DOLFIN element in FunctionSpace from Python:
> 
>   element = V.dolfin_element()
> 
> Need to sort out access to DOLFIN, UFL, FFC, SyFi, FIAT, UFC elements
>  etc... It's quite impressive that we have 6 different finite element
>  classes that are all wrappers for each other. :-)

Exactly. This is why I initiated the Blueprint

  <https://blueprints.launchpad.net/dolfin/+spec/ufc-ufl-versions-of-basic-
types>

Should we rename the current element method to ufl_element?

If so we could just rename (in SWIG) the actuall element function to 
dolfin_element.

Johan

> changeset:   6999:7b7ea0e186a68bead5121abc5aae796c650d59a6
> parent:      6996:8974976b83dd32de4395c25c364ed9737184417a
> parent:      6998:621192c85fc726631dd8ba11d598b4474467dd49
> user:        Anders Logg <logg@xxxxxxxxx>
> date:        Thu Sep 10 10:00:40 2009 +0200
> files:       demo/ode/lorenz/cpp/solution_dual.py
> description:
> merge
> 
> 
> changeset:   6998:621192c85fc726631dd8ba11d598b4474467dd49
> user:        Benjamin Kehlet <benjamik@xxxxxxxxxx>
> date:        Wed Sep 09 16:42:38 2009 +0200
> files:       demo/ode/harmonic/cpp/main_solvedual.cpp
>  demo/ode/lorenz/cpp/main.cpp demo/ode/lorenz/cpp/solution_dual.py
>  dolfin/ode/ODE.cpp dolfin/ode/ODE.h dolfin/ode/ODESolution.cpp
>  dolfin/ode/ODESolution.h dolfin/ode/ODESolver.cpp dolfin/ode/ODESolver.h
>  description:
> Remove solve_dual as ode parameter and add as function. Fix bug in Lorenz
>  demo
> 
> ----------------------------------------------------------------------
> 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
>