Inundation data output file (initiallydry.63)

The initiallydry.63 file was created as the foundation of inundation output data by specifying the areas that ADCIRC considers wet and dry upon cold start. Those areas that are initially dry can then be considered as inundated areas when they become wet.

When the inundationOutput parameter is set to .true. in the optional inundationOutputContol namelist at the bottom of the fort.15 file, the initiallydry.63 file will be written at the beginning of the simulation whether the run is a cold start or hot start. The nodal values in the initiallydry.63 file are 1 if a node is dry at cold start, and 0 if the node is wet at coldstart. The data in the initiallydry.63 file represent areas that are dry at cold start, even if the run that produced the initiallydry.63 file was hotstarted.

The wet/dry state in the initiallydry.63 file takes into account the initial_river_elevation nodal attribute, the surface_submergence_state nodal attribute, and the sea_surface_height_above_geoid nodal attribute from the nodal attributes (fort.13) file, as well as the bathymetric depth from the mesh (fort.14) file. It also includes the results of the landlocking algorithm, which dries any wet nodes that are completely surrounded by dry nodes. It does not include the effect of any tidal, meteorological, river, or other forcing.

The basic file structure is shown below. Each line of output is represented by a line containing the output variable name(s) in bold face type. Blank lines are to enhance readability. Loops indicate multiple lines of output. Definitions of each variable are provided via hot links.

Output may be in ascii or netCDF format depending on how NOUTGE is set in the Model Parameter and Periodic Boundary Condition (fort.15) File.

RUNDES, RUNID, AGRID

1, NP, DTDP*NSPOOLGE, NSPOOLGE, IRTYPE

TIME, IT

for k=1,NP

k, initiallydry(k)

end k loop

Note:

The initiallydry.63 is written at the very beginning of a simulation run, before timestepping begins.