Differences

This shows you the differences between two versions of the page.

--- news_v5p1:telemac3d [2012/04/08 10:30]
otadmin
+++ news_v5p1:telemac3d [2014/10/10 16:01] (current)
@@ Line 112: / Line 112: @@
     :if 1 : density function of temperature in which case, a tracer must be called <color darkblue>**TEMPERATURE**</color> (use key-word <color darkblue>**NAMES OF TRACERS**</color>)
     :if 2 : density function of salinity in which case, a tracer must be called <color darkblue>**SALINITY**</color>
-    :if 3 : density function of both temperature and salinity in which case, a tracer must be called <color darkblue>**TEMPERATURE**</color> and a tracer must be called <color darkblue>**SALINITY**</color>    :if 4 : density function of all tracers, in which case, the density will be computed with all tracers and the "BETA EXPANSION COEFFICIENT FOR ACTIVE TRACERS" will be used (it is now an array and the <color darkorange>SUBROUTINE **INBETA**</color> has been suppressed). If it is different between tracers, use user <color darkorange>SUBROUTINE **INBETA**</color>. The beta coefficients are used only in case 4 (built in coefficients are used in cases 1, 2 and 3, in <color darkorange>SUBROUTINE **DRSURR**</color>)
+    :if 3 : density function of both temperature and salinity in which case, a tracer must be called <color darkblue>**TEMPERATURE**</color> and a tracer must be called <color darkblue>**SALINITY**</color>
+    :if 4 : density function of all tracers, in which case, the density will be computed with all tracers and the "BETA EXPANSION COEFFICIENT FOR ACTIVE TRACERS" will be used (it is now an array and the <color darkorange>SUBROUTINE **INBETA**</color> has been suppressed). If it is different between tracers, use user <color darkorange>SUBROUTINE **INBETA**</color>. The beta coefficients are used only in case 4 (built in coefficients are used in cases 1, 2 and 3, in <color darkorange>SUBROUTINE **DRSURR**</color>)
   :The order of tracers has no importance, in cases 1, 2 and 3, only their names is important.
@@ Line 128: / Line 129: @@
   :This is now exactly like in TELEMAC-2D, choices are :
     :<color darkblue>**ZERO ELEVATION** (COTE NULLE)</color>
-    :<color darkblue>**CONSTANT ELEVATION** (COTE CONSTANTE)</color>
+    :<color darkblue>**CONSTANT ELEVATION** (COTE CONSTANTE)</color>, in which case the new key-word <color darkblue>**INITIAL ELEVATION** (COTE INITIALE)</color> must be used.
     :<color darkblue>**ZERO DEPTH** (HAUTEUR NULLE)</color>
-    :<color darkblue>**CONSTANT DEPTH** (HAUTEUR CONSTANTE)</color>
+    :<color darkblue>**CONSTANT DEPTH** (HAUTEUR CONSTANTE)</color>, in which case the new key-word <color darkblue>**INITIAL DEPTH** (HAUTEUR INITIALE)</color> must be used.
-    :<color darkblue>**SPECIAL** (PARTICULIERES)</color>
+    :<color darkblue>**SPECIAL** (PARTICULIERES)</color>, in which case <color darkorange>SUBROUTINE **CONDIM**</color> must be modified.
-  :In the latter case <color darkorange>SUBROUTINE **CONDIM**</color> must be modified. All the choices will act only on the depth, velocities are set to 0. With <color darkblue>**CONSTANT ELEVATION**</color>, the new key-word <color darkblue>**INITIAL ELEVATION** (COTE INITIALE)</color> must be used. With <color darkblue>**CONSTANT DEPTH**</color>, the new key-word <color darkblue>**INITIAL DEPTH**
+  :All the choices will act only on the depth, velocities are set to 0.
-(HAUTEUR INITIALE)</color> must be used. Another possibility for initial conditions is the key-word: <color darkblue>**2D CONTINUATION** (SUITE 2D)</color>. If set to yes, the <color darkblue>**BINARY FILE 1** (FICHIER BINAIRE 1)</color> will be considered as a 2D result and read to find the depth and the two components of the horizontal velocity.
+  :Another possibility for initial conditions is the key-word: <color darkblue>**2D CONTINUATION** (SUITE 2D)</color>. If set to yes, the <color darkblue>**BINARY FILE 1** (FICHIER BINAIRE 1)</color> will be considered as a 2D result and read to find the depth and the two components of the horizontal velocity.
 == TELEMAC-2D OPTIONS (OPTIONS POUR TELEMAC-2D) ==
@@ Line 171: / Line 172: @@
   :<color red>**Important notes**</color>:
-  -) The numbering is the numbering of liquid boundaries, as given at the beginning of the listing (by <color darkorange>SUBROUTINE **FRONT2**</color>, or by the boundary conditions file in parallelism)
+  - The numbering is the numbering of liquid boundaries, as given at the beginning of the listing (by <color darkorange>SUBROUTINE **FRONT2**</color>, or by the boundary conditions file in parallelism)
-  -) The key-words <color darkblue>**PRESCRIBED ELEVATIONS**</color>, <color darkblue>**PRESCRIBED DISCHARGES**</color> and <color darkblue>**PRESCRIBED VELOCITIES**</color> must be given in the steering file, with constant values, even if the values will be read after in the liquid boundaries file.
+  - The key-words <color darkblue>**PRESCRIBED ELEVATIONS**</color>, <color darkblue>**PRESCRIBED DISCHARGES**</color> and <color darkblue>**PRESCRIBED VELOCITIES**</color> must be given in the steering file, with constant values, even if the values will be read after in the liquid boundaries file.
-  -) All this automatic setting of boundary conditions can be erased in the user <color darkorange>SUBROUTINE **BORD3D**</color>, and changed into a simple setting of prescribed values. <color darkorange>**Q3**</color>, <color darkorange>**SL3**</color> and <color darkorange>**VIT3**</color> may also be reprogrammed for complex cases.
+  - All this automatic setting of boundary conditions can be erased in the user <color darkorange>SUBROUTINE **BORD3D**</color>, and changed into a simple setting of prescribed values. <color darkorange>**Q3**</color>, <color darkorange>**SL3**</color> and <color darkorange>**VIT3**</color> may also be reprogrammed for complex cases.
 ===== New user subroutine and modifications in user subroutines =====
@@ Line 183: / Line 184: @@
 == VISCO ==
- :The <color darkorange> SUBROUTINE **VISCO**</color> has been modified to take into account the two new keywords for turbulence models.
+  :The <color darkorange> SUBROUTINE **VISCO**</color> has been modified to take into account the two new keywords for turbulence models.
 == Q3D ==