ADCIRCWiki - User contributions [en]

Fort.22 file format

2020-06-17T16:09:35Z

Alexcrosby: move nws12 doc to individual page and link, also to 13

=General Notes=

The basic file structure is shown below. Each line of input data is represented by a line containing the input variable name(s). Blank lines are only to enhance readability. Loops indicate multiple lines of input. Conditional input is indicated by an if clause.

Meteorological data in formats other than OWI (NWS=12) and GFDL (NWS=16) must be provided for the entire model run, otherwise the run will crash.

See [[NWS]] for details on meteorological input types.

==NWS = 1 or 101==

===File Structure===

for k=1,[[NP]]

: [[JN]], [[WSX(k), WSY(k)]], [[PRN(k,j)]]

end k loop

===Notes===

Meteorological data is input directly to all nodes in the ADCIRC grid.

The units for pressure are meters of H2O.

The first set of met. data corresponds to <code>TIME=[[STATIM]]+[[DTDP]]</code>. Additional sets of met data must be provided at every time step, <code>([[WTIMINC]] = [[DTDP]])</code>.

Wind stress must be input in units of velocity squared (consistent with the units of gravity) and surface atmospheric pressure must be input in units of equivalent height of water (e.g., meters of water, feet of water that are consistent with the units of gravity). Stress in these units is obtained by dividing stress in units of force/area by the reference density of water. Pressure in these units is obtained by dividing pressure in units of force/area by the gravitational constant and the reference density of water. For example, 10^5Pa =10^5 N/m^2 =10^5 kg m/(s m)^2 divided by 9.81 m/s^2 and 10^3 kg/m^3 equals 10.2 meters of water.

==NWS = 2, -2, 102 or -102==

===File Structure===
for k=1, NP

: [[JN]], [[WSX(k), WSY(k)]], [[PRN(k,j)]]

end k loop

===Notes===

Meteorological data is input directly to all nodes in the ADCIRC grid.

The units for pressure are meters of H2O.

If <code>[[NWS]] = 2 or 102</code>, the first set of met. data corresponds to <code>TIME=[[STATIM]]</code>. If <code>[[NWS]]</code> = -2 or 102, the first set of met data corresponds to <code>TIME=HOT START TIME</code>. Additional sets of met. data must be provided every <code>[[WTIMINC]]</code>, where <code>[[WTIMINC]]</code> is the met. data time interval and is specified in the Model Parameter and Periodic Boundary Condition File. Met data is interpolated in time to the ADCIRC time step.

Wind stress must be input in units of velocity squared (consistent with the units of gravity) and surface atmospheric pressure must be input in units of equivalent height of water (e.g., meters of water, feet of water that are consistent with the units of gravity).Stress in these units is obtained by dividing stress in units of force/area by the reference density of water. Pressure in these units is obtained by dividing pressure in units of force/area by the gravitational constant and the reference density of water. For example,

<code>10^5Pa =10^5 N/m^2 =10^5 kg m/(s m)^2 divided by 9.81 m/s^2 and 10^3 kg/m^3 equals 10.2 meters of water</code>

==NWS = 3 or 103, Fleet Numeric Format==

===File Structure===

[[IWTIME]]

for k = 1,[[NWLAT]]

: for j = 1,[[NWLON]]

:: [[WSPEED(k,j)]]

: end j loop

end k loop

for k = 1, NWLAT

: for j = 1, NWLON

:: [[WDIR(k,j)]]

: end j loop

end k loop

===Notes===

Meteorological data is input to a longitude, latitude grid and interpolated in space onto the ADCIRC grid.The ADCIRC grid must be in lon, lat coordinates.

The first set of met. data must be at or before the date and time listed in the Model Parameter and Periodic Boundary Condition File as the beginning time of the simulation. Additional sets of met. data must be provided every <code>WTIMINC</code>, where <code>[[WTIMINC]]</code> is the met. data time interval.Values for <code>[[NWLAT]], [[NWLON]], [[WTIMINC]]</code>, and several other parameters must be set in the Model Parameter and Periodic Boundary Condition File. Met data is interpolated in time to the ADCIRC time step.

Wind velocity (@ 10 m above the water surface) must be input in units of m/s (regardless of the units of gravity).

The following relations are used to compute wind stress from the input wind velocity.

<code>WIND_SPEED = magnitude of WIND_VEL</code>

<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code>

