Model:Chi analysis tools: Difference between revisions
(Created page with "{{Model identity |Model also known as=Channel segment finder |Model type=Single }} {{Start models incorporated}} {{End a table}} {{Model identity2 |Categories=Terrestrial |Spa...") |
No edit summary |
||
Line 10: | Line 10: | ||
|Spatialscale=Regional-Scale, Landscape-Scale, Watershed-Scale | |Spatialscale=Regional-Scale, Landscape-Scale, Watershed-Scale | ||
|One-line model description=Tool for examining channel profiles in chi-elevation space using the integral method of channel analysis | |One-line model description=Tool for examining channel profiles in chi-elevation space using the integral method of channel analysis | ||
|Extended model description=This tool is used for examining bedrock channels. The tool is based on the assumption that the stream power incision model (SPIM) adequately describes channel incision. Channels profiles are converted to chi-elevation space, where chi is a transformed longitudinal coordinate that takes drainage area into account. The tool uses a variety of statistical tests to extract the most likely series of segments with distinct steepness in chi-elevation space. It also performs statistical tests to determine the best fit m/n ratio, where m is an area (A) exponent and n is a slope (S) exponent in the SPIM with E = K A^m S^n, where E is an erosion rate and K is an 'erodibility'. | |Extended model description=This tool is used for examining bedrock channels. The tool is based on the assumption that the stream power incision model (SPIM) adequately describes channel incision. Channels profiles are converted to chi-elevation space, where chi is a transformed longitudinal coordinate that takes drainage area into account. The tool uses a variety of statistical tests to extract the most likely series of segments with distinct steepness in chi-elevation space. It also performs statistical tests to determine the best fit m/n ratio, where m is an area (A) exponent and n is a slope (S) exponent in the SPIM with E = K A^m S^n, where E is an erosion rate and K is an 'erodibility'. | ||
}} | }} | ||
{{Start model keyword table}} | {{Start model keyword table}} | ||
Line 36: | Line 36: | ||
|Email address=simon.m.mudd@ed.ac.uk | |Email address=simon.m.mudd@ed.ac.uk | ||
|Phone=+44 (0) 131 650 2535 | |Phone=+44 (0) 131 650 2535 | ||
}} | |||
{{Additional modeler information | |||
|Additional first name=David | |||
|Additional last name=Milodowski | |||
|Additional type of contact=Model developer | |||
|Additional institute / Organization=University of Edinburgh | |||
|Additional postal address 1=School of GeoSciences | |||
|Additional postal address 2=Drummond Street | |||
|Additional town / City=Edinburgh | |||
|Additional postal code=EH8 9XP | |||
|Additional state=NO STATE | |||
|Additional country=United Kingdom | |||
}} | |||
{{Additional modeler information | |||
|Additional first name=Stuart | |||
|Additional last name=Grieve | |||
|Additional type of contact=Model developer | |||
|Additional institute / Organization=University of Edinburgh | |||
|Additional postal address 1=School of GeoSciences | |||
|Additional postal address 2=Drummond Street | |||
|Additional town / City=Edinburgh | |||
|Additional postal code=EH8 9XP | |||
|Additional state=NO STATE | |||
|Additional country=United Kingdom | |||
}} | }} | ||
{{Model technical information | {{Model technical information | ||
Line 56: | Line 80: | ||
}} | }} | ||
{{Input - Output description | {{Input - Output description | ||
|Describe input parameters=The input is a 'channel file' and a 'driver file'. The channel file contains data on channel profiles within a channel network composed of a main stem and tributaries flowing into that main stem (that is, there are no tributaries of tributaries). The driver file contains parameters for the model run. The format of these files is described in the documentation that accompanies the model source code. | |Describe input parameters=The input is a 'channel file' and a 'driver file'. The channel file contains data on channel profiles within a channel network composed of a main stem and tributaries flowing into that main stem (that is, there are no tributaries of tributaries). The driver file contains parameters for the model run. The format of these files is described in the documentation that accompanies the model source code. | ||
|Input format=ASCII | |Input format=ASCII | ||
|Describe output parameters=The outputs are | |Describe output parameters=The outputs are | ||
i) For chi_m_over_n_analysis.exe, a *.movern file that contains information about the goodness of fit of channel profiles to a series of linear segments as a function of the m/n ratio: this file is used to determine the best fit m/n ratio of a channel network. | i) For chi_m_over_n_analysis.exe, a *.movern file that contains information about the goodness of fit of channel profiles to a series of linear segments as a function of the m/n ratio: this file is used to determine the best fit m/n ratio of a channel network. | ||
ii) For chi_get_profiles.exe, a series of *.tree files which contain information about the best fit channel segments in chi-elevation space. This data can be used to infer erosion rates, tectonics, or variations in erodibility. | ii) For chi_get_profiles.exe, a series of *.tree files which contain information about the best fit channel segments in chi-elevation space. This data can be used to infer erosion rates, tectonics, or variations in erodibility. | ||
|Output format=ASCII | |Output format=ASCII | ||
|Pre-processing software needed?=Yes | |Pre-processing software needed?=Yes | ||
|Describe pre-processing software=Channel profile data must be prepared to meed the specifications of the *.chan file. The format of this file is described in the documentation provided with the source code. | |Describe pre-processing software=Channel profile data must be prepared to meed the specifications of the *.chan file. The format of this file is described in the documentation provided with the source code. | ||
|Post-processing software needed?=No | |Post-processing software needed?=No | ||
|Describe post-processing software= | |Describe post-processing software= | ||
Line 71: | Line 95: | ||
}} | }} | ||
{{Process description model | {{Process description model | ||
|Describe processes represented by the model=The module performs topographic analysis but the analysis is based on the assumption that the stream power incision model is a good approximation for channel incision. | |Describe processes represented by the model=The module performs topographic analysis but the analysis is based on the assumption that the stream power incision model is a good approximation for channel incision. | ||
|Describe key physical parameters and equations=Topographic analysis so no physical parameters as such. The main parameters fro the module are: | |Describe key physical parameters and equations=Topographic analysis so no physical parameters as such. The main parameters fro the module are: | ||
1) sigma: the uncertainty (in metres, or meters for you yanks), of the topographic data. | 1) sigma: the uncertainty (in metres, or meters for you yanks), of the topographic data. | ||
2) The target nodes: These are the number of nodes you wish to use in each subset of the channel. For details see associated documentation. This should vary between 60-140. The module partitions data and the number of partitions is a highly nonlinear function of the number of nodes so target node values of >150 will lead to compute times of many months - forever. | 2) The target nodes: These are the number of nodes you wish to use in each subset of the channel. For details see associated documentation. This should vary between 60-140. The module partitions data and the number of partitions is a highly nonlinear function of the number of nodes so target node values of >150 will lead to compute times of many months - forever. | ||
3) The minimum segment length: The shortest contiguous number of nodes the user is willing to consider for statistical analysis (in testing, 8-20 performed reasonably well). If you chose 2 you will be performing linear analysis on segments with 2 data points which is clearly nonsense. | 3) The minimum segment length: The shortest contiguous number of nodes the user is willing to consider for statistical analysis (in testing, 8-20 performed reasonably well). If you chose 2 you will be performing linear analysis on segments with 2 data points which is clearly nonsense. | ||
4) Mean skip: See associated documentation, but the module uses a Monte Carlo sampling regime which skips nodes, analyses a subset of data, and then performs this skipping and analysis routine over a number of iterations. For SRTM and ASTER data this should be 1-2. For 10m data it can be 1-10, and for LiDAR data you could skip up to 100 nodes. Note that because of the iterative processes you will need to increase the number of iterations as you increase the skip value if you are to sample all of the data. | 4) Mean skip: See associated documentation, but the module uses a Monte Carlo sampling regime which skips nodes, analyses a subset of data, and then performs this skipping and analysis routine over a number of iterations. For SRTM and ASTER data this should be 1-2. For 10m data it can be 1-10, and for LiDAR data you could skip up to 100 nodes. Note that because of the iterative processes you will need to increase the number of iterations as you increase the skip value if you are to sample all of the data. | ||
|Describe length scale and resolution constraints=With reasonable parameter values channel networks with individual channel of ~1000 nodes will take a few to 10s of minutes to analyse. The longer the channel network, the longer the analysis. | |Describe length scale and resolution constraints=With reasonable parameter values channel networks with individual channel of ~1000 nodes will take a few to 10s of minutes to analyse. The longer the channel network, the longer the analysis. | ||
|Describe time scale and resolution constraints=Topographic analysis so no time scale constraints. | |Describe time scale and resolution constraints=Topographic analysis so no time scale constraints. | ||
|Describe any numerical limitations and issues=See documentation. The major limitation is computational time. This can be alleviated with sensible selection of module parameters. See documentation for guidance. | |Describe any numerical limitations and issues=See documentation. The major limitation is computational time. This can be alleviated with sensible selection of module parameters. See documentation for guidance. | ||
}} | }} | ||
{{Model testing | {{Model testing | ||
|Describe available calibration data sets=Topographic analysis: no calibration required. | |Describe available calibration data sets=Topographic analysis: no calibration required. | ||
|Describe available test data sets=There are 3 datasets within this repository. Once from Southwest Pennsylvania, one from the Apennines in Italy, and one from a CHILD model run. Datasets are the same as those run with the associated manuscript (available at the developer's website) so users can compare results with figures from the manuscript. | |Describe available test data sets=There are 3 datasets within this repository. Once from Southwest Pennsylvania, one from the Apennines in Italy, and one from a CHILD model run. Datasets are the same as those run with the associated manuscript (available at the developer's website) so users can compare results with figures from the manuscript. | ||
|Describe ideal data for testing=Any bedrock channel profile. Module is intended for use on topographic data. | |Describe ideal data for testing=Any bedrock channel profile. Module is intended for use on topographic data. | ||
}} | }} | ||
{{Users groups model | {{Users groups model | ||
Line 93: | Line 117: | ||
}} | }} | ||
{{Additional comments model | {{Additional comments model | ||
|Comments=Manual and data will be included with source files. | |Comments=Manual and data will be included with source files. | ||
}} | }} | ||
{{CSDMS staff part | {{CSDMS staff part |
Revision as of 07:30, 6 September 2013
Chi analysis tools
Metadata
|
|
Download statistics
<pbars ytitle=Downloads Title='Monthly Downloads chi_analysis_tools' xlabels=true size=900x200 ymax=20 grid=true box=true cubic=true plots=open xformat=number connected=true angle=90 legend> ,Total downloads: 130 2008 - Jan,0 Feb,0 Mar,0 Apr,0 May,0 Jun,0 Jul,0 Aug,0 Sep,0 Oct,0 Nov,0 Dec,0 2009 - Jan,0 Feb,0 Mar,0 Apr,0 May,0 Jun,0 Jul,0 Aug,0 Sep,0 Oct,0 Nov,0 Dec,0 2010 - Jan,0 Feb,0 Mar,0 Apr,0 May,0 Jun,0 Jul,0 Aug,0 Sep,0 Oct,0 Nov,0 Dec,0 2011 - Jan,0 Feb,0 Mar,0 Apr,0 May,0 Jun,0 Jul,0 Aug,0 Sep,0 Oct,0 Nov,0 Dec,0 2012 - Jan,0 Feb,0 Mar,0 Apr,0 May,0 Jun,0 Jul,0 Aug,0 Sep,0 Oct,0 Nov,0 Dec,0 2013 - Jan,0 Feb,0 Mar,0 Apr,0 May,0 Jun,0 Jul,0 Aug,0 Sep,9 Oct,10 Nov,3 Dec,5 2014 - Jan,9 Feb,6 Mar,9 Apr,7 May,9 Jun,6 Jul,6 Aug,6 Sep,4 Oct,4 Nov,13 Dec,12 2015 - Jan,11 Feb,1 Mar,0 Apr,0 May,0 Jun,0 Jul,0 </pbars>
Introduction
History
References
Source code
Suggested way to reference a version of the model source code following data reference guidelines:
Publication(s) | Model described | Citations |
---|
Overview and general
Publication(s) | Model described | Citations |
---|
Applications
Publication(s) | Model described | Citations |
---|
Related theory and data
Publication(s) | Model described | Citations |
---|