← Back to team overview

ffc team mailing list archive

Re: Status

 



2010/1/12 Anders Logg <logg@xxxxxxxxx>:
On Tue, Jan 12, 2010 at 08:32:13PM +0100, Kristian Oelgaard wrote:


2010/1/12 Marie Rognes <meg@xxxxxxxxx>:
>Kristian Oelgaard wrote:
>>
>>
>>2010/1/12 Marie Rognes <meg@xxxxxxxxx>:
>>>
>>>Anders Logg wrote:
>>>>
>>>>We've come pretty far on the rewrite of FFC and only a few functions
>>>>remain. As far as I can see, it remains to implement code generation
>>>>for the following functions:
>>>>
>>>>Kristian:
>>>>
>>>> code["evaluate_basis_all"] = not_implemented
>>>> code["evaluate_basis_derivatives"] = not_implemented
>>>> code["evaluate_basis_derivatives_all"] = not_implemented
>>>>
>>>>Marie:
>>>>
>>>> code["tabulate_entity_dofs"] = not_implemented # Marie doesn't know
>>>>what
>>>>this function should do
>>>> code["tabulate_coordinates"] = not_implemented # Marie doesn't believe
>>>>in
>>>>this function
>>>>
>>>>Marie or Kristian:
>>>>
>>>> code["interpolate_vertex_values"] = not_implemented
>>>>
>>>>In addition, we need to get the code generation for the integral
>>>>classes working. It's sort of working for the tensor representation
>>>>but not at all (?) for the quadrature representation. I'll be working
>>>>on getting the tensor representation completely in place.
>>>>
>>>> 
>>>
>>>How are things going?
>>>
>>>I'm have a bug or two to fix in evaluate_dof for integral moments and
>>>will
>>>then fix evaluate_dofs.
>>>Need to sort out FIAT normal directions before correct code is generated
>>>for
>>>RT/BDM though.
>>>Otherwise good.
>>>
>>>Can we move the prefetching of the various format["..."] into the global
>>>scope of codegeneration.py
>>>or is that evil?
>>
>>We need to do something different with the way we handle the formatting.
>>At the moment we just import format from cpp in codegeneration.py, but that
>>is clearly not an option if one wants to generate different code.
>>
>
>Do we have any examples of different code that we want to generate?

Currently not.

Initially, I had in mind that one would like to generate different
code as an option (maybe Fortran) but it hasn't happened yet.

So for now it's just a convenient way to make it easy to edit how the
code is formatted in one single place without needing to search for +,
* etc throughout the code.

Yes, I totally agree. And when/if we decide to generate Fortran I will be very surprised if simply feeding the new format will work out of the box anyway.

Kristian

Another issue is cpp.py importing FFC_OPTIONS which will lead to some difficulties I think w.r.t. format["epsilon"].

Yes, it's an issue. It's something we need to sort out. I'll get to it
in time.

--
Anders


Kristian





_______________________________________________
Mailing list: https://launchpad.net/~ffc
Post to     : ffc@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~ffc
More help   : https://help.launchpad.net/ListHelp


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAktM0jsACgkQTuwUCDsYZdGJzwCfUsPOQ5MgiB1+GE9y6xUsEzYy
JtMAn14KSOisUYkuMq/2wlfzyz/4YpFu
=IwLF
-----END PGP SIGNATURE-----



Attachment: signature.asc
Description: OpenPGP digital signature


References