ffc team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Wed, Dec 16, 2009 at 08:37:35PM +0100, Kristian Oelgaard wrote:
>
>
> 2009/12/16 Anders Logg <logg@xxxxxxxxx>
>
>     On Wed, Dec 16, 2009 at 07:16:08PM +0000, Garth N. Wells wrote:
>     >
>     >
>     > Anders Logg wrote:
>     > > On Wed, Dec 16, 2009 at 06:54:54PM +0000, Garth N. Wells wrote:
>     > >>
>     > >> Anders Logg wrote:
>     > >>> Marie and I have had some discussions on the redesign and FFC and
>     > >>> here's what came out:
>     > >>>
>     > >>>   https://blueprints.launchpad.net/ffc/+spec/ffc-redesign
>
>
> The end result looks very nice. I think it makes sense.
>
>
>
>     > >>>
>     > >>> This allows us to remove both FiniteElement and DofMap since we won't
>     > >>> be needing any of those in the code generation stage.
>     > >>>
>     > >> And where does the transition to the new FIAT fit in?
>     > >
>     > > It's quite orthogonal to that. We just need to make sure that we use
>     > > the new FIAT interface in stage 2.
>     > >
>     > > Note that with this new design (which is really just a stricter
>     > > and cleaner version of what I originally intended) FIAT will only be
>     > > called in stage 2 which will make things easier.
>     > >
>     > > I will start on changing things from the top and down, starting with
>     > > cleanups in compiler.py and then we can go from there.
>     > >
>     >
>     > I am completely confused by the strategy. We discussed moving the work
>     > on the FIAT transition to lp:~ffc-core/ffc/dev, but now FiniteElement
>     > has been removed and the message says that everything is broken. We to
>     > have several things going on at once, none of which are working. Would
>     > it be more sensible to make one thing at a time work? There seems to be
>     > no clear plan.
>
>     The redesign is difficult to do one step at a time. I would have liked
>     to do it in careful steps but I don't see how.
>
>     Here's a more detailed plan:
>
>     1. I rework compile.py tonight.
>
>     2. We make the compiler stages work again, one at a time.
>
>
> As soon as stage 1 is complete we can work on both representations in parallel?

Yes!

It's basically independent but we should decide on a common convention
for the naming/nesting of the dictionary keys, like how to store the
data for the list of elements associated with a form etc.

--
Anders


>
>
>     As part of step 2, we make sure that we
>
>     a) Use the new FIAT interface
>
>     b) Use the code Kristian has been working on for evaluate_basis
>
>
> OK.
>
> Kristian
>
>
>
>
>     -----BEGIN PGP SIGNATURE-----
>     Version: GnuPG v1.4.9 (GNU/Linux)
>
>     iEYEARECAAYFAkspM54ACgkQTuwUCDsYZdHzbwCdFvFPPYvxTRObm8sfqpJ01HHF
>     9GUAoJA1N+eT3SRg249C2+FwNng8MQNW
>     =jgbw
>     -----END PGP SIGNATURE-----
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~ffc
>     Post to     : ffc@xxxxxxxxxxxxxxxxxxx
>     Unsubscribe : https://launchpad.net/~ffc
>     More help   : https://help.launchpad.net/ListHelp
>
>
>

Attachment: signature.asc
Description: Digital signature