WhatIs: The tracer.def input file - Historique des versions

Lguez le 3 janvier 2023 à 12:01

2023-01-03T12:01:00Z

Lguez le 3 janvier 2023 à 12:00

2023-01-03T12:00:06Z

Emillour le 3 janvier 2023 à 08:23

2023-01-03T08:23:36Z

Emillour le 3 janvier 2023 à 08:17

2023-01-03T08:17:55Z

Emillour le 3 janvier 2023 à 08:14

2023-01-03T08:14:22Z

Emillour : Page créée avec « == The tracer.def input file == This file contains information on the tracers that will be advected in the dynamics. It should be used instead of the now depreciated Wha... »

2023-01-03T08:07:52Z

Page créée avec « == The tracer.def input file == This file contains information on the tracers that will be advected in the dynamics. It should be used instead of the now depreciated Wha... »

Nouvelle page

== The tracer.def input file ==
This file contains information on the tracers that will be advected in the dynamics. It should be used instead of the now depreciated [[WhatIs: The traceur.def input file|traceur.def]] input file.

== Simple example of a ''tracer.def'' file ==
<pre>
&version=1.0
&lmdz
default type=tracer phases=g hadv=10 vadv=10 parent=air
H2O hadv=14 vadv=14
H2O phases=ls
Aga
</pre>
* The mandatory first line ''&version'' is there to handle (potential) versioning of these file and their format
* The mandatory second line ''&lmdz'' is there to specify the scope of the following lines, i.e. that all that follow is relevant for the LMDZ lon-lat dynamical core.
* The mandatory third line starting with ''default'' specifies the default attributes for all the tracers. In this example that they are of type ''tracer'' (as opposed to type ''tag'' for tagging), that there phase is ''g'' (gas), that they are advected using advection schemes hadv and vadv ''10'' (Van Leer advection scheme) and that their parent (i.e. carrier fluid) is ''air''.
* Then one should specify on successive lines the tracer names and optionally their properties such as phases (g: gas, l: liquid, s:solid). Note that one may condense information about phases using a mix of letters g/l/s rather than specifying the information for each on a separate line. In practice the lines
<pre>
H2O hadv=14 vadv=14
H2O phases=ls
</pre>
From the example above which specifies there are 3 H2O phases (gas, liquid and solid), where the gas phase is advected with the hadv and vadv ''14'' dedicated scheme could also be written more explicitly as:
<pre>
H2O phases=g hadv=14 vadv=14
H2O phases=l
H2O phases=s
</pre>

== A more advanced example of a ''tracer.def file'' ==

03/01/2023

[[Category:WhatIs]]

@@ Ligne 3 : / Ligne 3 : @@
 == Simple example of a ''tracer.def'' file ==
-In this example there are 4 tracers: 3 for water (one for each of its phases, gas, liquid or solid) and one called ''Aga''
+In this example there are 4 tracers: 3 for water (one for each of its phases, gas, liquid or solid) and one called ''Aga'' (age of air)
 <pre>
 &version=1.0

@@ Ligne 39 : / Ligne 39 : @@
 H2[18]O,H[2]HO,H2[16]O phases=gls parent=H2O
 con,oce phases=gls parent=H2[18]O,H[2]HO,H2[16]O type=tag
 </pre>

@@ Ligne 1 : / Ligne 1 : @@
 == The tracer.def input file ==
-This file contains information on the tracers that will be advected in the dynamics. It should be used instead of the now depreciated [[WhatIs: The traceur.def input file|traceur.def]] input file.
+This file contains information on the tracers that will be advected in the dynamics. It should be used instead of the now deprecated [[WhatIs: The traceur.def input file|traceur.def]] input file.
 == Simple example of a ''tracer.def'' file ==

@@ Ligne 28 : / Ligne 28 : @@
 == A more advanced example of a ''tracer.def file'' ==
+The following example includes water isotopes (identified by the fact that their ''parent'' is not ''air'' but the tracer ''H2O'')
 /01/2023
 [[Category:WhatIs]]