[firedrake] Perturbing mesh extrusion at runtime

[Tuomas Karna]

Hi David,

Ah, my bad, changing the coordinate function actually works (neat 
feature by the way). I just had some coordinate-dependent functions I 
wasn't updating :/

- Tuomas

On 03/04/2015 02:04 AM, David Ham wrote:
> Hi Tuomas,
>
> I suspect you may be hitting a bug in the assembly cache. Does the 
> issue go away if you specify:
>
> parameters["assembly_cache"]["enabled"] = False
>
> ?
>
> David
> |
> |
>
> On 3 March 2015 at 23:17, Tuomas Karna <tuomas.karna at gmail.com 
> <mailto:tuomas.karna at gmail.com>> wrote:
>
>     Hi all,
>
>     Custom mesh extrusions can be generated by manipulating
>     mesh.coordinates
>     directly. This works fine as long as the coordinates are changed prior
>     to the first solve. After that changing the coordinates has no
>     effect as
>     precomputed mesh properties do not get updated.
>
>     What do I need to do to force a mesh update? I need to update the
>     extrusion only, not the parent mesh. Can this be done efficiently?
>
>
>     Cheers,
>
>     Tuomas
>
>     _______________________________________________
>     firedrake mailing list
>     firedrake at imperial.ac.uk <mailto:firedrake at imperial.ac.uk>
>     https://mailman.ic.ac.uk/mailman/listinfo/firedrake
>
>
>
>
> -- 
> Dr David Ham
> Departments of Mathematics and Computing
> Imperial College London
>
> http://www.imperial.ac.uk/people/david.ham
>
>
> _______________________________________________
> firedrake mailing list
> firedrake at imperial.ac.uk
> https://mailman.ic.ac.uk/mailman/listinfo/firedrake

-------------- next part --------------
HTML attachment scrubbed and removed