Actions

DIDASPLIT: Difference between revisions

From BAWiki

imported>BAWiki 1
(Created page with '{{ProgramDescription |name_de=DIDASPLIT |name=DIDASPLIT |version=V3.x / January 2001 |version_descr= September 2002 |catchwords= postprocessor<br /> finite element grid<br /> s…')
 
(working group POS)
 
(7 intermediate revisions by 2 users not shown)
Line 3: Line 3:
|name=DIDASPLIT
|name=DIDASPLIT
|version=V3.x / January 2001  
|version=V3.x / January 2001  
|version_descr= September 2002
|version_descr= September 2022
|catchwords=
|catchwords=
postprocessor<br />
postprocessor<br />
Line 14: Line 14:
analyses data<br />
analyses data<br />
|shortdescription=
|shortdescription=
The program DidaSplit is a postprocessor for different numerical models (e.g. TRIM-2D, TRIM-3D, TELEMAC-2D, UNTRIM etc.). DidaSplit was designed to split results and/or bathymetry which are stored in
The program DIDASPLIT is a postprocessor for different numerical models (e.g. TRIM-2D, TRIM-3D, TELEMAC-2D, UNTRIM etc.). DIDASPLIT was designed to split results and/or bathymetry which are stored in


:* BDF-formatted files (see BAW-Datenformat BDF, description of the BDF file format is available in German only), where processed data can be either 2D or 3D synoptic data, time-series data or results from data analyses, and/or
:* BDF-formatted files (see [[DIRZ.BIN|dirz.bin]], description of the BDF file format is available in German only), where processed data can be either 2D or 3D synoptic data, time-series data or results from data analyses, and/or
:* splitting of a finite element grid file with bathymetric data.  
:* splitting of a finite element grid file with bathymetric data.  


Line 26: Line 26:
For every subdomain (polygon or grid-cell) the corresponding data and/or topographic points are collected into a separate file in BDF-format or into a separate finite element grid file. If data given in BDF-format shall be splitted a grid file (for bathymetry) is generated for each subdomain in any case.
For every subdomain (polygon or grid-cell) the corresponding data and/or topographic points are collected into a separate file in BDF-format or into a separate finite element grid file. If data given in BDF-format shall be splitted a grid file (for bathymetry) is generated for each subdomain in any case.


During one application of DidaSplit several sorting areas as well as data files can be handled at the same time.
During '''one''' application of DIDASPLIT several sorting areas as well as data files can be handled at the same time.


