UTRRND - Revision history

Ak3gseis at 07:53, 11 October 2022

2022-10-11T07:53:37Z

← Older revision		Revision as of 07:53, 11 October 2022
Line 111:		Line 111:
	\|language=Fortran95		\|language=Fortran95
	\|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:jens~~.~~juerges~~@baw.de ~~J. Jürges], [mailto:guntram.seiss@baw.de G. Seiß~~]		\|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
	\|documentation=		\|documentation=
	* please refer to $PROGHOME/examples/utrrnd/		* please refer to $PROGHOME/examples/utrrnd/

Ak3gseis: changes version 2022_02_23

2022-02-23T16:16:30Z

changes version 2022_02_23

← Older revision		Revision as of 16:16, 23 February 2022
Line 2:		Line 2:
	\|name_de=UTRRND		\|name_de=UTRRND
	\|name=UTRRND		\|name=UTRRND
	\|version=7.x / ~~September 2015~~		\|version=7.x / February 2022
	\|version_descr=~~September 2015~~		\|version_descr=February 2022
	\|catchwords=		\|catchwords=
	preprocessor<br />		preprocessor<br />
Line 95:		Line 95:
	** If measured data form the basis for interpolation of boundary time series data they will be interpolated to the location of the boundary node or grid cell in an analogous manner as described above for computational result based data.		** If measured data form the basis for interpolation of boundary time series data they will be interpolated to the location of the boundary node or grid cell in an analogous manner as described above for computational result based data.
	** An important difference exists for the generation of boundary time series data of water level elevation. In this situation an analysis to determine times of high and low water is carried through beforehand to determine the time shifts which are applied to the measured data before they are going to be interpolated to obtain a boundary time serie of water level elevation. This type of interpolation (time shift) can be optionally switched off in case the data to be interpolated are not dominated by the tides.		** An important difference exists for the generation of boundary time series data of water level elevation. In this situation an analysis to determine times of high and low water is carried through beforehand to determine the time shifts which are applied to the measured data before they are going to be interpolated to obtain a boundary time serie of water level elevation. This type of interpolation (time shift) can be optionally switched off in case the data to be interpolated are not dominated by the tides.

			'''commandline mode:
			'''

			The interactive requests can be avoided by using the commandline mode.

			Help about this mode: '''''utrrnd[.i18] --help''''' !



	\|preprocessor=		\|preprocessor=
	[[EXKNO]], [[FFT]], [[FRQ2ZEITR]], [[MESKOR]], [[TSCALC]], [[UTRPRE]], [[ZEITR]], [[ZEITRIO]]		[[EXKNO]], [[FFT]], [[FRQ2ZEITR]], [[MESKOR]], [[TSCALC]], [[UTRPRE]], [[ZEITR]], [[ZEITRIO]]

imported>Seiss Guntram: Support of EPSG codes in input data

2015-09-28T13:43:15Z

Support of EPSG codes in input data

← Older revision		Revision as of 13:43, 28 September 2015
Line 2:		Line 2:
	\|name_de=UTRRND		\|name_de=UTRRND
	\|name=UTRRND		\|name=UTRRND
	\|version=7.x / ~~May~~ 2015		\|version=7.x / September 2015
	\|version_descr=~~May~~ 2015		\|version_descr=September 2015
	\|catchwords=		\|catchwords=
	preprocessor<br />		preprocessor<br />
Line 66:		Line 66:
	## (optional) '''definition of boundary sections''' - can be used together with all types of numerical models (filetype [[BSECTION.DAT\|bsection.dat]]).		## (optional) '''definition of boundary sections''' - can be used together with all types of numerical models (filetype [[BSECTION.DAT\|bsection.dat]]).
	#: These informations may be useful when boundary data time series are going to be generated for water level elevation, salinity and temperature. For sources and sinks this information is not even useful.		#: These informations may be useful when boundary data time series are going to be generated for water level elevation, salinity and temperature. For sources and sinks this information is not even useful.

			'''Support of coordinate reference systems :'''
			# Files containing coordinate Information of type boewrt.dat, gitter05.dat/bin and untrim_grid.dat will be transformed into the sytem specified by BAWCRS during the reading process, if they contain a supported CRS internally as EPSG code. Use of BAWCRS leads to an export of the (valid) EPSG code into the boundary grid file. Further remarks are foud on page GEOTRANSFORMER.
			# The use of BAWCRS is recommended, especially, if meteorological input data from NetCDF files are used during a model run.
			# Nevertheless, the user shall add the EPSG code to the input data in all cases .

	Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).		Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).

