New features of Telemac-2D version 7.1

New features and differences with version 7.0

Estimated release date: end 2015

Latest article update: 05/01/2016

Main new features of this version 7.1

New distributive schemes, including a "dry-water proof" version

(see the article on all programmes for details).

Schematic tides for TELEMAC-2D and TELEMAC-3D

Modelling schematic tides (astronomical spring tide, mean spring tide, mean tide, mean neap tide, astronomical neap tide) to study schematic or average scenarii is available for the 4 tidal databases (JMJ already available since v6.1, and the other ones: TPXO-type from Oregon State University, NEA/FES, PREVIMER).
Keyword to activate OPTION FOR TIDAL BOUNDARY CONDITIONS with a value between 2 to 6.

Keywords to fill in: "GLOBAL NUMBER OF THE POINT TO CALIBRATE HIGH WATER" with TPXO-type tidal database from Oregon State University (mandatory) and "LOCAL NUMBER OF THE POINT TO CALIBRATE HIGH WATER" with JMJ, NEA/FES, PREVIMER tidal databases (if not filled in, a value is then automatically calculated).

New or modified key-words

"FRICTION DATA FILE" (FICHIER DE DONNEES POUR LE FROTTEMENT)

The friction law and the friction coefficient for boundaries must now always be given (they were before only given in the case of k-epsilon model).

"OPTION FOR TIDAL BOUNDARY CONDITIONS" (OPTION POUR LES CONDITIONS AUX LIMITES DE MAREE)

This keyword is now an array with a value given per liquid boundary file, separated by semicolons. Otherwise all liquid boundaries with prescribed velocities or depths would receive tidal conditions. This avoids a clash when using weirs in the domain. 0 codes for conditions other than tidal.

BEWARE !!! Old models must be changed if their tidal boundary is not number 1. In that case this keyword must be changed and more values given.

"LOCAL NUMBER OF THE POINT TO CALIBRATE HIGH WATER" (NUMERO LOCAL DU POINT POUR CALER LA PLEINE MER)

Local number between 1 and the number of tidal boundary points (of the HARMONIC CONSTANTS FILE) where the tidal boundary conditions are computed with JMJ, NEA, FES, PREVIMER databases (except TPXO-type databases).
The tidal constituents have their phase shifted with respect to this point to start the simulation with a high water (for schematic tides only). Default value is 0, which means that the value is automatically calculated by TELEMAC.

"GLOBAL NUMBER OF THE POINT TO CALIBRATE HIGH WATER" (NUMERO GLOBAL DU POINT POUR CALER LA PLEINE MER)

Global number of the point with respect to which the tidal constituents have their phase shifted to start the calculation with a high water (for schematic tides only). Only harmonic constants databases like TPXO are concerned. The user has to give an existing value.

"MAXIMUM NUMBER OF BOUNDARIES" (NOMBRE MAXIMUM DE FRONTIERES)

Maximal number of boundaries in the mesh. Used for dimensioning arrays. Can be increased if needed.

"MAXIMUM NUMBER OF SOURCES" (NOMBRE MAXIMUM DE SOURCES)

Maximal number of punctual sources in the mesh. Used for dimensioning arrays. Can be increased if needed.

"MAXIMUM NUMBER OF TRACERS" (NOMBRE MAXIMUM DE TRACEURS)

These 3 new keywords are used to give an a priori dimension to a number of allocatable files, they give the values of respectively MAXFRO, MAXSCE and MAXTRA. A number of arrays with hardcoded dimension are now allocated with these dimensions. Changing these keyword will avoid changing the hardcoded values, which required recompiling the whole package. A number of user functions have been amended to cope with this change: Q, TR, SL, VIT, DEBSCE and TRSCE. To adapt a specific user function, either copy your personal bits of code into the new functions or do the following: remove the declarations and initialisation of DEJA and OK. Change the remaining occurences of OK into OKQ for function Q, OKSL for function SL, etc., up to OKTRSCE for function TRSCE.

Modifications in user subroutines or new subroutines

condin.f

As the number of arguments of CONDI_TPXO subroutine (in module TPXO) has changed, this subroutine has changed in version 7.1. The user is advised to update this subroutine with version 7.1.