fill_sinks
functions in sinks.hpp
so that those are grid agnostic.
flow_graphe
API!
flow_graph
.
I'd love to see something like that to simulate mountain formation (with some realistic textures representing vegetation levels, snow, etc.)
That would be super cool indeed
DrainageArea
process by the FlowAccumulator
process (https://fastscape.readthedocs.io/en/latest/_api_generated/fastscape.processes.FlowAccumulator.html#fastscape.processes.FlowAccumulator) in which you can provide a value for runoff
(if you assume that all rainfall on the land surface is participating to surface runoff). You can also check the orographic precipitation extension to see how we can reuse those components (https://github.com/fastscape-lem/orographic-precipitation/blob/master/orographic_precipitation/fastscape_ext.py).
Advect
subroutine updates the bedrock elevation b
, the Strati
subroutine reuses b
to update the reflectors, and the FastScape_Execute_Step
subroutine should call Advect
before Strati
... I rarely use the Fortran library directly, though. I'm rather using the fastscape
Python library which has its own StratigraphicHorizons
component.
fastscapelib-fortran
(and its Python bindings). All active horizons should be advected (as their elevation corresponds to the elevation of the simulated topographic surface), but this is not the case for inactive horizons, which are indeed only uplifted in the subroutine run_Strati. However, in the fastscape
library, unless I'm missing something, the elevation of inactive horizons is updated with the bedrock vertical motion, which should include the vertical effect of advection if the HorizontalAdvection process is included in the model.