imported>Seiss Guntram: Remark on EPSG codes in output system files

2015-05-22T13:08:38Z

Remark on EPSG codes in output system files

← Older revision		Revision as of 13:08, 22 May 2015
Line 2:		Line 2:
	\|name_de=UTRRND		\|name_de=UTRRND
	\|name=UTRRND		\|name=UTRRND
	\|version=7.x / ~~August 2008~~		\|version=7.x / May 2015
	\|version_descr=~~October 2014~~		\|version_descr=May 2015
	\|catchwords=		\|catchwords=
	preprocessor<br />		preprocessor<br />
Line 69:		Line 69:
	Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).		Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).
	\|outputfiles=		\|outputfiles=
	# '''~~systemfile~~ with locations''' of the nodes or cells where boundary time series data were generated (filetype [[LOCATION_GRID.DAT\|location_grid.dat]]);		# '''systemfiles with locations''' of the nodes or cells where boundary time series data were generated (filetype [[LOCATION_GRID.DAT\|location_grid.dat]]); the system files will contain the user specified coordinate reference System (CRS), if the Environment variable '''BAWCRS''' is set to a valid EPSG code value. Valid EPSG codes are described on the page [[GEOTRANSFORMER]].
	# '''synoptic boundary data''' for all boundary data locations (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])		# '''synoptic boundary data''' for all boundary data locations (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])
	#: Remark: these result files are especially useful in connexion with the application of the numerical model UNTRIM.		#: Remark: these result files are especially useful in connexion with the application of the numerical model UNTRIM.
Line 94:		Line 94:
	\|postprocessor=		\|postprocessor=
	[[FDGITTER05]], [[GVIEW2D]], [[TM2RND]], [[TR2RND]], [[UNTRIM]], [[UNTRIM2]], [[UNTRIM2007]], [[ZEITR]]		[[FDGITTER05]], [[GVIEW2D]], [[TM2RND]], [[TR2RND]], [[UNTRIM]], [[UNTRIM2]], [[UNTRIM2007]], [[ZEITR]]
	\|language=~~Fortran90~~		\|language=Fortran95
	\|add_software= -		\|add_software= -
	\|contact_original=[mailto:guenther.lang@baw.de G. Lang]		\|contact_original=[mailto:guenther.lang@baw.de G. Lang]
	\|contact_maintenance=[mailto:guenther.lang@baw.de G. Lang]		\|contact_maintenance=[mailto:guenther.lang@baw.de G. Lang], [mailto:jens.juerges@baw.de J. Jürges], [mailto:guntram.seiss@baw.de G. Seiß]
	\|documentation=		\|documentation=
	* please refer to $PROGHOME/examples/utrrnd/		* please refer to $PROGHOME/examples/utrrnd/

imported>Seiss Guntram: additional link

2014-10-21T11:34:09Z

additional link

← Older revision		Revision as of 11:34, 21 October 2014
Line 3:		Line 3:
	\|name=UTRRND		\|name=UTRRND
	\|version=7.x / August 2008		\|version=7.x / August 2008
	\|version_descr=~~December 2010~~		\|version_descr=October 2014
	\|catchwords=		\|catchwords=
	preprocessor<br />		preprocessor<br />
Line 108:		Line 108:
	** '''./BSP_becken_power_plant/''' : example files for a closed basin with one sink, where the water is immediately re-introduced at a different location with respective alteration of temperature as well as salinity (useful for simulations of the cooling of a power plant).		** '''./BSP_becken_power_plant/''' : example files for a closed basin with one sink, where the water is immediately re-introduced at a different location with respective alteration of temperature as well as salinity (useful for simulations of the cooling of a power plant).
	* there are also more general informations concerning the [[Generation of Boundary Conditions\|generation of boundary conditions]] available		* there are also more general informations concerning the [[Generation of Boundary Conditions\|generation of boundary conditions]] available
	* especially have a look to the graphical representation for the [[Generation of Boundary Conditions#Graphical Representations of Complex Workflows\|generation of time series data from measured or simulated data]]		* especially have a look to the [[Generation of Boundary Conditions#Literature about methods\|literature list]] and the graphical representation for the [[Generation of Boundary Conditions#Graphical Representations of Complex Workflows\|generation of time series data from measured or simulated data]]
	}}		}}

