Model:Spbgc: Difference between revisions

From CSDMS
m (Text replacement - "|CCA component=No not possible" to "|CCA component=Not yet")
m (Text replacement - "|OpenMI compliant=No not possible" to "|OpenMI compliant=Not yet")
Line 78: Line 78:
{{Additional comments model}}
{{Additional comments model}}
{{CSDMS staff part
{{CSDMS staff part
|OpenMI compliant=No not possible
|OpenMI compliant=Not yet
|CCA component=Not yet
|CCA component=Not yet
|IRF interface=Not yet
|IRF interface=Not yet

Revision as of 16:00, 16 August 2016



Spbgc


Metadata

Also known as
Model type Single
Model part of larger framework
Note on status model
Date note status model
Spatial dimensions 2D
Spatial extent
Model domain
One-line model description 2D Numerical Simulation of Turbidity Currents
Extended model description High order two dimensional simulations of turbidity currents using DNS of incompressible Navier-Stokes and transport equations.
Keywords:

turbidity current, flow structure,

Name Zachary Borden
Type of contact Model developer
Institute / Organization UCSB
Postal address 1 Engr II Bldg, Room 2301
Postal address 2 Mechanical Engineering Department, UC Santa Barbara
Town / City Santa Barbara
Postal code 93106
State California
Country United States
Email address zborden@gmail.com
Phone 805 617-9887
Fax 805 617-9887


Supported platforms
Unix, Linux
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 2000
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)
Source web address
Source csdms web address
Program license type GPL v2
Program license type other
Memory requirements Typical ratio: 2,000,000 nodes requires 1 Gbyte
Typical run time Anywhere from minutes to days depending on the resolution


Describe input parameters Input parameters:
* Geometrical parameters: Nx, Ny, domain size
* Flow Parameters: Reynolds, Peclet
* Particle Parameters: Settling velocities.

The complete list of input parameters is set and described in the file input.inp

Input format ASCII
Other input format
Describe output parameters It can output local velocity, vorticity, concentration, stream-function, and all derivatives of velocity necessary to calculate dissipation, viscous momentum diffusion, kinetic energy flux, work by pressure forces, and change in kinetic energy. These quantities are written out in a binary file.
It also has routines for calculating the local height profile and tip position of gravity currents and internal bores, which are outputted every time step and stored as ASCII txt files.
Output format ASCII, Binary
Other output format
Pre-processing software needed? No
Describe pre-processing software
Post-processing software needed? Yes
Describe post-processing software The data is written out to binary files. I have a file called dataconv that converts the binary files to a format readable by the visualization software paraview. I also often use MATLAB to do post-processing on the data in the binary files.
Visualization software needed? Yes
If above answer is yes Matlab
Other visualization software Paraview


Describe processes represented by the model Any type of turbidity (or gravity) currents could be modeled with this code. I also use it for modeling internal bores.
Describe key physical parameters and equations Incompressible flow equations: Navier-Stokes with or without Boussinesq approximation. Transport equation to describe the motion of particles (or Salanity or Temperature).
Describe length scale and resolution constraints With the current version of the code (DNS and no turbulence model) we are restricted to low Reynolds numbers. Up to maximum 10,000.
Describe time scale and resolution constraints A parameter called the CFL number controls the time step in relation to the spatial scales. For boussinesq simulations, a CFL number of 0.2 is usually sufficient for code stability. However, for the non-boussinesq simulations, I usually have to lower the CFL number to around 0.05. It's really just a bit of trial and error though.
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
Is this a data component
Can be coupled with:
Model info
Nr. of publications: --
Total citations: 0
h-index: --"--" is not a number.
m-quotient: 0

Link to this page


Introduction

History

Papers

Issues

Help

Input Files

Output Files