Model:BRaKE

BRaKE

Metadata

Also known as	Blocky River and Knickpoint Evolution Model
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	Watershed-Scale, Reach-Scale
Model domain
One-line model description	Computes evolution of a bedrock river longitudinal profile in the presence of large, hillslope-derived blocks.
Extended model description	BRaKE is a 1-D bedrock channel profile evolution model. It calculates bedrock erosion in addition to treating the delivery, transport, degradation, and erosion-inhibiting effects of large, hillslope-derived blocks of rock. It uses a shear-stress bedrock erosion formulation with additional complexity related to flow resistance, block transport and erosion, and delivery of blocks from the hillslopes.

Keywords:	bedrock channel erosion, bedrock incision, River profile, Channel-hillslope coupling,

Name	Charles Shobe
Type of contact	Model developer
Institute / Organization	Department of Geological Sciences, University of Colorado
Postal address 1	UCB 399
Postal address 2
Town / City	Boulder
Postal code	80309-0399
State	Colorado
Country	United States
Email address	charles.shobe@colorado.edu
Phone	8048404514
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	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, Through CSDMS repository
Source web address	https://github.com/cmshobe/brake-model
Source csdms web address
Program license type	LGPL
Program license type other
Memory requirements
Typical run time	minutes to hours

Describe input parameters	Domain size/length/spacing, time to run, timestep, hillslope response timescale, baselevel lowering rate, bed erodibility, block erodibility, bed critical shear stress, block critical shear stress, block delivery coefficient, initial block size, roughness length scale, channel width, mean discharge, discharge variability, and data recording time interval.
Input format
Other input format
Describe output parameters	Elevation and slope arrays as well as optional information about bed cover and shear stress distributions, as well as block size distributions and incision rate records.
Output format
Other output format	.npy array data structures
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	Fluvial bedrock erosion; hillslope block delivery; block transport and degradation
Describe key physical parameters and equations	Shear stress-driven fluvial erosion, primarily modulated by bed erodibility, critical bed shear stress, block delivery, and block size.
Describe length scale and resolution constraints	This model is intended for a CHANNEL REACH of CONSTANT DRAINAGE AREA.
Describe time scale and resolution constraints	There is no conservation of mass on adjacent hillslopes, which presents a natural time limitation of ~10^6 years.
Describe any numerical limitations and issues	Model is solved implicitly, but can become inaccurate at very large (~1000 year) timesteps. When baselevel forcing is mild and block effects are significant, slope-inversion instabilities can develop. The model catches these and will not continue running.

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 model was initially published as Shobe et al in Geophysical Research Letters, May 2016: http://onlinelibrary.wiley.com/doi/10.1002/2016GL069262/abstract Other publications are in preparation.

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

Charles Shobe

Source code

Model citations

Nr. of publications:	1
Total citations:	77
h-index:	1
m-quotient:	0.1

QR-code

Link to this page

Other models by author

Introduction

BRaKE is the "Blocky River and Knickpoint Evolution" model developed by Charles Shobe in collaboration with Greg Tucker and Bob Anderson at the University of Colorado, Boulder.

History

-Summer 2015: Development started -May 2016: Descriptive paper published -May 2017: Submitted to CSDMS model repository -Ongoing: BMI wrapping

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 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

Issues

Help

Input Files

Output Files