[aspect-devel] Dynamic topography

Ian Rose ian.rose at berkeley.edu
Thu Oct 19 10:18:16 PDT 2017

A bit of context: I agree that the naming of the "topography" and "dynamic
topography" postprocessors are a bit confusing (the distinction is
described in the manual, section A.114). They are that way largely for
historical reasons, as Jacky and I were working on those at roughly the
same time and did not coordinate naming efforts. But yes, what Wolfgang and
Timo say is correct: they are measuring different things. With a free
surface, you expect the dynamic topgraphy to be near zero, since we are
enforcing no-stress boundary conditions there!

As to your other question, Lev: the "topography" postprocessor should
provide an option to output the full topography, rather than just min/max
values. It's just that nobody has put in the work to do the parallel I/O
for it.


On Thu, Oct 19, 2017 at 9:50 AM, Timo Heister <heister at clemson.edu> wrote:

> > Or are you saying that the topography you output is due to the moving
> > boundary? In that case, if the boundary would move in perfect response to
> > the fluid stress underneath, then the "dynamic topography" computed in
> each
> > time step would actually be zero, because there are no excess stresses
> that
> > aren't already accommodated by the displaced surface!
> To add to Wolfgang's reply:
> This is basically how the free surface implementation works, we
> compute how much fluid wants to move through the surface and move the
> surface accordingly.
> --
> Timo Heister
> http://www.math.clemson.edu/~heister/
> _______________________________________________
> Aspect-devel mailing list
> Aspect-devel at geodynamics.org
> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/aspect-devel/attachments/20171019/b5acc5e2/attachment-0001.html>

More information about the Aspect-devel mailing list