imported>Lang Guenther: UNTRIM2 added, link to UTRPRE

2010-12-17T14:06:25Z

UNTRIM2 added, link to UTRPRE

← Older revision		Revision as of 14:06, 17 December 2010
Line 14:		Line 14:
	numerical model TRIM-3D<br />		numerical model TRIM-3D<br />
	numerical model UNTRIM<br />		numerical model UNTRIM<br />
			numerical model UNTRIM2 (sub grid)<br />
	\|shortdescription=		\|shortdescription=
	Program UTRRND is used as a preprocessor to generate boundary time-series data for the different numerical models applied at BAW. The following services are provided by this program:		Program UTRRND is used as a preprocessor to generate boundary time-series data for the different numerical models applied at BAW. The following services are provided by this program:
Line 90:		Line 91:
	** An important difference exists for the generation of boundary time series data of water level elevation. In this situation an analysis to determine times of high and low water is carried through beforehand to determine the time shifts which are applied to the measured data before they are going to be interpolated to obtain a boundary time serie of water level elevation. This type of interpolation (time shift) can be optionally switched off in case the data to be interpolated are not dominated by the tides.		** An important difference exists for the generation of boundary time series data of water level elevation. In this situation an analysis to determine times of high and low water is carried through beforehand to determine the time shifts which are applied to the measured data before they are going to be interpolated to obtain a boundary time serie of water level elevation. This type of interpolation (time shift) can be optionally switched off in case the data to be interpolated are not dominated by the tides.
	\|preprocessor=		\|preprocessor=
	[[EXKNO]], [[FFT]], [[FRQ2ZEITR]], [[MESKOR]], [[TSCALC]], [[ZEITR]], [[ZEITRIO]]		[[EXKNO]], [[FFT]], [[FRQ2ZEITR]], [[MESKOR]], [[TSCALC]], [[UTRPRE]], [[ZEITR]], [[ZEITRIO]]
	\|postprocessor=		\|postprocessor=
	[[FDGITTER05]], [[GVIEW2D]], [[TM2RND]], [[TR2RND]], [[UNTRIM]], [[UNTRIM2]], [[UNTRIM2007]], [[ZEITR]]		[[FDGITTER05]], [[GVIEW2D]], [[TM2RND]], [[TR2RND]], [[UNTRIM]], [[UNTRIM2]], [[UNTRIM2007]], [[ZEITR]]

imported>Lang Guenther: link UNTRIM2

2010-12-16T12:32:31Z

link UNTRIM2

← Older revision		Revision as of 12:32, 16 December 2010
Line 3:		Line 3:
	\|name=UTRRND		\|name=UTRRND
	\|version=7.x / August 2008		\|version=7.x / August 2008
	\|version_descr=~~September 2008~~		\|version_descr=December 2010
	\|catchwords=		\|catchwords=
	preprocessor<br />		preprocessor<br />
Line 92:		Line 92:
	[[EXKNO]], [[FFT]], [[FRQ2ZEITR]], [[MESKOR]], [[TSCALC]], [[ZEITR]], [[ZEITRIO]]		[[EXKNO]], [[FFT]], [[FRQ2ZEITR]], [[MESKOR]], [[TSCALC]], [[ZEITR]], [[ZEITRIO]]
	\|postprocessor=		\|postprocessor=
	[[FDGITTER05]], [[GVIEW2D]], [[TM2RND]], [[TR2RND]], [[UNTRIM]], [[UNTRIM2007]], [[ZEITR]]		[[FDGITTER05]], [[GVIEW2D]], [[TM2RND]], [[TR2RND]], [[UNTRIM]], [[UNTRIM2]], [[UNTRIM2007]], [[ZEITR]]
	\|language=Fortran90		\|language=Fortran90
	\|add_software= -		\|add_software= -

imported>BAWiki 1 at 12:20, 24 June 2010

