How to visualize topography on top view in Fastscape

ASPECT
1

Hi, all
I linked ASPECT-Fastscape using the document in this forum (How to run cookbook "fastscape_eroding_box.prm"? - #2 by Djneu).

So, I can obtain the results by modifying “fastscape_eroding_box.prm” in the cookbook to two-dimension as follows

image
image1920×1003 81 KB

image
image1920×1038 82.3 KB

The first is the result at the start time and the second is the result at the end time.

Based on my understanding, I have to run the provided Python code (/aspect/contirb/fastscape/fastscape_rewrite_VTK_with_time.py) to visualize calculated topography on top view like below

image
image1920×1034 132 KB

This result is run in the earlier version in ASPECT-Fastscape.
This photo was provided by another user.

Although I obtained .vts and .pvd file from the Topography*.vtk by running the provided Python code, I can’t visualize it.

image
image1920×1012 82.8 KB

I think this problem is because the topography value is infinite.
Does anyone know how to solve this problem?
My ASPECT version is the latest.

2

I think you meet the same problem as me: How to run cookbook "fastscape_eroding_box.prm"? - #3 by Qyunian
But I still don’t know how to deal with it. :sob:

1 Like
3

Hopefully our problem is solved :blush:

4

Dear Jaeyoon,

Sorry to bother you. I want to know whether you find the way to visualization the fastscape results?
I really want to know how to deal with it. Because I’ve tried many ways but still wrong. T_T

Sincerely,
Shaohui Liu

5

Hi Qyunian,
I’m trying to compare aspect/source/mesh_deformation/fastscape.cc in earlier (aspect/source/mesh_deformation/fastscape.cc at fastscape_lithostatic_totalerosion_healing_updated · Kaili270/aspect · GitHub) and latest version.

Especially, I focus on the visualization section in fastscape.cc.
That’t it!

6

Hi both,

Sorry for taking so long to get back to this. Do both the .vtk and .vts not show up in paraview? I have ran into this problem often before, but it has always been an issue with not correctly setting

export GFORTRAN_CONVERT_UNIT=‘big_endian’

Do you have this set in your .bashrc, and was it set during fastscape installation and is it set whenever you run models? If this is the case and the visualizations still won’t work, I am not exactly sure what is going on.

If you run fastscape outside of ASPECT, do the visualizations show up?

A potential option to also check this is to revert to an older fastscape version (git checkout 508d4c3) where this setting wasn’t necessary. If it still appears in that then something else is going on. The quickest way to check this would be to also to run it solely in fastscape.

To run fastscape on it’s own, after building the .so library you can build/run one of the examples with something like this:

gfortran -O3 Fan.f90 libfastscapelib_fortran.a -o Fan

./Fan