Computational grids and boundary / initial / first guess conditions

The **computational spatial grid** must be defined by the user. The orientation (direction) can be chosen
arbitrarily.

The boundaries of the computational spatial grid in SWAN are either land or water. In the case of land
there is no problem: the land does not generate waves and in SWAN it absorbs all incoming wave energy.
But in the case of a water boundary there may be a problem. Often no wave conditions are known along
such a boundary and SWAN then assumes that no waves enter the area and that waves can leave the
area freely. These assumptions obviously contain errors which propagate into the model. These
boundaries must therefore be chosen sufficiently far away from the area where reliable computations are
needed so that they do not affect the computational results there. This is best established by varying the
location of these boundaries and inspect the effect on the results. Sometimes the waves at these boundaries
__can__ be estimated with a certain degree of reliability. This is the case if (a) results of another
model run are available (nested computations) or, (b) observations are available. If model results are
available along the boundaries of the computational spatial grid, they are usually from a coarser
resolution than the computational spatial grid under consideration. This implies that this coarseness of
the boundary propagates into the computational grid. The problem is therefore essentially the same as
if no waves are assumed along the boundary except that now the error may be more acceptable (or the
boundaries are permitted to be closer to the area of interest). If observations are available, they can be
used as input at the boundaries. However, this usually covers only part of the boundaries so that the rest
of the boundaries suffer from the same error as above.

A special case occurs near the coast. Here it is often possible to identify an up-wave boundary (with
proper wave information) and two lateral boundaries (with no or partial wave information). The affected
areas with errors are typically regions with the apex at the corners of the water boundary with wave
information, spreading towards shore at an angle of 30
^{o} to 45
^{o} for wind sea conditions
to either side of the imposed mean wave direction (less for swell conditions; the angle is essentially the
one-sided width of the directional distribution of wave energy). For propagation of short crested waves
(wind sea condtions) an example is given in Figure 2.1. For this reason the lateral boundaries
should be sufficiently far away from the area of interest to avoid the propagation of this error into this area.
Such problems do not occur if the lateral boundaries contain proper wave information over their entire length
e.g. obtained from a previous SWAN computation or if the lateral boundaries are coast.

When __output__ is requested along a __boundary of the computational grid__, it may occur
that this output differs from the boundary conditions that are imposed by the user. The reason is that
SWAN accepts only the user-imposed __incoming__ wave components and that it replaces the user-imposed
__outgoing__ wave components with computed outgoing components (propagating to the boundary from
the interior region). The user is informed by means of a warning in the output when the
computed significant wave height differs more than 10%, say (10% is default), from the user-imposed
significant wave height (command `BOUND`...). The actual value of this difference can be set by the
user (see the `SET` command). Note that this warning will not apply in the case of unstructured grids.

If the computational grid extends outside the input grid, the reader is referred to Section 2.6.2
to find the assumptions of SWAN on depth, current, water level, wind, bottom friction in the non-overlapping area.

The spatial resolution of the computational grid should be sufficient to resolve relevant details of the wave
field. Usually a good choice is to take the resolution of the computational grid approximately equal to that
of the bottom or current grid. If necessary, an unstructured grid may be used.

SWAN may not use the entire user-provided computational grid if the user defines exception values on
the depth grid (see command `INPGRID BOTTOM`) or on the curvilinear computational grid (see command
`CGRID`).
A computational grid point is either

__wet__, i.e. the grid point is included in the computations since it represents water; this may vary with time-dependent or wave-induced water levels or__dry__, i.e. the grid point is excluded from the computations since it represents land which may vary with time-dependent or wave-induced water levels or__exceptional__, i.e. the grid point is permanently excluded from the computations since it is so defined by the user.

- each grid line between two adjacent wet computational grid points (a wet link)
__without__an adjacent, parallel wet link, is removed, - each wet computational grid point that is linked to only one other wet computational grid point, is removed and
- each wet computational grid point that has no wet links is removed.

It must be noted that for parallel runs using MPI the user must indicate an exception value when reading the bottom levels (by means of command

The

The computational time step must be given by the user in case of nonstationary runs. Since, SWAN is based on implicit numerical schemes, it is not limited by the Courant stability criterion (which couples time and space steps). In this sense, the time step in SWAN is not restricted. However, the accuracy of the results of SWAN are obviously affected by the time step. Generally, the time step in SWAN should be small enough to resolve the time variations of computed wave field itself. Usually, it is enough to consider the time variations of the driving fields (wind, currents, water depth, wave boundary conditions). But be careful: relatively(!) small time variations in depth (e.g. by tide) can result in relatively(!) large variations in the wave field.

As default, the first guess conditions of a

A quasi-stationary approach can be employed with stationary SWAN computations in a time-varying sequence of stationary conditions.

The

- The lowest frequency, the highest frequency and the number of frequencies can be chosen.
- Only the lowest frequency and the number of frequencies can be chosen. The highest frequency
will be computed by SWAN such that
*f*= 0.1*f*. This resolution is required by the DIA method for the approximation of nonlinear 4-wave interactions (the so-called quadruplets). - Only the highest frequency and the number of frequencies can be chosen. The lowest frequency
will be computed by SWAN such that
*f*= 0.1*f*. This resolution is required by the DIA method for the approximation of nonlinear 4-wave interactions. - Only the lowest frequency and the highest frequency can be chosen. The number of frequencies
will be computed by SWAN such that
*f*= 0.1*f*. This resolution is required by the DIA method for the approximation of nonlinear 4-wave interactions.

SWAN has the option to make computations that can be nested in WAM or WAVEWATCH III. In such runs SWAN interpolates the spectral grid of WAM or WAVEWATCH III to the (user provided) spectral grid of SWAN. The WAM Cycle 4 source term in SWAN has been retuned for a highest prognostic frequency (that is explicitly computed by SWAN) of 1 Hz. It is therefore recommended that for cases where wind generation is important and WAM Cycle 4 formulations are chosen, the highest prognostic frequency is about 1 Hz.

In directional space, the directional range is the full 360

It is recommended to use the following discretization in SWAN for applications in coastal areas:

direction resolution for wind sea |
= 15^{o} -10^{o} |

direction resolution for swell |
= 5^{o} -2^{o} |

frequency range |
0.04 f 1.00 Hz |

spatial resolution |
x,y = 50 - 1000 m |

The numerical schemes in the SWAN model require a minimum number of discrete grid points in each spatial directions of 2. The minimum number of directional bins is 3 per directional quadrant and the minimum number of frequencies should be 4.