2010-06-24T12:20:38Z

← Older revision		Revision as of 12:20, 24 June 2010
Line 106:		Line 106:
	** '''./BSP_soliton /''' : propagation of a solitary wave in a straight wave channel.		** '''./BSP_soliton /''' : propagation of a solitary wave in a straight wave channel.
	** '''./BSP_becken_power_plant/''' : example files for a closed basin with one sink, where the water is immediately re-introduced at a different location with respective alteration of temperature as well as salinity (useful for simulations of the cooling of a power plant).		** '''./BSP_becken_power_plant/''' : example files for a closed basin with one sink, where the water is immediately re-introduced at a different location with respective alteration of temperature as well as salinity (useful for simulations of the cooling of a power plant).
	* there are also more general informations concerning the generation of boundary conditions available		* there are also more general informations concerning the [[Generation of Boundary Conditions\|generation of boundary conditions]] available
	* especially have a look to the graphical representation for the generation of time series data from measured or simulated data		* especially have a look to the graphical representation for the [[Generation of Boundary Conditions#Graphical Representations of Complex Workflows\|generation of time series data from measured or simulated data]]
	}}		}}

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

2010-05-26T11:07:06Z

imported>BAWiki 1 at 11:02, 26 May 2010

2010-05-26T11:02:45Z

