← Back to team overview

dolfin team mailing list archive

Re: PyDOLFIN: [...]

 

It will be interesting to see how large the overhead is for the Python
version of the ODE solver. For simple problems where f() is given by
an expression for each component (harmonic oscillator, Lorenz etc),
the overhead should be pretty big. On the other hand, there is
probably very little overhead for large systems (PDEs), where the
f() is something like

    FEM::assemble(L, b, mesh); // action of operator

/Anders

On Sun, Oct 09, 2005 at 07:03:20PM +0200, dolfin@xxxxxxxxxx wrote:
> Commit from johanjan (2005-10-09 19:03 CEST)
> --------------------
> 
> PyDOLFIN:
> 
> Work on ODE interface: ODE::f() is now available, but some problems
> still remain (memory errors).
> 
>   dolfin  src/demo/scripting/pydolfin/Makefile    1.10
>   dolfin  src/demo/scripting/pydolfin/dolfin.i    1.6
>   dolfin  src/demo/scripting/pydolfin/odedemo.py  1.2
> 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/cgi-bin/mailman/listinfo/dolfin-dev
> 

-- 
Anders Logg
Research Assistant Professor
Toyota Technological Institute at Chicago
http://www.tti-c.org/logg/



References