Model:OTTAR

OTTAR

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	Terrestrial, Hydrology
One-line model description	Ode To Transient (Ancho de los) Rivers: Transient evolution of river-channel width in response to river discharge and bank and sediment properties.
Extended model description	Transiently evolving river-channel width as a function of streambank properties, sediment in transport, and the hydrograph. This model is designed to compute the rates of river-channel widening and narrowing based on changing hydrological regimes. It is currently designed for rivers with cohesive banks, with a critical shear stress for particle detachment and an erosion-rate coefficient. OTTAR contains: The RiverWidth class, which contains methods to evolve the width of an alluvial river. The FlowDepthDoubleManning class, which is used to estimate flow depth from discharge, even with an evolving river-channel geometry.

Keywords:	river, channel width,

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	2021
Does model development still take place?	Yes
If above answer is no, provide end year model development
Code development status	Active
When did you indicate the 'code development status'?	2022
Model availability	As code
Source code availability (Or provide future intension)	Through web repository
Source web address	https://github.com/MNiMORPH/OTTAR
Source csdms web address
Program license type	GPL v3
Program license type other
Memory requirements	kb to Mb
Typical run time	Seconds

Describe input parameters	Discharge, channel properties
Input format	ASCII
Other input format
Describe output parameters	River width
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
Model forum / discussion board

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	No

Can be coupled with:

Model info

Authors

Andrew Wickert

Source code

Model citations

QR-code

Link to this page

Other models by author