Model:ChiFinder

ChiFinder

Metadata

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

Incorporated models or components:

Spatial dimensions	1D
Spatial extent	Landscape-Scale, Regional-Scale, Watershed-Scale
Model domain	Terrestrial
One-line model description	Calculate Chi Indices
Extended model description	This component calculates chi indices, sensu Perron & Royden, 2013, for a Landlab landscape.

Keywords:	chi index,

Name	Daniel Hobley
Type of contact
Institute / Organization
Postal address 1
Postal address 2
Town / City	Boulder
Postal code	80309
State
Country	United States
Email address	hobleyd@cardiff.ac.uk
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	2016
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
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. reference_concavity : float The reference concavity to use in the calculation. min_drainage_area : float (m2) The drainage area down to which to calculate chi. reference_area : float or None (m2) If None, will default to the mean core cell area on the grid. Else, provide a value to use. Essentially becomes a prefactor on the value of chi. use_true_dx : bool (default False) If True, integration to give chi is performed using each value of node spacing along the channel (which can lead to a quantization effect, and is not preferred by Taylor & Royden). If False, the mean value of node spacing along the all channels is assumed everywhere. clobber : bool (default False) Raise an exception if adding an already existing field.
Input format	ASCII
Other input format
Describe output parameters	"channel__chi_index": { "dtype": float, "intent": "out", "optional": False, "units": "variable", "mapping": "node", "doc": "the local steepness index", }, "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__link_to_receiver_node": { "dtype": int, "intent": "in", "optional": False, "units": "-", "mapping": "node", "doc": "ID of link downstream of each node, which carries the 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", }, "topographic__elevation": { "dtype": float, "intent": "in", "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", }
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

Authors

Daniel Hobley

Source code

Go to external source code site

Model citations

Nr. of publications:	--
Total citations:	0
h-index:	--"--" is not a number.
m-quotient:	0

QR-code

Link to this page

Other models by author

Introduction

History

References

Nr. of publications:	--
Total citations:	0
h-index:	--"--" is not a number.
m-quotient:	0

See more publications of ChiFinder

Issues

Help

Input Files

Output Files