Actions

Difference between revisions of "DIDAMERGE"

From BAWiki

imported>BAWiki 3
imported>BAWiki 3
m
 
(12 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
|version_descr=November 2005  
 
|version_descr=November 2005  
 
|catchwords=postprocessor<br />
 
|catchwords=postprocessor<br />
stationary data (one/several variants of a quantity)
+
stationary data (one/several variants of a quantity)<br />
synoptic data (one/several variants of a quantity)
+
synoptic data (one/several variants of a quantity)<br />
merging/thinning (in time) of different data sets
+
merging/thinning (in time) of different data sets<br />
universal direct access format for 2D/3D-data
+
universal direct access format for 2D/3D-data<br />
universal direct access format for profile-data
+
universal direct access format for profile-data<br />
universal direct access format for data at specific locations  
+
universal direct access format for data at specific locations
conversion of Delft3D computational results
+
|shortdescription=The program DIDAMERGE is a postprocessor for different numerical models (e.g. TRIM-2D, TRIM-3D, TELEMAC-2D, UNTRIM etc.). DIDAMERGE was designed to either merge or thin (in time) synoptic data sets of 2D or 3D scalar/vector data (stored in universal direct access format), which may also contain some stationary data sets.
|shortdescription=The program DidaMerge is a postprocessor for different numerical models (e.g. TRIM-2D, TRIM-3D, TELEMAC-2D, UNTRIM etc.). DidaMerge was designed to either merge or thin (in time) synoptic data sets of 2D or 3D scalar/vector data (stored in universal direct access format), which may also contain some stationary data sets.
 
  
 
If only one input data set is prescribed, this data set can be thinned (in time). If alternatively two data sets are prescribed, they can be merged and/or thinned (in time); both data sets must then be defined on the same computational grid and must also contain the same number and type of physical quantities. In the output file the desired data sets are stored in ascending order (in time). In case two input data sets are used only one set of stationary data from one input file will be transferred to the result file. The user can select from which input file stationary data shall be used.
 
If only one input data set is prescribed, this data set can be thinned (in time). If alternatively two data sets are prescribed, they can be merged and/or thinned (in time); both data sets must then be defined on the same computational grid and must also contain the same number and type of physical quantities. In the output file the desired data sets are stored in ascending order (in time). In case two input data sets are used only one set of stationary data from one input file will be transferred to the result file. The user can select from which input file stationary data shall be used.
 
|inputfiles=
 
|inputfiles=
# general input data (filetype [[DIDAMERGE.DAT|Didamerge.dat]])
+
# general input data (filetype [[DIDAMERGE.DAT|didamerge.dat]])
 
# synoptic input data set 1 with (optional) stationary data (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])
 
# synoptic input data set 1 with (optional) stationary data (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])
 
# (optional) synoptic input data set 2 with (optional) stationary data (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])
 
# (optional) synoptic input data set 2 with (optional) stationary data (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])
# grid for 2D/3D-data (filetype gitter05.dat/bin or filetype selafin or filetype [[UNTRIM_GRID.DAT|untrim_grid.dat]])
+
# grid for 2D/3D-data (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]] or filetype selafin or filetype [[UNTRIM_GRID.DAT|untrim_grid.dat]])
'''or''' profile-topography for profile-data (filetype [[PROFI105.BIN|profil05.bin]])
+
: '''or''' profile-topography for profile-data (filetype [[PROFIL05.BIN|profil05.bin]])
'''or''' system file for specific locations (filetype [[LOCATION_GRID.DAT|location_grid.dat]])  
+
: '''or''' system file for specific locations (filetype [[LOCATION_GRID.DAT|location_grid.dat]])  
 
|outputfiles=
 
|outputfiles=
 
# synoptic output data set 1+2 with (optional) stationary data (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]]  and [[DIRZ.BIN|dirz.bin]])
 
# synoptic output data set 1+2 with (optional) stationary data (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]]  and [[DIRZ.BIN|dirz.bin]])
# informative printer file (filetype [[DIDAMERGE.SDR|DidaMerge.sdr]])
+
# informative printer file (filetype didamerge.sdr)
# (optional) trace of program execution (filetype [[DIDAMERGE.TRC|DidaMerge.trc]])  
+
# (optional) trace of program execution (filetype didamerge.trc)  
 
|methodology=In dependance of the user specified input data a list for all desired output time steps is generated. The availability of the desired data sets is checked - each data set must be stored in one of the source files (input data set 1 or (optional) input data set 2). In addition a unique relationship between the time step and source file where this time step is stored is buildt up.
 
|methodology=In dependance of the user specified input data a list for all desired output time steps is generated. The availability of the desired data sets is checked - each data set must be stored in one of the source files (input data set 1 or (optional) input data set 2). In addition a unique relationship between the time step and source file where this time step is stored is buildt up.
  
 
Finally all data sets required for output are sorted into ascending order in time. The are read from the respective input data file and stored in the output data file immediately afterwards. Merging and thinning (in time) is perfomed according to the user specified input data.
 
Finally all data sets required for output are sorted into ascending order in time. The are read from the respective input data file and stored in the output data file immediately afterwards. Merging and thinning (in time) is perfomed according to the user specified input data.
 
As far as stationary data are contained in the input data files, only one file will be used as data source for stationaray data output, whereas the data stored in the second file are simply neglected.  
 
As far as stationary data are contained in the input data files, only one file will be used as data source for stationaray data output, whereas the data stored in the second file are simply neglected.  
|preprocessor=[[DATACONVERT]], [[DIDAMINTQ]], [[DIDARENAME]], [[DIDASPLIT]], [[TELEMAC2D]], [[TM2DIDA]], [[TR2DIDA]], [[TR3DIDA]], [[TR2GEOM]], [[TRIM-2D]], [[TRIM-3D]], [[UNS]], [[UNTRIM]], [[VTDK]], [[XTRLQ2]], .  
+
|preprocessor=[[DATACONVERT]], [[DIDAMINTQ]], [[DIDARENAME]], [[DIDASPLIT]], [[TELEMAC-2D]], [[TM2DIDA]], [[TR2DIDA]], [[TR3DIDA]], [[TR2GEOM]], [[TRIM-2D]], [[TRIM-3D]], [[UNS]], [[UNTRIM]], [[VTDK]], [[XTRLQ2]], .  
|postprocessor=[[ADCP2PROFILE]], [[DIDAMINTQ]], [[DidaRename]], [[DIDASPLIT]], [[GVIEW2D]], [[HVIEW2D]], [[LQ2PRO]], [[UNS]], [[TIMESHIFT, [[VTDK, [[VVIEW2D, [[ZEITR]]
+
|postprocessor=[[ADCP2PROFILE]], [[DIDAMINTQ]], [[DIDARENAME]], [[DIDASPLIT]], [[GVIEW2D]], [[HVIEW2D]], [[LQ2PRO]], [[UNS]], [[TIMESHIFT]], [[VTDK]], [[VVIEW2D]], [[ZEITR]]
 
|language=Fortran90  
 
|language=Fortran90  
 
|add_software=-  
 
|add_software=-  
 
|contact_original=[mailto:günther.lang@baw.de G. Lang]
 
|contact_original=[mailto:günther.lang@baw.de G. Lang]
|contact_maintenance=[mailto:günther.lang@baw.de G. Lang,], [mailto:susanne.spohr@baw.de S. Spohr,]
+
|contact_maintenance=[mailto:günther.lang@baw.de G. Lang], [mailto:susanne.spohr@baw.de S. Spohr,]
|documentation=please refer to $PROGHOME/fortran/examples/DidaMerge/
+
|documentation=please refer to $PROGHOME/fortran/examples/DIDAMERGE/
  
 
}}
 
}}

Latest revision as of 08:46, 2 June 2010

Basic Information

Name of Program

DIDAMERGE

Version-Date

4.x / November 2005

Description-Date

November 2005

Catchwords

postprocessor
stationary data (one/several variants of a quantity)
synoptic data (one/several variants of a quantity)
merging/thinning (in time) of different data sets
universal direct access format for 2D/3D-data
universal direct access format for profile-data
universal direct access format for data at specific locations

Short Description of Functionality

The program DIDAMERGE is a postprocessor for different numerical models (e.g. TRIM-2D, TRIM-3D, TELEMAC-2D, UNTRIM etc.). DIDAMERGE was designed to either merge or thin (in time) synoptic data sets of 2D or 3D scalar/vector data (stored in universal direct access format), which may also contain some stationary data sets.

If only one input data set is prescribed, this data set can be thinned (in time). If alternatively two data sets are prescribed, they can be merged and/or thinned (in time); both data sets must then be defined on the same computational grid and must also contain the same number and type of physical quantities. In the output file the desired data sets are stored in ascending order (in time). In case two input data sets are used only one set of stationary data from one input file will be transferred to the result file. The user can select from which input file stationary data shall be used.

Input-Files

  1. general input data (filetype didamerge.dat)
  2. synoptic input data set 1 with (optional) stationary data (filetype dirz.bin.r, dirz.bin.i and dirz.bin)
  3. (optional) synoptic input data set 2 with (optional) stationary data (filetype dirz.bin.r, dirz.bin.i and dirz.bin)
  4. grid for 2D/3D-data (filetype gitter05.dat/bin or filetype selafin or filetype untrim_grid.dat)
or profile-topography for profile-data (filetype profil05.bin)
or system file for specific locations (filetype location_grid.dat)

Output-Files

  1. synoptic output data set 1+2 with (optional) stationary data (filetype dirz.bin.r, dirz.bin.i and dirz.bin)
  2. informative printer file (filetype didamerge.sdr)
  3. (optional) trace of program execution (filetype didamerge.trc)

Methodology

In dependance of the user specified input data a list for all desired output time steps is generated. The availability of the desired data sets is checked - each data set must be stored in one of the source files (input data set 1 or (optional) input data set 2). In addition a unique relationship between the time step and source file where this time step is stored is buildt up.

Finally all data sets required for output are sorted into ascending order in time. The are read from the respective input data file and stored in the output data file immediately afterwards. Merging and thinning (in time) is perfomed according to the user specified input data. As far as stationary data are contained in the input data files, only one file will be used as data source for stationaray data output, whereas the data stored in the second file are simply neglected.

Program(s) to run before this Program

DATACONVERT, DIDAMINTQ, DIDARENAME, DIDASPLIT, TELEMAC-2D, TM2DIDA, TR2DIDA, TR3DIDA, TR2GEOM, TRIM-2D, TRIM-3D, UNS, UNTRIM, VTDK, XTRLQ2, .

Program(s) to run after this Program

ADCP2PROFILE, DIDAMINTQ, DIDARENAME, DIDASPLIT, GVIEW2D, HVIEW2D, LQ2PRO, UNS, TIMESHIFT, VTDK, VVIEW2D, ZEITR

Additional Information

Language

Fortran90

Additional software

-

Original Version

G. Lang

Maintenance

G. Lang, S. Spohr,

Documentation/Literature

please refer to $PROGHOME/fortran/examples/DIDAMERGE/


back to Program Descriptions


Overview