<code>If (DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code>

<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code>

==NWS = 4, -4, 104 or -104 - PBL Hurricane Model format==

Meteorological data is input directly to a subset of nodes in the ADCIRC grid (as specified by the node number JN).The ADCIRC grid must be either in lon, lat coordinates or in meter-based Cartesian coordinates.

===File Structure===

FOR EACH WIND TIME INCREMENT

: DO UNTIL LINE = ” #”

:: [[JN]], [[WVNX(JN), WVNY(JN)]], [[PRN(k,j)]]

: END DO UNTIL

END FOR EACH

===Notes===

If <code>[[NWS]] = 4 or 104</code>, the first set of met. data corresponds to <code>TIME=[[STATIM]]</code>. If <code>[[NWS]] = -104 or -4</code>, the first set of met data corresponds to <code>TIME=HOT START TIME</code>. Additional sets of met. data must be provided every <code>[[WTIMINC]]</code>, where <code>[[WTIMINC]]</code> is the met. data time interval and is specified in the Model Parameter and Periodic Boundary Condition File. Met data is interpolated in time to the ADCIRC time step.

Each data line must have the format I8, 3E13.5.Data input lines are repeated for as many nodes as desired. A line containing the # symbol in column 2 indicates met data at the next time increment begins on the following
line. At each new time, any node that is not specified in the input file is assumed to have zero wind velocity and pressure = 1013.

Wind velocity (assumed to be 10m 10 minute averaged value) must be input in knots and surface atmospheric pressure must be input in hundredths of a millibar.

The following relations are used to compute wind stress from wind velocity:

<code>WIND_VEL{m/s @ 10m} = WIND_VEL{knots @ bl average}*0.5144</code> (In prior ADCIRC versions, an additional factor of 1.04 was included in the formulation to convert from 30 minute avg winds to 10 minute avg winds. This factor was removed and it is currently assumed that the input wind data uses a 10 minute averaging period. Note, this is unrelated to the value of WTIMINC).

<code>WIND_SPEED = magnitude of WIND_VEL</code>

<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code>

<code>if(DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code>

<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code>

The following relationship is used in ADCIRC to convert to pressure in meters of water from pressure in hundredths of a millibar:

<code>PRESSURE{m H2O}=PRESSURE{Pa/100}*100/(GRAVITY*DENSITY H2O)</code>

==NWS = 5, -5, 105, or -105==

===File Structure===

for k = 1, NP

: [[JN]], [[WVX(k), WVY(k)]], [[PRN(k,j)]]

end k loop

===Notes===

Meteorological data is input directly to all nodes in the ADCIRC grid.The ADCIRC grid must be either in lon, lat coordinates or in meter-based Cartesian coordinates.

If <code>[[NWS]] = 5 or 105</code>, the first set of met. data corresponds to <code>TIME=[[STATIM]]</code>. If <code>[[NWS]] = -105 or -5</code>, the first set of met data corresponds to <code>TIME=HOT START TIME</code>. Additional sets of met. data must be provided every <code>[[WTIMINC]]</code>, where <code>[[WTIMINC]]</code> is the met. data time interval and is specified in the Model Parameter and Periodic Boundary Condition File. Met data is interpolated in time to the ADCIRC time step.

Wind velocity (@ 10 m above the water surface) must be input in m/s and surface atmospheric pressure must be input in meters of water.

The following relations are used to compute wind stress from wind velocity:

<code>WIND_SPEED = magnitude of WIND_VEL</code>

<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code>

<code>if(DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code>

<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code>

==NWS = 6 or 106==

===File Structure===

for k=1, NWLAT

: for j=1, NWLON

:: [[WVXFN(k,j), WVYFN(k,j)]], [[PRN(k,j)]]

: end j loop

end k loop

===Note===

In versions 43 and earlier the format of input was P, U, V. The input has now changed to U, V, P to be consistent with other NWS formats.

Meteorological data is input on a rectangular grid (either in Longitude, Latitude or Cartesian coordinates, consistent with the grid coordinates) and interpolated in space onto the ADCIRC grid. In setting up the meteorological grid it is assumed that y (e.g., latitude) varies from north (<code>k=1</code>) to south (<code>k=[[NWLAT]]</code>) and x (e.g., longitude) varies from west (<code>j=1</code>) to east (<code>j=[[NWLON]]</code>). The spatial extents of the meteorological grid must be consistent with the ADCIRC model domain. For example, if ADCIRC uses negative longitude values to indicate locations W of the Greenwich meridian, the meteorological file must be similarly organized. Any grid that crosses the Greenwich Meridian should be organized so that the seam occurs @ 180 deg longitude. Therefore, the meteorological and ADCIRC grids should use negative longitudes W of the Greenwich Meridian and positive longitudes to the E.

The meteorological grid MUST cover the entire ADCIRC mesh; that is, the ADCIRC mesh must be ENTIRELY within the meteorological grid or an error will result.

The first set of met. data corresponds to the beginning time of the current simulation. If the model is cold started this corresponds to <code>TIME=[[STATIM]] </code>. If the model is hot started, this corresponds to <code>TIME=HOT START TIME</code>. Additional sets of met. data must be provided every <code>[[WTIMINC]]</code>, where <code>[[WTIMINC]]</code> is the met. data time interval.Values for <code>[[NWLAT]], [[NWLON]], [[WTIMIN]]C</code>, and several other parameters must be set in the [[fort.15_file_format|fort.15 file]]. Met data is interpolated in time to the ADCIRC time step.

Wind velocity (@ 10 m above the water surface) must be input in units of m/s and surface atmospheric pressure must be input in units of Pascals = Newtons/square meter.

The following relations are used to compute wind stress from the input wind velocity.

<code>WIND_SPEED = magnitude of WIND_VEL</code>

<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code>

<code>If (DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code>

<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code>

The following relationship is used in ADCIRC to convert to pressure in meters of water from pressure in Pascal:

<code>PRESSURE{m H2O}=PRESSURE{Pascal}/(GRAVITY*DENSITY H2O)</code>

==NWS = 7 or -7==

===File Structure===
for k=1, NWLAT

: for j=1, NWLON

:: WVXFN(K,J),WVYFN(K,J),PRN(K,J)

: END DO

END DO

==NWS = 8==

===File Structure===
Use the [https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html ATCF Best Track/Objective Aid/Wind Radii Format].

===Notes===
Hurricane parameters are read in from the Single File Meteorological Forcing Input File. Wind velocity and atmospheric pressure are calculated at every node on the fly by ADCIRC internally using the Dynamic Holland model. The input file is fixed width (not comma separated values or csv) and is assumed to correspond to the <code>ATCF Best Track/Objective Aid/Wind Radii Format</code>. Historical tracks, real-time hindcast tracks and real-time forecast tracks may be found in this format. Selecting <code>[[NWS]] = 8</code> also requires the specification of the cold start time, storm number, and boundary layer adjustment (see <code>[[YYYY MM DD HH24 StormNumber BLAdj]]</code>). Garret’s formula is used to compute wind stress from the wind velocity.

The symmetric vortex model (<code>[[NWS]]=8</code>) in ADCIRC assumes that the longitudes in the fort.22 are west longitude, so it multiplies the longitude values by -1. It ignores the ‘E’ or ‘W’ in the longitude column of the fort.22.

The symmetric vortex model (<code>[[NWS]]=8</code>) does not use any of the isotach wind speeds or wind radii data. When reading lines labeled “BEST” from the fort.22, it obtains timing information from the year, month, day, and hour in column 3. When reading lines labeled “OFCL” from the fort.22, it uses the forecast increment (a.k.a. TAU) from column 6. The use of these two different columns by ADCIRC <code>[[NWS]]=8</code> is to maintain consistency with the official file structure for the ATCF file format.

For <code>[[NWS]]=8</code>, ADCIRC knows the current time because the user provides the year, month, day, and hour of cold start on the <code>[[WTIMINC]]</code> line in your fort.15. It also has the time that has elapsed since cold start, because that is provided in the hotstart file, if any. It then compares the current time with the date/times in the fort.22 (as described in the previous paragraph) to automatically find the right place to begin reading data from the fort.22.

So, in summary, if the whole fort.22 consists of “BEST” lines, the symmetric vortex model (<code>NWS=8</code>) only looks at column 3 for time information. And it automatically knows where to start reading cyclone data, based on the coldstart date/time the user provides in the fort.15 file.

==NWS = 10==

===File Structure===

for k=1, [[LONB*LATB]]

: [[PG(k)]], [[UG(k)]], [[VG(k)]]

end j loop

==NWS = 11==

===File Structure===

for k=1, LONB*LATB

: PG(k), UG(k), VG(k)

end j loop

==NWS = 12==

Oceanweather Inc (OWI) ASCII "WIN"/"PRE" format , details can be found at [[NWS12]]

==NWS = 13==

Oceanweather Inc (OWI) NetCDF format , details can be found at [[NWS13]] {{ADC version|version=55|relation=ge}}

==NWS = 14==
When using NetCDF files (fort.221.nc, fort.222.nc) as met inputs, the fort.22 is required in order to list the relevant variable names so that the internal NetCDF read routines can find the pertinent variables. In the case of GRIB2 input files (fort.221.grb2, fort.222.grb2) the fort.22 is not required because the variable names are standardized and on start-up the internal wgrb2api library prints out inventory look-up files (*.inv) that it uses to find the information contained within the *.grb2 files. {{ADC version|version=55|relation=eq}}

===File Structure===
Temporal dimension name 
Datetime variable name 
Format of the datetime time variable [special note, if first character is not a '%' then it will ignore this variable and will assume to start from the first time snap] 
Zonal (east-west) dimension name 
Longitude variable name 
Meridional (north-south) dimension name 
Latitude variable name 
Sea-level Pressure variable name 
Zonal 10-m Wind Velocity name 
Meridional 10-m Wind Velocity name 
Ice area-fraction name [optional, only if fort.225.nc present for ice area fraction]

===Example (WRF output)===
Time 
Times [if no datetime variable then set to dummy such as 'none'] 
%Y-%m-%d_%H:%M:%S [if no datetime variable then set to dummy such as 'none'] 
west_east 
XLONG 
south_north 
XLAT 
PSFC 
U10 
V10 
aice [optional] 

===Notes===
If the time variable is not in a datetime format (e.g., is a float in minutes since..) the datetime format can be set to a dummy name, e.g., 'minutes'. The code checks to see if the first character of the datetime format is '%'. If not the code will assume to simply begin reading from the first time snap. If the datetime variable is available the code will work out which time snap to start reading from based on the reference date, [[NCDATE]] located near or at the bottom of the [[fort.15 file]].

==NWS = 15==
The goal of the implementation of the HWind capability within ADCIRC was to allow HWind files to be used as-is, without resorting to an intermediate format. As a result, the fort.22 file consists of a header line to provide some configuration parameters, and then a list of the filenames of the HWind files to be used in the ADCIRC run.

===File Structure===

comment line

[[hWindMultiplier]]

[[presssureWindRelationship]]

for i=1 to numHWindFiles

: [[hours(i)]] [[centralPressure(i)]] [[rampMult(i)]] [[filename(i)]]

end i loop

===Notes===
HWind files are data assimilated snapshots of the wind velocity fields of tropical cyclones that are produced by the NOAA Hurricane Research Division (HRD). The files have the following characteristics:

<code>the format explicitly indicates the center of the storm</code>

<code>the (u,v) data are on a regular grid</code>

<code>the regular grid is a mercator projection with origin at storm center</code>

<code>the mercator grid spacing is in meters and is uniform in x and y (dx=dy)</code>

<code>the dimensions (nx,ny) of the mercator grid are equal (nx=ny)</code>

<code>the grid dimensions change from snapshot to snapshot; for example, the first shapshot may be 161×161 while the 2nd snapshot may be 121×121 (etc)</code>

<code>sequential hwind snapshots will not be evenly spaced in time for a particular storm</code>

hwind data do not contain barometric pressure information

For the dvorak, knaffzehr, and specifiedPc options, the barometric pressure field is computed by determining the radius to maximum winds Rmax (i.e., the distance of Vmax from the center of the storm), calculating the Holland B parameter, and then using the Holland formulation to calculate barometric pressure as a function of the distance from the center of the storm.

To illustrate the definitions and descriptions provided, a concrete example of an HWind fort.22 file is provided as follows:

<code>! first line is a comment line, max length 1024 characters</code>

<code>1.0 ! 2nd line is a velocity magnitude multiplier</code>

<code>dvorak ! 3rd line: one word for the pressure-wind relationship</code>

<code>0.0 -1 0.0 “/home/jason/hwind/al092011_0828_1330” ! time (hours), Pc (mb), ramp mult, filename</code>

<code>6.0 -1 0.5 “/home/jason/hwind/al092011_0828_1930”</code>

<code>12.0 -1 1.0 “/home/jason/hwind/al092011_0829_0130”</code>

==NWS = 16==
The GFDL input capability uses GFDL model output files as-is; as a result, the fort.22 file consists of a list of GFDL model output files to be used in ADCIRC.

===File Structure===

comment line

[[GFDLWindMultplier]]

[[MaxExtrapolationDistance]]

for i=1 to numGFDLFiles

: [[hours(i)]] [[rampMult(i)]] [[filename(i)]]

end i loop

===Notes===

GFDL model output files are produced by the Geophysical Fluid Dynamics Laboratory at NOAA. Each ASCII GFDL model output file contains one or more nested grid dataset where the nested grids are allowed to change in time. Coarse grid data is not stored where finer nest data is given. The files are formatted as follows:

<code>Line 1: Number of grid cells (f10.4) NCELLS</code>

<code>Lines 2 through NCELLS+1: Ten columns of data formatted as 10f10.4 as follows:</code>

<code>column 1: u (m/s)</code>

<code>column 2: v (m/s)</code>

<code>column 3: Temperature (K)</code>

<code>column 4: mixing ratio(kg/kg)</code>

<code>column 5: storm accum precipitation (cm)</code>

<code>column 6: sea level pressure (hPa)</code>

<code>column 7: longitude (decimal deg)</code>

<code>column 8: latitude (decimal deg)</code>

<code>column 9: hurricane hour</code>

<code>column 10: nest number (this is not always present)</code>

To illustrate the definitions and descriptions provided, a concrete example of a GFDL fort.22 file is provided as follows:

<code>! first line is a comment line, max length 1024 characters</code>

<code>1.0 ! 2nd line is a velocity magnitude multiplier</code>

<code>100.0 ! 3rd line: maximum extrapolation distance (m)</code>

<code>0.0 -1 0.0 “/home/jason/hwind/al092011_0828_1330″ ! time (hours), Pc (mb), ramp mult, filename</code>

<code>6.0 -1 0.5 “/home/jason/hwind/al092011_0828_1930″</code>

If the ADCIRC time falls outside the interval of time covered by the GFDL model output files, ADCIRC will insert “blank snaps”, i.e., it will set the wind velocity at all mesh vertices to 0.0 m/s and the barometric pressure to a uniform background pressure of 1013mb.

==NWS = 19==
Note that use of this [[Typical_ADCIRC_Parameter_Selections#Discouraged_Parameter_Selections|is discouraged]].
===File Structure===
The file needs to be in the [https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html ATCF Best Track/Objective Aid/Wind Radii Format].

===Notes===
User has the ability to select which Isotach to use in each of the 4 quadrants. User also has ability to modify <code>RMAX</code> and <code>Holland’s B parameter</code> using the ASWIP program. The auxiliary preprocessing program ASWIP.F (located in the /wind directory and executable is created by typing, make aswip, in the work folder after adcirc executable has been generated), will generate the fort.22 input file for <code>NWS=19</code> from a <code>NWS= 9</code> formatted input file.

Hurricane parameters are read in from the Single File Meteorological Forcing Input File. It is assumed that the line in the fort.22 file with a zero as the forecast increment (i.e., column 6) corresponds to the start of the current simulation run, whether it is a hotstart or cold start. In other words, there is no option to set the NWS value negative to indicate that the file starts at the ADCIRC hotstart time. Rather, the forecast increment in hours (column 6) is used to indicate the relationship between the ADCIRC time and the data in the fort.22 file. Wind velocity and atmospheric pressure are calculated at exact finite element mesh node locations and directly coupled to ADCIRC at every time step using the asymmetric hurricane vortex formulation (Mattocks et al, 2006; Mattocks and Forbes, 2008) based on the Holland gradient wind model. The input file is assumed to correspond to the <code>ATCF Best Track/Objective Aid/Wind Radii Format</code>. Historical tracks, real-time hindcast tracks and real-time forecast tracks may be found in this format. This option uses the radii at specific wind speeds (34, 50, 64, 100 knots) reported in the four quadrants (NE, SE, SW, NW) of the storm to calculate the radius of maximum winds as a function of the azimuthal angle. Garret’s formula is used to compute wind stress from the wind velocity. The <code>NWS=19</code> option allows the user to set a value for <code>Rmax</code> and <code>Holland B Parameter</code>. Additionally the user can select the isotachs to be used for each of the 4 quadrants. The utility program aswip_1.0.3.F located in the /wind folder will generate the <code>NWS=19</code> fomatted file from a <code>NWS=9</code> formatted fort.22 input file.

In order to use the <code>NWS=19</code> option, the file needs to be in best track format. The forecast period (column #6) needs to be edited to reflect the time of the forecast/nowcast for each track location (each line) in hours from the start of the simulation (0, 6, 12, 18, etc). The original data in that column depends on what type of best track format data is being used. The original data might have 0 or other numbers in that column. See: [https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html ATCF Best Track/Objective Aid/Wind Radii Format]. It is suggested that users change the “BEST” tech type to “ASYM” in column 5 in the fort.22 file to denote that the file has been modified to accommodate the asymmetric wind formulation (the simulation time in hours in the 6th column has been added, etc.) so it will not get confused in the future with a best track file.

The <code>NWS=19</code> option requires the following variables in the fort.22 file in a best track format:

<code>Forecast time in hours (column 6); enter the time in hours in each record starting at 0</code>

<code>Latitude of the eye (column 7)</code>

<code>Longitude of the eye (column 8)</code>

<code>Maximum sustained wind speed in knots (column 9)</code>

<code>Minimum sea level pressure in MB (column 10)</code>

<code>Wind intensity in knots of the radii defined in the record (34, 50, 64 or 100 knots) (column 12)</code>

<code>Radius of specified wind intensity for quadrants 1, 2, 3, 4 in NM (columns 14, 15, 16, 17); ? 0</code>

<code>Background pressure in MB (column 18); a standard value of 1013 can be used</code>

<code>Rmax as reported in the ATCF BEST TRACK file in column 20</code>

<code>Storm Name in Column 28 ATCF file format</code>

<code>Time Record number in column 29. There can be multiple lines for a given time record depending on the number of isotachs reported in the ATCF File</code>

<code>number of isotachs reported in the ATCF file for the corresponding Time record.</code>

<code>Columns 31-34 indicate the selection of radii for that particular isotach. 0 indicates do not use this radius, and 1 indicates use this radius and corresponding wind speed.</code>

<code>Columns 35-38 are the designated Rmax values computed for each of the quadrants selected for each particular isotach.</code>

<code>Column 39 is the Holland B parameter computed using the formulas outlines in the Holland paper, and implemented using the aswip program.</code>

Available files:

* [ftp://ftp.nhc.noaa.gov/atcf/archive/ Historical storm files]

* [ftp://ftp.nhc.noaa.gov/atcf/btk/ Forecast tracks]

The format of the file is fixed and users will want to use the aswip program to be sure that the input fort.22 file is properly formatted.

<code>The command line for NWS=19 is ./aswip -n 19 -m 2 -z 1</code>

==NWS = 20, Generalized Asymmetric Holland Model (GAHM)==

===File Structure===
The file needs is similar to the NWS = 19 format with 8 additional columns of data, see notes below for more information.

===Notes===

The Generalized Asymmetric Holland Model (GAHM) provides a set of theoretical and practical improvements over previous parametric meteorological vortex models in ADCIRC. The theory and implementation of the GAHM was initially described at the 2013 ADCIRC Users Group Meeting.

<code>Forecast time in hours (column 6); enter the time in hours in each record starting at 0</code>

<code>Latitude of the eye (column 7)</code>

<code>Longitude of the eye (column 8)</code>

<code>Maximum sustained wind speed in knots (column 9)</code>

<code>Minimum sea level pressure in MB (column 10)</code>

<code>Wind intensity in knots of the radii defined in the record (34, 50, 64 or 100 knots) (column 12)</code>

<code>Radius of specified wind intensity for quadrants 1, 2, 3, 4 in NM (columns 14, 15, 16, 17); ? 0</code>

<code>Background pressure in MB (column 18); a standard value of 1013 can be used</code>

<code>Rmax as reported in the ATCF BEST TRACK file in column 20</code>

<code>Storm Name in Column 28 ATCF file format</code>

<code>Time Record number in column 29. There can be multiple lines for a given time record depending on the number of isotachs reported in the ATCF File</code>

<code>number of isotachs reported in the ATCF file for the corresponding Time record.</code>

<code>Columns 31-34 indicate the selection of radii for that particular isotach. 0 indicates do not use this radius, and 1 indicates use this radius and corresponding wind speed.</code>

<code>Columns 35-38 are the designated Rmax values computed for each of the quadrants selected for each particular isotach.</code>

<code>Column 39 is the Holland B parameter computed using the formulas outlines in the Holland paper, and implemented using the aswip program.</code>

<code>Column 40-43 is the quadrant-varying Holland B parameter</code>

<code>Column 44-47 are the quadrant-varying Vmax calculated at the top of the planetary boundary (a wind reduction factor is applied to reduce the wind speed at the boundary to the 10-m surface)</code>

Historical storm files can be found archived here.

Forecast tracks can be found here.

The format of the file is fixed and users will want to use the aswip program to be sure that the input fort.22 file is properly formatted.

Options for the aswip program using NWS = 20 are the following:

<code>./aswip -n # -m # -z #</code>

;-n = nws option

;-m = methods of selecting isotachs for use in computation of radius/radii to maximum winds

:1: always use the 34kt isotach</code>

:2: use the highest available isotach in any quadrant each time

:3: use the 50kt isotach if it is available; otherwise use the 34kt isotach

:4: use all available isotachs (must choose this for GAHM/NWS=20)

;-z = approaches solving for Rmax

:1 = only rotate wind vectors afterward

:2 = rotate wind vectors before and afterwards (use this for NWS=20)

So the command line for <code>NWS=20</code> is: <code>./aswip -n 20 -m 4 -z 2</code>

NWS12

2020-06-17T16:04:45Z

Alexcrosby: add extended details from existing/bootcamp documentation

=NWS12=

Oceanweather Inc. (OWI) "WIN" and "PRE" file formats as supported in ADCIRC

==fort.22==

NWS12 uses the '''fort.22''' file as a control file because the OWI format supports individual files for wind and pressure inputs as well as multiple grid overlays of varying resolutions.

''fort.22 layout'':

NWSET
NWBS
DWM
<...to be expanded in new verions>

Where:
* '''NWSET''' is the number of nested grid overlays
* '''NWBS''' is the number of "blank" (constant 0 m/s wind speed and 1013mb pressure) timesteps to insert
* '''DWM''' is a wind multiplier to modify the wind speed magnitudes. Generally this should be set to 1 if using inputs sourced from OWI or if winds can be considered "marine exposure", with an averaging period between 10-min and 3-hrs at a height of 10 meters.

NWS12 WIN/PRE text files containing wind and pressure data should be named fort.22[1-4], as follows in order of increasing precedence in application to the ADCIRC mesh:
* ''fort.221'': Largest scale pressure (mb) fields
* ''fort.222'': Largest scale wind vector (m/s) fields
* ''fort.223'': Finer scale pressure (mb) fields
* ''fort.224'': Finer scale wind vector (m/s) fields
* ...to be expanded in new versions

===NWBS Details===

ADCIRC also has the ability to insert “blank” meteorological data if it is started before the beginning of the wind data (for a tidal spinup run, for example). Blank data is characterized by zero wind speed and 1013 mb of atmospheric pressure. This capability is activated via the NWBS parameter in the fort.22 file, as mentioned above, and it interacts with the sign of the NWS value in order to provide full control over the relationship between the ADCIRC start time (either hot start or cold start) and the beginning of the meteorological data. This capability and the interaction with the sign of NWS is described below.

If a NWBS is set to a positive number, NWBS specifies the number of blank snaps to be inserted before any information is read from fort.22[1-4]. This is useful when the duration of fort.22[1-4] files does not cover an entire ADCIRC run. Two examples are as follows:

# If NWS=+12, and if a hot start run is attempted from the 86400th time step, and if the first set, fort.221 and fort.222 files, starts at the 172800th time step, and if WTIMINC is set to 900 in UNIT 15, then you should set NWBS to (172800-0)/900 = 192. If the start times of the two sets are different, use the earlier start time, i.e., the start time of the first set.
# If NWS=-12, and if a hot start run is attempted from the 86400th time step, and if the first set, fort.221 and fort.222 files, starts at the 172800th time step, and if WTIMINC is set to 900 in the fort.15, then you should set NWBS to (172800 – 86400)/900 = 96. If the start times of the two sets are different, use the earlier start time, i.e., the start time of the first set.

If NWBS is set to a negative number, then NWBS determines how many snaps in the fort.22[1-4] should be skipped before the values in the files are used. This is useful when the fort.22[1-4] starts earlier than an ADCIRC run.

# If NWS=+12, and if a hot start run is attempted from the 86400th time step, and if the first set, fort.221 and fort.222 files, starts at the -86400th time step, and if WTIMINC is set to 900 in the fort.15, then you should set NWBS to (-86400-0)/900 = -96. If the start times of the two sets are different, use the earlier start time, i.e., the start time of the first set.
# If NWS=-12, and if a hot start run is attempted from the 86400th time step, and if the first set, fort.221 and fort.222 files, starts at the -86400th time step, and if WTIMINC is set to 900 in the fort.15, then you should set NWBS to (-86400-86400)/900 = -192. If the start times of the two sets are different, use the earlier start time, i.e., the start time of the first set.

=== Notes ===

# When the basin and region scale grids are both used in ADCIRC, data from the region scale grid takes precedence over data from the basin scale grid in the areas where the two grids overlap.
# If the fort.22[1-4] files are shorter in time than the duration of an ADCIRC run, the fort.22[1-4] will run out of data. However, the file reading error should be safely caught in ADCIRC and the computation will continue with blank snaps.

==WTIMINC in fort.15==

Although the WIN/PRE files contain datetime and timestepping information for the input data, ''WTIMINC'' must be set to the timestep of the input files (in seconds). This limitation locks all nested grid inputs to the same input timesteps, and requires that the input timesteps are constant for the duration of the input files, although the start and end times of the nested input overlay sets may differ.

== File Formatting==

Winds and pressure data formats are similar. The header format is the same,
but in the wind file the header is followed by U then V components while
in the pressure file the header is followed by just pressures.

The file begins with a header indicating the starting and ending dates and is
followed by a grid/date header for each time step and the u and v components
of the wind in meters/second or pressures in millibars. Starting/Ending dates
are in YYYYMMDDHH format where:

YYYY 4-character Year
MM 2-character Month
DD 2-character Day
HH 2-character Hour

''example WIN'':

OWI WWS Wind Output Ucomp,Vcomp in m/s Start:1995060600 End:1995060600
iLat= 67iLong= 67DX= 1.250DY= .833SWLat= 22.500SWlon= -82.500Dt=199506060000
-1.16856 -1.06439 -.84875 -1.03460 -1.50047 -2.09462 -2.80243 -3.55863
-4.24125 -4.84273 -5.59486 -5.37088 -5.30224 -5.12534 -4.89537 -4.67412
-4.49203 -4.35772 -4.26612 -4.20260 -4.14746 -4.08396 -4.00686 -3.92213
-3.83615 -3.74765 -3.65182 -3.54998 -3.45299 -3.37660 -3.32959 -3.28037
-3.10631 -2.67723 -2.08363 -1.53773 -1.12623 -.83526 -.62870 -.47371
[rest deleted]

* iLat is the number of parallels
* iLong is the number of meridians
* DX is the grid spacing in degrees of longitude
* DY is the grid spacing in degrees of latitude
* SWLat is the latitude of the South West corner
* SWlon is the longitude of the South West corner
* Dt is the date/time in YYYYMMDDHHmm (same as master header date format but with mm Minutes as well)

The number of grid points is iLat*iLong, the u component of the winds in meters/second is followed by the v component.

=== Sample code===
Sample fortran to read a win file (first time step only):

c Read in begining/ending dates of win file
10 format (t56,i10,t71,i10)
read (20,10) date1,date2

c Read Grid Specifications/Date
11 format (t6,i4,t16,i4,t23,f6.0,t32,f6.0,t44,f8.0,t58,f8.0,t69,i10,i2)
read (20,11) iLat, iLong, dx, dy, swlat, swlong, lCYMDH, iMin

c Read U/V Components of the wind
12 format (8f10.0)
read (20,12) ((uu(i,j),i=1,ilong),j=1,ilat)
read (20,12) ((vv(i,j),i=1,ilong),j=1,ilat)

Latitude and Longitude for each point can be calculated as follows:

do 20 icnt = 1,iLat
slat(icnt) = SWlat + (icnt - 1) * DY
20 continue

do 30 jcnt = 1,iLong
slon(jcnt) = SWlong + (jcnt - 1) * DX
30 continue

Supplemental meteorological/wave/ice parameters

2020-06-17T15:51:26Z

Alexcrosby: add nws13

{| class="wikitable" border="1" style="text-align: center"
|-
! Meteorological Data Format
! [[#Forcing Abbreviations|Forcing]]
! <code>[[NWS]]</code> Value
! <code>[[WTIMINC]]</code> Line
! [[#Requirements|Requirements]]
! [[#Notes|Notes]]
|-
| '''none'''
| nonexistent
| 0
| nonexistent
| none
| none
|- style="background:#efefef;"
| '''wind stress, every node, every timestep'''
| m
| 1
| nonexistent
| f22
| <ref group="note" name="c"><code>NWS</code> formats 1, 2, and 7 do not support the use of ice coverage (fort.25) files.</ref>
|- style="background:#efefef;"
|
| m, rs
| 101
| <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a">Radiation stress time increment (<code>RSTIMINC</code>) represents the time increment between the datasets in the fort.23 file (in seconds).</ref>
|- style="background:#efefef;"
|
| m, sw
| 301
| <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"><code>RSTIMINC</code> represents the span of ADCIRC simulation time that passes between calls to the coupled wave model.</ref>
|- style="background:#efefef;"
|
| m, st
| 401
| <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|-
| '''wind stress, every node, every <code>WTIMINC</code>'''
| m
| 2
| <code>WTIMINC</code>
| f22
| <ref group="note" name="c"></ref>
|-
|
| m, rs
| 102
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 302
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 402
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
| '''US Navy Fleet Numeric'''
| m
| 3
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code>
| f22
| none
|- style="background:#efefef;"
|
| m, rs
| 103
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw
| 303
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st
| 403
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, rs, ic
| 12103
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, f23, f25
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw, ic
| 12303
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, A+S, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st, ic
| 12403
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, STW, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, ic
| 12003
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>cice_timinc</code>
| f22, f25
| none
|-
| '''PBL/JAG'''
| m
| 4
| <code>WTIMINC</code>
| f22
| none
|-
|
| m, rs
| 104
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 304
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 404
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|-
|
| m, rs, ic
| 12104
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, f23, f25
| <ref group="note" name="a"></ref>
|-
|
| m, sw, ic
| 12304
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, A+S, f25
| <ref group="note" name="b"></ref>
|-
|
| m, st, ic
| 12404
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, STW, f25
| <ref group="note" name="b"></ref>
|-
|
| m, ic
| 12004
| <code>WTIMINC</code> <code>cice_timinc</code>
| f22, f25
| none
|- style="background:#efefef;"
| '''wind velocity, every node, every <code>WTIMINC</code>'''
| m
| 5
| <code>WTIMINC</code>
| f22
| none
|- style="background:#efefef;"
|
| m, rs
| 105
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw
| 305
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st
| 405
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, rs, ic
| 12105
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, f23, f25
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw, ic
| 12305
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, A+S, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st, ic
| 12405
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, STW, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, ic
| 12005
| <code>WTIMINC</code> <code>cice_timinc</code>
| f22, f25
| none
|-
| '''wind velocity, rectangular grid, every <code>WTIMINC</code>'''
| m
| 6
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code>
| f22
| none
|-
|
| m, rs
| 106
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 306
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 406
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|-
|
| m, rs, ic
| 12106
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, f23, f25
| <ref group="note" name="a"></ref>
|-
|
| m, sw, ic
| 12306
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, A+S, f25
| <ref group="note" name="b"></ref>
|-
|
| m, st ,ic
| 12406
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, STW, f25
| <ref group="note" name="b"></ref>
|-
|
| m, ic
| 12006
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>cice_timinc</code>
| f22, f25
| none
|- style="background:#efefef;"
| '''wind stress, regular grid, every <code>WTIMINC</code>'''
| m
| 7
| <code>WTIMINC</code>
| f22
| <ref group="note" name="c"></ref>
|- style="background:#efefef;"
|
| m, rs
| 107
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw
| 307
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st
| 407
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|-
| '''symmetric vortex model'''
| m
| 8
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code>
| f22
| none
|-
|
| m, rs
| 108
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 308
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 408
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|-
|
| m, rs, ic
| 12108
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, f23, f25
| <ref group="note" name="a"></ref>
|-
|
| m, sw, ic
| 12308
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, A+S, f25
| <ref group="note" name="b"></ref>
|-
|
| m, st, ic
| 12408
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, STW, f25
| <ref group="note" name="b"></ref>
|-
|
| m, ic
| 12008
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code>
| f22, f25
| none
|- style="background:#efefef;"
| '''asymmetric vortex model (no longer available)'''
| n/a
| 9
| n/a
| n/a
| none
|-
| '''National Climatic Data Center GFS'''
| m
| 10
| <code>WTIMINC</code>
| f2xx+
| none
|-
|
| m, rs
| 110
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f2xx+, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 310
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f2xx+, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 410
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f2xx+, STW
| <ref group="note" name="b"></ref>
|-
|
| m, rs, ic
| 12110
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f2xx+, f23, f25
| <ref group="note" name="a"></ref>
|-
|
| m, sw, ic
| 12310
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f2xx+, A+S, f25
| <ref group="note" name="b"></ref>
|-
|
| m, st, ic
| 12410
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f2xx+, STW, f25
| <ref group="note" name="b"></ref>
|-
|
| m, ic
| 12010
| <code>WTIMINC</code> <code>cice_timinc</code>
| f2xx+, f25
| none
|- style="background:#efefef;"
| '''National Weather Service ETA 29km'''
| m
| 11
| nonexistent
| f22
| none
|- style="background:#efefef;"
|
| m, rs
| 111
| <code>RSTIMINC</code>
| f22, f23
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw
| 311
| <code>RSTIMINC</code>
| f22, A+S
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st
| 411
| <code>RSTIMINC</code>
| f22, STW
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, rs, ic
| 12111
| <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, f23, f25
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw, ic
| 12311
| <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, A+S, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st, ic
| 12411
| <code>RSTIMINC</code> <code>cice_timinc</code>
| f22, STW, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m,ic
| 12011
| <code>cice_timinc</code>
| f22, f25
| none
|-
| '''Oceanweather Inc (OWI)'''
| m
| 12
| <code>WTIMINC</code>
| f22x
| none
|-
|
| m, rs
| 112
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22x, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 312
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22x, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 412
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22x, STW
| <ref group="note" name="b"></ref>
|-
|
| m, rs, ic
| 12112
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22x, f23, f25
| <ref group="note" name="a"></ref>
|-
|
| m, sw, ic
| 12312
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22x, A+S, f25
| <ref group="note" name="b"></ref>
|-
|
| m, st, ic
| 12412
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22x, STW, f25
| <ref group="note" name="b"></ref>
|-
|
| m, ic
| 12012
| <code>WTIMINC</code> <code>cice_timinc</code>
| f22x, f25
| none
|- style="background:#efefef;"
| '''Oceanweather Inc (OWI) NetCDF'''
| m
| 13
| <code>WTIMINC</code>
| f22nc
| [[NWS13]]
|- style="background:#efefef;"
|
| m, rs
| 113
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22nc, f23
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw
| 313
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22nc, A+S
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st
| 413
| <code>WTIMINC</code> <code>RSTIMINC</code>
| f22nc, STW
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, rs, ic
| 12113
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22nc, f23, f25
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw, ic
| 12313
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22nc, A+S, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st, ic
| 12413
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| f22nc, STW, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, ic
| 12013
| <code>WTIMINC</code> <code>cice_timinc</code>
| f22nc, f25
| none
|-
| '''H*Wind'''
| m
| 15
| <code>WTIMINC</code>
| hwind+,f22
| none
|-
|
| m, rs
| 115
| <code>WTIMINC</code> <code>RSTIMINC</code>
| hwind+,f22, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 315
| <code>WTIMINC</code> <code>RSTIMINC</code>
| hwind+,f22, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 415
| <code>WTIMINC</code> <code>RSTIMINC</code>
| hwind+,f22, STW
| <ref group="note" name="b"></ref>
|-
|
| m, rs, ic
| 12115
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| hwind+,f22, f23, f25
| <ref group="note" name="a"></ref>
|-
|
| m, sw, ic
| 12315
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| hwind+,f22, A+S, f25
| <ref group="note" name="b"></ref>
|-
|
| m, st, ic
| 12415
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| hwind+,f22, STW, f25
| <ref group="note" name="b"></ref>
|-
|
| m, ic
| 12015
| <code>WTIMINC</code> <code>cice_timinc</code>
| hwind+,f22, f25
| none
|- style="background:#efefef;"
| '''Geophysical Fluid Dynamics Laboratory (GFDL) Model'''
| m
| 16
| <code>WTIMINC</code>
| gfdl+,f22
| none
|- style="background:#efefef;"
|
| m, rs
| 116
| <code>WTIMINC</code> <code>RSTIMINC</code>
| gfdl+,f22, f23
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw
| 316
| <code>WTIMINC</code> <code>RSTIMINC</code>
| gfdl+,f22, A+S
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st
| 416
| <code>WTIMINC</code> <code>RSTIMINC</code>
| gfdl+,f22, STW
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, rs, ic
| 12116
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| gfdl+,f22, f23, f25
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw, ic
| 12316
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| gfdl+,f22, A+S, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st, ic
| 12416
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| gfdl+,f22, STW, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, ic
| 12016
| <code>WTIMINC</code> <code>cice_timinc</code>
| gfdl+,f22, f25
| none
|-
| '''Dynamic Asymmetric Model'''
| m
| 19
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code>
| pp,f22
| none
|-
|
| m, rs
| 119
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code>
| pp, f22, f23
| <ref group="note" name="a"></ref>
|-
|
| m, sw
| 319
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code>
| pp, f22, A+S
| <ref group="note" name="b"></ref>
|-
|
| m, st
| 419
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code>
| pp, f22, STW
| <ref group="note" name="b"></ref>
|-
|
| m, rs, ic
| 12119
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| pp, f22, f23, f25
| <ref group="note" name="a"></ref>
|-
|
| m, sw, ic
| 12319
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| pp, f22, A+S, f25
| <ref group="note" name="b"></ref>
|-
|
| m, st, ic
| 12419
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| pp, f22, STW, f25
| <ref group="note" name="b"></ref>
|-
|
| m, ic
| 12019
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code>
| pp, f22, f25
| none
|- style="background:#efefef;"
| '''Generalized Asymmetric Holland Model (GAHM)'''
| m
| 20
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code>
| pp, f22
| none
|- style="background:#efefef;"
|
| m, rs
| 120
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code>
| pp, f22, f23
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw
| 320
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code>
| pp, f22, A+S
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st
| 420
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code>
| pp, f22, STW
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, rs, ic
| 12120
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| pp, f22, f23, f25
| <ref group="note" name="a"></ref>
|- style="background:#efefef;"
|
| m, sw, ic
| 12320
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| pp, f22, A+S, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, st, ic
| 12420
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code> <code>cice_timinc</code>
| pp, f22, STW, f25
| <ref group="note" name="b"></ref>
|- style="background:#efefef;"
|
| m, ic
| 12020
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>cice_timinc</code>
| pp, f22, f25
| none
|- style="background:#efefef;"
|}

===Forcing Abbreviations===
: '''m''' - meteorology
: '''rs''' - Wave radiation stress in an analyst-supplied fort.23 input file
: '''sw''' - Wave coupling using a simulataneously executing coupled SWAN model
: '''st''' - Wave coupling using a simultaneously executing ESMF coupled STWAVE model
: '''ic''' - Ice coverage using an analyst-supplied ice coverage data files

===Requirements===
: '''f22''' - Requires analyst-supplied fort.22 meteorological forcing file.
: '''f2xx+''' - Requires at least two fort.2xx meteorological forcing files from the GFS model. See fort.22 documentation for file naming and formatting details.
: '''f22x''' - Requires datasets of pressure and wind data in OWI formatted fort.221 and fort.222 files respectively, optionally including nested wind and pressure in fort.223 and fort.224 files. See fort.22 documentation for details.
: '''hwind+''' - Requires two or more meteorological forcing files from the H*Wind model. See fort.22 documentation for details.
: '''gfdl+''' - Requires two or more meteorological forcing files from the GFDL model. See fort.22 documentation for details.
: '''pp''' - Requires preprocessing of the ATCF formatted track file using the ASymmetric Wind Input Preprocessor (aswip) program (distributed with ADCIRC) prior to use as input for this parametric vortex model.
: '''f23''' - Requires analyst-supplied fort.23 wave radiation stress input file.
: '''A+S''' - Requires ADCIRC+SWAN executable and input files for the coupled version of SWAN.
: '''STW''' - Requires ESMF-coupled ADCIRC and STWAVE and input files for STWAVE.
: '''f25''' - Requires analyst-supplied fort.25 ice coverage input file as well as a fort.225 basin scale ice coverage file and possibly an optional fort.227 region scale ice coverage file.

===Notes===
<references group="note" />

NWS

2020-06-17T15:26:59Z

Alexcrosby: add NWS13

'''<code>NWS</code>''' is a parameter in the [[fort.15 file]] that selects the meteorological forcing input type. One of the key advantages of ADCIRC is its ability to handle various meteorological input formats or generate tropical cyclone pressure and wind velocity fields from best-track data using internal parametric vortex generation algorithms. Special care must be taken with the selection of the NWS value and associate meteorological input file formats.

== Parameter Summary ==
The following table is a summary of possible <code>NWS</code> values, their description, and associated meteorological input files (required and optional).

{| class="wikitable" border="1"
|-
! <code>NWS</code> Value
! Short-name
! Description
! Required Input Files
! Optional Input Files
|-
| 1
| Wind stress, every node, every timestep
| Wind stress and atmospheric pressure are read in at all grid nodes at every model time step from the [[fort.22_file_format#NWS = 1 or 101|fort.22 file]]
| [[fort.22_file_format#NWS = 1 or 101|fort.22]]
|
|-
| 2
| Wind stress, every node, every [[WTIMINC]]
| 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 [[fort.22_file_format#NWS = 2, -2, 102 or -102|fort.22 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 in the [[fort.15_file_format|fort.15 file]].
| [[fort.22_file_format#NWS = 2, -2, 102 or -102|fort.22]]
|
|-
| 3
| US Navy Fleet Numeric
| Wind velocity is read in from a wind file from the [[fort.22_file_format#NWS = 3 or 103, Fleet Numeric Format|fort.22 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 describing the Fleet Numeric wind file must be specified in the [[fort.15_file_format|fort.15 file]].
| [[fort.22_file_format#NWS = 3 or 103, Fleet Numeric Format|fort.22]]
|
|-
| 4
| PBL/JAG
| Wind velocity and atmospheric pressure are read in (PBL/JAG format) at selected ADCIRC grid nodes from the [[fort.22_file_format#NWS = 4, -4, 104 or -104 - PBL Hurricane Model format|fort.22]] 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.
| [[fort.22_file_format#NWS = 4, -4, 104 or -104 - PBL Hurricane Model format|fort.22]]
|
|-
| 5
| Wind velocity, every node, every [[WTIMINC]]
| Wind velocity and atmospheric pressure are read in at all grid nodes from the [[fort.22_file_format#NWS = 5, -5, 105, or -105|fort.22]] 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.
| [[fort.22_file_format#NWS = 5, -5, 105, or -105|fort.22]]
|
|-
| 6
| wind velocity, rectangular grid, every [[WTIMINC]]
| Meteorological data (U,V,P) is input on a rectangular grid (either in Longitude, Latitude or Cartesian coordinates, consistent with the grid coordinates) and interpolated in space onto the ADCIRC grid. Wind velocity (U,V @ 10 m above the water surface) must be input in units of m/s and surface atmospheric pressure (P) must be input in units of Pascals = Newtons/square meter. The meteorological grid MUST cover the entire ADCIRC mesh; that is, the ADCIRC mesh must be ENTIRELY within the meteorological grid or an error will result.
| [[fort.22_file_format#NWS = 6 or 106|fort.22]]
|
|-
| 7
| Wind stress, regular grid, every [[WTIMINC]]
| Surface stress and pressure values are read in on a regular grid from the [[fort.22_file_format|fort.22 file]].
| [[fort.22_file_format#NWS = 7 or -7|fort.22]]
|
|-
| 8
| Symmetric Holland Vortex
| Wind velocity and atmospheric pressure are calculated at every node on the fly by ADCIRC internally using the Dynamic Holland model.
| [[Fort.22_file_format#NWS_.3D_8|fort.22]]
|
|-
| 10
| NCDC GFS
| 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.
| [[fort.200_file_format|fort.200, fort.200+N, fort.200+2*N, fort.200+3*N,….,]] where N is the time interval (in hours) between successive meteorological data
|
|-
| 11
| National Weather Service Eta-29 file
| 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
| [[fort.200_file_format|fort.200, fort.201, fort.202, fort.203,….,]]
|
|-
| 12 ([[NWS12]])
| OWI ASCII, every [[WTIMINC]]
| Wind velocities (U10, V10) and atmospheric sea level pressure (SLP) are provided in the OWI ASCII format on one to three rectangular (lat/lon) grid(s)
| [[Fort.22_file_format#NWS_.3D_12|fort.22]], [[fort.221]], [[fort.222]]
| [[fort.223]], [[fort.224]], [[fort.217]], [[fort.218]]
|-
| 13 ([[NWS13]]) {{ADC version|version=55|relation=ge}}
| OWI NetCDF
| Wind velocities (U10, V10) and atmospheric sea level pressure (SLP) fields are provided in the OWI NetCDF format as 1 or more meshgrid overlays stored in netCDF groups, supporting storm following grids on overlay 2 and on.
| [[NWS13]]
|
|-
| 14 / -14 {{ADC version|version=55|relation=ge}}
| GRIB2/NetCDF Binary, every [[WTIMINC]]
| Gridded data of wind velocities (U10, V10) and atmospheric sea level pressure (SLP) are provided in GRIB2 (e.g., GFS, CFSv2) or NetCDF (e.g., ERA5, WRF) binary files. Gridded data may be on a standard rectangular lat/lon grid, a [https://en.wikipedia.org/wiki/Gaussian_grid Gaussian grid], or a projected WRF-like grid. Requires that ADCIRC is compiled with DATETIME, NetCDF and if required, GRIB2 flags enabled (the static libraries must be compiled). Will find and read time-snaps based on the reference date, [[NCDATE]] located near or at the bottom of the [[fort.15_file_format|fort.15 file]] taking into account hot-start times etc. If the negative value is used, OWI ASCII (see NWS = 12) meteorology will overwrite the GRIB2/NetCDF meteorology data in the overlap region (except during the "skipping OWI time snap" phase).
| [[fort.22x.grb2 file|fort.221.grb2, fort.222.grb2]] '''or''' [[Fort.22_file_format#NWS_.3D_14|fort.22]], [[fort.221.nc]], [[fort.222.nc]]
|
|-
| 15
| HWIND
| Uses data assimilated snapshots of the wind velocity fields of tropical cyclones that are produced by the NOAA Hurricane Research Division (HRD)
| [[fort.22_file_format#NWS = 15|fort.22]]
| Additional HWIND files specified in the [[fort.22_file_format#NWS = 15|fort.22]] file
|-
| 16
| GFDL
| GFDL model output files produced by the Geophysical Fluid Dynamics Laboratory at NOAA. Each ASCII GFDL model output file contains one or more nested grid dataset where the nested grids are allowed to change in time. Coarse grid data is not stored where finer nest data is given.
| [[fort.22_file_format#NWS = 16|fort.22]]
| Additional GFDL files specified in the [[fort.22_file_format#NWS = 16|fort.22]] file
|-
| 19
| Dynamic Asymmetric Model
| Wind velocity and atmospheric pressure are calculated at exact finite element mesh node locations and directly coupled to ADCIRC at every time step using the asymmetric hurricane vortex formulation based on the Holland gradient wind model. The input file is assumed to correspond to the ATCF Best Track/Objective Aid/Wind Radii Format. This option uses the radii at specific wind speeds (34, 50, 64, 100 knots) reported in the four quadrants (NE, SE, SW, NW) of the storm to calculate the radius of maximum winds as a function of the azimuthal angle. Garret’s formula is used to compute wind stress from the wind velocity. This option allows the user to set a value for Rmax and Holland B Parameter. Additionally the user can select the isotachs to be used for each of the 4 quadrants. The utility program aswip_1.0.3.F located in the /wind folder will generate the NWS=19 formatted file from a NWS=9 formatted fort.22 input file.
| [[fort.22_file_format#NWS = 19|fort.22]]
|
|-
| 20
| Generalized Asymmetric Holland Model
| The Generalized Asymmetric Holland Model (GAHM) provides a set of theoretical and practical improvements over previous parametric meteorological vortex models in ADCIRC. The track file format is similar to that of the older Dynamic Asymmetric Model (NWS = 19) but with 8 additional columns of data.
| [[fort.22_file_format#NWS = 20, Generalized Asymmetric Holland Model (GAHM)|fort.22]]
|
|}

==Extended NWS with Ice + Waves==
The following presents a summary of the extended <code>NWS</code> values to included ice-coverage and/or wind wave-coupling

{| class="wikitable" border="1"
|-
! style="font-weight:bold;" |Meteorological Data Format
! style="font-weight:bold;" |Met. Only
! style="font-weight:bold;" |Met. plus Waves from fort.23
! style="font-weight:bold;" |Met. plus Waves SWAN
! style="font-weight:bold;" |Met. plus Waves STWAVE
! style="font-weight:bold;" |Met. plus Ice Coverage, Waves off
! style="font-weight:bold;" |Met. plus Ice Coverage OWI-like format plus Waves from fort.23
! style="font-weight:bold;" |Met. plus Ice Coverage OWI-like format plus Waves from SWAN
! style="font-weight:bold;" |Met. plus Ice Coverage OWI-like format plus Waves from STWAVE
|-
|none
| 0
| n/a
| n/a
| n/a
| n/a
| n/a
| n/a
|-
|wind stress, every node, every timestep
| 1
| 101
| 301
| 401
|
| 12101
| 12301
| 12401
|-
|wind stress, every node, every WTIMINC
| 2
| 102
| 302
| 402
|
| 12102
| 12302
| 12402
|-
|US Navy Fleet Numeric
| 3
| 103
| 303
| 403
|
| 12103
| 12303
| 12403
|-
|PBL/JAG
| 4
| 104
| 304
| 404
|
| 12104
| 12304
| 12404
|-
|wind velocity, every node, every WTIMINC
| 5
| 105
| 305
| 405
|
| 12105
| 12305
| 12405
|-
|wind velocity, rectangular grid, every WTIMINC
| 6
| 106
| 306
| 406
|
| 12106
| 12306
| 12406
|-
|wind stress, regular grid, every WTIMINC
| 7
| 107
| 307
| 407
|
| 12107
| 12307
| 12407
|-
|symmetrc vortex model
| 8
| 108
| 308
| 408
|
| 12108
| 12308
| 12408
|-
|asymmetric vortex model (no longer available)
| n/a
| n/a
| n/a
| n/a
| n/a
| n/a
| n/a
| n/a
|-
|National Weather Service AVN
| 10
| 110
| 310
| 410
|
| 12110
| 12310
| 12410
|-
|National Weather Service ETA 29km
| 11
| 111
| 311
| 411
|
| 12111
| 12311
| 12411
|-
|Oceanweather Inc (OWI)
| 12
| 112
| 312
| 412
|
| 12112
| 12312
| 12412
|-
|Oceanweather Inc (OWI) NetCDF
| 13
| 113?
| 313?
| 413?
|
| 12113?
| 12313?
| 12413?
|-
|GRIB2/NetCDF
| 14
| 114
| 314
| 414
| 14014 (GRIB2/NetCDF format ice)
| 14114 (GRIB2/NetCDF format ice)
| 14314 (GRIB2/NetCDF format ice)
| 14414 (GRIB2/NetCDF format ice)
|-
|H*Wind
| 15
| 115
| 315
| 415
|
| 12115
| 12315
| 12415
|-
|Dynamic Asymmetric Model
| 19
| 119
| 319
| 419
|
| 12119
| 12319
| 12419
|-
|Generalized Asymmetric Holland Model
| 20
| 120
| 320
| 420
|
| 12120
| 12320
| 12420
|
|}

NWS13

2020-06-15T19:52:25Z

Alexcrosby: /* Step 2: Apply intermediate input grid to mesh */ add language about fixed basin overlay

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for the newer NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|400px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

==Interpolation Details==

[[File:Ch maxmin interp timeseries.png|300px|thumb|right|Aliasing of peak storm conditions in time.]]

[[File:Ch movegrid interp spatial.png|300px|thumb|right|Spatial aliasing of peak wind speeds.]]

The [[NWS13]] met module implements a multi-step interpolation procedure, primarily to minimize aliasing of the wind and pressure fields in time and space.

The process occurs as follows:

===Step 1: Time/space on input grid(s)===

Input fields are interpolated on the input grid (in time, and space if necessary) to the intermediate timesteps specified in the ''fort.15'' parameter '''WTIMINC'''.

===Step 2: Apply intermediate input grid to mesh===

The gridded intermediate timesteps are interpolated in space on to the ADCIRC mesh, appropriately overlaying multiple input grids by rank as supplied. At this point the inputs are represented on the mesh at '''WTIMINC''' timesteps.

'''NB:''' For the lowest ranked overlay, the grid-to-mesh interpolation weights are pre-computed, which means that this grid cannot be a storm-following moving grid. For all additional overlays, the weights are dynamically updated.

===Step 3: Time interpolation to model timestep===

At each model computational timestep ('''DTDP''') the inputs at intermediate timesteps as represented on the mesh are interpolated in time to the appropriate model timestep node-by-node.

[[File:nws13_interp1.png|800px]]

[[File:nws13_interp2.png|800px]]

NWS13

2020-06-15T19:49:41Z

Alexcrosby: /* Motivation */ enlarge domain thumbnail

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for the newer NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|400px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

==Interpolation Details==

[[File:Ch maxmin interp timeseries.png|300px|thumb|right|Aliasing of peak storm conditions in time.]]

[[File:Ch movegrid interp spatial.png|300px|thumb|right|Spatial aliasing of peak wind speeds.]]

The [[NWS13]] met module implements a multi-step interpolation procedure, primarily to minimize aliasing of the wind and pressure fields in time and space.

The process occurs as follows:

===Step 1: Time/space on input grid(s)===

Input fields are interpolated on the input grid (in time, and space if necessary) to the intermediate timesteps specified in the ''fort.15'' parameter '''WTIMINC'''.

===Step 2: Apply intermediate input grid to mesh===

The gridded intermediate timesteps are interpolated in space on to the ADCIRC mesh, appropriately overlaying multiple input grids by rank as supplied. At this point the inputs are represented on the mesh at '''WTIMINC''' timesteps.

===Step 3: Time interpolation to model timestep===

At each model computational timestep ('''DTDP''') the inputs at intermediate timesteps as represented on the mesh are interpolated in time to the appropriate model timestep node-by-node.

[[File:nws13_interp1.png|800px]]

[[File:nws13_interp2.png|800px]]

NWS13

2020-06-15T19:45:18Z

Alexcrosby: /* Interpolation Details */ tweak steps formatting

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for the newer NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|200px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

==Interpolation Details==

[[File:Ch maxmin interp timeseries.png|300px|thumb|right|Aliasing of peak storm conditions in time.]]

[[File:Ch movegrid interp spatial.png|300px|thumb|right|Spatial aliasing of peak wind speeds.]]

The [[NWS13]] met module implements a multi-step interpolation procedure, primarily to minimize aliasing of the wind and pressure fields in time and space.

The process occurs as follows:

===Step 1: Time/space on input grid(s)===

Input fields are interpolated on the input grid (in time, and space if necessary) to the intermediate timesteps specified in the ''fort.15'' parameter '''WTIMINC'''.

===Step 2: Apply intermediate input grid to mesh===

The gridded intermediate timesteps are interpolated in space on to the ADCIRC mesh, appropriately overlaying multiple input grids by rank as supplied. At this point the inputs are represented on the mesh at '''WTIMINC''' timesteps.

===Step 3: Time interpolation to model timestep===

At each model computational timestep ('''DTDP''') the inputs at intermediate timesteps as represented on the mesh are interpolated in time to the appropriate model timestep node-by-node.

[[File:nws13_interp1.png|800px]]

[[File:nws13_interp2.png|800px]]

NWS13

2020-06-15T19:43:00Z

Alexcrosby: /* Motivation */ fix bad edit

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for the newer NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|200px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

==Interpolation Details==

[[File:Ch maxmin interp timeseries.png|300px|thumb|right|Aliasing of peak storm conditions in time.]]

[[File:Ch movegrid interp spatial.png|300px|thumb|right|Spatial aliasing of peak wind speeds.]]

The [[NWS13]] met module implements a multi-step interpolation procedure, primarily to minimize aliasing of the wind and pressure fields in time and space.

The process occurs as follows:

===Step 1: Time/space on input grid(s)===

Input fields are interpolated on the input grid (in time, and space if necessary) to the intermediate timesteps specified in the ''fort.15'' parameter '''WTIMINC'''.

===Step 2: Apply intermediate input grid to mesh===

The gridded intermediate timesteps are interpolated in space on to the ADCIRC mesh, appropriately overlaying multiple input grids by rank as supplied. At this point the inputs are represented on the mesh at '''WTIMINC''' timesteps.

===Step 3: ===

At each model computational timestep ('''DTDP''') the inputs at intermediate timesteps as represented on the mesh are interpolated in time to the appropriate model timestep node-by-node.

[[File:nws13_interp1.png|800px]]

[[File:nws13_interp2.png|800px]]

NWS13

2020-06-15T19:42:31Z

Alexcrosby: /* Motivation */ add the/typo

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for newer the NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|200px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

==Interpolation Details==

[[File:Ch maxmin interp timeseries.png|300px|thumb|right|Aliasing of peak storm conditions in time.]]

[[File:Ch movegrid interp spatial.png|300px|thumb|right|Spatial aliasing of peak wind speeds.]]

The [[NWS13]] met module implements a multi-step interpolation procedure, primarily to minimize aliasing of the wind and pressure fields in time and space.

The process occurs as follows:

===Step 1: Time/space on input grid(s)===

Input fields are interpolated on the input grid (in time, and space if necessary) to the intermediate timesteps specified in the ''fort.15'' parameter '''WTIMINC'''.

===Step 2: Apply intermediate input grid to mesh===

The gridded intermediate timesteps are interpolated in space on to the ADCIRC mesh, appropriately overlaying multiple input grids by rank as supplied. At this point the inputs are represented on the mesh at '''WTIMINC''' timesteps.

===Step 3: ===

At each model computational timestep ('''DTDP''') the inputs at intermediate timesteps as represented on the mesh are interpolated in time to the appropriate model timestep node-by-node.

[[File:nws13_interp1.png|800px]]

[[File:nws13_interp2.png|800px]]

NWS13

2020-06-15T19:41:28Z

Alexcrosby: /* Interpolation Details */ Flesh out the interpolation steps

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for newer NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|200px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

==Interpolation Details==

[[File:Ch maxmin interp timeseries.png|300px|thumb|right|Aliasing of peak storm conditions in time.]]

[[File:Ch movegrid interp spatial.png|300px|thumb|right|Spatial aliasing of peak wind speeds.]]

The [[NWS13]] met module implements a multi-step interpolation procedure, primarily to minimize aliasing of the wind and pressure fields in time and space.

The process occurs as follows:

===Step 1: Time/space on input grid(s)===

Input fields are interpolated on the input grid (in time, and space if necessary) to the intermediate timesteps specified in the ''fort.15'' parameter '''WTIMINC'''.

===Step 2: Apply intermediate input grid to mesh===

The gridded intermediate timesteps are interpolated in space on to the ADCIRC mesh, appropriately overlaying multiple input grids by rank as supplied. At this point the inputs are represented on the mesh at '''WTIMINC''' timesteps.

===Step 3: ===

At each model computational timestep ('''DTDP''') the inputs at intermediate timesteps as represented on the mesh are interpolated in time to the appropriate model timestep node-by-node.

[[File:nws13_interp1.png|800px]]

[[File:nws13_interp2.png|800px]]

NWS13

2020-06-15T19:06:04Z

Alexcrosby: Add some images, interpolation section

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for newer NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|200px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

==Interpolation Details==

[[File:Ch movegrid interp spatial.png]]

[[File:Ch maxmin interp timeseries.png]]

[[File:nws13_interp1.png]]

[[File:nws13_interp2.png]]

File:Nws13 interp2.png

2020-06-15T19:04:13Z

Alexcrosby:

File:Nws13 interp1.png

2020-06-15T19:03:51Z

Alexcrosby:

File:Ch movegrid interp spatial.png

2020-06-15T19:00:17Z

Alexcrosby: Alexcrosby uploaded a new version of File:Ch movegrid interp spatial.png

File:Ch maxmin interp timeseries.png

2020-06-15T18:59:52Z

Alexcrosby: Alexcrosby uploaded a new version of File:Ch maxmin interp timeseries.png

File:Ch maxmin interp timeseries.png

2020-06-15T18:59:22Z

Alexcrosby: Alexcrosby uploaded a new version of File:Ch maxmin interp timeseries.png

File:Ch maxmin interp timeseries.png

2020-06-15T18:56:38Z

Alexcrosby:

File:Ch movegrid interp spatial.png

2020-06-15T18:49:19Z

Alexcrosby:

NWS13

2020-06-15T18:37:11Z

Alexcrosby: /* Motivation */ Add overlay domain image

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields. In order to allow ADCIRC access to high quality and efficiently stored inputs the following features were added to the existing [[NWS12]] functionality for newer NetCDF version ([[NWS13]]).

[[File:overlay_domains.png|200px|thumb|right|Example of grid domains for multiple independent wind/pressure overlays, including storm-following.]]

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

File:Overlay domains.png

2020-06-15T18:31:37Z

Alexcrosby: Example of grid domains for multiple independent wind/pressure overlays.

== Summary ==
Example of grid domains for multiple independent wind/pressure overlays.

NWS13

2020-06-15T18:29:33Z

Alexcrosby: NWS13 Creation

=NWS13=

Oceanweather Inc. (OWI) NetCDF Meteorological Input Files

==Motivation==

A major source of error in ADCIRC can come from the accuracy and representation of the wind and pressure fields.

* Moving storm-centered grids
* Grids that can change size
* Curvilinear grids
* Arbitrary # of grid overlays
* New ADCIRC moving interpolation code
* Arbitrary & irregular timesteps

Some future-proofing attempts:

* Multi-resolution representation of tropical cyclone wind fields
* Be able to introduce additional meteorological parameters using the same format/NWS input
** Possibility to include wind stresses?
** Alternative reference heights?
** Ice information?
** Rainfall?

==NetCDF File Schema==

This description assumes some familiarity with NetCDF, HDF or other similar self-describing binary file formats, and in particular features like "groups" available in HDF5 and NetCDF4. Understanding of NetCDF conventions like Climate Forecast (CF) may also be helpful. For more information about NetCDF please visit the links below.

* https://www.unidata.ucar.edu/software/netcdf/
* https://www.hdfgroup.org/
* https://cfconventions.org/
* https://github.com/Unidata/netcdf4-python
* https://github.com/pydata/xarray

===''' '' OWI-NWS13 Convention '' '''===

'''NetCDF4 File''' contents:
* Group(s) – 1 group per grid or overlay
* Variables – U10/V10, PSFC
* Dimensions – time, yi, xi
* Attributes – grid rank/priority

'''Global Attributes''':
* ''group_order'': space separated list of group names reflecting their appropriate rank/order
* ''conventions'': should include “OWI-NWS13“ (Climate Forecast conventions (CF) seemingly don’t support NC groups)

'''Group Attributes''':
* ''rank'': integer representing the order of overlay/precedence in application to nodes

'''Group Dimensions''':
* ''time'' – length of time dimension
* ''yi'' – number of rows in spatial grid description
* ''xi'' – number of columns in spatial grid description

'''Group Variables''':
* ''U10'' (time, yi, xi), U-component of 10m WS (m/s)
* ''V10'' (time, yi, xi), V-component of 10m WS (m/s)
* ''PSFC'' (time, yi, xi), Surface Pressure (mb)
* ''lon'' (yi, xi) or (time, yi, xi), Longitude in Decimal Degrees
* ''lat'' (yi, xi) or (time, yi, xi), Latitude in Decimal Degrees
* ''time'' (time), Datetime-number with units of “minutes from YYYY-mm-dd HH:MM:SS”
* ''clon'' and ''clat'' (time), optional storm center coordinates for Powell drag

===Example===
netcdf fort.22 {

// global attributes:
:group_order = "Main JPM0135" ;
:institution = "Oceanweather Inc. (OWI)" ;
:conventions = "CF-1.6 OWI-NWS13" ;

group: Main {
dimensions:
yi = 211 ;
xi = 221 ;
time = 133 ;
variables:
float lon(yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float lat(yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 1 ;
} // group Main

group: JPM0135 {
dimensions:
time = 133 ;
yi = 501 ;
xi = 501 ;
variables:
int64 time(time) ;
time:units = "minutes since 1990-01-01T01:00:00" ;
time:calendar = "proleptic_gregorian" ;
float lat(time, yi, xi) ;
lat:_FillValue = NaNf ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:axis = "Y" ;
lat:coordinates = "time lat lon" ;
float lon(time, yi, xi) ;
lon:_FillValue = NaNf ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
lon:axis = "X" ;
lon:coordinates = "time lat lon" ;
float U10(time, yi, xi) ;
U10:_FillValue = NaNf ;
U10:units = "m s-1" ;
U10:coordinates = "time lat lon" ;
float V10(time, yi, xi) ;
V10:_FillValue = NaNf ;
V10:units = "m s-1" ;
V10:coordinates = "time lat lon" ;
float PSFC(time, yi, xi) ;
PSFC:_FillValue = NaNf ;
PSFC:units = "mb" ;
PSFC:coordinates = "time lat lon" ;
// group attributes:
:rank = 2 ;
} // group JPM0135
}

===Notes===

* Decoupling the yi/xi dimensions from lat/lon allows lat and lon to be 2-d arrays by depending on both dimensions
* Regular grids and Curvilinear grids
* Non-evenly spaced grids as long as they can be expressed in a 2-d "mesh-grid"
* Grids that change spatial resolution or position in time (but have consistent yi/xi array size)
* Each group/sub-grid can define the timesteps independently, including start and stop times
* Fill Value (and NetCDF packing/compression), and ieee nan floats supported

==fort.15 Configuration==

'''WTIMINC''': configurable grid-to-mesh interpolation timestep in seconds, separate from the input data timesteps. If the file contains storm-following grids, there may be some utility in setting this finer than the input timestep(s).

''&owiWindNetcdf'' fort.15 namelist with all inputs quoted as strings
* ''NWS13ColdStartString'': required cold start time of simulation formatted as 'YYYYMMDD.HHMMSS'
* ''NWS13WindMultiplier'': optional wind speed multiplier ('''DWM''' from [[NWS12]])
* ''NWS13File'': optional file name for netCDF file ( ''fort.22.nc'' default )
* ''NWS13GroupForPowell'': optional group # to use for Powell drag
''example'':
&owiWindNetcdf NWS13File='fort.22.nc' NWS13ColdStartString='20000706.000000' /

==Suggestions==

* Keep the spatial and temporal resolutions to only what is required
* Add sub-grids, more complex time dimensions, and complex lat/lon grid definitions only as necessary by sub-grid/group
* In most cases 1-hourly specified--if you have a moving-grid overlay and can rely on the built-in moving-aware interpolation
* Avoid discontinuities between overlays/grids
* Best case: the lowest rank grid should just be a less resolved version of exact same higher resolution fields that will be overlaid
* Lowest rank grid should probably cover the entire domain/mesh, and the entire model run time period

NWS12

2020-06-15T17:44:35Z

Alexcrosby: /* WTIMINC in fort.15 */ clarify input datetime requirement

NWS12

2020-06-15T17:41:49Z

Alexcrosby: /* WTIMINC in fort.15 */ add WTIMINC units

NWS12

2020-06-15T17:40:45Z

Alexcrosby: add wtiminc and fort.22 and fort.221-4 explainations

NWS12

2020-06-15T17:30:53Z

Alexcrosby: Created page with "=NWS12= Oceanweather Inc. (OWI) "WIN" and "PRE" file formats as supported in ADCIRC ==fort.22== NWS12 uses the '''fort.22''' file as a control file because the OWI format s..."

File formats

2020-06-15T17:03:51Z

Alexcrosby: Adding links to NWS12/13 descriptions

== ADCIRC File Formats ==

=== Input Files Contributor needed ===

'''Required''': Every ADCIRC run requires the following two input files:
*[[fort.14 file]] - Grid file: Defines the ADCIRC triangular finite element grid
*[[fort.15 file]] - Parameter file: Sets runtime parameters, frequency-dependent boundary forcing, and output options

'''Optional, frequently used''', depending on simulation configuration:
*[[fort.13 file]] - Nodal Attribute file: Defines parameters (e.g., Mannings N, canopy cover) that can be set at specific nodes.
*[[fort.22 file]] - Wind forcing file. The specific format of this file depends on the wind input format. See the NWS parameter in the fort.15 file description.

'''Optional''', depending on simulation forcing configuration:
*''For coupled SWAN runs'':
**[[fort.26 file]] - SWAN parameter file. Same format as a traditional SWAN input file, but with "SWAN unstructured grid" commands specific to the coupled ADCIRC+SWAN code.
**[[swaninit file]] - SWAN init file. This is the same as in a traditional SWAN run.

'''Meteorological Inputs''' (NWS#):
* Oceanweather (OWI) Formats [[NWS12]] and [[NWS13]]

=== Output Files Contributor needed ===

User:Alexcrosby

2018-08-01T13:07:21Z

Alexcrosby: Add some information about owi

== Alex Crosby ==

=== About Me ===
I am an ADCIRC and ADCIRC+SWAN user at Oceanweather Inc. (OWI), with a background in Ocean Engineering. At OWI, we specialize in providing highly-skilled atmospheric inputs for extreme weather events, and specifically tropical cyclones, to the ocean response modeling community, government and offshore industry.

=== About OWI ===
Since its formation in 1977, Oceanweather has been fully engaged with support divided between the private and public sector. In the public sector, the company performs basic and applied research in marine meteorology and ocean response numerical modeling, supported by both U.S. and foreign government agencies. Oceanweather staff continues to actively participate in international scientific conferences and research programs, and in open publication.

Oceanweather functions as a specialized consulting firm serving the coastal and ocean engineering communities with its unique capacity to integrate several areas of expertise into specification of definitive design data on the physical environment. Oceanweather's approach is to consistently develop and apply high-level technology to satisfy practical requirements in the areas of marine meteorology, ocean wave and current specification, ocean engineering, and statistics of environmental data.

In its long history, Oceanweather has performed dedicated hindcast studies and Joint Industry Projects (JIPs) in virtually every ocean basin in the world. Oceanweather offers an extensive selection of pre-computed hindcasts for fast-turnaround applications as well as the expertise to run dedicated hindcast studies for specific applications.

Since 1983, Oceanweather has operated a real-time forecasting division. The methodology follows a unique approach of optimally combining traditional weather forecasting (which retains the contributions of individual forecasters) and Oceanweather's high-level technology developed and applied in its hindcasting and consulting divisions. The forecast system includes a global wind and wave forecast system and high resolution regional applications.

=== Learn More ===

Here are some links that may be of interest:

http://oceanweather.com/news/

http://oceanweather.com/research/

http://oceanweather.com/forecast/About/

http://oceanweather.com/metocean/