UTRRND.DAT: Difference between revisions
From BAWiki
imported>BAWiki 1 (Created page with '{{FileDescription |name_de=UTRRND.DAT |filetype=utrrnd.dat |version=V7.x/August 2008 |version_descr=July 2009 |significance=contains user-specied input data for the program UT…') |
imported>BAWiki 1 No edit summary |
||
Line 16: | Line 16: | ||
#* '''sources''': measured data must be prescribed; | #* '''sources''': measured data must be prescribed; | ||
#* '''sinks''': measured data must be prescribed. | #* '''sinks''': measured data must be prescribed. | ||
#: Remarks concerning the use of measured data (typically boewrt.dat): | #: Remarks concerning the use of measured data (typically [[BOEWRT.DAT|boewrt.dat]]): | ||
## data must not be necessarily available at constant time intervals. | ## data must not be necessarily available at constant time intervals. | ||
## files of type boewrt.dat must be prescribed in a sorted way, in order to describe the model boundary in either clockwise or anti-clockwise orientation. Internal to the program a boundary polygon is generated. The first section consists out of data points one an two, the second section out of data points two and three, and so forth. | ## files of type [[BOEWRT.DAT|boewrt.dat]] must be prescribed in a sorted way, in order to describe the model boundary in either clockwise or anti-clockwise orientation. Internal to the program a boundary polygon is generated. The first section consists out of data points one an two, the second section out of data points two and three, and so forth. | ||
## During interpolation (IP) at a target point the following cases are distinguished: | ## During interpolation (IP) at a target point the following cases are distinguished: | ||
### the target point is not located between any start or end point of a segment: in this situation the time serie of the closest lying data point will be used. | ### the target point is not located between any start or end point of a segment: in this situation the time serie of the closest lying data point will be used. | ||
### the target point is located between a start and end point of a segment: in this situation the data from the sgement will be used, with closest orthogonal distance to the target point. | ### the target point is located between a start and end point of a segment: in this situation the data from the sgement will be used, with closest orthogonal distance to the target point. | ||
#:: Remark: A target point is located between start and end point of a segment if the orthogonal with respect to the segment originating at the target point has an intersection between S and E. | #:: Remark: A target point is located between start and end point of a segment if the orthogonal with respect to the segment originating at the target point has an intersection between S and E. | ||
#: Similarily for extracted (boewrt.dat) computational result. | #: Similarily for extracted ([[BOEWRT.DAT|boewrt.dat]]) computational result. | ||
# (optional) '''informations related to the boundary''': with these informations UTRRND will be able to generate boundary time series data for arbitrary sections along the (outer) boundary of a computational domain. In situations when they are not available the program will try to determine (open) boundary sections automatically from the grid structure. This auxiliary informations can only be prescribed for water level elevation and salinity boundary data. | # (optional) '''informations related to the boundary''': with these informations UTRRND will be able to generate boundary time series data for arbitrary sections along the (outer) boundary of a computational domain. In situations when they are not available the program will try to determine (open) boundary sections automatically from the grid structure. This auxiliary informations can only be prescribed for water level elevation and salinity boundary data. | ||
# '''start and end time''' as well as '''time step''' for which boundary time series data shall be generated. | # '''start and end time''' as well as '''time step''' for which boundary time series data shall be generated. |
Latest revision as of 13:59, 26 May 2010
Basic Information
File-Type
utrrnd.dat
File-Form
FORMATTED
Version
V7.x/August 2008
Description-Date
July 2009
Significance of the File
contains user-specied input data for the program UTRRND
File-Contents (in Catchwords)
- type and name of grid: from this information UTRRND knows for which (type of) grid boundary data time series shall be generated.
- (optional) file with vertical structure: if boundary data time series shall vary over the water depth the vertical structure (position of the horizontal computational layers) must be prescribed.
- (optional) reference point: when the origin of the grid differs from (0,0) the correct reference point for the coordinates must be prescribed.
- time series input data: all data required to generate the desired boundary time series data must be contained in the user-specified files.
- water level elevation: data files may contain either results of earlier simulation runs or measured data;
- salinity: measured data must be prescribed;
- suspended sediments (several fractions): measured data must be prescribed;
- tracers (several fractions): measured data must be prescribed;
- sources: measured data must be prescribed;
- sinks: measured data must be prescribed.
- Remarks concerning the use of measured data (typically boewrt.dat):
- data must not be necessarily available at constant time intervals.
- files of type boewrt.dat must be prescribed in a sorted way, in order to describe the model boundary in either clockwise or anti-clockwise orientation. Internal to the program a boundary polygon is generated. The first section consists out of data points one an two, the second section out of data points two and three, and so forth.
- During interpolation (IP) at a target point the following cases are distinguished:
- the target point is not located between any start or end point of a segment: in this situation the time serie of the closest lying data point will be used.
- the target point is located between a start and end point of a segment: in this situation the data from the sgement will be used, with closest orthogonal distance to the target point.
- Remark: A target point is located between start and end point of a segment if the orthogonal with respect to the segment originating at the target point has an intersection between S and E.
- Similarily for extracted (boewrt.dat) computational result.
- (optional) informations related to the boundary: with these informations UTRRND will be able to generate boundary time series data for arbitrary sections along the (outer) boundary of a computational domain. In situations when they are not available the program will try to determine (open) boundary sections automatically from the grid structure. This auxiliary informations can only be prescribed for water level elevation and salinity boundary data.
- start and end time as well as time step for which boundary time series data shall be generated.
- Remark: the required period of time must be available in the above mentioned input data. The time step must not coincide with the one for which input data are available.
- type and name of result files: with this information the amount of output data generated can be influenced independently for each type of boundary data.
- (optional) steering parameters for program execution, e. g. switching off tidal analysis during interpolation of water level time series.
Remark: dictionary-file utrrnd_dico.dat, normally present in directory $PROGHOME/dic/, will be automatically read by the application program in addition to the user-specified input file.
Programs using this Type of File
Example-File
please refer to $PROGHOME/examples/utrrnd/utrrnd.dat
back to: File Descriptions