AGRID =
alpha-numeric grid identification (<=24 characters).
BARINCFSB(k,j) = coefficient of free surface subcritical
flow at internal barrier node NBVV(k,j)
and the paired node IBCONN(k,j).
A typical value is BARINCFSB(k,j) = 1.0.
BARINCFSP(k,j) =
coefficient of free surface supercritical flow at internal barrier node NBVV(k,j) and the paired node IBCONN(k,j). A typical value is BARINCFSP(k,j) = 1.0.
BARINHT(k,j) = internal barrier height (positive above the geoid and negative below the geoid)
at node NBVV(k,j) and the paired
node IBCONN(k,j)). The barrier
height must be greater than the bathymetric depth at these nodes, i.e., recalling
the different sign convention between the bathymetric depth and the barrier
height, BARINHT(k,j)
> -DP(NBVV(k,j) and BARINHT(k,j)
> -DP(IBCONN(k,j)). If this is
not satisfied, the run will terminate.
BARLANCFSP(k,j) = coefficient of free surface supercritical flow at
external barrier node NBVV(k,j).
A typical value is BARLANCFSP(k,j)= 1.0.
BARLANHT(k,j) = external barrier height (positive above the geoid and negative below the geoid)
at node NBVV(k,j). The barrier
height must be greater than the bathymetric depth at this node, i.e., recalling
the different sign convention between the bathymetric depth and the barrier
height, BARLANHT(k,j) > -DP(NBVV(k,j). If this is not satisfied, the run will terminate.
BK(k) = bridge pier shape factor (K - see Table 1 in the
section on Bridge Piers)
BALPHA(k) = fraction of the cross section occupied by all of
the piers in the bridge = sum of bridge pier widths/width of cross section
(corresponds to in the section on Bridge
Piers)
BDELX(k) =
approximate nodal spacing at the location of a bridge in the
upstream/downstream direction in meters or feet depending on the grid
coordinate system (for lon,lat coordinates, use
meters for BDELX). (Note that 2*BDELX if the bridge pier effects are distributed across
3 nodes in the alongstream direction)
DP(JN) =
bathymetric depth with respect to the geoid, positive
below the geoid and negative above the geoid. Bathymetric depths above the geoid
or sufficiently small that nodes will dry, require that the wetting/drying
option is enabled (NOLIFA=2 or 3 in the Model Parameter and Periodic Boundary Condition File.)
IBCONN(k,j) = back
face node paired with the front face node, NBVV(k,j), on an internal barrier boundary
= 0
external boundary with no normal flow as an essential boundary condition and no
constraint on tangential flow. This is applied by zeroing the normal boundary
flux integral in the continuity equation and by zeroing the normal velocity in
the momentum equations. This boundary condition should satisfy no normal flow
in a global sense and no normal flow at each boundary node. This type of
boundary represents a mainland boundary with a strong no normal flow condition
and free tangential slip.
= 1
internal boundary with no normal flow treated as an essential boundary condition
and no constraint on the tangential flow. This is applied by zeroing the normal
boundary flux integral in the continuity equation and by zeroing the normal
velocity in the momentum equations. This boundary condition should satisfy no
normal flow in a global sense and no normal flow at each boundary node. This
type of boundary represents an island boundary with a strong normal flow
condition and free tangential slip.
= 2 external boundary with non-zero normal flow as an essential boundary
condition and no constraint on the tangential flow. This is applied by
specifying the non-zero contribution to the normal boundary flux integral in
the continuity equation and by specifying the non-zero normal velocity in the
momentum equations. This boundary condition should correctly satisfy the flux
balance in a global sense and the normal flux at each boundary node. This type
of boundary represents a river inflow or open ocean boundary with a strong
specified normal flow condition and free tangential slip. Discharges are
specified either in the Model Parameter and Periodic Boundary Condition File
for harmonic discharge forcing or in the Non-periodic, Normal Flux Boundary Condition File for
time series discharge forcing.
= 3
external barrier boundary with either zero or non-zero normal outflow from the domain
as an essential boundary condition and no constraint on the tangential flow.
This is applied by specifying the contribution (zero or non-zero) to the normal
boundary flux integral in the continuity equation and by specifying the (zero
or non-zero) normal velocity in the momentum equations. Non-zero normal flow is
computed using a supercritical, free surface weir formula if the barrier is
overtopped. Zero normal flow is assumed if the barrier is not overtopped. This
boundary condition should correctly satisfy the flux balance in a global sense
and the normal flux at each boundary node. This type of boundary represents a
mainland boundary comprised of a dike or levee with strong specified normal
flow condition and free tangential slip. See External Barrier Boundary Note below
for further information on exterior barrier boundaries.
= 4
internal barrier boundary with either zero or non-zero normal flow across the
barrier as an essential boundary condition and no constraint on the tangential
flow. This is applied by specifying the contribution (zero or non-zero) to the
normal boundary flux integral in the continuity equation and by specifying the
normal velocity (zero or non-zero) in the momentum equations. Non-zero normal
flow is compute using either subcritical or
supercritical, free surface weir formula (based on the water level on both
sides of the barrier) if the barrier is overtopped. Zero normal flow is assumed
if the barrier is not overtopped. This type of boundary represents a dike or
levee that lies inside the computational domain with a strong specified normal
flow condition and free tangential slip. See Internal Barrier Boundary Note for
further information on exterior barrier boundaries.
= 5 internal barrier boundary with additional cross barrier pipes located under the
crown. Cross barrier flow is treated as
an essential normal flow boundary condition which leaves/enters the domain on
one side of the barrier and enters/leaves the domain on the corresponding
opposite side of the barrier flow rate and direction are based on barrier
height, surface water elevation on both sides of the barrier, barrier
coefficient and the appropriate barrier flow formula. In addition cross barrier pipe flow rate and
direction are based on pipe crown height, surface water elevation on both sides
of the barrier, pipe friction coefficient, pipe diameter and the appropriate
pipe flow formula. Free tangential slip
is allowed
= 10 external boundary with no normal and no tangential flow as essential
boundary conditions. This is applied by zeroing the normal boundary flux
integral in the continuity equation and by setting the velocity = 0 rather than
solving momentum equations along the boundary. This boundary condition should
satisfy no normal flow in a global sense and zero velocity at each boundary
node. This type of boundary represents a mainland boundary with strong no
normal flow and no tangential slip conditions.
= 11 internal boundary with no normal and no tangential flow as essential
boundary conditions. This is applied by zeroing the normal boundary flux
integral in the continuity equation and by setting the velocity = 0 rather than
solving momentum equations along the boundary. This boundary condition should
correctly satisfy no normal flow in a global sense and zero velocity at each
boundary node. This type of boundary represents an island boundary with strong
no normal flow and no tangential slip conditions.
= 12 external boundary with non-zero normal and zero tangential flow as an
essential boundary condition. This is applied by specifying the non-zero
contribution to the normal boundary flux integral in the continuity equation
and by setting the non-zero normal velocity and zero tangential velocity rather
than solving momentum equations along the boundary. This boundary condition
should correctly satisfy the flux balance in a global sense and the specified
normal/zero tangential velocity at each boundary node. This type of boundary
represents a river inflow or open ocean boundary in which strong normal flow is
specified with no tangential slip. Discharges are specified either in the Model Parameter and Periodic Boundary Condition File
for harmonic forcing or in the Non-periodic, Normal Flux Boundary Condition File for
time series forcing.
=
13 external barrier boundary with either zero or non-zero normal outflow from
the domain and zero tangential flow as essential boundary conditions. This is
applied by specifying the contribution (zero or non-zero) to the normal
boundary flux integral in the continuity equation and by setting the (zero or
non-zero) normal velocity and zero tangential velocity rather than solving
momentum equations along the boundary. Non-zero normal flow is computed using a
supercritical, free surface weir formula if the barrier is overtopped. Zero
normal flow is assumed if the barrier is not overtopped. This boundary
condition should correctly satisfy the flux balance in a global sense and the
normal velocity/zero tangential velocity at each boundary node. This type of
boundary represents a mainland boundary comprised of a dike or levee with
strong specified normal flow and no tangential slip conditions. See External Barrier Boundary Note below
for further information on exterior barrier boundaries.
= 20 external boundary with no normal flow as a natural boundary condition
and no constraint on tangential flow. This is applied by zeroing the normal
boundary flux integral in the continuity equation. There is no constraint on
velocity (normal or tangential) applied in the momentum equations. This
boundary condition should satisfy no normal flow in a global sense, but will
only satisfy no normal flow at each boundary node in the limit of infinite
resolution. This type of boundary represents a mainland boundary with a weak no
normal flow condition and free tangential slip.
= 21 internal boundary with no normal flow as a natural boundary condition
and no constraint on the tangential flow. This is applied by zeroing the normal
boundary flux integral in the continuity equation. There is no constraint on
velocity (normal or tangential) in the momentum equations. This boundary
condition should satisfy no normal flow in a global sense but will only satisfy
no normal flow at each boundary node in the limit of infinite resolution. This
type of boundary represents an island boundary with a weak no normal flow
condition and free tangential slip.
= 22 external boundary with non-zero normal flow as a natural boundary
condition and no constraint on the tangential flow. This is applied by
specifying the non-zero contribution to the normal boundary flux integral in
the continuity equation. There is no constraint on velocity (normal or
tangential) in the momentum equations. This boundary condition should correctly
satisfy the flux balance in a global sense but will only satisfy the normal
flow at each boundary node in the limit of infinite resolution. This type of
boundary represents a river inflow or open ocean boundary with a weak specified
normal flow condition and free tangential slip. Discharges are specified either
in the Model Parameter and Periodic Boundary Condition File
for harmonic discharge forcing or in the Non-periodic, Normal Flux Boundary Condition File for
time series discharge forcing.
=
23 external barrier boundary with either zero or non-zero normal outflow from
the domain as a natural boundary condition and no constraint on the tangential
flow. This is applied by specifying the contribution (zero or non-zero) to the
normal boundary flux integral in the continuity equation. There is no
constraint on velocity (normal or tangential) in the momentum equations.
Non-zero normal flow is computed using a supercritical, free surface weir
formula if the barrier is overtopped. Zero normal flow is assumed if the
barrier is not overtopped. This boundary condition should correctly satisfy the
flux balance in a global sense but will only satisfy the normal flow at each
boundary node in the limit of infinite resolution. This type of boundary
represents a mainland boundary comprised of a dike or levee with a weak
specified normal flow condition and free tangential slip. See External Barrier Boundary Note below
for further information on exterior barrier boundaries.
=
24 internal barrier boundary with either zero or non-zero normal flow across
the barrier as a natural boundary condition and no constraint on the tangential
flow. This is applied by specifying the contribution (zero or non-zero) to the
normal boundary flux integral in the continuity equation. There is no
constraint on velocity (normal or tangential) in the momentum equations.
Non-zero normal flow is compute using either subcritical
or supercritical, free surface weir formula (based on the water level on both
sides of the barrier) if the barrier is overtopped. Zero normal flow is assumed
if the barrier is not overtopped. This boundary condition should correctly
satisfy the flux balance in a global sense but will only satisfy the normal
flow at each boundary node in the limit of infinite resolution. This type of
boundary represents a dike or levee that lies inside the computational domain
with a weak specified normal flow condition and free tangential slip. See Internal Barrier Boundary Note below
for further information on exterior barrier boundaries.
= 25 internal barrier boundary with additional cross barrier pipes located under the
crown. Cross barrier flow is treated as
a natural normal flow boundary condition which leaves/enters the domain on one
side of the barrier and enters/leaves the domain on the corresponding opposite
side of the barrier. Flow rate and
direction are based on barrier height, surface water elevation on both sides of
the barrier, barrier coefficient and the appropriate barrier flow formula. In addition cross barrier pipe flow rate and
direction are based on pipe crown height, surface water elevation on both sides
of the barrier, pipe friction coefficient, pipe diameter and the appropriate
pipe flow formula. Free tangential slip
is allowed.
=
30 wave radiation normal to the boundary as a natural boundary condition. This
is applied by specifying the contribution to the normal boundary flux integral
in the continuity equation. There is no constraint on velocity (normal or
tangential) in the momentum equations. The normal flow is computed using a Sommerfield radiation condition. This boundary condition
should correctly satisfy the flux balance in a global sense but will only
satisfy the normal flow at each boundary node in the limit of infinite resolution.
This type of boundary represents an open boundary where waves are allowed to
propagate freely out of the domain.
=
32 a combined specified normal flux and outward radiating boundary. The GWCE is forced with the total normal flux
computed by adding the specified normal flux and the flux associated with the
outward radiating wave. The latter is
determine from a Sommerfeld type condition,
flux=celerity*wave elevation. The
momentum equations are used to compute the velocity field the same as for a nonboundary node.
=
40 a zero normal velocity gradient boundary.
The GWCE is forced with normal flux, the momentum eqs
are sacrificed in favor of setting the velocity at a boundary node equal to the
value at a fictitious point inside the domain.
The fictitious point lies on the inward directed normal to the boundary
a distance equal to the distance from the boundary node to its farthest
'neighbor. This should ensure that the fictitious point does not fall into an
element that contains the boundary node.
The velocity at the fictitious point is determined by interpolation.
=
41 a zero normal velocity gradient boundary.
The GWCE is forced with normal flux.
The momentum eqs are sacrificed in favor of eqs that set the velocity gradient normal to the boundary
equal to zero in the Galerkin sense.
IBTYPEE = elevation boundary type, (At present the only
allowable value for IBTYPEE is 0). Elevations are specified either in the Model Parameter and Periodic Boundary Condition File
for harmonic forcing or in the Non-periodic Elevation Boundary Condition File for
time series forcing.
JE = element number. The elements must be input in
ascending order.
JN = node number. The nodes must be input in ascending
order.
NBDV(k,j) = node numbers on elevation specified boundary
segment k. The node numbers must be entered in order as one moves along the
boundary segment, however the direction (counter clockwise or clockwise around
the domain) does not matter.
NBPNODES =
total number of nodes (centerline and adjacent) in ADCIRC grid used to
represent the effects of bridge piers
NBNNUM(k) =
node number in the ADCIRC grid of node k used to represent the frictional
effects of bridge piers
NBOU = number of normal flow (discharge) specified
boundary segments. These include zero normal flow (land) boundaries, non-zero
normal flow (river) boundaries, potentially overflowing external barrier
boundaries, potentially overtopping internal barrier boundaries and radiation
boundaries. See also General Notes for
Normal Flow Boundary Conditions.
NBVV(k,j) = node
numbers on normal flow boundary segment k. The node numbers must be entered in
order as one moves along the boundary segment with land always on the right,
i.e., in a counter clockwise direction for external (e.g., mainland, external
barrier) boundaries and a clockwise direction for internal (e.g., island,
internal barrier) boundaries. For an internal barrier boundary (IBTYPE(k) = 4, 24) only the nodes
on the front face of the boundary are specified in NBVV(k,j). The paired nodes on the back
face of the boundary are specified in IBCONN(k,j).
NE = number of
elements in the horizontal grid
NETA = total number of elevation specified boundary nodes
NHY = number of nodes per element. At present the only
allowable value for the number of nodes per element is 3 indicating a
triangular element with linear basis functions.
NM(JE,1), NM(JE,2), NM(JE,3) = node numbers
comprising element JE. These must be specified in a counter clockwise direction
moving around the element.
NOPE = number of elevation specified boundary forcing
segments.
NP = number of nodes in the horizontal grid
NVDLL(k) = number
of nodes in elevation boundary segment k
NVEL = total number of normal flow specified boundary
nodes including both the front and back nodes on internal barrier boundaries.
NVELL(k) = number of nodes in normal flow specified boundary
segment k. For an internal barrier boundary (IBTYPE 4 or
24), NVELL(k) includes only the
nodes on the front face of the boundary as specified in NBVV(k,j) and not the paired nodes on the back face of the
boundary specified in IBCONN(k,j).
X(JN), Y(JN) = X and Y coordinates. If ICS=1 in the Model Parameter and Periodic Boundary Condition File
then X(JN), Y(JN) are Cartesian coordinates with units of length (e.g., feet or
meters) that are consistent with the definition of gravity in the Model Parameter and Periodic Boundary Condition File.
If ICS=2 in the Model Parameter and Periodic Boundary Condition File
then X(JN), Y(JN) are spherical coordinates in degrees of longitude (east of
Greenwich is positive and west of Greenwich is negative) and degrees of
latitude (north of the equator is positive and south of the equator is
negative)
RUNDES = alpha-numeric run description 1 (<=32
characters)
RUNID = alphanumeric run description 2 (<= 24
characters)
NFOVER = non-fatal error override option;
=
0, inconsistent input parameters will cause program termination.
=
1, inconsistent input parameters will, (when possible), be automatically
corrected to a default or consistent value and execution continued. Be sure to
read the nonfatal warning messages to see whether any parameters have been
modified. Note that not all inconsistent parameters can be corrected
automatically and therefore fatal error messages and program termination may
still result.
NABOUT = parameter controlling whether output to the
diagnostic run information file (fort.16) is abbreviated or verbose.
=
0, output to the diagnostic run information file (fort,16) will include echo
printing of most input files including the fort.14, fort.21 and fort.22 files.
=
1, output to the diagnostic run information file (fort.16) will be abbreviated
by not echo printing most of the fort.14, 21, and 22 input
information.
NSCREEN = parameter controlling screen output (fort.6)
= 0
no screen output (fort.6) is written
= 1
screen output (fort.6) is written
IHOT = parameter controlling whether the model is hot started.
The hot start facility is presently only available for 2DDI runs.
= 0
cold start the model
=
67 hot start model using input information in hot start file fort.67
=
68 hot start model using input information in hot start file fort.68
ICS = parameter controlling whether the model is run in
spherical or Cartesian coordinates.
= 1
ADCIRC governing equations are in standard Cartesian coordinates. Coordinates
in the grid file (fort.14) are assumed to have units of length that are
consistent with the units of gravity (as specified below). In the unlikely case
that tidal potential forcing (NTIP=1 or 2) and/or a
spatially variable Coriolis coefficient (NCOR=1) are desired for this type of run, an inverse map
projection (Carte Parallelo-grammatique) is used to
obtain longitude and latitude values for the grid. However, we strongly
recommend that if the model domain is large enough for either spatially variable
Coriolis or tidal potential forcing to be considered
important, the model should be run with spherical governing equations (ICS=2) using a longitude, latitude grid.
= 2
ADCIRC governing equations are in spherical coordinates transformed into
Cartesian coordinates prior to discretization using a
map projection (Carte Parallelo-grammatique - CPP).
Coordinates in the grid file (fort.14) are in decimal degrees longitude and
latitude. This option is presently only available for 2DDI runs.
IM = model type
= 0
Barotropic 2DDI run using original GWCE and Momentum
equation formulations
= 1
Barotropic 3D run using original GWCE and velocity
based Momentum equations
= 2
3D run using original GWCE and stress based Momentum equations (not fully
implemented)
=
10 Barotropic 2DDI run using original GWCE and
Momentum equation formulations plus passive scalar transport (not fully
implemented)
=
11 Barotropic 3D run using original GWCE and velocity
based Momentum equations plus passive scalar transport (not fully implemented)
=
20 Baroclinic 2DDI run using original GWCE and
Momentum equation formulations (not fully implemented)
=
21 Baroclinic 3D run using original GWCE and velocity
based Momentum equations (not fully implemented)
=
30 Baroclinic 2DDI run using original GWCE and
Momentum equation formulations plus passive scalar transport (not fully
implemented)
=
31 Baroclinic 3D run using original GWCE and velocity
based Momentum equations plus passive scalar transport (not fully implemented)
NCOR = parameter controlling whether the Coriolis parameter is constant in space and read in below
or spatially varying as computed from the y-coordinates of the nodes in the
grid (assumed to be in degrees Latitude). The grid coordinate system is
specified by the ICS parameter (see above).
=
0, to read in a spatially constant Coriolis parameter
=
1, to compute a spatially variable Coriolis parameter
NOLIBF = parameter controlling the type of bottom stress
parameterization used in a 2DDI ADCIRC run. This parameter must be specified
but is ignored in a 3D run.
= 0
linear bottom friction law. The friction coefficient (FFACTOR) is specified
below.
= 1
quadratic bottom friction law. The friction coefficient (FFACTOR) is specified
below.
= 2
hybrid nonlinear bottom friction law. In deep water, the friction coefficient
is constant and a quadratic bottom friction law results. In shallow water the
friction coefficient increases as the depth decreases (e.g. as in a
Manning-type friction law). The friction coefficient is determined as:
FFACTOR=FFACTORMIN*[1+(HBREAK/H)**FTHETA]**(FGAMMA/FTHETA).
The required parameters (FFACTORMIN, HBREAK, FTHETA, FGAMMA)
are specified below.
NOLIFA = parameter controlling the finite amplitude terms in
ADCIRC. The value of NOLIFA effects the meaning of the minimum water depth parameter
(H0) and requires the specification of additional parameters together with H0,
(see below). When the finite amplitude terms are turned on, the time derivative
portion of the advective terms should also be turned
on for proper mass conservation and consistency (i.e. when NOLIFA>0, then NOLICAT=1).
= 0
finite amplitude terms ARE NOT included in the model run (i.e., the depth is linearized by using the bathymetric depth, rather than the
total depth, in all terms except the transient term in the continuity equation)
and wetting and drying of elements is disabled. Initial water depths are
assumed equal to the bathymetric water depth specified in the grid file (fort.14).
= 1
finite amplitude terms ARE included in the model run and wetting and drying of
elements is disabled. Initial water depths are assumed equal to the bathymetric
water depth specified in the grid file (fort.14).
= 2
finite amplitude terms ARE included in the model run and wetting and drying of
elements is enabled. Initial water depths are assumed equal to the bathymetric
water depth specified in the grid file (fort.14).
= 3
finite amplitude terms ARE included in the model run and wetting and drying of
elements is enabled. Initial water depths are assumed equal to the bathymetric
water depth specified in the grid file (fort.14) unless over ridden in the Initial Water Level File. This can be used to
initialize a region as being dry that is below the Geoid,
such as an area that is protected by levees or dikes (e.g., a polder). Without
this option, this type of region would be assumed to have an initial water
level at the Geoid.
NOLICA = parameter controlling the advective
terms in ADCIRC (with the exception of a time derivative portion that occurs in
the GWCE form of the continuity equation and is controlled by NOLICAT).
When these (spatial derivative) portions of the advective
terms are included, the time derivative portion of the advective
terms in the GWCE should also be included (i.e. when NOLICA=1, NOLICAT=1).
= 0
advective terms ARE NOT included in the computations
= 1 advective terms ARE included in the computations
NOLICAT = parameter controlling the time derivative portion
of the advective terms that occurs in the GWCE form
of the continuity equation in ADCIRC. The remainder of the advective
terms in the GWCE and the entire advective terms in
the momentum equation are controlled by NOLICA. These
terms should be included if either the finite amplitude or the remainder of the
advective terms are included to maintain mass
conservation and solution consistency.
= 0
the time derivative portion of the advective terms
that occur in the GWCE continuity equation ARE NOT included in the
computations.
= 1
the time derivative portion of the advective terms
that occur in the GWCE continuity equation ARE included in the computations.
NRAMP = ramp option parameter controlling whether a ramp is
applied to ADCIRC forcing functions.
= 0
no ramp function is used with forcing functions
= 1
a hyperbolic tangent ramp function is specified and applied to forcing from
surface elevation specified boundary conditions, nonzero flux boundary
conditions, tidal potential, wind and atmospheric pressure and wave radiation
stress. See description of DRAMP for further information
on the ramp function.
NTIP = parameter controlling whether tidal potential and
self attraction/load tide forcings will be used to
force ADCIRC.
=
0, tidal potential & self attraction/load tide forcings
are not used
=
1, tidal potential forcing is used
=
2, tidal potential & self attraction/load tide forcings
are used. In this case the self attraction/load tide information is read in for
each constituent at each node in the grid from the Self Attraction/Earth Load Tide Forcing File.
NWP = parameter controlling whether the bottom friction
coefficient is constant in space or specified to be spatially varying using the
Spatially Varying Friction Coefficient File. This option works only for NOLIBF=0
or 1.
= 0 to use a spatially
constant bottom friction coefficient (FFACTOR see below)
= 1 to use a spatially
varying bottom friction coefficient.
Friction coefficients are read in at all nodes in the domain from the Spatially Varying Friction Coefficient File.
= 2 to use locally
enhanced friction to represent the effects of bridge piers at select areas in
the grid. See the section on Bridge
Piers for details of how this is implemented and the coefficients that are
required. The coefficients are read in
at specified nodes from the Spatially Varying Friction Coefficient File.
NWS = parameter controlling whether wind velocity or
stress, wave radiation stress and atmospheric pressure are used to force
ADCIRC.
=
0, no wind, radiation stress or atmospheric pressure forcings
are used.
=
1, wind stress and atmospheric pressure are read in at all grid nodes at every
model time step from the Single File Meteorological Forcing Input File.
=
2, wind stress and atmospheric pressure are read in at all grid nodes at a time
interval that does not equal the model time step from the Single
File Meteorological Forcing Input File. Interpolation in time is
used to synchronize the wind and pressure information with the model time step.
The wind time interval (WTIMINC) is specified below.
=
-2, wind stress and atmospheric pressure are read in at all grid nodes at a
time interval that does not equal the model time step from the
=
3, wind velocity is read in from a wind file from the Single
File Meteorological Forcing Input File in US Navy Fleet Numeric
format. This information is interpolated in space onto the ADCIRC grid and in
time to synchronize the wind and pressure information with the model time step.
Garret's formula is used to compute wind stress from the wind velocity. Several
parameters (IREFYR, IREFMO, IREFDAY, IREFHR, IREFMIN,
REFSEC, NWLAT, NWLON,
WLATMAX, WLONMIN, WLATINC, WLONINC, WTIMINC)
describing the Fleet Numeric wind file must be specified below.
=
4, wind velocity and atmospheric pressure are read in (PBL/JAG format) at
selected ADCIRC grid nodes from the Single
File Meteorological Forcing Input File. It is assumed that the first
entry in the Single
File Meteorological Forcing Input File corresponds to the beginning
of the model run (e.g., the cold start time). Succeeding entries occur at the
time interval (WTIMINC) specified below. Thus, if the
model is hot started wind data must exist in the fort.22 file dating back to
the beginning of the model run so that the model can find its appropriate place
in the file. Interpolation in time is used to synchronize the wind and pressure
information with the model time step. Garret's formula is used to compute wind
stress from wind velocity.
=-4,
wind velocity and atmospheric pressure are read in (PBL/JAG format) at selected
ADCIRC grid nodes from the Single
File Meteorological Forcing Input File. It is assumed that the first
entry in the Single
File Meteorological Forcing Input File corresponds to the time that
the current model run is started. Specifically, if the model is hot started, it
is assumed that first entry in the Single
File Meteorological Forcing Input File corresponds to the
model hot start time. Succeeding entries in the Single
File Meteorological Forcing Input File occur at the time
interval (WTIMINC) specified below. Interpolation in time is used to
synchronize the wind and pressure information with the model time step.
Garret's formula is used to compute wind stress from wind velocity.
=
5, wind velocity and atmospheric pressure are read in at all grid nodes from the Single
File Meteorological Forcing Input File. It is assumed that the first
entry in the Single
File Meteorological Forcing Input File corresponds to the
beginning of the model run (e.g., the cold start time). Succeeding entries
occur at the time interval (WTIMINC) specified below. Thus, if the model is hot
started wind data must exist in the Single
File Meteorological Forcing Input File dating back to the beginning
of the model run so that the model can find its appropriate place in the file.
Interpolation in time is used to synchronize the wind and pressure information
with the model time step. Garret's formula is used to compute wind stress from
wind velocity.
=-5,
wind velocity and atmospheric pressure are read in at all grid nodes from the Single
File Meteorological Forcing Input File. It is assumed that the first
entry in the Single
File Meteorological Forcing Input File corresponds to the
time that the current model run is started. Specifically, if the model is hot
started, it is assumed that first entry in the fort.22 file corresponds to the
model hot start time. Succeeding entries in the Single
File Meteorological Forcing Input File occur at the time
interval (WTIMINC) specified below. Interpolation in
time is used to synchronize the wind and pressure information with the model
time step. Garret's formula is used to compute wind stress from wind velocity.
=
6, wind velocity and atmospheric pressure are read in for a rectangular grid (either
in Longitude, Latitude or Cartesian coordinates, consistent with the grid
coordinates) from the Single
File Meteorological Forcing Input File. This information is
interpolated in space onto the ADCIRC grid and in time to synchronize the wind
and pressure information with the model time step. Garret's formula is used to
compute wind stress from the wind velocity. Several parameters describing the
rectangular grid and time increment (NWLAT, NWLON, WLATMAX, WLONMIN,
WLATINC, WLONINC, WTIMINC) must be specified below.
=10,
wind velocity (10 m) and atmospheric pressure are read in from a sequence of National
Weather Service (NWS) Aviation (AVN) model output files. Each AVN file is
assumed to contain data on a Gaussian longitude, latitude grid at a single
time. Consecutive files in the sequence are separated by N hours in time (where
N=WTIMINC/3600 and WTIMINC is
read in below). The files are named using the convention: fort.200 - wind &
pressure at the time of a model hot start (this file is not used for a cold
start); fort.XX1 (where XX1=200+1*N) - wind & pressure N hours after a cold
or hot start; fort.XX2 (where XX2=200+2*N) - wind & pressure 2N hours after
a cold or hot start; fort.XX3 (where XX3=200+3*N) - wind & pressure 3N
hours after a cold or hot start and so on for all meteorological files. Prior
to ADCIRC version 34.05 these files were in binary and created from a larger Grib form file using the program UNPKGRB1. Starting with
ADCIRC version 34.05, the files are in ASCII tabular format. If ADCIRC is hot
started, it must be done at an even N hour interval so that the hot start time
corresponds to the time of a meteorological file. Enough meteorological files
must be present to extend through the ending time of the model run. Garret's
formula is used to compute wind stress from the wind velocity.
=11,
wind velocity (10 m) and atmospheric pressure are read in from a sequence of
stripped down National Weather Service (NWS) ETA 29km model output files. Each
ETA file is assumed to contain data on an E grid for a single day (8 data sets,
one every 3 hours, beginning @
=100,
101, 102, -102, 103, 104, -104, 105, -105, 106, 110, 111, wave radiation stress
is applied in addition to meteorological forcing. The meteorological input is
specified by: SIGN(NWS)*(ABS(NWS)-100). For example, NWS=100 means
include wave radiation stress with no meteorological forcing (NWS=0); NWS=101 means include wave radiation stress plus meteorological
forcing corresponding to NWS=1; NWS=-104 means include wave radiation
stress plus meteorological forcing corresponding to NWS=-4, etc. Wave radiation stress is read from a Wave Radiation Stress Forcing File. The format of this
file is similar to the generic meteorological forcing file when NWS=-4 with the exception that no
pressure values are read in. The time increment between consecutive radiation
stress fields (RSTIMINC) is specified below.
POAN(k) =
parameter that weights bridge pier drag between adjacent and centerline nodes.
= 2
if node represents a centerline node
= 1
if node represents an adjacent node
G = gravitational constant. The units of this constant
determine the distance units that ADCIRC operates with. (ADCIRC always operates
in seconds and therefore the time units for G must be seconds.) When ICS = 2, it is required
that G = 9.81 m/sec2. Regardless of
ICS, when either NTIP = 1 or NCOR = 1, it is required that G = 9.81 m/sec2.
TAU0 = Generalized Wave-Continuity Equation (GWCE) weighting factor that weights the relative contribution of the primitive and wave portions of the GWCE.
= 0, the GWCE is a pure wave equation.
> 1, the GWCE behaves like a pure primitive continuity equation. A good rule of thumb for setting TAU0 is to set it equal to the largest value of an equivalent linear friction factor (e.g, for linear friction TAU0 = TAU; for quadratic friction TAU0 = maximum (speed*CF/depth). Typical values for TAU0 are in the range of 0.001 - 0.01.
< 0, uses a depth-dependent variable TAU0 scheme. If the depth is >=10 TAU0 is set to 0.005, if the depth is < 10, TAU0 is set to 0.020.
DTDP = ADCIRC time step ( in seconds
). Note: time in the model is computed as: TIME = STATIM*86400.+DT*IT.
STATIM = starting simulation time (in days). The first time
step computes results at: TIME = STATIM*86400+DT. A nonzero value may be useful, for example, to align model
output times with a specific time reference.
REFTIM = reference time (in days). This is used only to
compute time for the harmonic forcing and analysis terms. A nonzero value
allows equilibrium arguments to be used that have been calculated for a time
other than TIME0 = STATIM*86400. The time used for
harmonic terms is compute as: TIMEH = (STATIM-REFTIM)*86400.+ DT*IT.
WTIMINC = meteorological wind time interval
IF NWS = 1, 101, ADCIRC assumes WTIMINC = DT (model time step).
IF NWS = 2, -2, 3, 4, -4, 5, -5, 6, 102, 103, 104, -104, 105,
-105, 106, WTIMINC must be specified
in the Model Parameter and Periodic Boundary Condition File
and is the time interval (in seconds) between successive wind and pressure data
in the Single
File Meteorological Forcing Input File.
IF NWS = 10, 110, WTIMINC
must be specified in the Model Parameter and Periodic Boundary Condition File
and is the time interval (in seconds) between the Multiple File Meteorological Forcing Input Files.
IF NWS = 11, 111, ADCIRC assumes WTIMINC = 10800 (3 hrs) is the time interval between the Multiple File Meteorological Forcing Input Files.
RSTIMINC =
time interval (in seconds) between successive wave radiation stress values in
the Wave Radiation Stress Forcing File. This value must be
specified in the Model Parameter and Periodic Boundary Condition File
if the absolute value of NWS >=100.
IREFYR, IREFMO, IREFDAY, IREFHR, IREFMIN, REFSEC = starting time parameters for a
Single
File Meteorological Forcing Input File in US Navy Fleet Numeric
format (NWS = 3, 103). IREFYR
= year of the start of the simulation, IREFMO
= month of the start of the simulation, IREFDAY
= day of the start of the simulation, IREFHR
= hour of the start of the simulation, IREFMIN
= minute of the start of the simulation, REFSEC
= second of the start of the simulation. These values are used in ADCIRC to
compute WREFTIM which is the start time of the simulation in seconds since the
beginning of the calendar year. ADCIRC is configured to accept only 1 calendar
year's data, i.e., it is not possible to combine Fleet Numeric met data from
two different years into a single file and then run.
NWLAT, NWLON, WLATMAX, WLONMIN, WLATINC, WLONINC = parameters describing the spatial
structure of a Single
File Meteorological Forcing Input File where met data is set up on a
simple rectangular grid (NWS = 3, 6, 103, 106). NWLAT = number of latitude values in
the met file, NWLON = number of
longitude values in met file, WLATMAX
= maximum latitude (decimal deg) of data in met file (< 0 south of the equator),
WLONMIN = minimum longitude (decimal
deg) of data in the met file (< 0 west of Greenwich meridian), WLATINC = latitude increment (decimal
deg) of data in the met file (must be > 0), WLONINC = longitude increment (decimal deg) of data in the met file
(must be > 0).
RNDAY = length of the ADCIRC run (in decimal days)
DRAMP = value (in decimal days) used to compute the ramp
function that ramps up ADCIRC forcings from zero (if NRAMP=1). The ramp function is computed as RAMP=tanh(2.0*IT*DT/(86400.*DRAMP))
where IT = the time step number since the beginning of the model run. DRAMP is equal to the number of days
when RAMP=0.96.
A00, B00,C00 = time weighting factors (at time levels k+1, k, k-1,
respectively) in the GWCE
H0 - minimum water depth
IF NOLIFA = 0, 1, H0
= minimum bathymetric depth. All bathymetric depths in the Grid and Boundary Information File less than H0 are changed to be equal to H0.
If NOLIFA = 2, H0 =
nominal water depth for a node (and the accompanying elements) to be considered
dry (typical value 0.01 - 0.1 m).
NODEDRYMIN = minimum number of time
steps after a node dries that it must remain dry before it can wet again. This
parameter helps to keep nodes/elements from repeatedly turning on and off
during the wetting process. A typical value might be from 5 - 20.
NODEWETMIN = minimum number of time
steps after a node wets that it must remain wet before it can dry again. This
parameter helps to keep nodes/elements from repeatedly turning on and off
during the wetting process. A typical value might be from 5 - 20.
VELMIN = minimum velocity for wetting. A dry node wets if a
water surface slope exists that would drive water from a currently wet node to
the dry node and the steady-state current velocity that resulted would have a
velocity > VELMIN. This parameter
helps to keep nodes/elements from repeatedly turning on and off during the
wetting process. A typical value might be 0.05 m/s.
SLAM0,SFEA0 = longitude and latitude on
which the CPP coordinate projection is centered (in degrees) if ICS
= 2.
TAU – bottom friction is a linear function of
depth-averaged velocity and TAU is the corresponding linear friction
coefficient (units of 1/sec). In this
case it is strongly recommended that TAU0 = TAU (Used with NOLIBF = 0)
CF = 2DDI bottom friction coefficient used in ADCIRC
unless spatially varying bottom friction (NWP = 1) is
specified.
If NOLIBF
= 1, bottom friction is a quadratic function of depth-averaged velocity and FFACTOR is the corresponding quadratic
friction coefficient (dimensionless).
If NOLIBF = 2, minimum friction coefficient (dimensionless) in
the hybrid bottom friction relationship This friction coefficient is
approached in deep water (H > HBREAK) where the hybrid
friction relationship reverts to a quadratic function of depth-averaged
velocity.
HBREAK = the break depth (units of length) utilized for NOLIBF = 2 in the hybrid bottom friction relationship FFACTOR = FFACTORMIN*[1+(HBREAK/H)**FTHETA]**(FGAMMA/FTHETA). If the water depth (H)
is greater than HBREAK, bottom
friction approaches a quadratic function of depth-averaged velocity with FFACTOR = FFACTORMIN. If the
water depth is less than HBREAK, the
friction factor increases as the depth decreases (e.g. like a manning type
friction law). (HBREAK = 1 m is
recommended)
FTHETA = a parameter (dimensionless) that determines (for NOLIBF = 2) how rapidly the hybrid bottom friction
relationship approaches its deep water and shallow water limits when the water
depth is greater than or less than HBREAK. (FTHETA = 10 is recommended).
FGAMMA = a parameter (dimensionless) that determines (for NOLIBF = 2) how the friction factor increases as the water
depth decreases. Setting this to 1/3 gives a manning friction law type of
behavior (FGAMMA = 1/3 is
recommended).
ESLM = Spatially constant
horizontal eddy viscosity for the momentum equations (units of length2/time)
ESLC = Spatially constant
horizontal eddy diffusivity for the transport equation (units of
length2/time). This is only specified if IM = 10.
CORI = Constant Coriolis
coefficient. This value is always read in, however it is only used in the
computations when NCOR = 0.
NTIF = number of tidal potential constituents
TIPOTAG(I): see description of TPK(I),AMIGT(I),ETRF(I),FFT(I)
and FACET(I)
TPK(I),AMIGT(I),ETRF(I),FFT(I),FACET(I), I=1,NTIF
; tidal potential amplitude, frequency, earth tide potential reduction factor
(generally taken to be 0.690 for all constituents (Hendershott)
but for more precise calculations can take on slightly different values (e.g.
see Wahr, 1981)), nodal factor and equilibrium
argument in degrees. These values are preceded by TIPOTAG(I) which is an alphanumeric descriptor (i.e. the
constituent name)
NBFR = number of periodic forcing frequencies on elevation
specified boundaries. if NBFR=0 and
a nonzero number of elevation specified boundary segments are included in the Grid and Boundary Information File, the elevation
boundary condition is assumed to be non-periodic and will be read in from the Non-periodic Elevation Boundary Condition File. For
reasons of backward compatability, NBFR is included in the Model Parameter and Periodic Boundary Condition File
regardless of whether any elevation specified boundaries (IBTYPE=0)
are defined in the fort.14 input.
BOUNTAG(k) : see description of AMIG(k),FF(k),FACE(k)
AMIG(k),FF(k),FACE(k) k=1,NBFR
; forcing frequency, nodal factor, equilibrium argument in degrees for tidal
forcing on elevation specified boundaries. These values are preceded by BOUNTAG(k), an alphanumeric
descriptor (i.e. the constituent name)
ALPHA : see description of EMO(k,j), EFA(k,j) (<= 10 characters)
EMO(k,j),EFA(k,j)
k=1,NBFR , j=1,NETA ; amplitude and
phase (in degrees) of the harmonic forcing function at the elevation specified
boundaries for frequency k and elevation specified boundary forcing node j.
NOTE that the parameter NETA is defined and read in from Grid and Boundary Information File: the forcing values
are preceded by an alphanumeric descriptor EALPHA to
facilitate verifying that the correct data matches a given frequency
ANGINN : flow boundary nodes which are set up to have a
normal flow essential boundary condition and have an inner angle less than ANGINN (specified in degrees) will have
the tangential velocity zeroed. In either case, the normal velocity will be
determined from the essential boundary condition.
NFFR = number of frequencies in the specified normal flow
external boundary condition. If NFFR=0,
the normal flow boundary condition is assumed to be non-periodic and will be
read in from the Non-periodic, Normal Flux Boundary Condition File. NFFR is only included in the Model Parameter and Periodic Boundary Condition File if
one or more specified (non-zero) normal flow external boundaries were defined
in the Grid and Boundary Information File (IBTYPE=2,12
OR 22).
FBOUNTAG(k) : see
description of FAMIGT(k),FFF(k),FFACE(k)
FAMIGT(k),FFF(k),FFACE(k) k=1,NFFR ; forcing
frequency, nodal factor, equilibrium argument in degrees for periodic normal
flow forcing on flow boundaries. these values are
preceded by FBOUNTAG(k), an alphanumeric descriptor
(i.e. the constituent name)
ALPHA: see description of QNAM(k,j),QNPH(k,j) (<=10 characters)
QNAM(k,j) ,QNPH(k,j)
k=1,NFFR, j=1,NFLBN; amplitude and
phase (in degrees) of the periodic normal flow/unit width (e.g. m2/s) for
frequency I and "specified normal flow" boundary node j. A positive
flow/unit width is into the domain and a negative flow/unit width is out of the
domain. Note: the forcing values are preceded by an alphanumeric descriptor ALPHA to facilitate verifying that the correct data matches
a given frequency.
NOUTE, TOUTSE, TOUTFE, NSPOOLE = output
parameters which control the time series output provided for elevations solutions
at selected elevation recording stations (fort.61 output)
NOUTE =-2 Output is provided at the selected elevation recording stations in
binary format. Following a hot start, a new fort.61 file is created.
NOUTE =-1 Output is provided at the
selected elevation recording stations in standard ascii
format. Following a hot start, a new fort.61 file is created.
NOUTE = 0 No output is provided at
the selected elevation recording stations.
NOUTE = 1 Output is provided at the selected
elevation recording stations in standard ascii
format. Following a hot start, continued output is merged into the existing
fort.61 file.
NOUTE = 2 Output is provided at the
selected elevation recording stations in binary format. Following a hot start,
continued output is merged into the existing fort.61 file.
TOUTSE = the number of days after
which elevation station data is recorded to fort.61 (TOUTSE is relative to STATIM)
TOUTFE = the number of days after
which elevation station data ceases to be recorded to fort.61 (TOUTFE is relative to STATIM)
NSPOOLE = the number of time steps
at which information is written to fort.61; i.e. the output is written to
fort.61 every NSPOOLE time steps
after TOUTSE
NSTAE = the number of elevation recording stations (this is
always read in regardless of the value of NOUTE)
XEL(k),YEL(k)
k=1,NSTAE ; the coordinates of the elevation recording
station k, for all NSTAE stations.
IF ICS = 1, coordinates are input as standard cartesian
IF ICS = 2, coordinates are input as degrees longitude and
latitude
If
an elevation recording station is input which does not lie within the
computational domain, a non-fatal error message will appear. If NFOVER has been set equal to 1, the code will estimate the
nearest element and use that as the basis of interpolation. A proximity index
is also printed out, which indicates how close or far the station coordinates
are from the nearest element. This index may be interpreted as the number of
elements that the station lies from the nearest element
NOUTV,TOUTSV,TOUTFV,NSPOOLV = output
parameters which control the time series output provided for velocity solutions
at selected velocity recording stations (fort.62 output)
NOUTV =-2 Output is provided at the selected velocity recording stations in
binary format. Following a hot start, a new fort.62 file is created.
NOUTV =-1 Output is provided at the
selected velocity recording stations in standard ascii
format. Following a hot start, a new fort.62 file is created.
NOUTV = 0 No output is provided at
the selected velocity recording stations
NOUTV = 1 Output is provided at the
selected velocity recording stations in standard ascii
format. Following a hot start, continued output is merged into the existing
fort.62 file.
NOUTV = 2 Output is provided at the
selected velocity recording stations in binary format. Following a hot start,
continued output is merged into the existing fort.62 file.
TOUTSV = the number of days after
which velocity station data is recorded to fort.62 (TOUTSV is relative to STATIM)
TOUTFV = the number of days after
which velocity station data ceases to be recorded to fort.62 (TOUTFV is relative to STATIM)
NSPOOLV = the number of time steps at
which information is written to fort.62; i.e. the output is written to fort.62
every NSPOOLV time steps after TOUTSV
NSTAV = the number of velocity recording stations (this is
always read in regardless of the value of NOUTV)
XEV(k),YEV(k) k=1,NSTAV ; the coordinates of the velocity recording station k,
for all NSTAV stations
If ICS = 1, coordinates are input as standard cartesian
If ICS = 2, coordinates are input as degrees longitude and
latitude
If a velocity recording station is input which does not lie within the
computational domain, a non-fatal error message will appear. If NFOVER has been set equal to 1, the code will estimate the
nearest element and use that as the basis of interpolation. A proximity index
is also printed out, which indicates how close or far the station coordinates
are from the nearest element. This index may be interpreted as the number of
elements that the station lies from the nearest element
NOUTC,TOUTSC,TOUTFC,NSPOOLC = output
parameters which control the time series output provided for concentration
solutions at selected concentration recording stations (fort.91 output)
NOUTC =-2 Output is provided at the selected concentration recording
stations in binary format. Following a hot start, a new fort.91 file is
created.
NOUTC =-1 Output is provided at the
selected concentration recording stations in standard ascii format. Following a hot start, a new fort.91
file is created.
NOUTC = 0 no output is provided at
the selected concentration recording stations
NOUTC = 1 output is provided at the
selected concentration recording stations in standard ascii format. Following a hot start, continued output
is merged into the existing fort.91 file.
NOUTC = 2 output is provided at the
selected concentration recording stations in binary format. Following a hot
start, continued output is merged into the existing fort.91 file.
TOUTSC = the number of days after
which concentration station data is recorded to fort.91 (TOUTSC is relative to STATIM)
TOUTFC = the number of days after
which concentration station data ceases to be recorded to fort.91 (TOUTFC is relative to STATIM)
NSPOOLC = the number of time steps
at which information is written to fort.91; i.e. the output is written to
fort.91 every NSPOOLC time steps
after TOUTSC
Note: this line is only read in if transport is included in the model run (i.e.
IM=10)
NSTAC = the number of concentration recording stations
Note: this line is only read in if transport is included in the model run (i.e.
IM=10) Note: this is read in even if NOUTC=0
XEC(k),YEC(k)
k=1,NSTAC ; the coordinates of the concentration recording
station k, for all NSTAC stations.
Note:
this line is only read in if transport is included in the model run (i.e. IM=10)
Note: the coordinates must be consistent (i.e. cartesian
or spherical) with the Grid and Boundary Information File and the coordinate
designation parameter, ICS, in the Model Parameter and Periodic Boundary Condition File.
Note: If a concentration recording station is input which does not lie within
the computational domain, a non-fatal error message will appear. If NFOVER has been set equal to 1, the code will estimate the
nearest element and use that as the basis of interpolation. A proximity index
is printed out in the fort.16 file that indicates how close or far the station
coordinates are from the nearest element. This index may be interpreted as the
number of elements that the station lies from the nearest element
NOUTM,TOUTSM,TOUTFM,NSPOOLM = output
parameters which control the time series output provided for met data at
selected met recording stations (units 71&72 output)
NOUTM =-2 Output is provided at the selected met recording stations in
binary format. Following a hot start, new fort.71&72 files are created.
NOUTM =-1 Output is provided at the
selected met recording stations in standard ascii
format. Following a hot start, new fort.71&72 files are created.
NOUTM = 0 No output is provided at
the selected met recording stations.
NOUTM = 1 Output is provided at the
selected met recording stations in standard ascii
format. Following a hot start, continued output is merged into the existing
fort.71&72 files.
NOUTM = 2 Output is provided at the
selected met recording stations in binary format. Following a hot start,
continued output is merged into the existing fort.71&72 files.
TOUTSM = the number of days after
which met station data is recorded to units 71&72 (TOUTSM is relative to STATIM)
TOUTFM = the number of days after
which met station data ceases to be recorded to units 71&72 (is relative to
STATIM)
NSPOOLM = the number of time steps
at which information is written to units 71&72; i.e., output is written to
units 71&72 every NSPOOLM time
steps after TOUTSM. Note: this line
is only read in if meteorological forcing is included in the model run (i.e. NWS<>0 and NWS<>100)
NSTAM = the number of meteorological recording stations.
Note: this line is only read in if met forcing is included in the model run
(i.e. NWS<>0 and NWS<>100).
Note: this is read in even if NOUTM=0
XEM(k),YEM(k)
k=1,NSTAM ; the coordinates of the meteorological
recording station I, for all NSTAM stations.
Note:
this line is only read in if met forcing is included in the model run (i.e. NWS<>0 and NWS<>100)
Note: the coordinates must be consistent (i.e. cartesian
or spherical) with the Grid and Boundary Information File and the coordinate
designation parameter, ICS, in the Model Parameter and Periodic Boundary Condition File.
Note: if a meteorological recording station is input which does not lie within
the computational domain, a non-fatal error message will appear. If NFOVER has been set equal to 1, the code will estimate the
nearest element and use that as the basis of interpolation. A proximity index
is printed out in the fort.16 file that indicates how close or far the station
coordinates are from the nearest element. This index may be interpreted as the
number of elements that the station lies from the nearest element
NOUTGE,TOUTSGE,TOUTFGE,NSPOOLGE=output
parameters which control the time series output provided for global elevation
solutions at all nodes within the domain (fort.63 output)
NOUTGE =-2 Global elevation output is provided in binary format. Following a
hot start, a new fort.63 file is created.
NOUTGE =-1 Global elevation output
is provided in standard ascii format. Following a hot
start, a new fort.63 file is created.
NOUTGE = 0 No global elevation
output is provided
NOUTGE = 1 Global elevation output
is provided in standard ascii format. Following a hot
start, continued output is merged into the existing fort.63 file.
NOUTGE = 2 Global elevation output
is provided in binary format. Following a hot start, continued output is merged
into the existing fort.63 file.
TOUTSGE = the number of days after
which global elevation data is recorded to fort.63 (TOUTSGE is relative to STATIM)
TOUTFGE = the number of days after
which global elevation data ceases to be recorded to fort.63 (TOUTFGE is relative to STATIM)
NSPOOLGE = the number of time steps
at which information is written to fort.63; i.e. the output is written to
fort.63 every NSPOOLGE time steps
after TOUTFGE
NOUTGV,TOUTSGV,TOUTFGV,NSPOOLGV=output
parameters which control the time series output provided for global velocity
solutions at all nodes within the domain (fort.64 output)
NOUTGV =-2 Global velocity output is provided in binary format. Following a
hot start, a new fort.64 file is created.
NOUTGV =-1 Global velocity output is
provided in standard ascii format. Following a hot
start, a new fort.64 file is created.
NOUTGV = 0 No global velocity output
is provided
NOUTGV = 1 Global velocity output is
provided in standard ascii format. Following a hot
start, continued output is merged into the existing fort.64 file.
NOUTGV = 2 Global velocity output is
provided in binary format. Following a hot start, continued output is merged
into the existing fort.64 file.
TOUTSGV = the number of days after
which global velocity data is recorded to fort.64 (TOUTSGV is relative to STATIM)
TOUTFGV = the number of days after
which global velocity data ceases to be recorded to fort.64 (TOUTFGV is relative to STATIM)
NSPOOLGV = the number of time steps
at which information is written to fort.64; i.e. the output is written to
fort.64 every NSPOOLGV time steps
after TOUTFGV
NOUTGC,TOUTSGC,TOUTFGC,NSPOOLGC = output parameters
which control the time series output provided for global concentration
solutions at all nodes within the domain (fort.93 output)
NOUTGC =-2 Global concentration output is provided in binary format.
Following a hot start, a new fort.93 file is created.
NOUTGC =-1 Global concentration
output is provided in standard ascii format.
Following a hot start, a new fort.93 file is created.
NOUTGC = 0 No global concentration
output is provided
NOUTGC = 1 Global concentration
output is provided in standard ascii
format. Following a hot start, continued output is merged into the existing
fort.93 file.
NOUTGC = 2 Global concentration
output is provided in binary format. Following a hot start, continued output is
merged into the existing fort. 93 file.
TOUTSGC = the number of days after
which global concentration data is recorded to fort.93 (TOUTSGC is relative to STATIM)
TOUTFGC = the number of days after
which global concentration data ceases to be recorded to fort.93 (TOUTFGC is relative to STATIM)
NSPOOLGC = the number of time steps
at which information is written to fort.93; i.e. the output is written to
fort.93 every NSPOOLGC time steps
after TOUTFGC
Note: this line is only read in if transport is included in the model run (i.e.
IM=10)
NOUTGW, TOUTSGW,
TOUTFGW, NSPOOLGW
= output parameters which control the time series output provided for wind stress
or velocity and atmospheric pressure at all nodes within the domain (fort.73
and 74 output)
NOUTGW =-2 Global wind stress/velocity and atmospheric pressure outputs are
provided in binary format. Following a hot start, new fort.73 and 74 files are
created.
NOUTGW =-1 Global wind
stress/velocity and atmospheric pressure outputs are provided in standard ascii format. Following a hot
start, new fort.73 and 74 files. are created.
NOUTGW = 0 no global wind
stress/velocity or atmospheric pressure output is provided
NOUTGW = 1 Global wind
stress/velocity and atmospheric pressure output are provided in standard ascii format. Following a hot
start, continued output is merged into the existing fort.73 and 74 files.
NOUTGW = 2 Global wind
stress/velocity and atmospheric pressure output are provided in binary format.
Following a hot start, continued output is merged into the existing fort.73 and
74 files.
TOUTSGW = the number of days after
which global wind stress/velocity and atmospheric pressure data are recorded to
units 73,74 (TOUTSGM is relative to STATIM)
TOUTFGW = the number of days after
which global wind stress/velocity and atmospheric pressure data cease to be
recorded to units 73,74 (TOUTFGM is
relative to STATIM)
NSPOOLGW = the number of time steps
at which information is written to units 73,74; i.e. the output is written to
units 73,74 every NSPOOLGM time
steps after TOUTSGM
Note: this line is only read in if meteorological forcing is included in the
model run (i.e. NWS<>0 and NWS<>100)
NFREQ = number of frequencies included in harmonic analysis
of model results. Note: harmonic output is only available for 2DDI elevation
and velocity
NAMEFR(k) : an alphanumeric descriptor (i.e. the constituent
name) whose length must be <= 16 characters
HAFREQ(k),HAFF(k),HAFACE(k) k=1,NFREQ = parameters describing the
constituents to be included in the harmonic analysis of model results
HAFREQ(k) = frequency (rad/s)
HAFF(k) = nodal factor
HAFACE(k) = equilibrium argument
(degrees)
Note: these values are preceded by FNAME,
Note: if a steady component will be included in the harmonic analysis, this
must be the first constituent listed (i.e., the constituent corresponding to
k=1)
THAS,THAF,NHAINC,FMV = parameters that control the
calculation of harmonic constituents both at stations and globally
THAS = the number of days after which data starts to be harmonically analysed (THAS
is relative to STATIM)
THAF = the number of days after
which data ceases to be harmonically analysed (THAF is relative to STATIM)
NHAINC = the number of time steps at
which information is harmonically analysed
(information every NHAINC time steps
after THAS is used in harmonic
analysis)
FMV = fraction of the harmonic
analysis period (extending back from the end of the harmonic analysis period)
to use for comparing the water elevation and velocity means and variances from
the raw model time series with corresponding means and variances of a time
series resynthesized from the harmonic constituents.
this comparison is helpful for identifying numerical instabilities and for
determining how complete the harmonic analysis was. Examples:
FMV = 0. - do not compute any means
and vars.
FMV = 0.1 - compute means and vars.
over final 10% of period used in harmonic analysis
FMV = 1.0 - compute means and vars.
over entire period used in harmonic analysis
Note: the means and variance calculations are only done if global harmonic
calculations are performed. Results are written out to fort.55. A summary of
the poorest comparisons throughout the domain and the node numbers where these
occurred is given at the end of the fort.16 output file.
Note: the time series resysthesis from the harmonic
constituents can use up a lot of CPU time since this is done for every time
step during the specified part of the harmonic analysis period. If the harmonic
analysis period extends for only a few days, it is practical to set FMV=1. Otherwise, it becomes
unreasonably time consuming to compute means and variances for more than 10-20
days. Ultimately, the practical limit to these calculations depends on the
number of nodes, the number of constituents in the harmonic analysis, and the
size of the time step.
NHASE. NHASV, NHAGE, NHAGV =
parameters that control the spatial locations where harmonic analysis is
performed
NHASE = 0 no harmonic analysis is performed at the selected elevation
recording stations
NHASE = 1 harmonic analysis is
performed at the selected elevation recording stations (output on fort.51)
Note: the stations are as specified in the section on time series station
elevation output
NHASV = 0 no harmonic analysis is
performed at the selected velocity recording stations
NHASV = 1 harmonic analysis is
performed at the selected velocity recording stations (output on fort.52) Note:
the stations are as specified in the section on time series station velocity
output
NHAGE = 0 no harmonic analysis is
performed for global elevations
NHAGE = 1 harmonic analysis is
performed for global elevations (output on fort.53)
NHAGV = 0 no harmonic analysis is
performed for global velocities
NHAGV = 1 harmonic analysis is
performed for global velocities (output on fort.54)
NHSTAR,NHSINC
= parameters that control the generation of hot start output.
NHSTAR = 0 no hot start output files generated
NHSTAR = 1 hot start output files
generated
NHSINC = the number of time steps at
which hot start output file is generated (hot start file is generated every NHSINC time steps)
ITITER,ISLDIA,CONVCR,ITMAX = parameters
that provide information about the solver that will be used for the GWCE.
ITITER = -1 only for lumped, explicit GWCE, matrix is diagonal and no external
solver is needed
ITITER = 1 use iterative JCG solver
(from ITPACKV 2D)
ISLDIA = 0 fatal error messgs only from ITPACKV 2D(fort.33)
ISLDIA = 1 warning messgs and minimum output from ITPACKV 2D (fort.33)
ISLDIA = 2 reasonable summary of
algorithm progress from ITPACKV 2D (fort.33)
ISLDIA = 3 parameter values and
informative comments from ITPACKV 2D (fort.33)
ISLDIA = 4 approximate solution
after each iteration from ITPACKV 2D (fort.33)
ISLDIA = 5 original system from
ITPACKV 2D (fort.33)
CONVCR = absolute convergence
criteria (should be no smaller than 500 times the machine precision)
ITMAX = maximum number of iterations
each time step
Note: all of the parameters must be input regardless of whether a diagonal or
iterative solver is selected. However, ISLDIA,
CONVCR and ITMAX are only used with the iterative solvers
Note: we typically use CONVCR=1E-6
on the CRAY and CONVCR=1E-5 on a 32
bit machine. After the first few time steps, the solutions usually converge
within 5-10 iterations.
IDEN = form of density
forcing in the 2DDI or 3D run (for all baroclinic
model runs, the initial density, temperature and/or salinity field is read in
from UNIT 11)
IDEN =0 barotropic
model run
=1 prognostic baroclinic
model run, density forcing
=2 prognostic baroclinic
model run, salinity forcing (not presently operational)
=3 prognostic baroclinic
model run, temperature forcing (not presently operational)
=4 prognostic baroclinic
model run, salinity and temperature forcing (not presently operational)
=-1
diagnostic baroclinic model run, density forcing
=-2
diagnostic baroclinic model run, salinity forcing
(not presently operational)
=-3
diagnostic baroclinic model run, temperature forcing
(not presently operational)
=-4
diagnostic baroclinic model run, salinity and
temperature forcing (not presently operational)
KP = 3D bottom friction coefficient used in ADCIRC
If
If
If
Z0S,Z0B = free surface
& bottom roughnesses (constant over horizontal)
if the turbulent length scale is determined by q2l eqn and a slip coefficient is used, this should be the
thickness of the constant stress layer (e.g., 1 m) above the surface boundary
node and below the bottom boundary node.
ALP1,ALP2,ALP3 = time
weighting coefficients for the 3D velocity solution.
0.= fully explicit, 0.5=time centered, 1.= fully
implicit
ALP1 weights the Coriolis term
ALP2 weights the bottom friction terms
ALP3 weights the vertical diffusion terms
IGC,NFEN = vertical grid code, # nodes in the vertical grid
IGC = 0,
vertical grid read in
IGC = 1,
uniform vertical grid generated
IGC = 2,
log vertical grid generated
IGC = 3,
log linear vertical grid generated
IGC = 4,
double log vertical grid generated
IGC = 5,
P-grid generated
IGC = 6,
sine grid generated
IEVC, EVMIN, EVCON = vertical
eddy viscosity code, vertical eddy viscosity minimum value and vertical eddy
viscosity constant
NOTE: EVCON
is only used for some of the vertical eddy viscosity formulations as discussed
below.
NOTE: In cases where vertical eddy viscosity is
specified to vary linearly over the lower 20% of the water column, it actually
varies linearly with a constant slope up to the vertical FE grid node that is
less than or equal to the 20% location.
The value is constant as specified at all FE grid nodes above the 20%
location. The vertical eddy viscosity
above and below the 20% level is joined by one additional linearly varying
segment.
NOTE: The vertical eddy viscosity is constrained to
always be greater than or equal to EVMIN.
IEVC = 0-9,
EV constant in time & horizontal space
0 - vertical eddy viscosity read in - EVCON is not used
1 - EV = EVCON
IEVC =10-19
vertical eddy viscosity proportional to omega*h*h (Lynch and Officer (1986)
Lynch and Werner (1987, 1991))
10 - EV = omega*h*h/10 over the entire water
column
11 - EV = omega*h*h/1000 at bottom varies linear over
lower 20% of water column
=
omega*h*h/10 in upper 80% of water column
NOTE:For
this vertical eddy viscosity formulation, EVCON
is not used and omega is hardwired for a 12.42 hour tide.
IEVC =20-29
EV proportional to kappa U* z
20 - EV = 0.41U*Zo at
bottom
=
0.41U*Z over entire water column
21 - EV = 0.41U*Zo at bottom
=
0.41U*Z in lower 20% of water column
=
0.082U*h in upper 80% of water column
WHERE: U* is the friction velocity
NOTE: For this EV formulation, EVCON is not used.
IEVC
=30-39, EV proportional to Uh (Davies 1990)
30 - EV = 0.025|U|h/9.001 over entire water column
31 - EV = EVCON
|U|h over entire water column
32 - EV = 0.025|U|h/9.001 in upper 80% of water column
=
0.000025h|U|/9.001 at bottom
varies linear over lower 20% of water column
33 - EV = EVCON
|U|h in upper 80% of water column
= EVCON |U|h/1000. at bottom varies
linear over lower 20% of water column
WHERE: U is depth averaged velocity
NOTE: For this vertical eddy viscosity formulation, EVCON is used only for IEVC =31,33
IEVC
=40-49, EV proportional to U*U (Davies 1990)
40 - EV = 2|UU|/9.001 over entire water column
41 - EV = EVCON
|UU| over entire water column
42 - EV = 2|UU|/9.001 in upper 80% of water
column
=
0.002|UU|/9.001 at bottom varies linear over lower 20% of water column
43 - EV = EVCON
|UU| in upper 80% of water column
= EVCON |UU|/1000. at bottom varies
linear over lower 20% of water column
WHERE: U is depth averaged velocity
NOTE: For this EV formulation, EVCON is used only for IEVC=41,43
IEVC =50,
EV computed from Mellor-Yamada L2.5 closure
NOTE: For this EV formulation, EVCON is not used.
EVTOT(K) - eddy viscosity associated with vertical grid
node K
THETA1, THETA2 - time
weighting coefficients for the MY2.5 turbulence soln.
(include this line only if IEVC = 50)
0.= fully explicit, 0.5=time centered, 1.= fully
implicit
THETA1 weights the dissipation term
THETA2 weights the vertical diffusion term
I3DSD,TO3DSDS,TO3DSDF,NSPO3DSD
I3DSD = 0 no station 3D temperature, salinity and/or
density info is output to unit 41
= 1 station 3D temperature, salinity and/or density
info is output in ascii format
= 2 station 3D temperature, salinity and/or density
info is output in binary format
TO3DSDS = the number of days after which station 3D temperature, salinity and/or density are written to unit 41.
TO3DSDF = the number of days after which station 3D temperature, salinity and/or density cease to be written to
unit 41.
NSPO3DSD = the number of time steps at which data is written
to unit 41. (i.e., data is output to
unit 41 every NSPO3DSD time steps
after TO3DSSD.)
NSTA3DD
= number of 3D density stations
X3DS(k), Y3DS(k) - the coordinates of the 3D temperature,
salinity, and/or density recording station k, for all NSTA3DD,
NSTA3DV or NSTA3DT stations (only
include this line if I3DSD,
I3DSV or I3DST is not = 0)
I3DSV,TO3DSVS,TO3DSVF,NSPO3DSV
I3DSV = 0 no station 3D velocities are output to unit
42
=
1 station 3D velocities are output in ascii format
=
2 station 3D velocities are output in
binary format
TO3DSVS = the number of
days after which station 3 D velocities are written to unit 42.
TO3DFVF = the number
of days after which station 3 D velocities cease to be written to unit 42.
NSPO3DSV = the number
of time steps at which data is written to unit 42. (i.e., data is output to unit 42 every NSPO3DSV time steps after TO3DSSV.)
NSTA3DV – number of 3D velocity stations
I3DST,TO3DSTS,TO3DSTF,NSPO3DST
I3DST = 0 no station 3D turbulence variables output to
unit 43
= 1 station 3D turbulence variables output in ascii format
= 2 station 3D turbulence variables output in binary
format
TO3DSTS = the number
of days after which station 3D turbulence variables are written to unit 43.
TO3DSTF = the number
of days after which station 3D turbulence variables cease to be written to unit
43.
NSPO3DST = the number of time steps at which data is written
to unit 43. (i.e., data is output to
unit 43 every NSPO3DSV time steps
after TO3DSSV.)
NSTA3DT – number of 3D turbulence stations
I3DGD,TO3DGDS,TO3DGDF,NSPO3DGD
I3DGD = 0 no global 3D temperature, salinity, and/or
density info is output to unit 44
= 1 global 3D
temperature, salinity, and/or density info is output in ascii
format
= 2 global 3D
temperature, salinity, and/or density info is output in binary format
TO3DGDS = the number
of days after which global 3D temperature, salinity, and/or density are written
to unit 44.
TO3DGDF = the number
of days after which global 3D temperature, salinity, and/or density cease to be
written to unit 44.
NSPO3DGD = the number
of time steps at which data is written to unit 44. (i.e., data is output to unit 44 every NSPO3DGD time steps after TO3DSGD.)
I3DGV,TO3DGVS,TO3DGVF,NSPO3DGV
I3DGV = 0 no global 3D velocities are output to unit 45
= 1
global 3D velocities are output in ascii format
=
2 global 3D velocities are output in binary format
TO3DGVS = the number
of days after which global 3D velocity data is written to unit 45.
TO3DGVF = the number
of days after which global 3D velocity data ceases to be written to unit 45.
NSPO3DGV = the number
of time steps at which data is written to unit 45. (i.e., data is output to unit 45 every NSPO3DGV time steps after TO3DSGV.)
I3DGT,TO3DGTS,TO3DGTF,NSPO3DGT
I3DGT = 0 no global 3D turbulence variables output to unit 46
= 1 global 3D turbulence variables output in ascii format
= 2 global 3D turbulence variables output in binary
format
TO3DGTS = the number
of days after which global 3D turbulence variables are written to unit 46.
TO3DGTF = the number
of days after which global 3D turbulence variables cease to be written to unit
46.
NSPO3DGT = the number
of time steps at which data is written to unit 46. (i.e., data is output to unit 46 every NSPO3DGT time steps after TO3DSGT.)
Variable Definitions
(fort.12):
AGRID2 =
alphanumeric file identification (<=24 characters). To facilitate
organization of files for individual model runs, it is suggested that AGRID2 match AGRID
in the Grid and Boundary Information File.
STARTDRY(JN) = start dry code; STARTDRY = -88888 at nodes which will
be initialized as dry. It can have any value at other nodes.
Variable Definitions
(fort.10):
DACONC
- generic passive scalar 2D depth-averaged
concentration field
CONC
- generic passive scalar 3D concentration field
Variable Definitions
(fort.11):
NVN - number of
nodes in vertical, must match NFEN
NVP = number of
nodes in the horizontal grid, must match NP
NHNN - horizontal
node number
NVNN - vertical
node number
DASIGT – Sigma T value (kg/m^3) (=density-1000) for a 2DDI
run
DATEMP – Temperature (DEG C) for a 2DDI run
DASALT – Salinity (PSU) for a 2DDI run
SIGT(NHNN,NVNN) - Sigma T value (kg/m^3) (=density-1000)
TEMP(NHNN,NVNN) - Temperature
(DEG C)
SAL(NHNN,NVNN) - Salinity (PSU)
SIGMA(K) =
dimensionless level of the vertical grid node K from -1 (bottom) to +1
(surface)
Variable Definitions
(fort.19):
ESBIN(k) = elevation (referenced to the geoid)
at specified elevation node k. The sequencing is assumed to match what is
defined in the elevation specified boundary condition part of the Grid and Boundary Information File.
ETIMINC = time increment (secs)
between consecutive sets of elevation specified boundary condition values
contained in this file.
Variable
Definitions(fort.20):
FTIMINC = time increment (secs)
between consecutive sets of normal flow boundary condition values contained in
this file.
NFLBN= Total number of flow boundary nodes
QNIN(k) = normal flow/unit width (e.g., m2/s) at specified
normal flow node k. A positive flow/unit width is into the domain and a
negative flow/unit width is out of the domain. The sequencing is assumed to
match what is defined in the part of the Grid and Boundary Information File specifying non zero normal flow boundaries.
Variable
Definitions(fort.21):
AFRIC = alpahanumeric friction
file ID (<= 24 characters)
FRIC(k) = nodal bottom friction coefficient.
Variable
Definitions(fort.22):
IWTIME = (if NWS =3, 103) time of the
wind field in the following integer format:
YEAR*1000000 + MONTH*10000 + DAY*100 + HR
PRN = applied
atmospheric pressure at the free surface. Units depend on the specific type of
wind input file.
WDIR =
(if NWS = 3, 103) direction wind blows from in deg cw from north
WSPEED = (if NWS =3, 103) wind speed in
m/s
WSX, WSY =
applied horizontal wind stress in the x,y directions
divided by the reference density of water (should be units (length/time)2). An
oceanographic convention is used where velocity is positive when it is blowing
toward positive coordinate directions.
WVX, WVY =
applied horizontal wind velocity in the x,y
directions. An oceanographic convention is used where velocity is positive when
it is blowing toward positive coordinate directions. Units depend on the
specific type of wind input file.
WVNX, WVNY =
(if NWS = 4, -4, 104, -104) applied horizontal wind velocity
in the x,y directions. An
oceanographic convention is used where velocity is positive when it is blowing
toward positive coordinate directions. Units are knots.
WVXFN, WVYFN
= (if NWS = 6, 106) applied horizontal wind velocity in the x,y directions. An oceanographic
convention is used where velocity is positive when it is blowing toward
positive coordinate directions. Units are assumed to be m/s
LONB, LATG =
(if NWS = 10) – number of longitude and latitudes in a global Gaussian Lon/Lat
grid (NWS = 10) or ETA-29 grid (NWS =
11), these are specified in the ADCIRC program.
PG = (if NWS = 10) – surface pressure
in m H20.
UG = (if NWS = 10) – 10 meter U velocity in m/s.
VG = (if NWS = 10) – 10 meter V velocity in m/s.
PE = (if NWS = 11) – surface pressure in mbars.
UE = (if NWS = 11) –10 meter U velocity in m/s.
VE = (if NWS = 11) – 10 meter V velocity in m/s
Variable
Definitions(fort.23):
RSX, RSY =
applied wave radiation stress in the x,y directions
divided by the reference density of water (should be units (length/time)2). An
oceanographic convention is used where stress is positive when it is pointed in
positive coordinate directions.
Variable Definitions
(fort.24)
SALTAMP(k,JN) = amplitude of the self attraction/earth tide loading
forcing for constituent k and node number JN. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, amplitude is in m, if gravity is in ft/s2, amplitude is in ft.). If ICS=2, gravity must be specified in m/s2 and the amplitude is in m.
SALTPHA(k,JN) = phase
(degrees) of the self attraction/earth tide loading forcing for constituent k
and node number JN.
Output file variable
definitions:
Variable Definitions
(fort.51,52,53,54)
EMAG(j,k) -
Elevation amplitude for constituent k at station j. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, amplitude is in m, if gravity is in ft/s2, amplitude is in ft.). If ICS=2, gravity must be specified in m/s2 and the amplitude is in m. This
quantity is computed by the harmonic analysis routines in ADCIRC.
PHASEDE(j,k) -
Elevation phase (in deg) for constituent k at node or station j. This quantity is computed by the harmonic
analysis routines in ADCIRC.
EMAGT(j,k) -
Elevation amplitude for constituent k at node j. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, amplitude is in m, if gravity is in ft/s2, amplitude is in ft.). If ICS=2, gravity must be specified in m/s2 and the amplitude is in m. This quantity
is computed by the harmonic analysis routines in ADCIRC.
UMAG(j,k) - X
direction velocity amplitude for constituent k at station j. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, amplitude is in m, if gravity is in ft/s2, amplitude is in ft.). If ICS=2, gravity must be specified in m/s2 and the amplitude is in m. This quantity is computed by the harmonic analysis routines in ADCIRC.
PHASEDU(j,k) - X -
direction velocity phase (in deg) for constituent k at node
or station j. This quantity is
computed by the harmonic analysis routines in ADCIRC.
VMAG(j,k) - Y
direction velocity amplitude for constituent k at station j. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, amplitude is in m, if gravity is in ft/s2, amplitude is in ft.). If ICS=2, gravity must be specified in m/s2 and the amplitude is in m. This quantity is computed by the harmonic analysis routines in ADCIRC.
PHASEDV(j,k) - Y -
direction velocity phase (in deg) for constituent k at node or station j. This quantity is computed by the harmonic
analysis routines in ADCIRC.
UMAGT(j,k) - X
direction velocity amplitude for constituent k at node or station j. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, amplitude is in m, if gravity is in ft/s2, amplitude is in ft.). If ICS=2, gravity must be specified in m/s2 and the amplitude is in m. This quantity is computed by the harmonic analysis routines in ADCIRC.
VMAGT(j,k) - Y direction
velocity amplitude (in units of distance consistent with gravity) for
constituent k at node or station j. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, amplitude is in m, if gravity is in ft/s2, amplitude is in ft.). If ICS=2, gravity must be specified in m/s2 and the amplitude is in m. This
quantity is computed by the harmonic analysis routines in ADCIRC.
Variable Definitions(fort.55):
EAV(J) - mean elevation in the resynthesized
time series
ESQ(J) - elevation variance in the resynthesized
time series
UAV(J) - mean x-velocity in the resynthesized
time series
USQ(J) - x-velocity variance in the resynthesized
time series
VAV(J) - mean y-velocity in the resynthesized
time series
VSQ(J) - y-velocity variance in the resynthesized
time series
Variable Definitions
(fort.61,62,63,64,71,72,73,74,81,82):
TIME - model time (in seconds) (TIME = STATIM*86400 + IT*DT)
IRTYPE = the record type (= 1 for elevation files, = 2 for
velocity files, and = 3 for 3D velocity file)
NDSETSE = the number of data sets to be written to fort.63
NDSETSV = the number of data sets to be written to fort.64
NDSETSW - the number of data sets to be spooled to fort.73
& 74
NDSETSC = the number of data sets to be spooled to fort.83
NTRSPE = the number of data sets to be written to fort.61
NTRSPV = the number of data sets to be written to fort.62
NTRSPM = the number of data sets to be spooled to fort.71 or
fort.72
NTRSPC = the number
of data sets to be spooled to fort.81
ET00(k) = surface elevation at NSTAE
elevation recording stations. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, elevation is in m, if gravity is in ft/s2, elevation is in ft.). If ICS=2, gravity must be specified in m/s2 and the elevation is in m.
ETA2(k) -
surface elevation at node k at the current time step. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, elevation is in m, if gravity is in ft/s2, elevation is in ft.). If ICS=2, gravity must be specified in m/s2 and the elevation is in m.
UU00(k), VV00(k) = x, y velocity at NSTAV
velocity recording stations. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, velocity is m/s, if gravity is in ft/s2, velocity is in ft/s). If ICS=2, gravity must be specified in m/s2 and the velocity units are m/s.
UU(k), VV2(k) - depth-averaged velocity in the x,y -coordinate direction at node k at the current time
step. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, velocity is m/s, if gravity is in ft/s2, velocity is in ft/s). If ICS=2, gravity must be specified in m/s2 and the velocity units are m/s.
RMP00(k) - atmospheric surface pressure (m of water) output at
NSTAM meteorological recording stations.
RMU00, RMV00(k) = x,y wind stress (NWS =1, 2, -2) or velocity (NWS = 3, 4, -4,
5, -5, 6, 10, 11) at NSTAM meteorological recording
stations. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, velocity is m/s, if gravity is in ft/s2, velocity is in ft/s). If ICS=2, gravity must be specified in m/s2 and the velocity units are m/s.
CC00(k) - scalar concentration at NSTAC concentration
recording stations.
PR2(k) - atmospheric surface pressure (m of water) output
for all nodes in the domain.
WVNXOUT(k),
WVNYOUT(k) = x,y
wind stress (NWS =1, 2, -2) or velocity (NWS
= 3, 4, -4, 5, -5, 6, 10, 11) for all nodes in the domain. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, velocity is m/s, if gravity is in ft/s2, velocity is in ft/s). If ICS=2, gravity must be specified in m/s2 and the velocity units are m/s.
C1(k) =
scalar concentration output for all nodes in domain
Hot Start Files (fort.67, 68)
IT - model time step number since the beginning of the
model run.
ETA1(k) - surface elevation at node k at the previous time
step
ICSTP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Scalar Concentration Time Series at Specified
Concentration Recording Stations output file.
IESTP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Elevation Time Series at Specified Elevation Recording
Stations output file.
IPSTP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Atmospheric Pressure Time Series at Specified
Meteorological Recording Stations output file.
IVSTP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Depth-averaged Velocity Time Series at Specified Velocity
Recording Stations output file.
IWSTP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Wind Velocity Time Series at Specified Meteorological
Recording Stations output file.
IGCP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Scalar Concentration Time Series at All Nodes in the Model
Grid output file.
IGEP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Elevation Time Series at All Nodes in the Model Grid
output file.
IGPP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Atmospheric Pressure Time Series at All Nodes in the Model
Grid output file.
IGVP - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the Depth-averaged Velocity Time Series at All Nodes in the
Model Grid output file.
IGWP - line number (for ASCII output) or record number (for
binary output) of the most recent entry in the Wind Stress or Velocity Time Series at All Nodes in the
Model Grid output file.
NODECODE(k) - node code at node k
indicating whether the node is presently wet (active) or dry (inactive)
NOFF – Element based wetting/drying flag.
EP – Scaling parameter that is used to maximize the
diagonal dominance of the GWCE system matrix.
It is computed within ADCIRC at a cold start or when the GWCE matrix
changes (e.g., wetting and drying has occurred).
NSCOUC - time step counter to determine when the next entry
will be written to the Scalar Concentration
Time Series at Specified Concentration Recording Stations output file.
NSCOUE - time step counter to determine when the next entry
will be written to the Elevation Time Series at Specified Elevation Recording
Stations output file.
NSCOUM - time step counter to determine when the next entry
will be written to the Atmospheric Pressure Time Series at Specified
Meteorological Recording Stations and Wind Velocity Time Series at Specified Meteorological
Recording Stations output files.
NSCOUV - time step counter to determine when the next entry
will be written to the Depth-averaged Velocity Time Series at Specified Velocity
Recording Stations output file.
NSCOUGC - time step counter to determine when the next entry
will be written to the Scalar Concentration Time Series at All Nodes in the Model
Grid output file.
NSCOUGE - time step counter to determine when the next entry
will be written to the Elevation Time Series at All Nodes in the Model Grid
output file.
NSCOUGW - time step counter to determine when the next entry
will be written to the Atmospheric Pressure Time Series at All Nodes in the Model
Grid and Wind Stress or Velocity Time Series at All Nodes in the
Model Grid output files.
NSCOUGV - time step counter to determine when the next entry
will be written to the Depth-averaged Velocity Time Series at All Nodes in the
Model Grid output file.
N3DSD - time step counter to determine when the next entry will be written to
the 3D Density, Temperature
and/or Salinity at Specified Recording Stations (fort.41) output
file.
I3DSDRec - line number (for ASCII output) or record number (for binary output) of the most recent entry in the 3D Density, Temperature and/or Salinity at Specified Recording Stations (fort.41) output file.
N3DSV - time step counter to determine when the next entry
will be written to the 3D Velocity at Specified Recording Stations (fort.42)
output file.
I3DSVRec - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the 3D Velocity at Specified Recording Stations (fort.42)
output file.
N3DST - time step counter to determine when the next entry
will be written to the 3D Turbulence at Specified Recording Stations (fort.43)
output file.
I3DSTRec - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the 3D Turbulence at Specified Recording Stations (fort.43)
output file.
N3DGD - time step counter to determine when the next entry
will be written to the 3D Density, Temperature and/or Salinity at All Nodes in
the Model Grid (fort.44) output file.
I3DGDRec - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the 3D Density, Temperature and/or Salinity at All Nodes in
the Model Grid (fort.44) output file.
N3DGV - time step counter to determine when the next entry
will be written to the 3D Velocity at All Nodes in the Model Grid (fort.45)
output file.
I3DGVRec - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the 3D Velocity at All Nodes in the Model Grid (fort.45)
output file.
N3DGT - time step counter to determine when the next entry
will be written to the 3D Turbulence at All Nodes in the Model Grid (fort.46)
output file.
I3DGTRec - line number (for ASCII output) or record number
(for binary output) of the most recent entry in the 3D Turbulence at All Nodes in the Model Grid (fort.46)
output file.
DUU(k), DUV(k), DVV(k) – Dispersion terms
UU(k), VV(k) – depth-averaged horizontal
velocity
BSX(k),
BSY(k) – x, y bottom stresses
VIDBCPDX(k), VIDBCPDY(k) –
vertically integrated baroclinic pressure
REAL(Q(k,j)) – u velocity component
AIMAG(Q(k,j)) – v velocity component
Q20(k,j) – previous time step value of Q2
HA(k,j) - coefficients
in the least squares matrix used for the harmonic analysis
CH1(k) - depth-averaged scalar concentration value at node k
at the current time step
ELAV(k) - sum of
elevations computed by ADCIRC, at every node k in the model grid, over all time
steps since harmonic analysis means and variance checking has begun
ELVA(k) - sum of squares of elevations computed by ADCIRC, at
every node k in the model grid, over all time steps since harmonic analysis
means and variance checking has begun
FNAM8(1) – the first
8 characters of FNAME(k)
FNAM8(2) – the
second 8 characters of FNAME(k)
GLOELV(k,j) - harmonic analysis load vectors for elevation at all
nodes in the model grid
GLOULV(k,j) - harmonic
analysis load vectors for depth-averaged u velocity at all nodes in the model
grid
GLOVLV(k,j) - harmonic
analysis load vectors for depth-averaged v velocity at all nodes in the model
grid
ICALL - number of times the harmonic analysis has been
updated
ICHA - time step counter to determine when the next update
will be made to the harmonic analysis.
IHARIND - indicator of whether any harmonic analysis will be
performed during the model run.
ITUD - model time step when the harmonic analysis was last
updated
MM = 2*NFREQ - NF
NF - indicator of whether the steady frequency is
included in the harmonic analysis (NF = 1, steady is included; NF = 0, steady
is not included).
NTSTEPS - number of time steps since harmonic analysis means
and variance checking has begun
NZ - indicator of whether the steady frequency is
included in the harmonic analysis (NZ = 0, steady is included; NZ = 1, steady
is not included).
STAELV(j,k) - harmonic analysis load vectors for elevation at
elevation recording stations
STAULV(j,k) - harmonic analysis load vectors for depth-averaged u
velocity at velocity recording stations
STAVLV(j,k) - harmonic analysis load vectors for depth-averaged v
velocity at velocity recording stations
TIMEUD - model time when the harmonic analysis was last
updated
XVELAV(k) - sum of
depth-averaged u velocities computed by ADCIRC, at every node k in the model grid,
over all time steps since harmonic analysis means and variance checking has
begun
XVELVA(k) - sum of squares of
depth-averaged u velocities computed by ADCIRC, at every node k in the model
grid, over all time steps since harmonic analysis means and variance checking
has begun
YVELAV(k) - sum of depth-averaged v
velocities computed by ADCIRC, at every node k in the model grid, over all time
steps since harmonic analysis means and variance checking has begun
YVELVA(k) - sum of squares of depth-averaged
v velocities computed by ADCIRC, at every node k in the model grid, over all
time steps since harmonic analysis means and variance checking has begun
Variable Definitions
(fort.41, fort.42, fort.43, fort.44, fort.45, fort.46)
NDSET3DSD – number of data sets to be
written to fort.41
SIGTSTA
- Sigma T value (kg/m^3) (=density-1000) at a specified recording station
SALSTA – Salinity (PSU)
at a specified recording station
TEMPSTA – Temperature
(DEG C) at a specified recording station
NDSET3DSV – number of data sets to be written to fort.42
REAL(QSTA(k,j)) – u velocity component for station output
AIMAG(QSTA(k,j)) – v velocity component for station output
WZSTA(k,j) – vertical velocity for station output. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, velocity is m/s, if gravity is in ft/s2, velocity is in ft/s). If ICS=2, gravity must be specified in m/s2 and the velocity units are m/s.
NDSET3DST – number of data sets to be
written to fort.43
q20STA(M) –
turbulent kinetic energy for station output
ISTA(M) – mixing length for station output
EVSTA(M) - Spatially constant horizontal
eddy viscosity for the momentum equations (units of length2/time) for station
output
REAL(Q(j,M)) – u velocity component for global output
AIMAG(Q(j,M)) – v velocity component for global output
WZ(j,M) – vertical velocity for global output. If ICS=1, units are determined by the units of gravity (G) specified in the fort.15 file (eg. if G is in m/s2, velocity is m/s, if gravity is in ft/s2, velocity is in ft/s). If ICS=2, gravity must be specified in m/s2 and the velocity units are m/s.
q20(j,M) – turbulent kinetic energy
EV (j,M) -
horizontal eddy viscosity for the momentum equations (units of length2/time)
for global output
NDSET3DGD – the number of data sets to be written to fort.44
NDSET3DGV – the number of data sets to be written to fort.45
NDSET3DGT – the number of data sets to be written to fort.46
NLSD – salinity lateral diffusion coefficient
NVSD – salinity vertical diffusion coefficient
NLTD – temperature lateral diffusion coefficient
NVTD – temperature vertical diffusion coefficient
ALP4 – time stepping coefficient associated with the transport equation terms
NTF – temperature boundary condition file type (this file is not supported yet).