Table of Contents
New telemac2d features for v5p6 links from New version features
v5p6 TELEMAC-2D
Date: 5th July 2006
The principal features of this version v5p6 of TELEMAC-2D are:
- Wave equation + Quasi-bubble is possible
New options and new or modified keywords
THRESHOLD DEPTH FOR WIND (PROFONDEUR LIMITE POUR LE VENT)
Double precision. The default value is 1.
This keyword is used to avoid artificial velocities in shallow waters or tidal flats.
THRESHOLD FOR NEGATIVE DEPTHS (SEUIL POUR LES PROFONDEURS NEGATIVES)
Double precision. The default value is 0.
This threshold is a negative number. Negative depths below this threshold will be smoothed.
For example if THRESHOLD FOR NEGATIVE DEPTHS=-0.01 depths down to –0.01 m will remain unchanged.
ORIGIN COORDINATES (COORDONNEES DE L’ORIGINE)
Integer, size 2. The default value is 0;0
These 2 integers will be transferred to the results file in the SELAFIN format, for a use by post-processors for superimposition of results with digital maps (coordinates in meshes may be reduced to avoid large real numbers). These 2 integers may be used in user subroutines under the names: I_ORIG and J_ORIG. Otherwise they are not yet used.
PERIODE DE SORTIE LISTING
:: has now an alias in French PERIODE POUR LES SORTIES LISTING for compatibility with TELEMAC-3D
New user subroutine and modifications in user subroutines
FUNCTION TR
A third and new argument: IERR.
If IERR is 0, an imposed value of the tracer has been found either in the liquid boundaries file or in the parameter file.
If IERR is 1, nothing has been found (and in this case subroutine BORD will keep the data taken in the boundary conditions file). The order of priority is thus:
- Liquid boundaries file (values such as TR(1), TR(2) varying in time but constant per boundary).
- Parameter file (values constant in time per boundary)
- Boundary conditions file (values constant in time but that may vary from point to point)
Other cases may be programmed in function TR, but TR is called only if the prescribed values of tracer have been given in the parameter file or if the liquid boundaries file exist. In this case IERR must be set to 0, otherwise the result will be discarded by SUBROUTINE BORD.