Model:Bio: Difference between revisions

From CSDMS
m (Text replacement - "{{Add_reference_upload_button}}" to "<br>{{Add_reference_upload_button}}<br><br> {{#ifexist:Template:{{PAGENAME}}-citation-indices|{{{{PAGENAME}}-citation-indices}}|}}<br>")
m (Text replacement - "<br>{{Add_reference_upload_button}}<br><br>" to "<br>{{Add_reference_upload_buttons}}<br><br>")
Line 80: Line 80:


== References  ==
== References  ==
<br>{{Add_reference_upload_button}}<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>
{{Add_model_references}}
{{Add_model_references}}

Revision as of 10:09, 31 October 2016



Bio


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 Biogenic mixing of marine sediments
Extended model description Biogenic mixing of marine sediments
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


Name Bjarte Hannisdal
Type of contact
Institute / Organization
Postal address 1
Postal address 2
Town / City
Postal code
State
Country
Email address
Phone
Fax


Supported platforms
Unix, 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 2008
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 GPL v2
Program license type other
Memory requirements 1GB at the most
Typical run time Seconds to minutes


Describe input parameters
Input format ASCII
Other input format
Describe output parameters
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 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/100099
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
Eric Hutton
Hannisdal

Nr. of publications: 4
Total citations: 495
h-index: 3
m-quotient: 0.08
Qrcode Bio.png
Link to this page



Introduction

History

References




Nr. of publications: 4
Total citations: 495
h-index: 3
m-quotient: 0.08



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