ADCIRC+SWAN supplementary scripts and example of spatial and temporal controls. With these controls, the user can specify exactly when and where SWAN will perform its computations during a coupled ADCIRC+SWAN simulation. Instead of having to run SWAN on the full mesh and for the entire timeframe, the user can limit SWAN to a spatial region near landfall and a temporal duration at the height of the storm. These controls have the potential to speed-up the overall simulation, without much sacrifice in accuracy.
This control has been added to give flexibility to the user to simulate SWAN for a unique timeframe within the ADCIRC+SWAN simulation. Previously, it was required that SWAN would compute for the entire timeframe of the simulation, which was inefficient if the storm was far offshore and the waves were small. Now, the user can control SWAN to compute only for a portion of the simulation, thus allowing for an efficiency gain when SWAN is idle.
There are two changes that need to be made to use the temporal controls.
- On the ADCIRC input side - the namelist
SWANTimeControlmust be used and theRunStartDateTimemust be set with the start of the current ADCIRC simulation at the end of the ADCIRC model control file (fort.15).
&SWANTimeControl RunStartDateTime='20180907.000000' /- On the SWAN input side - the
COMPUTE' time in the SWAN input file (fort.26`) can be altered to the desired time range.
- For example, to run a simulation for only four days, change the COMPUTE time.
TEST 1,0
COMPUTE 20180912.000000 1200 SEC 20180916.000000
STOPThis will result in SWAN running for four days, regardless of the ADCIRC timeframe, thus leading to faster wall clock run times of simulations.
This control has been added to give flexibility to the user to simulate SWAN for a unique spatial domain within the ADCIRC computational mesh. Previously, it was required that SWAN would compute on the full ADCIRC mesh, which again was inefficient in regions far from the storm. Now, the user can specify a region for the SWAN computations, such as a portion of the coastal ocean near landfall, thus allowing for an efficency gain in the regions where SWAN is idle.
There are several changes that need to be made to use the spatial controls.
- On the ADCIRC input side - the nodal attribute
swan_local_controlmust be added and accounted for in the ADCIRC model control file (fort.15).
3 ! NWP
sea_surface_height_above_geoid
mannings_n_at_sea_floor
swan_local_controlThe nodal attribute must be added to the nodal attributes file (fort.13) with the default values and non-default nodes.
swan_local_control
1
2
1 0swan_local_control
54
973 0 0
977 1 8
978 0 0
980 1 9Each node that is inactive or an internal source node (non-deault) is listed.
- In the example above, 54 nodes are non-defaults with node 973 and 978 being inactive vertices and nodes 977 and 980 being set as internal sources.
- On the SWAN input side - input commands to apply spectra must be set in the SWAN input file (
fort.26) for each internal source node. Each internal source spectral file should be in the main simulation directory.
- For example, to apply the spectral file
bnd977.spcat internal source node 977 (side 8), the following command is needed.
BOUnd SHAPespec JONswap 3.3 PEAK DSPR DEGRees
$
BOUndspec SIDE 8 CONstant FILE 'bnd977.spc' 1
BOUndspec SIDE 9 CONstant FILE 'bnd980.spc' 1
BOUndspec SIDE 10 CONstant FILE 'bnd984.spc' 1This will result in SWAN running in a limited spatial domain with internal spectra applied at the desired locations.
The supplementary scripts are helpful tools when using the spatial controls, and more detail is provided on each script. This workflow supports running SWAN over a selective spatial domain using internal source spectra to account for offshore swell enegery, with flexibility depending on whether the boundary spectra already exist or must be generated.
For questions or modifications, please contact:
Nicole Arrigo
North Carolina State University - Coastal & Computational Hydraulics Team
Email: nkarrigo@ncsu.edu