← Back to team overview

dolfin team mailing list archive

Re: evaluate_basis() vs evaluate_basis_all() in python dolfin

 

Hi Johan,

On Thu, Apr 21, 2011 at 1:23 AM, Johan Hake <johan.hake@xxxxxxxxx> wrote:
> Update your repo and try!
>
> The ufc::cell version of evaluate_basis_all is not usable in Python. You need
> a dolfin::Cell version, which I just added ;)

Thanks, works now if I use finite_element = V.dolfin_element() rather
than finite_element = V.element().

> We should probably ignore all the ufc::cell versions, and add unit test for
> the one we do expose...

Please excuse my naivete, but what is the essential difficulty in
exposing the functions to the python side? Or at least, why when two
functions have essentially identical C++ function signatures does the
one work in python and not the other?

I ask since from a perspective of both testability of my own code and
of learning what FEniCS does it is quite usefull to be able to call
the lower level functions from python. For instance, I also want to
use finite_element.map_to_reference_cell(), but it seems to give the
same error that evaluate_basis_all() did before you fixed it :)

If it is not to difficult you could teach me how to fix such problems.
Then I could go fishing rather than asking for fish periodically :)

Cheers
Neilen



Follow ups

References