Model:Bedrock Fault Scarp

From CSDMS
Revision as of 20:29, 21 July 2015 by WikiSysop (talk | contribs) (WikiSysop moved page Temp:Bedrock Fault Scarp to Model:Bedrock Fault Scarp without leaving a redirect)


Bedrock Fault Scarp


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 2D
Spatial extent Watershed-Scale, Reach-Scale
Model domain
One-line model description This is a two-dimensional numerical model that computes the topographic evolution of the facet slope in the footwall of an active normal fault.
Extended model description [[Extended model description::The code computes the formation of a hillslope profile above an active normal fault. It represents the hillslope as a set of points with vertical and horizontal (fault-perpendicular) coordinates. Points move due to a prescribed erosion rate (which may vary in time) and due to offset during earthquakes with a specified recurrence interval and slip rate.

The model is described and illustrated in the following journal article:

Tucker, G. E., S. W. McCoy, A. C. Whittaker, G. P. Roberts, S. T. Lancaster, and R. Phillips (2011), Geomorphic significance of postglacial bedrock scarps on normal-fault footwalls, J. Geophys. Res., 116, F01022, doi:10.1029/2010JF001861.]]

Keywords:

fault, erosion, hillslope, facet, spur, scarp, ,

Name Greg Tucker
Type of contact Model developer
Institute / Organization Cooperative Institute for Research in Environmental Sciences (CIRES)
Postal address 1 Campus Box 399
Postal address 2 University of Colorado
Town / City Boulder
Postal code 80309
State Colorado
Country United States
Email address gtucker@colorado.edu
Phone +1 303 492 6985
Fax +1 303 492 2606


Supported platforms
Unix, Linux, Mac OS
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 2010
Does model development still take place? No
If above answer is no, provide end year model development 2010
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 https://github.com/csdms-contrib/bedrock_fault_scarp
Program license type GPL v2
Program license type other
Memory requirements
Typical run time minutes


Describe input parameters HILLSLOPE_LENGTH: length of hillslope, in meters

NUMBER_OF_NODES: number of model nodes (initially) EROSION_RATE: slope-normal erosion rate in m/yr THRESHOLD_SLOPE: threshold slope angle (m/m) THROW_RATE: fault throw rate, meters per year FAULT_DIP: fault dip angle, degrees SEISMIC_INTERVAL: Time interval between earthquakes, in years RUN_DURATION: duration of run in years DT: time step duration in years OPT_ERO_VAR: option for time variation in erosion rate AMPLITUDE: amplitude of sinusoidal variation (m/yr) PERIOD: period of sinusoidal variation (yr) PHASE: phase offset for sinusoidal variation (degrees) DEL18O_FILENAME: name of file containing oxygen isotope curve DEL18O_POWER: exponent MIN_ERORATE: OPT_PLOT: option for plotting OPT_EPS_PLOT: option for output to .eps file PLOT_INTERVAL: time interval for plotting, in years

Input format ASCII
Other input format
Describe output parameters Simple ascii files containing x and z coordinates of points at end of run. Optional output of figure in .eps format.
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 Weathering and erosion of bedrock on a hillslope; vertical and horizontal displacement due to earthquakes.
Describe key physical parameters and equations [[Describe key physical parameters::See:

Tucker, G. E., S. W. McCoy, A. C. Whittaker, G. P. Roberts, S. T. Lancaster, and R. Phillips (2011), Geomorphic significance of postglacial bedrock scarps on normal-fault footwalls, J. Geophys. Res., 116, F01022, doi:10.1029/2010JF001861.]]

Describe length scale and resolution constraints Resolution on order of one to a few meters. Domain length grows over time, reaching order tens to hundreds of meters long.
Describe time scale and resolution constraints Typical time scale of order tens to hundreds of thousands of years.
Describe any numerical limitations and issues


Describe available calibration data sets [[Describe available calibration data::For case study see:

Tucker, G. E., S. W. McCoy, A. C. Whittaker, G. P. Roberts, S. T. Lancaster, and R. Phillips (2011), Geomorphic significance of postglacial bedrock scarps on normal-fault footwalls, J. Geophys. Res., 116, F01022, doi:10.1029/2010JF001861.]]

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 but possible
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
DOI model 10.1594/IEDA/100097
For model version 0.1
Year version submitted 2011
Link to file http://csdms.colorado.edu/pub/models/doi-source-code/bedrock_fault_scarp-10.1594.IEDA.100097-0.1.tar.gz
Can be coupled with:
Model info

  • Download Bedrock Fault Scarp version: 0.1
    Doi: 10.1594/IEDA/100097
Nr. of publications: 2
Total citations: 75
h-index: 1
m-quotient: 0.08
Qrcode Bedrock Fault Scarp.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