← Older revision		Revision as of 11:07, 26 May 2010
Line 47:		Line 47:
	Time series data for sources and sinks are exclusively generated for the specific location given by the user.		Time series data for sources and sinks are exclusively generated for the specific location given by the user.
	\|inputfiles=		\|inputfiles=
	# general input data (filetype [[UTRRND.DAT\|utrrnd.dat]]).		# '''general input data''' (filetype [[UTRRND.DAT\|utrrnd.dat]]).
	# grid with boundary nodes or boundary grid cells for which boundary time series data shall be generated or which describes the modelling domain for which sources and sinks are going to be generated:		# '''grid''' with boundary nodes or boundary grid cells for which boundary time series data shall be generated or which describes the modelling domain for which sources and sinks are going to be generated:
	#: for [[Mathematical Model TELEMAC-2D\|TELEMAC-2D]] - filetype [[~~GIITER05~~.DAT and GITTER05.BIN\|gitter05.dat/bin]]		#: for [[Mathematical Model TELEMAC-2D\|TELEMAC-2D]] - filetype [[GITTER05.DAT and GITTER05.BIN\|gitter05.dat/bin]]
	#: or		#: '''or'''
	#: for [[Mathematical Model TRIM-2D\|TRIM-2D]] and [[Mathematical Model TRIM-3D\|TRIM-3D]] - filetype [[TR2.TOPO.BIN.IND\|tr2.topo.bin.ind]]		#: for [[Mathematical Model TRIM-2D\|TRIM-2D]] and [[Mathematical Model TRIM-3D\|TRIM-3D]] - filetype [[TR2.TOPO.BIN.IND\|tr2.topo.bin.ind]]
	#: or		#: '''or'''
	#: for UNTRIM - filetype [[UNTRIM_GRID.DAT\|untrim_grid.dat]]		#: for UNTRIM - filetype [[UNTRIM_GRID.DAT\|untrim_grid.dat]]
	# (optional) description of the vertical structure, e.g. the position of layers, when three-dimensional boundary time series data shall be generated for the numerical model UNTRIM (filetype [[VERTICAL.DAT\|vertical.dat]]) This information is only of importance in connexion with the computation of salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions), along open boundaries or sources and sinks inside the modelling domain.		# (optional) description of the '''vertical structure''', e.g. the position of layers, when three-dimensional boundary time series data shall be generated for the numerical model UNTRIM (filetype [[VERTICAL.DAT\|vertical.dat]]) This information is only of importance in connexion with the computation of salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions), along open boundaries or sources and sinks inside the modelling domain.
	# (optional) if 2D-/3D-results of a previous numerical simulation shall be used:		# (optional) if 2D-/3D-'''results of a previous numerical simulation''' shall be used:
	## grid (filetype [[GITTER05.DAT and GITTER05.BIN\|gitter05.dat/bin]] or [[UNTRIM_GRID.DAT\|untrim_grid.dat]] or [[PROFIL05.BIN\|profil05.bin]] or [[LOCATION_GRID.DAT\|location_grid.dat]])		## '''grid''' (filetype [[GITTER05.DAT and GITTER05.BIN\|gitter05.dat/bin]] '''or''' [[UNTRIM_GRID.DAT\|untrim_grid.dat]] '''or''' [[PROFIL05.BIN\|profil05.bin]] '''or''' [[LOCATION_GRID.DAT\|location_grid.dat]])
	## computed time series data (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])		## '''computed time series data''' (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])
	## (optional) manually prescribed time series for modification of mean value, amplitude and phase of the time series derived from numerically calculated results (files of type [[BOEWRT.DAT\|boewrt.dat]])		## (optional) manually prescribed '''time series for modification''' of mean value, amplitude and phase of the time series derived from numerically calculated results (files of type [[BOEWRT.DAT\|boewrt.dat]])
	#: This functionality is currently only available in connexion with water level elevation boundary data time series.		#: This functionality is currently only available in connexion with water level elevation boundary data time series.
	# (optional) if measured data shall be used to generate the boundary time series data (files of type [[BOEWRT.DAT\|boewrt.dat]])		# (optional) if '''measured data''' shall be used to generate the boundary time series data (files of type [[BOEWRT.DAT\|boewrt.dat]])
	# (optional) definition of boundaries, in situations where the positions of boundary nodes or grid cells shall not be automatically determined from analysis of the grid structure:		# (optional) '''definition of boundaries''', in situations where the positions of boundary nodes or grid cells shall not be automatically determined from analysis of the grid structure:
	## (optional) indices of boundary cells - if the numerical models TRIM-2D or TRIM-3D shall be later used (filetype [[FD2RND.DAT\|fd2rnd.dat]])		## (optional) '''indices of boundary''' cells - if the numerical models TRIM-2D or TRIM-3D shall be later used (filetype [[FD2RND.DAT\|fd2rnd.dat]])
	## (optional) definition of boundary sections - can be used together with all types of numerical models (filetype [[BSECTION.DAT\|bsection.dat]]).		## (optional) '''definition of boundary sections''' - can be used together with all types of numerical models (filetype [[BSECTION.DAT\|bsection.dat]]).
	#: These informations may be useful when boundary data time series are going to be generated for water level elevation, salinity and temperature. For sources and sinks this information is not even useful.		#: These informations may be useful when boundary data time series are going to be generated for water level elevation, salinity and temperature. For sources and sinks this information is not even useful.

	Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).		Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).
	\|outputfiles=		\|outputfiles=
	# systemfile with locations of the nodes or cells where boundary time series data were generated (filetype [[LOCATION_GRID.DAT\|location_grid.dat]]);		# '''systemfile with locations''' of the nodes or cells where boundary time series data were generated (filetype [[LOCATION_GRID.DAT\|location_grid.dat]]);
	# synoptic boundary data for all boundary data locations (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])		# '''synoptic boundary data''' for all boundary data locations (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])
	#: Remark: these result files are especially useful in connexion with the application of the numerical model UNTRIM.		#: Remark: these result files are especially useful in connexion with the application of the numerical model UNTRIM.
	# (optional) boundary time series data (filetype [[RNDWERTE.DAT\|rndwerte.dat]])		# (optional) '''boundary time series data''' (filetype [[RNDWERTE.DAT\|rndwerte.dat]])
	#: Remark: this data file can be used as input file for the programs [[TM2RND]] and [[TR2RND]] respectively to generate boundary time series data for the numerical models TELEMAC-2D or TRIM-2D and TRIM-3D.		#: Remark: this data file can be used as input file for the programs [[TM2RND]] and [[TR2RND]] respectively to generate boundary time series data for the numerical models TELEMAC-2D or TRIM-2D and TRIM-3D.
	#: Remark: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.		#: Remark: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.
	# (optional) indices of boundary cells, if either TRIM-2D or TRIM-3D shall be later used, and the boundary grid cells have not been already specified as input data before (filetype [[FD2RND.DAT\|fd2rnd.dat]])		# (optional) '''indices of boundary cells''', if either TRIM-2D or TRIM-3D shall be later used, and the boundary grid cells have not been already specified as input data before (filetype [[FD2RND.DAT\|fd2rnd.dat]])
	#: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.		#: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.
	# (optional) lineprinter file contains useful informations related to program execution (filetype utrrnd.sdr);		# (optional) '''lineprinter file''' contains useful informations related to program execution (filetype utrrnd.sdr);
	# (optional) file with trace of program execution (filetype utrrnd.trc).		# (optional) file with '''trace of program execution''' (filetype utrrnd.trc).
	\|methodology=		\|methodology=
	* how boundary locations are determined (water level elevation, salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions))		* '''how boundary locations are determined''' (water level elevation, salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions))
	** If the user does not explicitely specify informations which describe the positions of boundary nodes or grid cells the latter ones will be automatically determined by the program. The algorithm tries to determine all open boundary nodes from the grid structure.		** If the user does not explicitely specify informations which describe the positions of boundary nodes or grid cells the latter ones will be automatically determined by the program. The algorithm tries to determine all open boundary nodes from the grid structure.
	** If the user has specified additional informations (e.g. fd2rnd.dat or bsection.dat), they are used to determine the locations of boundary nodes or grid cells which are situated along the outer boundary of a computational grid.		** If the user has specified additional informations (e.g. fd2rnd.dat or bsection.dat), they are used to determine the locations of boundary nodes or grid cells which are situated along the outer boundary of a computational grid.
	* interpolation using computational results (water level elevation)		* '''interpolation using computational results''' (water level elevation)
	** For any location where boundary time series data shall be generated at first the closest lying computational points are determined. Thereafter the time serie at the location of the boundary node will be determined from the numerically computed time series by means of a linear interpolation. No interpolation is done with respect to time.		** For any location where boundary time series data shall be generated at first the closest lying computational points are determined. Thereafter the time serie at the location of the boundary node will be determined from the numerically computed time series by means of a linear interpolation. No interpolation is done with respect to time.
	** If a boundary node or grid cell is located outside the computational domain the closest lying computational point will be determined and the computed time series data will be used directly without any interpolation or extrapolation.		** If a boundary node or grid cell is located outside the computational domain the closest lying computational point will be determined and the computed time series data will be used directly without any interpolation or extrapolation.
	** Interpolated data can be optionally modified using user-specified values with respect to mean value, amplitude and phase. The modification parameters can be both, space as well as time dependent. Data necessary must be prescribed by the user in files of type boewrt.dat.		** Interpolated data can be optionally modified using user-specified values with respect to mean value, amplitude and phase. The modification parameters can be both, space as well as time dependent. Data necessary must be prescribed by the user in files of type boewrt.dat.
	* interpolation using measured data (water level elevation)		* '''interpolation using measured data''' (water level elevation)
	** If measured data form the basis for interpolation of boundary time series data they will be interpolated to the location of the boundary node or grid cell in an analogous manner as described above for computational result based data.		** If measured data form the basis for interpolation of boundary time series data they will be interpolated to the location of the boundary node or grid cell in an analogous manner as described above for computational result based data.
	** An important difference exists for the generation of boundary time series data of water level elevation. In this situation an analysis to determine times of high and low water is carried through beforehand to determine the time shifts which are applied to the measured data before they are going to be interpolated to obtain a boundary time serie of water level elevation. This type of interpolation (time shift) can be optionally switched off in case the data to be interpolated are not dominated by the tides.		** An important difference exists for the generation of boundary time series data of water level elevation. In this situation an analysis to determine times of high and low water is carried through beforehand to determine the time shifts which are applied to the measured data before they are going to be interpolated to obtain a boundary time serie of water level elevation. This type of interpolation (time shift) can be optionally switched off in case the data to be interpolated are not dominated by the tides.
