Model:NormalFault

NormalFault

Metadata

Also known as
Model type	Single
Model part of larger framework	LandLab
Note on status model
Date note status model

Incorporated models or components:

Spatial dimensions	2D
Spatial extent	Regional-Scale, Landscape-Scale, Watershed-Scale
Model domain	Terrestrial, Geodynamic
One-line model description	NormalFault implements relative rock motion due to a normal fault.
Extended model description	The fault can have an arbitrary trace given by two points (x1, y1) and (x2, y2) in the fault_trace input parameter. These value of these points is in model-space coordinates and is not based on node id values or number of rows and columns.

Keywords:	fault, scarp, uplift,

Name	Katy Barnhart
Type of contact
Institute / Organization
Postal address 1
Postal address 2
Town / City	Boulder
Postal code	80309
State
Country	United States
Email address	katherine.barnhart@colorado.edu
Phone
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	2018
Does model development still take place?	No
If above answer is no, provide end year model development	2020
Code development status	Only maintenance
When did you indicate the 'code development status'?	2020
Model availability	As code
Source code availability (Or provide future intension)	Through web repository
Source web address	https://github.com/landlab/landlab/tree/master/landlab
Source csdms web address
Program license type	BSD or MIT X11
Program license type other
Memory requirements
Typical run time

Describe input parameters	[[Describe input parameters model::grid : ModelGrid faulted_surface : str or list of str Surface that is modified by the NormalFault component. Must be a field name or a list of field names if the fault should uplift more than one field. Default value is `topographic__elevation`. If the faulted surface does not yet exist, it will be ingored. The ``run_one_step`` method will check to see an ignored field has been added and if it has been, it will modify it. fault_throw_rate_through_time : dict, optional Dictionary that specifies the time varying throw rate on the fault. Expected format is: `fault_throw_rate_through_time = {'time': array, 'rate': array}` Default value is a constant rate of 0.001 (units not specified). This is acomplished by providing the dictionary `{'time': [0], 'rate': [0.001]}`. NormalFault uses numpy.interp to interpolate the time and rate pattern to the current model time. This function uses the first value for all values less than the first, and the last value for all values greater than the last, and thus providing only one number results in all times getting a rate of that value. fault_dip_angle : float, optional Dip angle of the fault in degrees. Default value is 90 degrees. fault_trace : dictionary, optional Dictionary that specifies the coordinates of two locations on the fault trace. Expected format is .. code-block:: python fault_trace = {'x1': float, 'y1': float, 'x2': float, 'y2': float} where the vector from `(x1, y1)` to `(x2, y2)` defines the strike of the fault trace. The orientation of the fault dip relative to the strike follows the right hand rule. Default is for the fault to strike NE. include_boundaries : boolean, optional Flag to indicate if model grid boundaries should be uplifted. If set to `True` uplifted model grid boundaries will be set to the average value of their upstream nodes. Default value is False.]]
Input format	ASCII
Other input format
Describe output parameters	"topographic__elevation": { "dtype": float, "intent": "inout", "optional": True, "units": "m", "mapping": "node", "doc": "Land surface topographic elevation", }
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
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	https://landlab.github.io
Model forum / discussion board	https://github.com/landlab/landlab/issues

Comments

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 "Code IRF or not" 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	Not yet"Not yet" is not in the list (Yes, In progress, No but possible, No not possible) of allowed values for the "Code PyMT compliant or not" property.
Is this a data component

Can be coupled with:

Model info

Authors

Katy Barnhart

Source code

Go to external source code site

Model citations

Nr. of publications:	--
Total citations:	0
h-index:	--"--" is not a number.
m-quotient:	0

QR-code

Link to this page

Other models by author

Introduction

History

References

Nr. of publications:	--
Total citations:	0
h-index:	--"--" is not a number.
m-quotient:	0

See more publications of NormalFault

Issues

Help

Input Files

Output Files