Model:LateralEroder

LateralEroder

Metadata

Also known as
Model type	Tool
Model part of larger framework	LandLab
Note on status model
Date note status model

Incorporated models or components:

Spatial dimensions	2D
Spatial extent	Regional-Scale, Landscape-Scale, Watershed-Scale
Model domain	Terrestrial
One-line model description	Laterally erode neighbor node through fluvial erosion.
Extended model description	Landlab component that finds a neighbor node to laterally erode and calculates lateral erosion.

Keywords:	erosion, lateral erosion,

Name	Abigail Langston
Type of contact
Institute / Organization
Postal address 1
Postal address 2
Town / City	Manhattan
Postal code	66506
State	Kansas
Country	United States
Email address	alangston@k-state.edu
Phone
Fax

Supported platforms	Unix, Linux, Mac OS, Windows
Other platform
Programming language	Python
Other program language
Code optimized	Single Processor
Multiple processors implemented
Nr of distributed processors
Nr of shared processors
Start year development	2019
Does model development still take place?	No
If above answer is no, provide end year model development	2020
Code development status	Only maintenance
When did you indicate the 'code development status'?	2020
Model availability	As code
Source code availability (Or provide future intension)	Through web repository
Source web address	https://github.com/landlab/landlab/tree/master/landlab
Source csdms web address
Program license type	BSD or MIT X11
Program license type other
Memory requirements
Typical run time

Describe input parameters	grid : ModelGrid A Landlab square cell raster grid object latero_mech : string, optional (defaults to UC) Lateral erosion algorithm, choices are "UC" for undercutting-slump model and "TB" for total block erosion alph : float, optional (defaults to 0.8) Parameter describing potential for deposition, dimensionless Kv : float, node array, or field name Bedrock erodibility in vertical direction, 1/years Kl_ratio : float, optional (defaults to 1.0) Ratio of lateral to vertical bedrock erodibility, dimensionless solver : string Solver options: (1) 'basic' (default): explicit forward-time extrapolation. Simple but will become unstable if time step is too large or if bedrock erodibility is very high. (2) 'adaptive': subdivides global time step as needed to prevent slopes from reversing. inlet_node : integer, optional Node location of inlet (source of water and sediment) inlet_area : float, optional Drainage area at inlet node, must be specified if inlet node is "on", m^2 qsinlet : float, optional Sediment flux supplied at inlet, optional. m3/year flow_accumulator : Instantiated Landlab FlowAccumulator, optional When solver is set to "adaptive", then a valid Landlab FlowAccumulator must be passed. It will be run within sub-timesteps in order to update the flow directions and drainage area.
Input format	ASCII
Other input format
Describe output parameters	"drainage_area": { "dtype": float, "intent": "in", "optional": False, "units": "m*2", "mapping": "node", "doc": "Upstream accumulated surface area contributing to the node's discharge", } "flow__receiver_node": { "dtype": int, "intent": "in", "optional": False, "units": "-", "mapping": "node", "doc": "Node array of receivers (node that receives flow from current node)", } "flow__upstream_node_order": { "dtype": int, "intent": "in", "optional": False, "units": "-", "mapping": "node", "doc": "Node array containing downstream-to-upstream ordered list of node IDs", } "lateral_erosion__depth_increment": { "dtype": float, "intent": "out", "optional": False, "units": "m", "mapping": "node", "doc": "Change in elevation at each node from lateral erosion during time step", } "sediment__flux": { "dtype": float, "intent": "out", "optional": False, "units": "m3/y", "mapping": "node", "doc": "Sediment flux (volume per unit time of sediment entering each node)", } "topographic__elevation": { "dtype": float, "intent": "inout", "optional": False, "units": "m", "mapping": "node", "doc": "Land surface topographic elevation", } "topographic__steepest_slope": { "dtype": float, "intent": "in", "optional": False, "units": "-", "mapping": "node", "doc": "The steepest downhill* slope", } "volume__lateral_erosion": { "dtype": float, "intent": "out", "optional": False, "units": "m3", "mapping": "node", "doc": "Array tracking volume eroded at each node from lateral erosion", }
Output format	ASCII
Other output format
Pre-processing software needed?	No
Describe pre-processing software
Post-processing software needed?	No
Describe post-processing software
Visualization software needed?	No
If above answer is yes
Other visualization software

Describe processes represented by the model
Describe key physical parameters and equations
Describe length scale and resolution constraints
Describe time scale and resolution constraints
Describe any numerical limitations and issues

Describe available calibration data sets
Upload calibration data sets if available:
Describe available test data sets
Upload test data sets if available:
Describe ideal data for testing

Do you have current or future plans for collaborating with other researchers?

Is there a manual available?	No
Upload manual if available:
Model website if any	https://landlab.github.io
Model forum / discussion board	https://github.com/landlab/landlab/issues

Comments

This part will be filled out by CSDMS staff

OpenMI compliant	Not yet"Not yet" is not in the list (Yes, No but planned, No but possible, No not possible) of allowed values for the "Code openmi compliant or not" property.
BMI compliant	Not yet"Not yet" is not in the list (Yes, No but planned, No but possible, No not possible) of allowed values for the "Code IRF or not" property.
WMT component	Not yet"Not yet" is not in the list (Yes, In progress, No but possible, No not possible) of allowed values for the "Code CMT compliant or not" property.
PyMT component	Not yet"Not yet" is not in the list (Yes, In progress, No but possible, No not possible) of allowed values for the "Code PyMT compliant or not" property.
Is this a data component