Model:GullyErosionProfiler1D

From CSDMS
Revision as of 07:06, 28 July 2014 by WikiSysop (talk | contribs)


GullyErosionProfiler1D


Metadata

Also known as
Model type Single
Model part of larger framework
Note on status model
Date note status model
Incorporated models or components:
Spatial dimensions 1D
Spatial extent Reach-Scale
Model domain
One-line model description This model is designed to simulate longitudinal profiles with headward advancing headcuts.
Extended model description This model is designed to simulate longitudinal profiles with headward advancing headcuts. This model simulates gully erosion on the centennial-scale given information such as average rainfall and infiltration rates. The modeler also specifies a headcut erosion rate and or a rule for headcut retreat (either discharge-dependent or height-dependent retreat).
Keywords:

Gully, elevation profile, Matlab, arid alluvial channel,

Name Francis Rengers
Type of contact Model developer
Institute / Organization University of Colorado
Postal address 1 UCB 399
Postal address 2
Town / City Boulder
Postal code 80309-0399
State Colorado
Country USA"USA" is not in the list (Afghanistan, Albania, Algeria, Andorra, Angola, Antigua and Barbuda, Argentina, Armenia, Australia, Austria, ...) of allowed values for the "Country" property.
Email address francis.rengers@colorado.edu
Phone
Fax


Supported platforms
Mac OS, Windows
Other platform
Programming language

Matlab

Other program language
Code optimized Single Processor
Multiple processors implemented
Nr of distributed processors
Nr of shared processors
Start year development
Does model development still take place? No
If above answer is no, provide end year model development 2012
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
Program license type GPL v2
Program license type other
Memory requirements
Typical run time Depends on the settings. Can be several hours.


Describe input parameters The input file is a text file and users are required to input:

Time (in model years) dT (the time step in fractions of a year) tauc (Critical Shear stress for portions of the channel that are vegetated in Pascals) taucWepp (Critical Shear stress for portions of the channel that are soil in Pascals) lenzone (the length of channel that is bare soil in Meters) Pmmphr (Rainfall to be used for erosion in Millimeters per Hour) tval (this is the number of loop iterations before a profile is saved as output) Immphr (Infiltration to be used for erosion in Millimeters per Hour)

One additional input: One must supply the input length of the channel as a matlab data array called xcell.mat

Input format ASCII
Other input format
Describe output parameters The output are elevation values that represent the gully channel profile.
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? Yes
If above answer is yes Matlab
Other visualization software In order to plot the output data, it is probably easiest in Matlab


Describe processes represented by the model This code will erode cells according to a shear stress and also deposit sediment based on the concentration of sediment in a modeled water column. Additionally it has a headcut that migrates upstream and as the headcut erodes it deposits sediment downstream that the model must erode.
Describe key physical parameters and equations manning's n for vegetation

manning's n for soil critical shear stress for vegetation critical shear stress for soil rainfall infiltration

Describe length scale and resolution constraints This works for channels of hundreds of meters with 1 m cells
Describe time scale and resolution constraints It is typically run for times no less than 25 years and no greater than 700 years.
Describe any numerical limitations and issues Numerical instabilities occur if the time step is too large.


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


This part will be filled out by CSDMS staff

OpenMI compliant No not possible
BMI compliant No not possible
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: 1
Total citations: 53
h-index: 1
m-quotient: 0.09

Link to this page

Download statistics

<pbars ytitle=Downloads Title='Monthly Downloads gullyerosionprofiler1d' xlabels=true size=900x200 ymax=10 grid=true box=true cubic=true plots=open xformat=number connected=true angle=90 legend> ,Total downloads: 2 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,0 Oct,0 Nov,0 Dec,0 2014 - Jan,0 Feb,0 Mar,0 Apr,0 May,0 Jun,0 Jul,0 Aug,1 Sep,0 Oct,0 Nov,0 Dec,0 2015 - Jan,1 Feb,0 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:


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