\documentclass{article}
\usepackage[english]{babel}
\usepackage[latin1]{inputenc}

\usepackage{a4wide}
\begin{document}

\def\afaire#1{{\bf Afaire : #1}}
\title{Hands on tutorial \#1: First steps with the model}
\date{November 30, 2017}
\author{The LMDZ team}

\maketitle

This first tutorial focuses on installing and making basic first
runs using the LMDZ model.

This document can be downloaded as a pdf file:
\begin{verbatim}
wget http://www.lmd.jussieu.fr/~lmdz/pub/Training/Tutorials/Tutorial_1.pdf
\end{verbatim}
which should ease any copy/paste of command lines to issue.

%\def\infol#1{#1}
%\def\infol#1{\verb+ #1 +}
\def\infol#1{{\bf #1}}
%\newcommand{\infol}[1]{\verb\+ #1 \+}

\def\resol#1#2#3{#1$\times$#2-L#3} %


\section{Prerequisits}

To run LMDZ, you will need a significant amount of memory, so first
ensure this is true. You can use the following command line
(that you can also, for convenience, put in your ~/.bashrc file):
\begin{verbatim}
ulimit -Ss unlimited
\end{verbatim}


If you are working on a laptop provided by the LMD and dedicated to
these training sessions, you have to log in as the default (and sole)
user util1 (the associated password will be given during the training session).
On those machines, a working folder, named LMDZ, contains all the required
archives ; if it's not already there, you can create it:
\begin{verbatim}
mkdir LMDZ
cd LMDZ
\end{verbatim}
You may want to copy this full folder on a USB key at the end of the sessions.

\section{Running the install\_lmdz.sh script}

%If you're using a laptop provided for this training courses, you should
%find the \verb+install_lmdz.sh+ in the main directory (LMDZ) ; otherwise,
The first step consists in downloading it from the LMD website
and {\em blindly} running it (after having first set the access permissions
to make it executable):
\begin{verbatim}
wget http://www.lmd.jussieu.fr/~lmdz/pub/install_lmdz.sh
chmod +x install_lmdz.sh
./install_lmdz.sh -d 48x36x39 -v 20171119.trunk
\end{verbatim}

In the present case, option \verb+-v 20171119.trunk+ implies that the version
built on 19th November 2017 will be installed, and option \verb+-d 48x36x39+
that a bench testcase at resolution \resol{48}{36}{39} will be run. \newline
Compilation should take around five minutes.
The test bench is then downloaded (or copied over if already on the disk) and the
1 day long test simulation on a regular \resol{48}{36}{39} grid is run ;
messages about various downloads (via \infol{wget}) and/or compiler
informations are displayed.

The script should then run smoothly (if it isn't the case,
immediately ask for some assistance) and
end with messages of the likes of:
\begin{verbatim}
##########################################################
Simulation finished in ...
You have compiled with:
./makelmdz...
You may re-run it with : cd  ...
or ./bench.sh
##########################################################
\end{verbatim}

You can take advantage of the installation time to open a second terminal
window and explore the downloaded directories and files.\newline

\verb+install_lmdz.sh+ will check if some archives (LMDZ, NetCDF library, etc.) are
on the disk (in the \verb+~/LMDZ+ directory and subdirectories) and if not, will try to retrieve
them through the network using \verb+wget+ command.
It will create the \infol{LMDZ20171119.trunk} directory ; inside, you will find subdirectories
\infol{modipsl}, which contains the model, and
\infol{netcdf-4.0.1}, which contains the NetCDF library.

In \infol{modipsl}, you will find directory \infol{modeles}, containing the 
\infol{LMDZ} directory.


Once the test bench simulation has been launched (the final step of the \infol{install\_lmdz.sh}
script), you will also find a  \infol{LMDZ/BENCH48x36x39/} directory from where
you will be able to list the outputs of the run (even if the simulation is still running:
it indeed takes a few minutes to complete the 1 day-long run on a single processor).
Check out the contents of this directory and use your favorite software (Grads,
Ferret,...) to browse the contents of the \infol{histday.nc} file.\newline

%If you're using a laptop dedicated to the training, the required files/archives
%are already there. Otherwise, if downloads fail (slow network), please ask
%for some help to get them from a USB key.

The default behavior of the \verb+install_lmdz.sh+ script is to install the model
using the \verb+gfortran+ compiler, which is fine on the laptops provided
for this training course.
In any case, you can switch to another compiler using the\verb+-compiler+ option of the \verb+install_lmdz.sh+ script.
%For example, on CICLAD cluster, you may set \verb+compilo=ifort+
%before launching \verb+./install_lmdz.sh+.

Several other features of the script can be modified or unactivated
just by editing few parameters in the file or specifying the appropriate
option (run \verb+./install_lmdz.sh -h+ to learn about these). For example, you can disable the
NetCDF download and installation (first operation performed by \verb+install_lmdz.sh+)
in case this library is already present on the computer you are using.
%\footnote{The LMDZ compilation embedded in {\bf install\_lmdz.sh} uses the
%{\bf makelmdz\_fcm} script rather than the default {\bf makelmdz} script.
%To change this behaviour in the {\bf install\_lmdz.sh} script find the instruction line
%{\bf compile\_with\_fcm=0} and change it to {\bf compile\_with\_fcm=1}. }.


\section{Changing the outputs}

The model outputs are controled in file \infol{config.def} by the following
lines:
\begin{verbatim}
phys_out_filekeys=       y       y       n       y       n
phys_out_filenames=      histmth histday histhf  histins histLES
phys_out_filetimesteps=  5day    1day    1hr     6hr     6hr
phys_out_filelevels=     10      5       0       4       4
phys_out_filetypes=      ave(X)  ave(X)  ave(X) inst(X) inst(X)
\end{verbatim}
Note the \verb+phys_out_filekeys+ flags (y/n) which set which file is generated.
In the present case, you will obtain 3 files (apart from ORCHIDEE related outputs):
\verb+histmth.nc+, \verb+histday.nc+ and \verb+histins.nc+, containing respectively
0 days (should contain 1 record for the whole run, but the output frequency set for \verb+histmth.nc+ above is \verb+5day+, whereas the run was only 1 day long), daily and 6-hour averages.

You can find out which variables have been written in a given file by running the command:
\begin{verbatim}
ncdump -h histday.nc | grep long_name
\end{verbatim}

To get a \verb+histmth.nc+ with data, you would need to run the model over 5 days.
This means you would need to change the value of \infol{nday} in file \infol{run.def} to 5.
To run a new simulation, issue command \verb+./gcm.e+; if all goes well, it should end with the message \verb+"Everything is cool"+.

%Before relaunching the model, you can switch the ORCHIDEE model off
%by editing, in the bench directory, the \verb+config.def+ parameters file
%and setting \verb+VEGET=n+.\\
%Also, you need to remove some output files (in case you relaunch in the
%same directory):
%\begin{verbatim}
%rm sechiba_out_*.nc sechiba_rest_out.nc
%\end{verbatim}

You may also re-run the simulation with a higher output frequency for
few variables (e.g. atmospheric temperature at 2m above the surface:
\infol{t2m}, surface pressure: \infol{psol}, precipitation: \infol{precip}, etc.),
and other fields types (for instance instantaneous fields) by modifying \infol{config.def}:
\begin{verbatim}
phys_out_filekeys=       y       y       n       y       n
phys_out_filenames=      histmth histday histhf  histins histLES
phys_out_filetimesteps=  5day    1day    1hr     1TS     6hr
phys_out_filelevels=     10      5       0       4       4
phys_out_filetypes=      ave(X)  ave(X)  ave(X) inst(X) inst(X)
flag_t2m=                10      10      5       3       5
flag_psol=               10      10      5       3       4
flag_precip=             10      10      4       3       5
\end{verbatim}
Note that unlike other frequencies, 1TS (1 Time Step) is written in capital letters.\\
You can check in particular the \infol{histts.nc} file and explain the special results.


\section{Making some sensitivity test runs}

You can now move on to changing parameters in a .def file. 
One may for instance deactivate the subgrid orography parametrizations by
changing the \infol{ok\_orodr} and \infol{ok\_orolf} flags in \infol{physiq.def}.
One could also choose to change the value of the cloud water to rain conversion
factor \infol{cld\_tau\_lsc} (in \infol{physiq.def}), or the atmospheric CO$_2$
concentration, etc. (ask around
to find out the meaning of the various available parameters).

Just run the simulation (in a different directory to avoid overwritting output
files) and investigate the differences between simulations (using \verb+diff+ 
or your favorite visualization software).


\section{Preparing things for tomorrow's course}
Tomorrow you will need to run the model (at \resol{48}{36}{39} resolution)
and investigate the outputs. To prepare things for that you must,
in a dedicated directory, run the model for 1 day.
\begin{itemize}
\item go to \verb+LMDZtesting/modipsl/modeles/LMDZ+ and use the file called:

\begin{verbatim}
bench_lmdz_48x36x39.tar.gz
\end{verbatim}

to create a new experiment:

\begin{verbatim}
mv BENCH48x36x39 BENCH48x36x39_old
tar -xf bench_lmdz_48x36x39.tar.gz 
cd BENCH48x36x39
\end{verbatim}

\item make sure that \verb+nday=1+ in \verb+run.def+
\item to avoid recompiling the code, just create a link to the executable you have 
already compiled before:
\begin{verbatim}
ln -s ../BENCH48x36x39_old/gcm.e .
\end{verbatim}

\item open the config.def files and after the section where the outputs are defined:

\begin{verbatim}
phys_out_filekeys=       y       y       y        y       n
phys_out_filenames=      histmth histday histhf   histins histLES
phys_out_filetimesteps=  5day    1day    1TS      6hr     6hr
phys_out_filelevels=     10      5       1        4       4
phys_out_filetypes=      ave(X)  ave(X)  inst(X) inst(X) inst(X)
\end{verbatim}

add these lines:

\begin{verbatim}
flag_vitu= 0 0 1 0 0
flag_vitv= 0 0 1 0 0
flag_du_gwd_hines= 0 0 1 0 0
flag_dv_gwd_hines= 0 0 1 0 0
flag_duoro= 0 0 1 0 0
flag_dvoro= 0 0 1 0 0
flag_dulif= 0 0 1 0 0
flag_dvlif= 0 0 1 0 0
flag_dthin= 0 0 1 0 0
flag_dtoro= 0 0 1 0 0
flag_dtlif= 0 0 1 0 0

ok_hines=y
\end{verbatim}

\item Run the model using \verb+./gcm.e > listing+.

\end{itemize}

\section{Optional: Running an aquaplanet configuration}

The simulations run in the previous example included initial and boundary
conditions (\infol{start*.nc} and \infol{limit.nc} files).
It is also possible to run the model in "aquaplanet" configuration, with
idealized initial and boundary conditions are used (no topography and
imposed surface temperatures).\newline


Make an \infol{AQUAPLANET} directory where you will run the model.
Copy over the \infol{gcm.e} and \infol{*.def} files from another simulation
to this directory. Edit the \infol{gcm.def} file to set 
\begin{verbatim}
read_start=n
iflag_phys=101
\end{verbatim}
Note that there are various possibilities for flag \infol{iflag\_phys},
values between 101 and 114 correspond to different choices
of imposed SSTs (see routines \infol{iniaqua} and \infol{profil\_sst} in
file \infol{phyaqua\_mod.F90} in the \infol{LMDZ/libf/phylmd}
directory).


Then run the model:
\begin{verbatim}
./gcm.e > listing 2>&1
\end{verbatim}
Inspect the various outputs (e.g. zonal averages and deviations of meteorological
quantities such as surface pressure $psol$) and their temporal evolution,
and compare to previously obtained simulations.
Experiment changing the length of the run (variable \infol{nday} in the
\infol{run.def} file to investigate the evolution of the system from
initial settings to a "converged" state.\newline


If time permits, experiment running at a different resolution (e.g.
\resol{96}{95}{39} ; which means you will have to recompile the model).
Note that the number of time steps per day depends on the model resolution, and
has to be higher for this resolution than it was strictly required for the \resol{48}{36}{39}
case. The gcm.def file you've used has already \infol{day\_step=480}, which is
enough, but you can check that the model will crash if you reduce it significantly (try it !).


\section{Optional: Switching to a different version of the model}

By using the installation script with option \verb+-v 20171119.trunk+,
the version dated November 19th 2017, which corresponds to {\em svn release}
3080 has been installed.
This information can moreover be obtained directly from within the LMDZ directory:
\begin{verbatim}
cd ~/LMDZ/LMDZ20171119.trunk/modipsl/modeles/LMDZ
svn info
\end{verbatim}
Note: you may encounter the following error when typing {\em svn info}:
\begin{verbatim}
svn: E155036: Voir la commande 'svn upgrade'
svn: E155036: The working copy at '/home/util1/LMDZ/LMDZtesting/modipsl/modeles/LMDZ'
is too old (format 10) to work with client version '1.8.8 (r1568071)' (expects format 31).
\end{verbatim}
If so, simply follow the suggested cure. Enter:
\verb+svn upgrade+.
Then try again \verb+svn info+.\\
%Similarly, for {\em trunk} versions, this information is available at the end
%of the file
%\begin{verbatim}
%http://www.lmd.jussieu.fr/~lmdz/Distrib/LISMOI.trunk
%\end{verbatim}
%Alternatively, same information is available on the following web page,
%dedicated to this branch:
%\begin{verbatim}
%http://lmdz.lmd.jussieu.fr/utilisateurs/distribution-du-modele/
%versions-intermediaires/versions-intermediaires-ou-testing-en?set_language=en
%\end{verbatim}

Using svn, it is possible to change from model version and select and older
or newer \verb+svn release+.
To change from current version to {\em svn release} 3069 (a previous version), go to directory \infol{LMDZ} and issue command:
\begin{verbatim}
svn update --revision 3069
\end{verbatim}
%Important: as you change svn revision, a conflict on a file (\infol{bld.cfg}) will occur,
%answer {\em tc} ('tc' for theirs-full) to tell svn you want to use the default version and not your own
%modifications\footnote{This conflict comes from the fact that the installation script
%{\em install\_lmdz.sh} adds a line in the \infol{bld.cfg} script and that
%there have also been some (harmless) changes of these very same lines between
%svn revisions of that file. Thus svn cannot know which modifications should
%overrule and thus asks you.}
%of the file.

In the \infol{LMDZ} directory, recompile LMDZ. To do so, run\footnote{To avoid typing such a long line over and over, it is more convenient to have it in a script, e.g. \infol{compile.sh} to execute each time a compilation is required.} \infol{./makelmdz\_fcm -arch local -j 8 -rrtm  true -d 48x36x39 -v orchidee2.0 -cpp ORCHIDEE\_NOZ0H gcm}\\
% (or alternatively \infol{./makelmdz -arch local -d 48x36x39 -rrtm  true -d 48x36x39 -v orchidee2.0 -cpp ORCHIDEE\_NOZ0H gcm}).\\
Options \infol{-v orchidee2.0 -cpp ORCHIDEE\_NOZ0H} is not mandatory. They only indicate that we compile with
Orchidee, but in fact, apart from the first bench, automatically launched by the
\verb+install_lmdz.sh+ script, it won't be used in this tutorial.
Only routines modified by the svn update or depending on them will be recompiled.\newline
%If using the \infol{makelmdz} script, it might be necessary to re-issue the command a second time\footnote{Having to sometimes run the \infol{makelmdz} command to create gcm.e comes from an (yet unresolved) issue in the script which fails to see some of the dependencies between source files} to generate the \infol{gcm.e} program.


Once the model has been successfully recompiled, run a new simulation.
To do so, create a new subdirectory in \infol{LMDZ} (e.g. \infol{BENCH48x36x39.3069}) and copy boundary
conditions, initial conditions and parameters files (\infol{limit.nc, start*nc, *.def}) over from
directory \infol{BENCH48x36x39}, along with the newly created gcm executable.\\
%If you used \infol{makelmdz}, it will be \infol{LMDZ/gcm.e}.\\
As you used  \infol{makelmdz\_fcm}, it will be \infol{LMDZ/bin/gcm\_48x36x39\_phylmd\_seq\_orch.e} and you should copy it over to the directory where you will run the model, e.g.:
\begin{verbatim}
cp LMDZ/bin/gcm_48x36x39_phylmd_seq_orch.e BENCH48x36x39.3069
\end{verbatim}

Then launch the run\footnote{As for the compilation step, this step can be put in a script, e.g. \infol{bench.sh}, as is the case in \infol{BENCH48x36x39}}:
\begin{verbatim}
./gcm.e > listing 2>&1
\end{verbatim}
Redirection of the model outputs in a text file is usually the best way to keep a trace of the run.\\

Once the simulation is finished, you can compare, using the \infol{diff}
command and visualisation software, the simulation results (compare files \infol{listing}, \infol{hist*.nc}
\infol{restart.nc} and \infol{restartphy.nc} from the two simulations) which
should be almost identical, except for some differences in the text outputs
and the fact that two variables (\infol{ALE\_WAKE} and \infol{ALE\_BL\_STAT} are not present in the \infol{restartphy.nc} file for svn revision 3069).
%The two LMDZ versions you used are not very different, as illustrated by the
%relatively low number of source files that have been updated when you run {\em  svn
%update}, but you can check it is already enough to explain that the numerical results differ.


Once this test finished, revert to the {\em trunk} 3080 version of the model
by going to directory \infol{LMDZ} and using:
\begin{verbatim}
svn update --revision 3080
\end{verbatim}
Note that using \infol{svn update} without any specific revision number implies
updating to the latest version on the branch (which is something you should do
regularly if you want to keep up with model updates). Don't forget to recompile
the model after any \infol{svn update}!


\end{document}



\begin{verbatim}
		lon: Longitude ;
		lat: Latitude ;
		presnivs: Vertical levels ;
		Ahyb: Ahyb comp of Hyb Cord ;
		Bhyb: Bhyb comp of Hyb Cord ;
		Alt: Height approx for scale heigh of 8km at levels ;
		t_ave_00864000: Time axis ;
		t_t_min_00864000: Time axis ;
		t_t_max_00864000: Time axis ;
		t_inst_00864000: Time axis ;
		aire: Grid area ;
		contfracATM: % sfce ter+lic ;
		phis: Surface geop.height ;
		contfracOR: % sfce terre OR ;
		aireTER: Grid area CONT ;
		flat: Latent heat flux ;
		slp: Sea Level Pressure ;
		tsol: Surface Temperature ;
		t2m: Temperature 2m ;
		t2m_min: Temp 2m min ;
		t2m_max: Temp 2m max ;
		wind10m: 10-m wind speed ;
		wind10max: 10m wind speed max ;
		sicf: Sea-ice fraction ;
		q2m: Specific humidity 2m ;
		u10m: Vent zonal 10m ;
		v10m: Vent meridien 10m ;
		psol: Surface Pressure ;
		qsurf: Surface Air humidity ;
		qsol: Soil watter content ;
		ndayrain: Number of dayrain(liq+sol) ;
		precip: Precip Totale liq+sol ;
		plul: Large-scale Precip. ;
		pluc: Convective Precip. ;
		snow: Snow fall ;
		msnow: Surface snow amount ;
		fsnow: Surface snow area fraction ;
		evap: Evaporat ;
		tops: Solar rad. at TOA ;
		tops0: CS Solar rad. at TOA ;
		topl: IR rad. at TOA ;
		topl0: IR rad. at TOA ;
		SWupTOA: SWup at TOA ;
		SWupTOAclr: SWup clear sky at TOA ;
		SWdnTOA: SWdn at TOA ;
		SWdnTOAclr: SWdn clear sky at TOA ;
		nettop: Net dn radiatif flux at TOA ;
		SWup200: SWup at 200mb ;
		SWup200clr: SWup clear sky at 200mb ;
		SWdn200: SWdn at 200mb ;
		SWdn200clr: SWdn clear sky at 200mb ;
		LWup200: LWup at 200mb ;
		LWup200clr: LWup clear sky at 200mb ;
		LWdn200: LWdn at 200mb ;
		LWdn200clr: LWdn clear sky at 200mb ;
		sols: Solar rad. at surf. ;
		sols0: Solar rad. at surf. ;
		soll: IR rad. at surface ;
		radsol: Rayonnement au sol ;
		soll0: IR rad. at surface ;
		SWupSFC: SWup at surface ;
		SWupSFCclr: SWup clear sky at surface ;
		SWdnSFC: SWdn at surface ;
		SWdnSFCclr: SWdn clear sky at surface ;
		LWupSFC: Upwd. IR rad. at surface ;
		LWdnSFC: Down. IR rad. at surface ;
		LWupSFCclr: CS Upwd. IR rad. at surface ;
		LWdnSFCclr: Down. CS IR rad. at surface ;
		bils: Surf. total heat flux ;
		sens: Sensible heat flux ;
		fder: Heat flux derivation ;
		ffonte: Thermal flux for snow melting ;
		fqcalving: Ice Calving ;
		fqfonte: Land ice melt ;
		taux: Zonal wind stress ;
		tauy: Meridional wind stress ;
		pourc_ter: % ter ;
		fract_ter: Fraction ter ;
		taux_ter: Zonal wind stresster ;
		tauy_ter: Meridional wind stress ter ;
		tsol_ter: Temperature ter ;
		u10m_ter: Vent Zonal 10m ter ;
		evap_ter: evaporation at surface ter ;
		v10m_ter: Vent meredien 10m ter ;
		t2m_ter: Temp 2m ter ;
		sens_ter: Sensible heat flux ter ;
		lat_ter: Latent heat flux ter ;
		flw_ter: LW ter ;
		fsw_ter: SW ter ;
		wbils_ter: Bilan sol ter ;
		wbilo_ter: Bilan eau ter ;
		albe_ter: Albedo VIS surf. ter ;
		rugs_ter: Surface roughness ter ;
		ages_ter: Snow age ;
		pourc_lic: % lic ;
		fract_lic: Fraction lic ;
		taux_lic: Zonal wind stresslic ;
		tauy_lic: Meridional wind stress lic ;
		tsol_lic: Temperature lic ;
		u10m_lic: Vent Zonal 10m lic ;
		evap_lic: evaporation at surface lic ;
		v10m_lic: Vent meredien 10m lic ;
		t2m_lic: Temp 2m lic ;
		sens_lic: Sensible heat flux lic ;
		lat_lic: Latent heat flux lic ;
		flw_lic: LW lic ;
		fsw_lic: SW lic ;
		wbils_lic: Bilan sol lic ;
		wbilo_lic: Bilan eau lic ;
		albe_lic: Albedo VIS surf. lic ;
		rugs_lic: Surface roughness lic ;
		ages_lic: Snow age ;
		pourc_oce: % oce ;
		fract_oce: Fraction oce ;
		taux_oce: Zonal wind stressoce ;
		tauy_oce: Meridional wind stress oce ;
		tsol_oce: Temperature oce ;
		u10m_oce: Vent Zonal 10m oce ;
		evap_oce: evaporation at surface oce ;
		v10m_oce: Vent meredien 10m oce ;
		t2m_oce: Temp 2m oce ;
		sens_oce: Sensible heat flux oce ;
		lat_oce: Latent heat flux oce ;
		flw_oce: LW oce ;
		fsw_oce: SW oce ;
		wbils_oce: Bilan sol oce ;
		wbilo_oce: Bilan eau oce ;
		albe_oce: Albedo VIS surf. oce ;
		rugs_oce: Surface roughness oce ;
		ages_oce: Snow age ;
		pourc_sic: % sic ;
		fract_sic: Fraction sic ;
		taux_sic: Zonal wind stresssic ;
		tauy_sic: Meridional wind stress sic ;
		tsol_sic: Temperature sic ;
		u10m_sic: Vent Zonal 10m sic ;
		evap_sic: evaporation at surface sic ;
		v10m_sic: Vent meredien 10m sic ;
		t2m_sic: Temp 2m sic ;
		sens_sic: Sensible heat flux sic ;
		lat_sic: Latent heat flux sic ;
		flw_sic: LW sic ;
		fsw_sic: SW sic ;
		wbils_sic: Bilan sol sic ;
		wbilo_sic: Bilan eau sic ;
		albe_sic: Albedo VIS surf. sic ;
		rugs_sic: Surface roughness sic ;
		ages_sic: Snow age ;
		alb1: Surface VIS albedo ;
		alb2: Surface Near IR albedo ;
		cdrm: Momentum drag coef. ;
		cdrh: Heat drag coef. ;
		cldl: Low-level cloudiness ;
		cldm: Mid-level cloudiness ;
		cldh: High-level cloudiness ;
		cldt: Total cloudiness ;
		cldq: Cloud liquid water path ;
		lwp: Cloud water path ;
		iwp: Cloud ice water path ;
		ue: Zonal energy transport ;
		ve: Merid energy transport ;
		uq: Zonal humidity transport ;
		vq: Merid humidity transport ;
		cape: Conv avlbl pot ener ;
		pbase: Cld base pressure ;
		ptop: Cld top pressure ;
		fbase: Cld base mass flux ;
		prw: Precipitable water ;
		cape_max: CAPE max. ;
		upwd: saturated updraft ;
		Ma: undilute adiab updraft ;
		dnwd: saturated downdraft ;
		dnwd0: unsat. downdraft ;
		mc: Convective mass flux ;
		ftime_con: Fraction of time convection Occurs ;
		s_pblh: Boundary Layer Height ;
		s_pblt: t at Boundary Layer Height ;
		s_lcl: Condensation level ;
		s_therm: Exces du thermique ;
		u850: Zonal wind 850 hPa ;
		v850: Meridional wind 850 hPa ;
		w850: Vertical wind 850 hPa ;
		z850: Geopotential height 850 hPa ;
		q850: Specific humidity 850 hPa ;
		t850: Temperature 850 hPa ;
		u700: Zonal wind 700 hPa ;
		v700: Meridional wind 700 hPa ;
		w700: Vertical wind 700 hPa ;
		z700: Geopotential height 700 hPa ;
		q700: Specific humidity 700 hPa ;
		t700: Temperature 700 hPa ;
		u500: Zonal wind 500 hPa ;
		v500: Meridional wind 500 hPa ;
		w500: Vertical wind 500 hPa ;
		z500: Geopotential height 500 hPa ;
		q500: Specific humidity 500 hPa ;
		t500: Temperature 500 hPa ;
		u200: Zonal wind 200 hPa ;
		v200: Meridional wind 200 hPa ;
		w200: Vertical wind 200 hPa ;
		z200: Geopotential height 200 hPa ;
		q200: Specific humidity 200 hPa ;
		t200: Temperature 200 hPa ;
		u100: Zonal wind 100 hPa ;
		v100: Meridional wind 100 hPa ;
		w100: Vertical wind 100 hPa ;
		z100: Geopotential height 100 hPa ;
		q100: Specific humidity 100 hPa ;
		t100: Temperature 100 hPa ;
		u50: Zonal wind 50  hPa ;
		v50: Meridional wind 50  hPa ;
		w50: Vertical wind 50  hPa ;
		z50: Geopotential height 50  hPa ;
		q50: Specific humidity 50  hPa ;
		t50: Temperature 50  hPa ;
		u10: Zonal wind 10  hPa ;
		v10: Meridional wind 10  hPa ;
		w10: Vertical wind 10  hPa ;
		z10: Geopotential height 10  hPa ;
		q10: Specific humidity 10  hPa ;
		t10: Temperature 10  hPa ;
		t_oce_sic: Temp mixte oce-sic ;
		weakinv: Weak inversion ;
		dthmin: dTheta mini ;
		rh2m: Relative humidity at 2m ;
		rh2m_min: Min Relative humidity at 2m ;
		rh2m_max: Max Relative humidity at 2m ;
		qsat2m: Saturant humidity at 2m ;
		tpot: Surface air potential temperature ;
		tpote: Surface air equivalent potential temperature ;
		SWnetOR: Sfce net SW radiation OR ;
		SWdownOR: Sfce incident SW radiation OR ;
		LWdownOR: Sfce incident LW radiation OR ;
		snowl: Solid Large-scale Precip. ;
		solldown: Down. IR rad. at surface ;
		dtsvdfo: Boundary-layer dTs(o) ;
		dtsvdft: Boundary-layer dTs(t) ;
		dtsvdfg: Boundary-layer dTs(g) ;
		dtsvdfi: Boundary-layer dTs(g) ;
		rugs: rugosity ;
		ec550aer: Extinction at 550nm ;
		lwcon: Cloud liquid water content ;
		iwcon: Cloud ice water content ;
		temp: Air temperature ;
		theta: Potential air temperature ;
		ovap: Specific humidity ;
		ovapinit: Specific humidity (begin of timestep) ;
		geop: Geopotential height ;
		vitu: Zonal wind ;
		vitv: Meridional wind ;
		vitw: Vertical wind ;
		pres: Air pressure ;
		paprs: Air pressure Inter-Couches ;
		mass: Masse Couches ;
		zfull: Altitude of full pressure levels ;
		zhalf: Altitude of half pressure levels ;
		rneb: Cloud fraction ;
		rnebcon: Convective Cloud Fraction ;
		rhum: Relative humidity ;
		ozone: Ozone mole fraction ;
		dtphy: Physics dT ;
		dqphy: Physics dQ ;
		cldtau: Cloud optical thickness ;
		cldemi: Cloud optical emissivity ;
		pr_con_l: Convective precipitation lic ;
		pr_con_i: Convective precipitation ice ;
		pr_lsc_l: Large scale precipitation lic ;
		pr_lsc_i: Large scale precipitation ice ;
		re: Cloud droplet effective radius ;
		fl: Denominator of Cloud droplet effective radius ;
		kz: Kz melange ;
		kz_max: Kz melange max ;
		clwcon: Convective Cloud Liquid water content ;
		dtdyn: Dynamics dT ;
		dqdyn: Dynamics dQ ;
		dudyn: Dynamics dU ;
		dvdyn: Dynamics dV ;
		dtcon: Convection dT ;
		ducon: Convection du ;
		dqcon: Convection dQ ;
		dtlsc: Condensation dT ;
		dtlschr: Large-scale condensational heating rate ;
		dqlsc: Condensation dQ ;
		dtvdf: Boundary-layer dT ;
		dqvdf: Boundary-layer dQ ;
		dteva: Reevaporation dT ;
		dqeva: Reevaporation dQ ;
		ptconv: POINTS CONVECTIFS ;
		ratqs: RATQS ;
		dtthe: Thermal dT ;
		dtajs: Dry adjust. dT ;
		dqajs: Dry adjust. dQ ;
		dtswr: SW radiation dT ;
		dtsw0: CS SW radiation dT ;
		dtlwr: LW radiation dT ;
		dtlw0: CS LW radiation dT ;
		dtec: Cinetic dissip dT ;
		duvdf: Boundary-layer dU ;
		dvvdf: Boundary-layer dV ;
		rsu: SW upward radiation ;
		rsd: SW downward radiation ;
		rlu: LW upward radiation ;
		rld: LW downward radiation ;
		rsucs: SW CS upward radiation ;
		rsdcs: SW CS downward radiation ;
		rlucs: LW CS upward radiation ;
		rldcs: LW CS downward radiation ;
		tnt: Tendency of air temperature ;
		tntc: Tendency of air temperature due to Moist Convection ;
		tntr: Air temperature tendency due to Radiative heating ;
		tntscpbl: Air temperature tendency due to St cloud and
precipitation and BL mixing ;
		tnhus: Tendency of specific humidity ;
		tnhusc: Tendency of specific humidity due to convection ;
		tnhusscpbl: Tendency of Specific humidity due to ST cl, precip
and BL mixing ;
		evu: Eddy viscosity coefficient for Momentum Variables ;
		h2o: Mass Fraction of Water ;
		mcd: Downdraft COnvective Mass Flux ;
		dmc: Deep COnvective Mass Flux ;
		ref_liq: Effective radius of convective cloud liquid water
particle ;
		ref_ice: Effective radius of startiform cloud ice particle ;
		RN: Tracer RNVL1 ;
		PB: Tracer PBVL1 ;

\end{verbatim}

