Model:DepressionFinderAndRouter

From CSDMS



DepressionFinderAndRouter


Metadata

Also known as
Model type Tool
Model part of larger framework LandLab
Incorporated models or components:
Spatial dimensions 2D
Spatial extent Point-Based
Model domain Terrestrial, Hydrology
One-line model description Find depressions on a topographic surface.
Extended model description This component identifies depressions in a topographic surface, finds an outlet for each depression. If directed to do so (default True), and the component is able to find existing routing fields output from the 'route_flow_dn' component, it will then modify the drainage directions and accumulations already stored in the grid to route flow across these depressions.
Keywords:

flow path, drainage,


First name Dan
Last name Hobley
Type of contact
Institute / Organization
Postal address 1
Postal address 2
Town / City BOULDER
Postal code 80309
State Colorado
Country United States
Email address daniel.hobley@colorado.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 2018
Does model development still take place? No
If above answer is no, provide end year model development 2020
Code development status
When did you indicate the 'code development status'?
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/components/overland_flow
Source csdms web address
Program license type BSD or MIT X11
Program license type other
Memory requirements
Typical run time


Describe input parameters grid : RasterModelGrid

A landlab RasterModelGrid.

routing : str
If grid is a raster type, controls whether lake connectivity can occur on diagonals ('D8', default), or only orthogonally ('D4'). Has no effect if grid is not a raster.

pits : array or str or None, optional
If a field name, the boolean field containing True where pits. If an array, either a boolean array of nodes of the pits, or an array of pit node IDs. It does not matter whether or not open boundary nodes are flagged as pits; they are never treated as such. Default is 'flow__sink_flag', the pit field output from the

py:mod:`FlowDirectors <landlab.components.flow_director>`.

reroute_flow : bool, optional
If True (default), and the component detects the output fields in the grid produced by the FlowAccumulator component, this component will modify the existing flow fields to route the flow across the lake surface(s).

Input format ASCII
Other input format
Describe output parameters "depression__depth":

{ "dtype": float, "intent": "out", "optional": False, "units": "m", "mapping": "node", "doc": "Depth of depression below its spillway point", }

"depression__outlet_node": { "dtype": int, "intent": "out", "optional": False, "units": "-", "mapping": "node", "doc": "If a depression, the id of the outlet node for that depression, otherwise grid.BAD_INDEX", }

"flood_status_code": { "dtype": int, "intent": "out", "optional": False, "units": "-", "mapping": "node", "doc": "Map of flood status (_PIT, _CURRENT_LAKE, _UNFLOODED, or _FLOODED).", }

"is_pit": { "dtype": bool, "intent": "out", "optional": False, "units": "-", "mapping": "node", "doc": "Boolean flag indicating whether a node is a pit.", }

"topographic__elevation": { "dtype": float, "intent": "in", "optional": False, "units": "m", "mapping": "node", "doc": "Land surface topographic elevation", }

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
Can be coupled with:
Model info
Dan Hobley
Citation indices DepressionFinderAndRouter
Nr. of pubs: --
Citations: 0
h-index: --"--" is not a number.
Qrcode DepressionFinderAndRouter.png
Link to this page



Introduction

History

References




Citation indices DepressionFinderAndRouter
Nr. of pubs: --
Citations: 0
h-index: --"--" is not a number.


See more publications of DepressionFinderAndRouter

Issues

Help

Input Files

Output Files