Line 99:		Line 99:
	\|documentation=		\|documentation=
	* please refer to $PROGHOME/examples/utrrnd/		* please refer to $PROGHOME/examples/utrrnd/
	** ./BSP_becken_src_snk/ : example files for a closed basin with one sink and one source.		** '''./BSP_becken_src_snk/''' : example files for a closed basin with one sink and one source.
	** ./BSP_becken_wind/ : example files for wind influence on water level elevation and current velocity in a closed basin.		** '''./BSP_becken_wind/''' : example files for wind influence on water level elevation and current velocity in a closed basin.
	** ./BSP_hafen/ : example files for wave propagation in a harbour basin.		** '''./BSP_hafen/''' : example files for wave propagation in a harbour basin.
	** ./BSP_kanal_w_gradient/ : example files for a straight channel with constant water level gradient;		** '''./BSP_kanal_w_gradient/''' : example files for a straight channel with constant water level gradient;
	** ./BSP_kanal_w_inflow/ : example files for a straight channel with constant inflow (discharge).		** '''./BSP_kanal_w_inflow/''' : example files for a straight channel with constant inflow (discharge).
	** ./BSP_soliton / : propagation of a solitary wave in a straight wave channel.		** '''./BSP_soliton /''' : propagation of a solitary wave in a straight wave channel.
	** ./BSP_becken_power_plant/ : example files for a closed basin with one sink, where the water is immediately re-introduced at a different location with respective alteration of temperature as well as salinity (useful for simulations of the cooling of a power plant).		** '''./BSP_becken_power_plant/''' : example files for a closed basin with one sink, where the water is immediately re-introduced at a different location with respective alteration of temperature as well as salinity (useful for simulations of the cooling of a power plant).
	* there are also more general informations concerning the generation of boundary conditions available		* there are also more general informations concerning the generation of boundary conditions available
	* especially have a look to the graphical representation for the generation of time series data from measured or simulated data		* especially have a look to the graphical representation for the generation of time series data from measured or simulated data
	}}		}}

