Model:Inflow

Edit Model information

Inflow

Metadata

Summary Contact Technical specs In/Output Process Testing Other Component info 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 Spatial extent Model domain One-line model description Steady-state hyperpycnal flow model Extended model description Steady-state hyperpycnal flow model. Keywords: hyperpycnal inflows, river, Name Eric Hutton Type of contact Model developer Institute / Organization CSDMS, INSTAAR, University of Colorado Postal address 1 1560 30th street Postal address 2 Town / City Boulder Postal code 80305 State Colorado Country United States Email address huttone@colorado.edu Phone Fax Supported platforms Unix, Linux, Mac OS, Windows Other platform Programming language Other program language Code optimized Multiple processors implemented Nr of distributed processors Nr of shared processors Start year development 1997 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 Source web address https://github.com/mcflugen/sedflux Source csdms web address Program license type Apache public license Program license type other Memory requirements Minimal Typical run time Seconds Describe input parameters Main input parameters: River velocity, width, depth, and sediment concentration. Bathymetry Input format ASCII Other input format Describe output parameters CSV file of final bathymetry and deposit thickness for each grain size contained in the flow 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 Hyperpycnal flow Describe key physical parameters and equations See Skene et al., 1997 (doi:10.1016/S0098-3004(97)00064-2) Describe length scale and resolution constraints Horizontal resolution is typically 10s of meters Describe time scale and resolution constraints A single river flood event. Describe any numerical limitations and issues Model has difficulty with negative (uphill) slopes Describe available calibration data sets 1663 Saguenay Fjord event 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? None 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 No but 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 DOI model 10.1594/IEDA/100139 For model version 2.1 Year version submitted 2011 Link to file http://csdms.colorado.edu/pub/models/doi-source-code/sedflux-10.1594.IEDA.100161-2.1.tar.gz Can be coupled with:

Model info Authors Eric Hutton Source code Go to external source code site DOI Download Inflow version: 2.1 Doi: 10.1594/IEDA/100139 Model citations Nr. of publications: 2 Total citations: 47 h-index: 1 m-quotient: 0.03 QR-code Link to this page Other models by author Avulsion Bing Bio Compact Diffusion Flexure Inflow Plume Sedflux Subside WAVEWATCH III Data Component

References

Add a publication

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