DIDAMINTQ: Difference between revisions

Revision as of 11:00, 18 December 2012

Basic Information

Name of Program

DIDAMINTQ

Version-Date

4.x / December 2012

Description-Date

December 2012

Catchwords

postprocessor
numerical integration of synoptic 2D/3D data sets along profiles
averaging of synoptic 2D/3D data sets along profiles
static (alternative) bathymetry
dynamic bathymetry (morphodynamics)
time varying system slope
universal direct access data format for profile data

Short Description of Functionality

The program DIDAMINTQ is a post processor which is able to treat data originating from different numerical models (e.g. TRIM-2D, TRIM-3D, TELEMAC-2D, UNTRIM or UNTRIM2007). It can be used for an automated integration and/or averaging of two- as well as three-dimensional synoptic data sets defined along profiles. Furthermore vector and scalar quantities may be recombined to form (new) flux quantities.

Cross sectional averages/integrals are typically computed for one or more of the following physical quantities:

water level elevation,
current velocity,
hydrodynamic pressure,
density,
salinity,
temperature,
suspended load (one or several fractions),
tracer (one or several fractions),
turbulent kinetic energy,
generic turbulent length scale,
vertical turbulent viscosity,
vertical turbulent diffusivity,
settling velocity,
turbulent shear stress,
adv. salt transport (depth integrated),
adv. heat transport (depth integrated),
adv. suspended load transport (depth integrated),
adv. tracer transport (depth integrated),
bed load transport,
bed load transport capacity,
bathymetry,
system slope,
specific energy (potential, mechanic, kinetic), and
dynamic pressure.

The following results can be obtained in general:

input quantity is a scalar quantity:
- average value along profile (e.g. mean water level elevation along profile);
- weighted (using water depth) average along profile (e.g. cross sectional average of salinity).
input quantity is a vector quantity:
- average value along profile for the component which is orthogonal to the profile (e.g. average current velocity orthogonal to a profile).
- integral along profiles (e.g. discharge through cross section);
input quantities are a scalar and a vector quantity:
- integral of the flux quantity defined by the two input quantities, flux of scalar quantity through cross section (e.g. advective salt transport)
for the water level elevation the following additional output quantities are calculated:
- cross section of the flow;
- wetted perimeter;
- hydraulic radius.
special treatment for time dependent bathymetry:
- maximum depth at cross section.

Connecting input and output quantities can be done in a flexible way by means of a configuration file of the type didamintq.cfg. But it must be remembered that for all input as well as output quantities valid definitions of the physical quantities used must be present in the various configuration files phydef.cfg.*.dat for physical quantities.
Notice: If the input data contains depth integrated quantities of transport, the program DIDAMINTQ reads the special configuration file DidaMintQ.2D.cfg. Otherwise the standard file DidaMintQ.cfg is used.
DidaMintQ is not able to handle depth integrated quantities of transport and three-dimensional input data in the same run.

To obtain meaningful results the user of the program DIDAMINTQ should take into account the following rules before starting his work:

A proper classification of profiles (longitudinal or cross-sectional) in the definition-stage of the profiles (in this respect please check input data for the programs TR2LQ2, TICLQ2 or XTRLQ2).
All (cross-) sectional profiles should have the same orientation (e.g. from the left bank to the right bank within an estuary); in this case it is guaranteed that if results for different profiles are compared the sign of the calculated results will allways have the same significance (e.g. positive for the flood current direction and negative for the ebb current direction).
It may be useful when a longitudinal profile which covers the relevant extent of the system is defined. This may be later used during presentation of results to demonstrate the variation of of the cross-sectional averaged/integrated results along the system.
Each cross-sectional profile should not have more than one intersection with a longitudinal profile.

Input-Files

general input data (filetype didamintq.dat)
profile-topography (filetype profil05.bin)
synoptic data sets along profiles (files of type dirz.bin.r, dirz.bin.i and dirz.bin)
(optional) configuration file for rules of computation (filetype didamintq.cfg)
Notice: If this type of file is not present in the local working directory the standard configuration file didamintq.cfg from directory $PROGHOME/cfg/ will be used.

Output-Files

