Model:KnickZone-Picker: Difference between revisions

From CSDMS
(Created page with "{{Model identity |Model also known as=KPP |Model type=Tool }} {{Start models incorporated}} {{End a table}} {{Model identity2 |Categories=Model domain, Terrestrial |Spatial di...")
 
No edit summary
Line 6: Line 6:
{{End a table}}
{{End a table}}
{{Model identity2
{{Model identity2
|Categories=Model domain, Terrestrial
|Spatial dimensions=1.5D, 2D
|Spatial dimensions=1.5D, 2D
|Spatialscale=Regional-Scale, Landscape-Scale, Watershed-Scale, Reach-Scale, Patch-Scale
|Spatialscale=Regional-Scale, Landscape-Scale, Watershed-Scale, Reach-Scale, Patch-Scale
Line 38: Line 37:
|Does model development still take place?=Yes
|Does model development still take place?=Yes
|Model availability=As code
|Model availability=As code
|Source code availability=Through CSDMS repository
|Source code availability=Through web repository
|Source web address=https://github.com/UP-RS-ESP/DEM-KZP
|Program license type=GPL v3
|Program license type=GPL v3
|Memory requirements=depending on DEM size
|Memory requirements=depending on DEM size
Line 67: Line 67:
}}
}}
{{CSDMS staff part
{{CSDMS staff part
|OpenMI compliant=Not yet
|OpenMI compliant=Yes
|IRF interface=Not yet
|IRF interface=Yes
|CMT component=Not yet
|CMT component=Not yet
}}
}}

Revision as of 11:37, 26 May 2017



KnickZone-Picker


Metadata

Also known as KPP
Model type Tool
Model part of larger framework
Note on status model
Date note status model
Incorporated models or components:
Spatial dimensions 1.5D, 2D
Spatial extent Regional-Scale, Landscape-Scale, Watershed-Scale, Reach-Scale, Patch-Scale
Model domain
One-line model description Matlab-based script to extract topometrics for catchments and river knickpoints.
Extended model description --- WHEN USING THIS CODE FOR YOUR RESEARCH, PLEASE CITE: ---

Neely, A., Bookhagen, B., Burbank, D.W. (in review): Connecting Stream Transience and Hillslope Evolution: Insights from a Knickpoints Selection Algorithm applied to Santa Cruz Island, California, JGR-Earth Surface
---

The Matlab-based script extract several topometrics at the catchment scale (drainage area and stream-order size can be adjusted) based on log area/log slope and chi-squared plots. Topometrics include: steepness index, theta, steepness index with adjusted theta for each drainage basin, specific stream power, curvature, local relief, and others. Output is written as GeoTIFF files, shapefiles, and CSV files. In a second step, detrended and normalized chi-squared plots are used to identify river knickpoints. Output is written as shapefile and CSV files.

Keywords:
Name Bodo Bookhagen
Type of contact Model developer
Institute / Organization University of Potsdam
Postal address 1 Institute of Earth and Environmental Science
Postal address 2 Karl-Liebknecht-Str. 24-25
Town / City Potsdam-Golm
Postal code 14476
State
Country Germany
Email address bodo.bookhagen@uni-potsdam.de
Phone
Fax


Supported platforms
Linux, Mac OS, Windows
Other platform
Programming language

Matlab

Other program language
Code optimized Multiple Processors
Multiple processors implemented
Nr of distributed processors
Nr of shared processors
Start year development 2015
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 web repository
Source web address https://github.com/UP-RS-ESP/DEM-KZP
Source csdms web address
Program license type GPL v3
Program license type other
Memory requirements depending on DEM size
Typical run time depending on DEM size


Describe input parameters All input parameters are defined in a well-documented and commented Matlab parameter file.

Only a Digital Elevation Model, preferable in GeoTIFF format is needed.

Input format Binary
Other input format GeoTIFF
Describe output parameters Output data are written as GeoTIFF files, shapefiles, CSV files.
Output format ASCII, Binary
Other output format ESRI shapefiles, GeoTIFF
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
Model forum / discussion board
Comments Well documented Matlab Parameter file, HOWTO file for example catchment and detailed algorithm description with application in:

Neely, A., Bookhagen, B., Burbank, D.W. (in review): Connecting Stream Transience and Hillslope Evolution: Insights from a Knickpoints Selection Algorithm applied to Santa Cruz Island, California, JGR-Earth Surface


This part will be filled out by CSDMS staff

OpenMI compliant Yes
BMI compliant Yes
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
Nr. of publications: --
Total citations: 0
h-index: --"--" is not a number.
m-quotient: 0
Qrcode KnickZone-Picker.png
Link to this page


Introduction

History

References


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 describedCitations


Overview and general


The part "]]" of the query was not understood.</br>Results might not be as expected.
Publication(s)Model describedCitations


Applications


The part "]]" of the query was not understood.</br>Results might not be as expected.
Publication(s)Model describedCitations


Related theory and data


The part "]]" of the query was not understood.</br>Results might not be as expected.
Publication(s)Model describedCitations

Issues

Help

Input Files

Output Files