Sorted results may be post processed in the same manner as this is the case for the overall original data set.  
Sorted results may be post processed in the same manner as this is the case for the overall original data set.  
|inputfiles=
|inputfiles=
# general input data (filetype DidaSplit.dat)
# general input data (filetype [[DIDASPLIT.DAT|didasplit.dat]])
# grid for the overall domain (filetype gitter05.dat/bin or filetype selafin or filetype untrim_grid.dat)
# grid for the overall domain (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]] or filetype [[SELAFIN|selafin]] or filetype [[UNTRIM_GRID.DAT|untrim_grid.dat]])
# (optional) original data for the overall domain (filetype dirz.bin.R, dirz.bin.I and dirz.bin)  
# (optional) original data for the overall domain (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])  
|outputfiles=
|outputfiles=
# grids for subdomains (filetype gitter05.dat/bin) Notice: if on input a grid file of type selafin or untrim_grid.dat was specified by the user on output the grid files for the subdomains will be automatically of type gitter05.dat/bin.
# grids for subdomains (filetype [[GITTER05.DAT and GITTER05.BIN|gitter05.dat/bin]])  
# (optional) data for subdomains (filetype dirz.bin.R, dirz.bin.I and dirz.bin)
#: '''Notice''': if on input a grid file of type selafin or untrim_grid.dat was specified by the user on output the grid files for the subdomains will be automatically of type gitter05.dat/bin.
# informative printer file (filetype DidaMerge.sdr)
# (optional) data for subdomains (filetype [[DIRZ.BIN.R|dirz.bin.r]], [[DIRZ.BIN.I|dirz.bin.i]] and [[DIRZ.BIN|dirz.bin]])
# (optional) trace of program execution (filetype DidaMerge.trc)
# informative printer file (filetype didamerge.sdr)
#: '''Notice''': In situations when DidaSplit was terminated before the normal end of the program was reached the job can be submitted again. Outputfiles for subdomains which are already present will not be generated a second time. Missing outputfiles will be newly generated. It is recommended to remove outputfiles from the working directory which have been generated immediately before abnormal program termination took place.  
# (optional) trace of program execution (filetype didamerge.trc)
#: '''Notice''': In situations when DIDASPLIT was terminated before the normal end of the program was reached the job can be submitted again. Outputfiles for subdomains which are already present will not be generated a second time. Missing outputfiles will be newly generated. It is recommended to remove outputfiles from the working directory which have been generated immediately before abnormal program termination took place.  
|methodology=
|methodology=
In dependence of the input data specified by the user a list of nodes which are lying inside or outside the subdomain of interest (specified as a polygon or grid-cell of a regular grid) is generated first. To this list some nodes may be added which do belong to triangles which have intersections with segments of the polygon defining the subdomain.
In dependence of the input data specified by the user a list of nodes which are lying inside or outside the subdomain of interest (specified as a polygon or grid-cell of a regular grid) is generated first. To this list some nodes may be added which do belong to triangles which have intersections with segments of the polygon defining the subdomain.
Line 44: Line 45:
From these points a new grid is generated for the subdomain which is stored subsequently in a file. Later all data sets which are belonging to the sorted nodes are copied into the output data file for the subdomain area if desired.  
From these points a new grid is generated for the subdomain which is stored subsequently in a file. Later all data sets which are belonging to the sorted nodes are copied into the output data file for the subdomain area if desired.  
|preprocessor=
|preprocessor=
DATACONVERT, DidaMerge, DidaMintZ, DidaRename, ENERF, FRQWF, LZKAF, LZKMF, LZKSF, LZKVF, LZKWF, METDIDA, PGCALC, TELEMAC2D, TM2DIDA, TR2DIDA, TR3DIDA, TDKLF, TDKSF, TDKVF, TDKWF, TRIM-2D, TRIM-3D, UNS, UNTRIM, VTDK, ZEITR
[[DATACONVERT]], [[DIDAMERGE]], [[DIDAMINTZ]], [[DIDARENAME]], [[ENERF]], [[FRQWF]], [[LZKAF]], [[LZKMF]], [[LZKSF]], [[LZKVF]], [[LZKWF]], [[METDIDA]], [[PGCALC]], [[TELEMAC-2D]], [[TM2DIDA]], [[TR2DIDA]], [[TR3DIDA]], [[TDKLF]], [[TDKSF]], [[TDKVF]], [[TDKWF]], [[TRIM-2D]], [[TRIM-3D]], [[UNS]], [[UNTRIM]], [[VTDK]], [[ZEITR]]
|postprocessor=
|postprocessor=
ABDF, DidaMerge, DidaMintZ, DidaRename, ENERF, FRQWF, GVIEW2D, HVIEW2D, IO_VOLUME, LZKAF, LZKMF, LZKSF, LZKVF, LZKWF, PGCALC, TDKLF, TDKSF, TDKVF, TDKWF, UNS, VTDK, XTRDATA, XTRLQ2, ZEITR
[[ABDF]], [[DIDAMERGE]], [[DIDAMINTZ]], [[DIDARENAME]], [[ENERF]], [[FRQWF]], [[GVIEW2D]], [[HVIEW2D]], [[IO_VOLUME]], [[LZKAF]], [[LZKMF]], [[LZKSF]], [[LZKVF]], [[LZKWF]], [[PGCALC]], [[TDKLF]], [[TDKSF]], [[TDKVF]], [[TDKWF]], [[UNS]], [[VTDK]], [[XTRDATA]], [[XTRLQ2]], [[ZEITR]]
|language=Fortran90
|language=Fortran90
|add_software= -  
|add_software= -  
|contact_original=[mailto:guenther.lang@baw.de G. Lang]
|contact_original=G. Lang
|contact_maintenance=[mailto:guenther.lang@baw.de G. Lang], [mailto:elisabeth.rudolph@baw.de E. Rudolph]
|contact_maintenance=[mailto:pos.proghome@baw.de Working group POS]
|documentation=
|documentation=
for template files see $PROGHOME/examples/DidaSplit/<br /><br />
for template files see $PROGHOME/examples/DidaSplit/<br /><br />
If you are going to display your DidaSplitted results using e.g. the program HVIEW2D you may profit from reading the article Das Skript SplitScript published in No. 3/1998 of Supercomputing News (available in German only) before proceeding with your work.  
If you are going to display your DidaSplitted results using e.g. the program [[HVIEW2D]] you may profit from reading the article Das Skript SplitScript published in No. 3/1998 of Supercomputing News (available in German only) before proceeding with your work.  
}}
}}

Latest revision as of 09:12, 6 September 2022

Basic Information

Name of Program

DIDASPLIT

Version-Date

V3.x / January 2001

Description-Date

September 2022

Catchwords

postprocessor
finite element grid
splitting of bathymetry (defined on a finite element grid)
splitting of data files (BDF-format) with respect to different spatial criteria
universal direct access format for 2D/3D-data
synoptic data
time-series data
analyses data

Short Description of Functionality

The program DIDASPLIT is a postprocessor for different numerical models (e.g. TRIM-2D, TRIM-3D, TELEMAC-2D, UNTRIM etc.). DIDASPLIT was designed to split results and/or bathymetry which are stored in

  • BDF-formatted files (see dirz.bin, description of the BDF file format is available in German only), where processed data can be either 2D or 3D synoptic data, time-series data or results from data analyses, and/or
  • splitting of a finite element grid file with bathymetric data.

The following criteria can be applied:

  1. sorting of data and/or topographic points which are either lying inside or outside an arbitrary polygon;
  2. sorting of data and/or topographic points which belong to a grid-cell of a regular raster grid.

For every subdomain (polygon or grid-cell) the corresponding data and/or topographic points are collected into a separate file in BDF-format or into a separate finite element grid file. If data given in BDF-format shall be splitted a grid file (for bathymetry) is generated for each subdomain in any case.

During one application of DIDASPLIT several sorting areas as well as data files can be handled at the same time.

Sorted results may be post processed in the same manner as this is the case for the overall original data set.

Input-Files

  1. general input data (filetype didasplit.dat)
  2. grid for the overall domain (filetype gitter05.dat/bin or filetype selafin or filetype untrim_grid.dat)
  3. (optional) original data for the overall domain (filetype dirz.bin.r, dirz.bin.i and dirz.bin)

Output-Files

  1. grids for subdomains (filetype gitter05.dat/bin)
    Notice: if on input a grid file of type selafin or untrim_grid.dat was specified by the user on output the grid files for the subdomains will be automatically of type gitter05.dat/bin.
  2. (optional) data for subdomains (filetype dirz.bin.r, dirz.bin.i and dirz.bin)
  3. informative printer file (filetype didamerge.sdr)
  4. (optional) trace of program execution (filetype didamerge.trc)
    Notice: In situations when DIDASPLIT was terminated before the normal end of the program was reached the job can be submitted again. Outputfiles for subdomains which are already present will not be generated a second time. Missing outputfiles will be newly generated. It is recommended to remove outputfiles from the working directory which have been generated immediately before abnormal program termination took place.

Methodology

In dependence of the input data specified by the user a list of nodes which are lying inside or outside the subdomain of interest (specified as a polygon or grid-cell of a regular grid) is generated first. To this list some nodes may be added which do belong to triangles which have intersections with segments of the polygon defining the subdomain.

From these points a new grid is generated for the subdomain which is stored subsequently in a file. Later all data sets which are belonging to the sorted nodes are copied into the output data file for the subdomain area if desired.

Program(s) to run before this Program

DATACONVERT, DIDAMERGE, DIDAMINTZ, DIDARENAME, ENERF, FRQWF, LZKAF, LZKMF, LZKSF, LZKVF, LZKWF, METDIDA, PGCALC, TELEMAC-2D, TM2DIDA, TR2DIDA, TR3DIDA, TDKLF, TDKSF, TDKVF, TDKWF, TRIM-2D, TRIM-3D, UNS, UNTRIM, VTDK, ZEITR

Program(s) to run after this Program

ABDF, DIDAMERGE, DIDAMINTZ, DIDARENAME, ENERF, FRQWF, GVIEW2D, HVIEW2D, IO_VOLUME, LZKAF, LZKMF, LZKSF, LZKVF, LZKWF, PGCALC, TDKLF, TDKSF, TDKVF, TDKWF, UNS, VTDK, XTRDATA, XTRLQ2, ZEITR

Additional Information

Language

Fortran90

Additional software

-

Original Version

G. Lang

Maintenance

Working group POS

Documentation/Literature

for template files see $PROGHOME/examples/DidaSplit/

If you are going to display your DidaSplitted results using e.g. the program HVIEW2D you may profit from reading the article Das Skript SplitScript published in No. 3/1998 of Supercomputing News (available in German only) before proceeding with your work.

back to Program Descriptions

Overview

Retrieved from "http://wiki.baw.de/en/index.php?title=DIDASPLIT&oldid=14864"