User talk:MOSSCO

From CSDMS
Revision as of 12:14, 25 May 2016 by Platipodium (talk | contribs) (Created page with "{{Model identity |Model also known as=Modular System for Shelves and Coasts |Model type=Modular }} {{Start models incorporated}} {{Models incorporated |Incorporated modules=GE...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


MOSSCO


Metadata

Also known as Modular System for Shelves and Coasts
Model type Modular
Model part of larger framework
Note on status model
Date note status model
Incorporated models or components:

GETM, FABM, EROSED, NETCDF, ,

Spatial dimensions 1D, 1.5D, 2D, 3D
Spatial extent Regional-Scale, Landscape-Scale
Model domain
One-line model description http://www.mossco.de
Extended model description http://www.mossco.de/doc
Keywords:
Name Carsten Lemmen
Type of contact Project manager
Institute / Organization Helmholtz-Zentrum Geesthacht
Postal address 1 Max-Planck-Straße 1
Postal address 2
Town / City Geesthacht
Postal code 21502
State
Country Germany
Email address carsten.lemmen@hzg.de
Phone +49415287-2013
Fax +49415287-2020


Supported platforms
Unix, Linux, Mac OS
Other platform
Programming language

Fortran90, Python

Other program language Fortran2003
Code optimized Multiple Processors
Multiple processors implemented Distributed memory
Nr of distributed processors 1-4000
Nr of shared processors
Start year development 2013
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://sf.net/p/mossco/
Source csdms web address
Program license type GPL v3
Program license type other
Memory requirements depends on application
Typical run time depends on application


Describe input parameters Meteorology, Bathymetry, Hydrologic and ecosystem parameters
Input format
Other input format NetCDF
Describe output parameters Typically currents, waves, ecosystem state, benthic-pelagic fluxes
Output format
Other output format NetCDF
Pre-processing software needed? No
Describe pre-processing software
Post-processing software needed? No
Describe post-processing software
Visualization software needed? Yes
If above answer is yes
Other visualization software Python


Describe processes represented by the model Coupler infrastructure
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 Typical application setups available from repository, 0D to 3D test cases
Upload test data sets if available:
Describe ideal data for testing


Do you have current or future plans for collaborating with other researchers? Integration with CDSMS, development of interfaces to OpenMI desired


Do you have current or future plans for collaborating with other researchers?
Is there a manual available? Yes
Upload manual if available:
Model website if any www.mossco.de/doc
Model forum / discussion board
Comments


This part will be filled out by CSDMS staff

OpenMI compliant No not possible
BMI compliant No not possible
WMT component Not yet
PyMT component
Is this a data component
Can be coupled with:

Animation_model_name,

Model info
Nr. of publications: --
Total citations: 0
h-index: --
m-quotient: {{{4}}}
Qrcode MOSSCO.png
Link to this page


Introduction

History

References


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