ffc team mailing list archive

[Peter Brune <prbrune@xxxxxxxxx>]

So, I took a short break from this, but I'm back at it today and have a
couple questions:

1. Why do we not put the metadata for the integral as part of its string
description?  This is a one-line change, but I was wondering what the reason
for reconstructing the integrals without metadata was.
2. Eventually, this all will require other things like the
evaluate_basis_derivative functions to either know about the coordinates, or
to have some sort of a second implementation when associated with a form
(potentially with multiple types of coordinates)
3. By calculating the jacobian in this create_*, ... I'm not quite getting
what you're thinking.  Do you have an organizational idea for this that I'm
not seeing?  Right now I'm appending a coordinate coefficient to forms with
coordinate metadata, and am working on getting it to generate the jacobian
in such a way I could use it.
4.  Two options: either generate the Jacobian like we do now as a
codesnippet and apply it, OR create a preprocessing transformation-aware
transformer that puts the gradient of the coefficient in ALL the right
places (because we're doing this in FFC and know what the basis functions
transform like now).  I'm leaning towards the second because I've already
sort of done it once, and I don't see how one would be slower than the
other.   This might make the above problem with the other evaluation
functions becoming harder.

Thoughts?

- Peter