https://wiki.adcirc.org/api.php?action=feedcontributions&user=Taylorgasher&feedformat=atomADCIRCWiki - User contributions [en]2024-03-28T15:00:27ZUser contributionsMediaWiki 1.38.1https://wiki.adcirc.org/index.php?title=Wind_Stress&diff=1144Wind Stress2024-03-22T18:34:19Z<p>Taylorgasher: /* Interpolating Roughness Lengths Before v55 */ adding video</p>
<hr />
<div>When wind blows over the water, it exerts a shear stress at the water surface that transfers horizontal momentum vertically downward across the air–sea interface, driving circulation. In ADCIRC, wind stress is an input forcing term, with several different formats provided. See the <code>[[NWS]]</code> parameter for available formats. In most cases, the exact wind stress to be applied to the model is not provided, therefore ADCIRC must determine how to convert a given wind speed to the actual stress applied at the ocean surface. This page covers the various aspects of this process, as well as the options available to the user. <br />
<br />
== Definition of Winds ==<br />
The characteristics of wind forcing are often broken down in three ways: <br />
# Whether the winds are considered to be over-water (termed "marine exposure") or over-land<br />
# The elevation above the sea (or ground) surface of the winds<br />
# The time-averaging (if any) that has been applied<br />
<br />
ADCIRC generally expects 10-meter, 10-minute winds at their actual exposure, although the exact expectations vary depending on the input type. For instance, when Holland-type wind inputs are provided (e.g. <code>NWS=8</code> or <code>NWS=20</code>), the wind speed is expected to be the '''1-minute [https://en.wikipedia.org/wiki/Maximum_sustained_wind maximum sustained wind]''' at 10 meters elevation. If marine-exposure winds are provided, then [[Fort.13_file#Surface_Roughness|surface roughness]] reductions may be needed<br />
<ref name="simiu1996">Simiu, E., Scanlan, R.H., 1996. Wind effects on structures: fundamentals and applications to design, 3rd ed. ed. John Wiley, New York.</ref><br />
<ref name="simiu2018">Simiu, E., Yeo, D., 2018. Wind effects on structures: modern structural design for wind, Fourth edition. ed. John Wiley & Sons, Hoboken, NJ.</ref><br />
. If winds are provided with a different averaging time, then an appropriate correction may be needed, though winds with averaging times of 10 to 60 minutes are generally considered to be quite similar; this is the so-called mesoscale gap. For recommendations on wind time-scale conversions not handled internally by ADCIRC, for tropical cyclones, see the WMO guidelines of Harper et al.<br />
<ref name="wmotcaveraging">Harper, B., Kepert, J., Ginger, J., 2010. Guidelines for converting between various wind averaging periods in tropical cyclone conditions (No. WMO/TD-No. 1555). WMO, Geneva, Switzerland.</ref><br />
<br />
== Roughness Reductions ==<br />
Reductions in wind speed to convert to the appropriate exposure come from a logarithmic boundary layer formulation (see, e.g. <ref name="simiu1996" /> <ref name="simiu2018" />) to determine a fraction <math>f</math> to reduce the winds, <br />
:<math>f=\left ( \frac{z_{0l}}{z_{0m}}\right ) ^{0.0706} \left ( \frac{\ln \frac{10}{z_{0l}}}{\ln \frac{10}{z_{0m}}} \right ) </math><br />
for marine roughness length <math>z_{0m}</math> and reduced ("land") roughness length <math>z_{0l}</math>. Wind speed is then reduced as, <br />
:<math>\mathbf{w}'=f\mathbf{w}=f [u,v]</math><br />
for x- and y- wind vector components <math>u</math> and <math>v</math>. The marine roughness length is, <br />
:<math>z_{0m}=\frac{0.018}{g} c_d \left \Vert \mathbf{w} \right \| </math><br />
for Charnock parameter <math>0.018</math>, drag coefficient <math>c_d</math> and acceleration due to gravity <math>g</math>. The wind drag coefficient is addressed below in [[#Converting Wind Velocity to Wind Stress|this section]]. As previously noted, the reduced ("land") roughness length <math>z_{0l}</math> is specified by the user via the [[Fort.13_file#Surface_Roughness|surface roughness]] nodal attribute. The fraction <math>f</math> is bounded on <math>[0,1]</math>, meaning the winds cannot be increased, nor change direction. <br />
<br />
=== Older Behavior ===<br />
====Interpolating Roughness Lengths Before v55====<br />
[[File:WindTraceV2.png|right|frameless|Comparison of output wind velocities using old and new methods.]]<br />
<br />
{{ADC version|version=55|relation=lt}}Before version 55, the directional wind reductions were applied by determining which of the 12 directional bins the wind velocity (at each time step) fell into, and using that roughness reduction, i.e. nearest neighbor interpolation. Starting in version 55, the roughness length is linearly (in angle space) interpolated between directional bins. In testing, this has been found to generally have a very small effect on water levels, but a notable effect on wind speeds, since time evolution of winds is smoother. It can have large localized effects on water levels in cases where there are large changes in neighboring roughness length bins coinciding with well-aligned winds, as in [[:File:MaxeleDiffRun13MinusRun12View1.png|this test case]] with Hurricane Isaac. <br />
[[File:Run03masterVsRun05interp trimmedAndAnnotatedTry7-min.gif|thumb|500px|Video of wind speeds before (left) and after (right) adding linear interpolation of surface roughness.]]<br />
<br clear=all><br />
<br />
====Roughness Reduction Bug Before v54====<br />
{{ADC version|version=54|relation=lt}}Before version 54, there was a bug in this calculation. The mistake and its effects are addressed in this PDF document: <u><span style="color:red">'''ADD A LINK TO A PDF HERE YOOOOO'''</span></u>.<br />
<br />
== Converting Wind Velocity to Wind Stress ==<br />
In ADCIRC, four formulations are available to convert wind velocities to the wind stresses applied in the momentum equations. Although there are several ways to control this, users are generally encouraged to use the [[metControl]] namelist in the [[fort.15]] file. The default drag formulation is the Garratt<br />
<ref name=garratt1977>Garratt, J.R., 1977. Review of Drag Coefficients over Oceans and Continents. Mon. Wea. Rev. 105, 915–929. https://doi.org/10.1175/1520-0493(1977)105<0915:RODCOO>2.0.CO;2</ref><br />
linear formula. An alternative for use with tropical cyclones is the Powell formulation,<br />
<ref>Powell, M.D., Vickery, P.J., Reinhold, T.A., 2003. Reduced drag coefficient for high wind speeds in tropical cyclones. Nature 422, 279–283. https://doi.org/10.1038/nature01481</ref><br />
which varies drag by the sector of the tropical cyclone. When ice coverage is included in the model, a wind drag formulation that accounts for this effect should be used. By default, if ice coverage input data are supplied, ADCIRC uses a cubic function of ice coverage, termed the "IceCube" drag formulation. Lastly, the "swell" drag law option allows users to utilize SWAN's drag formulation when employing the coupled model. <br />
<br />
In all cases, the actual wind drag coefficients determined by ADCIRC can be output to a [[fort.63]]-type file named [[winddrag.173]]. Output settings (file format, output start/end times, and output interval) match those of either the fort.63 or fort.73/74 files, ''I think'' fort.73/74. Outputting of this file is enabled by setting <code>outputWindDrag=.TRUE.</code> in the <code>&metControl</code> namelist of the [[Fort.15_file_format#Namelists|fort.15 file's namelist section]]. <br />
<br />
=== Garratt Drag Formulation ===<br />
This is the default wind drag formulation in ADCIRC. From Garratt (1977)<ref name=garratt1977></ref>, the formula is, <br />
:<math>c_d=0.001 \left ( 0.75+0.067 \left \Vert \mathbf{w} \right \| \right ) </math><br />
<br />
By default, ADCIRC puts an upper bound on the drag coefficient of <math>c_d\le0.0035</math>. This upper bound <code>WindDragLimit</code> can be changed via the [[metControl]] fort.15 namelist. <br />
<br />
=== Powell Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
Note that the code for the Powell drag law has not been configured to reverse orientation in the southern hemisphere, and so will produce the wrong results. For details on Powell, see [https://ccht.ccee.ncsu.edu/wind-drag-based-on-storm-sectors/ this post].<br />
<br />
=== IceCube Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:meteorology]]<br />
[[Category:physics]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=User:Taylorgasher&diff=1143User:Taylorgasher2024-03-22T18:25:23Z<p>Taylorgasher: </p>
<hr />
<div>My user page<br />
<br />
== etc. ==<br />
<nowiki><nowiki>'''not bold text''' ''not italic text'' not ADC version {{ADC version|version=-4E7|relation=ge}} </nowiki></nowiki><br />
<br />
<nowiki>A redirect: #REDIRECT [[Fort.13_file#Nodal_Attributes]]</nowiki><br />
<br />
<nowiki><!--comment text<br/><br />
<br />
<br />
(that can span multiple lines in the code)--></nowiki><!--the real comment text, sucka!!!--><br />
<br />
== gifo sho ==<br />
[[File:Run03masterVsRun05interp trimmedAndAnnotatedTry7-min.gif|frame|alt=or not?|oh yeah]]<br />
<br />
== syntax highlivin ==<br />
monty<br />
<syntaxhighlight lang="python" line='line'><br />
def quick_sort(arr):<br />
less = []<br />
pivot_list = []<br />
more = []<br />
if len(arr) <= 1:<br />
return arr<br />
else:<br />
pass<br />
</syntaxhighlight><br />
<br />
fortless<br />
<syntaxhighlight lang="fortran" line='line'><br />
! I N I T W I N D M O D U L E<br />
! ----------------------------------------------------------------<br />
subroutine initWindModule()<br />
use mesh, only : np<br />
call setMessageSource("initWindModule")<br />
#if defined(WIND_TRACE) || defined(ALL_TRACE)<br />
call allMessage(DEBUG,"Enter.")<br />
#endif<br />
allocate ( wvnx1(np),wvny1(np) )<br />
allocate ( wvnx2(np),wvny2(np) )<br />
allocate ( prn1(np) )<br />
allocate ( prn2(np) )<br />
<br />
C well this commenting approach does not work<br />
if(yourMom.eq.fat)then<br />
write(*,*)'ahahahahaha'<br />
endif !looks like this doesn't work<br />
IF((EyeLat(1).EQ.0.D0).OR.(EyeLon(1).EQ.0.D0).OR.<br />
& (EyeLat(2).EQ.0.D0).OR.(EyeLon(2).EQ.0.D0).OR.<br />
& (EyeLat(3).EQ.0.D0).OR.(EyeLon(3).EQ.0.D0))THEN<br />
FoundEye = .FALSE.<br />
ENDIF<br />
<br />
!.... tcm v49.16 20100617 added<br />
!.... convert background pressure from millibars to meters of water<br />
PRBCKGRND_MH2O = 100.0D0*PRBCKGRND/(RHOWAT0*G)<br />
prn1 = PRBCKGRND_MH2O<br />
prn2 = PRBCKGRND_MH2O<br />
<br />
CALL checkWindDragType()<br />
CALL mapWindDragFunctionPointer()<br />
<br />
#if defined(WIND_TRACE) || defined(ALL_TRACE)<br />
call allMessage(DEBUG,"Return.")<br />
#endif<br />
call unsetMessageSource()<br />
<br />
! ----------------------------------------------------------------<br />
END SUBROUTINE initWindModule<br />
! ----------------------------------------------------------------<br />
</syntaxhighlight><br />
== some mats ==<br />
:<math>a_b(c)=\left ( \frac{de^2}{\sqrt[6]{f+\alpha(\beta)}} \right ) ^{\Tau^\tau}</math><br />
<br />
<br />
<!--:<math>\{A|A\in\mathbb{E}\land\}</math>--><br />
<br />
:<math>\{ A \mid A \in \mathbb{E} \land \mathbb{E} - (N \cup R) \} </math><br />
for <math>A</math> Andrew, <math>\mathbb{E}</math> the entire space, <math>N</math> Nickelback fans, and <math>R</math> Republicans.<br />
<br />
== linky ==<br />
<nowiki>[[#test table| link to subsection or anchor in same page]]</nowiki>[[#test table| link to subsection or anchor in same page]]<br />
<br />
== test table ==<br />
but<br />
<br />
{| class="wikitable"<br />
|-<br />
| apple || pear<br />
|-<br />
| orange || grape <br />
|}<br />
<br />
srsly<br />
<br />
{| style="background-color: orange; border-style: solid; border-width: 2px"<br />
|-<br />
| <br />
{| style="border-style: solid; border-width: 4px"<br />
| ap || ple<br />
|}<br />
|<br />
{| style="border-style: solid; border-width: 4px"<br />
| pe || ar<br />
|}<br />
|-<br />
| <br />
{| style="border-style: solid; border-width: 4px"<br />
| ora || nge<br />
|}<br />
|<br />
{| style="border-style: solid; border-width: 4px"<br />
| gr || ape<br />
|}<br />
|}<br />
<br />
Some norma text<br />
<br />
<br />
== wind drag in/out notes ==<br />
see email with John, subject line "Outputting wind drag coefficients"<br />
<br />
<br />
winddrag.173<br />
or <br />
winddrag.173.nc<br />
<br />
outputWindDrag=.true.<br />
<br />
&metControl<br />
<br />
from ncdump -h winddrag.173.nc: <br />
<br />
double winddrag(time, node) ;<br />
winddrag:long_name = "wind drag coefficient at sea level" ;<br />
winddrag:standard_name = "wind drag coefficient" ;<br />
winddrag:coordinates = "time y x" ;<br />
winddrag:location = "node" ;<br />
winddrag:mesh = "adcirc_mesh" ;<br />
winddrag:units = "unitless" ;<br />
winddrag:_FillValue = -99999. ;<br />
<br />
<br />
<br />
<br />
<br />
== test transclus ==<br />
<!--{{:Manning's n at sea floor#model specification}}--><br />
<br />
<br />
<br />
<br />
== yup ==<br />
Internal tide energy conversion refers to the energy conversion from barotropic to baroclinic modes as surface tides flow over steep and rough topography in the deep ocean generating internal tides. The "lost" barotropic tidal energy is often accounted for through a linear friction term in large-scale numerical models that are barotropic or not fine-scaled enough to resolve the energy conversion. It is implemented in ADCIRC through a spatially varying [[nodal attribute]] called [[internal_tide_friction]], in the [[fort.13 file]].<br />
<br />
== Background and Theory ==<br />
For a review.<ref>C. Garrett, E. Kunze, Internal Tide Generation in the Deep Ocean, Annu. Rev. Fluid Mech. 39 (2007) 57–87. doi:10.1146/annurev.fluid.39.050905.110227.</ref><br />
<br />
How it was known that internal energy conversion is important to the global energy balance of the surface tides.<ref>G.D. Egbert, R.D. Ray, Significant dissipation of tidal energy in the deep ocean inferred from satellite altimeter data, Nature. 405 (2000) 775–778. doi:10.1038/35015531</ref><ref>G.D. Egbert, R.D. Ray, Estimates of M2 tidal energy dissipation from TOPEX/Poseidon altimeter data, J. Geophys. Res. Ocean. 106 (2001) 22475–22502. doi:10.1029/2000JC000699.</ref><br />
<br />
== Attribute Summary ==<br />
In a computational domain covering a large portion of the deep ocean it is critical to include the effect of internal tide energy conversion to obtain more accurate tidal solutions. The user should only elect to use the internal_tide_friction nodal attribute when tides are included in the simulation through tidal boundary conditions and tidal potential functions. The attribute is unnecessary for domains that are small in size and/or do not cover a significant portion of the deep ocean (taken here to mean the portion of the ocean excluding the continental shelf). <br />
<br />
ADCIRC reads the internal_tide_friction attribute in as the ''IT_Fric'' variable, which can have 1 (scalar) or 3 (tensor) dimensions. The attribute has dimensions of [1/time], meaning that it is a linear friction term which is multiplied by the velocity in the governing equations, and is normalized by the ocean depth prior to simulation. Hence, it ignores the water surface elevation portion of the total water depth, which is reasonable since the term and theory it is based on is only applicable to deep ocean. Typically, it is only applied to ocean depths greater than 100-500 m.<br />
<br />
== Specifying ''IT_Fric'' Values ==<br />
''IT_Fric'' values are determined through analytical formulations based on Bell's linear theory<ref name="Bell1975">{{cite journal|last1=Bell|first1=T.H.|title=Topographically generated internal waves in the open ocean|journal=Journal of Geophysical Research|volume=80|year=1975|pages=320–327|doi=10.1029/JC080i003p00320}}</ref>, valid in what is called sub-critical topography. <br />
<br />
Recent publications using ADCIRC<ref>W.J. Pringle, D. Wirasaet, A. Suhardjo, J. Meixner, J.J. Westerink, A.B. Kennedy, S. Nong, Finite-Element Barotropic Model for the Indian and Western Pacific Oceans: Tidal Model-Data Comparisons and Sensitivities, Ocean Model. 129 (2018) 13–38. doi:10.1016/j.ocemod.2018.07.003.</ref><ref>W.J. Pringle, D. Wirasaet, J.J. Westerink, Modifications to Internal Tide Conversion Parameterizations and Implementation into Barotropic Ocean Models, EarthArXiv. (2018) 9. doi:10.31223/osf.io/84w53.</ref> provide relevant formulation and implementation details. <br />
<br />
==References==<br />
{{Reflist}}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Wind_Stress&diff=1142Wind Stress2024-03-22T18:23:35Z<p>Taylorgasher: /* Interpolating Roughness Lengths Before v55 */ typo</p>
<hr />
<div>When wind blows over the water, it exerts a shear stress at the water surface that transfers horizontal momentum vertically downward across the air–sea interface, driving circulation. In ADCIRC, wind stress is an input forcing term, with several different formats provided. See the <code>[[NWS]]</code> parameter for available formats. In most cases, the exact wind stress to be applied to the model is not provided, therefore ADCIRC must determine how to convert a given wind speed to the actual stress applied at the ocean surface. This page covers the various aspects of this process, as well as the options available to the user. <br />
<br />
== Definition of Winds ==<br />
The characteristics of wind forcing are often broken down in three ways: <br />
# Whether the winds are considered to be over-water (termed "marine exposure") or over-land<br />
# The elevation above the sea (or ground) surface of the winds<br />
# The time-averaging (if any) that has been applied<br />
<br />
ADCIRC generally expects 10-meter, 10-minute winds at their actual exposure, although the exact expectations vary depending on the input type. For instance, when Holland-type wind inputs are provided (e.g. <code>NWS=8</code> or <code>NWS=20</code>), the wind speed is expected to be the '''1-minute [https://en.wikipedia.org/wiki/Maximum_sustained_wind maximum sustained wind]''' at 10 meters elevation. If marine-exposure winds are provided, then [[Fort.13_file#Surface_Roughness|surface roughness]] reductions may be needed<br />
<ref name="simiu1996">Simiu, E., Scanlan, R.H., 1996. Wind effects on structures: fundamentals and applications to design, 3rd ed. ed. John Wiley, New York.</ref><br />
<ref name="simiu2018">Simiu, E., Yeo, D., 2018. Wind effects on structures: modern structural design for wind, Fourth edition. ed. John Wiley & Sons, Hoboken, NJ.</ref><br />
. If winds are provided with a different averaging time, then an appropriate correction may be needed, though winds with averaging times of 10 to 60 minutes are generally considered to be quite similar; this is the so-called mesoscale gap. For recommendations on wind time-scale conversions not handled internally by ADCIRC, for tropical cyclones, see the WMO guidelines of Harper et al.<br />
<ref name="wmotcaveraging">Harper, B., Kepert, J., Ginger, J., 2010. Guidelines for converting between various wind averaging periods in tropical cyclone conditions (No. WMO/TD-No. 1555). WMO, Geneva, Switzerland.</ref><br />
<br />
== Roughness Reductions ==<br />
Reductions in wind speed to convert to the appropriate exposure come from a logarithmic boundary layer formulation (see, e.g. <ref name="simiu1996" /> <ref name="simiu2018" />) to determine a fraction <math>f</math> to reduce the winds, <br />
:<math>f=\left ( \frac{z_{0l}}{z_{0m}}\right ) ^{0.0706} \left ( \frac{\ln \frac{10}{z_{0l}}}{\ln \frac{10}{z_{0m}}} \right ) </math><br />
for marine roughness length <math>z_{0m}</math> and reduced ("land") roughness length <math>z_{0l}</math>. Wind speed is then reduced as, <br />
:<math>\mathbf{w}'=f\mathbf{w}=f [u,v]</math><br />
for x- and y- wind vector components <math>u</math> and <math>v</math>. The marine roughness length is, <br />
:<math>z_{0m}=\frac{0.018}{g} c_d \left \Vert \mathbf{w} \right \| </math><br />
for Charnock parameter <math>0.018</math>, drag coefficient <math>c_d</math> and acceleration due to gravity <math>g</math>. The wind drag coefficient is addressed below in [[#Converting Wind Velocity to Wind Stress|this section]]. As previously noted, the reduced ("land") roughness length <math>z_{0l}</math> is specified by the user via the [[Fort.13_file#Surface_Roughness|surface roughness]] nodal attribute. The fraction <math>f</math> is bounded on <math>[0,1]</math>, meaning the winds cannot be increased, nor change direction. <br />
<br />
=== Older Behavior ===<br />
====Interpolating Roughness Lengths Before v55====<br />
[[File:WindTraceV2.png|right|thumb|Comparison of output wind velocities using old and new methods.]]<br />
{{ADC version|version=55|relation=lt}}Before version 55, the directional wind reductions were applied by determining which of the 12 directional bins the wind velocity (at each time step) fell into, and using that roughness reduction, i.e. nearest neighbor interpolation. Starting in version 55, the roughness length is linearly (in angle space) interpolated between directional bins. In testing, this has been found to generally have a very small effect on water levels, but a notable effect on wind speeds, since time evolution of winds is smoother. It can have large localized effects on water levels in cases where there are large changes in neighboring roughness length bins coinciding with well-aligned winds, as in [[:File:MaxeleDiffRun13MinusRun12View1.png|this test case]] with Hurricane Isaac. <br />
<br clear=all><br />
<br />
====Roughness Reduction Bug Before v54====<br />
{{ADC version|version=54|relation=lt}}Before version 54, there was a bug in this calculation. The mistake and its effects are addressed in this PDF document: <u><span style="color:red">'''ADD A LINK TO A PDF HERE YOOOOO'''</span></u>.<br />
<br />
== Converting Wind Velocity to Wind Stress ==<br />
In ADCIRC, four formulations are available to convert wind velocities to the wind stresses applied in the momentum equations. Although there are several ways to control this, users are generally encouraged to use the [[metControl]] namelist in the [[fort.15]] file. The default drag formulation is the Garratt<br />
<ref name=garratt1977>Garratt, J.R., 1977. Review of Drag Coefficients over Oceans and Continents. Mon. Wea. Rev. 105, 915–929. https://doi.org/10.1175/1520-0493(1977)105<0915:RODCOO>2.0.CO;2</ref><br />
linear formula. An alternative for use with tropical cyclones is the Powell formulation,<br />
<ref>Powell, M.D., Vickery, P.J., Reinhold, T.A., 2003. Reduced drag coefficient for high wind speeds in tropical cyclones. Nature 422, 279–283. https://doi.org/10.1038/nature01481</ref><br />
which varies drag by the sector of the tropical cyclone. When ice coverage is included in the model, a wind drag formulation that accounts for this effect should be used. By default, if ice coverage input data are supplied, ADCIRC uses a cubic function of ice coverage, termed the "IceCube" drag formulation. Lastly, the "swell" drag law option allows users to utilize SWAN's drag formulation when employing the coupled model. <br />
<br />
In all cases, the actual wind drag coefficients determined by ADCIRC can be output to a [[fort.63]]-type file named [[winddrag.173]]. Output settings (file format, output start/end times, and output interval) match those of either the fort.63 or fort.73/74 files, ''I think'' fort.73/74. Outputting of this file is enabled by setting <code>outputWindDrag=.TRUE.</code> in the <code>&metControl</code> namelist of the [[Fort.15_file_format#Namelists|fort.15 file's namelist section]]. <br />
<br />
=== Garratt Drag Formulation ===<br />
This is the default wind drag formulation in ADCIRC. From Garratt (1977)<ref name=garratt1977></ref>, the formula is, <br />
:<math>c_d=0.001 \left ( 0.75+0.067 \left \Vert \mathbf{w} \right \| \right ) </math><br />
<br />
By default, ADCIRC puts an upper bound on the drag coefficient of <math>c_d\le0.0035</math>. This upper bound <code>WindDragLimit</code> can be changed via the [[metControl]] fort.15 namelist. <br />
<br />
=== Powell Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
Note that the code for the Powell drag law has not been configured to reverse orientation in the southern hemisphere, and so will produce the wrong results. For details on Powell, see [https://ccht.ccee.ncsu.edu/wind-drag-based-on-storm-sectors/ this post].<br />
<br />
=== IceCube Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:meteorology]]<br />
[[Category:physics]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=File:Run03masterVsRun05interp_trimmedAndAnnotatedTry7-min.gif&diff=1141File:Run03masterVsRun05interp trimmedAndAnnotatedTry7-min.gif2024-03-22T17:52:28Z<p>Taylorgasher: </p>
<hr />
<div>GIF showing differences in wind speeds from improved (linear interpolation) of surface_directional_effective_roughness_length values.</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file_format&diff=1140Fort.15 file format2024-03-15T20:36:51Z<p>Taylorgasher: /* Namelists */ added smag namelist, reorganized, cleaned up namelists section</p>
<hr />
<div>The basic file structure of the [[fort.15 file]] is shown below. Each line of input data is represented by a line containing the input variable name(s). Inputs in the [[fort.15 file]] must be entered in the exact order shown on this page. '''Blank lines and headings are only to enhance readability.''' Loops indicate multiple lines of input. <br/><br />
==Main Controls==<br />
===Metadata and Logging===<br />
'''<code>[[RUNDES]]'''</code> - alphanumeric run description 1, 32 characters or less<br/><br />
'''<code>[[RUNID]]'''</code> - alphanumeric run description 2, 24 characters or less<br/><br />
'''<code>[[NFOVER]]'''</code> - non-fatal error override option<br/><br />
'''<code>[[NABOUT]]'''</code> - verbosity of run log output, <code>= -1</code> is debug mode, higher is less output, up to <code>3</code> for errors only<br/><br />
'''<code>[[NSCREEN]]'''</code> - directs log messages to the screen (<code>> 0</code>), the adcirc.log file (<code>< 0</code>), or disables them (<code>= 0</code>)<br/><br />
<!-- Comments<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Parameter<br />
! Type<br />
! Required?<br />
! Description<br />
! Values<br />
|-<br />
| <code>RUNDES</code><br />
| <math>\leq</math>32 character string<br />
| Always<br />
| Run description<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>RUNID</code><br />
| <math>\leq</math>24 character string<br />
| Always<br />
| Run identification<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>[[NFOVER]]</code><br />
| integer<br />
| Always<br />
| Non-fatal error override option <br />
| 0 or 1<br />
|- style="background:#efefef;"<br />
| <code>[[NABOUT]]</code><br />
| integer<br />
| Always<br />
| Logging level <br />
| -1, 0, 1, 2, or 3<br />
|- style="background:#efefef;"<br />
| <code>[[NSCREEN]]</code><br />
| integer<br />
| Always<br />
| Logging output destination<br />
| -1, 0, or 1<br />
|}<br />
--><br />
<br />
===Numerics & Physics===<br />
'''<code>[[IHOT]]'''</code> - whether to read a hotstart file<br/><br />
'''<code>[[ICS]]</code>''' - coordinate projection to run in<br/><br />
'''<code>[[IM]]</code>''' - model run mode<br/><br />
'''<code>[[IDEN]]</code>''' - density forcing mode, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 20, 21, 30, 31</code>, or if <code>IM</code>'s last 6-digit entry is > 4 (e.g., <code>51311<b>5</b></code>).<br/><br />
'''<code>[[NOLIBF]]</code>''' - bottom stress parameterization mode<br/><br />
'''<code>[[NOLIFA]]</code>''' - finite amplitude term and wetting/drying mode, off if <code>= 0</code><br/><br />
'''<code>[[NOLICA]]</code>''' - advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NOLICAT]]</code>''' - time-derivative advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NWP]]</code>''' - number of [[nodal attribute]]s<br/><br />
''for j=1 to <code>[[NWP]]</code>''<br/><br />
: '''<code>[[AttrName(j)]]</code>''' - nodal attributes to use, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NWP]] > 0</code><br/><br />
''end j loop''<br/><br />
'''<code>[[NCOR]]</code>''' - Coriolis control, spatially constant if <code>= 0</code>, varies with latitude if <code>= 1</code><br/><br />
'''<code>[[NTIP]]</code>''' - tidal potential forcing control, off if <code>= 0</code><br/><br />
<span id="NWS"/>'''<code>[[NWS#Value_Seen_in_fort.15_File|NWS]]</code>''' - meteorological, wave, and ice forcing control<br/><br />
'''<code>[[NRAMP]]</code>''' - forcing ramping control<br/><br />
'''<code>[[G]]</code>''' - acceleration due to gravity<br/><br />
'''<code>[[TAU0]]</code>''' - affects numerical diffusion/stability of governing equations<br/><br />
'''<code>[[Tau0FullDomainMin]] [[Tau0FullDomainMax]]</code>''' - limits on <code>[[TAU0]]</code>, ''<span style="background:blanchedalmond">include this line only if:</span>''<code>TAU0 = -5.0</code>.<br/><br />
'''<code>[[DTDP]]</code>''' - model time step (seconds) and predictor-corrector control<br/><br />
'''<code>[[STATIM]]</code>''' - shifts numeric value of starting simulation time (days)<br/><br />
<span id="REFTIM"/>'''<code>[[REFTIM]]</code>''' - shifts reference time (days) for tidal harmonic analysis<br/><br />
<span id="WTIMINC"/><span id="RSTIMINC"/><span id="CICE_TIMINC"/>'''[[Supplemental_Meteorological/Wave/Ice_Parameters|Meteorological controls including <code>WTIMINC, RSTIMINC</code>]]''' - ''<span style="background:blanchedalmond">include this line:</span>'' for most cases of <code>NWS ≠ 0</code>, see linked page for details.<br/><br />
'''<code>[[RNDAY]]</code>''' - end time of simulation (days)<br/><br />
'''[[Ramping|Ramping controls including <code>DRAMP, FluxSettlingTime</code>]]''' - ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>NRAMP > 0</code>, see linked page for details<br/><br />
'''<code>[[A00 B00 C00]]</code>''' - time weighting factors in GWCE<br/><br />
'''<code>[[H0]]</code>''' - minimum depth, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 0</code> or <code>1</code>''<br/><br />
'''<code>[[H0]]</code> <code>INTEGER</code> <code>INTEGER</code> <code>[[VELMIN]]</code>''' - alternate minimum depth controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 2</code> or <code>3</code>''<br/><br />
'''<code>[[SLAM0]] [[SFEA0]]</code>''' - longitude and latitude for center of CPP coordinate projection<br/><br />
'''<code>[[TAU]]</code>''' - linear bottom friction coefficient, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 0</code>''<br/><br />
'''<code>[[CF]]</code>''' - quadratic bottom friction coefficient or limit, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 1</code>''<br/><br />
'''<code>[[CF]]</code> <code>[[HBREAK]]</code> <code>[[FTHETA]]</code> <code>[[FGAMMA]]</code>''' - alternate quadratic bottom friction controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 2</code>''<br/><br />
'''<code>[[ESLM]]</code>''' - horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 0</code>, <code>1</code>, or <code>2</code>''<br/><br />
'''<code>[[ESLM]]</code> <code>[[ESLC]]</code>''' - alternate horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 10</code>''<br/><br />
'''<code>[[CORI]]</code>''' - constant Coriolis coefficient, ''<span style="background:mistyRose">only used if</span>'' <code>NCOR=0</code><br />
<br />
===Periodic (Tidal) Body Forcing===<br />
[[NTIF]]<br/><br />
for k=1 to [[NTIF]]<br />
: [[TIPOTAG(k)]]<br />
: [[TPK(k)]], [[AMIGT(k)]], [[ETRF(k)]], [[FFT(k)]], [[FACET(k)]]<br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Elevations===<br />
[[NBFR]]<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[BOUNTAG(k)]]<br/><br />
: [[AMIG(k)]], [[FF(k)]], [[FACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NETA]]<br/><br />
:: [[EMO(k,j), EFA(k,j)]]<br/><br />
: end j loop<br/><br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Velocities===<br />
[[ANGINN]]<br/><br />
[[NFFR]] - include this line only if [[IBTYPE]] = 2, 12, 22, 32 or 52 in the Grid and Boundary Information File<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[FBOUNTAG(k)]]<br/><br />
: [[FAMIGT(k),FFF(k),FFACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NVEL]]<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]] - use this line if [[IBTYPE]] = 2, 12, 22 in the Grid and Boundary Information File<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]], [[ENAM(k,j), ENPH(k,j)]] - use this line if [[IBTYPE]] = 32 in the Grid and Boundary Information File<br/><br />
:end j loop<br/><br />
end k loop<br />
<br />
===Model Output===<br />
[[NOUTE]], [[TOUTSE]], [[TOUTFE]], [[NSPOOLE]]<br/><br />
[[NSTAE]]<br/><br />
for k=1 to [[NSTAE]]<br/><br />
: [[XEL(k), YEL(k)]] - use these lines if [[NSTAE]] is positive. If negative, stations are listed in the [[elev_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTV]], [[TOUTSV]], [[TOUTFV]], [[NSPOOLV]]<br/><br />
[[NSTAV]]<br/><br />
for k=1 to [[NSTAV]]<br/><br />
: [[XEV(k), YEV(k)]] - use these lines if [[NSTAV]] is positive. If negative, stations are listed in the [[vel_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTC]], [[TOUTSC]], [[TOUTFC]], [[NSPOOLC]] - include this line only if IM =10<br/><br />
[[NSTAC]] - include this line only if IM =10<br/><br />
for k=1 to [[NSTAC]]<br/><br />
: [[XEC(k), YEC(k)]]<br/><br />
end k loop<br/><br />
[[NOUTM]], [[TOUTSM]], [[TOUTFM]], [[NSPOOLM]] - include this line only if NWS is not equal to zero.<br/><br />
[[NSTAM]] - include this line only if NWS is not equal to zero.<br/><br />
for k=1 to [[NSTAM]]<br/><br />
: [[XEM(k), YEM(k)]] - use these lines if [[NSTAM]] is positive. If negative, stations are listed in the [[met_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTGE]], [[TOUTSGE]], [[TOUTFGE]], [[NSPOOLGE]]<br/><br />
[[NOUTGV]], [[TOUTSGV]], [[TOUTFGV]], [[NSPOOLGV]]<br/><br />
[[NOUTGC]], [[TOUTSGC]], [[TOUTFGC]], [[NSPOOLGC]] - include this line only if IM =10<br/><br />
[[NOUTGW]], [[TOUTSGW]], [[TOUTFGW]], [[NSPOOLGW]] - include this line only if NWS is not equal to zero.<br />
<br />
====Harmonic Analysis====<br />
[[NFREQ]]<br/><br />
for k=1 to [[NFREQ]]<br/><br />
: [[NAMEFR(k)]]<br/><br />
: [[HAFREQ(k), HAFF(k), HAFACE(k)]]<br/><br />
end k loop<br/><br />
[[THAS]], [[THAF]], [[NHAINC]], [[FMV]]<br/><br />
[[NHASE]], [[NHASV]], [[NHAGE]], [[NHAGV]]<br />
<br />
====Hotstart Output and Numeric Controls====<br />
[[NHSTAR]], [[NHSINC]]<br/><br />
[[ITITER]], [[ISLDIA]], [[CONVCR]], [[ITMAX]]<br/><br />
<br />
''For a 2DDI ADCIRC run that does not use netCDF nor namelists, the file ends here. For those controls, see further below in the [[#NetCDF Controls|NetCDF Controls]] and [[#Namelists|Namelists]] sections.''<br />
<br />
==3D Model Run==<br />
[[IDEN]]<br/><br />
[[ISLIP]], [[KP]]<br/><br />
[[Z0S,Z0B]]<br/><br />
[[ALP1,ALP2,ALP3]]<br/><br />
[[IGC]], [[NFEN]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IGC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[SIGMA(k)]]<br/><br />
end k loop<br/><br />
[[IEVC]], [[EVMIN]], [[EVCON]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IEVC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[EVTOT(k)]]<br/><br />
end k loop<br/><br />
[[THETA1, THETA2]](include this line only if [[IEVC]] = 50 or 51)<br/><br />
[[I3DSD,TO3DSDS,TO3DSDF,NSPO3DSD]]<br/><br />
[[NSTA3DD]]<br/><br />
for k=1 to [[NSTA3DD]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DSV,TO3DSVS,TO3DSVF,NSPO3DSV]]<br/><br />
[[NSTA3DV]]<br/><br />
for k=1 to [[NSTA3DV]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DST,TO3DSTS,TO3DSTF,NSPO3DST]]<br/><br />
[[NSTA3DT]]<br/><br />
for k=1 to [[NSTA3DT]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DGD]],[[TO3DGDS]],[[TO3DGDF]],[[NSPO3DGD]]<br/><br />
[[I3DGV]],[[TO3DGVS]],[[TO3DGVF]],[[NSPO3DGV]]<br/><br />
[[I3DGT]],[[TO3DGTS]],[[TO3DGTF]],[[NSPO3DGT]]<br/><br />
The following line will be read in if [[IM]] is 21 or 31.<br/><br />
[[RES_BC_FLAG]], [[BCFLAG_LNM]], [[BCFLAG_TEMP]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] is negative.<br/><br />
[[RBCTIMEINC]]<br/><br />
[[BCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 2.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3.<br/><br />
[[RBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 4.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3 or 4 and [[BCFLAG_TEMP]] is not equal to 0.<br/><br />
[[TTBCTIMEINC]], [[TTBCSTATIM]]<br/><br />
[[TTBCTIMEINC]]<br/><br />
The following two lines will be read in only if [[IM]] is 21 or 31.<br/><br />
[[SPONGEDIST]]<br/><br />
[[EQNSTATE]]<br/><br />
The following lines will be read in only if [[IDEN]] is > 0.<br/><br />
[[NLSD, NVSD]]<br/><br />
[[NLTD, NVTD]]<br/><br />
[[ALP4]]<br/><br />
The following line will be read in only if [[IDEN]] = 3 or 4.<br/><br />
[[NTF]]<br />
<br />
==NetCDF Controls==<br />
The following lines will be read in only if the NetCDF output or hotstart format is chosen<br/><br />
NCPROJ<br/><br />
NCINST<br/><br />
NCSOUR<br/><br />
NCHIST<br/><br />
NCREF<br/><br />
NCCOM<br/><br />
NCHOST<br/><br />
NCCONV<br/><br />
NCCONT<br/><br />
NCDATE<br />
<br />
==Namelists==<br />
The following Fortran namelist lines are optional, but if they appear, they must appear at the very end of the fort.15 file. Namelist entries can have blank lines between them, and individual entries in a given namelist can be on separate lines in addition to being comma-delimited. Each namelist is terminated by a slash. <br/><br />
<code>&[[AliDispersionControl]] CAliDisp=logicalValue, Cs=floatValue, Ad=floatValue, Bd=floatValue /</code><br />
<br />
<code>&[[Dynamic_water_level_correction#Controlling_Water_Level_Correction|dynamicWaterLevelCorrectionControl]] dynamicWaterLevelCorrectionFileName='stringValue', dynamicWaterLevelCorrectionMultiplier=floatValue, dynamicWaterLevelCorrectionRampStart=floatValue, dynamicWaterLevelCorrectionRampEnd=floatValue, dynamicWaterLevelCorrectionRampReferenceTime='stringValue', dynamicWaterLevelCorrectionSkipSnaps=integerValue /</code><br />
<br />
<code>&[[Horizontal_eddy_viscosity#Smagorinsky_Eddy_Viscosity|Smag_Control]] SMAG_LOWER_LIM=floatValue, SMAG_UPPER_LIM=floatValue /</code><br />
<br />
<code>&inundationOutputControl inundationOutput=logicalValue0, inunThresh =floatValue /</code><br />
<br />
<code>&metControl WindDragLimit=floatValue, DragLawString='stringValue', rhoAir=floatValue, outputWindDrag=logicalValue /</code><br />
<br />
<code>&subdomainModeling subdomainOn=logicalValue/</code><br />
<br />
<code>&SWANOutputControl SWAN_OutputHS=logicalValue, SWAN_OutputDIR=logicalValue, SWAN_OutputTM01=logicalValue, SWAN_OutputTPS=logicalValue, SWAN_OutputWIND=logicalValue, SWAN_OutputTM02=logicalValue, SWAN_OutputTMM10=logicalValue /</code><br />
<br />
<code>&timeBathyControl NDDT=integerValue, BTIMINC=floatValue, BCHGTIMINC=floatValue, invertedBarometerOnElevationBoundary=logicalValue /</code><br />
<br />
<code>&TVWControl use_TVW=logicalValue, TVW_file='stringValue', nout_TVW =integerValue, touts_TVW =floatValue, toutf_TVW=floatValue, nspool_TVW =integerValue /</code><br />
<br />
<code>&WarnElevControl WarnElev=floatValue, ErrorElev=floatValue, WarnElevDump=logicalValue, WarnElevDumpLimit=integerValue /</code><br />
<br />
<code>&waveCoupling WindWaveMultiplier=floatValue /</code><br />
<br />
<code>&wetDryControl outputNodeCode=logicalValue, outputNOFF=logicalValue, noffActive=logicalValue /</code><br />
<br />
[[category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file_format&diff=1139Fort.15 file format2024-03-15T20:27:11Z<p>Taylorgasher: /* Namelists */ typo</p>
<hr />
<div>The basic file structure of the [[fort.15 file]] is shown below. Each line of input data is represented by a line containing the input variable name(s). Inputs in the [[fort.15 file]] must be entered in the exact order shown on this page. '''Blank lines and headings are only to enhance readability.''' Loops indicate multiple lines of input. <br/><br />
==Main Controls==<br />
===Metadata and Logging===<br />
'''<code>[[RUNDES]]'''</code> - alphanumeric run description 1, 32 characters or less<br/><br />
'''<code>[[RUNID]]'''</code> - alphanumeric run description 2, 24 characters or less<br/><br />
'''<code>[[NFOVER]]'''</code> - non-fatal error override option<br/><br />
'''<code>[[NABOUT]]'''</code> - verbosity of run log output, <code>= -1</code> is debug mode, higher is less output, up to <code>3</code> for errors only<br/><br />
'''<code>[[NSCREEN]]'''</code> - directs log messages to the screen (<code>> 0</code>), the adcirc.log file (<code>< 0</code>), or disables them (<code>= 0</code>)<br/><br />
<!-- Comments<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Parameter<br />
! Type<br />
! Required?<br />
! Description<br />
! Values<br />
|-<br />
| <code>RUNDES</code><br />
| <math>\leq</math>32 character string<br />
| Always<br />
| Run description<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>RUNID</code><br />
| <math>\leq</math>24 character string<br />
| Always<br />
| Run identification<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>[[NFOVER]]</code><br />
| integer<br />
| Always<br />
| Non-fatal error override option <br />
| 0 or 1<br />
|- style="background:#efefef;"<br />
| <code>[[NABOUT]]</code><br />
| integer<br />
| Always<br />
| Logging level <br />
| -1, 0, 1, 2, or 3<br />
|- style="background:#efefef;"<br />
| <code>[[NSCREEN]]</code><br />
| integer<br />
| Always<br />
| Logging output destination<br />
| -1, 0, or 1<br />
|}<br />
--><br />
<br />
===Numerics & Physics===<br />
'''<code>[[IHOT]]'''</code> - whether to read a hotstart file<br/><br />
'''<code>[[ICS]]</code>''' - coordinate projection to run in<br/><br />
'''<code>[[IM]]</code>''' - model run mode<br/><br />
'''<code>[[IDEN]]</code>''' - density forcing mode, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 20, 21, 30, 31</code>, or if <code>IM</code>'s last 6-digit entry is > 4 (e.g., <code>51311<b>5</b></code>).<br/><br />
'''<code>[[NOLIBF]]</code>''' - bottom stress parameterization mode<br/><br />
'''<code>[[NOLIFA]]</code>''' - finite amplitude term and wetting/drying mode, off if <code>= 0</code><br/><br />
'''<code>[[NOLICA]]</code>''' - advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NOLICAT]]</code>''' - time-derivative advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NWP]]</code>''' - number of [[nodal attribute]]s<br/><br />
''for j=1 to <code>[[NWP]]</code>''<br/><br />
: '''<code>[[AttrName(j)]]</code>''' - nodal attributes to use, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NWP]] > 0</code><br/><br />
''end j loop''<br/><br />
'''<code>[[NCOR]]</code>''' - Coriolis control, spatially constant if <code>= 0</code>, varies with latitude if <code>= 1</code><br/><br />
'''<code>[[NTIP]]</code>''' - tidal potential forcing control, off if <code>= 0</code><br/><br />
<span id="NWS"/>'''<code>[[NWS#Value_Seen_in_fort.15_File|NWS]]</code>''' - meteorological, wave, and ice forcing control<br/><br />
'''<code>[[NRAMP]]</code>''' - forcing ramping control<br/><br />
'''<code>[[G]]</code>''' - acceleration due to gravity<br/><br />
'''<code>[[TAU0]]</code>''' - affects numerical diffusion/stability of governing equations<br/><br />
'''<code>[[Tau0FullDomainMin]] [[Tau0FullDomainMax]]</code>''' - limits on <code>[[TAU0]]</code>, ''<span style="background:blanchedalmond">include this line only if:</span>''<code>TAU0 = -5.0</code>.<br/><br />
'''<code>[[DTDP]]</code>''' - model time step (seconds) and predictor-corrector control<br/><br />
'''<code>[[STATIM]]</code>''' - shifts numeric value of starting simulation time (days)<br/><br />
<span id="REFTIM"/>'''<code>[[REFTIM]]</code>''' - shifts reference time (days) for tidal harmonic analysis<br/><br />
<span id="WTIMINC"/><span id="RSTIMINC"/><span id="CICE_TIMINC"/>'''[[Supplemental_Meteorological/Wave/Ice_Parameters|Meteorological controls including <code>WTIMINC, RSTIMINC</code>]]''' - ''<span style="background:blanchedalmond">include this line:</span>'' for most cases of <code>NWS ≠ 0</code>, see linked page for details.<br/><br />
'''<code>[[RNDAY]]</code>''' - end time of simulation (days)<br/><br />
'''[[Ramping|Ramping controls including <code>DRAMP, FluxSettlingTime</code>]]''' - ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>NRAMP > 0</code>, see linked page for details<br/><br />
'''<code>[[A00 B00 C00]]</code>''' - time weighting factors in GWCE<br/><br />
'''<code>[[H0]]</code>''' - minimum depth, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 0</code> or <code>1</code>''<br/><br />
'''<code>[[H0]]</code> <code>INTEGER</code> <code>INTEGER</code> <code>[[VELMIN]]</code>''' - alternate minimum depth controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 2</code> or <code>3</code>''<br/><br />
'''<code>[[SLAM0]] [[SFEA0]]</code>''' - longitude and latitude for center of CPP coordinate projection<br/><br />
'''<code>[[TAU]]</code>''' - linear bottom friction coefficient, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 0</code>''<br/><br />
'''<code>[[CF]]</code>''' - quadratic bottom friction coefficient or limit, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 1</code>''<br/><br />
'''<code>[[CF]]</code> <code>[[HBREAK]]</code> <code>[[FTHETA]]</code> <code>[[FGAMMA]]</code>''' - alternate quadratic bottom friction controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 2</code>''<br/><br />
'''<code>[[ESLM]]</code>''' - horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 0</code>, <code>1</code>, or <code>2</code>''<br/><br />
'''<code>[[ESLM]]</code> <code>[[ESLC]]</code>''' - alternate horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 10</code>''<br/><br />
'''<code>[[CORI]]</code>''' - constant Coriolis coefficient, ''<span style="background:mistyRose">only used if</span>'' <code>NCOR=0</code><br />
<br />
===Periodic (Tidal) Body Forcing===<br />
[[NTIF]]<br/><br />
for k=1 to [[NTIF]]<br />
: [[TIPOTAG(k)]]<br />
: [[TPK(k)]], [[AMIGT(k)]], [[ETRF(k)]], [[FFT(k)]], [[FACET(k)]]<br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Elevations===<br />
[[NBFR]]<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[BOUNTAG(k)]]<br/><br />
: [[AMIG(k)]], [[FF(k)]], [[FACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NETA]]<br/><br />
:: [[EMO(k,j), EFA(k,j)]]<br/><br />
: end j loop<br/><br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Velocities===<br />
[[ANGINN]]<br/><br />
[[NFFR]] - include this line only if [[IBTYPE]] = 2, 12, 22, 32 or 52 in the Grid and Boundary Information File<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[FBOUNTAG(k)]]<br/><br />
: [[FAMIGT(k),FFF(k),FFACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NVEL]]<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]] - use this line if [[IBTYPE]] = 2, 12, 22 in the Grid and Boundary Information File<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]], [[ENAM(k,j), ENPH(k,j)]] - use this line if [[IBTYPE]] = 32 in the Grid and Boundary Information File<br/><br />
:end j loop<br/><br />
end k loop<br />
<br />
===Model Output===<br />
[[NOUTE]], [[TOUTSE]], [[TOUTFE]], [[NSPOOLE]]<br/><br />
[[NSTAE]]<br/><br />
for k=1 to [[NSTAE]]<br/><br />
: [[XEL(k), YEL(k)]] - use these lines if [[NSTAE]] is positive. If negative, stations are listed in the [[elev_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTV]], [[TOUTSV]], [[TOUTFV]], [[NSPOOLV]]<br/><br />
[[NSTAV]]<br/><br />
for k=1 to [[NSTAV]]<br/><br />
: [[XEV(k), YEV(k)]] - use these lines if [[NSTAV]] is positive. If negative, stations are listed in the [[vel_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTC]], [[TOUTSC]], [[TOUTFC]], [[NSPOOLC]] - include this line only if IM =10<br/><br />
[[NSTAC]] - include this line only if IM =10<br/><br />
for k=1 to [[NSTAC]]<br/><br />
: [[XEC(k), YEC(k)]]<br/><br />
end k loop<br/><br />
[[NOUTM]], [[TOUTSM]], [[TOUTFM]], [[NSPOOLM]] - include this line only if NWS is not equal to zero.<br/><br />
[[NSTAM]] - include this line only if NWS is not equal to zero.<br/><br />
for k=1 to [[NSTAM]]<br/><br />
: [[XEM(k), YEM(k)]] - use these lines if [[NSTAM]] is positive. If negative, stations are listed in the [[met_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTGE]], [[TOUTSGE]], [[TOUTFGE]], [[NSPOOLGE]]<br/><br />
[[NOUTGV]], [[TOUTSGV]], [[TOUTFGV]], [[NSPOOLGV]]<br/><br />
[[NOUTGC]], [[TOUTSGC]], [[TOUTFGC]], [[NSPOOLGC]] - include this line only if IM =10<br/><br />
[[NOUTGW]], [[TOUTSGW]], [[TOUTFGW]], [[NSPOOLGW]] - include this line only if NWS is not equal to zero.<br />
<br />
====Harmonic Analysis====<br />
[[NFREQ]]<br/><br />
for k=1 to [[NFREQ]]<br/><br />
: [[NAMEFR(k)]]<br/><br />
: [[HAFREQ(k), HAFF(k), HAFACE(k)]]<br/><br />
end k loop<br/><br />
[[THAS]], [[THAF]], [[NHAINC]], [[FMV]]<br/><br />
[[NHASE]], [[NHASV]], [[NHAGE]], [[NHAGV]]<br />
<br />
====Hotstart Output and Numeric Controls====<br />
[[NHSTAR]], [[NHSINC]]<br/><br />
[[ITITER]], [[ISLDIA]], [[CONVCR]], [[ITMAX]]<br/><br />
<br />
''For a 2DDI ADCIRC run that does not use netCDF nor namelists, the file ends here. For those controls, see further below in the [[#NetCDF Controls|NetCDF Controls]] and [[#Namelists|Namelists]] sections.''<br />
<br />
==3D Model Run==<br />
[[IDEN]]<br/><br />
[[ISLIP]], [[KP]]<br/><br />
[[Z0S,Z0B]]<br/><br />
[[ALP1,ALP2,ALP3]]<br/><br />
[[IGC]], [[NFEN]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IGC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[SIGMA(k)]]<br/><br />
end k loop<br/><br />
[[IEVC]], [[EVMIN]], [[EVCON]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IEVC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[EVTOT(k)]]<br/><br />
end k loop<br/><br />
[[THETA1, THETA2]](include this line only if [[IEVC]] = 50 or 51)<br/><br />
[[I3DSD,TO3DSDS,TO3DSDF,NSPO3DSD]]<br/><br />
[[NSTA3DD]]<br/><br />
for k=1 to [[NSTA3DD]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DSV,TO3DSVS,TO3DSVF,NSPO3DSV]]<br/><br />
[[NSTA3DV]]<br/><br />
for k=1 to [[NSTA3DV]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DST,TO3DSTS,TO3DSTF,NSPO3DST]]<br/><br />
[[NSTA3DT]]<br/><br />
for k=1 to [[NSTA3DT]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DGD]],[[TO3DGDS]],[[TO3DGDF]],[[NSPO3DGD]]<br/><br />
[[I3DGV]],[[TO3DGVS]],[[TO3DGVF]],[[NSPO3DGV]]<br/><br />
[[I3DGT]],[[TO3DGTS]],[[TO3DGTF]],[[NSPO3DGT]]<br/><br />
The following line will be read in if [[IM]] is 21 or 31.<br/><br />
[[RES_BC_FLAG]], [[BCFLAG_LNM]], [[BCFLAG_TEMP]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] is negative.<br/><br />
[[RBCTIMEINC]]<br/><br />
[[BCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 2.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3.<br/><br />
[[RBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 4.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3 or 4 and [[BCFLAG_TEMP]] is not equal to 0.<br/><br />
[[TTBCTIMEINC]], [[TTBCSTATIM]]<br/><br />
[[TTBCTIMEINC]]<br/><br />
The following two lines will be read in only if [[IM]] is 21 or 31.<br/><br />
[[SPONGEDIST]]<br/><br />
[[EQNSTATE]]<br/><br />
The following lines will be read in only if [[IDEN]] is > 0.<br/><br />
[[NLSD, NVSD]]<br/><br />
[[NLTD, NVTD]]<br/><br />
[[ALP4]]<br/><br />
The following line will be read in only if [[IDEN]] = 3 or 4.<br/><br />
[[NTF]]<br />
<br />
==NetCDF Controls==<br />
The following lines will be read in only if the NetCDF output or hotstart format is chosen<br/><br />
NCPROJ<br/><br />
NCINST<br/><br />
NCSOUR<br/><br />
NCHIST<br/><br />
NCREF<br/><br />
NCCOM<br/><br />
NCHOST<br/><br />
NCCONV<br/><br />
NCCONT<br/><br />
NCDATE<br />
<br />
==Namelists==<br />
The following Fortran namelist lines are optional, but if they appear, they must appear at the very end of the fort.15 file.<br/><br />
<code>&metControl WindDragLimit=floatValue, DragLawString='stringValue', rhoAir=floatValue, outputWindDrag=logicalValue /</code><br/><br />
<code>&timeBathyControl NDDT=integerValue, BTIMINC=floatValue, BCHGTIMINC=floatValue, invertedBarometerOnElevationBoundary=logicalValue /</code><br/><br />
<code>&waveCoupling WindWaveMultiplier=floatValue /</code><br/><br />
<code>&SWANOutputControl SWAN_OutputHS=logicalValue, SWAN_OutputDIR=logicalValue, SWAN_OutputTM01=logicalValue, SWAN_OutputTPS=logicalValue, SWAN_OutputWIND=logicalValue, SWAN_OutputTM02=logicalValue, SWAN_OutputTMM10=logicalValue /</code><br/><br />
<code>&subdomainModeling subdomainOn=logicalValue/</code><br/><br />
<code>&wetDryControl outputNodeCode=logicalValue, outputNOFF=logicalValue, noffActive=logicalValue /</code><br/><br />
<code>&inundationOutputControl inundationOutput=logicalValue0, inunThresh =floatValue /</code><br/><br />
<code>&TVWControl use_TVW=logicalValue, TVW_file='stringValue', nout_TVW =integerValue, touts_TVW =floatValue, toutf_TVW=floatValue, nspool_TVW =integerValue /</code><br/><br />
<code>&WarnElevControl WarnElev=floatValue, ErrorElev=floatValue, WarnElevDump=logicalValue, WarnElevDumpLimit=integerValue /</code><br/><br />
<code>[[Dynamic_water_level_correction#Controlling_Water_Level_Correction|&dynamicWaterLevelCorrectionControl]] dynamicWaterLevelCorrectionFileName='stringValue', dynamicWaterLevelCorrectionMultiplier=floatValue, dynamicWaterLevelCorrectionRampStart=floatValue, dynamicWaterLevelCorrectionRampEnd=floatValue, dynamicWaterLevelCorrectionRampReferenceTime='stringValue', dynamicWaterLevelCorrectionSkipSnaps=integerValue /</code><br/><br />
<code>&[[AliDispersionControl]] CAliDisp=logicalValue, Cs=floatValue, Ad=floatValue, Bd=floatValue /</code><br/><br />
[[category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Tips_and_Tricks&diff=1138Tips and Tricks2024-03-04T21:52:52Z<p>Taylorgasher: /* Method 1 - Very Easy */ added a little info</p>
<hr />
<div>This page serves as a catch-all covering methods to achieve common goals or overcome common issues. <br />
<br />
== Pre-Processing Tips and Tricks ==<br />
<br />
== ADCIRC-Only Tips and Tricks ==<br />
* [[fort.15_file#Meteorological-Only Mode|Meteorological-Only Mode]]<br />
* [[fort.15_file#Ramping Meteorological Forcing at Hot-Start|Ramping Meteorological Forcing at Hot-Start]]<br />
<br />
== ADCIRC+SWAN Tips and Tricks ==<br />
=== Writing Alternative Station SWAN Output ===<br />
SWAN has expansive outputting capabilities, documented in [https://swanmodel.sourceforge.io/online_doc/swanuse/swanuse.html its manual], but figuring out how can be a bit difficult. Here's a simple summary of how to output various parameters at a user-specified set of locations. Add two lines to your [[fort.26]] (SWAN control) file. I put these lines after the <code>NUM</code> line in the fort.26 file. The first line declares the existence and name of a set of points at which you want outputs: <br/><br />
<code>POINTS 'aStringIdForPointsFile' FILE 'theFileNameOfYourPointsFile'</code><br/><br />
where <code>'aStringIdForPointsFile</code> is the name you're giving the list of locations, and <code>'theFileNameOfYourPointsFile</code> is the actual file name. This file should be placed in your base run directory. The file format is ASCII x-y coordinate pairs, no header line, space-delimited, and one point per line, e.g. <br/><br />
x1 y1<br/>x2 y2<br/>x3 y3<br/>...<br />
<br />
The second line describes the outputs you want: <br/><br />
<code>TABLE 'aStringIdForPointsFile' HEADER 'outputFile' HSIGN HSWELL DIR PDIR TDIR TM02 STEEPNESS OUT 20010101.000000 15 MIN</code><br/><br />
where <code>HEADER</code> (or <code>NOHEADER</code>) indicates whether you want a header, <code>'outputFile'</code> is the output file name that SWAN writes to, <code>HSIGN HSWELL...STEEPNESS</code> are a list of the parameters to-be-output, <code>OUT</code> denotes the termination of the list of parameters, <code>20010101.000000</code> indicates when outputting should start in YYYYMMDD.hhmmss format, and <code>15 MIN</code> indicates a 15-minute output interval. Some notes: <br />
<br />
* The header can be nice but it can also sometimes cause format problems if the numeric values being output are too large to fit in the fixed-width columns. If you do <code>NOHEADER</code>, the file won't have this issue, though it can be harder to inspect visually...it'll be just as easy to read it with a computer program or something like Excel. <br />
* The list of parameters you can output is long, and the definitions are even longer. The list is currently on the SWAN website [https://swanmodel.sourceforge.io/online_doc/swanuse/node32.html here] under the description of the <code>BLOCK</code> output command, and has [https://swanmodel.sourceforge.io/online_doc/swanuse/node35.html#app:defvar a link] to the parameter definitions. If that link doesn't work, maybe go to the SWAN user manual [https://swanmodel.sourceforge.io/online_doc/swanuse/swanuse.html base page], then click on "Write or plot computed quantities". <br />
* In a parallel run, for model versions later than roughly ADCIRC version v52, the output should be a single file in the main run directory. In earlier versions, the output was written individually by each subdomain to its PE* folder. <br />
<br />
Note that you can add multiple <code>POINTS</code> and/or <code>TABLE</code> lines for different list of coordinates and/or different outputs. <br />
<br />
=== Writing Alternative Global SWAN Output ===<br />
Have you ever wanted to write different SWAN parameters to output in a coupled ADCIRC+SWAN simulation? If so, these tips and tricks are for you! The current implementations of the dynamically coupled version of ADCIRC+SWAN only write a few SWAN parameters to global time-series output files. Those output parameters and files include:<br />
* spectrally significant wave height (filename: swan_HS.63)<br />
* "smoothed" peak wave period (filename: swan_TPS.63)<br />
* mean absolute wave period (filename: swan_TMM10.63) <br />
* mean wave direction (filename: swan_DIR.63)<br />
* and perhaps others like TM01, TM02, and WIND<br />
<br />
The SWAN model has many other potentially useful output parameters and, in some cases, they may be more appropriate for your needs than these default outputs. For example, what if you preferred seeing the peak wave direction instead of the mean wave direction? Or maybe you need the swell wave height instead of, or in addition to, the significant wave height? The two methods below will allow you to accomplish just this. Granted, this does require that you modify some files within the SWAN and ADCIRC source codes, and that you recompile the source code into your desired executables. We hope the instructions below make the task of modifying the source code a little less daunting. There is one major caveat to the two methods outlined below: it will not allow you to 'define' your desired SWAN output in either the fort.26 file OR in namelist form at the bottom of fort.15. In other words, you will receive whatever outputs you hardwire into your source code and you cannot easily turn them on or off without again modifying the source code. <br />
<br />
==== Method 1 - Very Easy ====<br />
Use the approach described in the [[Tips_and_Tricks#Writing_Alternative_Station_SWAN_Output|last section]] and use the coordinates of all nodes as your list of stations. It's possible this may not exactly match what you'd get with other methods, e.g. if SWAN interpolates the station value even when a point exactly matches a node location then it would be subject to floating point errors and to effects of wetting/drying at the other nodes in the triangle.<br />
<br />
==== Method 2 - Easy but Limited ====<br />
<br />
This is by far the simplest method for modifying SWAN output in a coupled ADCIRC+SWAN simulation. By following the instructions below, you will be able to write any SWAN output you desire… but only to the existing SWAN output files. Existing SWAN output files include swan_HS.63, swan_TPS.63, swan_TMM10.63, swan_DIR.63, etc. This method will not produce NEW or ADDITIONAL SWAN output files. Rather, it will simply write the user-specified output to these existing filenames.<br />
<br />
Go to the swan/ folder in your adcirc source code directory tree and open the file swanout1.f<br />
<br />
You are looking for a variable assignment named IVTYPE in the subroutine named SWOEXA. The IVTYPE value is linked to SWAN output variables. For example, this is what the first IVTYPE definition looks like in my version of SWAN…<br />
<br />
!<br /><br />
! significant wave height<br /><br />
!<br /><br />
IVTYPE = 10<br />
<br />
Keep searching and note the IVTYPE values corresponding to your desired SWAN output variable(s). I have included a few below for reference.<br />
<br />
'''IVTYPE value / variable name'''<br /><br />
10 / significant wave height<br /><br />
44 / swell wave height<br /><br />
12 / peak wave period<br /><br />
14 / peak wave direction<br /><br />
13 / mean wave direction<br /><br />
16 / directional spread<br /><br />
15 / energy transport direction<br /> <br />
17 / average wave length<br /><br />
18 / steepness<br /><br />
<br />
With the IVTYPE value(s) noted, proceed to the src/ directory and open the file couple2swan.F<br />
<br />
Search for the variable IVTYPE. Reassign the IVTYPE values using the values of your desired output. For example, if you want to write the peak wave direction to the “swan_DIR.63” file instead of the mean wave direction, you’d want to change IVTYPE = 13 to IVTYPE = 14. Note that you’ll need to make this change in approximately five places within the couple2swan.F file. The embedded images below show comparisons between the original and modified files for this example (substituting IVTYPE=14 (PDIR) for IVTYPE=13 (DIR)). The change areas appear in the following subroutines of couple2swan.F:<br />
* ComputeWaveFrictionProperties<br />
* SwanOutput<br />
<br />
<br />
You would of course want to make these IVTYPE reassignments for any and all existing SWAN output that you'd like to modify. Keep in mind that you only have four existing files to work with here, so that is ultimately your limit on output parameters as well. You may want to consider renaming your output files so that you do not misinterpret your results. The output filenames are found in src/write_output.F. Using the example IVTYPE reassignment above, you might consider renaming swan_DIR.63 to swan_PDIR.63. If you need more than four output parameters and also want to change the filenames, see Method 2 below.<br />
<br />
<gallery><br />
method1_1.png|Change area 1 of 5 (click to enlarge)<br />
method1_2.png|Change area 2 of 5 (click to enlarge)<br />
method1_3.png|Change area 3 of 5 (click to enlarge)<br />
method1_4.png|Change area 4 of 5 (click to enlarge)<br />
method1_5.png|Change area 5 of 5 (click to enlarge)<br />
</gallery><br />
<br />
==== Method 3 - Moderately Difficult but Limitless ====<br />
<br />
This method is more complex but it will allow you to name and create any number of original SWAN output files. For example, say I wanted to keep the existing default SWAN output files (referenced above in Method 1) but also write the peak wave direction output to a brand new file named swan_PDIR.63. You can do that if you follow the steps below. Note that the example below will also generate a corresponding swan_PDIR_max.63 file in a manner similar to swan_HS_max.63, swan_TPS_max.63, etc. <br />
<br />
In this more complicated (really just more work) method you will need to perform four general tasks:<br />
# Increment an output counter in multiple places (in my example, from 7 to 8 because I am only adding the PDIR output)<br />
# Insert new sections of code pertaining to your desired output<br />
# Create and insert new variable names in GLOBAL and OUTPUT blocks<br />
# Add new code to direct your parameters to output files<br />
<br />
I honestly did this somewhat blindly the first time and it worked just fine (for me). You do need to be very careful and take your time going through the couple2swan.F file and all internal subroutines to make sure you are making all appropriate additions. Like method 1 above, your only modifications will be in couple2swan.F, but you will need to refer to the IVTYPE values found in swan/swanout1.f as described above. <br />
<br />
As was done above, I am providing screenshots of a "diff" comparison between the original and modified couple2swan.F files for this simple example of adding the PDIR output as a new output file. For consistency purposes I do specify PDIR as an output variable in my fort.26 file, but as Casey and others have mentioned in the past I don't think that makes any difference whatsoever. If you follow my example below you would get the PDIR outputs even if you omitted PDIR from the fort.26 file. The change areas appear in the following subroutines of couple2swan.F:<br />
* ComputeWaveFrictionProperties<br />
* SwanOutput<br />
<br />
<br />
<gallery><br />
method2_1.png|Change area 1 of 7 (click to enlarge)<br />
method2_2.png|Change area 2 of 7 (click to enlarge)<br />
method2_3.png|Change area 3 of 7 (click to enlarge)<br />
method2_4.png|Change area 4 of 7 (click to enlarge)<br />
method2_5.png|Change area 5 of 7 (click to enlarge)<br />
method2_6.png|Change area 6 of 7 (click to enlarge)<br />
method2_7.png|Change area 7 of 7 (click to enlarge)<br />
</gallery><br />
<br />
== Post-Processing Tips and Tricks ==</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Tips_and_Tricks&diff=1137Tips and Tricks2024-03-04T21:49:33Z<p>Taylorgasher: /* ADCIRC+SWAN Tips and Tricks */ added section on SWAN station output</p>
<hr />
<div>This page serves as a catch-all covering methods to achieve common goals or overcome common issues. <br />
<br />
== Pre-Processing Tips and Tricks ==<br />
<br />
== ADCIRC-Only Tips and Tricks ==<br />
* [[fort.15_file#Meteorological-Only Mode|Meteorological-Only Mode]]<br />
* [[fort.15_file#Ramping Meteorological Forcing at Hot-Start|Ramping Meteorological Forcing at Hot-Start]]<br />
<br />
== ADCIRC+SWAN Tips and Tricks ==<br />
=== Writing Alternative Station SWAN Output ===<br />
SWAN has expansive outputting capabilities, documented in [https://swanmodel.sourceforge.io/online_doc/swanuse/swanuse.html its manual], but figuring out how can be a bit difficult. Here's a simple summary of how to output various parameters at a user-specified set of locations. Add two lines to your [[fort.26]] (SWAN control) file. I put these lines after the <code>NUM</code> line in the fort.26 file. The first line declares the existence and name of a set of points at which you want outputs: <br/><br />
<code>POINTS 'aStringIdForPointsFile' FILE 'theFileNameOfYourPointsFile'</code><br/><br />
where <code>'aStringIdForPointsFile</code> is the name you're giving the list of locations, and <code>'theFileNameOfYourPointsFile</code> is the actual file name. This file should be placed in your base run directory. The file format is ASCII x-y coordinate pairs, no header line, space-delimited, and one point per line, e.g. <br/><br />
x1 y1<br/>x2 y2<br/>x3 y3<br/>...<br />
<br />
The second line describes the outputs you want: <br/><br />
<code>TABLE 'aStringIdForPointsFile' HEADER 'outputFile' HSIGN HSWELL DIR PDIR TDIR TM02 STEEPNESS OUT 20010101.000000 15 MIN</code><br/><br />
where <code>HEADER</code> (or <code>NOHEADER</code>) indicates whether you want a header, <code>'outputFile'</code> is the output file name that SWAN writes to, <code>HSIGN HSWELL...STEEPNESS</code> are a list of the parameters to-be-output, <code>OUT</code> denotes the termination of the list of parameters, <code>20010101.000000</code> indicates when outputting should start in YYYYMMDD.hhmmss format, and <code>15 MIN</code> indicates a 15-minute output interval. Some notes: <br />
<br />
* The header can be nice but it can also sometimes cause format problems if the numeric values being output are too large to fit in the fixed-width columns. If you do <code>NOHEADER</code>, the file won't have this issue, though it can be harder to inspect visually...it'll be just as easy to read it with a computer program or something like Excel. <br />
* The list of parameters you can output is long, and the definitions are even longer. The list is currently on the SWAN website [https://swanmodel.sourceforge.io/online_doc/swanuse/node32.html here] under the description of the <code>BLOCK</code> output command, and has [https://swanmodel.sourceforge.io/online_doc/swanuse/node35.html#app:defvar a link] to the parameter definitions. If that link doesn't work, maybe go to the SWAN user manual [https://swanmodel.sourceforge.io/online_doc/swanuse/swanuse.html base page], then click on "Write or plot computed quantities". <br />
* In a parallel run, for model versions later than roughly ADCIRC version v52, the output should be a single file in the main run directory. In earlier versions, the output was written individually by each subdomain to its PE* folder. <br />
<br />
Note that you can add multiple <code>POINTS</code> and/or <code>TABLE</code> lines for different list of coordinates and/or different outputs. <br />
<br />
=== Writing Alternative Global SWAN Output ===<br />
Have you ever wanted to write different SWAN parameters to output in a coupled ADCIRC+SWAN simulation? If so, these tips and tricks are for you! The current implementations of the dynamically coupled version of ADCIRC+SWAN only write a few SWAN parameters to global time-series output files. Those output parameters and files include:<br />
* spectrally significant wave height (filename: swan_HS.63)<br />
* "smoothed" peak wave period (filename: swan_TPS.63)<br />
* mean absolute wave period (filename: swan_TMM10.63) <br />
* mean wave direction (filename: swan_DIR.63)<br />
* and perhaps others like TM01, TM02, and WIND<br />
<br />
The SWAN model has many other potentially useful output parameters and, in some cases, they may be more appropriate for your needs than these default outputs. For example, what if you preferred seeing the peak wave direction instead of the mean wave direction? Or maybe you need the swell wave height instead of, or in addition to, the significant wave height? The two methods below will allow you to accomplish just this. Granted, this does require that you modify some files within the SWAN and ADCIRC source codes, and that you recompile the source code into your desired executables. We hope the instructions below make the task of modifying the source code a little less daunting. There is one major caveat to the two methods outlined below: it will not allow you to 'define' your desired SWAN output in either the fort.26 file OR in namelist form at the bottom of fort.15. In other words, you will receive whatever outputs you hardwire into your source code and you cannot easily turn them on or off without again modifying the source code. <br />
<br />
==== Method 1 - Very Easy ====<br />
Use the approach described in the [[Tips_and_Tricks#Writing_Alternative_Station_SWAN_Output|last section]]. <br />
<br />
==== Method 2 - Easy but Limited ====<br />
<br />
This is by far the simplest method for modifying SWAN output in a coupled ADCIRC+SWAN simulation. By following the instructions below, you will be able to write any SWAN output you desire… but only to the existing SWAN output files. Existing SWAN output files include swan_HS.63, swan_TPS.63, swan_TMM10.63, swan_DIR.63, etc. This method will not produce NEW or ADDITIONAL SWAN output files. Rather, it will simply write the user-specified output to these existing filenames.<br />
<br />
Go to the swan/ folder in your adcirc source code directory tree and open the file swanout1.f<br />
<br />
You are looking for a variable assignment named IVTYPE in the subroutine named SWOEXA. The IVTYPE value is linked to SWAN output variables. For example, this is what the first IVTYPE definition looks like in my version of SWAN…<br />
<br />
!<br /><br />
! significant wave height<br /><br />
!<br /><br />
IVTYPE = 10<br />
<br />
Keep searching and note the IVTYPE values corresponding to your desired SWAN output variable(s). I have included a few below for reference.<br />
<br />
'''IVTYPE value / variable name'''<br /><br />
10 / significant wave height<br /><br />
44 / swell wave height<br /><br />
12 / peak wave period<br /><br />
14 / peak wave direction<br /><br />
13 / mean wave direction<br /><br />
16 / directional spread<br /><br />
15 / energy transport direction<br /> <br />
17 / average wave length<br /><br />
18 / steepness<br /><br />
<br />
With the IVTYPE value(s) noted, proceed to the src/ directory and open the file couple2swan.F<br />
<br />
Search for the variable IVTYPE. Reassign the IVTYPE values using the values of your desired output. For example, if you want to write the peak wave direction to the “swan_DIR.63” file instead of the mean wave direction, you’d want to change IVTYPE = 13 to IVTYPE = 14. Note that you’ll need to make this change in approximately five places within the couple2swan.F file. The embedded images below show comparisons between the original and modified files for this example (substituting IVTYPE=14 (PDIR) for IVTYPE=13 (DIR)). The change areas appear in the following subroutines of couple2swan.F:<br />
* ComputeWaveFrictionProperties<br />
* SwanOutput<br />
<br />
<br />
You would of course want to make these IVTYPE reassignments for any and all existing SWAN output that you'd like to modify. Keep in mind that you only have four existing files to work with here, so that is ultimately your limit on output parameters as well. You may want to consider renaming your output files so that you do not misinterpret your results. The output filenames are found in src/write_output.F. Using the example IVTYPE reassignment above, you might consider renaming swan_DIR.63 to swan_PDIR.63. If you need more than four output parameters and also want to change the filenames, see Method 2 below.<br />
<br />
<gallery><br />
method1_1.png|Change area 1 of 5 (click to enlarge)<br />
method1_2.png|Change area 2 of 5 (click to enlarge)<br />
method1_3.png|Change area 3 of 5 (click to enlarge)<br />
method1_4.png|Change area 4 of 5 (click to enlarge)<br />
method1_5.png|Change area 5 of 5 (click to enlarge)<br />
</gallery><br />
<br />
==== Method 3 - Moderately Difficult but Limitless ====<br />
<br />
This method is more complex but it will allow you to name and create any number of original SWAN output files. For example, say I wanted to keep the existing default SWAN output files (referenced above in Method 1) but also write the peak wave direction output to a brand new file named swan_PDIR.63. You can do that if you follow the steps below. Note that the example below will also generate a corresponding swan_PDIR_max.63 file in a manner similar to swan_HS_max.63, swan_TPS_max.63, etc. <br />
<br />
In this more complicated (really just more work) method you will need to perform four general tasks:<br />
# Increment an output counter in multiple places (in my example, from 7 to 8 because I am only adding the PDIR output)<br />
# Insert new sections of code pertaining to your desired output<br />
# Create and insert new variable names in GLOBAL and OUTPUT blocks<br />
# Add new code to direct your parameters to output files<br />
<br />
I honestly did this somewhat blindly the first time and it worked just fine (for me). You do need to be very careful and take your time going through the couple2swan.F file and all internal subroutines to make sure you are making all appropriate additions. Like method 1 above, your only modifications will be in couple2swan.F, but you will need to refer to the IVTYPE values found in swan/swanout1.f as described above. <br />
<br />
As was done above, I am providing screenshots of a "diff" comparison between the original and modified couple2swan.F files for this simple example of adding the PDIR output as a new output file. For consistency purposes I do specify PDIR as an output variable in my fort.26 file, but as Casey and others have mentioned in the past I don't think that makes any difference whatsoever. If you follow my example below you would get the PDIR outputs even if you omitted PDIR from the fort.26 file. The change areas appear in the following subroutines of couple2swan.F:<br />
* ComputeWaveFrictionProperties<br />
* SwanOutput<br />
<br />
<br />
<gallery><br />
method2_1.png|Change area 1 of 7 (click to enlarge)<br />
method2_2.png|Change area 2 of 7 (click to enlarge)<br />
method2_3.png|Change area 3 of 7 (click to enlarge)<br />
method2_4.png|Change area 4 of 7 (click to enlarge)<br />
method2_5.png|Change area 5 of 7 (click to enlarge)<br />
method2_6.png|Change area 6 of 7 (click to enlarge)<br />
method2_7.png|Change area 7 of 7 (click to enlarge)<br />
</gallery><br />
<br />
== Post-Processing Tips and Tricks ==</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Tips_and_Tricks&diff=1136Tips and Tricks2024-03-04T21:11:22Z<p>Taylorgasher: initializing new section on SWAN station output</p>
<hr />
<div>This page serves as a catch-all covering methods to achieve common goals or overcome common issues. <br />
<br />
== Pre-Processing Tips and Tricks ==<br />
<br />
== ADCIRC-Only Tips and Tricks ==<br />
* [[fort.15_file#Meteorological-Only Mode|Meteorological-Only Mode]]<br />
* [[fort.15_file#Ramping Meteorological Forcing at Hot-Start|Ramping Meteorological Forcing at Hot-Start]]<br />
<br />
== ADCIRC+SWAN Tips and Tricks ==<br />
=== Writing Alternative Station SWAN Output ===<br />
SWAN has expansive outputting capabilities, but navigating the means of doing these can be a bit difficult. Here's a simple summary of how to output one of various parameters at a user-specified set of locations. <br />
<br />
=== Writing Alternative Global SWAN Output ===<br />
Have you ever wanted to write different SWAN parameters to output in a coupled ADCIRC+SWAN simulation? If so, these tips and tricks are for you! The current implementations of the dynamically coupled version of ADCIRC+SWAN only write a few SWAN parameters to global time-series output files. Those output parameters and files include:<br />
* spectrally significant wave height (filename: swan_HS.63)<br />
* "smoothed" peak wave period (filename: swan_TPS.63)<br />
* mean absolute wave period (filename: swan_TMM10.63) <br />
* mean wave direction (filename: swan_DIR.63)<br />
* and perhaps others like TM01, TM02, and WIND<br />
<br />
The SWAN model has many other potentially useful output parameters and, in some cases, they may be more appropriate for your needs than these default outputs. For example, what if you preferred seeing the peak wave direction instead of the mean wave direction? Or maybe you need the swell wave height instead of, or in addition to, the significant wave height? The two methods below will allow you to accomplish just this. Granted, this does require that you modify some files within the SWAN and ADCIRC source codes, and that you recompile the source code into your desired executables. We hope the instructions below make the task of modifying the source code a little less daunting. There is one major caveat to the two methods outlined below: it will not allow you to 'define' your desired SWAN output in either the fort.26 file OR in namelist form at the bottom of fort.15. In other words, you will receive whatever outputs you hardwire into your source code and you cannot easily turn them on or off without again modifying the source code. <br />
<br />
==== Method 1 - Very Easy ====<br />
Use the approach described in the last section, [[Tips_and_Tricks#Writing_Alternative_Station_SWAN_Output|last section]]<br />
==== Method 2 - Easy but Limited ====<br />
<br />
This is by far the simplest method for modifying SWAN output in a coupled ADCIRC+SWAN simulation. By following the instructions below, you will be able to write any SWAN output you desire… but only to the existing SWAN output files. Existing SWAN output files include swan_HS.63, swan_TPS.63, swan_TMM10.63, swan_DIR.63, etc. This method will not produce NEW or ADDITIONAL SWAN output files. Rather, it will simply write the user-specified output to these existing filenames.<br />
<br />
Go to the swan/ folder in your adcirc source code directory tree and open the file swanout1.f<br />
<br />
You are looking for a variable assignment named IVTYPE in the subroutine named SWOEXA. The IVTYPE value is linked to SWAN output variables. For example, this is what the first IVTYPE definition looks like in my version of SWAN…<br />
<br />
!<br /><br />
! significant wave height<br /><br />
!<br /><br />
IVTYPE = 10<br />
<br />
Keep searching and note the IVTYPE values corresponding to your desired SWAN output variable(s). I have included a few below for reference.<br />
<br />
'''IVTYPE value / variable name'''<br /><br />
10 / significant wave height<br /><br />
44 / swell wave height<br /><br />
12 / peak wave period<br /><br />
14 / peak wave direction<br /><br />
13 / mean wave direction<br /><br />
16 / directional spread<br /><br />
15 / energy transport direction<br /> <br />
17 / average wave length<br /><br />
18 / steepness<br /><br />
<br />
With the IVTYPE value(s) noted, proceed to the src/ directory and open the file couple2swan.F<br />
<br />
Search for the variable IVTYPE. Reassign the IVTYPE values using the values of your desired output. For example, if you want to write the peak wave direction to the “swan_DIR.63” file instead of the mean wave direction, you’d want to change IVTYPE = 13 to IVTYPE = 14. Note that you’ll need to make this change in approximately five places within the couple2swan.F file. The embedded images below show comparisons between the original and modified files for this example (substituting IVTYPE=14 (PDIR) for IVTYPE=13 (DIR)). The change areas appear in the following subroutines of couple2swan.F:<br />
* ComputeWaveFrictionProperties<br />
* SwanOutput<br />
<br />
<br />
You would of course want to make these IVTYPE reassignments for any and all existing SWAN output that you'd like to modify. Keep in mind that you only have four existing files to work with here, so that is ultimately your limit on output parameters as well. You may want to consider renaming your output files so that you do not misinterpret your results. The output filenames are found in src/write_output.F. Using the example IVTYPE reassignment above, you might consider renaming swan_DIR.63 to swan_PDIR.63. If you need more than four output parameters and also want to change the filenames, see Method 2 below.<br />
<br />
<gallery><br />
method1_1.png|Change area 1 of 5 (click to enlarge)<br />
method1_2.png|Change area 2 of 5 (click to enlarge)<br />
method1_3.png|Change area 3 of 5 (click to enlarge)<br />
method1_4.png|Change area 4 of 5 (click to enlarge)<br />
method1_5.png|Change area 5 of 5 (click to enlarge)<br />
</gallery><br />
<br />
==== Method 3 - Moderately Difficult but Limitless ====<br />
<br />
This method is more complex but it will allow you to name and create any number of original SWAN output files. For example, say I wanted to keep the existing default SWAN output files (referenced above in Method 1) but also write the peak wave direction output to a brand new file named swan_PDIR.63. You can do that if you follow the steps below. Note that the example below will also generate a corresponding swan_PDIR_max.63 file in a manner similar to swan_HS_max.63, swan_TPS_max.63, etc. <br />
<br />
In this more complicated (really just more work) method you will need to perform four general tasks:<br />
# Increment an output counter in multiple places (in my example, from 7 to 8 because I am only adding the PDIR output)<br />
# Insert new sections of code pertaining to your desired output<br />
# Create and insert new variable names in GLOBAL and OUTPUT blocks<br />
# Add new code to direct your parameters to output files<br />
<br />
I honestly did this somewhat blindly the first time and it worked just fine (for me). You do need to be very careful and take your time going through the couple2swan.F file and all internal subroutines to make sure you are making all appropriate additions. Like method 1 above, your only modifications will be in couple2swan.F, but you will need to refer to the IVTYPE values found in swan/swanout1.f as described above. <br />
<br />
As was done above, I am providing screenshots of a "diff" comparison between the original and modified couple2swan.F files for this simple example of adding the PDIR output as a new output file. For consistency purposes I do specify PDIR as an output variable in my fort.26 file, but as Casey and others have mentioned in the past I don't think that makes any difference whatsoever. If you follow my example below you would get the PDIR outputs even if you omitted PDIR from the fort.26 file. The change areas appear in the following subroutines of couple2swan.F:<br />
* ComputeWaveFrictionProperties<br />
* SwanOutput<br />
<br />
<br />
<gallery><br />
method2_1.png|Change area 1 of 7 (click to enlarge)<br />
method2_2.png|Change area 2 of 7 (click to enlarge)<br />
method2_3.png|Change area 3 of 7 (click to enlarge)<br />
method2_4.png|Change area 4 of 7 (click to enlarge)<br />
method2_5.png|Change area 5 of 7 (click to enlarge)<br />
method2_6.png|Change area 6 of 7 (click to enlarge)<br />
method2_7.png|Change area 7 of 7 (click to enlarge)<br />
</gallery><br />
<br />
== Post-Processing Tips and Tricks ==</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Dynamic_water_level_correction&diff=1135Dynamic water level correction2023-10-29T19:22:46Z<p>Taylorgasher: Added note about file being read from the start of the run</p>
<hr />
<div>'''Dynamic Water Level Correction''' is a process by which modeled water levels are dynamically adjusted by use of a forcing term. The correction can be applied as constant or varying in space and/or time. The correction is applied as a forcing term in the momentum equations whose mathematical form is equivalent to that of an atmospheric pressure term. This means that, for gradually-varying corrections, corrected water levels should closely follow the input correction, though these may deviate if a correction is applied very quickly or to an area that has a very weak connection to an open boundary through which water can flow. Further discussion is below in the [[#FAQ|FAQ]]. <br />
<br />
Overviews and examples of this capability have been provided in multiple presentations (Luettich et al. 2017<ref name="luettichPres2017">Luettich, R.L., T.G. Asher, B.O. Blanton, J.G. Fleming. Representing Low Frequency, Spatially Varying Water Level Anomalies in Storm Surge Computations. 2017 American Meteorological Society Annual Meeting. [https://ams.confex.com/ams/97Annual/webprogram/Paper316033.html Link to talk]</ref>, Asher et al. 2018<ref name="asherPres2018">Asher, T.G., R.L. Luettich, J.G. Fleming, B.O.Blanton. Assimilation of Observed Water Levels into Storm Surge Model Predictions. 2018 American Meteorological Society Annual Meeting. [https://ams.confex.com/ams/98Annual/webprogram/Paper334044.html Link to talk]</ref>) and a journal article (Asher et al. 2019<ref name="asher2019">Asher, T.G., Luettich Jr., R.A., Fleming, J.G., Blanton, B.O., 2019. Low frequency water level correction in storm surge models using data assimilation. Ocean Modelling 144, 101483. https://doi.org/10.1016/j.ocemod.2019.101483</ref>) with details and an application to Hurricane Matthew. Users looking for ways to generate water level correction surfaces can look to that same article and this digital publication/data repository<ref>Asher, T., 2019. Hurricane Matthew (2016) Storm Surge and Wave Simulations with Data Assimilation. https://doi.org/10.17603/2Z8H-7K90</ref>, which holds the code base used in the aforementioned paper. <br />
<br />
== Version ==<br />
{{ADC version|version=54|relation=ge}} <br />
Early versions of this feature were implemented in v53, however important bug fixes and a renaming of related variables<ref group="note">If using an older version, note that in the fort.15 file, instances of "dynamicWaterLevelCorrection" should be changed to "offset" in the namelist parameter names, e.g. "offsetControl". </ref> were done later, so users are strongly encouraged to not use these earlier versions. <br />
<br />
==Controlling Water Level Correction==<br />
The water level correction feature is triggered by the presence of the &dynamicWaterLevelCorrectionControl namelist at the bottom of the [[fort.15 file]]. Here is an example of how this line is used:<br/><br />
<code>&dynamicWaterLevelCorrectionControl dynamicWaterLevelCorrectionFileName="hsofs_offset_test_ft.dat" dynamicWaterLevelCorrectionMultiplier=0.3048, dynamicWaterLevelCorrectionRampStart=0.0, dynamicWaterLevelCorrectionRampEnd=259200.0 dynamicWaterLevelCorrectionRampReferenceTime="hotstart", dynamicWaterLevelCorrectionSkipSnaps=0 /</code><br />
<br />
* <code>dynamicWaterLevelCorrectionMultiplier</code> allows one to easily change the entire dataset by a single factor, e.g. if the data were provided in feet; ADCIRC requires meters. <br />
* <code>dynamicWaterLevelCorrectionRampStart</code> and <code>dynamicWaterLevelCorrectionRampEnd</code> are the time in seconds for a linear ramp up period. <br />
* <code>dynamicWaterLevelCorrectionRampReferenceTime</code> controls whether the ramp times are relative to the hotstart time or the coldstart time. Prior to the start of the ramp, the correction values are multiplied by 0.0, eliminating the correction until the ramp period starts. <br />
* <code>dynamicWaterLevelCorrectionSkipSnaps</code> is used to skip the specified number of initial data sets in the corrections data file. It can also be used to insert blank snaps at the beginning of the run if it is negative. <br />
<br />
===Water Level Correction Input File===<br />
ADCIRC will begin reading this input file when the run starts, so time snaps are needed from the start of the run. ADCIRC looks for the water level correction input file in the same directory as the other full-domain files, both in serial and in parallel. In parallel, each subdomain does domain decomposition of the correction data on the fly, so the only change to adcprep is the read/write of the new namelist to the subdomain fort.15 files. The water level correction input file starts with the following three header lines:<br />
<br />
<nowiki>#</nowiki> test file for 1ft correction on hsofs mesh during matthew<br />
14400.0 # time increment between datasets, must be positive -- read but ignored if constant correction<br />
0.0 # default correction value<br />
<br />
The first line is a comment line. The second line is the time interval in seconds between successive datasets. The third line is the default correction value; this allows us to create correction input files in a "sparse" format where only the non-default values are provided.If there is only one dataset in the correction file, then the values are treated as temporally constant. If there is more than one dataset, ADCIRC linearly interpolates between them in time. If ADCIRC runs out of correction data, it continues with the last dataset as a set of constant values for the remainder of the run. <br />
<br />
Because each correction dataset may have a different number of values, the # (hash, pound, or number) symbol is used as a separator. Specifically, users should place a line containing # in the first and second columns, i.e. <code>##</code>, of the file after the end of the current time snap of data. When ADCIRC sees this, it understands the next line is the start of the next time snap of data.<br />
<br />
===Output===<br />
If a water level correction input file is specified, then the time interpolated water level correction values will be written to a file called [[offset.63]] on the same schedule as output to the [[fort.63]]. This file can then be used as a diagnostic to check that the correction values have been applied as expected. <br />
<br />
==Compatibility==<br />
Although the correction is implemented as a pseudo barometric pressure, it is entirely independent of any/all meteorological forcing and meteorological data. The values do not show up in the fort.71 (barometric pressure stations) or fort.73 (fulldomain barometric pressure field) output files. The correction can be used with any meteorological forcing data, or with no meteorological forcing data at all. <br />
<br />
==Example==<br />
An ADCIRC model is coldstarted with a tide only run that uses a 10 day ramp, and runs for 15 days. How should the water level correction be configured?<br />
<br />
In this case, I suggest that you apply your bias correction after reaching full strength tidal forcing (i.e., after the 10 day tidal ramp). So to have your bias correction ramp completed at the end of the 15 day tidal spinup, start the ramp period at 10.0 days and end it at 13.0 days. This should ensure you clearly see the correction occurring when you look at the output data, while avoiding applying the correction too rapidly. In summary, set your ramp period in the fort.15 file to <code>dynamicWaterLevelCorrectionRampStart =864000.0, dynamicWaterLevelCorrectionRampEnd = 1036800.0</code><br />
<br />
Since this is the model spin-up period, using a time-constant correction is likely sufficient. That means a single time snap of correction data can be supplied, for example:<br />
<nowiki>#</nowiki> bias correction values test for GFS 20161002 cycle 00Z <br />
99999.9 # time increment in seconds; not used in this case<br />
0.0 # default nodal value applied to any node not specified below<br />
234 0.5<br />
1223 0.6<br />
1789 -0.2<br />
4000 0.1 <br />
##<br />
<br />
After the spinup, in preparation for a forecast run, when you want to migrate from one set of bias correction values to another over a 6 hour time period, the fort.15 file's <code>dynamicWaterLevelCorrectionControl</code> line would be something like this:<br/><br />
<code>&dynamicWaterLevelCorrectionControl dynamicWaterLevelCorrectionFileName= "offset_migration_from_00Z_to_06Z.dat", dynamicWaterLevelCorrectionMultiplier = 1.0, dynamicWaterLevelCorrectionRampStart = 1252800.0, dynamicWaterLevelCorrectionRampEnd = 1296000.0, dynamicWaterLevelCorrectionRampReferenceTime = "coldstart", dynamicWaterLevelCorrectionSkipSnaps = 0 /</code><br />
<br />
and the corresponding file would look like something like the following:<br />
# bias correction values for GFS 20161002 from cycle 00Z to cycle 06Z <br />
21600.0 # 6 hour time increment in seconds<br />
0.0 # default nodal value applied to any node not specified below<br />
234 0.5<br />
1223 0.6<br />
1789 -0.2<br />
4000 0.1 <br />
##<br />
512 0.3<br />
1001 -0.5<br />
2346 0.74<br />
4000 -0.1<br />
##<br />
<br />
At the end of the 15.0 day tidal spinup in this example the bias correction at node 234 would be 0.5. Three hours later (after the hotstart) it would be 0.25. Six hours after the hotstart it would be zero. <br />
<br />
At the end of the 15.0 day tidal spinup in this example the bias correction at node 1001 would be 0.0. Three hours later (after the hotstart) it would be -0.25. Six hours after the hotstart it would be -0.5. <br />
<br />
At the end of the 15.0 day tidal spinup in this example the bias correction at node 4000 would be 0.1. Three hours later (after the hotstart) it would be 0.0. Six hours after the hotstart it would be -0.1.<br />
<br />
==Frequently Asked Questions==<br />
'''Question: '''When writing the &dynamicWaterLevelCorrectionControl namelist, should I write the parameters on a single line, comma separated?<br/><br />
'''Answer: '''I always put fortran namelist parameters on a single line and separate the assignments with commas, but other formatting may be possible depending on the compiler you are using. Commas has always worked for me, but I've not tried any other way. <br />
<br />
'''Question: '''Do I need to ramp the correction, i.e., is it wise to do so for some reason? <br/><br />
'''Answer: '''It should behave the same as a sudden application of atmospheric pressure forcing, which could lead to (presumably spurious) waves. Our shortest ramp up period is 12 hours but you might get away with 6 hours or even less. We have seen that rapidly ramping in the correction can lead to two outcomes that may be undesirable. One is a strong geostrophic current response. The other is that the water level response can lag behind the correction. This is most common for large water bodies with narrow connections to the open ocean, such as Pamlico Sound in North Carolina. Further details are in Asher et al. 2019<ref name="asher2019"></ref>. <br />
<br />
'''Question: '''Does the application of a dynamic water level correction surface affect the velocity solution (not just the elevation solution as it is primarily intended)? <br/><br />
'''Answer: '''Yes, hopefully in a physically realistic manner. As an example, when applying a water level correction to a back bay area with a nearby tidal inlet, the water level change in the back bay must be reflected in the velocity in the inlet in order to maintain continuity (conservation of mass). In the case of an initial application of a temporally steady water level correction, this velocity effect should be a one-time occurrence. On the other hand, for a time varying water level correction surface, the continuous adjustments to the water level will be continuously reflected in the velocity solution. This should be physically realistic when the water ''should have'' come from offshore, but if the elevated water level is due to rainfall, then the model is directing flow in the wrong direction. Further details are in Asher et al. 2019<ref name="asher2019"></ref>. <br />
<br />
==Notes==<br />
<references group="note"/><br />
<br />
==References==<br />
<references /></div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Supplemental_meteorological/wave/ice_parameters&diff=1134Supplemental meteorological/wave/ice parameters2023-06-01T16:42:14Z<p>Taylorgasher: updated wiki formatting in NWS = 6</p>
<hr />
<div>This table is helpful for understanding file requirements and how the [[Fort.15_file_format#WTIMINC|meteorological parameter line]] (informally, the <code>[[WTIMINC]]</code> line) should look in the [[fort.15 file]]. These are principally determined by the value of the <code>[[NWS]]</code> line (also in the fort.15 file), though note that the "NWS" values below are for the [[NWS#Value_Seen_in_fort.15_File|full-length value]] in the fort.15 file. Useful information is also contained in the [[fort.22 file format]] and [[wind stress]] pages. <br />
<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Meteorological Data Format<br />
! [[#Forcing Abbreviations|Forcing]]<br />
! <code>[[NWS]]</code> Value<br />
! <code>[[WTIMINC]]</code> Line<br />
! [[#Requirements|Requirements]]<br />
! [[#Notes|Notes]]<br />
|-<br />
| '''none''' <br />
| nonexistent<br />
| 0<br />
| nonexistent<br />
| none<br />
| none<br />
|- style="background:#efefef;"<br />
| '''wind stress, every node, every timestep'''<br />
| m<br />
| 1<br />
| nonexistent<br />
| f22<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 101<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 301<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 401<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''wind stress, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 2<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|-<br />
|<br />
| m, rs <br />
| 102<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 302<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 402<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''US Navy Fleet Numeric'''<br />
| m<br />
| 3<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
|<br />
| m, rs<br />
| 103<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw <br />
| 303<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st<br />
| 403<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic<br />
| 12003<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
|<br />
| m, rs, ic<br />
| 12103<br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw, ic<br />
| 12303<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st, ic<br />
| 12403<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''PBL/JAG'''<br />
| m<br />
| 4<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
|<br />
| m, rs <br />
| 104<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 304<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, ic <br />
| 12004<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25 <br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12104 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw, ic<br />
| 12304 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st, ic<br />
| 12404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''wind velocity, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 5<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic <br />
| 12005 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''wind velocity, rectangular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 6<br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 106<br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 306<br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 406<br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic <br />
| 12006<br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC cice_timinc</code><br />
| f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12106<br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC RSTIMINC cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12306 <br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC RSTIMINC cice_timinc</code><br />
| f22, A+S, f25 <br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st ,ic<br />
| 12406 <br />
| <code>NWLAT NWLON WLATMAX WLONMIN WLATINC WLONINC WTIMINC RSTIMINC cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''wind stress, regular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 7<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, rs <br />
| 107<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 307<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, st <br />
| 407<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''symmetric vortex model'''<br />
| m<br />
| 8<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| f22<br />
| none<br />
|- <br />
| <br />
| m, rs<br />
| 108<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 308<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st<br />
| 408<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12008<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12108 <br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12308<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12408<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''asymmetric vortex model (no longer available)'''<br />
| n/a<br />
| 9<br />
| n/a<br />
| n/a<br />
| none<br />
|- <br />
| '''National Climatic Data Center GFS'''<br />
| m<br />
| 10<br />
| <code>WTIMINC</code><br />
| f2xx+<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 410<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12010 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12410 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f2xx+, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''National Weather Service ETA 29km'''<br />
| m<br />
| 11<br />
| nonexistent<br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 111<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 311<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 411<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m,ic <br />
| 12011<br />
| <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12111<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12311<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12411<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''Oceanweather Inc (OWI)'''<br />
| m<br />
| 12<br />
| <code>WTIMINC</code><br />
| f22x<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw<br />
| 312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12012<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22x, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;" <br />
| '''Oceanweather Inc (OWI) NetCDF'''<br />
| m<br />
| 13<br />
| <code>WTIMINC</code><br />
| f22nc<br />
| [[NWS13]]<br />
|- style="background:#efefef;" <br />
| <br />
| m, rs<br />
| 113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12013<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''H*Wind'''<br />
| m<br />
| 15<br />
| <code>WTIMINC</code><br />
| hwind+,f22<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw<br />
| 315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12015<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''Geophysical Fluid Dynamics Laboratory (GFDL) Model'''<br />
| m<br />
| 16<br />
| <code>WTIMINC</code><br />
| gfdl+,f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 316<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic <br />
| 12016<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12316 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''Dynamic Asymmetric Model''' <br />
| m<br />
| 19<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| pp,f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 119<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 319<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 419<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12019<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code> <br />
| pp, f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12119<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12319<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12419 <br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''Generalized Asymmetric Holland Model (GAHM)'''<br />
| m<br />
| 20<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code><br />
| pp, f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 120<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 320<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 420<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12020<br />
| <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><br />
| pp, f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12120<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12320<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12420<br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''Blended GAHM and OWI'''<br />
| m<br />
| 30<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 130<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw <br />
| 330<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 430<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic<br />
| 12030<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12130<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12330<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12430<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
|}<br />
<br />
<br />
===Forcing Abbreviations===<br />
: '''m''' - meteorology<br />
: '''rs''' - Wave radiation stress in an analyst-supplied [[fort.23]] input file<br />
: '''sw''' - Wave coupling using a simultaneously executing coupled SWAN model<br />
: '''st''' - Wave coupling using a simultaneously executing ESMF coupled STWAVE model<br />
: '''ic''' - Ice coverage using an analyst-supplied ice coverage data files<br />
<br />
===Requirements===<br />
: '''f22''' - Requires analyst-supplied [[fort.22]] meteorological forcing file.<br />
: '''f2xx+''' - Requires at least two fort.2xx meteorological forcing files from the GFS model. See fort.22 documentation for file naming and formatting details.<br />
: '''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.<br />
: '''hwind+''' - Requires two or more meteorological forcing files from the H*Wind model. See fort.22 documentation for details.<br />
: '''gfdl+''' - Requires two or more meteorological forcing files from the GFDL model. See fort.22 documentation for details.<br />
: '''nwsf22''' - Requires analyst-supplied [[NWS_20_fort.22]] meteorological forcing file.<br />
: '''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.<br />
: '''f23''' - Requires analyst-supplied fort.23 wave radiation stress input file.<br />
: '''A+S''' - Requires ADCIRC+SWAN executable and input files for the coupled version of SWAN.<br />
: '''STW''' - Requires ESMF-coupled ADCIRC and STWAVE and input files for STWAVE.<br />
: '''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.<br />
<br />
===Notes===<br />
<references group="note" /></div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Supplemental_meteorological/wave/ice_parameters&diff=1133Supplemental meteorological/wave/ice parameters2023-06-01T16:34:22Z<p>Taylorgasher: fixing typos in NWS = 6</p>
<hr />
<div>This table is helpful for understanding file requirements and how the [[Fort.15_file_format#WTIMINC|meteorological parameter line]] (informally, the <code>[[WTIMINC]]</code> line) should look in the [[fort.15 file]]. These are principally determined by the value of the <code>[[NWS]]</code> line (also in the fort.15 file), though note that the "NWS" values below are for the [[NWS#Value_Seen_in_fort.15_File|full-length value]] in the fort.15 file. Useful information is also contained in the [[fort.22 file format]] and [[wind stress]] pages. <br />
<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Meteorological Data Format<br />
! [[#Forcing Abbreviations|Forcing]]<br />
! <code>[[NWS]]</code> Value<br />
! <code>[[WTIMINC]]</code> Line<br />
! [[#Requirements|Requirements]]<br />
! [[#Notes|Notes]]<br />
|-<br />
| '''none''' <br />
| nonexistent<br />
| 0<br />
| nonexistent<br />
| none<br />
| none<br />
|- style="background:#efefef;"<br />
| '''wind stress, every node, every timestep'''<br />
| m<br />
| 1<br />
| nonexistent<br />
| f22<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 101<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 301<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 401<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''wind stress, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 2<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|-<br />
|<br />
| m, rs <br />
| 102<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 302<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 402<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''US Navy Fleet Numeric'''<br />
| m<br />
| 3<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
|<br />
| m, rs<br />
| 103<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw <br />
| 303<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st<br />
| 403<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic<br />
| 12003<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
|<br />
| m, rs, ic<br />
| 12103<br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw, ic<br />
| 12303<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st, ic<br />
| 12403<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''PBL/JAG'''<br />
| m<br />
| 4<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
|<br />
| m, rs <br />
| 104<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 304<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, ic <br />
| 12004<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25 <br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12104 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw, ic<br />
| 12304 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st, ic<br />
| 12404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''wind velocity, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 5<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic <br />
| 12005 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''wind velocity, rectangular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 6<br />
| <code>NWLAT</code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 106<br />
| <code>NWLAT</code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 306<br />
| <code>NWLAT</code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 406<br />
| <code>NWLAT</code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic <br />
| 12006<br />
| <code>NWLAT</code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12106<br />
| <code>NWLAT</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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12306 <br />
| <code>NWLAT</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><br />
| f22, A+S, f25 <br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st ,ic<br />
| 12406 <br />
| <code>NWLAT</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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''wind stress, regular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 7<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, rs <br />
| 107<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 307<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, st <br />
| 407<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''symmetric vortex model'''<br />
| m<br />
| 8<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| f22<br />
| none<br />
|- <br />
| <br />
| m, rs<br />
| 108<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 308<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st<br />
| 408<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12008<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12108 <br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12308<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12408<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''asymmetric vortex model (no longer available)'''<br />
| n/a<br />
| 9<br />
| n/a<br />
| n/a<br />
| none<br />
|- <br />
| '''National Climatic Data Center GFS'''<br />
| m<br />
| 10<br />
| <code>WTIMINC</code><br />
| f2xx+<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 410<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12010 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12410 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f2xx+, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''National Weather Service ETA 29km'''<br />
| m<br />
| 11<br />
| nonexistent<br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 111<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 311<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 411<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m,ic <br />
| 12011<br />
| <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12111<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12311<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12411<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''Oceanweather Inc (OWI)'''<br />
| m<br />
| 12<br />
| <code>WTIMINC</code><br />
| f22x<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw<br />
| 312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12012<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22x, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;" <br />
| '''Oceanweather Inc (OWI) NetCDF'''<br />
| m<br />
| 13<br />
| <code>WTIMINC</code><br />
| f22nc<br />
| [[NWS13]]<br />
|- style="background:#efefef;" <br />
| <br />
| m, rs<br />
| 113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12013<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''H*Wind'''<br />
| m<br />
| 15<br />
| <code>WTIMINC</code><br />
| hwind+,f22<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw<br />
| 315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12015<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''Geophysical Fluid Dynamics Laboratory (GFDL) Model'''<br />
| m<br />
| 16<br />
| <code>WTIMINC</code><br />
| gfdl+,f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 316<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic <br />
| 12016<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12316 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''Dynamic Asymmetric Model''' <br />
| m<br />
| 19<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| pp,f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 119<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 319<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 419<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12019<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code> <br />
| pp, f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12119<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12319<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12419 <br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''Generalized Asymmetric Holland Model (GAHM)'''<br />
| m<br />
| 20<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code><br />
| pp, f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 120<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 320<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 420<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12020<br />
| <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><br />
| pp, f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12120<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12320<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12420<br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''Blended GAHM and OWI'''<br />
| m<br />
| 30<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 130<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw <br />
| 330<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 430<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic<br />
| 12030<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12130<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12330<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12430<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
|}<br />
<br />
<br />
===Forcing Abbreviations===<br />
: '''m''' - meteorology<br />
: '''rs''' - Wave radiation stress in an analyst-supplied [[fort.23]] input file<br />
: '''sw''' - Wave coupling using a simultaneously executing coupled SWAN model<br />
: '''st''' - Wave coupling using a simultaneously executing ESMF coupled STWAVE model<br />
: '''ic''' - Ice coverage using an analyst-supplied ice coverage data files<br />
<br />
===Requirements===<br />
: '''f22''' - Requires analyst-supplied [[fort.22]] meteorological forcing file.<br />
: '''f2xx+''' - Requires at least two fort.2xx meteorological forcing files from the GFS model. See fort.22 documentation for file naming and formatting details.<br />
: '''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.<br />
: '''hwind+''' - Requires two or more meteorological forcing files from the H*Wind model. See fort.22 documentation for details.<br />
: '''gfdl+''' - Requires two or more meteorological forcing files from the GFDL model. See fort.22 documentation for details.<br />
: '''nwsf22''' - Requires analyst-supplied [[NWS_20_fort.22]] meteorological forcing file.<br />
: '''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.<br />
: '''f23''' - Requires analyst-supplied fort.23 wave radiation stress input file.<br />
: '''A+S''' - Requires ADCIRC+SWAN executable and input files for the coupled version of SWAN.<br />
: '''STW''' - Requires ESMF-coupled ADCIRC and STWAVE and input files for STWAVE.<br />
: '''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.<br />
<br />
===Notes===<br />
<references group="note" /></div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file_format&diff=1132Fort.15 file format2023-05-18T14:23:35Z<p>Taylorgasher: /* Namelists */ added invertedBarometerOnElevationBoundary</p>
<hr />
<div>The basic file structure of the [[fort.15 file]] is shown below. Each line of input data is represented by a line containing the input variable name(s). Inputs in the [[fort.15 file]] must be entered in the exact order shown on this page. '''Blank lines and headings are only to enhance readability.''' Loops indicate multiple lines of input. <br/><br />
==Main Controls==<br />
===Metadata and Logging===<br />
'''<code>[[RUNDES]]'''</code> - alphanumeric run description 1, 32 characters or less<br/><br />
'''<code>[[RUNID]]'''</code> - alphanumeric run description 2, 24 characters or less<br/><br />
'''<code>[[NFOVER]]'''</code> - non-fatal error override option<br/><br />
'''<code>[[NABOUT]]'''</code> - verbosity of run log output, <code>= -1</code> is debug mode, higher is less output, up to <code>3</code> for errors only<br/><br />
'''<code>[[NSCREEN]]'''</code> - directs log messages to the screen (<code>> 0</code>), the adcirc.log file (<code>< 0</code>), or disables them (<code>= 0</code>)<br/><br />
<!-- Comments<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Parameter<br />
! Type<br />
! Required?<br />
! Description<br />
! Values<br />
|-<br />
| <code>RUNDES</code><br />
| <math>\leq</math>32 character string<br />
| Always<br />
| Run description<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>RUNID</code><br />
| <math>\leq</math>24 character string<br />
| Always<br />
| Run identification<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>[[NFOVER]]</code><br />
| integer<br />
| Always<br />
| Non-fatal error override option <br />
| 0 or 1<br />
|- style="background:#efefef;"<br />
| <code>[[NABOUT]]</code><br />
| integer<br />
| Always<br />
| Logging level <br />
| -1, 0, 1, 2, or 3<br />
|- style="background:#efefef;"<br />
| <code>[[NSCREEN]]</code><br />
| integer<br />
| Always<br />
| Logging output destination<br />
| -1, 0, or 1<br />
|}<br />
--><br />
<br />
===Numerics & Physics===<br />
'''<code>[[IHOT]]'''</code> - whether to read a hotstart file<br/><br />
'''<code>[[ICS]]</code>''' - coordinate projection to run in<br/><br />
'''<code>[[IM]]</code>''' - model run mode<br/><br />
'''<code>[[IDEN]]</code>''' - density forcing mode, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 20, 21, 30, 31</code>, or if <code>IM</code>'s last 6-digit entry is > 4 (e.g., <code>51311<b>5</b></code>).<br/><br />
'''<code>[[NOLIBF]]</code>''' - bottom stress parameterization mode<br/><br />
'''<code>[[NOLIFA]]</code>''' - finite amplitude term and wetting/drying mode, off if <code>= 0</code><br/><br />
'''<code>[[NOLICA]]</code>''' - advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NOLICAT]]</code>''' - time-derivative advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NWP]]</code>''' - number of [[nodal attribute]]s<br/><br />
''for j=1 to <code>[[NWP]]</code>''<br/><br />
: '''<code>[[AttrName(j)]]</code>''' - nodal attributes to use, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NWP]] > 0</code><br/><br />
''end j loop''<br/><br />
'''<code>[[NCOR]]</code>''' - Coriolis control, spatially constant if <code>= 0</code>, varies with latitude if <code>= 1</code><br/><br />
'''<code>[[NTIP]]</code>''' - tidal potential forcing control, off if <code>= 0</code><br/><br />
<span id="NWS"/>'''<code>[[NWS#Value_Seen_in_fort.15_File|NWS]]</code>''' - meteorological, wave, and ice forcing control<br/><br />
'''<code>[[NRAMP]]</code>''' - forcing ramping control<br/><br />
'''<code>[[G]]</code>''' - acceleration due to gravity<br/><br />
'''<code>[[TAU0]]</code>''' - affects numerical diffusion/stability of governing equations<br/><br />
'''<code>[[Tau0FullDomainMin]] [[Tau0FullDomainMax]]</code>''' - limits on <code>[[TAU0]]</code>, ''<span style="background:blanchedalmond">include this line only if:</span>''<code>TAU0 = -5.0</code>.<br/><br />
'''<code>[[DTDP]]</code>''' - model time step (seconds) and predictor-corrector control<br/><br />
'''<code>[[STATIM]]</code>''' - shifts numeric value of starting simulation time (days)<br/><br />
<span id="REFTIM"/>'''<code>[[REFTIM]]</code>''' - shifts reference time (days) for tidal harmonic analysis<br/><br />
<span id="WTIMINC"/><span id="RSTIMINC"/><span id="CICE_TIMINC"/>'''[[Supplemental_Meteorological/Wave/Ice_Parameters|Meteorological controls including <code>WTIMINC, RSTIMINC</code>]]''' - ''<span style="background:blanchedalmond">include this line:</span>'' for most cases of <code>NWS ≠ 0</code>, see linked page for details.<br/><br />
'''<code>[[RNDAY]]</code>''' - end time of simulation (days)<br/><br />
'''[[Ramping|Ramping controls including <code>DRAMP, FluxSettlingTime</code>]]''' - ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>NRAMP > 0</code>, see linked page for details<br/><br />
'''<code>[[A00 B00 C00]]</code>''' - time weighting factors in GWCE<br/><br />
'''<code>[[H0]]</code>''' - minimum depth, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 0</code> or <code>1</code>''<br/><br />
'''<code>[[H0]]</code> <code>INTEGER</code> <code>INTEGER</code> <code>[[VELMIN]]</code>''' - alternate minimum depth controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 2</code> or <code>3</code>''<br/><br />
'''<code>[[SLAM0]] [[SFEA0]]</code>''' - longitude and latitude for center of CPP coordinate projection<br/><br />
'''<code>[[TAU]]</code>''' - linear bottom friction coefficient, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 0</code>''<br/><br />
'''<code>[[CF]]</code>''' - quadratic bottom friction coefficient or limit, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 1</code>''<br/><br />
'''<code>[[CF]]</code> <code>[[HBREAK]]</code> <code>[[FTHETA]]</code> <code>[[FGAMMA]]</code>''' - alternate quadratic bottom friction controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 2</code>''<br/><br />
'''<code>[[ESLM]]</code>''' - horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 0</code>, <code>1</code>, or <code>2</code>''<br/><br />
'''<code>[[ESLM]]</code> <code>[[ESLC]]</code>''' - alternate horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 10</code>''<br/><br />
'''<code>[[CORI]]</code>''' - constant Coriolis coefficient, ''<span style="background:mistyRose">only used if</span>'' <code>NCOR=0</code><br />
<br />
===Periodic (Tidal) Body Forcing===<br />
[[NTIF]]<br/><br />
for k=1 to [[NTIF]]<br />
: [[TIPOTAG(k)]]<br />
: [[TPK(k)]], [[AMIGT(k)]], [[ETRF(k)]], [[FFT(k)]], [[FACET(k)]]<br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Elevations===<br />
[[NBFR]]<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[BOUNTAG(k)]]<br/><br />
: [[AMIG(k)]], [[FF(k)]], [[FACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NETA]]<br/><br />
:: [[EMO(k,j), EFA(k,j)]]<br/><br />
: end j loop<br/><br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Velocities===<br />
[[ANGINN]]<br/><br />
[[NFFR]] - include this line only if [[IBTYPE]] = 2, 12, 22, 32 or 52 in the Grid and Boundary Information File<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[FBOUNTAG(k)]]<br/><br />
: [[FAMIGT(k),FFF(k),FFACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NVEL]]<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]] - use this line if [[IBTYPE]] = 2, 12, 22 in the Grid and Boundary Information File<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]], [[ENAM(k,j), ENPH(k,j)]] - use this line if [[IBTYPE]] = 32 in the Grid and Boundary Information File<br/><br />
:end j loop<br/><br />
end k loop<br />
<br />
===Model Output===<br />
[[NOUTE]], [[TOUTSE]], [[TOUTFE]], [[NSPOOLE]]<br/><br />
[[NSTAE]]<br/><br />
for k=1 to [[NSTAE]]<br/><br />
: [[XEL(k), YEL(k)]] - use these lines if [[NSTAE]] is positive. If negative, stations are listed in the [[elev_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTV]], [[TOUTSV]], [[TOUTFV]], [[NSPOOLV]]<br/><br />
[[NSTAV]]<br/><br />
for k=1 to [[NSTAV]]<br/><br />
: [[XEV(k), YEV(k)]] - use these lines if [[NSTAV]] is positive. If negative, stations are listed in the [[vel_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTC]], [[TOUTSC]], [[TOUTFC]], [[NSPOOLC]] - include this line only if IM =10<br/><br />
[[NSTAC]] - include this line only if IM =10<br/><br />
for k=1 to [[NSTAC]]<br/><br />
: [[XEC(k), YEC(k)]]<br/><br />
end k loop<br/><br />
[[NOUTM]], [[TOUTSM]], [[TOUTFM]], [[NSPOOLM]] - include this line only if NWS is not equal to zero.<br/><br />
[[NSTAM]] - include this line only if NWS is not equal to zero.<br/><br />
for k=1 to [[NSTAM]]<br/><br />
: [[XEM(k), YEM(k)]] - use these lines if [[NSTAM]] is positive. If negative, stations are listed in the [[met_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTGE]], [[TOUTSGE]], [[TOUTFGE]], [[NSPOOLGE]]<br/><br />
[[NOUTGV]], [[TOUTSGV]], [[TOUTFGV]], [[NSPOOLGV]]<br/><br />
[[NOUTGC]], [[TOUTSGC]], [[TOUTFGC]], [[NSPOOLGC]] - include this line only if IM =10<br/><br />
[[NOUTGW]], [[TOUTSGW]], [[TOUTFGW]], [[NSPOOLGW]] - include this line only if NWS is not equal to zero.<br />
<br />
====Harmonic Analysis====<br />
[[NFREQ]]<br/><br />
for k=1 to [[NFREQ]]<br/><br />
: [[NAMEFR(k)]]<br/><br />
: [[HAFREQ(k), HAFF(k), HAFACE(k)]]<br/><br />
end k loop<br/><br />
[[THAS]], [[THAF]], [[NHAINC]], [[FMV]]<br/><br />
[[NHASE]], [[NHASV]], [[NHAGE]], [[NHAGV]]<br />
<br />
====Hotstart Output and Numeric Controls====<br />
[[NHSTAR]], [[NHSINC]]<br/><br />
[[ITITER]], [[ISLDIA]], [[CONVCR]], [[ITMAX]]<br/><br />
<br />
''For a 2DDI ADCIRC run that does not use netCDF nor namelists, the file ends here. For those controls, see further below in the [[#NetCDF Controls|NetCDF Controls]] and [[#Namelists|Namelists]] sections.''<br />
<br />
==3D Model Run==<br />
[[IDEN]]<br/><br />
[[ISLIP]], [[KP]]<br/><br />
[[Z0S,Z0B]]<br/><br />
[[ALP1,ALP2,ALP3]]<br/><br />
[[IGC]], [[NFEN]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IGC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[SIGMA(k)]]<br/><br />
end k loop<br/><br />
[[IEVC]], [[EVMIN]], [[EVCON]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IEVC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[EVTOT(k)]]<br/><br />
end k loop<br/><br />
[[THETA1, THETA2]](include this line only if [[IEVC]] = 50 or 51)<br/><br />
[[I3DSD,TO3DSDS,TO3DSDF,NSPO3DSD]]<br/><br />
[[NSTA3DD]]<br/><br />
for k=1 to [[NSTA3DD]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DSV,TO3DSVS,TO3DSVF,NSPO3DSV]]<br/><br />
[[NSTA3DV]]<br/><br />
for k=1 to [[NSTA3DV]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DST,TO3DSTS,TO3DSTF,NSPO3DST]]<br/><br />
[[NSTA3DT]]<br/><br />
for k=1 to [[NSTA3DT]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DGD]],[[TO3DGDS]],[[TO3DGDF]],[[NSPO3DGD]]<br/><br />
[[I3DGV]],[[TO3DGVS]],[[TO3DGVF]],[[NSPO3DGV]]<br/><br />
[[I3DGT]],[[TO3DGTS]],[[TO3DGTF]],[[NSPO3DGT]]<br/><br />
The following line will be read in if [[IM]] is 21 or 31.<br/><br />
[[RES_BC_FLAG]], [[BCFLAG_LNM]], [[BCFLAG_TEMP]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] is negative.<br/><br />
[[RBCTIMEINC]]<br/><br />
[[BCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 2.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3.<br/><br />
[[RBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 4.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3 or 4 and [[BCFLAG_TEMP]] is not equal to 0.<br/><br />
[[TTBCTIMEINC]], [[TTBCSTATIM]]<br/><br />
[[TTBCTIMEINC]]<br/><br />
The following two lines will be read in only if [[IM]] is 21 or 31.<br/><br />
[[SPONGEDIST]]<br/><br />
[[EQNSTATE]]<br/><br />
The following lines will be read in only if [[IDEN]] is > 0.<br/><br />
[[NLSD, NVSD]]<br/><br />
[[NLTD, NVTD]]<br/><br />
[[ALP4]]<br/><br />
The following line will be read in only if [[IDEN]] = 3 or 4.<br/><br />
[[NTF]]<br />
<br />
==NetCDF Controls==<br />
The following lines will be read in only if the NetCDF output or hotstart format is chosen<br/><br />
NCPROJ<br/><br />
NCINST<br/><br />
NCSOUR<br/><br />
NCHIST<br/><br />
NCREF<br/><br />
NCCOM<br/><br />
NCHOST<br/><br />
NCCONV<br/><br />
NCCONT<br/><br />
NCDATE<br />
<br />
==Namelists==<br />
The following Fortran namelist lines are optional, but if they appear, they must appear at the very end of the fort.15 file.<br/><br />
<code>&metControl WindDragLimit=floatValue, DragLawString='stringValue', rhoAir=floatValue, outputWindDrag=logicalValue /</code><br/><br />
<code>&timeBathyControl NDDT=integerValue, BTIMINC=floatValue, BCHGTIMINC=floatValue, invertedBarometerOnElevationBoundary=logicalValue /</code><br/><br />
<code>&waveCoupling WindWaveMultiplier=floatValue /</code><br/><br />
<code>&SWANOutputControl SWAN_OutputHS=logicalValue, SWAN_OutputDIR=logicalValue, SWAN_OutputTM01=logicalValue, SWAN_OutputTPS=logicalValue, SWAN_OutputWIND=logicalValue, SWAN_OutputTM02=logicalValue, SWAN_OutputTMM10=logicalValue /</code><br/><br />
<code>&subdomainModeling subdomainOn=logicalValue/</code><br/><br />
<code>&wetDryControl outputNodeCode=logicalValue, outputNOFF=logicalValue, noffActive=logicalValue /</code><br/><br />
<code>&inundationOutputControl inundationOutput=logicalValue0, inunThresh =floatValue /</code><br/><br />
<code>&TVWControl use_TVW=logicalValue, TVW_file='stringValue', nout_TVW =integerValue, touts_TVW =floatValue, toutf_TVW=floatValue, nspool_TVW =integerValue /</code><br/><br />
<code>&WarnElevControl WarnElev=floatValue, ErrorElev=floatValue, WarnElevDump=logicalValue, WarnElevDumpLimit=integerValue /</code><br/><br />
<code>[[Dynamic_water_level_correction#Controlling_Water_Level_Correction|&dynamicWaterLevelCorrectionControl]] dynamicWaterLevelCorrectionFileName='stringValue' dynamicWaterLevelCorrectionMultiplier=floatValue, dynamicWaterLevelCorrectionRampStart=floatValue, dynamicWaterLevelCorrectionRampEnd=floatValue, dynamicWaterLevelCorrectionRampReferenceTime='stringValue', dynamicWaterLevelCorrectionSkipSnaps=integerValue /</code><br/><br />
<code>&[[AliDispersionControl]] CAliDisp=logicalValue, Cs=floatValue, Ad=floatValue, Bd=floatValue /</code><br/><br />
[[category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.13_file&diff=1131Fort.13 file2023-02-02T20:22:19Z<p>Taylorgasher: /* Advection State */ Added a note to ease comprehension</p>
<hr />
<div>The fort.13 file contains nodal attributes, which can vary spatially. For each attribute, one or more values are specified at each node. The number of values and their meaning(s) varies by attribute. <br />
<br />
== File Format ==<br />
See [[fort.13 file format]] for details. This file is only read when [[NWP]] > 0 in the Model Parameter and Periodic Boundary Condition File ([[fort.15 file]]). <br />
<br />
== Nodal Attributes ==<br />
Note that units for nodal attributes are specified by the user in the fort.13 file, though ADCIRC may require that attributes be supplied in certain units. <br />
<br />
===Advection State===<br />
'''Nodal attribute name:''' advection_state<br /><br />
'''Description:''' The advection_state nodal attribute is used to provide fine grained control over the NOLICA and NOLICAT parameters, so that they can be set on an element-by-element basis. The bathymetric depth at the three nodes of an element are compared to the corresponding nodal attribute values, and if the bathymetric depth at all three nodes is greater than or equal to the corresponding nodal attribute value, the values of NOLICA and NOLICAT will be set to the value indicated in the Model Parameter and Periodic Boundary Condition (fort.15) file. If the bathymetric depth at any of the three nodes of a particular element is less than the corresponding nodal attribute value, the values of NOLICA and NOLICAT will be set to zero on that element.<br />
<br />
The most common application of this is to set advection_state to a very large positive value (greater than any depth in the mesh) at selected nodes in the fort.13 file at which you want advection to be off. Then, to turn on advection at all other nodes, set the default value in the fort.13 file to a very large negative value, and set NOLICA=1 and NOLICAT=1 in the fort.15 file. <br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Length.<br /><br />
'''Values:''' Any.<br /><br />
'''ADCIRC Variable:''' AdvectionState<br /><br />
<br />
===Bottom Roughness===<br />
'''Nodal attribute name:''' bottom_roughness_length<br /><br />
'''Description:''' Roughness length for 3D bottom friction calculations. Has no effect on a 2DDI ADCIRC run.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Length (m)<br /><br />
'''Values:''' Greater than zero. A reasonable range for the bottom_roughness_length would be 0.001m -0.2m , (densely vegetated overland values would have an upper limit of about 0.2-0.5m and smooth muddy bottoms could have values as low as 0.0001 m).<br /><br />
'''ADCIRC Variable:''' Z0b_var<br /><br />
<br />
=== Bridge Pilings Friction Parameters ===<br />
'''Nodal attribute name:''' bridge_pilings_friction_parameters<br /><br />
'''Description:''' Extra friction from bridge pilings. See Note below.<br /><br />
'''Requirement:''' Very optional.<br /><br />
'''Units:''' Vary, see note below and BK, BALPHA, BDELX and POAN.<br /><br />
'''Values:''' Vary, see note below and BK, BALPHA, BDELX and POAN.<br /><br />
'''ADCIRC Variable:''' BK, BAlpha, BDelX, POAN<br /><br />
'''Note:''' Special considerations must be used when designing a grid for an ADCIRC application that includes the effects of bridge pilings. Specifically, it is necessary to build the grid to provide at least three rows of nodes that parallel the bridge span. One row of nodes (centerline nodes) should lie along the approximate centerline of the bridge while the second and third rows of nodes (adjacent nodes) should lie on either side of the centerline nodes in the along steam direction. An initial implementation of obstruction drag in ADCIRC placed this drag entirely at the row of centerline nodes. However, tests showed that this arrangement led to significant oscillations in the numerical solution. The oscillations abated when the obstruction drag was distributed in the along stream direction so that 25 percent was located at each row of adjacent nodes and 50 percent was located at the row of centerline nodes. Node numbers and coefficient values at all nodes on the centerline and two adjacent rows must be entered in this input file. It is not necessary for centerline nodes to correspond to actual piling positions, (i.e., in the cross stream direction), since the overall effect of the pilings on the large scale circulation is all that is being represented. It is important, however, to construct a grid that is as uniform as possible in the vicinity of the bridge.<br /><br />
<br />
===Chezy Friction Coefficient===<br />
'''Nodal attribute name:''' chezy_friction_coefficient_at_sea_floor<br /> <br />
'''Description:''' Chezy friction coefficient. If the user elects to use this nodal attribute, NOLIBF must be set to 1 or the run will terminate.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Specified by user.<br /><br />
'''Values:''' Greater than zero.<br /> <br />
'''ADCIRC Variable:''' ChezyFric'''<br /> <br />
<br />
===Eddy Viscosity===<br />
'''Nodal attribute name:''' average_horizontal_eddy_viscosity_in_sea_water_wrt_depth<br /><br />
'''Description:''' See description [[horizontal eddy viscosity]].<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' For standard eddy viscosity, units are specified by the user,((length**2)/time). For Smagorinsky-type, unitless.<br /><br />
'''Values:''' Greater than or equal to zero.<br /><br />
'''ADCIRC Variable:''' EVC<br /><br />
<br />
===Elemental Slope Limiter===<br />
'''Nodal attribute name:''' elemental_slope_limiter<br /><br />
'''Description:''' This nodal attribute is used to selectively limit the maximum elevation gradient that can occur across an element, thus improving numerical stability. Alternatively, it is also capable of merely logging individual elements where a specified elemental slope is exceeded at some point during the simulation. When this nodal attribute is loaded, warning messages will be written to the screen and to the fort.16 log file whenever the elevation gradient meets or exceeds the threshold value for the first time at a particular node. When the elemental slope limiter is active at a node, the water surface elevation at that node is reset to the average of the water surface elevations of the surrounding nodes. At the end of the run, a file called ESLNodes.63 will be written to indicate the nodes where the threshold elevation gradient was met or exceeded. Furthermore, If there is an ESLNodes.63 file in the input directory when ADCIRC starts, ADCIRC will load the existing ESLNodes.63 file along with the hotstart file so that the simulation can pick up where it left off, in terms of the elements where the slope is actively limited. When such a simulation finishes, it will overwrite the existing ESLNodes.63 file with a new one that reflects the updated state of limited elemental slopes.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' length/length or unitless.<br /><br />
'''Values:''' Zero indicates that slope limiting is always active at that node, because a zero elevation gradient will always be met or exceeded; a positive value indicates the maximum gradient to be allowed at that node, at or beyond which the slope limiter is activated; a negative number indicates that the elevation gradients should be compared to the absolute value of the nodal attribute at this node. In the case of a negative number, ADCIRC will log a warning to the screen and to the fort.16 file the first time the elemental slope is exceeded, but ESLNodes.63 file will not be affected, and the elemental slope limiting will not actually occur at the node. A suggested value for this nodal attribute is 0.001.<br /><br />
'''ADCIRC Variable:''' elemental_slope_limiter_grad_max<br /><br />
<br />
'''Version Notes:'''<br />
{{ADC version|version=51.47|relation=ge}}<br />
Any activated elemental slope limiter from the previous time step is deactivated and reassessed whether the elevation gradient meets or exceeds the threshold value for the current time step.<br />
{{ADC version|version=51.47|relation=lt}}<br />
Once the elevation gradient is met or exceeded at a node, the elemental slope limiter remains active at that node for the remainder of the ADCIRC run.<br />
<br />
===Initial River Elevation===<br />
'''Nodal attribute name:''' initial_river_elevation<br /><br />
'''Description:''' The initial_river_elevation nodal attribute is used to set the initial water surface elevation at specified nodes. This attribute is functionally identical to the [[Sea Surface Height Above Geoid|<code>sea_surface_height_above_geoid</code>]] attribute, except that any values assigned to elevation-specified boundary conditions in this attribute '''do not''' persist after the start of the simulation. As a result, this attribute is more appropriate for initializing rivers. If both attributes are specified, then the assigned elevation is their sum. Currently, this attribute is only applied if the value supplied at a given node is above zero (i.e. depth less than zero). From cstart.F: <br />
where (River_et_WSE.GT.0.d0)<br />
eta2 = eta2 + River_et_WSE<br />
end where<br />
ADCIRC assumes by default that vertices with negative depths will be dry when the simulation starts. This is, of course, not the case for an inland river whose bed is above mean sea level. This nodal attribute is used in those cases to provide the initial water surface elevation of the river at cold start, and is typically used in conjunction with a flux or elevation [[boundary conditions|boundary condition]] at the inland boundary. See also [[initial conditions]]. <br /><br />
'''Requirement:''' Optional, but recommended if the domain contains a river with an upstream flux boundary condition and a bed elevation above ADCIRC's starting water elevation (zero unless otherwise specified).<br /><br />
'''Units:''' Length.<br /><br />
'''Values:''' Any.<br /><br />
'''ADCIRC Variable:''' <code>River_et_WSE</code>.<br /><br />
<br />
===[[Internal Tide Energy Conversion]]===<br />
{{ADC version|version=53.01|relation=ge}}<br />
'''Nodal attribute name:''' internal_tide_friction<br /><br />
'''Description:''' Linear friction term that accounts for energy conversion from barotropic modes to baroclinic modes as surface tides flow over steep and rough topography in the deep ocean generating internal tides. <br /><br />
'''Requirement:''' Important when simulating tides in computational domains that cover large portions of the deep ocean.<br /><br />
'''Units:''' 1/sec.<br /><br />
'''Values:''' Computed through analytical formulations that are spatially dependent on buoyancy frequencies and topographic gradients.<br /><br />
'''ADCIRC Variable:''' IT_Fric<br /><br />
'''Note:''' IT_Fric can have 1 (scalar) or 3 (tensor) dimensions. The scalar form dissipates equally in all flow directions. The tensor form dissipates asymmetrically to account for the fact that internal tides are generated as surface tides flow across topographic slopes but not along them.<br /><br />
<br />
===[[Manning's n at sea floor]]===<br />
'''Nodal attribute name:''' mannings_n_at_sea_floor<br /><br />
'''Description:''' Manning's n. If the user elects to use this nodal attribute, [[NOLIBF]] must be set to 1 or the run will terminate. During execution, the Manning’s n value specified here is converted to an equivalent quadratic friction coefficient before the bottom stress is calculated. The equivalent quadratic friction coefficient is calculated according to the following formula at each node at each time step: Cd(t)=(g*n^2)/cuberoot(depth[+eta(t)]) where depth is the bathymetric depth and [eta(t)] is the water surface elevation. The addition of the water surface elevation is conditional upon the setting of NOLIFA: eta(t) is treated as zero if NOLIFA is set to zero in the fort.15 file. Finally, the value of CF in the fort.15 is used to set a lower limit on the resulting equivalent quadratic friction coefficient, since the Cd calculated from this formula tends to become small in deep water.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Specified by user.<br /><br />
'''Values:''' Greater than zero.<br /><br />
'''ADCIRC Variable:''' ManningsN<br /><br />
<br />
===Min and Max Primitive Weighting in Continuity Equation===<br />
'''Nodal attribute name:''' min_and_max_primitive_weighting_in_continuity_equation<br /><br />
'''Description:''' Controls upper and lower bounds on [[TAU0]], which affects numerical damping and stability.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Specified by the user, 1/time.<br /><br />
'''Values:''' Information and suggested range supplied in description of [[TAU0]].<br /><br />
'''ADCIRC Variable:''' Tau0MinMax<br/><br />
<br />
===Primitive Weighting in Continuity Equation===<br />
'''Nodal attribute name:''' primitive_weighting_in_continuity_equation<br /><br />
'''Description:''' Related to [[TAU0]], affects numerical damping and stability.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Specified by the user, 1/time.<br /><br />
'''Values:''' Information and suggested range supplied in description of [[TAU0]].<br /><br />
'''ADCIRC Variable:''' Tau0Var<br/><br />
<br />
===Quadratic Friction coefficient===<br />
'''Nodal attribute name:''' quadratic_friction_coefficient_at_sea_floor<br /><br />
'''Description:''' See the description of CF in the Model Parameter and Periodic Boundary Condition File. If the user elects to load this from the fort.13 file, [[NOLIBF]] must be set to 1 or the run will terminate.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Unitless.<br /><br />
'''Values:''' Same as CF.<br /><br />
'''ADCIRC Variable:''' Fric<br /><br />
<br />
===Sea Surface Height Above Geoid===<br />
'''Nodal attribute name:''' sea_surface_height_above_geoid<br /> <br />
'''Description:''' Creates an initial offset of the sea surface from ADCIRC's reference water level (informally, the geoid). If the offset is specified at an elevation boundary such as an open-ocean tidal boundary, it will remain throughout the simulation. Except for that trait, this attribute is functionally identical to the [[initial river elevation|<code>initial_river_elevation</code>]] attribute. Since this attribute does persist along boundaries, it is often used to simulate a steric effect, where water levels are higher in warm seasons because of thermal expansion. See also [[initial conditions]]. <br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Specified by the user (length).<br /><br />
'''Values:''' Any.<br /><br />
'''ADCIRC Variable:''' <code>GeoidOffset</code><br /><br />
<br />
=== Surface Canopy coefficient ===<br />
'''Nodal attribute name:''' surface_canopy_coefficient<br /><br />
'''Description:''' This attribute allows the user to turn off wind stress in heavily forested areas that have been flooded, like a swamp. The canopy shields the water from the effect of the wind.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Unitless.<br /><br />
'''Values:''' Zero if the wind stress should be zero because of a canopy. One otherwise.<br /><br />
'''ADCIRC Variable:''' VCanopy<br /><br />
<br />
===[[Wind_Stress#Roughness_Reductions|Surface Roughness]]===<br />
'''Nodal attribute name:''' surface_directional_effective_roughness_length<br /><br />
'''Description:''' A measure of the “roughness” of the land that can impede wind flow and reduce the surface stress that the wind applies. The ocean would be considered very smooth, and skyscrapers would be considered very rough. This attribute is directional, and the twelve values represent the roughness lengths “seen” by winds blowing from twelve different compass directions at each node. The orientation of the twelve values follows the trigonometric convention, that is, zero degrees represents due east, and the values proceed counter clockwise. In other words, the first value at a node is applied to winds blowing from west to east, the second value applies to winds blowing East-Northeast, etc.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Specified by the user, as is the case for all nodal attributes. The data we use is provided in meters.<br /><br />
'''Values:''' Greater than or equal to zero.<br /><br />
'''ADCIRC Variable:''' z0Land<br /><br />
<br />
===Surface Submergence State===<br />
'''Nodal attribute name:''' surface_submergence_state<br /><br />
'''Description:''' This attribute can force a node to be categorized as dry at the start of the simulation, even if it is below the geoid. This is important for simulating places like New Orleans that are below sea level but are not underwater.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Unitless.<br /><br />
'''Values:''' If set to 1, the node is categorized as dry at the cold start of the simulation. If set to zero, the node is categorized as wet or dry depending on whether its depth is below or above the geoid.<br /><br />
'''ADCIRC Variable:''' StartDry<br /><br />
<br />
===Wave Refraction in SWAN===<br />
'''Nodal attribute name:''' wave_refraction_in_swan<br /><br />
'''Description:''' to turn wave refraction on or off in the SWAN calculations during a coupled ADCIRC+SWAN run. In an ADCIRC-only run, this nodal attribute is ignored.<br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Unitless.<br /><br />
'''Values:''' If set to 1 at a node, wave refraction will be active at that node in the SWAN calculations during a coupled ADCIRC+SWAN run. If set to 0, wave refraction will be deactivated at that node in a coupled ADCIRC+SWAN run.<br /><br />
'''ADCIRC Variable:''' SwanWaveRefrac<br /><br />
<br />
'''Version Notes:'''<br />
{{ADC version|version=53.00|relation=lt}}<br />
Starting with version v41.01B of SWAN and version 53.00 of ADCIRC, this nodal attribute should no longer be used. See post by Casey Dietrich, [https://ccht.ccee.ncsu.edu/updates-to-spectral-propagation-velocities/ here].<br />
<br />
===Absorption-generation Sponge Layer===<br />
'''Nodal attribute name:''' sponge_generator_layer<br /><br />
'''Description:''' <br /><br />
'''Requirement:''' Optional.<br /><br />
'''Units:''' Unitless.<br /><br />
'''Values:''' <br /><br />
<br />
[[Category:input files]]<br />
[[Category:nodal attributes]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Wind_Stress&diff=1130Wind Stress2022-11-17T04:53:57Z<p>Taylorgasher: /* Powell Drag Formulation */</p>
<hr />
<div>When wind blows over the water, it exerts a shear stress at the water surface that transfers horizontal momentum vertically downward across the air–sea interface, driving circulation. In ADCIRC, wind stress is an input forcing term, with several different formats provided. See the <code>[[NWS]]</code> parameter for available formats. In most cases, the exact wind stress to be applied to the model is not provided, therefore ADCIRC must determine how to convert a given wind speed to the actual stress applied at the ocean surface. This page covers the various aspects of this process, as well as the options available to the user. <br />
<br />
== Definition of Winds ==<br />
The characteristics of wind forcing are often broken down in three ways: <br />
# Whether the winds are considered to be over-water (termed "marine exposure") or over-land<br />
# The elevation above the sea (or ground) surface of the winds<br />
# The time-averaging (if any) that has been applied<br />
<br />
ADCIRC generally expects 10-meter, 10-minute winds at their actual exposure, although the exact expectations vary depending on the input type. For instance, when Holland-type wind inputs are provided (e.g. <code>NWS=8</code> or <code>NWS=20</code>), the wind speed is expected to be the '''1-minute [https://en.wikipedia.org/wiki/Maximum_sustained_wind maximum sustained wind]''' at 10 meters elevation. If marine-exposure winds are provided, then [[Fort.13_file#Surface_Roughness|surface roughness]] reductions may be needed<br />
<ref name="simiu1996">Simiu, E., Scanlan, R.H., 1996. Wind effects on structures: fundamentals and applications to design, 3rd ed. ed. John Wiley, New York.</ref><br />
<ref name="simiu2018">Simiu, E., Yeo, D., 2018. Wind effects on structures: modern structural design for wind, Fourth edition. ed. John Wiley & Sons, Hoboken, NJ.</ref><br />
. If winds are provided with a different averaging time, then an appropriate correction may be needed, though winds with averaging times of 10 to 60 minutes are generally considered to be quite similar; this is the so-called mesoscale gap. For recommendations on wind time-scale conversions not handled internally by ADCIRC, for tropical cyclones, see the WMO guidelines of Harper et al.<br />
<ref name="wmotcaveraging">Harper, B., Kepert, J., Ginger, J., 2010. Guidelines for converting between various wind averaging periods in tropical cyclone conditions (No. WMO/TD-No. 1555). WMO, Geneva, Switzerland.</ref><br />
<br />
== Roughness Reductions ==<br />
Reductions in wind speed to convert to the appropriate exposure come from a logarithmic boundary layer formulation (see, e.g. <ref name="simiu1996" /> <ref name="simiu2018" />) to determine a fraction <math>f</math> to reduce the winds, <br />
:<math>f=\left ( \frac{z_{0l}}{z_{0m}}\right ) ^{0.0706} \left ( \frac{\ln \frac{10}{z_{0l}}}{\ln \frac{10}{z_{0m}}} \right ) </math><br />
for marine roughness length <math>z_{0m}</math> and reduced ("land") roughness length <math>z_{0l}</math>. Wind speed is then reduced as, <br />
:<math>\mathbf{w}'=f\mathbf{w}=f [u,v]</math><br />
for x- and y- wind vector components <math>u</math> and <math>v</math>. The marine roughness length is, <br />
:<math>z_{0m}=\frac{0.018}{g} c_d \left \Vert \mathbf{w} \right \| </math><br />
for Charnock parameter <math>0.018</math>, drag coefficient <math>c_d</math> and acceleration due to gravity <math>g</math>. The wind drag coefficient is addressed below in [[#Converting Wind Velocity to Wind Stress|this section]]. As previously noted, the reduced ("land") roughness length <math>z_{0l}</math> is specified by the user via the [[Fort.13_file#Surface_Roughness|surface roughness]] nodal attribute. The fraction <math>f</math> is bounded on <math>[0,1]</math>, meaning the winds cannot be increased, nor change direction. <br />
<br />
=== Older Behavior ===<br />
====Interpolating Roughness Lengths Before v55====<br />
[[File:WindTraceV2.png|right|thumb|Comparison of output wind velocities using old and new methods.]]<br />
{{ADC version|version=55|relation=lt}}Before version 55, the directional wind reductions were applied by determining which of the 12 directional bins the wind velocity (at each time step) fell into, and using that roughness reduction, i.e. nearest neighbor interpolation. Starting in version 55, the roughness length is linearly (in angle space) interpolated between directional bins. In testing, this has been found to generally have a very small effect on water levels, but a notable effect on wind speeds, since time evolution of winds is smoother. It can have large localized effects on water levels in rare cases in cases where there are large changes in neighboring roughness length bins coinciding with well-aligned winds, as in [[:File:MaxeleDiffRun13MinusRun12View1.png|this test case]] with Hurricane Isaac. <br />
<br clear=all><br />
<br />
====Roughness Reduction Bug Before v54====<br />
{{ADC version|version=54|relation=lt}}Before version 54, there was a bug in this calculation. The mistake and its effects are addressed in this PDF document: <u><span style="color:red">'''ADD A LINK TO A PDF HERE YOOOOO'''</span></u>.<br />
<br />
== Converting Wind Velocity to Wind Stress ==<br />
In ADCIRC, four formulations are available to convert wind velocities to the wind stresses applied in the momentum equations. Although there are several ways to control this, users are generally encouraged to use the [[metControl]] namelist in the [[fort.15]] file. The default drag formulation is the Garratt<br />
<ref name=garratt1977>Garratt, J.R., 1977. Review of Drag Coefficients over Oceans and Continents. Mon. Wea. Rev. 105, 915–929. https://doi.org/10.1175/1520-0493(1977)105<0915:RODCOO>2.0.CO;2</ref><br />
linear formula. An alternative for use with tropical cyclones is the Powell formulation,<br />
<ref>Powell, M.D., Vickery, P.J., Reinhold, T.A., 2003. Reduced drag coefficient for high wind speeds in tropical cyclones. Nature 422, 279–283. https://doi.org/10.1038/nature01481</ref><br />
which varies drag by the sector of the tropical cyclone. When ice coverage is included in the model, a wind drag formulation that accounts for this effect should be used. By default, if ice coverage input data are supplied, ADCIRC uses a cubic function of ice coverage, termed the "IceCube" drag formulation. Lastly, the "swell" drag law option allows users to utilize SWAN's drag formulation when employing the coupled model. <br />
<br />
In all cases, the actual wind drag coefficients determined by ADCIRC can be output to a [[fort.63]]-type file named [[winddrag.173]]. Output settings (file format, output start/end times, and output interval) match those of either the fort.63 or fort.73/74 files, ''I think'' fort.73/74. Outputting of this file is enabled by setting <code>outputWindDrag=.TRUE.</code> in the <code>&metControl</code> namelist of the [[Fort.15_file_format#Namelists|fort.15 file's namelist section]]. <br />
<br />
=== Garratt Drag Formulation ===<br />
This is the default wind drag formulation in ADCIRC. From Garratt (1977)<ref name=garratt1977></ref>, the formula is, <br />
:<math>c_d=0.001 \left ( 0.75+0.067 \left \Vert \mathbf{w} \right \| \right ) </math><br />
<br />
By default, ADCIRC puts an upper bound on the drag coefficient of <math>c_d\le0.0035</math>. This upper bound <code>WindDragLimit</code> can be changed via the [[metControl]] fort.15 namelist. <br />
<br />
=== Powell Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
Note that the code for the Powell drag law has not been configured to reverse orientation in the southern hemisphere, and so will produce the wrong results. For details on Powell, see [https://ccht.ccee.ncsu.edu/wind-drag-based-on-storm-sectors/ this post].<br />
<br />
=== IceCube Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:meteorology]]<br />
[[Category:physics]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Tools&diff=1129Tools2022-11-12T17:56:20Z<p>Taylorgasher: Added a bunch of stuff</p>
<hr />
<div>There are a wide host of tools within the ADCIRC community, covering many purposes, and there is not yet a single centralized repository for all of them. This page serves as a host for organizing and linking to these various tools. Tools specifically for model visualization are discussed on the [[visualization]] page. <br />
<br />
Did we miss something? Let us know!<br />
<br />
==Multi-Purpose==<br />
*[https://github.com/jasonfleming/asgs ASGS] enables automated operational simulations of ADCIRC, including acquisition of National Hurricane Center advisory data. <br />
*[https://github.com/natedill/ourPerl/tree/master/AdcircUtils A suite of Perl utilities] can be found on Nate Dill's Github. <br />
*[https://github.com/BrianOBlanton/adcirc_util adcirc_util] is a suite of utilities in Matlab. <br />
*[https://github.com/noaa-ocs-modeling/adcircpy adcircpy] is a suite of utilities in Python. <br />
*[https://github.com/zcobell/ADCIRCModules ADCIRCModules] is a suite of utilities in C++ and Python. <br />
<br />
==Uncategorized==<br />
*[http://adcirc.org/home/related-software/adcirc-utility-programs/ The ADCIRC utilities webpage] hosts several basic and more advanced tools. <br />
<br />
==File Construction==<br />
*[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] facilitates mesh construction and editing. <br />
*[http://adcirc.org/home/related-software/adcirc-utility-programs/ f13builder] helps easily create nodal attributes and the [[fort.13 file]]. <br />
*[https://www.aquaveo.com/software/sms-surface-water-modeling-system-introduction SMS] is a commercial software specially designed for constructing ADCIRC input files and visualizing model outputs.</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Visualization&diff=1128Visualization2022-11-12T17:53:24Z<p>Taylorgasher: Added some small items</p>
<hr />
<div>For more general tools and utilities, see [[Tools]]. In the course of running ADCIRC you may wish to visualize or plot data pertaining to your model. Visualizing data can help you fine tune the mesh design, conduct QA/QC on results, and communicate key facets of the modeling to others. Examples of datasets you might plot include mesh elevation; [[nodal attribute]]s such as [[Manning's n at sea floor|Manning’s n]]; or modeled results such as water surface elevation. For visualizing on a 2D flexible mesh, ADCIRC users often choose to plot them as color contours that follow the mesh triangulation. <br />
<br />
== Plotting Considerations ==<br />
Options abound for generating plots, and the best tool for the job depends on project goals and available resources/software. Some factors to consider in choosing a visualization tool include:<br />
*Interactive vs. static image – do you intend to zoom and pan around your visualized data and/or change contour intervals on the fly, or would you prefer to batch process image files at fixed zoom extents and contour limits?<br />
*Data transfer – do you intend to run simulations on the same computer you visualize results?<br />
*Desired processing speed – does the speed of plotting matter to you? This can be important, e.g. when making videos. <br />
*NetCDF vs. ASCII data – while ADCIRC mesh and nodal attributes input files must take ASCII form, outputs can be ASCII or NetCDF. Consider this since some plotting tools only work with one or the other. A few considerations: <br />
**Multiple applications can read a NetCDF4 file simultaneously, which could save considerable time if you can run your plotting tool concurrently on multiple processors within one compute node. <br />
**NetCDF ADCIRC output files self-contain mesh node, connectivity, and boundary information.<br />
**The learning curve to coding with netCDF files can be much steeper than ASCII. <br />
*Projection – ADCIRC is often run in geographic coordinate system, which references a spherical object; do you need the plotting tool to accurately project geographic coordinates, or is distortion acceptable? <br />
*Which files do you need to visualize? Do you need to plot nodal attribute (fort.13) data, or just ADCIRC output?<br />
*Effort – do you prefer a DIY, high customization approach or a ready-to-run program? Somewhat related question: do you want to buy software or leverage open source libraries? Common items: <br />
**Overlaying a vector field showing wind magnitude and direction or wave direction<br />
**Adding background aerial imagery<br />
**Auto-calculating contour bounds within the specified zoom extents<br />
**Overlaying shapefiles showing county boundaries, inshore waterways, storm track, etc.<br />
<br />
==SMS (Surface-water Modeling System)==<br />
Aquaveo’s SMS software features a suite of many GUI-based pre- and post-processing tools that allow for interactive visualization. SMS requires a license, but out of the box you can easily open and view an ADCIRC mesh and any associated data, including nodal attributes files. SMS plots mesh data as a triangulated irregular network (TIN) surface, allowing the user to change contour intervals as desired. You will need to download files from the HPC you run ADCIRC onto your desktop to plot them with SMS. A few notes about SMS: <br />
*ADCIRC output NetCDF support is “coming soon” as of version 12.1. SMS supports other types of NetCDF data but cannot open a *.63.nc file.<br />
*When ADCIRC output files are opened, SMS automatically converts them from ASCII to binary HDF5 format. This format allows data to load quickly – anecdotal reports estimate this speed to be faster than the same data displayed as a TIN in ArcMap. <br />
*SMS can...<br />
**project data in geographic coordinates properly.<br />
**download zoom-specific aerial imagery to display as a background layer.<br />
**supports vector overlays for fort.74-style ADCIRC data (u v format only, so you need to reformat swan_DIR.63 before displaying as vector field). <br />
**display shapefiles, but with limited options for changing their symbology.<br />
<br />
==FigureGen==<br />
[https://ccht.ccee.ncsu.edu/figuregen-v-49/ FigureGen] (by Casey Dietrich of NC State) batch produces images of model data. FigureGen is a Fortran program that uses the Generic Mapping Tools (GMT) library. To use FigureGen, you must first install GMT and any of its auxiliary programs that don’t already exist on your system. These may already be installed if on a supercomputer. When you compile FigureGen, you can use flags to enable Google Earth output, NetCDF support, and parallel processing. You’ll then edit a text file of input parameters, including zoom extent and required output snaps (for time-varying ADCIRC output file), and FigureGen will generate the series of requested images. A few notes about FigureGen:<br />
*FigureGen is a triple threat – it’s fast, easy to use, and free (but please cite as appropriate!)<br />
*You can typically run FigureGen on the same machine you run ADCIRC, no need to download large output files.<br />
*GMT supports map projections so FigureGen plots geographic coordinates correctly.<br />
*Features options for overlaying a vector field ([[fort.74 file|fort.74]]-style data) including automatically finding the maximum vector magnitude present within the zoom extent.<br />
**Can automatically find the maximum data value present within the zoom extent to set the contour maximum.<br />
**Can overlay a GSHHS shoreline. If your mesh includes detailed inshore waterways, this shoreline may not include sufficient resolution.<br />
**Can add a time bar.<br />
**Can plot the difference between two (scalar?) files. <br />
**Can plot nodal attribute data (except for ''elemental_slope_limiter'', but that is easy to add yourself)<br />
**Can produce several types of image files, and the user can set resolution to control file size.<br />
<br />
==Kalpana==<br />
[https://ccht.ccee.ncsu.edu/kalpana/ Kalpana] (by Rosemary Cyriac) produces either a shapefile or a Google Earth kml file of ADCIRC netCDF output or mesh bathymetry. Kalpana is a Python script that generates color contours using the mesh triangulation via the 2D plotting library Matplotlib, then converts the contours to either shapefile via the Fiona/Shapely libraries, or to kmz via the Simplekml library. Both the shapefile option and kml option produce polygons that enclose areas with data values that fall into one contour bin. <br />
*How-to instructions can be found [https://ccht.ccee.ncsu.edu/how-to-run-kalpana/ here]<br />
*Kalpana is free (but cite as appropriate!)<br />
*No support for plotting nodal attributes parameters yet.<br />
*Shapely/Fiona and Simplekml support map projections and thus properly plot geographic coordinates.<br />
*Like many Python scripts, Kalpana should be run in a virtual environment. Setting up this virtual environment can be simple or frustrating depending on existing system installations on your HPC. Jason Fleming wrote a [https://ccht.ccee.ncsu.edu/installing-python-modules-for-kalpana/ great post on his experience] in installing the various Python libraries within a virtual environment. <br />
*Kalpana runs on an HPC, so you don’t need to download data to your desktop to plot.<br />
*There exists a file size and speed trade-off to the two file format options – the kml option is slower to generate, but the file size is relatively small; the shapefile option generates very quickly (nearly as fast as FigureGen) but the file size is on the order of the size of the file it’s plotting. Also note that the speed of the kml generation depends on the number of lat/long bins you set up in the command line, and the number of bins depends on mesh extent and resolution.<br />
*The shapefiles and kml files produced allow the user to zoom and pan around, but not to dynamically change contour intervals on the fly – the polygons represent an instance or a snapshot of the data.<br />
*Both shapefile and kml are popular file formats with the outside world, so they’re good choices for communicating your model results to others.<br />
*Neither file format supports vector fields. If you want vector fields, you should edit the Kalpana script to skip the Shapely/Fiona or Simplekml parts and use Matplotlib directly to add the vector field and save the Matplotlib plot as a png. <br />
<br />
==ArcGIS==<br />
Esri’s classic software contains no canned tools to read or write ADCIRC data. The user must develop scripts to read ADCIRC files via ArcMap's integrated Python package (ArcPy). Once you’ve imported ADCIRC mesh geometry, nodal attributes, and model results data into a geodatabase, you can easily create a TIN using the mesh triangulation as hard breaklines to view your data in a similar fashion to SMS. Note that the license for ArcMap costs significantly more than an SMS license. So why the heck would you ever consider using ArcStuff for your visualization needs? <br />
*Esri is everywhere – you might already have access to a network license or to colleagues with advanced GIS knowledge.<br />
*While ArcMap doesn’t feature canned tools to read ADCIRC data, it does feature canned geoprocessing tools that can aid greatly in assigning nodal attribute data or interpolating mesh node elevations. For example, you can map data showing land use/land cover in raster or polygon format onto your nodes to assign Manning’s ''n'', or you can create custom schemes for interpolating DEM data onto your mesh nodes.<br />
*As of version 10.3, ArcPy includes the netCDF4 library.<br />
*ArcMap allows for a very high level of customization in your image layout. North arrows, scales, legends, infinite symbology and overlays – wow!<br />
*But, you must download ADCIRC output data from your HPC to wherever your ArcGIS license exists.<br />
<br />
==Python==<br />
See [[tools]]. <br />
<br />
==Matlab==<br />
See [[tools]]. <br />
<br />
==Paraview==<br />
Super powerful, but can be a pain. Tough to generalize here, email the listserv if interested. <br />
<br />
==External Links==<br />
* [https://www.aquaveo.com/software/sms-surface-water-modeling-system-introduction SMS by Aquaveo]<br />
* [https://ccht.ccee.ncsu.edu/figuregen-v-49/ FigureGen v49] NC State Coastal & Computational Hydraulics Team<br />
* [https://ccht.ccee.ncsu.edu/kalpana/ Kalpana] NC State Coastal & Computational Hydraulics Team<br />
* [http://www.adcirc.io/ ADCIRC.io]<br />
* [http://desktop.arcgis.com/en/arcmap/ ArcMap]<br />
* [https://www.mathworks.com/products/matlab.html Matlab]<br />
* [https://www.paraview.org/ Paraview]<br />
* [https://github.com/GenericMappingTools/gmt Generic Mapping Tools (GMT)]<br />
* [https://matplotlib.org/ Matplotlib]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Visualization&diff=1127Visualization2022-11-12T17:40:34Z<p>Taylorgasher: tools link</p>
<hr />
<div>For more general tools and utilities, see [[Tools]]. In the course of running ADCIRC you may wish to visualize or plot data pertaining to your model. Visualizing data can help you fine tune the mesh design, conduct QA/QC on results, and communicate key facets of the modeling to others. Examples of datasets you might plot include mesh elevation; [[nodal attribute]]s such as [[Manning's n at sea floor|Manning’s n]]; or modeled results such as water surface elevation. For visualizing on a 2D flexible mesh, ADCIRC users often choose to plot them as color contours that follow the mesh triangulation. <br />
<br />
== Plotting Considerations ==<br />
Options abound for generating plots, and the best tool for the job depends on project goals and available resources/software. Some factors to consider in choosing a visualization tool include:<br />
*Interactive vs. static image – do you intend to zoom and pan around your visualized data and/or change contour intervals on the fly, or would you prefer to batch process image files at fixed zoom extents and contour limits?<br />
*Data transfer – do you intend to run simulations on the same computer you visualize results?<br />
*Desired processing speed – does the speed of plotting matter to you? This can be important, e.g. when making videos. <br />
*NetCDF vs. ASCII data – while ADCIRC mesh and nodal attributes input files must take ASCII form, outputs can be ASCII or NetCDF. Consider this since some plotting tools only work with one or the other. A few considerations: <br />
**Multiple applications can read a NetCDF4 file simultaneously, which could save considerable time if you can run your plotting tool concurrently on multiple processors within one compute node. <br />
**NetCDF ADCIRC output files self-contain mesh node, connectivity, and boundary information.<br />
**The learning curve to coding with netCDF files can be much steeper than ASCII. <br />
*Projection – ADCIRC is often run in geographic coordinate system, which references a spherical object; do you need the plotting tool to accurately project geographic coordinates, or is distortion acceptable? <br />
*Which files do you need to visualize? Do you need to plot nodal attribute (fort.13) data, or just ADCIRC output?<br />
*Effort – do you prefer a DIY, high customization approach or a ready-to-run program? Somewhat related question: do you want to buy software or leverage open source libraries? Common items: <br />
**Overlaying a vector field showing wind magnitude and direction or wave direction<br />
**Adding background aerial imagery<br />
**Auto-calculating contour bounds within the specified zoom extents<br />
**Overlaying shapefiles showing county boundaries, inshore waterways, storm track, etc.<br />
<br />
==SMS (Surface-water Modeling System)==<br />
Aquaveo’s SMS software features a suite of many GUI-based pre- and post-processing tools that allow for interactive visualization. SMS requires a license, but out of the box you can easily open and view an ADCIRC mesh and any associated data, including nodal attributes files. SMS plots mesh data as a triangulated irregular network (TIN) surface, allowing the user to change contour intervals as desired. You will need to download files from the HPC you run ADCIRC onto your desktop to plot them with SMS. A few notes about SMS: <br />
*ADCIRC output NetCDF support is “coming soon” as of version 12.1. SMS supports other types of NetCDF data but cannot open a *.63.nc file.<br />
*When ADCIRC output files are opened, SMS automatically converts them from ASCII to binary HDF5 format. This format allows data to load quickly – anecdotal reports estimate this speed to be faster than the same data displayed as a TIN in ArcMap. <br />
*SMS can...<br />
**project data in geographic coordinates properly.<br />
**download zoom-specific aerial imagery to display as a background layer.<br />
**supports vector overlays for fort.74-style ADCIRC data (u v format only, so you need to reformat swan_DIR.63 before displaying as vector field). <br />
**display shapefiles, but with limited options for changing their symbology.<br />
<br />
==FigureGen==<br />
[https://ccht.ccee.ncsu.edu/figuregen-v-49/ FigureGen] (by Casey Dietrich of NC State) batch produces images of model data. FigureGen is a Fortran program that uses the Generic Mapping Tools (GMT) library. To use FigureGen, you must first install GMT and any of its auxiliary programs that don’t already exist on your system. These may already be installed if on a supercomputer. When you compile FigureGen, you can use flags to enable Google Earth output, NetCDF support, and parallel processing. You’ll then edit a text file of input parameters, including zoom extent and required output snaps (for time-varying ADCIRC output file), and FigureGen will generate the series of requested images. A few notes about FigureGen:<br />
*FigureGen is a triple threat – it’s fast, easy to use, and free (but please cite as appropriate!)<br />
*You can typically run FigureGen on the same machine you run ADCIRC, no need to download large output files.<br />
*GMT supports map projections so FigureGen plots geographic coordinates correctly.<br />
*Features options for overlaying a vector field ([[fort.74 file|fort.74]]-style data) including automatically finding the maximum vector magnitude present within the zoom extent.<br />
**Can automatically find the maximum data value present within the zoom extent to set the contour maximum.<br />
**Can overlay a GSHHS shoreline. If your mesh includes detailed inshore waterways, this shoreline may not include sufficient resolution.<br />
**Can add a time bar.<br />
**Can plot the difference between two (scalar?) files. <br />
**Can plot nodal attribute data (except for ''elemental_slope_limiter'', but that is easy to add yourself)<br />
**Can produce several types of image files, and the user can set resolution to control file size.<br />
<br />
==Kalpana==<br />
[https://ccht.ccee.ncsu.edu/kalpana/ Kalpana] (by Rosemary Cyriac) produces either a shapefile or a Google Earth kml file of ADCIRC netCDF output or mesh bathymetry. Kalpana is a Python script that generates color contours using the mesh triangulation via the 2D plotting library Matplotlib, then converts the contours to either shapefile via the Fiona/Shapely libraries, or to kmz via the Simplekml library. Both the shapefile option and kml option produce polygons that enclose areas with data values that fall into one contour bin. <br />
*How-to instructions can be found [https://ccht.ccee.ncsu.edu/how-to-run-kalpana/ here]<br />
*Kalpana is free (but cite as appropriate!)<br />
*No support for plotting nodal attributes parameters yet.<br />
*Shapely/Fiona and Simplekml support map projections and thus properly plot geographic coordinates.<br />
*Like many Python scripts, Kalpana should be run in a virtual environment. Setting up this virtual environment can be simple or frustrating depending on existing system installations on your HPC. Jason Fleming wrote a [https://ccht.ccee.ncsu.edu/installing-python-modules-for-kalpana/ great post on his experience] in installing the various Python libraries within a virtual environment. <br />
*Kalpana runs on an HPC, so you don’t need to download data to your desktop to plot.<br />
*There exists a file size and speed trade-off to the two file format options – the kml option is slower to generate, but the file size is relatively small; the shapefile option generates very quickly (nearly as fast as FigureGen) but the file size is on the order of the size of the file it’s plotting. Also note that the speed of the kml generation depends on the number of lat/long bins you set up in the command line, and the number of bins depends on mesh extent and resolution.<br />
*The shapefiles and kml files produced allow the user to zoom and pan around, but not to dynamically change contour intervals on the fly – the polygons represent an instance or a snapshot of the data.<br />
*Both shapefile and kml are popular file formats with the outside world, so they’re good choices for communicating your model results to others.<br />
*Neither file format supports vector fields. If you want vector fields, you should edit the Kalpana script to skip the Shapely/Fiona or Simplekml parts and use Matplotlib directly to add the vector field and save the Matplotlib plot as a png. <br />
<br />
==ArcGIS==<br />
Esri’s classic software contains no canned tools to read or write ADCIRC data. The user must develop scripts to read ADCIRC files via ArcMap's integrated Python package (ArcPy). Once you’ve imported ADCIRC mesh geometry, nodal attributes, and model results data into a geodatabase, you can easily create a TIN using the mesh triangulation as hard breaklines to view your data in a similar fashion to SMS. Note that the license for ArcMap costs significantly more than an SMS license. So why the heck would you ever consider using ArcStuff for your visualization needs? <br />
*Esri is everywhere – you might already have access to a network license or to colleagues with advanced GIS knowledge.<br />
*While ArcMap doesn’t feature canned tools to read ADCIRC data, it does feature canned geoprocessing tools that can aid greatly in assigning nodal attribute data or interpolating mesh node elevations. For example, you can map data showing land use/land cover in raster or polygon format onto your nodes to assign Manning’s ''n'', or you can create custom schemes for interpolating DEM data onto your mesh nodes.<br />
*As of version 10.3, ArcPy includes the netCDF4 library.<br />
*ArcMap allows for a very high level of customization in your image layout. North arrows, scales, legends, infinite symbology and overlays – wow!<br />
*But, you must download ADCIRC output data from your HPC to wherever your ArcGIS license exists.<br />
<br />
==Matlab==<br />
<br />
==Paraview==<br />
<br />
==External Links==<br />
* [https://www.aquaveo.com/software/sms-surface-water-modeling-system-introduction SMS by Aquaveo]<br />
* [https://ccht.ccee.ncsu.edu/figuregen-v-49/ FigureGen v49] NC State Coastal & Computational Hydraulics Team<br />
* [https://ccht.ccee.ncsu.edu/kalpana/ Kalpana] NC State Coastal & Computational Hydraulics Team<br />
* [http://www.adcirc.io/ ADCIRC.io]<br />
* [http://desktop.arcgis.com/en/arcmap/ ArcMap]<br />
* [https://www.mathworks.com/products/matlab.html Matlab]<br />
* [https://www.paraview.org/ Paraview]<br />
* [https://github.com/GenericMappingTools/gmt Generic Mapping Tools (GMT)]<br />
* [https://matplotlib.org/ Matplotlib]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Dynamic_water_level_correction&diff=1126Dynamic water level correction2022-08-23T14:48:57Z<p>Taylorgasher: /* Water Level Correction Input File */ tweak</p>
<hr />
<div>'''Dynamic Water Level Correction''' is a process by which modeled water levels are dynamically adjusted by use of a forcing term. The correction can be applied as constant or varying in space and/or time. The correction is applied as a forcing term in the momentum equations whose mathematical form is equivalent to that of an atmospheric pressure term. This means that, for gradually-varying corrections, corrected water levels should closely follow the input correction, though these may deviate if a correction is applied very quickly or to an area that has a very weak connection to an open boundary through which water can flow. Further discussion is below in the [[#FAQ|FAQ]]. <br />
<br />
Overviews and examples of this capability have been provided in multiple presentations (Luettich et al. 2017<ref name="luettichPres2017">Luettich, R.L., T.G. Asher, B.O. Blanton, J.G. Fleming. Representing Low Frequency, Spatially Varying Water Level Anomalies in Storm Surge Computations. 2017 American Meteorological Society Annual Meeting. [https://ams.confex.com/ams/97Annual/webprogram/Paper316033.html Link to talk]</ref>, Asher et al. 2018<ref name="asherPres2018">Asher, T.G., R.L. Luettich, J.G. Fleming, B.O.Blanton. Assimilation of Observed Water Levels into Storm Surge Model Predictions. 2018 American Meteorological Society Annual Meeting. [https://ams.confex.com/ams/98Annual/webprogram/Paper334044.html Link to talk]</ref>) and a journal article (Asher et al. 2019<ref name="asher2019">Asher, T.G., Luettich Jr., R.A., Fleming, J.G., Blanton, B.O., 2019. Low frequency water level correction in storm surge models using data assimilation. Ocean Modelling 144, 101483. https://doi.org/10.1016/j.ocemod.2019.101483</ref>) with details and an application to Hurricane Matthew. Users looking for ways to generate water level correction surfaces can look to that same article and this digital publication/data repository<ref>Asher, T., 2019. Hurricane Matthew (2016) Storm Surge and Wave Simulations with Data Assimilation. https://doi.org/10.17603/2Z8H-7K90</ref>, which holds the code base used in the aforementioned paper. <br />
<br />
== Version ==<br />
{{ADC version|version=54|relation=ge}} <br />
Early versions of this feature were implemented in v53, however important bug fixes and a renaming of related variables<ref group="note">If using an older version, note that in the fort.15 file, instances of "dynamicWaterLevelCorrection" should be changed to "offset" in the namelist parameter names, e.g. "offsetControl". </ref> were done later, so users are strongly encouraged to not use these earlier versions. <br />
<br />
==Controlling Water Level Correction==<br />
The water level correction feature is triggered by the presence of the &dynamicWaterLevelCorrectionControl namelist at the bottom of the [[fort.15 file]]. Here is an example of how this line is used:<br/><br />
<code>&dynamicWaterLevelCorrectionControl dynamicWaterLevelCorrectionFileName="hsofs_offset_test_ft.dat" dynamicWaterLevelCorrectionMultiplier=0.3048, dynamicWaterLevelCorrectionRampStart=0.0, dynamicWaterLevelCorrectionRampEnd=259200.0 dynamicWaterLevelCorrectionRampReferenceTime="hotstart", dynamicWaterLevelCorrectionSkipSnaps=0 /</code><br />
<br />
* <code>dynamicWaterLevelCorrectionMultiplier</code> allows one to easily change the entire dataset by a single factor, e.g. if the data were provided in feet; ADCIRC requires meters. <br />
* <code>dynamicWaterLevelCorrectionRampStart</code> and <code>dynamicWaterLevelCorrectionRampEnd</code> are the time in seconds for a linear ramp up period. <br />
* <code>dynamicWaterLevelCorrectionRampReferenceTime</code> controls whether the ramp times are relative to the hotstart time or the coldstart time. Prior to the start of the ramp, the correction values are multiplied by 0.0, eliminating the correction until the ramp period starts. <br />
* <code>dynamicWaterLevelCorrectionSkipSnaps</code> is used to skip the specified number of initial data sets in the corrections data file. It can also be used to insert blank snaps at the beginning of the run if it is negative. <br />
<br />
===Water Level Correction Input File===<br />
ADCIRC looks for the water level correction input file in the same directory as the other full-domain files, both in serial and in parallel. In parallel, each subdomain does domain decomposition of the correction data on the fly, so the only change to adcprep is the read/write of the new namelist to the subdomain fort.15 files. The water level correction input file starts with the following three header lines:<br />
<br />
<nowiki>#</nowiki> test file for 1ft correction on hsofs mesh during matthew<br />
14400.0 # time increment between datasets, must be positive -- read but ignored if constant correction<br />
0.0 # default correction value<br />
<br />
The first line is a comment line. The second line is the time interval in seconds between successive datasets. The third line is the default correction value; this allows us to create correction input files in a "sparse" format where only the non-default values are provided.If there is only one dataset in the correction file, then the values are treated as temporally constant. If there is more than one dataset, ADCIRC linearly interpolates between them in time. If ADCIRC runs out of correction data, it continues with the last dataset as a set of constant values for the remainder of the run. <br />
<br />
Because each correction dataset may have a different number of values, the # (hash, pound, or number) symbol is used as a separator. Specifically, users should place a line containing # in the first and second columns, i.e. <code>##</code>, of the file after the end of the current time snap of data. When ADCIRC sees this, it understands the next line is the start of the next time snap of data.<br />
<br />
===Output===<br />
If a water level correction input file is specified, then the time interpolated water level correction values will be written to a file called [[offset.63]] on the same schedule as output to the [[fort.63]]. This file can then be used as a diagnostic to check that the correction values have been applied as expected. <br />
<br />
==Compatibility==<br />
Although the correction is implemented as a pseudo barometric pressure, it is entirely independent of any/all meteorological forcing and meteorological data. The values do not show up in the fort.71 (barometric pressure stations) or fort.73 (fulldomain barometric pressure field) output files. The correction can be used with any meteorological forcing data, or with no meteorological forcing data at all. <br />
<br />
==Example==<br />
An ADCIRC model is coldstarted with a tide only run that uses a 10 day ramp, and runs for 15 days. How should the water level correction be configured?<br />
<br />
In this case, I suggest that you apply your bias correction after reaching full strength tidal forcing (i.e., after the 10 day tidal ramp). So to have your bias correction ramp completed at the end of the 15 day tidal spinup, start the ramp period at 10.0 days and end it at 13.0 days. This should ensure you clearly see the correction occurring when you look at the output data, while avoiding applying the correction too rapidly. In summary, set your ramp period in the fort.15 file to <code>dynamicWaterLevelCorrectionRampStart =864000.0, dynamicWaterLevelCorrectionRampEnd = 1036800.0</code><br />
<br />
Since this is the model spin-up period, using a time-constant correction is likely sufficient. That means a single time snap of correction data can be supplied, for example:<br />
<nowiki>#</nowiki> bias correction values test for GFS 20161002 cycle 00Z <br />
99999.9 # time increment in seconds; not used in this case<br />
0.0 # default nodal value applied to any node not specified below<br />
234 0.5<br />
1223 0.6<br />
1789 -0.2<br />
4000 0.1 <br />
##<br />
<br />
After the spinup, in preparation for a forecast run, when you want to migrate from one set of bias correction values to another over a 6 hour time period, the fort.15 file's <code>dynamicWaterLevelCorrectionControl</code> line would be something like this:<br/><br />
<code>&dynamicWaterLevelCorrectionControl dynamicWaterLevelCorrectionFileName= "offset_migration_from_00Z_to_06Z.dat", dynamicWaterLevelCorrectionMultiplier = 1.0, dynamicWaterLevelCorrectionRampStart = 1252800.0, dynamicWaterLevelCorrectionRampEnd = 1296000.0, dynamicWaterLevelCorrectionRampReferenceTime = "coldstart", dynamicWaterLevelCorrectionSkipSnaps = 0 /</code><br />
<br />
and the corresponding file would look like something like the following:<br />
# bias correction values for GFS 20161002 from cycle 00Z to cycle 06Z <br />
21600.0 # 6 hour time increment in seconds<br />
0.0 # default nodal value applied to any node not specified below<br />
234 0.5<br />
1223 0.6<br />
1789 -0.2<br />
4000 0.1 <br />
##<br />
512 0.3<br />
1001 -0.5<br />
2346 0.74<br />
4000 -0.1<br />
##<br />
<br />
At the end of the 15.0 day tidal spinup in this example the bias correction at node 234 would be 0.5. Three hours later (after the hotstart) it would be 0.25. Six hours after the hotstart it would be zero. <br />
<br />
At the end of the 15.0 day tidal spinup in this example the bias correction at node 1001 would be 0.0. Three hours later (after the hotstart) it would be -0.25. Six hours after the hotstart it would be -0.5. <br />
<br />
At the end of the 15.0 day tidal spinup in this example the bias correction at node 4000 would be 0.1. Three hours later (after the hotstart) it would be 0.0. Six hours after the hotstart it would be -0.1.<br />
<br />
==Frequently Asked Questions==<br />
'''Question: '''When writing the &dynamicWaterLevelCorrectionControl namelist, should I write the parameters on a single line, comma separated?<br/><br />
'''Answer: '''I always put fortran namelist parameters on a single line and separate the assignments with commas, but other formatting may be possible depending on the compiler you are using. Commas has always worked for me, but I've not tried any other way. <br />
<br />
'''Question: '''Do I need to ramp the correction, i.e., is it wise to do so for some reason? <br/><br />
'''Answer: '''It should behave the same as a sudden application of atmospheric pressure forcing, which could lead to (presumably spurious) waves. Our shortest ramp up period is 12 hours but you might get away with 6 hours or even less. We have seen that rapidly ramping in the correction can lead to two outcomes that may be undesirable. One is a strong geostrophic current response. The other is that the water level response can lag behind the correction. This is most common for large water bodies with narrow connections to the open ocean, such as Pamlico Sound in North Carolina. Further details are in Asher et al. 2019<ref name="asher2019"></ref>. <br />
<br />
'''Question: '''Does the application of a dynamic water level correction surface affect the velocity solution (not just the elevation solution as it is primarily intended)? <br/><br />
'''Answer: '''Yes, hopefully in a physically realistic manner. As an example, when applying a water level correction to a back bay area with a nearby tidal inlet, the water level change in the back bay must be reflected in the velocity in the inlet in order to maintain continuity (conservation of mass). In the case of an initial application of a temporally steady water level correction, this velocity effect should be a one-time occurrence. On the other hand, for a time varying water level correction surface, the continuous adjustments to the water level will be continuously reflected in the velocity solution. This should be physically realistic when the water ''should have'' come from offshore, but if the elevated water level is due to rainfall, then the model is directing flow in the wrong direction. Further details are in Asher et al. 2019<ref name="asher2019"></ref>. <br />
<br />
==Notes==<br />
<references group="note"/><br />
<br />
==References==<br />
<references /></div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=User:Taylorgasher&diff=1111User:Taylorgasher2022-06-24T17:36:05Z<p>Taylorgasher: </p>
<hr />
<div>My user page<br />
<br />
== etc. ==<br />
<nowiki><nowiki>'''not bold text''' ''not italic text'' not ADC version {{ADC version|version=-4E7|relation=ge}} </nowiki></nowiki><br />
<br />
<nowiki>A redirect: #REDIRECT [[Fort.13_file#Nodal_Attributes]]</nowiki><br />
<br />
<nowiki><!--comment text<br/><br />
<br />
<br />
(that can span multiple lines in the code)--></nowiki><!--the real comment text, sucka!!!--><br />
<br />
== syntax highlivin ==<br />
monty<br />
<syntaxhighlight lang="python" line='line'><br />
def quick_sort(arr):<br />
less = []<br />
pivot_list = []<br />
more = []<br />
if len(arr) <= 1:<br />
return arr<br />
else:<br />
pass<br />
</syntaxhighlight><br />
<br />
fortless<br />
<syntaxhighlight lang="fortran" line='line'><br />
! I N I T W I N D M O D U L E<br />
! ----------------------------------------------------------------<br />
subroutine initWindModule()<br />
use mesh, only : np<br />
call setMessageSource("initWindModule")<br />
#if defined(WIND_TRACE) || defined(ALL_TRACE)<br />
call allMessage(DEBUG,"Enter.")<br />
#endif<br />
allocate ( wvnx1(np),wvny1(np) )<br />
allocate ( wvnx2(np),wvny2(np) )<br />
allocate ( prn1(np) )<br />
allocate ( prn2(np) )<br />
<br />
C well this commenting approach does not work<br />
if(yourMom.eq.fat)then<br />
write(*,*)'ahahahahaha'<br />
endif !looks like this doesn't work<br />
IF((EyeLat(1).EQ.0.D0).OR.(EyeLon(1).EQ.0.D0).OR.<br />
& (EyeLat(2).EQ.0.D0).OR.(EyeLon(2).EQ.0.D0).OR.<br />
& (EyeLat(3).EQ.0.D0).OR.(EyeLon(3).EQ.0.D0))THEN<br />
FoundEye = .FALSE.<br />
ENDIF<br />
<br />
!.... tcm v49.16 20100617 added<br />
!.... convert background pressure from millibars to meters of water<br />
PRBCKGRND_MH2O = 100.0D0*PRBCKGRND/(RHOWAT0*G)<br />
prn1 = PRBCKGRND_MH2O<br />
prn2 = PRBCKGRND_MH2O<br />
<br />
CALL checkWindDragType()<br />
CALL mapWindDragFunctionPointer()<br />
<br />
#if defined(WIND_TRACE) || defined(ALL_TRACE)<br />
call allMessage(DEBUG,"Return.")<br />
#endif<br />
call unsetMessageSource()<br />
<br />
! ----------------------------------------------------------------<br />
END SUBROUTINE initWindModule<br />
! ----------------------------------------------------------------<br />
</syntaxhighlight><br />
== some mats ==<br />
:<math>a_b(c)=\left ( \frac{de^2}{\sqrt[6]{f+\alpha(\beta)}} \right ) ^{\Tau^\tau}</math><br />
<br />
<br />
<!--:<math>\{A|A\in\mathbb{E}\land\}</math>--><br />
<br />
:<math>\{ A \mid A \in \mathbb{E} \land \mathbb{E} - (N \cup R) \} </math><br />
for <math>A</math> Andrew, <math>\mathbb{E}</math> the entire space, <math>N</math> Nickelback fans, and <math>R</math> Republicans.<br />
<br />
== linky ==<br />
<nowiki>[[#test table| link to subsection or anchor in same page]]</nowiki>[[#test table| link to subsection or anchor in same page]]<br />
<br />
== test table ==<br />
but<br />
<br />
{| class="wikitable"<br />
|-<br />
| apple || pear<br />
|-<br />
| orange || grape <br />
|}<br />
<br />
srsly<br />
<br />
{| style="background-color: orange; border-style: solid; border-width: 2px"<br />
|-<br />
| <br />
{| style="border-style: solid; border-width: 4px"<br />
| ap || ple<br />
|}<br />
|<br />
{| style="border-style: solid; border-width: 4px"<br />
| pe || ar<br />
|}<br />
|-<br />
| <br />
{| style="border-style: solid; border-width: 4px"<br />
| ora || nge<br />
|}<br />
|<br />
{| style="border-style: solid; border-width: 4px"<br />
| gr || ape<br />
|}<br />
|}<br />
<br />
Some norma text<br />
<br />
<br />
== wind drag in/out notes ==<br />
see email with John, subject line "Outputting wind drag coefficients"<br />
<br />
<br />
winddrag.173<br />
or <br />
winddrag.173.nc<br />
<br />
outputWindDrag=.true.<br />
<br />
&metControl<br />
<br />
from ncdump -h winddrag.173.nc: <br />
<br />
double winddrag(time, node) ;<br />
winddrag:long_name = "wind drag coefficient at sea level" ;<br />
winddrag:standard_name = "wind drag coefficient" ;<br />
winddrag:coordinates = "time y x" ;<br />
winddrag:location = "node" ;<br />
winddrag:mesh = "adcirc_mesh" ;<br />
winddrag:units = "unitless" ;<br />
winddrag:_FillValue = -99999. ;<br />
<br />
<br />
<br />
<br />
<br />
== test transclus ==<br />
<!--{{:Manning's n at sea floor#model specification}}--><br />
<br />
<br />
<br />
<br />
== yup ==<br />
Internal tide energy conversion refers to the energy conversion from barotropic to baroclinic modes as surface tides flow over steep and rough topography in the deep ocean generating internal tides. The "lost" barotropic tidal energy is often accounted for through a linear friction term in large-scale numerical models that are barotropic or not fine-scaled enough to resolve the energy conversion. It is implemented in ADCIRC through a spatially varying [[nodal attribute]] called [[internal_tide_friction]], in the [[fort.13 file]].<br />
<br />
== Background and Theory ==<br />
For a review.<ref>C. Garrett, E. Kunze, Internal Tide Generation in the Deep Ocean, Annu. Rev. Fluid Mech. 39 (2007) 57–87. doi:10.1146/annurev.fluid.39.050905.110227.</ref><br />
<br />
How it was known that internal energy conversion is important to the global energy balance of the surface tides.<ref>G.D. Egbert, R.D. Ray, Significant dissipation of tidal energy in the deep ocean inferred from satellite altimeter data, Nature. 405 (2000) 775–778. doi:10.1038/35015531</ref><ref>G.D. Egbert, R.D. Ray, Estimates of M2 tidal energy dissipation from TOPEX/Poseidon altimeter data, J. Geophys. Res. Ocean. 106 (2001) 22475–22502. doi:10.1029/2000JC000699.</ref><br />
<br />
== Attribute Summary ==<br />
In a computational domain covering a large portion of the deep ocean it is critical to include the effect of internal tide energy conversion to obtain more accurate tidal solutions. The user should only elect to use the internal_tide_friction nodal attribute when tides are included in the simulation through tidal boundary conditions and tidal potential functions. The attribute is unnecessary for domains that are small in size and/or do not cover a significant portion of the deep ocean (taken here to mean the portion of the ocean excluding the continental shelf). <br />
<br />
ADCIRC reads the internal_tide_friction attribute in as the ''IT_Fric'' variable, which can have 1 (scalar) or 3 (tensor) dimensions. The attribute has dimensions of [1/time], meaning that it is a linear friction term which is multiplied by the velocity in the governing equations, and is normalized by the ocean depth prior to simulation. Hence, it ignores the water surface elevation portion of the total water depth, which is reasonable since the term and theory it is based on is only applicable to deep ocean. Typically, it is only applied to ocean depths greater than 100-500 m.<br />
<br />
== Specifying ''IT_Fric'' Values ==<br />
''IT_Fric'' values are determined through analytical formulations based on Bell's linear theory<ref name="Bell1975">{{cite journal|last1=Bell|first1=T.H.|title=Topographically generated internal waves in the open ocean|journal=Journal of Geophysical Research|volume=80|year=1975|pages=320–327|doi=10.1029/JC080i003p00320}}</ref>, valid in what is called sub-critical topography. <br />
<br />
Recent publications using ADCIRC<ref>W.J. Pringle, D. Wirasaet, A. Suhardjo, J. Meixner, J.J. Westerink, A.B. Kennedy, S. Nong, Finite-Element Barotropic Model for the Indian and Western Pacific Oceans: Tidal Model-Data Comparisons and Sensitivities, Ocean Model. 129 (2018) 13–38. doi:10.1016/j.ocemod.2018.07.003.</ref><ref>W.J. Pringle, D. Wirasaet, J.J. Westerink, Modifications to Internal Tide Conversion Parameterizations and Implementation into Barotropic Ocean Models, EarthArXiv. (2018) 9. doi:10.31223/osf.io/84w53.</ref> provide relevant formulation and implementation details. <br />
<br />
==References==<br />
{{Reflist}}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file_format&diff=1105Fort.15 file format2022-06-23T19:35:23Z<p>Taylorgasher: /* Main Controls */ updated formatting in top sections</p>
<hr />
<div>The basic file structure of the [[fort.15 file]] is shown below. Each line of input data is represented by a line containing the input variable name(s). Inputs in the [[fort.15 file]] must be entered in the exact order shown on this page. '''Blank lines and headings are only to enhance readability.''' Loops indicate multiple lines of input. <br/><br />
==Main Controls==<br />
===Metadata and Logging===<br />
'''<code>[[RUNDES]]'''</code> - alphanumeric run description 1, 32 characters or less<br/><br />
'''<code>[[RUNID]]'''</code> - alphanumeric run description 2, 24 characters or less<br/><br />
'''<code>[[NFOVER]]'''</code> - non-fatal error override option<br/><br />
'''<code>[[NABOUT]]'''</code> - verbosity of run log output, <code>= -1</code> is debug mode, higher is less output, up to <code>3</code> for errors only<br/><br />
'''<code>[[NSCREEN]]'''</code> - directs log messages to the screen (<code>> 0</code>), the adcirc.log file (<code>< 0</code>), or disables them (<code>= 0</code>)<br/><br />
<!-- Comments<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Parameter<br />
! Type<br />
! Required?<br />
! Description<br />
! Values<br />
|-<br />
| <code>RUNDES</code><br />
| <math>\leq</math>32 character string<br />
| Always<br />
| Run description<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>RUNID</code><br />
| <math>\leq</math>24 character string<br />
| Always<br />
| Run identification<br />
| Any alpha-numeric <br />
|- style="background:#efefef;"<br />
| <code>[[NFOVER]]</code><br />
| integer<br />
| Always<br />
| Non-fatal error override option <br />
| 0 or 1<br />
|- style="background:#efefef;"<br />
| <code>[[NABOUT]]</code><br />
| integer<br />
| Always<br />
| Logging level <br />
| -1, 0, 1, 2, or 3<br />
|- style="background:#efefef;"<br />
| <code>[[NSCREEN]]</code><br />
| integer<br />
| Always<br />
| Logging output destination<br />
| -1, 0, or 1<br />
|}<br />
--><br />
<br />
===Numerics & Physics===<br />
'''<code>[[IHOT]]'''</code> - whether to read a hotstart file<br/><br />
'''<code>[[ICS]]</code>''' - coordinate projection to run in<br/><br />
'''<code>[[IM]]</code>''' - model run mode<br/><br />
'''<code>[[IDEN]]</code>''' - density forcing mode, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 20, 21, 30, 31</code>, or if <code>IM</code>'s last 6-digit entry is > 4 (e.g., <code>51311<b>5</b></code>).<br/><br />
'''<code>[[NOLIBF]]</code>''' - bottom stress parameterization mode<br/><br />
'''<code>[[NOLIFA]]</code>''' - finite amplitude term and wetting/drying mode, off if <code>= 0</code><br/><br />
'''<code>[[NOLICA]]</code>''' - advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NOLICAT]]</code>''' - time-derivative advection term mode, off if <code>= 0</code>, on if <code>= 1</code><br/><br />
'''<code>[[NWP]]</code>''' - number of [[nodal attribute]]s<br/><br />
''for j=1 to <code>[[NWP]]</code>''<br/><br />
: '''<code>[[AttrName(j)]]</code>''' - nodal attributes to use, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NWP]] > 0</code><br/><br />
''end j loop''<br/><br />
'''<code>[[NCOR]]</code>''' - Coriolis control, spatially constant if <code>= 0</code>, varies with latitude if <code>= 1</code><br/><br />
'''<code>[[NTIP]]</code>''' - tidal potential forcing control, off if <code>= 0</code><br/><br />
<span id="NWS"/>'''<code>[[NWS#Value_Seen_in_fort.15_File|NWS]]</code>''' - meteorological, wave, and ice forcing control<br/><br />
'''<code>[[NRAMP]]</code>''' - forcing ramping control<br/><br />
'''<code>[[G]]</code>''' - acceleration due to gravity<br/><br />
'''<code>[[TAU0]]</code>''' - affects numerical diffusion/stability of governing equations<br/><br />
'''<code>[[Tau0FullDomainMin]] [[Tau0FullDomainMax]]</code>''' - limits on <code>[[TAU0]]</code>, ''<span style="background:blanchedalmond">include this line only if:</span>''<code>TAU0 = -5.0</code>.<br/><br />
'''<code>[[DTDP]]</code>''' - model time step (seconds) and predictor-corrector control<br/><br />
'''<code>[[STATIM]]</code>''' - shifts numeric value of starting simulation time (days)<br/><br />
<span id="REFTIM"/>'''<code>[[REFTIM]]</code>''' - shifts reference time (days) for tidal harmonic analysis<br/><br />
<span id="WTIMINC"/><span id="RSTIMINC"/><span id="CICE_TIMINC"/>'''[[Supplemental_Meteorological/Wave/Ice_Parameters|Meteorological controls including <code>WTIMINC, RSTIMINC</code>]]''' - ''<span style="background:blanchedalmond">include this line:</span>'' for most cases of <code>NWS ≠ 0</code>, see linked page for details.<br/><br />
'''<code>[[RNDAY]]</code>''' - end time of simulation (days)<br/><br />
'''[[Ramping|Ramping controls including <code>DRAMP, FluxSettlingTime</code>]]''' - ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>NRAMP > 0</code>, see linked page for details<br/><br />
'''<code>[[A00 B00 C00]]</code>''' - time weighting factors in GWCE<br/><br />
'''<code>[[H0]]</code>''' - minimum depth, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 0</code> or <code>1</code>''<br/><br />
'''<code>[[H0]]</code> <code>INTEGER</code> <code>INTEGER</code> <code>[[VELMIN]]</code>''' - alternate minimum depth controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIFA]] = 2</code> or <code>3</code>''<br/><br />
'''<code>[[SLAM0]] [[SFEA0]]</code>''' - longitude and latitude for center of CPP coordinate projection<br/><br />
'''<code>[[TAU]]</code>''' - linear bottom friction coefficient, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 0</code>''<br/><br />
'''<code>[[CF]]</code>''' - quadratic bottom friction coefficient or limit, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 1</code>''<br/><br />
'''<code>[[CF]]</code> <code>[[HBREAK]]</code> <code>[[FTHETA]]</code> <code>[[FGAMMA]]</code>''' - alternate quadratic bottom friction controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[NOLIBF]] = 2</code>''<br/><br />
'''<code>[[ESLM]]</code>''' - horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 0</code>, <code>1</code>, or <code>2</code>''<br/><br />
'''<code>[[ESLM]]</code> <code>[[ESLC]]</code>''' - alternate horizontal eddy viscosity controls, ''<span style="background:blanchedalmond">include this line only if:</span>'' <code>[[IM]] = 10</code>''<br/><br />
'''<code>[[CORI]]</code>''' - constant Coriolis coefficient, ''<span style="background:mistyRose">only used if</span>'' <code>NCOR=0</code><br />
<br />
===Periodic (Tidal) Body Forcing===<br />
[[NTIF]]<br/><br />
for k=1 to [[NTIF]]<br />
: [[TIPOTAG(k)]]<br />
: [[TPK(k)]], [[AMIGT(k)]], [[ETRF(k)]], [[FFT(k)]], [[FACET(k)]]<br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Elevations===<br />
[[NBFR]]<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[BOUNTAG(k)]]<br/><br />
: [[AMIG(k)]], [[FF(k)]], [[FACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NBFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NETA]]<br/><br />
:: [[EMO(k,j), EFA(k,j)]]<br/><br />
: end j loop<br/><br />
end k loop<br />
<br />
===Periodic (Tidal) Boundary Velocities===<br />
[[ANGINN]]<br/><br />
[[NFFR]] - include this line only if [[IBTYPE]] = 2, 12, 22, 32 or 52 in the Grid and Boundary Information File<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[FBOUNTAG(k)]]<br/><br />
: [[FAMIGT(k),FFF(k),FFACE(k)]]<br/><br />
end k loop<br/><br />
for k=1 to [[NFFR]]<br/><br />
: [[ALPHA(k)]]<br/><br />
: for j=1 to [[NVEL]]<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]] - use this line if [[IBTYPE]] = 2, 12, 22 in the Grid and Boundary Information File<br/><br />
:: [[QNAM(k,j), QNPH(k,j)]], [[ENAM(k,j), ENPH(k,j)]] - use this line if [[IBTYPE]] = 32 in the Grid and Boundary Information File<br/><br />
:end j loop<br/><br />
end k loop<br />
<br />
===Model Output===<br />
[[NOUTE]], [[TOUTSE]], [[TOUTFE]], [[NSPOOLE]]<br/><br />
[[NSTAE]]<br/><br />
for k=1 to [[NSTAE]]<br/><br />
: [[XEL(k), YEL(k)]] - use these lines if [[NSTAE]] is positive. If negative, stations are listed in the [[elev_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTV]], [[TOUTSV]], [[TOUTFV]], [[NSPOOLV]]<br/><br />
[[NSTAV]]<br/><br />
for k=1 to [[NSTAV]]<br/><br />
: [[XEV(k), YEV(k)]] - use these lines if [[NSTAV]] is positive. If negative, stations are listed in the [[vel_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTC]], [[TOUTSC]], [[TOUTFC]], [[NSPOOLC]] - include this line only if IM =10<br/><br />
[[NSTAC]] - include this line only if IM =10<br/><br />
for k=1 to [[NSTAC]]<br/><br />
: [[XEC(k), YEC(k)]]<br/><br />
end k loop<br/><br />
[[NOUTM]], [[TOUTSM]], [[TOUTFM]], [[NSPOOLM]] - include this line only if NWS is not equal to zero.<br/><br />
[[NSTAM]] - include this line only if NWS is not equal to zero.<br/><br />
for k=1 to [[NSTAM]]<br/><br />
: [[XEM(k), YEM(k)]] - use these lines if [[NSTAM]] is positive. If negative, stations are listed in the [[met_stat.151]] file<br/><br />
end k loop<br/><br />
[[NOUTGE]], [[TOUTSGE]], [[TOUTFGE]], [[NSPOOLGE]]<br/><br />
[[NOUTGV]], [[TOUTSGV]], [[TOUTFGV]], [[NSPOOLGV]]<br/><br />
[[NOUTGC]], [[TOUTSGC]], [[TOUTFGC]], [[NSPOOLGC]] - include this line only if IM =10<br/><br />
[[NOUTGW]], [[TOUTSGW]], [[TOUTFGW]], [[NSPOOLGW]] - include this line only if NWS is not equal to zero.<br />
<br />
====Harmonic Analysis====<br />
[[NFREQ]]<br/><br />
for k=1 to [[NFREQ]]<br/><br />
: [[NAMEFR(k)]]<br/><br />
: [[HAFREQ(k), HAFF(k), HAFACE(k)]]<br/><br />
end k loop<br/><br />
[[THAS]], [[THAF]], [[NHAINC]], [[FMV]]<br/><br />
[[NHASE]], [[NHASV]], [[NHAGE]], [[NHAGV]]<br />
<br />
====Hotstart Output and Numeric Controls====<br />
[[NHSTAR]], [[NHSINC]]<br/><br />
[[ITITER]], [[ISLDIA]], [[CONVCR]], [[ITMAX]]<br/><br />
<br />
''For a 2DDI ADCIRC run that does not use netCDF nor namelists, the file ends here. For those controls, see further below in the [[#NetCDF Controls|NetCDF Controls]] and [[#Namelists|Namelists]] sections.''<br />
<br />
==3D Model Run==<br />
[[IDEN]]<br/><br />
[[ISLIP]], [[KP]]<br/><br />
[[Z0S,Z0B]]<br/><br />
[[ALP1,ALP2,ALP3]]<br/><br />
[[IGC]], [[NFEN]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IGC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[SIGMA(k)]]<br/><br />
end k loop<br/><br />
[[IEVC]], [[EVMIN]], [[EVCON]]<br/><br />
for k=1 to [[NFEN]] (include this loop only if [[IEVC]] = 0, k=1 at bottom, k= [[NFEN]] at surface)<br/><br />
: [[EVTOT(k)]]<br/><br />
end k loop<br/><br />
[[THETA1, THETA2]](include this line only if [[IEVC]] = 50 or 51)<br/><br />
[[I3DSD,TO3DSDS,TO3DSDF,NSPO3DSD]]<br/><br />
[[NSTA3DD]]<br/><br />
for k=1 to [[NSTA3DD]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DSV,TO3DSVS,TO3DSVF,NSPO3DSV]]<br/><br />
[[NSTA3DV]]<br/><br />
for k=1 to [[NSTA3DV]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DST,TO3DSTS,TO3DSTF,NSPO3DST]]<br/><br />
[[NSTA3DT]]<br/><br />
for k=1 to [[NSTA3DT]]<br/><br />
: [[X3DS(k), Y3DS(k)]]<br/><br />
end k loop<br/><br />
[[I3DGD]],[[TO3DGDS]],[[TO3DGDF]],[[NSPO3DGD]]<br/><br />
[[I3DGV]],[[TO3DGVS]],[[TO3DGVF]],[[NSPO3DGV]]<br/><br />
[[I3DGT]],[[TO3DGTS]],[[TO3DGTF]],[[NSPO3DGT]]<br/><br />
The following line will be read in if [[IM]] is 21 or 31.<br/><br />
[[RES_BC_FLAG]], [[BCFLAG_LNM]], [[BCFLAG_TEMP]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] is negative.<br/><br />
[[RBCTIMEINC]]<br/><br />
[[BCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 2.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3.<br/><br />
[[RBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 4.<br/><br />
[[RBCTIMEINC]], [[SBCTIMEINC]], [[TBCTIMEINC]]<br/><br />
[[BCSTATIM]], [[SBCSTATIM]], [[TBCSTATIM]]<br/><br />
The following two lines will be read in if [[RES_BC_FLAG]] = 3 or 4 and [[BCFLAG_TEMP]] is not equal to 0.<br/><br />
[[TTBCTIMEINC]], [[TTBCSTATIM]]<br/><br />
[[TTBCTIMEINC]]<br/><br />
The following two lines will be read in only if [[IM]] is 21 or 31.<br/><br />
[[SPONGEDIST]]<br/><br />
[[EQNSTATE]]<br/><br />
The following lines will be read in only if [[IDEN]] is > 0.<br/><br />
[[NLSD, NVSD]]<br/><br />
[[NLTD, NVTD]]<br/><br />
[[ALP4]]<br/><br />
The following line will be read in only if [[IDEN]] = 3 or 4.<br/><br />
[[NTF]]<br />
<br />
==NetCDF Controls==<br />
The following lines will be read in only if the NetCDF output or hotstart format is chosen<br/><br />
NCPROJ<br/><br />
NCINST<br/><br />
NCSOUR<br/><br />
NCHIST<br/><br />
NCREF<br/><br />
NCCOM<br/><br />
NCHOST<br/><br />
NCCONV<br/><br />
NCCONT<br/><br />
NCDATE<br />
<br />
==Namelists==<br />
The following Fortran namelist lines are optional, but if they appear, they must appear at the very end of the fort.15 file.<br/><br />
<code>&metControl WindDragLimit=floatValue, DragLawString='stringValue', rhoAir=floatValue, outputWindDrag=logicalValue /</code><br/><br />
<code>&timeBathyControl NDDT=integerValue, BTIMINC=floatValue, BCHGTIMINC=floatValue /</code><br/><br />
<code>&waveCoupling WindWaveMultiplier=floatValue /</code><br/><br />
<code>&SWANOutputControl SWAN_OutputHS=logicalValue, SWAN_OutputDIR=logicalValue, SWAN_OutputTM01=logicalValue, SWAN_OutputTPS=logicalValue, SWAN_OutputWIND=logicalValue, SWAN_OutputTM02=logicalValue, SWAN_OutputTMM10=logicalValue /</code><br/><br />
<code>&subdomainModeling subdomainOn=logicalValue/</code><br/><br />
<code>&wetDryControl outputNodeCode=logicalValue, outputNOFF=logicalValue, noffActive=logicalValue /</code><br/><br />
<code>&inundationOutputControl inundationOutput=logicalValue0, inunThresh =floatValue /</code><br/><br />
<code>&TVWControl use_TVW=logicalValue, TVW_file='stringValue', nout_TVW =integerValue, touts_TVW =floatValue, toutf_TVW=floatValue, nspool_TVW =integerValue /</code><br/><br />
<code>&WarnElevControl WarnElev=floatValue, ErrorElev=floatValue, WarnElevDump=logicalValue, WarnElevDumpLimit=integerValue /</code><br/><br />
<code>[[Dynamic_water_level_correction#Controlling_Water_Level_Correction|&dynamicWaterLevelCorrectionControl]] dynamicWaterLevelCorrectionFileName='stringValue' dynamicWaterLevelCorrectionMultiplier=floatValue, dynamicWaterLevelCorrectionRampStart=floatValue, dynamicWaterLevelCorrectionRampEnd=floatValue, dynamicWaterLevelCorrectionRampReferenceTime='stringValue', dynamicWaterLevelCorrectionSkipSnaps=integerValue /</code><br/><br />
<code>&[[AliDispersionControl]] CAliDisp=logicalValue, Cs=floatValue, Ad=floatValue, Bd=floatValue /</code><br/><br />
[[category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file&diff=1104Fort.15 file2022-06-23T19:13:21Z<p>Taylorgasher: /* Ramping Meteorological Forcing at Hot-Start */</p>
<hr />
<div>This file contains the majority of the parameters required to run both the 2DDI and 3D versions of ADCIRC and the information to drive the model with harmonic boundary conditions (either elevation or flux). This file is required to run the ADCIRC model.<br />
<br />
== File Format ==<br />
See [[fort.15 file format]] for details.<br />
<br />
== Tips and Tricks ==<br />
=== Meteorological-Only Mode ===<br />
By turning off all ocean state-related outputting and disabling wave coupling, ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set <code>DT</code> equal to the time interval you wish met. data to be output, and then set the <code>[[NSPOOLM]]</code> and/or <code>[[NSPOOLGW]]</code> (the local and global met. output intervals) to <code>1</code> (i.e. output every time step). For typical 2D ADCIRC runs, this requires setting the following in the fort.15 file: <br/><br />
<code>[[NOUTE]] = 0</code> <br/><br />
<code>[[NOUTV]] = 0</code> <br/><br />
<code>[[NOUTGE]] = 0</code> <br/><br />
<code>[[NOUTGV]] = 0</code> <br/><br />
<code>[[NHSTAR]] = 0</code> <br/><br />
<code>[[NHASE]] = 0</code> <br/><br />
<code>[[NHASV]] = 0</code> <br/><br />
<code>[[NHAGE]] = 0</code> <br/><br />
<code>[[NHAGV]] = 0</code> <br/><br />
<br />
For passive scalar transport (<code>[[IM]] = 10</code>), also set: <br/><br />
<code>[[NOUTC]] = 0</code> <br/><br />
<code>[[NOUTGC]] = 0</code> <br/><br />
<br />
while for barotropic or baroclinic 3D ADCIRC, also set: <br/><br />
<code>[[I3DSD]] = 0</code> <br/><br />
<code>[[I3DSV]] = 0</code> <br/><br />
<code>[[I3DST]] = 0</code> <br/><br />
<code>[[I3DGD]] = 0</code> <br/><br />
<code>[[I3DGV]] = 0</code> <br/><br />
<code>[[I3DGT]] = 0</code> <br/><br />
<br />
=== Ramping Meteorological Forcing at Hot-Start ===<br />
It is generally best to [[ramping]] in forcing terms to the model to avoid shocking the system, but ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Since it is common-place to initialize meteorological forcing at hotstart time, there is a special parameter to facilitate hotstart ramping of met. data. Let's say you run a 15-day tide-only run and output a hotstart file. Setting <br/><br />
<code>[[NRAMP]] = 8</code><br/><br />
means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/><br />
<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP, DRAMPExtFlux, FluxSettlingTime, DRAMPIntFlux, DRAMPElev, DRAMPTip, DRAMPMete, DRAMPWRad, DRAMPUnMete</code><br/><br />
What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).<br />
<br />
<br />
[[Category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Global_Storm_Tide_-_Hurricane_Katrina&diff=1103Global Storm Tide - Hurricane Katrina2022-06-23T19:01:12Z<p>Taylorgasher: added test cases category</p>
<hr />
<div>This example tests ADCIRC version 55 (and beyond). It tests the simulation of the storm tides on the spherical Earth under astronomical and atmospheric forcing during August 2005 when Hurricane Katrina impacted the Gulf of Mexico. The results of interest are the global elevations, velocities and meteorology. The test finishes in about 5 minutes in serial ADCIRC for a full month of simulation. Find the test at the [https://github.com/adcirc/adcirc-cg-testsuite/tree/v55/adcirc/adcirc_global-tide%2Bsurge-2d GitHub test suite].<br />
<br />
== Mesh == <br />
The mesh is a coarse representation of the spherical Earth with minimum resolution of approximately 50 km, comprised of 27,330 vertices and 50,859 triangular elements. <br />
<br />
== Options/Features Tested ==<br />
*<code>[[ICS]]</code> = -22: Uses the Mercator projection with a coordinate rotation to remove the pole singularity (need to provide a [[fort.rotm]]). <br />
*<code>[[IM]]</code> = 513113: Uses the fully implicit scheme for the gravity wave term (computational time step is 12 minutes). <br />
*<code>[[NTIP]]</code> = 2: Equilibrium tide + self-attraction and loading tide (read from a [[fort.24 file]]) forcing for 10 tidal constituents.<br />
*<code>[[NWS]]</code> = -14: Reads from GRIB2 files that specify the global atmospheric forcing (6-hourly CFS reanalysis data) in addition to OWI ASCII files that specify the 3-hourly atmospheric forcing in the Hurricane Katrina landfall region. <br />
*<code>[[WTIMINC]]</code> = 21600, 10800: First value gives the temporal interval of the GRIB2 met data (6 hours), second value gives the temporal interval of the OWI met data (3 hours) in seconds.<br />
*<code>[[A00, B00, C00]]</code> = 0.5, 0.5, 0: Ensures that the fully implicit scheme is stable with a large time step.<br />
*<code>[[ESLM]]</code> = -0.2: Enables the Smagorinsky turbulence closure with a coefficient of 0.2.<br />
*<code>[[NOUTGE]]</code> = 5: Outputs the global elevations into a netCDF4 [[fort.63 file]]. <br />
*<code>[[NOUTGV]]</code> = 5: Outputs the global velocities into a netCDF4 [[fort.64 file]]. <br />
*<code>[[NOUTGM]]</code> = 5: Outputs the global meteorology into a netCDF4 [[fort.73 file]] (pressure) and a netCDF4 [[fort.74 file]] (velocity). <br />
*[[fort.13_file#Internal_Tide_Energy_Conversion|internal_tide_friction]]: Spatially varying linear wave drag [[fort.13 file]] attribute accounting for energy conversion due to internal tide generation in the deep ocean.<br />
*[[fort.13_file#Quadratic_Friction_coefficient|quadratic_friction_coefficient]]: Spatially varying quadratic bottom friction [[fort.13 file]] attribute.<br />
<br />
[[Category:test cases]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.22_file&diff=1101Fort.22 file2021-11-30T14:43:30Z<p>Taylorgasher: Added NWS = 30 info</p>
<hr />
<div>A single meteorological input file (wind velocity and atmospheric pressure) is read when meteorological forcing has been indicated by the <code>[[NWS]]</code> parameter in the [[fort.15 file]]. More precisely, the format of and need for the fort.22 file depend on the ones and tens (i.e. the last 2) digits and the sign (positive/negative) of <code>NWS</code> (see [[NWS#Value_Seen_in_fort.15_File|here]]). See also the [[supplemental meteorological/wave/ice parameters]] and [[wind stress]] pages. <br />
<br />
== General Notes ==<br />
Unless otherwise specified for a given format, ADCIRC expects wind data to represent [[Wind_Stress#Definition_of_Winds|specific conditions]] and pressure data to be sea level pressure. Where necessary, ADCIRC assumes a "background" atmospheric pressure of 1013 millibars. <br />
<br />
Meteorological data in most formats must be provided for the entire model run, otherwise the run will crash. Exceptions include OWI (<code>NWS=12</code>) and GFDL (<code>NWS=16</code>).<br />
<br />
For most formats, latitude and longitude coordinates describing the spatial extents of the meteorological data must follow the convention of the ADCIRC model domain. For example, if the [[fort.14 file|mesh]] uses negative longitude values to indicate locations West 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 at 180 deg longitude. Therefore, the meteorological and ADCIRC grids should use negative longitudes West of the Greenwich Meridian and positive longitudes to the East.<br />
<br />
== File Format ==<br />
The remainder of this page is devoted to the formats of the fort.22 file for the different values of <code>NWS</code>. 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. <br />
<br />
==NWS = 1 Wind Stress & Pressure at All Nodes and Timesteps==<br />
<br />
===File Structure===<br />
<br />
for k=1,[[NP]]<br />
<br />
: [[JN]], [[WSX(k), WSY(k)]], [[PRN(k,j)]]<br />
<br />
end k loop<br />
<br />
===Notes===<br />
<br />
Meteorological data is input directly to all nodes in the ADCIRC grid.<br />
<br />
The units for pressure are meters of water.<br />
<br />
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>.<br />
<br />
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.<br />
<br />
==NWS = ±2 Wind Stress & Pressure at All Nodes and Specified Time Interval==<br />
<br />
===File Structure===<br />
for k=1, NP<br />
<br />
: [[JN]], [[WSX(k), WSY(k)]], [[PRN(k,j)]]<br />
<br />
end k loop<br />
<br />
===Notes===<br />
<br />
Meteorological data is input directly to all nodes in the ADCIRC grid.<br />
<br />
The units for pressure are meters of H2O.<br />
<br />
If <code>[[NWS]]=2</code>, the first set of met. data corresponds to <code>TIME=[[STATIM]]</code>. If <code>NWS=-2</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.<br />
<br />
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, <br />
<br />
<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><br />
<br />
==NWS = 3 Fleet Numeric Format==<br />
<br />
===File Structure===<br />
<br />
[[IWTIME]]<br />
<br />
for k = 1,[[NWLAT]]<br />
<br />
: for j = 1,[[NWLON]]<br />
<br />
:: [[WSPEED(k,j)]]<br />
<br />
: end j loop<br />
<br />
end k loop<br />
<br />
for k = 1, NWLAT<br />
<br />
: for j = 1, NWLON<br />
<br />
:: [[WDIR(k,j)]]<br />
<br />
: end j loop<br />
<br />
end k loop<br />
<br />
<br />
===Notes===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Wind velocity (@ 10 m above the water surface) must be input in units of m/s (regardless of the units of gravity).<br />
<br />
The following relations are used to compute wind stress from the input wind velocity.<br />
<br />
<code>WIND_SPEED = magnitude of WIND_VEL</code><br />
<br />
<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code><br />
<br />
<code>If (DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code><br />
<br />
<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code><br />
<br />
==NWS = ±4 PBL Hurricane Model format==<br />
<br />
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.<br />
<br />
===File Structure===<br />
<br />
FOR EACH WIND TIME INCREMENT<br />
<br />
: DO UNTIL LINE = ” #”<br />
<br />
:: [[JN]], [[WVNX(JN), WVNY(JN)]], [[PRN(k,j)]]<br />
<br />
: END DO UNTIL<br />
<br />
END FOR EACH<br />
<br />
===Notes===<br />
<br />
If <code>[[NWS]] = 4</code>, the first set of met. data corresponds to <code>TIME=[[STATIM]]</code>. If <code>[[NWS]] = -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.<br />
<br />
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<br />
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.<br />
<br />
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.<br />
<br />
The following relations are used to compute wind stress from wind velocity:<br />
<br />
<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).<br />
<br />
<code>WIND_SPEED = magnitude of WIND_VEL</code><br />
<br />
<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code><br />
<br />
<code>if(DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code><br />
<br />
<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code><br />
<br />
The following relationship is used in ADCIRC to convert to pressure in meters of water from pressure in hundredths of a millibar:<br />
<br />
<code>PRESSURE{m H2O}=PRESSURE{Pa/100}*100/(GRAVITY*DENSITY H2O)</code><br />
<br />
==NWS = ±5 Wind Velocity & Pressure at All Nodes and Specified Time Interval==<br />
<br />
===File Structure===<br />
<br />
for k = 1, NP<br />
<br />
: [[JN]], [[WVX(k), WVY(k)]], [[PRN(k,j)]]<br />
<br />
end k loop<br />
<br />
===Notes===<br />
<br />
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.<br />
<br />
If <code>[[NWS]]=5</code>, the first set of met. data corresponds to <code>TIME=[[STATIM]]</code>. If <code>[[NWS]]=-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.<br />
<br />
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.<br />
<br />
The following relations are used to compute wind stress from wind velocity:<br />
<br />
<code>WIND_SPEED = magnitude of WIND_VEL</code><br />
<br />
<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code><br />
<br />
<code>if(DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code><br />
<br />
<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code><br />
<br />
==NWS = 6 Wind Velocity and Pressure on Rectangular Grid==<br />
<br />
===File Structure===<br />
<br />
for k=1, NWLAT<br />
<br />
: for j=1, NWLON<br />
<br />
:: [[WVXFN(k,j), WVYFN(k,j)]], [[PRN(k,j)]]<br />
<br />
: end j loop<br />
<br />
end k loop<br />
<br />
===Notes===<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
The following relations are used to compute wind stress from the input wind velocity.<br />
<br />
<code>WIND_SPEED = magnitude of WIND_VEL</code><br />
<br />
<code>DRAG_COEFF = 0.001*(0.75+0.067*WIND_SPEED)</code><br />
<br />
<code>If (DRAG_COEFF.gt.0.003) DRAG_COEFF=0.003</code><br />
<br />
<code>WIND_STRESS = DRAG_COEFF*0.001293*WIND_VEL*WIND_SPEED</code><br />
<br />
The following relationship is used in ADCIRC to convert to pressure in meters of water from pressure in Pascal:<br />
<br />
<code>PRESSURE{m H2O}=PRESSURE{Pascal}/(GRAVITY*DENSITY H2O)</code><br />
<br />
==NWS = ±7 Wind Stress and Pressure on Rectangular Grid==<br />
'''This format has not been fully implemented, though it is expected in v55.'''{{ADC version|version=?55?|relation=ge}}<br />
<br />
===File Structure===<br />
for k=1, NWLAT<br />
<br />
: for j=1, NWLON<br />
<br />
:: WVXFN(K,J),WVYFN(K,J),PRN(K,J)<br />
<br />
: END DO<br />
<br />
END DO<br />
<br />
=== Notes ===<br />
<br />
==NWS = 8 Dynamic Symmetric Holland Vortex Model==<br />
<br />
===File Structure===<br />
Use the [https://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html ATCF Best Track/Objective Aid/Wind Radii Format].<br />
<br />
===Notes===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
==NWS = 9 Asymmetric Holland Vortex Model==<br />
'''This has been deprecated and is no longer available.''' {{ADC version|version=???|relation=lt}}<br />
<br />
==NWS = 10 National Climatic Data Center GFS==<br />
<span style="color:red">It appears there is no fort.22 file for this format, and users should consult the </span>[[fort.200]]<span style="color:red"> page, but this hasn't been confirmed. </span><br />
<br />
Wind velocity 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.<br />
<br />
===File Structure===<br />
<br />
for k=1, [[LONB*LATB]]<br />
<br />
: [[PG(k)]], [[UG(k)]], [[VG(k)]]<br />
<br />
end j loop<br />
<br />
==NWS = 11 Stripped National Weather Service (NWS) ETA 29km==<br />
<span style="color:red">It appears there is no fort.22 file for this format, and users should consult the </span>[[fort.200]]<span style="color:red"> page, but this hasn't been confirmed. </span><br />
<br />
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. <br />
<br />
===File Structure===<br />
<br />
for k=1, LONB*LATB<br />
<br />
: PG(k), UG(k), VG(k)<br />
<br />
end j loop<br />
<br />
==NWS = ±12 Oceanweather ASCII Format Gridded Wind and Pressure==<br />
<br />
Oceanweather Inc (OWI) ASCII "WIN"/"PRE" format , details can be found at [[NWS12]] <br />
<br />
==NWS = 13 Oceanweather NetCDF Format Gridded Wind and Pressure==<br />
<br />
Oceanweather Inc (OWI) NetCDF format , details can be found at [[NWS13]] {{ADC version|version=55|relation=ge}}<br />
<br />
==NWS = ±14 Gridded GRIB2 or NetCDF Wind and Pressure==<br />
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}}<br />
<br />
===File Structure===<br />
Temporal dimension name<br /><br />
Datetime variable name<br /> <br />
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]<br /><br />
Zonal (east-west) dimension name<br /><br />
Longitude variable name<br /><br />
Meridional (north-south) dimension name<br /><br />
Latitude variable name<br /><br />
Sea-level Pressure variable name<br /><br />
Zonal 10-m Wind Velocity name<br /><br />
Meridional 10-m Wind Velocity name<br /><br />
Ice area-fraction name [optional, only if fort.225.nc present for ice area fraction]<br />
<br />
===Example (WRF output)===<br />
Time<br /><br />
Times [if no datetime variable then set to dummy such as 'none']<br /><br />
%Y-%m-%d_%H:%M:%S [if no datetime variable then set to dummy such as 'none']<br /><br />
west_east<br /><br />
XLONG<br /><br />
south_north<br /><br />
XLAT<br /><br />
PSFC<br /><br />
U10<br /><br />
V10<br /><br />
aice [optional]<br /><br />
<br />
===Notes===<br />
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]].<br />
<br />
==NWS = 15 H*Wind Gridded Wind and Inferred Pressure==<br />
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. <br />
<br />
===File Structure===<br />
<br />
comment line<br />
<br />
[[hWindMultiplier]]<br />
<br />
[[presssureWindRelationship]]<br />
<br />
for i=1 to numHWindFiles<br />
<br />
: [[hours(i)]] [[centralPressure(i)]] [[rampMult(i)]] [[filename(i)]]<br />
<br />
end i loop<br />
<br />
===Notes===<br />
HWind files are data assimilated snapshots of the wind velocity fields of tropical cyclones that were produced by the NOAA Hurricane Research Division (HRD) through 2013, before becoming a private sector data product. The files have the following characteristics:<br />
<br />
<code>the format explicitly indicates the center of the storm</code><br />
<br />
<code>the (u,v) data are on a regular grid</code><br />
<br />
<code>the regular grid is a mercator projection with origin at storm center</code><br />
<br />
<code>the mercator grid spacing is in meters and is uniform in x and y (dx=dy)</code><br />
<br />
<code>the dimensions (nx,ny) of the mercator grid are equal (nx=ny)</code><br />
<br />
<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><br />
<br />
<code>sequential hwind snapshots will not be evenly spaced in time for a particular storm</code><br />
<br />
H*Wind data do not contain barometric pressure information. For the dvorak, knaffzehr, and specified Pc 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.<br />
<br />
To illustrate the definitions and descriptions provided, a concrete example of an HWind fort.22 file is provided as follows:<br />
<br />
<code>! first line is a comment line, max length 1024 characters</code><br />
<br />
<code>1.0 ! 2nd line is a velocity magnitude multiplier</code><br />
<br />
<code>dvorak ! 3rd line: one word for the pressure-wind relationship</code><br />
<br />
<code>0.0 -1 0.0 “/home/jason/hwind/al092011_0828_1330” ! time (hours), Pc (mb), ramp mult, filename</code><br />
<br />
<code>6.0 -1 0.5 “/home/jason/hwind/al092011_0828_1930”</code><br />
<br />
<code>12.0 -1 1.0 “/home/jason/hwind/al092011_0829_0130”</code><br />
<br />
==NWS = 16 ASCII NOAA GFDL Gridded Wind And Pressure==<br />
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. <br />
<br />
===File Structure===<br />
<br />
comment line<br />
<br />
[[GFDLWindMultplier]]<br />
<br />
[[MaxExtrapolationDistance]]<br />
<br />
for i=1 to numGFDLFiles<br />
<br />
: [[hours(i)]] [[rampMult(i)]] [[filename(i)]]<br />
<br />
end i loop<br />
<br />
===Notes===<br />
<br />
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:<br />
<br />
<code>Line 1: Number of grid cells (f10.4) NCELLS</code><br />
<br />
<code>Lines 2 through NCELLS+1: Ten columns of data formatted as 10f10.4 as follows:</code><br />
<br />
<code>column 1: u (m/s)</code><br />
<br />
<code>column 2: v (m/s)</code><br />
<br />
<code>column 3: Temperature (K)</code><br />
<br />
<code>column 4: mixing ratio(kg/kg)</code><br />
<br />
<code>column 5: storm accum precipitation (cm)</code><br />
<br />
<code>column 6: sea level pressure (hPa)</code><br />
<br />
<code>column 7: longitude (decimal deg)</code><br />
<br />
<code>column 8: latitude (decimal deg)</code><br />
<br />
<code>column 9: hurricane hour</code><br />
<br />
<code>column 10: nest number (this is not always present)</code><br />
<br />
<br />
To illustrate the definitions and descriptions provided, a concrete example of a GFDL fort.22 file is provided as follows:<br />
<br />
<code>! first line is a comment line, max length 1024 characters</code><br />
<br />
<code>1.0 ! 2nd line is a velocity magnitude multiplier</code><br />
<br />
<code>100.0 ! 3rd line: maximum extrapolation distance (m)</code><br />
<br />
<code>0.0 -1 0.0 “/home/jason/hwind/al092011_0828_1330″ ! time (hours), Pc (mb), ramp mult, filename</code><br />
<br />
<code>6.0 -1 0.5 “/home/jason/hwind/al092011_0828_1930″</code><br />
<br />
<br />
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.<br />
<br />
==NWS = 19 Dynamic Asymmetric Holland Vortex Model==<br />
'''Note that use of this [[Typical_ADCIRC_Parameter_Selections#Discouraged_Parameter_Selections|is discouraged]].''' <br />
<br />
===File Structure===<br />
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].<br />
<br />
===Notes===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
The <code>NWS=19</code> option requires the following variables in the fort.22 file in a best track format:<br />
<br />
<code>Forecast time in hours (column 6); enter the time in hours in each record starting at 0</code><br />
<br />
<code>Latitude of the eye (column 7)</code><br />
<br />
<code>Longitude of the eye (column 8)</code><br />
<br />
<code>Maximum sustained wind speed in knots (column 9)</code><br />
<br />
<code>Minimum sea level pressure in MB (column 10)</code><br />
<br />
<code>Wind intensity in knots of the radii defined in the record (34, 50, 64 or 100 knots) (column 12)</code><br />
<br />
<code>Radius of specified wind intensity for quadrants 1, 2, 3, 4 in NM (columns 14, 15, 16, 17); ? 0</code><br />
<br />
<code>Background pressure in MB (column 18); a standard value of 1013 can be used</code><br />
<br />
<code>Rmax as reported in the ATCF BEST TRACK file in column 20</code><br />
<br />
<code>Storm Name in Column 28 ATCF file format</code><br />
<br />
<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><br />
<br />
<code>number of isotachs reported in the ATCF file for the corresponding Time record.</code><br />
<br />
<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><br />
<br />
<code>Columns 35-38 are the designated Rmax values computed for each of the quadrants selected for each particular isotach.</code><br />
<br />
<code>Column 39 is the Holland B parameter computed using the formulas outlines in the Holland paper, and implemented using the aswip program.</code><br />
<br />
Available files:<br />
<br />
* [ftp://ftp.nhc.noaa.gov/atcf/archive/ Historical storm files] <br />
<br />
* [ftp://ftp.nhc.noaa.gov/atcf/btk/ Forecast tracks]<br />
<br />
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.<br />
<br />
<code>The command line for NWS=19 is ./aswip -n 19 -m 2 -z 1</code><br />
<br />
==NWS = 20 Generalized Asymmetric Holland Vortex Model (GAHM)==<br />
<br />
===File Structure===<br />
The file needs is similar to the NWS = 19 format with 8 additional columns of data, see notes below for more information.<br />
<br />
===Notes===<br />
<br />
The Generalized Asymmetric Holland Model (GAHM) provides a set of theoretical and practical improvements over previous parametric meteorological vortex models in ADCIRC. <br />
<br />
<code>Forecast time in hours (column 6); enter the time in hours in each record starting at 0</code><br />
<br />
<code>Latitude of the eye (column 7)</code><br />
<br />
<code>Longitude of the eye (column 8)</code><br />
<br />
<code>Maximum sustained wind speed in knots (column 9)</code><br />
<br />
<code>Minimum sea level pressure in MB (column 10)</code><br />
<br />
<code>Wind intensity in knots of the radii defined in the record (34, 50, 64 or 100 knots) (column 12)</code><br />
<br />
<code>Radius of specified wind intensity for quadrants 1, 2, 3, 4 in NM (columns 14, 15, 16, 17); ? 0</code><br />
<br />
<code>Background pressure in MB (column 18); a standard value of 1013 can be used</code><br />
<br />
<code>Rmax as reported in the ATCF BEST TRACK file in column 20</code><br />
<br />
<code>Storm Name in Column 28 ATCF file format</code><br />
<br />
<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><br />
<br />
<code>number of isotachs reported in the ATCF file for the corresponding Time record.</code><br />
<br />
<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><br />
<br />
<code>Columns 35-38 are the designated Rmax values computed for each of the quadrants selected for each particular isotach.</code><br />
<br />
<code>Column 39 is the Holland B parameter computed using the formulas outlines in the Holland paper, and implemented using the aswip program.</code><br />
<br />
<code>Column 40-43 is the quadrant-varying Holland B parameter</code><br />
<br />
<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><br />
<br />
Historical storm files can be found archived here.<br />
<br />
Forecast tracks can be found here.<br />
<br />
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.<br />
<br />
Options for the aswip program using NWS = 20 are the following:<br />
<br />
<code>./aswip -n # -m # -z #</code><br />
<br />
;-n = nws option<br />
<br />
;-m = methods of selecting isotachs for use in computation of radius/radii to maximum winds<br />
<br />
:1: always use the 34kt isotach</code><br />
<br />
:2: use the highest available isotach in any quadrant each time<br />
<br />
:3: use the 50kt isotach if it is available; otherwise use the 34kt isotach<br />
<br />
:4: use all available isotachs (must choose this for GAHM/NWS=20)<br />
<br />
;-z = approaches solving for Rmax <br />
<br />
:1 = only rotate wind vectors afterward <br />
<br />
:2 = rotate wind vectors before and afterwards (use this for NWS=20)<br />
<br />
So the command line for <code>NWS=20</code> is: <code>./aswip -n 20 -m 4 -z 2</code><br />
<br />
==NWS = 30 Blended GAHM & Background Gridded Wind and Pressure==<br />
This format is a combination of GAHM (<code>NWS=12</code>) and a gridded background meteorological field (<code>NWS=20</code>). The core of a tropical cyclone is represented using the GAHM model and read in from a file named NWS_20_fort.22, which should be created following the procedure presented in the [[#NWS = 20 Generalized Asymmetric Holland Vortex Model (GAHM)|section on <code>NWS=20</code>]]. The user must also supply gridded wind and pressure files in the form of an OWI-style fort.22 file, a fort.221 file, and a fort.222 file, details on these are in the [[#NWS = ±12 Oceanweather ASCII Format Gridded Wind and Pressure|section on <code>NWS=12</code>]]. ADCIRC internally blends the wind and pressure fields from these two sets of inputs over a user-controlled distance. Specifically, the <code>[[pureVortex]]</code> and <code>[[pureBackground]]</code> inputs in the [[fort.15 file]] (for formatting, see info on the [[Supplemental meteorological/wave/ice parameters|meteorological parameter line]]) are coefficients used to define where transitions between the vortex and background meteorology occur. At or within the distance <code>pureVortex*vortexRMW</code> of the storm's center, the GAHM meteorology is used. At or beyond the distance <code>pureBackground*vortexRMW</code> of the storm's center, the background meteorology is used. In between these, a linear distance-weighted average of the two sets of meteorology is used to define the forcing. <br />
<br />
[[Category:input files]]<br />
[[Category:meteorology]]<br />
[[Category:unverified behavior]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Supplemental_meteorological/wave/ice_parameters&diff=1100Supplemental meteorological/wave/ice parameters2021-11-30T14:09:38Z<p>Taylorgasher: Reordered entries so they're in order</p>
<hr />
<div>This table is helpful for understanding file requirements and how the [[Fort.15_file_format#WTIMINC|meteorological parameter line]] (informally, the <code>[[WTIMINC]]</code> line) should look in the [[fort.15 file]]. These are principally determined by the value of the <code>[[NWS]]</code> line (also in the fort.15 file), though note that the "NWS" values below are for the [[NWS#Value_Seen_in_fort.15_File|full-length value]] in the fort.15 file. Useful information is also contained in the [[fort.22 file format]] and [[wind stress]] pages. <br />
<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Meteorological Data Format<br />
! [[#Forcing Abbreviations|Forcing]]<br />
! <code>[[NWS]]</code> Value<br />
! <code>[[WTIMINC]]</code> Line<br />
! [[#Requirements|Requirements]]<br />
! [[#Notes|Notes]]<br />
|-<br />
| '''none''' <br />
| nonexistent<br />
| 0<br />
| nonexistent<br />
| none<br />
| none<br />
|- style="background:#efefef;"<br />
| '''wind stress, every node, every timestep'''<br />
| m<br />
| 1<br />
| nonexistent<br />
| f22<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 101<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 301<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 401<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''wind stress, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 2<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|-<br />
|<br />
| m, rs <br />
| 102<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 302<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 402<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''US Navy Fleet Numeric'''<br />
| m<br />
| 3<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
|<br />
| m, rs<br />
| 103<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw <br />
| 303<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st<br />
| 403<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic<br />
| 12003<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
|<br />
| m, rs, ic<br />
| 12103<br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw, ic<br />
| 12303<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st, ic<br />
| 12403<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''PBL/JAG'''<br />
| m<br />
| 4<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
|<br />
| m, rs <br />
| 104<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 304<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, ic <br />
| 12004<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25 <br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12104 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw, ic<br />
| 12304 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st, ic<br />
| 12404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''wind velocity, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 5<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic <br />
| 12005 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''wind velocity, rectangular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 6<br />
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 106<br />
| <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><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 306<br />
| <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><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 406<br />
| <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><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic <br />
| 12006<br />
| <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><br />
| f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12106<br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12306 <br />
| <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><br />
| f22, A+S, f25 <br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st ,ic<br />
| 12406 <br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''wind stress, regular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 7<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, rs <br />
| 107<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 307<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, st <br />
| 407<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''symmetric vortex model'''<br />
| m<br />
| 8<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| f22<br />
| none<br />
|- <br />
| <br />
| m, rs<br />
| 108<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 308<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st<br />
| 408<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12008<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12108 <br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12308<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12408<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''asymmetric vortex model (no longer available)'''<br />
| n/a<br />
| 9<br />
| n/a<br />
| n/a<br />
| none<br />
|- <br />
| '''National Climatic Data Center GFS'''<br />
| m<br />
| 10<br />
| <code>WTIMINC</code><br />
| f2xx+<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 410<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12010 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12410 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f2xx+, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''National Weather Service ETA 29km'''<br />
| m<br />
| 11<br />
| nonexistent<br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 111<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 311<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 411<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m,ic <br />
| 12011<br />
| <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12111<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12311<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12411<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''Oceanweather Inc (OWI)'''<br />
| m<br />
| 12<br />
| <code>WTIMINC</code><br />
| f22x<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw<br />
| 312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12012<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22x, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;" <br />
| '''Oceanweather Inc (OWI) NetCDF'''<br />
| m<br />
| 13<br />
| <code>WTIMINC</code><br />
| f22nc<br />
| [[NWS13]]<br />
|- style="background:#efefef;" <br />
| <br />
| m, rs<br />
| 113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12013<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''H*Wind'''<br />
| m<br />
| 15<br />
| <code>WTIMINC</code><br />
| hwind+,f22<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw<br />
| 315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12015<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''Geophysical Fluid Dynamics Laboratory (GFDL) Model'''<br />
| m<br />
| 16<br />
| <code>WTIMINC</code><br />
| gfdl+,f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 316<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic <br />
| 12016<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12316 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| '''Dynamic Asymmetric Model''' <br />
| m<br />
| 19<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| pp,f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 119<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 319<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 419<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12019<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code> <br />
| pp, f22, f25<br />
| none<br />
|-<br />
| <br />
| m, rs, ic<br />
| 12119<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12319<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12419 <br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''Generalized Asymmetric Holland Model (GAHM)'''<br />
| m<br />
| 20<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code><br />
| pp, f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 120<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 320<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 420<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12020<br />
| <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><br />
| pp, f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12120<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12320<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12420<br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''Blended GAHM and OWI'''<br />
| m<br />
| 30<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 130<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw <br />
| 330<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 430<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic<br />
| 12030<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f25<br />
| none<br />
|- <br />
| <br />
| m, rs, ic<br />
| 12130<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12330<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12430<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
|}<br />
<br />
<br />
===Forcing Abbreviations===<br />
: '''m''' - meteorology<br />
: '''rs''' - Wave radiation stress in an analyst-supplied [[fort.23]] input file<br />
: '''sw''' - Wave coupling using a simultaneously executing coupled SWAN model<br />
: '''st''' - Wave coupling using a simultaneously executing ESMF coupled STWAVE model<br />
: '''ic''' - Ice coverage using an analyst-supplied ice coverage data files<br />
<br />
===Requirements===<br />
: '''f22''' - Requires analyst-supplied [[fort.22]] meteorological forcing file.<br />
: '''f2xx+''' - Requires at least two fort.2xx meteorological forcing files from the GFS model. See fort.22 documentation for file naming and formatting details.<br />
: '''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.<br />
: '''hwind+''' - Requires two or more meteorological forcing files from the H*Wind model. See fort.22 documentation for details.<br />
: '''gfdl+''' - Requires two or more meteorological forcing files from the GFDL model. See fort.22 documentation for details.<br />
: '''nwsf22''' - Requires analyst-supplied [[NWS_20_fort.22]] meteorological forcing file.<br />
: '''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.<br />
: '''f23''' - Requires analyst-supplied fort.23 wave radiation stress input file.<br />
: '''A+S''' - Requires ADCIRC+SWAN executable and input files for the coupled version of SWAN.<br />
: '''STW''' - Requires ESMF-coupled ADCIRC and STWAVE and input files for STWAVE.<br />
: '''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.<br />
<br />
===Notes===<br />
<references group="note" /></div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Supplemental_meteorological/wave/ice_parameters&diff=1099Supplemental meteorological/wave/ice parameters2021-11-30T13:59:26Z<p>Taylorgasher: Added NWS = 30 and variants, various formatting changes</p>
<hr />
<div>This table is helpful for understanding file requirements and how the [[Fort.15_file_format#WTIMINC|meteorological parameter line]] (informally, the <code>[[WTIMINC]]</code> line) should look in the [[fort.15 file]]. These are principally determined by the value of the <code>[[NWS]]</code> line (also in the fort.15 file), though note that the "NWS" values below are for the [[NWS#Value_Seen_in_fort.15_File|full-length value]] in the fort.15 file. Useful information is also contained in the [[fort.22 file format]] and [[wind stress]] pages. <br />
<br />
{| class="wikitable" border="1" style="text-align: center"<br />
|-<br />
! Meteorological Data Format<br />
! [[#Forcing Abbreviations|Forcing]]<br />
! <code>[[NWS]]</code> Value<br />
! <code>[[WTIMINC]]</code> Line<br />
! [[#Requirements|Requirements]]<br />
! [[#Notes|Notes]]<br />
|-<br />
| '''none''' <br />
| nonexistent<br />
| 0<br />
| nonexistent<br />
| none<br />
| none<br />
|- style="background:#efefef;"<br />
| '''wind stress, every node, every timestep'''<br />
| m<br />
| 1<br />
| nonexistent<br />
| f22<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 101<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 301<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <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><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 401<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''wind stress, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 2<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|-<br />
|<br />
| m, rs <br />
| 102<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 302<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 402<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| '''US Navy Fleet Numeric'''<br />
| m<br />
| 3<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
|<br />
| m, rs<br />
| 103<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw <br />
| 303<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st<br />
| 403<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, rs, ic<br />
| 12103<br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, sw, ic<br />
| 12303<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, st, ic<br />
| 12403<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic<br />
| 12003<br />
| <code>irefyr</code> <code>irefmo</code> <code>irefday</code> <code>irefhr</code> <code>irefmin</code> <code>refsec</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|-<br />
| '''PBL/JAG'''<br />
| m<br />
| 4<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
|<br />
| m, rs <br />
| 104<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw <br />
| 304<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st <br />
| 404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, rs, ic<br />
| 12104 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw, ic<br />
| 12304 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, st, ic<br />
| 12404<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
|<br />
| m, ic <br />
| 12004<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25 <br />
| none<br />
|- style="background:#efefef;"<br />
| '''wind velocity, every node, every <code>WTIMINC</code>'''<br />
| m<br />
| 5<br />
| <code>WTIMINC</code><br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12105<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12305<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12405<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
|<br />
| m, ic <br />
| 12005 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|-<br />
| '''wind velocity, rectangular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 6<br />
| <code><code>NWLON</code></code> NWLON <code>WLATMAX</code> <code>WLONMIN</code> <code>WLATINC</code> <code><code>WLONINC</code></code> <code>WTIMINC</code><br />
| f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 106<br />
| <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><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 306<br />
| <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><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 406<br />
| <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><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, rs, ic<br />
| 12106<br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12306 <br />
| <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><br />
| f22, A+S, f25 <br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st ,ic<br />
| 12406 <br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic <br />
| 12006<br />
| <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><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| '''wind stress, regular grid, every <code>WTIMINC</code>'''<br />
| m<br />
| 7<br />
| <code>WTIMINC</code><br />
| f22<br />
| <ref group="note" name="c"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, rs <br />
| 107<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 307<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;" <br />
| <br />
| m, st <br />
| 407<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| '''symmetric vortex model'''<br />
| m<br />
| 8<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| f22<br />
| none<br />
|- <br />
| <br />
| m, rs<br />
| 108<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 308<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st<br />
| 408<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, rs, ic<br />
| 12108 <br />
| <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><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12308<br />
| <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><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12408<br />
| <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><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12008<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| '''asymmetric vortex model (no longer available)'''<br />
| n/a<br />
| 9<br />
| n/a<br />
| n/a<br />
| none<br />
|- <br />
| '''National Climatic Data Center GFS'''<br />
| m<br />
| 10<br />
| <code>WTIMINC</code><br />
| f2xx+<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw<br />
| 310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 410<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f2xx+, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, rs, ic<br />
| 12110<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12310<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12410 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code> <br />
| f2xx+, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic <br />
| 12010 <br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f2xx+, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| '''National Weather Service ETA 29km'''<br />
| m<br />
| 11<br />
| nonexistent<br />
| f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 111<br />
| <code>RSTIMINC</code><br />
| f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 311<br />
| <code>RSTIMINC</code><br />
| f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 411<br />
| <code>RSTIMINC</code><br />
| f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12111<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12311<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12411<br />
| <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m,ic <br />
| 12011<br />
| <code>cice_timinc</code><br />
| f22, f25<br />
| none<br />
|-<br />
| '''Oceanweather Inc (OWI)'''<br />
| m<br />
| 12<br />
| <code>WTIMINC</code><br />
| f22x<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw<br />
| 312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22x, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, rs, ic<br />
| 12112<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12312<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12412<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22x, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12012<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22x, f25<br />
| none<br />
|- style="background:#efefef;" <br />
| '''Oceanweather Inc (OWI) NetCDF'''<br />
| m<br />
| 13<br />
| <code>WTIMINC</code><br />
| f22nc<br />
| [[NWS13]]<br />
|- style="background:#efefef;" <br />
| <br />
| m, rs<br />
| 113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st<br />
| 413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| f22nc, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12113<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12313<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12413<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| f22nc, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12013<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| f22nc, f25<br />
| none<br />
|- <br />
| '''H*Wind'''<br />
| m<br />
| 15<br />
| <code>WTIMINC</code><br />
| hwind+,f22<br />
| none<br />
|-<br />
| <br />
| m, rs<br />
| 115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
|<br />
| m, sw<br />
| 315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st<br />
| 415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| hwind+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, rs, ic<br />
| 12115<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12315<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12415<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12015<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| hwind+,f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| '''Geophysical Fluid Dynamics Laboratory (GFDL) Model'''<br />
| m<br />
| 16<br />
| <code>WTIMINC</code><br />
| gfdl+,f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw<br />
| 316<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code><br />
| gfdl+,f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12116<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12316 <br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12416<br />
| <code>WTIMINC</code> <code>RSTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic <br />
| 12016<br />
| <code>WTIMINC</code> <code>cice_timinc</code><br />
| gfdl+,f22, f25<br />
| none<br />
|-<br />
| '''Dynamic Asymmetric Model''' <br />
| m<br />
| 19<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code><br />
| pp,f22<br />
| none<br />
|-<br />
| <br />
| m, rs <br />
| 119<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw <br />
| 319<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st <br />
| 419<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, rs, ic<br />
| 12119<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|-<br />
| <br />
| m, sw, ic<br />
| 12319<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, st, ic<br />
| 12419 <br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|-<br />
| <br />
| m, ic<br />
| 12019<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>cice_timinc</code> <br />
| pp, f22, f25<br />
| none<br />
|- style="background:#efefef;"<br />
| '''Generalized Asymmetric Holland Model (GAHM)'''<br />
| m<br />
| 20<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code><br />
| pp, f22<br />
| none<br />
|- style="background:#efefef;"<br />
| <br />
| m, rs <br />
| 120<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, f23<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw <br />
| 320<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st <br />
| 420<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>RSTIMINC</code><br />
| pp, f22, STW<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, rs, ic<br />
| 12120<br />
| <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><br />
| pp, f22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, sw, ic<br />
| 12320<br />
| <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><br />
| pp, f22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, st, ic<br />
| 12420<br />
| <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><br />
| pp, f22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- style="background:#efefef;"<br />
| <br />
| m, ic<br />
| 12020<br />
| <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><br />
| pp, f22, f25<br />
| none<br />
|- <br />
| '''Blended GAHM and OWI'''<br />
| m<br />
| 30<br />
| <code>YYYY</code> <code>MM</code> <code>DD</code> <code>HH24</code> <code>StormNumber</code> <code>BLAdj</code> <code>geofactor</code> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22<br />
| none<br />
|- <br />
| <br />
| m, rs <br />
| 130<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw <br />
| 330<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st <br />
| 430<br />
| <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>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, rs, ic<br />
| 12130<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f23, f25<br />
| <ref group="note" name="a"></ref><br />
|- <br />
| <br />
| m, sw, ic<br />
| 12330<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, A+S, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, st, ic<br />
| 12430<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, STW, f25<br />
| <ref group="note" name="b"></ref><br />
|- <br />
| <br />
| m, ic<br />
| 12030<br />
| <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> <code>pureVortex</code> <code>pureBackground</code><br />
| pp, f22, nwsf22, f25<br />
| none<br />
|- <br />
|}<br />
<br />
<br />
===Forcing Abbreviations===<br />
: '''m''' - meteorology<br />
: '''rs''' - Wave radiation stress in an analyst-supplied [[fort.23]] input file<br />
: '''sw''' - Wave coupling using a simultaneously executing coupled SWAN model<br />
: '''st''' - Wave coupling using a simultaneously executing ESMF coupled STWAVE model<br />
: '''ic''' - Ice coverage using an analyst-supplied ice coverage data files<br />
<br />
===Requirements===<br />
: '''f22''' - Requires analyst-supplied [[fort.22]] meteorological forcing file.<br />
: '''f2xx+''' - Requires at least two fort.2xx meteorological forcing files from the GFS model. See fort.22 documentation for file naming and formatting details.<br />
: '''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.<br />
: '''hwind+''' - Requires two or more meteorological forcing files from the H*Wind model. See fort.22 documentation for details.<br />
: '''gfdl+''' - Requires two or more meteorological forcing files from the GFDL model. See fort.22 documentation for details.<br />
: '''nwsf22''' - Requires analyst-supplied [[NWS_20_fort.22]] meteorological forcing file.<br />
: '''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.<br />
: '''f23''' - Requires analyst-supplied fort.23 wave radiation stress input file.<br />
: '''A+S''' - Requires ADCIRC+SWAN executable and input files for the coupled version of SWAN.<br />
: '''STW''' - Requires ESMF-coupled ADCIRC and STWAVE and input files for STWAVE.<br />
: '''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.<br />
<br />
===Notes===<br />
<references group="note" /></div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file&diff=1098Fort.15 file2021-11-16T15:05:25Z<p>Taylorgasher: /* Ramping Meteorological Forcing at Hot-Start */</p>
<hr />
<div>This file contains the majority of the parameters required to run both the 2DDI and 3D versions of ADCIRC and the information to drive the model with harmonic boundary conditions (either elevation or flux). This file is required to run the ADCIRC model.<br />
<br />
== File Format ==<br />
See [[fort.15 file format]] for details.<br />
<br />
== Tips and Tricks ==<br />
=== Meteorological-Only Mode ===<br />
By turning off all ocean state-related outputting and disabling wave coupling, ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set <code>DT</code> equal to the time interval you wish met. data to be output, and then set the <code>[[NSPOOLM]]</code> and/or <code>[[NSPOOLGW]]</code> (the local and global met. output intervals) to <code>1</code> (i.e. output every time step). For typical 2D ADCIRC runs, this requires setting the following in the fort.15 file: <br/><br />
<code>[[NOUTE]] = 0</code> <br/><br />
<code>[[NOUTV]] = 0</code> <br/><br />
<code>[[NOUTGE]] = 0</code> <br/><br />
<code>[[NOUTGV]] = 0</code> <br/><br />
<code>[[NHSTAR]] = 0</code> <br/><br />
<code>[[NHASE]] = 0</code> <br/><br />
<code>[[NHASV]] = 0</code> <br/><br />
<code>[[NHAGE]] = 0</code> <br/><br />
<code>[[NHAGV]] = 0</code> <br/><br />
<br />
For passive scalar transport (<code>[[IM]] = 10</code>), also set: <br/><br />
<code>[[NOUTC]] = 0</code> <br/><br />
<code>[[NOUTGC]] = 0</code> <br/><br />
<br />
while for barotropic or baroclinic 3D ADCIRC, also set: <br/><br />
<code>[[I3DSD]] = 0</code> <br/><br />
<code>[[I3DSV]] = 0</code> <br/><br />
<code>[[I3DST]] = 0</code> <br/><br />
<code>[[I3DGD]] = 0</code> <br/><br />
<code>[[I3DGV]] = 0</code> <br/><br />
<code>[[I3DGT]] = 0</code> <br/><br />
<br />
=== Ramping Meteorological Forcing at Hot-Start ===<br />
It is generally best to [[ramp|ramping]] in forcing terms to the model to avoid shocking the system, but ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Since it is common-place to initialize meteorological forcing at hotstart time, there is a special parameter to facilitate hotstart ramping of met. data. Let's say you run a 15-day tide-only run and output a hotstart file. Setting <br/><br />
<code>[[NRAMP]] = 8</code><br/><br />
means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/><br />
<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP, DRAMPExtFlux, FluxSettlingTime, DRAMPIntFlux, DRAMPElev, DRAMPTip, DRAMPMete, DRAMPWRad, DRAMPUnMete</code><br/><br />
What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).<br />
<br />
<br />
[[Category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.18_file&diff=1097Fort.18 file2021-11-16T14:58:03Z<p>Taylorgasher: Added note about being in PE* folders</p>
<hr />
<div>The fort.18 file is a file with information needed for parallel (MPI) execution of ADCIRC (commonly termed PADCIRC). The file is created by the [[adcprep]] executable, which is run prior to launching a parallel ADCIRC run. The file is not located in the main run directory, but instead there is one copy of the file in each of the PE* (PE0000, PE0001, etc.) subdirectories created by adcprep. <br />
<br />
[[Category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.18&diff=1096Fort.182021-11-16T14:56:42Z<p>Taylorgasher: Created redirect</p>
<hr />
<div>#REDIRECT [[fort.18 file]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.18_file&diff=1095Fort.18 file2021-11-16T14:56:29Z<p>Taylorgasher: Created page with a simple explanation</p>
<hr />
<div>The fort.18 file is a file with information needed for parallel (MPI) execution of ADCIRC (commonly termed PADCIRC). The file is created by the [[adcprep]] executable, which is run prior to launching a parallel ADCIRC run. <br />
<br />
[[Category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file&diff=1093Fort.15 file2021-02-12T23:43:11Z<p>Taylorgasher: /* Meteorological-Only Mode */</p>
<hr />
<div>This file contains the majority of the parameters required to run both the 2DDI and 3D versions of ADCIRC and the information to drive the model with harmonic boundary conditions (either elevation or flux). This file is required to run the ADCIRC model.<br />
<br />
== File Format ==<br />
See [[fort.15 file format]] for details.<br />
<br />
== Tips and Tricks ==<br />
=== Meteorological-Only Mode ===<br />
By turning off all ocean state-related outputting and disabling wave coupling, ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set <code>DT</code> equal to the time interval you wish met. data to be output, and then set the <code>[[NSPOOLM]]</code> and/or <code>[[NSPOOLGW]]</code> (the local and global met. output intervals) to <code>1</code> (i.e. output every time step). For typical 2D ADCIRC runs, this requires setting the following in the fort.15 file: <br/><br />
<code>[[NOUTE]] = 0</code> <br/><br />
<code>[[NOUTV]] = 0</code> <br/><br />
<code>[[NOUTGE]] = 0</code> <br/><br />
<code>[[NOUTGV]] = 0</code> <br/><br />
<code>[[NHSTAR]] = 0</code> <br/><br />
<code>[[NHASE]] = 0</code> <br/><br />
<code>[[NHASV]] = 0</code> <br/><br />
<code>[[NHAGE]] = 0</code> <br/><br />
<code>[[NHAGV]] = 0</code> <br/><br />
<br />
For passive scalar transport (<code>[[IM]] = 10</code>), also set: <br/><br />
<code>[[NOUTC]] = 0</code> <br/><br />
<code>[[NOUTGC]] = 0</code> <br/><br />
<br />
while for barotropic or baroclinic 3D ADCIRC, also set: <br/><br />
<code>[[I3DSD]] = 0</code> <br/><br />
<code>[[I3DSV]] = 0</code> <br/><br />
<code>[[I3DST]] = 0</code> <br/><br />
<code>[[I3DGD]] = 0</code> <br/><br />
<code>[[I3DGV]] = 0</code> <br/><br />
<code>[[I3DGT]] = 0</code> <br/><br />
<br />
=== Ramping Meteorological Forcing at Hot-Start ===<br />
Let's say you run a 15-day tide-only run and output a hotstart file. Then, you want to hotstart a simulation with meteorological forcing. Initiating the hotstart simulation with full-strength met. forcing could apply a shock to the system, creating spurious waves. Therefore, it's best to ramp in the met. forcing. But, ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Setting <br/><br />
<code>[[NRAMP]] = 8</code><br/><br />
means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/><br />
<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete</code><br/><br />
What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).<br />
<br />
<br />
[[Category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file&diff=1092Fort.15 file2021-02-12T23:42:37Z<p>Taylorgasher: </p>
<hr />
<div>This file contains the majority of the parameters required to run both the 2DDI and 3D versions of ADCIRC and the information to drive the model with harmonic boundary conditions (either elevation or flux). This file is required to run the ADCIRC model.<br />
<br />
== File Format ==<br />
See [[fort.15 file format]] for details.<br />
<br />
== Tips and Tricks ==<br />
=== Meteorological-Only Mode ===<br />
By turning off all ocean state-related outputting and disabling wave coupling, ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set <code>DT</code> equal to the time interval you wish met. data to be output, and then set the <code>[[NSPOOLM]]</code> and/or <code>[[NSPOOLGW]]</code> (the local and global met. output intervals) to <code>1</code> (i.e. output every time step). For typical 2D ADCIRC runs, this requires setting the following in the fort.15 file: <br/><br />
<code>[[NOUTE]] = 0</code> <br/><br />
<code>[[NOUTV]] = 0</code> <br/><br />
<code>[[NOUTGE]] = 0</code> <br/><br />
<code>[[NOUTGV]] = 0</code> <br/><br />
<code>[[NHSTAR]] = 0</code> <br/><br />
<code>[[NHASE]] = 0</code> <br/><br />
<code>[[NHASV]] = 0</code> <br/><br />
<code>[[NHAgE]] = 0</code> <br/><br />
<code>[[NHAGV]] = 0</code> <br/><br />
<br />
For passive scalar transport (<code>[[IM]] = 10</code>), also set: <br/><br />
<code>[[NOUTC]] = 0</code> <br/><br />
<code>[[NOUTGC]] = 0</code> <br/><br />
<br />
while for barotropic or baroclinic 3D ADCIRC, also set: <br/><br />
<code>[[I3DSD]] = 0</code> <br/><br />
<code>[[I3DSV]] = 0</code> <br/><br />
<code>[[I3DST]] = 0</code> <br/><br />
<code>[[I3DGD]] = 0</code> <br/><br />
<code>[[I3DGV]] = 0</code> <br/><br />
<code>[[I3DGT]] = 0</code> <br/><br />
<br />
=== Ramping Meteorological Forcing at Hot-Start ===<br />
Let's say you run a 15-day tide-only run and output a hotstart file. Then, you want to hotstart a simulation with meteorological forcing. Initiating the hotstart simulation with full-strength met. forcing could apply a shock to the system, creating spurious waves. Therefore, it's best to ramp in the met. forcing. But, ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Setting <br/><br />
<code>[[NRAMP]] = 8</code><br/><br />
means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/><br />
<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete</code><br/><br />
What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).<br />
<br />
<br />
[[Category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Fort.15_file&diff=1091Fort.15 file2021-02-12T23:40:49Z<p>Taylorgasher: updated met-only mode, per recommendations from Kyle Steffen</p>
<hr />
<div>This file contains the majority of the parameters required to run both the 2DDI and 3D versions of ADCIRC and the information to drive the model with harmonic boundary conditions (either elevation or flux). This file is required to run the ADCIRC model.<br />
<br />
== File Format ==<br />
See [[fort.15 file format]] for details.<br />
<br />
== Tips and Tricks ==<br />
=== Meteorological-Only Mode ===<br />
By turning off all ocean state-related outputting and disabling wave coupling, ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set <code>DT</code> equal to the time interval you wish met. data to be output, and then set the <code>[[NSPOOLM]]</code> and/or <code>[[NSPOOLGW]]</code> (the local and global met. output intervals) to <code>1</code> (i.e. output every time step). For typical 2D ADCIRC runs, this requires setting the following in the fort.15 file: <br/><br />
<code>[[NOUTE]] = 0</code> <br/><br />
<code>[[NOUTV]] = 0</code> <br/><br />
<code>[[NOUTGE]] = 0</code> <br/><br />
<code>[[NOUTGV]] = 0</code> <br/><br />
<code>[[NHSTAR]] = 0</code> <br/><br />
<code>[[NHASE]] = 0</code> <br/><br />
<code>[[NHASV]] = 0</code> <br/><br />
<code>[[NHAgE]] = 0</code> <br/><br />
<code>[[NHAGV]] = 0</code> <br/><br />
<br />
For passive scalar transport (<code>[[IM]] = 10</code>), also set: <br/><br />
<code>[[NOUTC]] = 0</code> <br/><br />
<code>[[NOUTGC]] = 0</code> <br/><br />
<br />
while for barotropic or baroclinic 3D ADCIRC, also set: <br />
<code>[[I3DSD]] = 0</code> <br/><br />
<code>[[I3DSV]] = 0</code> <br/><br />
<code>[[I3DST]] = 0</code> <br/><br />
<code>[[I3DGD]] = 0</code> <br/><br />
<code>[[I3DGV]] = 0</code> <br/><br />
<code>[[I3DGT]] = 0</code> <br/><br />
<br />
=== Ramping Meteorological Forcing at Hot-Start ===<br />
Let's say you run a 15-day tide-only run and output a hotstart file. Then, you want to hotstart a simulation with meteorological forcing. Initiating the hotstart simulation with full-strength met. forcing could apply a shock to the system, creating spurious waves. Therefore, it's best to ramp in the met. forcing. But, ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Setting <br/><br />
<code>[[NRAMP]] = 8</code><br/><br />
means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/><br />
<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete</code><br/><br />
What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).<br />
<br />
<br />
[[Category:input files]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1083Template:ADC version2020-07-10T20:13:54Z<p>Taylorgasher: updated examples</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude><br />
{| style="border: 4px solid #AA00AA; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
| ADCIRC version: <br />
| <abbr style="font-weight: bold; font-size: 180%;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|}<br />
</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52.dev, 53|relation=gt}}</nowiki></code> || {{ADC version|version=52.dev, 53|relation=gt}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le}}</nowiki></code> || {{ADC version|version=53|relation=le}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-}}</nowiki></code> || {{ADC version|version=50|relation=-}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:Version_support_box&diff=1082Template:Version support box2020-07-10T19:37:02Z<p>Taylorgasher: typo</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid {{#switch: {{{support|}}} <br />
|sup|yes|supported=&#35;00BB00; <br />
|tp|tech preview=&#35;EEEE00; <br />
|uns|no|unsupported=&#35;FF9933; <br />
|dep|deprecated=&#35;FF0000; <br />
| #default=&#35;FF00FF; <br />
}} float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| {{#switch: {{{size|}}} |full=ADCIRC version: |mini= | #default=ADCIRC version: }}<br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline; text-align:center;" | {{#switch: {{{size|}}} |full={{Support level text|level={{{support}}}}} |mini= | #default={{Support level text|level={{{support}}}}}<br />
}} <!----end outer switch-case statement for size----><br />
|}</onlyinclude><br />
<br />
This template will give a box with version number indicator and feature support info on the right-hand side of a page (or table or whatever) that it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is in and how supported/finalized the feature is in the code. This is a variant of [[Template:ADC version]]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{Version support box|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>|support=</nowiki><u><nowiki>SUPPORT</nowiki></u><nowiki>|size=</nowiki><u><nowiki>SIZE</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u>, <code><u>RELATION</code></u>, <code><u>SUPPORT</code></u>, and <code><u>SIZE</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{Version support box}}</nowiki></code> || {{Version support box}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52}}</nowiki></code> || {{Version support box|version=52}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=>}}</nowiki></code> || {{Version support box|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=gt|support=sup}}</nowiki></code> || {{Version support box|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=44-47|relation=ge|support=tech preview|size=mini}}</nowiki></code> || {{Version support box|version=44-47|relation=ge|support=tech preview|size=mini}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52.dev, 53|relation=le|support=tp}}</nowiki></code> || {{Version support box|version=52.dev, 53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=50|relation=-|support=uns}}</nowiki></code> || {{Version support box|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{Version support box|relation=+|support=unsupported}}</nowiki></code> || {{Version support box|relation=+|support=unsupported}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}</nowiki></code> || {{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|support=dep|size=mini}}</nowiki></code> || {{Version support box|version=a long, long time ago|support=dep|size=mini}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:Version_support_box&diff=1081Template:Version support box2020-07-10T19:35:39Z<p>Taylorgasher: again</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid {{#switch: {{{support|}}} <br />
|sup|yes|supported=&#35;00BB00; <br />
|tp|tech preview=&#35;EEEE00; <br />
|uns|no|unsupported=&#35;FF9933; <br />
|dep|deprecated=&#35;FF0000; <br />
| #default=&#35;FF00FF; <br />
}} float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| {{#switch: {{{size|}}} |full=ADCIRC version: |mini= | #default=ADCIRC version: }}<br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline; text-align:center;" | {{#switch: {{{size|}}} |full={{Support level text|level={{{support}}}}} |mini= | #default={{Support level text|level={{{support}}}}}<br />
}} <!----end outer switch-case statement for size----><br />
|}</onlyinclude><br />
<br />
This template will give a box with version number indicator and feature support info on the right-hand side of a page (or table or whatever) that it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is in and how supported/finalized the feature is in the code. This is a variant of [[Template:ADC version]]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{Version support box|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>|support=</nowiki><u><nowiki>SUPPORT</nowiki></u><nowiki>|size=</nowiki><u><nowiki>SIZE</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u>, <code><u>RELATION</code></u>, <code><u>SUPPORT</code></u>, and <code><u>SIZE</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{Version support box}}</nowiki></code> || {{Version support box}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52}}</nowiki></code> || {{Version support box|version=52}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=>}}</nowiki></code> || {{Version support box|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=gt|support=sup}}</nowiki></code> || {{Version support box|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=44-47|relation=ge|support=tech preview|size=mini}}</nowiki></code> || {{Version support box|version=44-47|relation=ge|support=tech preview|size=mini}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52.dev, 53|relation=le|support=tp}}</nowiki></code> || {{Version support box|version=52.dev, 53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=50|relation=-|support=uns}}</nowiki></code> || {{Version support box|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{Version support box|relation=+|support=unsupported}}</nowiki></code> || {{Version support box|relation=+|support=unsupported}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}</nowiki></code> || {{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep|size=mini}}</nowiki></code> || {{Version support box|version=a long, long time ago|support=dep|size=mini}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:Version_support_box&diff=1080Template:Version support box2020-07-10T19:29:51Z<p>Taylorgasher: revised examples</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid {{#switch: {{{support|}}} <br />
|sup|yes|supported=&#35;00BB00; <br />
|tp|tech preview=&#35;EEEE00; <br />
|uns|no|unsupported=&#35;FF9933; <br />
|dep|deprecated=&#35;FF0000; <br />
| #default=&#35;FF00FF; <br />
}} float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| {{#switch: {{{size|}}} |full=ADCIRC version: |mini= | #default=ADCIRC version: }}<br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline; text-align:center;" | {{#switch: {{{size|}}} |full={{Support level text|level={{{support}}}}} |mini= | #default={{Support level text|level={{{support}}}}}<br />
}} <!----end outer switch-case statement for size----><br />
|}</onlyinclude><br />
<br />
This template will give a box with version number indicator and feature support info on the right-hand side of a page (or table or whatever) that it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is in and how supported/finalized the feature is in the code. This is a variant of [[Template:ADC version]]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{Version support box|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>|support=</nowiki><u><nowiki>SUPPORT</nowiki></u><nowiki>|size=</nowiki><u><nowiki>SIZE</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u>, <code><u>RELATION</code></u>, <code><u>SUPPORT</code></u>, and <code><u>SIZE</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{Version support box}}</nowiki></code> || {{Version support box}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52}}</nowiki></code> || {{Version support box|version=52}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=44-47}}</nowiki></code> || {{Version support box|version=44-47}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=>}}</nowiki></code> || {{Version support box|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=gt|support=sup}}</nowiki></code> || {{Version support box|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52.dev, 53|relation=ge|support=tech preview|size=mini}}</nowiki></code> || {{Version support box|version=52.dev, 53|relation=ge|support=tech preview|size=mini}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=53|relation=le|support=tp}}</nowiki></code> || {{Version support box|version=53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=50|relation=-|support=uns}}</nowiki></code> || {{Version support box|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{Version support box|relation=+|support=unsupported}}</nowiki></code> || {{Version support box|relation=+|support=unsupported}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}</nowiki></code> || {{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep|size=mini}}</nowiki></code> || {{Version support box|version=a long, long time ago|relation=+|support=dep|size=mini}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1079Template:ADC version2020-07-10T19:09:05Z<p>Taylorgasher: made color purple to distinguish from version support box colors</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude><br />
{| style="border: 4px solid #AA00AA; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
| ADCIRC version: <br />
| <abbr style="font-weight: bold; font-size: 180%;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|}<br />
</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt}}</nowiki></code> || {{ADC version|version=52|relation=gt}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le}}</nowiki></code> || {{ADC version|version=53|relation=le}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-}}</nowiki></code> || {{ADC version|version=50|relation=-}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1078Template:ADC version2020-07-10T19:06:52Z<p>Taylorgasher: Reverting to version before all of today's edits</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude><br />
{| style="border: 4px solid #FF9933; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
| ADCIRC version: <br />
| <abbr style="font-weight: bold; font-size: 180%;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|}<br />
</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt}}</nowiki></code> || {{ADC version|version=52|relation=gt}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le}}</nowiki></code> || {{ADC version|version=53|relation=le}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-}}</nowiki></code> || {{ADC version|version=50|relation=-}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:Version_support_box&diff=1077Template:Version support box2020-07-10T19:00:47Z<p>Taylorgasher: Created this to separate it from ADC version</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid {{#switch: {{{support|}}} <br />
|sup|yes|supported=&#35;00BB00; <br />
|tp|tech preview=&#35;EEEE00; <br />
|uns|no|unsupported=&#35;FF9933; <br />
|dep|deprecated=&#35;FF0000; <br />
| #default=&#35;FF00FF; <br />
}} float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| {{#switch: {{{size|}}} |full=ADCIRC version: |mini= | #default=ADCIRC version: }}<br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline; text-align:center;" | {{#switch: {{{size|}}} |full={{Support level text|level={{{support}}}}} |mini= | #default={{Support level text|level={{{support}}}}}<br />
}} <!----end outer switch-case statement for size----><br />
|}</onlyinclude><br />
<br />
This template will give a box with version number indicator and feature support info on the right-hand side of a page (or table or whatever) that it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is in and how supported/finalized the feature is in the code. This is a variant of [[Template:ADC version]]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{Version support box|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>|support=</nowiki><u><nowiki>SUPPORT</nowiki></u><nowiki>|size=</nowiki><u><nowiki>SIZE</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u>, <code><u>RELATION</code></u>, <code><u>SUPPORT</code></u>, and <code><u>SIZE</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{Version support box}}</nowiki></code> || {{Version support box}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52}}</nowiki></code> || {{Version support box|version=52}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=44-47}}</nowiki></code> || {{Version support box|version=44-47}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=>}}</nowiki></code> || {{Version support box|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=gt|support=sup}}</nowiki></code> || {{Version support box|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=52|relation=gt|support=sup|size=mini}}</nowiki></code> || {{Version support box|version=52|relation=gt|support=sup|size=mini}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=53|relation=le|support=tp}}</nowiki></code> || {{Version support box|version=53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=50|relation=-|support=uns}}</nowiki></code> || {{Version support box|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep}}</nowiki></code> || {{Version support box|version=a long, long time ago|relation=+|support=dep}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}</nowiki></code> || {{Version support box|version=a long, long time ago|relation=+|support=dep|size=full}}<br />
|-<br />
| <code><nowiki>{{Version support box|version=a long, long time ago|relation=+|support=dep|size=mini}}</nowiki></code> || {{Version support box|version=a long, long time ago|relation=+|support=dep|size=mini}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1076Template:ADC version2020-07-10T18:51:00Z<p>Taylorgasher: added size option, now using the Support Level Text template</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid {{#switch: {{{support|}}} <br />
|sup|yes|supported=&#35;00BB00; <br />
|tp|tech preview=&#35;EEEE00; <br />
|uns|no|unsupported=&#35;FF9933; <br />
|dep|deprecated=&#35;FF0000; <br />
| #default=&#35;FF00FF; <br />
}} float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| {{#switch: {{{size|}}} |full=ADCIRC version: |mini= | #default=ADCIRC version: }}<br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline; text-align:center;" | {{#switch: {{{size|}}} |full={{Support level text|level={{{support}}}}} |mini= | #default={{Support level text|level={{{support}}}}}<br />
}} <!----end outer switch-case statement for size----><br />
|}</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt|support=sup}}</nowiki></code> || {{ADC version|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt|support=sup|size=mini}}</nowiki></code> || {{ADC version|version=52|relation=gt|support=sup|size=mini}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le|support=tp}}</nowiki></code> || {{ADC version|version=53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-|support=uns}}</nowiki></code> || {{ADC version|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+|support=dep}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+|support=dep}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+|support=dep|size=full}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+|support=dep|size=full}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+|support=dep|size=mini}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+|support=dep|size=mini}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:Support_level_text&diff=1075Template:Support level text2020-07-10T18:44:53Z<p>Taylorgasher: created to simplify ADC version</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{{#switch: {{{level|}}} <!----switch-case statement for support level text----><br />
|sup|yes|supported=Supported<br />
|tp|tech preview=Tech Preview<br />
|uns|no|unsupported=Unsupported<br />
|dep|deprecated=Deprecated<br />
| #default=?unknown support?<br />
}}</onlyinclude><br />
<br />
This template will give a text label for the level of support a piece of code will receive. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{Support level text|level=</nowiki><u><nowiki>LEVEL</nowiki></u></code><br />
<br />
You specify the values for <code><u>LEVEL</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{Support level text}}</nowiki></code> || {{Support level text}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=sup}}</nowiki></code> || {{Support level text|level=sup}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=yes}}</nowiki></code> || {{Support level text|level=yes}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=supported}}</nowiki></code> || {{Support level text|level=supported}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=tp}}</nowiki></code> || {{Support level text|level=tp}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=tech preview}}</nowiki></code> || {{Support level text|level=tech preview}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=uns}}</nowiki></code> || {{Support level text|level=uns}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=no}}</nowiki></code> || {{Support level text|level=no}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=unsupported}}</nowiki></code> || {{Support level text|level=unsupported}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=dep}}</nowiki></code> || {{Support level text|level=dep}}<br />
|-<br />
| <code><nowiki>{{Support level text|level=deprecated}}</nowiki></code> || {{Support level text|level=deprecated}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1074Template:ADC version2020-07-10T18:01:11Z<p>Taylorgasher: something</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid {{#switch: {{{support|}}} <br />
|sup|yes|supported=&#35;00BB00; <br />
|tp|tech preview=&#35;EEEE00; <br />
|uns|no|unsupported=&#35;FF9933; <br />
|dep|deprecated=&#35;FF0000; <br />
| #default=&#35;FF00FF; <br />
}} float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| ADCIRC version: <br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline; text-align:center;" | {{#switch: {{{support|}}} <!----switch-case statement for support level text----><br />
|sup|yes|supported=Supported<br />
|tp|tech preview=Tech Preview<br />
|uns|no|unsupported=Unsupported<br />
|dep|deprecated=Deprecated<br />
| #default=?unknown support?<br />
}} <!----end switch-case statement for support level text----><br />
|}</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt|support=sup}}</nowiki></code> || {{ADC version|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le|support=tp}}</nowiki></code> || {{ADC version|version=53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-|support=uns}}</nowiki></code> || {{ADC version|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+|support=dep}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+|support=dep}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1073Template:ADC version2020-07-10T17:35:05Z<p>Taylorgasher: got color working</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid {{#switch: {{{support|}}} |sup|yes|supported=&#35;00BB00; |tp|tech preview=&#35;EEEE00; |uns|no|unsupported=&#35;FF9933; |dep|deprecated=&#35;FF0000; | #default=&#35;FF00FF; }} float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| ADCIRC version: <br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline;" | {{#switch: {{{support|}}} <!----switch-case statement for support level text----><br />
|sup|yes|supported=Supported<br />
|tp|tech preview=Tech Preview<br />
|uns|no|unsupported=Unsupported<br />
|dep|deprecated=Deprecated<br />
|?unknown support?<br />
}} <!----end switch-case statement for support level text----><br />
|}</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt|support=sup}}</nowiki></code> || {{ADC version|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le|support=tp}}</nowiki></code> || {{ADC version|version=53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-|support=uns}}</nowiki></code> || {{ADC version|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+|support=dep}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+|support=dep}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1072Template:ADC version2020-07-10T16:57:23Z<p>Taylorgasher: added examples per last thing</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid #FF9933; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| ADCIRC version: <br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline;" | {{#switch: {{{support|}}} <!----switch-case statement for support level----><br />
|sup|yes|supported=Supported<br />
|tp|tech preview=Tech Preview<br />
|uns|no|unsupported=Unsupported<br />
|dep|deprecated=Deprecated<br />
|?unknown support?<br />
}}<br />
|}</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt|support=sup}}</nowiki></code> || {{ADC version|version=52|relation=gt|support=sup}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le|support=tp}}</nowiki></code> || {{ADC version|version=53|relation=le|support=tp}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-|support=uns}}</nowiki></code> || {{ADC version|version=50|relation=-|support=uns}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+|support=dep}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+|support=dep}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1071Template:ADC version2020-07-10T16:48:06Z<p>Taylorgasher: added switch-case for support level</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid #FF9933; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| ADCIRC version: <br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline;" | {{#switch: {{{support|}}} <!----switch-case statement for support level----><br />
|sup|yes|supported=Supported<br />
|tp|tech preview=Tech Preview<br />
|uns|no|unsupported=Unsupported<br />
|dep|deprecated=Deprecated<br />
|?unknown support?<br />
}}<br />
|}</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt}}</nowiki></code> || {{ADC version|version=52|relation=gt}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le}}</nowiki></code> || {{ADC version|version=53|relation=le}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-}}</nowiki></code> || {{ADC version|version=50|relation=-}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Template:ADC_version&diff=1070Template:ADC version2020-07-10T16:38:03Z<p>Taylorgasher: Starting a series of edits. This time: got 2 row span thing working</p>
<hr />
<div><!----------This is the actual template----------><br />
<onlyinclude>{| style="border: 4px solid #FF9933; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse: collapse;" <!-----Table format-----><br />
|-<br />
| ADCIRC version: <br />
| rowspan="2" | <abbr style="font-weight: bold; font-size: 180%; vertical-align:middle;"> {{#switch: {{{relation|}}} <!-----switch-case statement for relation symbol-----><br />
|eq|{{=}}={{=}}<br />
|gt|>=<small>&gt;</small><br />
|lt|<=<small>&lt;</small><br />
|ge|+=<small>&ge;</small><br />
|le|-=<small>&le;</small><br />
}} {{#ifeq: {{{version|}}} | {{{version}}} | {{{version}}} | ?????}} </abbr> <!-----display version if supplied-----><br />
|-<br />
| style="font-weight: bold; text-decoration:underline;" | ?semi-supported?<br />
|}</onlyinclude><br />
<br />
This template will give a version number indicator on the right-hand side of a page (or table or whatever) it is added to, and is intended as a way to highlight what version(s) of ADCIRC something is relevant for. This was inspired by [https://www.mediawiki.org/wiki/Template:MW_version a much more advanced template on MediaWiki]. <br />
<br />
== Syntax ==<br />
<code><nowiki>{{ADC version|version=</nowiki><u><nowiki>VERSION</nowiki></u><nowiki>|relation=</nowiki><u><nowiki>RELATION</nowiki></u><nowiki>}}</nowiki></code><br />
<br />
You specify the values for <code><u>VERSION</code></u> and <code><u>RELATION</code></u>, examples of which are given below. <br />
<br />
== Examples ==<br />
{| class="wikitable"<br />
!you type<br />
!you get<br />
|-<br />
| <code><nowiki>{{ADC version}}</nowiki></code> || {{ADC version}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52}}</nowiki></code> || {{ADC version|version=52}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=44-47}}</nowiki></code> || {{ADC version|version=44-47}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=>}}</nowiki></code> || {{ADC version|version=52|relation=>}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=52|relation=gt}}</nowiki></code> || {{ADC version|version=52|relation=gt}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=53|relation=le}}</nowiki></code> || {{ADC version|version=53|relation=le}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=50|relation=-}}</nowiki></code> || {{ADC version|version=50|relation=-}}<br />
|-<br />
| <code><nowiki>{{ADC version|version=a long, long time ago|relation=+}}</nowiki></code> || {{ADC version|version=a long, long time ago|relation=+}}<br />
|}</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=File:MaxeleDiffRun13MinusRun12View1.png&diff=1060File:MaxeleDiffRun13MinusRun12View1.png2020-07-10T14:52:05Z<p>Taylorgasher: </p>
<hr />
<div>== Summary ==<br />
Change in peak surge due to the new interpolation of z0 values. New minus old. Hindcast run of Hurricane Isaac with OWI met. on the NGOM3_v18b_chk.grd mesh.</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=Wind_Stress&diff=1059Wind Stress2020-07-10T14:51:45Z<p>Taylorgasher: /* Interpolating Roughness Lengths Before v55 */ added link to maxele diff</p>
<hr />
<div>When wind blows over the water, it exerts a shear stress at the water surface that transfers horizontal momentum vertically downward across the air–sea interface, driving circulation. In ADCIRC, wind stress is an input forcing term, with several different formats provided. See the <code>[[NWS]]</code> parameter for available formats. In most cases, the exact wind stress to be applied to the model is not provided, therefore ADCIRC must determine how to convert a given wind speed to the actual stress applied at the ocean surface. This page covers the various aspects of this process, as well as the options available to the user. <br />
<br />
== Definition of Winds ==<br />
The characteristics of wind forcing are often broken down in three ways: <br />
# Whether the winds are considered to be over-water (termed "marine exposure") or over-land<br />
# The elevation above the sea (or ground) surface of the winds<br />
# The time-averaging (if any) that has been applied<br />
<br />
ADCIRC generally expects 10-meter, 10-minute winds at their actual exposure, although the exact expectations vary depending on the input type. For instance, when Holland-type wind inputs are provided (e.g. <code>NWS=8</code> or <code>NWS=20</code>), the wind speed is expected to be the '''1-minute [https://en.wikipedia.org/wiki/Maximum_sustained_wind maximum sustained wind]''' at 10 meters elevation. If marine-exposure winds are provided, then [[Fort.13_file#Surface_Roughness|surface roughness]] reductions may be needed<br />
<ref name="simiu1996">Simiu, E., Scanlan, R.H., 1996. Wind effects on structures: fundamentals and applications to design, 3rd ed. ed. John Wiley, New York.</ref><br />
<ref name="simiu2018">Simiu, E., Yeo, D., 2018. Wind effects on structures: modern structural design for wind, Fourth edition. ed. John Wiley & Sons, Hoboken, NJ.</ref><br />
. If winds are provided with a different averaging time, then an appropriate correction may be needed, though winds with averaging times of 10 to 60 minutes are generally considered to be quite similar; this is the so-called mesoscale gap. For recommendations on wind time-scale conversions not handled internally by ADCIRC, for tropical cyclones, see the WMO guidelines of Harper et al.<br />
<ref name="wmotcaveraging">Harper, B., Kepert, J., Ginger, J., 2010. Guidelines for converting between various wind averaging periods in tropical cyclone conditions (No. WMO/TD-No. 1555). WMO, Geneva, Switzerland.</ref><br />
<br />
== Roughness Reductions ==<br />
Reductions in wind speed to convert to the appropriate exposure come from a logarithmic boundary layer formulation (see, e.g. <ref name="simiu1996" /> <ref name="simiu2018" />) to determine a fraction <math>f</math> to reduce the winds, <br />
:<math>f=\left ( \frac{z_{0l}}{z_{0m}}\right ) ^{0.0706} \left ( \frac{\ln \frac{10}{z_{0l}}}{\ln \frac{10}{z_{0m}}} \right ) </math><br />
for marine roughness length <math>z_{0m}</math> and reduced ("land") roughness length <math>z_{0l}</math>. Wind speed is then reduced as, <br />
:<math>\mathbf{w}'=f\mathbf{w}=f [u,v]</math><br />
for x- and y- wind vector components <math>u</math> and <math>v</math>. The marine roughness length is, <br />
:<math>z_{0m}=\frac{0.018}{g} c_d \left \Vert \mathbf{w} \right \| </math><br />
for Charnock parameter <math>0.018</math>, drag coefficient <math>c_d</math> and acceleration due to gravity <math>g</math>. The wind drag coefficient is addressed below in [[#Converting Wind Velocity to Wind Stress|this section]]. As previously noted, the reduced ("land") roughness length <math>z_{0l}</math> is specified by the user via the [[Fort.13_file#Surface_Roughness|surface roughness]] nodal attribute. The fraction <math>f</math> is bounded on <math>[0,1]</math>, meaning the winds cannot be increased, nor change direction. <br />
<br />
=== Older Behavior ===<br />
====Interpolating Roughness Lengths Before v55====<br />
[[File:WindTraceV2.png|right|thumb|Comparison of output wind velocities using old and new methods.]]<br />
{{ADC version|version=55|relation=lt}}Before version 55, the directional wind reductions were applied by determining which of the 12 directional bins the wind velocity (at each time step) fell into, and using that roughness reduction, i.e. nearest neighbor interpolation. Starting in version 55, the roughness length is linearly (in angle space) interpolated between directional bins. In testing, this has been found to generally have a very small effect on water levels, but a notable effect on wind speeds, since time evolution of winds is smoother. It can have large localized effects on water levels in rare cases in cases where there are large changes in neighboring roughness length bins coinciding with well-aligned winds, as in [[:File:MaxeleDiffRun13MinusRun12View1.png|this test case]] with Hurricane Isaac. <br />
<br clear=all><br />
<br />
====Roughness Reduction Bug Before v54====<br />
{{ADC version|version=54|relation=lt}}Before version 54, there was a bug in this calculation. The mistake and its effects are addressed in this PDF document: <u><span style="color:red">'''ADD A LINK TO A PDF HERE YOOOOO'''</span></u>.<br />
<br />
== Converting Wind Velocity to Wind Stress ==<br />
In ADCIRC, four formulations are available to convert wind velocities to the wind stresses applied in the momentum equations. Although there are several ways to control this, users are generally encouraged to use the [[metControl]] namelist in the [[fort.15]] file. The default drag formulation is the Garratt<br />
<ref name=garratt1977>Garratt, J.R., 1977. Review of Drag Coefficients over Oceans and Continents. Mon. Wea. Rev. 105, 915–929. https://doi.org/10.1175/1520-0493(1977)105<0915:RODCOO>2.0.CO;2</ref><br />
linear formula. An alternative for use with tropical cyclones is the Powell formulation,<br />
<ref>Powell, M.D., Vickery, P.J., Reinhold, T.A., 2003. Reduced drag coefficient for high wind speeds in tropical cyclones. Nature 422, 279–283. https://doi.org/10.1038/nature01481</ref><br />
which varies drag by the sector of the tropical cyclone. When ice coverage is included in the model, a wind drag formulation that accounts for this effect should be used. By default, if ice coverage input data are supplied, ADCIRC uses a cubic function of ice coverage, termed the "IceCube" drag formulation. Lastly, the "swell" drag law option allows users to utilize SWAN's drag formulation when employing the coupled model. <br />
<br />
In all cases, the actual wind drag coefficients determined by ADCIRC can be output to a [[fort.63]]-type file named [[winddrag.173]]. Output settings (file format, output start/end times, and output interval) match those of either the fort.63 or fort.73/74 files, ''I think'' fort.73/74. Outputting of this file is enabled by setting <code>outputWindDrag=.TRUE.</code> in the <code>&metControl</code> namelist of the [[Fort.15_file_format#Namelists|fort.15 file's namelist section]]. <br />
<br />
=== Garratt Drag Formulation ===<br />
This is the default wind drag formulation in ADCIRC. From Garratt (1977)<ref name=garratt1977></ref>, the formula is, <br />
:<math>c_d=0.001 \left ( 0.75+0.067 \left \Vert \mathbf{w} \right \| \right ) </math><br />
<br />
By default, ADCIRC puts an upper bound on the drag coefficient of <math>c_d\le0.0035</math>. This upper bound <code>WindDragLimit</code> can be changed via the [[metControl]] fort.15 namelist. <br />
<br />
=== Powell Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
=== IceCube Drag Formulation ===<br />
<span style="color:red">CONTRIBUTOR NEEDED</span><br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:meteorology]]<br />
[[Category:physics]]</div>Taylorgasherhttps://wiki.adcirc.org/index.php?title=IM&diff=1050IM2020-07-09T15:45:55Z<p>Taylorgasher: finished adding flag variables</p>
<hr />
<div>'''<code>IM</code>''' is an important parameter in the [[fort.15 file]] that defines numerical model formulation and dimension. Among other things, <code>IM</code> specifies whether ADCIRC is solved in two-dimensional depth-integrated (2DDI) or in three-dimensions (3D), solution of the governing equations is semi-implicit or explicit in time, and whether the model formulation is barotropic or baroclinic. Popular values for 2D barotropic ADCIRC include <code>IM=0</code> and <code>IM=111112</code>, though the latter also requires modifying <code>[[A00, B00, C00]]</code>. <br />
<br />
== Default IM Values ==<br />
Default simulation option combinations can be specified through single or double digit values, some of which are shortcuts to the six-digit codes described in the next heading. <br />
The available <code>IM</code> values are specified in the table below and in the following section on 6-digit values:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! IM Value<br />
! Six-digit Equivalent<br />
! Description<br />
|-<br />
| 0<br />
| 111111<br />
| Barotropic 2DDI <br />
|-<br />
| 1<br />
| 611111<br />
| Barotropic 3D velocity-based momentum<br />
|-<br />
| 2<br />
| -<br />
| Barotropic 3D stress-based momentum<br />
|-<br />
| 10<br />
| -<br />
| Barotropic 2DDI with passive scalar transport<br />
|-<br />
| 11<br />
| -<br />
| Barotropic 3D velocity-based momentum with passive scalar transport<br />
|-<br />
| 20<br />
| 111113<br />
| Baroclinic 2DDI<br />
|-<br />
| 21<br />
| 611113<br />
| Baroclinic 3D velocity-based momentum<br />
|-<br />
| 30<br />
| -<br />
| Baroclinic 2DDI with passive scalar transport<br />
|-<br />
| 31<br />
| -<br />
| Baroclinic 3D velocity-based momentum with passive scalar transport<br />
|}<br />
<br />
Note that all default <code>IM</code> values employ the semi-implicit consistent GWCE mass matrix solver. It has less numerical error and tends to be more stable than the explicit mass-lumping approach at the expense of computational time and memory.<br />
<br />
== Six-digit IM Codes ==<br />
For fine-grained control of various options six-digit codes for <code>IM</code> can be specified. Each digit represents a specific option regarding the dimension and the formulation of certain terms or integration methods in the GWCE or momentum equations. <br />
The available options for each digit are specified below, with the first digit being the left-most. The internal flags that are set are listed to help users dig through the code. <br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Value<br />
! Digit 1: 2DDI/3D, Lateral Stress in GWCE<ref name=Kendra1>K.M. Dresback, R.L. Kolar, R.A. Luettich, Jr. (2005). On the Form of the Momentum Equation and Lateral Stress Closure Law in Shallow Water Modeling, in: Estuar. Coast. Model., American Society of Civil Engineers, Reston, VA, 399–418. doi:10.1061/40876(209)23</ref><br />
! Digit 2: Advection in GWCE<ref name=Kendra2>K.M. Dresback, R.L. Kolar, J.C. Dietrich (2005). On the Form of the Momentum Equation for Shallow Water Models Based on the Generalized Wave Continuity Equation: Conservative vs. Non-Conservative. Advances in Water Resources, 28(4), 345-358. doi:10.1016/j.advwatres.2004.11.011</ref><br />
! Digit 3: Lateral Stress in Momentum<ref name=Kendra1></ref><br />
! Digit 4: Advection in Momentum<ref name=Kendra2></ref><br />
! Digit 5: Area Integration in Momentum<br />
! Digit 6: GWCE Mass Matrix, Barotropic/Baroclinic<br />
|-<br />
| 1 (default)<br />
| 2DDI, Kolar-Gray flux-based<br/><code>CGWCE_LS_KGQ=.TRUE.</code><br />
| Non conservative<br/><code>CGWCE_Advec_NC=.TRUE.</code><br />
| Integration by parts, velocity-based<br/><code>CME_LS_IBPV=.TRUE.</code><br />
| Non conservative<br/><code>CME_New_NC=.TRUE.</code><br />
| Corrected <br/><code>CME_AreaInt_Corr=.TRUE.</code><br />
| Consistent (implicit for linear part of gravity wave term), barotropic<br/><code>ILump=0</code><br />
|-<br />
| 2<br />
| 2DDI, 2-part flux-based<br/><code>CGWCE_LS_2PartQ=.TRUE.</code><br />
| Conservative form 1<br/><code>CGWCE_Advec_C1=.TRUE.</code><br />
| Integration by parts, flux-based<br/><code>CME_LS_IBPQ=.TRUE.</code><br />
| Conservative form 1<br/><code>CME_New_C1=.TRUE.</code><br />
| Original <br/><code>CME_AreaInt_Orig=.TRUE.</code><br />
| Lumped (explicit), barotropic<br/><code>CGWCE_Lump=.TRUE.</code>, <code>ILump=1</code><br />
|-<br />
| 3<br />
| 2DDI, 2-part velocity-based<br/><code>CGWCE_LS_2PartV=.TRUE.</code><br />
| Conservative form 2<br/><code>CGWCE_Advec_C2=.TRUE.</code><br />
| Integration by parts, velocity-based symmetrical<br/><code>CME_LS_IBPSV=.TRUE.</code><br />
| Conservative form 2<br/><code>CME_New_C2=.TRUE.</code><br />
| -<br />
| Consistent (implicit for full gravity wave term), barotropic<br/><code>CGWCE_HDP=.TRUE.</code>, <code>IFNL_HDP=1</code>, <code>ILump=0</code> {{ADC version|version=55|relation=eq}}<br />
|-<br />
| 4<br />
| 2DDI, 2-part flux-based symmetrical<br/><code>CGWCE_LS_2PartSQ=.TRUE.</code><br />
| -<br />
| Integration by parts, flux-based symmetrical<br/><code>CME_LS_IBPSQ=.TRUE.</code><br />
| -<br />
| -<br />
| Consistent (implicit for full gravity wave term, modified dispersion relation), barotropic<br/><code>CGWCE_HDP=.TRUE.</code>, <code>IFNL_HDP=1</code>, <code>ILump=0</code>, <code>CAliDisp=.TRUE.</code> {{ADC version|version=55|relation=eq}}<br />
|-<br />
| 5<br />
| 2DDI, 2-part velocity-based symmetrical<br/><code>CGWCE_LS_2PartSV=.TRUE.</code><br />
| -<br />
| 2 Part, velocity-based (''not implemented'')<br/><code>CME_LS_2PartV=.TRUE.</code><br />
| -<br />
| -<br />
| A value of 5-8 does the same as 1-4 (same order) but in baroclinic mode<br/><code>CBaroclinic=.TRUE.</code> {{ADC version|version=55|relation=eq}}<br />
|-<br />
| 6<br />
| 3D, Kolar-Gray flux-based<br/><code>C2DDI=.FALSE.</code>, <code>CGWCE_LS_KGQ=.TRUE.</code>, <code>C3D=.TRUE.</code>, <code>C3DVS=.TRUE.</code>, <code>ILump=0</code><br />
| -<br />
| 2 Part, flux-based (''not implemented'')<br/><code>CME_LS_2PartQ=.TRUE.</code><br />
| -<br />
| -<br />
| See above <br />
|}<br />
<br />
A common code combination is <code>IM=111112</code>, which is identical to the default <code>111111</code> (same as <code>IM=0</code>), but simulates in explicit mass-lumping mode. Note that <code>[[A00, B00, C00]]</code> must be set to <code>0.0 1.0 0.0</code> when in this mode. Lumped explicit mode is a useful alternative to the (default) semi-implicit consistent GWCE mass matrix mode, because the latter requires a matrix solve that increases computational time and memory. By comparison, the explicit mass-lumping mode is about twice as fast and scales to fewer grid nodes per computational core.<ref>S. Tanaka, S. Bunya, J.J. Westerink, C. Dawson, R.A. Luettich, Scalability of an Unstructured Grid Continuous Galerkin Based Hurricane Storm Surge Model, J. Sci. Comput. 46 (2011) 329–358. doi:10.1007/s10915-010-9402-1</ref> Moreover, for model setups that are sufficiently resolved in space and time, differences in the solution between approaches should be small. Though, many users have reported somewhat lower stability in lumped explicit mode. <br />
<br />
== References ==<br />
<references /></div>Taylorgasher