WhatIs: The tracer.def input file
De LMDZPedia
Révision de 3 janvier 2023 à 13:00 par Lguez (discussion | contributions)
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 deprecated traceur.def input file.
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
&version=1.0 &lmdz default type=tracer phases=g hadv=10 vadv=10 parent=air H2O hadv=14 vadv=14 H2O phases=ls Aga
- 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
H2O hadv=14 vadv=14 H2O phases=ls
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:
H2O phases=g hadv=14 vadv=14 H2O phases=l H2O phases=s
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) with two tags (con and oce)
&version=1.0 &lmdz default hadv=10 vadv=10 phases=g parent=air type=tracer H2O hadv=14 vadv=14 H2O phases=ls RN,PB 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
As LMDZ runs it outputs the detailed information about all tracers and their dependencies to one another. For the example above one would get:
readTracersFiles: RAW CONTENT OF SECTION "lmdz": readTracersFiles: iq | hadv | vadv | name | parent | phase readTracersFiles: ----+------+------+------------------------+------------------------+------- readTracersFiles: 1 | 14 | 14 | H2O | air | g readTracersFiles: 2 | 10 | 10 | H2O | air | ls readTracersFiles: 3 | 10 | 10 | RN,PB | air | g readTracersFiles: 4 | 10 | 10 | H2[18]O,H[2]HO,H2[16]O | H2O | gls readTracersFiles: 5 | 10 | 10 | con,oce | H2[18]O,H[2]HO,H2[16]O | gls readTracersFiles: readTracersFiles: EXPANDED CONTENT OF SECTION "lmdz": readTracersFiles: iq | hadv | vadv | name | parent | igen | phase readTracersFiles: ----+------+------+---------------+-----------+------+------- readTracersFiles: 1 | 14 | 14 | H2O_g | air | 0 | g readTracersFiles: 2 | 10 | 10 | H2O_l | air | 0 | l readTracersFiles: 3 | 10 | 10 | H2O_s | air | 0 | s readTracersFiles: 4 | 10 | 10 | RN | air | 0 | g readTracersFiles: 5 | 10 | 10 | PB | air | 0 | g readTracersFiles: 6 | 10 | 10 | H2[18]O_g | H2O_g | 1 | g readTracersFiles: 7 | 10 | 10 | H2[18]O_l | H2O_l | 1 | l readTracersFiles: 8 | 10 | 10 | H2[18]O_s | H2O_s | 1 | s readTracersFiles: 9 | 10 | 10 | H[2]HO_g | H2O_g | 1 | g readTracersFiles: 10 | 10 | 10 | H[2]HO_l | H2O_l | 1 | l readTracersFiles: 11 | 10 | 10 | H[2]HO_s | H2O_s | 1 | s readTracersFiles: 12 | 10 | 10 | H2[16]O_g | H2O_g | 1 | g readTracersFiles: 13 | 10 | 10 | H2[16]O_l | H2O_l | 1 | l readTracersFiles: 14 | 10 | 10 | H2[16]O_s | H2O_s | 1 | s readTracersFiles: 15 | 10 | 10 | H2[18]O_g_con | H2[18]O_g | 2 | g readTracersFiles: 16 | 10 | 10 | H2[18]O_l_con | H2[18]O_l | 2 | l readTracersFiles: 17 | 10 | 10 | H2[18]O_s_con | H2[18]O_s | 2 | s readTracersFiles: 18 | 10 | 10 | H2[18]O_g_oce | H2[18]O_g | 2 | g readTracersFiles: 19 | 10 | 10 | H2[18]O_l_oce | H2[18]O_l | 2 | l readTracersFiles: 20 | 10 | 10 | H2[18]O_s_oce | H2[18]O_s | 2 | s readTracersFiles: 21 | 10 | 10 | H[2]HO_g_con | H[2]HO_g | 2 | g readTracersFiles: 22 | 10 | 10 | H[2]HO_l_con | H[2]HO_l | 2 | l readTracersFiles: 23 | 10 | 10 | H[2]HO_s_con | H[2]HO_s | 2 | s readTracersFiles: 24 | 10 | 10 | H[2]HO_g_oce | H[2]HO_g | 2 | g readTracersFiles: 25 | 10 | 10 | H[2]HO_l_oce | H[2]HO_l | 2 | l readTracersFiles: 26 | 10 | 10 | H[2]HO_s_oce | H[2]HO_s | 2 | s readTracersFiles: 27 | 10 | 10 | H2[16]O_g_con | H2[16]O_g | 2 | g readTracersFiles: 28 | 10 | 10 | H2[16]O_l_con | H2[16]O_l | 2 | l readTracersFiles: 29 | 10 | 10 | H2[16]O_s_con | H2[16]O_s | 2 | s readTracersFiles: 30 | 10 | 10 | H2[16]O_g_oce | H2[16]O_g | 2 | g readTracersFiles: 31 | 10 | 10 | H2[16]O_l_oce | H2[16]O_l | 2 | l readTracersFiles: 32 | 10 | 10 | H2[16]O_s_oce | H2[16]O_s | 2 | s
03/01/2023
