--- Welcome to the official ADCIRCWiki site! The site is currently under construction, with limited information. ---

For general information, see the ADCIRC site, ADCIRC FAQ, or the ADCIRC Wikipedia page. For model documentation not yet available on the wiki, see the ADCIRC site. New content is being continuously added to the ADCIRCWiki, and material from the main ADCIRC site will be gradually transitioned over to the wiki.

Fort.15 file

From ADCIRCWiki
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This file contains the majority of the parameters required to run both the 2DDI and 3D versions of ADCIRC and the information to drive the model with harmonic boundary conditions (either elevation or flux). This file is required to run the ADCIRC model.

File Format

See fort.15 file format for details.

Tips and Tricks

Meteorological-Only Mode

By turning off all ocean state-related outputting and disabling wave coupling, ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing DT, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set DT equal to the time interval you wish met. data to be output, and then set the NSPOOLM and/or NSPOOLGW (the local and global met. output intervals) to 1 (i.e. output every time step). For typical 2D ADCIRC runs, this requires setting the following in the fort.15 file:
NOUTE = 0
NOUTV = 0
NOUTGE = 0
NOUTGV = 0
NHSTAR = 0
NHASE = 0
NHASV = 0
NHAGE = 0
NHAGV = 0

For passive scalar transport (IM = 10), also set:
NOUTC = 0
NOUTGC = 0

while for barotropic or baroclinic 3D ADCIRC, also set:
I3DSD = 0
I3DSV = 0
I3DST = 0
I3DGD = 0
I3DGV = 0
I3DGT = 0

Ramping Meteorological Forcing at Hot-Start

It is generally best to ramping in forcing terms to the model to avoid shocking the system, but ramping parameters like DRAMP define the start of ramp time as being cold-start time. Since it is common-place to initialize meteorological forcing at hotstart time, there is a special parameter to facilitate hotstart ramping of met. data. Let's say you run a 15-day tide-only run and output a hotstart file. Setting
NRAMP = 8
means you can supply DRAMPUnMete, which is the number of delays at which to start met. ramping, on the DRAMP line. Here's an example:
5 0 0 0 0 0 0.5 0 15  ! DRAMP, DRAMPExtFlux, FluxSettlingTime, DRAMPIntFlux, DRAMPElev, DRAMPTip, DRAMPMete, DRAMPWRad, DRAMPUnMete
What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).