modified profile-topography (filetype profil05.bin)
Notice: the name of the output file is mainly identical with the input file name having the leading prefix QP.. This file is in great parts identical to the input profile topography but less data points are contained. This is due to the fact that integral as well as averaged quantities are only stored for one single point along each profile (point with data). All other points do remain as points without data to keep the information about the bathymetry. Additional points may be also present if there exist intersections between cross sectional and longitudinal profiles.
integrated or averaged results along profiles (files of type dirz.bin.r, dirz.bin.i and dirz.bin)
Notice: the names of the output files are mainly identical with the input files but with leading prefix QP..
(optional) structural lines and text informations (filetype insel.dat)
Notice: this file contains the coordinates for all the profiles which have been taken into account during the calculation process. Furthermore the coordinates for one location along each profile (so called profile master point) are also stored together with a short name to identify the different profiles in use. Calculated data are normally stored at the profile master point.
(optional) description of geopositions (filetype geopos.dat)
Notice: these files do contain coordinates as well as short textual descriptions of the so called profile master points (see above). These informations may be useful in situations when data shall be extracted into ASCII-format (e.g. by means of the program XTRDATA) or during further data analysis (e.g. by means of program TDKWF).
(optional) informative printer file (filetype didamintq.sdr)
(optional) trace of program execution (filetype didamintq.trc)

Methodology

The cross sectional data are generated from synoptic data sets available along profiles by means of numerical integration over the cross section. In this step the data are assumed to be stepwise constant along the profile as well as into the vertical direction (one or several layers). The calculated result may therefore differ from the the result for an exact integration.

Meaningful results may be mainly obtained for profiles representing cross-sections. The program allows for exclusion of categories (longitudinal and cross-sectional) from data processing.

The following sign-rule is valid for vector quantities: Looking along the profile with flow from left to right means positive sign. The opposite is true when flow is going on from right to left. This rule may be overcome by prescribing specific input parameters in the steering file; from this possibility no intensive use should be made in general or (even better) not at all.

If longitudinal as well as cross sectional profiles are present intersections between profiles are calculated automatically if required. They are later inserted as additional points into the output topography. Intersections are also used as profile master points to store data resultiong from cross sectional averaging/integration. This facilitates the generation of longitudinal sections of cross sectional quantities considerabely.

Selected profiles can be optionally excluded from further processing.

Program(s) to run before this Program

DIDAMERGE, DIDARENAME, ENERF, PGCALC, POLWIND, TELEMAC-2D, TRIM-2D, TRIM-3D, UNTRIM, UNTRIM2007, XTRLQ2

Program(s) to run after this Program

DIDAMERGE, DIDARENAME, GVIEW2D, LQ2PRO, XTRDATA, ZEITR

Additional Information

Language

Fortran90

Additional software

-

Original Version

G. Lang

Maintenance

G. Lang, S. Spohr

@@ Line 2: / Line 2: @@
 |name_de=DIDAMINTQ
 |name=DIDAMINTQ
-|version=3.x / April 2011
+|version=4.x / December 2012
-|version_descr=April 2011
+|version_descr=December 2012
 |catchwords=
 postprocessor<br />
@@ Line 31: / Line 31: @@
 :* settling velocity,
 :* turbulent shear stress,
+:* adv. salt transport (depth integrated),
+:* adv. heat transport (depth integrated),
+:* adv. suspended load transport (depth integrated),
+:* adv. tracer transport (depth integrated),
 :* bed load transport,
 :* bed load transport capacity,
@@ Line 55: / Line 59: @@
 :** maximum depth at cross section.
-Connecting input and output quantities can be done in a flexible way by means of the configuration file [[DIDAMINTQ.CFG|didamintq.cfg]]. But it must be remembered that for all input as well as output quantities valid definitions of the physical quantities used must be present in the various configuration files '''phydef.cfg.*.dat''' for physical quantities.
+Connecting input and output quantities can be done in a flexible way by means of a configuration file of the type
+[[DIDAMINTQ.CFG|didamintq.cfg]]. But it must be remembered that for all input as well as output quantities
+valid definitions of the physical quantities used must be present in the various configuration files '''phydef.cfg.*.dat'''
+for physical quantities.<br />
+'''Notice''': If the input data contains depth integrated quantities of transport, the program DIDAMINTQ reads the special
+configuration file '''''DidaMintQ.2D.cfg'''''. Otherwise the standard file '''''DidaMintQ.cfg''''' is used.<br />
+DidaMintQ is not able to handle depth integrated quantities of transport and three-dimensional input data in the same run.
 To obtain meaningful results the user of the program DIDAMINTQ should take into account the following rules before starting his work: