UNK.DAT

Basic Information

File-Type

unk.dat

File-Form

FORMATTED

Version

September 2019

Description-Date

February 2018

Significance of the File

contains specific input data related to the post processor program UnK (unstructured k-model).

File-Contents (in Catchwords)

1. block Input_Files, with different information concerning required as well as optional input files:
   1. key "Grid_File" with name and type (GITTER05, UNTRIM_BAW) for the file with the computational grid (filetype untrim_grid.dat or gitter05.dat/bin).
   2. Key "Wind_Speed_File" with name and type (BDF or NETCDF) plus a (optional) maximum interpolation radius in case wind data are defined on an irregular grid for the file with space- and time-dependent wind speed above the computational domain (filetypes dirz.bin.r, dirz.bin.i and dirz.bin or cf-netcdf.nc). Remarks:
      • regular grid data: this file must be created using program METDIDA or UNTRIM2007. The grid must be regular, which means that it must possess constant grid size DX in x direction as well as constant grid size DY in y direction. DX and DY may differ.
      • irregular grid data: UNK automatically converts wind data onto a regular grid. In case no (optional) maximum interpolation radius is prescribed by the user UNK tries to compute a reasonable one automatically.
   3. Key "K_Model_Steering_File" mit Name und Typ (STEERING) der Datei mit den Eingabesteuerdaten für das Softwarepaket K_Model (Datei des Typs k_model.dat).

      Notice: this file must have been generated beforehand using program METDIDA.

   4. Key "K_Model_Steering_File" with name and type (STEERING) for the file with input data of the software package k_model (filetype k_model.dat).
   5. (optional) key "Water_Level_File" with space- and time-dependent water level within the computational domain.In case BDF use dirz.bin.r, dirz.bin.i and dirz.bin, or cf-netcdf.nc (NETCDF) otherwise plus (optional) maximum interpolation radius.

      Notice: For case BDF water level data must be available for the computational grid prescribed in key "Grid_File".

   6. (optional) key "Current_Velocity_File" with space- and time-dependent depth-averaged current velocity within the computational domain. In case BDF use dirz.bin.r, dirz.bin.i and dirz.bin, or cf-netcdf.nc (NETCDF) otherwise plus (optional) maximum interpolation radius.

      Notice 1: For case BDF current velocity data must be available for the computational grid prescribed in key "Grid_File";

      Notice 2: For case NETCDF file must be identical with "Water_Level_File".

   7. (optional) key "Bathymetry_Depth_File" with alternative or dynamic bathymetry depths within the computational domain. In case BDF use dirz.bin.r, dirz.bin.i and dirz.bin, or cf-netcdf.nc (NETCDF) otherwise plus (optional) maximum interpolation radius.

      Notice 1: For case BDF bathymetry depth data must be available for the computational grid prescribed in key "Grid_File".

      Notice 2: For case BDF the type of bathymetry depths must be consistent with the water level and velocity files; e.g. all files have alternative bathymetry depths;

      Notice 2: For case NETCDF file must be identical with "Water_Level_File".

2. block Simulation_Times with information for the simulation period:
   1. key "Start_Time" with start time given as DD.MM.YYYY-hh:mm:ss.nnnnnnnnn.
   2. key "End_Time" with end time given as DD.MM.YYYY-hh:mm:ss.nnnnnnnnn.

Notice:

• dictionary-file unk_dico.dat, usually present in directory $PROGHOME/dic/, will be automatically read by the application program in addition to the user-specified input file.

Programs using this Type of File

UNK

Example-File

please refer to $PROGHOME/examples/unk/unk.dat
and $PROGHOME/examples/unk/BSP_dynamic_bathymetry/unk.10min.dat

---

back to: File Descriptions

---

Overview