← Older revision		Revision as of 11:02, 26 May 2010
Line 47:		Line 47:
	Time series data for sources and sinks are exclusively generated for the specific location given by the user.		Time series data for sources and sinks are exclusively generated for the specific location given by the user.
	\|inputfiles=		\|inputfiles=
	# general input data (filetype utrrnd.dat).		# general input data (filetype [[UTRRND.DAT\|utrrnd.dat]]).
	# grid with boundary nodes or boundary grid cells for which boundary time series data shall be generated or which describes the modelling domain for which sources and sinks are going to be generated:		# grid with boundary nodes or boundary grid cells for which boundary time series data shall be generated or which describes the modelling domain for which sources and sinks are going to be generated:
	#: for TELEMAC-2D - filetype gitter05.dat/bin		#: for [[Mathematical Model TELEMAC-2D\|TELEMAC-2D]] - filetype [[GIITER05.DAT and GITTER05.BIN\|gitter05.dat/bin]]
	#: or		#: or
	#: for TRIM-2D and TRIM-3D - filetype tr2.topo.bin.ind		#: for [[Mathematical Model TRIM-2D\|TRIM-2D]] and [[Mathematical Model TRIM-3D\|TRIM-3D]] - filetype [[TR2.TOPO.BIN.IND\|tr2.topo.bin.ind]]
	#: or		#: or
	#: for UNTRIM - filetype untrim_grid.dat		#: for UNTRIM - filetype [[UNTRIM_GRID.DAT\|untrim_grid.dat]]
	# (optional) description of the vertical structure, e.g. the position of layers, when three-dimensional boundary time series data shall be generated for the numerical model UNTRIM (filetype vertical.dat) This information is only of importance in connexion with the computation of salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions), along open boundaries or sources and sinks inside the modelling domain.		# (optional) description of the vertical structure, e.g. the position of layers, when three-dimensional boundary time series data shall be generated for the numerical model UNTRIM (filetype [[VERTICAL.DAT\|vertical.dat]]) This information is only of importance in connexion with the computation of salinity, temperature, suspended sediment load (several fractions) and tracer load (several fractions), along open boundaries or sources and sinks inside the modelling domain.
	# (optional) if 2D-/3D-results of a previous numerical simulation shall be used:		# (optional) if 2D-/3D-results of a previous numerical simulation shall be used:
	## grid (filetype gitter05.dat/bin or untrim_grid.dat or profil05.bin or location_grid.dat)		## grid (filetype [[GITTER05.DAT and GITTER05.BIN\|gitter05.dat/bin]] or [[UNTRIM_GRID.DAT\|untrim_grid.dat]] or [[PROFIL05.BIN\|profil05.bin]] or [[LOCATION_GRID.DAT\|location_grid.dat]])
	## computed time series data (files of type dirz.bin.R, dirz.bin.I and dirz.bin)		## computed time series data (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])
	## (optional) manually prescribed time series for modification of mean value, amplitude and phase of the time series derived from numerically calculated results (files of type boewrt.dat)		## (optional) manually prescribed time series for modification of mean value, amplitude and phase of the time series derived from numerically calculated results (files of type [[BOEWRT.DAT\|boewrt.dat]])
	#: This functionality is currently only available in connexion with water level elevation boundary data time series.		#: This functionality is currently only available in connexion with water level elevation boundary data time series.
	# (optional) if measured data shall be used to generate the boundary time series data (files of type boewrt.dat)		# (optional) if measured data shall be used to generate the boundary time series data (files of type [[BOEWRT.DAT\|boewrt.dat]])
	# (optional) definition of boundaries, in situations where the positions of boundary nodes or grid cells shall not be automatically determined from analysis of the grid structure:		# (optional) definition of boundaries, in situations where the positions of boundary nodes or grid cells shall not be automatically determined from analysis of the grid structure:
	## (optional) indices of boundary cells - if the numerical models TRIM-2D or TRIM-3D shall be later used (filetype fd2rnd.dat)		## (optional) indices of boundary cells - if the numerical models TRIM-2D or TRIM-3D shall be later used (filetype [[FD2RND.DAT\|fd2rnd.dat]])
	## (optional) definition of boundary sections - can be used together with all types of numerical models (filetype bsection.dat).		## (optional) definition of boundary sections - can be used together with all types of numerical models (filetype [[BSECTION.DAT\|bsection.dat]]).
	#: These informations may be useful when boundary data time series are going to be generated for water level elevation, salinity and temperature. For sources and sinks this information is not even useful.		#: These informations may be useful when boundary data time series are going to be generated for water level elevation, salinity and temperature. For sources and sinks this information is not even useful.

	Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).		Remark: the user should also read the comments stored in the different template files available (please refer to $PROGHOME/examples/utrrnd/).
	\|outputfiles=		\|outputfiles=
	# systemfile with locations of the nodes or cells where boundary time series data were generated (filetype location_grid.dat);		# systemfile with locations of the nodes or cells where boundary time series data were generated (filetype [[LOCATION_GRID.DAT\|location_grid.dat]]);
	# synoptic boundary data for all boundary data locations (files of type dirz.bin.R, dirz.bin.I and dirz.bin)		# synoptic boundary data for all boundary data locations (files of type [[DIRZ.BIN.R\|dirz.bin.r]], [[DIRZ.BIN.I\|dirz.bin.i]] and [[DIRZ.BIN\|dirz.bin]])
	#: Remark: these result files are especially useful in connexion with the application of the numerical model UNTRIM.		#: Remark: these result files are especially useful in connexion with the application of the numerical model UNTRIM.
	# (optional) boundary time series data (filetype rndwerte.dat)		# (optional) boundary time series data (filetype [[RNDWERTE.DAT\|rndwerte.dat]])
	#: Remark: this data file can be used as input file for the programs TM2RND and TR2RND respectively to generate boundary time series data for the numerical models TELEMAC-2D or TRIM-2D and TRIM-3D.		#: Remark: this data file can be used as input file for the programs [[TM2RND]] and [[TR2RND]] respectively to generate boundary time series data for the numerical models TELEMAC-2D or TRIM-2D and TRIM-3D.
	#: Remark: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.		#: Remark: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.
	# (optional) indices of boundary cells, if either TRIM-2D or TRIM-3D shall be later used, and the boundary grid cells have not been already specified as input data before (filetype fd2rnd.dat)		# (optional) indices of boundary cells, if either TRIM-2D or TRIM-3D shall be later used, and the boundary grid cells have not been already specified as input data before (filetype [[FD2RND.DAT\|fd2rnd.dat]])
	#: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.		#: This option is only available when boundary data time series for water level elevation, salinity or temperature are going to be generated.
	# (optional) lineprinter file contains useful informations related to program execution (filetype utrrnd.sdr);		# (optional) lineprinter file contains useful informations related to program execution (filetype utrrnd.sdr);