Summary
| Also known as
|
|
| Model type
|
Single
|
| Model part of larger framework
|
|
| Note on status model
|
|
| Date note status model
|
|
Technical specs
| Supported platforms
|
Unix, Linux
|
| Other platform
|
|
| Programming language
|
C
|
| Other program language
|
|
| Code optimized
|
|
| Multiple processors implemented
|
|
| Nr of distributed processors
|
|
| Nr of shared processors
|
|
| Start year development
|
2006
|
| 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 owner"Through owner" is not in the list (Through web repository, Through CSDMS repository) of allowed values for the "Source code availability" property.
|
| Source web address
|
|
| Source csdms web address
|
|
| Program license type
|
GPL v2
|
| Program license type other
|
|
| Memory requirements
|
Typical ratio: 250,000 nodes requires 1 Gbyte
|
| Typical run time
|
--
|
In/Output
| Describe input parameters
|
Input parameters:
- Geometrical parameters: Nx, Ny, Nz.
- Grid: Uniform or nonuniform.
- Flow Parameters: Reynolds, Peclet
- Particle Parameters: Settling velocities.
- Flags: Output writing flags. Inflow/Outflow to the domain flags.
|
| Input format
|
ASCII
|
| Other input format
|
|
| Describe output parameters
|
Depending on the flags indicated in the input file, typical flow quantities are stored to the file at the given time steps.
Velocities, Pressure, Concentration (of the particles).
Depending on the problems, some other quantities could be stored too.
|
| 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
|
Yes, a C code is developed for this gvg3Dp in order to convert the raw binary data into the xml-vtr format which can be read using paraview software.
|
| Visualization software needed?
|
Yes
|
| If above answer is yes
|
|
| Other visualization software
|
Paraview
|
Process
| Describe processes represented by the model
|
Any type of turbidity (or gravity) currents could be modeled with this code. Is also handles the flows passing complex topographies, inflow/outflows too.
|
| Describe key physical parameters and equations
|
Incompressible flow equations: Navier-Stokes with Boussinesq approximations. 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
|
--
|
| Describe any numerical limitations and issues
|
--
|
Testing
| 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
|
--
|
Other
| 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
|
|
Introduction
History
Papers
Issues
Help
Input Files
Output Files
Download
Source |
