Property:Describe input parameters model
From CSDMS
This is a property of type Text.
D
Timestep (sec.), Spacestep (m), Flow velocity at river mouth (m/s), Width and depth of river mouth (m), Bedload dumping rate (m/s), Concentration (gm/m3 of coarse and med silt, Concentration (gm/m3) of fine silt and clay) +
W
B
To generate a grid, the user should input the boundary node information, boundary segment information and hole (or island) information in form of a .poly file, as described in the Triangle manual (http://www.cs.cmu.edu/~quake/triangle.poly.html). These input nodes and segments in the .poly file are forced into the triangulation of the domain. Alternatively (and this is a strong point of BATTRI), all this information can be created from only a bathymetric dataset with the use of the editing options of BATTRI (see Option 0 in Running BATTRI section). This process may require manual deleting of unnecessary segments and nodes, closing of islands by segment adding, addition of an open ocean boundary segment, etc.
As a starting point, ordered digital coastline node data can be extracted from the National Geophysical Data Center's webpage (https://www.ngdc.noaa.gov/mgg/shorelines/) at various scales ranging from 1:70,000 to 1:5,000,000. If the coastline is very highly resolved, causing an excessive number of elements along the shoreline, the routine "xy_simplify.m" can be used to reduce the number of nodes to the desired resolution. Remember to format this data into a .poly file, consisting of nodes and segments, before inputting into BATTRI. To refine an already created grid, the user can input the above referenced information either in the form of a previously created .poly file or in the form of NML standard .nod, .ele and .bat files (see next section, Running BATTRI). +
T
Too many to list here. Please see the HTML help system and the wiki pages for all of the process components. +
Q
M
Too many to mention here, see:
http://water.usgs.gov/nrp/gwsoftware/modflow2000/modflow2000.html +
H
Topography
3D temperature and salinity field
2D sea surface height
Tidal components
River discharge
2D Meteo forcing +
C
Topography z(x,y) or parameters describing a topographic surface; rate coefficients; switches for activating options and choosing between alternative transport/erosion formulas. Uses a formatted text file for input of parameters. +
I
P
Topography, temperature, salinity, wind, heat/salt fluxes. Determine by user and application. +
Two input files, all in ESRI ASCII format:
# DEM
# Flow direction grid (D8)
To change the input files, edit lines 19 for DEM and line 20 for Flow-direction in the source code. +
O
Two text files are required as input for analysis of each vertical succession of strata in the following formats.
Vertical thickness and facies succession:
<unit thickness (m)> <facies code (integer)>
<unit thickness (m)> <facies code (integer)>
...
<unit thickness (m)> <facies code (integer)>
EOF
e.g.
0.61 9
0.05 5
0.52 1
...
1.21 3
Facies codes, colour coding and names:
<Facies code 1 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)>
<Facies code 2 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)>
...
<Facies code n (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)>
e.g.
1 0.55 0.32 0 clay
2 1 0.65 0 silt
3 0.93 0.91 0.8 fineSST
4 1 0.95 0.71 medSST
5 0.81 0.71 0.23 crsSST +
Two text files are required as input for analysis of each vertical succession of strata in the following formats.
Vertical thickness and facies succession: <unit thickness (m)> <facies code (integer)> <unit thickness (m)> <facies code (integer)> ... <unit thickness (m)> <facies code (integer)> EOF
e.g. 0.61 9 0.05 5 0.52 1 ... 1.21 3
Facies codes, colour coding and names: <Facies code 1 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)> <Facies code 2 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)> ... <Facies code n (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)>
e.g. 1 0.55 0.32 0 clay 2 1 0.65 0 silt 3 0.93 0.91 0.8 fineSST 4 1 0.95 0.71 medSST 5 0.81 0.71 0.23 crsSST +
Typical inputs of a 1D river profile model (resolution, river length, model time, rock-uplift, erodibility, grain size characteristics) +
F
USer-specified data on temperature distributions
We present the Frost model with a subsampled version of the CRU-NCEP reanalysis data for the region of Alaska. The geographical extent of this dataset has been reduced to greatly reduce the number of ocean, Aleatian Islands or Canadian pixels. The spatial resolution has been reduced by a factor of 13 in each direction, resulting in an effective pixel resolution of about 10km.
The data are monthly average temperatures for each month from January 1901 through December 2009. +
G
Upper Boundary (Air temperature)
Lower Boundary (Temperature gradient)
Initial conditions (Temperature distribution at initial time)
Thermo-physical properties +
P
Users can upload ILAMB-compatible model outputs and benchmark datasets to the PBS. More information can be found in the PBS documentation, available at https://permamodel.github.io/pbs. +
S
Various flow properties; sizes, densities and proportions of all grain fractions making up the active layer of the bed +
C
G
