> On 8 Nov 2018, at 14:34, Ham, David A <david.ham@imperial.ac.uk> wrote:
>
> Hmm. OK. For some reason I thought it was worse than this. Is there an example somewhere we could try?
When I looked at this, I ran out of brain, I summarised the issues I found here:
https://github.com/firedrakeproject/firedrake/issues/1246
Basically:
1. Right now the Mesh constructor hard-codes a P1 coordinate field, one needs to change it so that you can pass a coordinate element that it will use (easy).
Yep.
2. There is a reordering that needs to be applied to map from the Plex coordinate field to the Firedrake one. I didn't figure this out.
(Matt: we don't "just use" the plex coordinate field as is, because we don't use any of your evaluation routines. Hence we need it to be a fully-fledged function, with all the numbering conventions that we have).
What about just projecting the coordinate field into your DG space? I think to do this you only need a gadget that evaluates
the coordinates at any point you ask for. Luckily, we have that. Toby made all coordinates use a DMField object, so you can
ask it to evaluate somewhere and it will.
Matt
Lawrence