Model:Bing: Difference between revisions

From CSDMS
m (Text replacement - "{{Add_model_references}} " to "{{Include_references_models}}")
Line 89: Line 89:
<br>{{Add_reference_upload_buttons}}<br><br>
<br>{{Add_reference_upload_buttons}}<br><br>
{{#ifexist:Template:{{PAGENAME}}-citation-indices|{{{{PAGENAME}}-citation-indices}}|}}<br>
{{#ifexist:Template:{{PAGENAME}}-citation-indices|{{{{PAGENAME}}-citation-indices}}|}}<br>
{{Include_references_models}}
{{Add_model_references}}
 
== Issues ==
== Issues ==



Revision as of 16:05, 24 April 2017



Bing


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
Spatial extent
Model domain
One-line model description Submarine debris flows
Extended model description Run a submarine debris flow
Keywords:

sediment transport,

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

C

Other program language
Code optimized Single Processor
Multiple processors implemented
Nr of distributed processors
Nr of shared processors
Start year development 1999
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
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 Minutes


Describe input parameters Yield/shear strength, viscosity, bulk density, shape of failed material; bathymetry
Input format ASCII
Other input format
Describe output parameters Debris flow deposit thickness
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 Submarine debris flow generated by slope failure
Describe key physical parameters and equations Bulk density, viscosity, shear/yield strength
Describe length scale and resolution constraints Vertical resolution typically centimeters
Describe time scale and resolution constraints For stability, time step is typically fractions of a second
Describe any numerical limitations and issues Assumes Bingham rheology


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? 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/100098
For model version 0.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

Nr. of publications: 2
Total citations: 183
h-index: 1
m-quotient: 0.04
Qrcode Bing.png
Link to this page



Introduction

History

References




Nr. of publications: 2
Total citations: 183
h-index: 1
m-quotient: 0.04



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