Model:DrEICH algorithm

Edit Model information

DrEICH algorithm

Metadata

Summary Contact Technical specs In/Output Process Testing Other Component info Also known as Channel extraction tool Model type Tool Model part of larger framework Note on status model Date note status model Incorporated models or components: Spatial dimensions 2D Spatial extent Landscape-Scale Model domain One-line model description Algorithm for extracting channel networks from high resolution topographic data Extended model description This tool uses chi river profile analysis to predict channel head locations across a landscape and therefore allow the extraction of river networks. It is most suitable for use with high resolution LiDAR (1m) DEMs. The model requires an input DEM in float format and will output the extracted channel heads and networks, also in float format. For detailed information about how to use this tool please refer to the documentation (http://www.geos.ed.ac.uk/~smudd/LSDTT_docs/html/channel_heads.html) and to the associated paper (http://onlinelibrary.wiley.com/doi/10.1002/2013WR015167/full). Keywords: geomorphology, hydrological, bedrock channel erosion, Name Fiona Clubb Type of contact Model developer Institute / Organization University of Edinburgh Postal address 1 Geography Building Postal address 2 Drummond Street Town / City Edinburgh Postal code EH8 9XP State NO STATE Country United Kingdom Email address f.clubb@ed.ac.uk Phone +44 (0)131 650 9170 Fax Name Simon Mudd Type of contact Model developer Institute / Organization University of Edinburgh Postal address 1 Rm 1.05d Geography Building Postal address 2 Drummond Street Town / City Edinburgh Postal code EH8 9XP State NO STATE Country United Kingdom Email address simon.m.mudd@ed.ac.uk Phone +44 (0)131 650 2535 Fax Name David Milodowski Type of contact Model developer Institute / Organization University of Edinburgh Postal address 1 Geography Building Postal address 2 Drummond Street Town / City Edinburgh Postal code EH8 9XP State NO STATE Country United Kingdom Email address D.T.Milodowski@ed.ac.uk Phone +44 (0)131 650 9170 Fax Supported platforms Unix, Linux Other platform Programming language C++ Other program language Code optimized Single Processor Multiple processors implemented Nr of distributed processors Nr of shared processors Start year development 2012 Does model development still take place? Yes If above answer is no, provide end year model development Code development status When did you indicate the 'code development status'? Model availability As code Source code availability (Or provide future intension) Through CSDMS repository Source web address Source csdms web address https://github.com/csdms-contrib/dreich_algorithm Program license type GPL v2 Program license type other Memory requirements Varies depending on the input DEM size Typical run time Around 10 minutes to half an hour Describe input parameters The input file is a DEM in .flt format. A driver text file is also required which contains the parameters used for the extraction. Information on the parameters needed in the driver file is available in the documentation (http://www.geos.ed.ac.uk/~smudd/LSDTT_docs/html/channel_heads.html). Input format Other input format float Describe output parameters Output format Other output format float Pre-processing software needed? Yes Describe pre-processing software A chi analysis of the landscape must first be performed to get the correct m/n value for the landscape. This can be done using the chi analysis toolkit available on CSDMS (http://csdms.colorado.edu/wiki/Model:Chi_analysis_tools). 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 This tool works under the assumption that the channels incise approximately based on the stream power law. It identifies the channel head as the upstream limit of fluvial incision based on the chi profile of the channel. Describe key physical parameters and equations There are two user-defined parameters which need to be defined in the model. 1) The m/n value. This parameter is in the steady state stream power equation for channel slope: dz/dx = (U/K)^1/n * A(x)^(-m/n), where U is rock uplift rate, K is an erodibility coefficient, A is drainage area, and m and n are constants. The best fit m/n value for each landscape must be determined using the chi analysis toolkit (http://csdms.colorado.edu/wiki/Model:Chi_analysis_tools) before the DrEICH algorithm can be run. The routines in the chi analysis toolkit provide a statistical method of identifying the m/n value for the landscape. 2) The number of linked pixels with a contour curvature > 0.1 m^-1. The first stage in the DrEICH algorithm is identifying valleys with positive curvature in which to run the model. A valley is selected to contain a channel head if there are more than a defined number of pixels in that valley with a contour curvature greater than 0.1. This parameter does not affect the location of the channel head within each valley, but does affect how many valleys will be selected. A default value of 10 is suggested, but this may need to vary depending on the relief of the landscape (a lower value of 5 may be more appropriate for lower-relief landscapes). Describe length scale and resolution constraints This algorithm attempts to identify channel head, which are features present on a metre to sub-metre scale. Therefore, the accuracy of the prediction will decrease as the DEM resolution becomes coarser. 1 to 2m resolution DEMs are suggested as appropriate for use with this tool. Describe time scale and resolution constraints No time resolution constraints as this software performs topographic analysis. Describe any numerical limitations and issues With larger DEMs this tool will take longer to run - it takes around half an hour to run with a 1m DEM with 23000 rows and 18000 columns. Documentation is available for guidance. Describe available calibration data sets Topographic analysis; no calibration required. Upload calibration data sets if available: Describe available test data sets Two test DEMs are included in the repository, both from Wayne National Forest, Ohio. Two example driver files, one for each DEM, are also included. These DEMs are the same as are used in the associated manuscript (http://onlinelibrary.wiley.com/doi/10.1002/2013WR015167/full) so that the resulting channel networks can be compared with figures from the paper. Upload test data sets if available: Describe ideal data for testing Any 1m resolution digital elevation model. Do you have current or future plans for collaborating with other researchers? Yes Is there a manual available? Yes Upload manual if available: Model website if any http://www.geos.ed.ac.uk/~smudd/LSDTT_docs/html/channel_heads.html Model forum / discussion board 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 "BMICompliant" 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 Is this a data component Can be coupled with:

Model info Authors Fiona Clubb Mudd, Milodowski Source code View in CSDMS GitHub repository Model citations Nr. of publications: 3 Total citations: 160 h-index: 3 m-quotient: 0.25 QR-code Link to this page Other models by author DrEICH algorithm

References

Add a publication

Nr. of publications:	3
Total citations:	160
h-index:	3
m-quotient:	0.25

Source code

Suggested way to reference a version of the model source code following data reference guidelines:

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations

Overview and general

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations

Applications

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations

Related theory and data

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations