DIDAMINTQ - Revision history

Ak3glang: working group POS

2022-09-06T09:03:44Z

working group POS

← Older revision		Revision as of 09:03, 6 September 2022
Line 3:		Line 3:
	\|name=DIDAMINTQ		\|name=DIDAMINTQ
	\|version=4.x / December 2012		\|version=4.x / December 2012
	\|version_descr=~~December 2012~~		\|version_descr=September 2022
	\|catchwords=		\|catchwords=
	postprocessor<br />		postprocessor<br />
Line 106:		Line 106:
	\|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:susanne~~.~~spohr~~@baw.de ~~S. Spohr~~]		\|contact_maintenance=[mailto:pos.proghome@baw.de Working group POS]
	\|documentation=See also $PROGHOME/examples/DidaMintQ/.		\|documentation=See also $PROGHOME/examples/DidaMintQ/.

	Further useful informations concerning this program may be found in the article ''Integration und Mittelung auf Querschnitten'' (available in German only) published in [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/sc4-98a2.pdf No. 4/1998] of Supercomputing News.		Further useful informations concerning this program may be found in the article ''Integration und Mittelung auf Querschnitten'' (available in German only) published in [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/sc4-98a2.pdf No. 4/1998] of Supercomputing News.
	}}		}}

imported>Spohr Susanne: Version 4.x

2012-12-18T11:00:27Z

Version 4.x

← Older revision		Revision as of 11:00, 18 December 2012
Line 2:		Line 2:
	\|name_de=DIDAMINTQ		\|name_de=DIDAMINTQ
	\|name=DIDAMINTQ		\|name=DIDAMINTQ
	\|version=3.x / ~~April 2011~~		\|version=4.x / December 2012
	\|version_descr=~~April 2011~~		\|version_descr=December 2012
	\|catchwords=		\|catchwords=
	postprocessor<br />		postprocessor<br />
Line 31:		Line 31:
	:* settling velocity,		:* settling velocity,
	:* turbulent shear stress,		:* 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,
	:* bed load transport capacity,		:* bed load transport capacity,
Line 55:		Line 59:
	:** maximum depth at cross section.		:** 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:		To obtain meaningful results the user of the program DIDAMINTQ should take into account the following rules before starting his work:

imported>Lang Guenther: date and time adjusted for current program version

2011-04-07T11:08:07Z

date and time adjusted for current program version

← Older revision		Revision as of 11:08, 7 April 2011
Line 2:		Line 2:
	\|name_de=DIDAMINTQ		\|name_de=DIDAMINTQ
	\|name=DIDAMINTQ		\|name=DIDAMINTQ
	\|version=3.x / ~~October 2009~~		\|version=3.x / April 2011
	\|version_descr=~~October 2009~~		\|version_descr=April 2011
	\|catchwords=		\|catchwords=
	postprocessor<br />		postprocessor<br />

imported>Spohr Susanne at 07:42, 7 October 2010

2010-10-07T07:42:05Z

← Older revision		Revision as of 07:42, 7 October 2010
Line 55:		Line 55:
	:** maximum depth at cross section.		:** 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 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.

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

imported>Spohr Susanne at 07:37, 7 October 2010

2010-10-07T07:37:33Z

← Older revision		Revision as of 07:37, 7 October 2010
Line 91:		Line 91:
	Selected profiles can be optionally excluded from further processing.		Selected profiles can be optionally excluded from further processing.
	\|preprocessor=		\|preprocessor=
	[[DIDAMERGE]], [[DIDARENAME]], [[ENERF]], [[PGCALC]], [[POLWIND]], [[~~TELEMAC2D~~]], [[TRIM-2D]], [[TRIM-3D]], [[UNTRIM]], [[UNTRIM2007]], [[XTRLQ2]]		[[DIDAMERGE]], [[DIDARENAME]], [[ENERF]], [[PGCALC]], [[POLWIND]], [[TELEMAC-2D]], [[TRIM-2D]], [[TRIM-3D]], [[UNTRIM]], [[UNTRIM2007]], [[XTRLQ2]]
	\|postprocessor=		\|postprocessor=
	[[DIDAMERGE]], [[DIDARENAME]], [[GVIEW2D]], [[LQ2PRO]], [[XTRDATA]], [[ZEITR]]		[[DIDAMERGE]], [[DIDARENAME]], [[GVIEW2D]], [[LQ2PRO]], [[XTRDATA]], [[ZEITR]]

imported>BAWiki 1 at 11:50, 6 May 2010

2010-05-06T11:50:30Z

imported>BAWiki 1 at 11:07, 6 May 2010

2010-05-06T11:07:17Z

← Older revision		Revision as of 11:07, 6 May 2010
Line 100:		Line 100:
	\|documentation=See also $PROGHOME/examples/DidaMintQ/.		\|documentation=See also $PROGHOME/examples/DidaMintQ/.

	Further useful informations concerning this program may be found in the article Integration und Mittelung auf Querschnitten (available in German only) published in [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/sc4-98a2.pdf No. 4/1998] of Supercomputing News.		Further useful informations concerning this program may be found in the article ''Integration und Mittelung auf Querschnitten'' (available in German only) published in [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/sc4-98a2.pdf No. 4/1998] of Supercomputing News.
	}}		}}

imported>BAWiki 1 at 11:05, 6 May 2010

2010-05-06T11:05:22Z

← Older revision		Revision as of 11:05, 6 May 2010
Line 70:		Line 70:
	#: '''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.		#: '''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.
	\|outputfiles=		\|outputfiles=
	# '''modified profile-topography''' (filetype profil05.bin)		# '''modified profile-topography''' (filetype [[PROFIL05.BIN\|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.		#: '''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)		# '''integrated or averaged results along profiles''' (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])
	#: '''Notice''': the names of the output files are mainly identical with the input files but with leading prefix '''QP.'''.		#: '''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)		# (optional) '''structural lines and text informations''' (filetype [[INSEL.DAT\|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.		#: '''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)		# (optional) description of '''geopositions''' (filetype [[GEOPOS.DAT\|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).		#: '''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) informative '''printer''' file (filetype DidaMintQ.sdr)
	# (optional) '''trace''' of program execution (filetype DidaMintQ.trc)		# (optional) '''trace''' of program execution (filetype DidaMintQ.trc)
Line 91:		Line 91:
	Selected profiles can be optionally excluded from further processing.		Selected profiles can be optionally excluded from further processing.
	\|preprocessor=		\|preprocessor=
	DIDAMERGE, DIDARENAME, ENERF, PGCALC, POLWIND, TELEMAC2D, TRIM-2D, TRIM-3D, UNTRIM, UNTRIM2007, XTRLQ2		[[DIDAMERGE]], [[DIDARENAME]], [[ENERF]], [[PGCALC]], [[POLWIND]], [[TELEMAC2D]], [[TRIM-2D]], [[TRIM-3D]], [[UNTRIM]], [[UNTRIM2007]], [[XTRLQ2]]
	\|postprocessor=		\|postprocessor=
	DIDAMERGE, DIDARENAME, GVIEW2D, LQ2PRO, XTRDATA, ZEITR		[[DIDAMERGE]], [[DIDARENAME]], [[GVIEW2D]], [[LQ2PRO]], [[XTRDATA]], [[ZEITR]]
	\|language=Fortran90		\|language=Fortran90
	\|add_software= -		\|add_software= -
Line 100:		Line 100:
	\|documentation=See also $PROGHOME/examples/DidaMintQ/.		\|documentation=See also $PROGHOME/examples/DidaMintQ/.

	Further useful informations concerning this program may be found in the article Integration und Mittelung auf Querschnitten (available in German only) published in No. 4/1998 of Supercomputing News.		Further useful informations concerning this program may be found in the article Integration und Mittelung auf Querschnitten (available in German only) published in [http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/sc4-98a2.pdf No. 4/1998] of Supercomputing News.
	}}		}}

imported>BAWiki 1 at 10:58, 6 May 2010

2010-05-06T10:58:39Z

imported>BAWiki 1 at 10:50, 6 May 2010

2010-05-06T10:50:49Z

← Older revision		Revision as of 11:50, 6 May 2010
Line 13:		Line 13:
	universal direct access data format for profile data<br />		universal direct access data format for profile data<br />
	\|shortdescription=		\|shortdescription=
	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.		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:		Cross sectional averages/integrals are typically computed for one or more of the following physical quantities:
Line 57:		Line 57:
	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 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.

	To obtain meaningful results the user of the program ~~DidaMintQ~~ should take into account the following rules before starting his work:		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]]).		# 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]]).
Line 78:		Line 78:
	# (optional) description of '''geopositions''' (filetype [[GEOPOS.DAT\|geopos.dat]])		# (optional) description of '''geopositions''' (filetype [[GEOPOS.DAT\|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]]).		#: '''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) informative '''printer''' file (filetype didamintq.sdr)
	# (optional) '''trace''' of program execution (filetype ~~DidaMintQ~~.trc)		# (optional) '''trace''' of program execution (filetype didamintq.trc)
	\|methodology=		\|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.		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.

← Older revision		Revision as of 10:58, 6 May 2010
Line 55:		Line 55:
	:** maximum depth at cross section.		:** 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. 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 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.

	To obtain meaningful results the user of the program DidaMintQ should take into account the following rules before starting his work:		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).		# 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).		# 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.		# 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.		# Each cross-sectional profile should not have more than one intersection with a longitudinal profile.
	\|inputfiles=		\|inputfiles=
	# general '''input data''' (filetype ~~DidaMintQ~~.dat)		# general '''input data''' (filetype [[DIDAMINTQ.DAT\|didamintq.dat]])
	# '''profile-topography''' (filetype profil05.bin)		# '''profile-topography''' (filetype [[PROFIL05.BIN\|profil05.bin]])
	# '''synoptic data sets along profiles''' (files of type dirz.bin.R, dirz.bin.I and dirz.bin)		# '''synoptic data sets along profiles''' (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])
	# (optional) '''configuration file''' for rules of computation (filetype ~~DidaMintQ~~.cfg)		# (optional) '''configuration file''' for rules of computation (filetype [[DIDAMINTQ.CFG\|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.		#: '''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.
	\|outputfiles=		\|outputfiles=
	# '''modified profile-topography''' (filetype profil05.bin)		# '''modified profile-topography''' (filetype profil05.bin)

← Older revision		Revision as of 10:50, 6 May 2010
Line 71:		Line 71:
	\|outputfiles=		\|outputfiles=
	# '''modified profile-topography''' (filetype profil05.bin)		# '''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.		#: '''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)		# '''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'''..		#: '''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)		# (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.		#: '''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.
Line 85:		Line 85:
	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.		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.		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.		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.
Line 91:		Line 91:
	Selected profiles can be optionally excluded from further processing.		Selected profiles can be optionally excluded from further processing.
	\|preprocessor=		\|preprocessor=
	DIDAMERGE, ~~DiIDARENAME~~, ENERF, PGCALC, POLWIND, TELEMAC2D, TRIM-2D, TRIM-3D, UNTRIM, UNTRIM2007, XTRLQ2		DIDAMERGE, DIDARENAME, ENERF, PGCALC, POLWIND, TELEMAC2D, TRIM-2D, TRIM-3D, UNTRIM, UNTRIM2007, XTRLQ2
	\|postprocessor=		\|postprocessor=
	DIDAMERGE, DIDARENAME, GVIEW2D, LQ2PRO, XTRDATA, ZEITR		DIDAMERGE, DIDARENAME, GVIEW2D, LQ2PRO, XTRDATA, ZEITR