Planets - User contributions [en]

Installing Titan mesoscale model on spirit

2026-02-26T14:56:30Z

Emoisan: /* Step by step */

== Install FCM ==

On your home, do:

<syntaxhighlight lang="Bash">
mkdir TOOLS
cd TOOLS
svn checkout https://forge.ipsl.jussieu.fr/fcm/svn/PATCHED/FCM_V1.2
cd
vi .bash_profile
</syntaxhighlight>

In your ~/.bash_profile, add:
<syntaxhighlight lang="Bash">
export PATH=$PATH:$HOME/TOOLS/FCM_V1.2/bin
</syntaxhighlight>

== Configure your ~/.bashrc ==
In your ~/bashrc, add:

<syntaxhighlight lang="Bash">
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

# User specific aliases and functions

ulimit -s unlimited

declare -x PATH=./:$PATH
declare -x WRFIO_NCD_LARGE_FILE_SUPPORT=1

module purge
module load intel/2021.4.0
module load intel-mkl/2020.4.304
module load openmpi/4.0.7
module load hdf5/1.10.7-mpi
module load netcdf-fortran/4.5.3-mpi
module load netcdf-c/4.7.4-mpi
declare -x WHERE_MPI=/net/nfs/tools/u20/22.3/PrgEnv/intel/linux-ubuntu20.04-zen2/openmpi/4.0.7-intel-2021.4.0-43fdcnab3ydwu7ycrplnzlp6xieusuz7/bin/
declare -x NETCDF=/scratchu/spiga/les_mars_project_spirit/netcdf_hacks/SPIRIT
declare -x NCDFLIB=$NETCDF/lib
declare -x NCDFINC=$NETCDF/include
</syntaxhighlight>

== Add private key ==
If you don't have one already, you need to add a private key file on your home, that corresponds to the public key file you have on GitLab.

To do this, put your id_rsa file in the directory ~/.ssh/.
Then, change the rights to the file, so that only you can access and read it:

<syntaxhighlight lang="Bash">
chmod go-r ~./ssh/id_rsa
</syntaxhighlight>

== Install the code ==

=== Load les_planet_workflow from Git ===
On one of the scratch disks (e.g. scratchu), do:

<syntaxhighlight lang="Bash">
git clone git@gitlab.in2p3.fr:aymeric.spiga/les_mars_project.git les_planet_workflow
</syntaxhighlight>

=== Create a new branch ===
In the les_planet_workflow directory, do:

<syntaxhighlight lang="Bash">
git branch new_branch
git checkout new_branch
</syntaxhighlight>

=== Adapt 0_defining file ===
Some lines are specific to the cluster, for SPIRIT:
<syntaxhighlight lang="Bash">
archname="ifort_MESOIPSL"
</syntaxhighlight>

Some lines are specific to Titan:
<syntaxhighlight lang="Bash">
version=tags/titan_les_compiles_and_runs_master_MESOIPSL # titan
physics=titan
add="-d 32x48x55 -s 1 -b 23x23 -cpp OLD_COMPILO" # titan
</syntaxhighlight>

/!\ The "inputs to script configure" depend on the version of WRF you use.

=== Run install.sh ===
<syntaxhighlight lang="Bash">
./install.sh
</syntaxhighlight>

== Run a simulation ==

=== Simple run ===

Go to a test directory, for instance:
<syntaxhighlight lang="Bash">
cd titan_pbl
</syntaxhighlight>

Adapt the simulation parameters in namelist.input (e.g. the duration of the simulation).

Update the GCM data path: in callphys.def, set datadir to the same path as the datadir defined in physiq.def (e.g. /data/mlefevre/SIMU/filephys/TITAN/datagcm).

Then initialize and launch the simulation:
<syntaxhighlight lang="Bash">
./ideal.exe
./wrf.exe
</syntaxhighlight>

=== Step by step ===

Go to a test directory, for instance:
<syntaxhighlight lang="Bash">
cd tests/test_folder
</syntaxhighlight>

* Adapt the simulation parameters in namelist.input (e.g. the duration of the simulation).
* Adapt the simulation parameters in callphys.def (e.g. the number of physical time steps between radiative time steps).
* Adapt the simulation parameters in input_bubble. If you do not want a bubble, set delt and bubble_addCH4 to 0.
* Adapt the simulation parameters in input_coords (longitude, latitude, Ls, local time).
* If you have the namelist option use_levels activated, check that the levels file is coherent with your number of vertical layers. If you want to create a new levels file, use the scripts in tests/zlevels_create_levels_file.
* Create the input_sounding and tracer_sounding files with gettitan_xarray.py:
<syntaxhighlight lang="Bash">
python3 gettitan_xarray.py
</syntaxhighlight>
* Check that symbolic links exist, otherwise create them by running ./make_symbolic_links.sh
* Initialize the simulation:
<syntaxhighlight lang="Bash">
./ideal.exe
</syntaxhighlight>
* Check rsl.out.0000 and rsl.error.0000. You should have "wrf: SUCCESS COMPLETE IDEAL INIT" written at the end.
* If you want to launch a Spirit job: adapt the simulation duration, memory, number of CPUs, ... in scriptlaunch
* Launch the simulation:
If you want to launch a Spirit job:
<syntaxhighlight lang="Bash">
./launch
</syntaxhighlight>
If you want to launch interactively on the console:
<syntaxhighlight lang="Bash">
./wrf.exe
</syntaxhighlight>

[[Category:Titan-Mesoscale]]
[[Category:Titan-Model]]

Installing Titan mesoscale model on spirit

2026-02-26T14:54:50Z

Emoisan:

== Install FCM ==

On your home, do:

<syntaxhighlight lang="Bash">
mkdir TOOLS
cd TOOLS
svn checkout https://forge.ipsl.jussieu.fr/fcm/svn/PATCHED/FCM_V1.2
cd
vi .bash_profile
</syntaxhighlight>

In your ~/.bash_profile, add:
<syntaxhighlight lang="Bash">
export PATH=$PATH:$HOME/TOOLS/FCM_V1.2/bin
</syntaxhighlight>

== Configure your ~/.bashrc ==
In your ~/bashrc, add:

<syntaxhighlight lang="Bash">
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

# User specific aliases and functions

ulimit -s unlimited

declare -x PATH=./:$PATH
declare -x WRFIO_NCD_LARGE_FILE_SUPPORT=1

module purge
module load intel/2021.4.0
module load intel-mkl/2020.4.304
module load openmpi/4.0.7
module load hdf5/1.10.7-mpi
module load netcdf-fortran/4.5.3-mpi
module load netcdf-c/4.7.4-mpi
declare -x WHERE_MPI=/net/nfs/tools/u20/22.3/PrgEnv/intel/linux-ubuntu20.04-zen2/openmpi/4.0.7-intel-2021.4.0-43fdcnab3ydwu7ycrplnzlp6xieusuz7/bin/
declare -x NETCDF=/scratchu/spiga/les_mars_project_spirit/netcdf_hacks/SPIRIT
declare -x NCDFLIB=$NETCDF/lib
declare -x NCDFINC=$NETCDF/include
</syntaxhighlight>

== Add private key ==
If you don't have one already, you need to add a private key file on your home, that corresponds to the public key file you have on GitLab.

To do this, put your id_rsa file in the directory ~/.ssh/.
Then, change the rights to the file, so that only you can access and read it:

<syntaxhighlight lang="Bash">
chmod go-r ~./ssh/id_rsa
</syntaxhighlight>

== Install the code ==

=== Load les_planet_workflow from Git ===
On one of the scratch disks (e.g. scratchu), do:

<syntaxhighlight lang="Bash">
git clone git@gitlab.in2p3.fr:aymeric.spiga/les_mars_project.git les_planet_workflow
</syntaxhighlight>

=== Create a new branch ===
In the les_planet_workflow directory, do:

<syntaxhighlight lang="Bash">
git branch new_branch
git checkout new_branch
</syntaxhighlight>

=== Adapt 0_defining file ===
Some lines are specific to the cluster, for SPIRIT:
<syntaxhighlight lang="Bash">
archname="ifort_MESOIPSL"
</syntaxhighlight>

Some lines are specific to Titan:
<syntaxhighlight lang="Bash">
version=tags/titan_les_compiles_and_runs_master_MESOIPSL # titan
physics=titan
add="-d 32x48x55 -s 1 -b 23x23 -cpp OLD_COMPILO" # titan
</syntaxhighlight>

/!\ The "inputs to script configure" depend on the version of WRF you use.

=== Run install.sh ===
<syntaxhighlight lang="Bash">
./install.sh
</syntaxhighlight>

== Run a simulation ==

=== Simple run ===

Go to a test directory, for instance:
<syntaxhighlight lang="Bash">
cd titan_pbl
</syntaxhighlight>

Adapt the simulation parameters in namelist.input (e.g. the duration of the simulation).

Update the GCM data path: in callphys.def, set datadir to the same path as the datadir defined in physiq.def (e.g. /data/mlefevre/SIMU/filephys/TITAN/datagcm).

Then initialize and launch the simulation:
<syntaxhighlight lang="Bash">
./ideal.exe
./wrf.exe
</syntaxhighlight>

=== Step by step ===

Go to a test directory, for instance:
<syntaxhighlight lang="Bash">
cd test_folder
</syntaxhighlight>

* Adapt the simulation parameters in namelist.input (e.g. the duration of the simulation).
* Adapt the simulation parameters in callphys.def (e.g. the number of physical time steps between radiative time steps).
* Adapt the simulation parameters in input_bubble. If you do not want a bubble, set delt and bubble_addCH4 to 0.
* Adapt the simulation parameters in input_coords (longitude, latitude, Ls, local time).
* If you have the namelist option use_levels activated, check that the levels file is coherent with your number of vertical layers. If you want to create a new levels file, use the scripts in tests/zlevels_create_levels_file.
* Create the input_sounding and tracer_sounding files with gettitan_xarray.py:
<syntaxhighlight lang="Bash">
python3 gettitan_xarray.py
</syntaxhighlight>
* Check that symbolic links exist, otherwise create them by running ./make_symbolic_links.sh
* Initialize the simulation:
<syntaxhighlight lang="Bash">
./ideal.exe
</syntaxhighlight>
* Check rsl.out.0000 and rsl.error.0000. You should have "wrf: SUCCESS COMPLETE IDEAL INIT" written at the end.
* If you want to launch a Spirit job: adapt the simulation duration, memory, number of CPUs, ... in scriptlaunch
* Launch the simulation:
If you want to launch a Spirit job:
<syntaxhighlight lang="Bash">
./launch
</syntaxhighlight>
If you want to launch interactively on the console:
<syntaxhighlight lang="Bash">
./wrf.exe
</syntaxhighlight>

[[Category:Titan-Mesoscale]]
[[Category:Titan-Model]]

Installing Titan mesoscale model on spirit

2026-02-26T14:49:00Z

Emoisan:

== Install FCM ==

On your home, do:

<syntaxhighlight lang="Bash">
mkdir TOOLS
cd TOOLS
svn checkout https://forge.ipsl.jussieu.fr/fcm/svn/PATCHED/FCM_V1.2
cd
vi .bash_profile
</syntaxhighlight>

In your ~/.bash_profile, add:
<syntaxhighlight lang="Bash">
export PATH=$PATH:$HOME/TOOLS/FCM_V1.2/bin
</syntaxhighlight>

== Configure your ~/.bashrc ==
In your ~/bashrc, add:

<syntaxhighlight lang="Bash">
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

# User specific aliases and functions

ulimit -s unlimited

declare -x PATH=./:$PATH
declare -x WRFIO_NCD_LARGE_FILE_SUPPORT=1

module purge
module load intel/2021.4.0
module load intel-mkl/2020.4.304
module load openmpi/4.0.7
module load hdf5/1.10.7-mpi
module load netcdf-fortran/4.5.3-mpi
module load netcdf-c/4.7.4-mpi
declare -x WHERE_MPI=/net/nfs/tools/u20/22.3/PrgEnv/intel/linux-ubuntu20.04-zen2/openmpi/4.0.7-intel-2021.4.0-43fdcnab3ydwu7ycrplnzlp6xieusuz7/bin/
declare -x NETCDF=/scratchu/spiga/les_mars_project_spirit/netcdf_hacks/SPIRIT
declare -x NCDFLIB=$NETCDF/lib
declare -x NCDFINC=$NETCDF/include
</syntaxhighlight>

== Add private key ==
If you don't have one already, you need to add a private key file on your home, that corresponds to the public key file you have on GitLab.

To do this, put your id_rsa file in the directory ~/.ssh/.
Then, change the rights to the file, so that only you can access and read it:

<syntaxhighlight lang="Bash">
chmod go-r ~./ssh/id_rsa
</syntaxhighlight>

== Install the code ==

=== Load les_planet_workflow from Git ===
On one of the scratch disks (e.g. scratchu), do:

<syntaxhighlight lang="Bash">
git clone git@gitlab.in2p3.fr:aymeric.spiga/les_mars_project.git les_planet_workflow
</syntaxhighlight>

=== Create a new branch ===
In the les_planet_workflow directory, do:

<syntaxhighlight lang="Bash">
git branch new_branch
git checkout new_branch
</syntaxhighlight>

=== Adapt 0_defining file ===
Some lines are specific to the cluster, for SPIRIT:
<syntaxhighlight lang="Bash">
archname="ifort_MESOIPSL"
</syntaxhighlight>

Some lines are specific to Titan:
<syntaxhighlight lang="Bash">
version=tags/titan_les_compiles_and_runs_master_MESOIPSL # titan
physics=titan
add="-d 32x48x55 -s 1 -b 23x23 -cpp OLD_COMPILO" # titan
</syntaxhighlight>

/!\ The "inputs to script configure" depend on the version of WRF you use.

=== Run install.sh ===
<syntaxhighlight lang="Bash">
./install.sh
</syntaxhighlight>

== Run a simulation ==

=== Simple run ===

Go to a test directory, for instance:
<syntaxhighlight lang="Bash">
cd titan_pbl
</syntaxhighlight>

Adapt the simulation parameters in namelist.input (e.g. the duration of the simulation).

Update the GCM data path: in callphys.def, set datadir to the same path as the datadir defined in physiq.def (e.g. /data/mlefevre/SIMU/filephys/TITAN/datagcm).

Then initialize and launch the simulation:
<syntaxhighlight lang="Bash">
./ideal.exe
./wrf.exe
</syntaxhighlight>

=== Step by step ===

Go to a test directory, for instance:
<syntaxhighlight lang="Bash">
cd test_folder
</syntaxhighlight>

# Adapt the simulation parameters in namelist.input (e.g. the duration of the simulation).
# Adapt the simulation parameters in callphys.def (e.g. the number of physical time steps between radiative time steps).
# Adapt the simulation parameters in input_bubble. If you do not want a bubble, set delt and bubble_addCH4 to 0.
# Adapt the simulation parameters in input_coords (longitude, latitude, Ls, local time).
# If you have the namelist option use_levels activated, check that the levels file is coherent with your number of vertical layers. If you want to create a new levels file, use the scripts in tests/zlevels_create_levels_file.
# Create the input_sounding and tracer_sounding files with gettitan_xarray.py:
<syntaxhighlight lang="Bash">
python3 gettitan_xarray.py
</syntaxhighlight>
# Check that symbolic links exist, otherwise create them by running ./make_symbolic_links.sh
# Initialize the simulation:
<syntaxhighlight lang="Bash">
./ideal.exe
</syntaxhighlight>
# Check rsl.out.0000 and rsl.error.0000. You should have "wrf: SUCCESS COMPLETE IDEAL INIT" written at the end.
# If you want to launch a Spirit job: adapt the simulation duration, memory, number of CPUs, ... in scriptlaunch
# Launch the simulation:
If you want to launch a Spirit job:
<syntaxhighlight lang="Bash">
./launch
</syntaxhighlight>
If you want to launch interactively on the console:
<syntaxhighlight lang="Bash">
./wrf.exe
</syntaxhighlight>

[[Category:Titan-Mesoscale]]
[[Category:Titan-Model]]

Quick Install and Run Titan PCM

2025-07-09T09:56:13Z

Emoisan: Created page with "In this page we give a hopefully exhaustive enough overview of the necessary prerequisites and steps to download, compile and run a simple simulation with the GCM on a Linux c..."

In this page we give a hopefully exhaustive enough overview of the necessary prerequisites and steps to download, compile and run a simple simulation with the GCM on a Linux computer.

Automating the process is not trivial as there are many subtle variants of Linux flavors and user account setups, so the script may fail in your case, but hopefully the information given in this page should help you solve the encountered problems.

== Prerequisites: Tools and Libraries ==
In order to use (i.e. compile and run) the GCM, one needs to have some tools and installed libraries at hand. We list below a (minimal) set that you should check that is available and/or that you'll need to first install on your machine. Note that we assume in this tutorial that you are on a Linux native-OS/cluster.

=== Fortran compiler ===
The GCM source code is in Fortran. One thus needs a Fortran compiler to build (compile) the executable.
The most easily available one (on Linux) is gfortran and examples discussed here will assume it is the one used.
You can check that you indeed have a gfortran compiler at hand with the following Bash command:
<syntaxhighlight lang="bash">
which gfortran
</syntaxhighlight>
which should return something like
<syntaxhighlight lang="bash">
/usr/bin/gfortran
</syntaxhighlight>

=== Subversion ===
The source code is managed using subversion (svn), which you'll need to download or update. Leaving aside the subtleties of svn and code organization for now, downloading the code amounts to doing the following:
<syntaxhighlight lang="bash">
svn checkout https://svn.lmd.jussieu.fr/Planeto/trunk --depth empty
cd trunk
svn update LMDZ.COMMON LMDZ.TITAN
</syntaxhighlight>

As a side note: the source code that will be fetched by svn can also be browsed online here: https://trac.lmd.jussieu.fr/Planeto

Note: if the command line above doesn't work, you may also try to replace 'http' by 'https'.

=== Git ===

Alternatively to svn, you can use [[Git usage|git to download the source code]].

=== FCM ===
The FCM (Flexible Configuration Management) tool is a suite of perl scripts to help building and managing codes. We use a slightly modified version which can be obtained using subversion (svn). Ideally you'll want to download it somewhere on your computer once in for all. To do this:
<syntaxhighlight lang="bash">
svn checkout https://forge.ipsl.jussieu.fr/fcm/svn/PATCHED/FCM_V1.2
</syntaxhighlight>
You'll then need to add the resulting FCM_V1.2/bin to your PATH environment variable so that the command "fcm" may be used from anywhere on your machine. e.g. by adding the following line in your .bashrc:
<syntaxhighlight lang="bash">
export PATH=$PATH:$HOME/FCM_V1.2/bin
</syntaxhighlight>
The assumption here is that the downloaded FCM_V1.2 directory is in your home ($HOME) directory. Adapt accordingly if not.

=== the NetCDF library ===
The GCM reads and writes input and output files in NetCDF format, therefore a NetCDF library is required. Most of the clusters propose a NetCDF library that you can load before using the model.

If this library is not available, you can install it by yourself on your system (check out [[the netCDF library]] page for more). You can use the following home-made "install_netcdf4_hdf5_seq.bash" script to do so. For this, ensure that you are in your home directory:
<syntaxhighlight lang="bash">
mkdir netcdf
cd netcdf
wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/script_install/install_netcdf4_hdf5_seq.bash
chmod u=rwx install_netcdf4_hdf5_seq.bash
./install_netcdf4_hdf5_seq.bash > netcdf.log 2>&1
</syntaxhighlight>
Compiling the library and dependencies can take a while (>>15 minutes; be patient).
Once this is done, check file netcdf.log to verify that all went well.
You may want to also add its "bin" directory to your PATH environment variable by adding in your .bashrc a line of:
<syntaxhighlight lang="bash">
export PATH=$PATH:$HOME/netcdf/bin
</syntaxhighlight>
The assumption here is that you have run the "install_netcdf4_hdf5_seq.bash" script in a "netcdf" subdirectory of your home directory. Adapt accordingly if not.

As a side note: The NetCDF library provides a very simple command line tool (ncdump) to inspect the contents of NetCDF files, but you'll need more advanced visualization tools (e.g., Panoply, Python scripts, etc. - see further down this page in the "Checking the Results" section) for more advanced post-processing of the outputs.

=== the IOIPSL library ===

The IOIPSL (Input/Output IPSL) library is designed to handle the reading of some input files used by the GCM (the *.def files which are described further below).

==== Automated IOIPSL install script ====
Scripts to download and install the IOIPSL library can be found in the "ioipsl" subdirectory of the "LMDZ.COMMON" library. Since here we assume we're working with gfortran, the relevant one is "install_ioipsl_gfortran.bash". If your PATH environment variable is already such that it includes the path to your NetCDF library distribution's bin directory (see previous section) then all you need to do is execute the script:
<syntaxhighlight lang="bash">
./install_ioipsl_gfortran.bash
</syntaxhighlight>
If all went well the script should end with:
<syntaxhighlight lang="bash">
OK: ioipsl library is in ...
</syntaxhighlight>

''(for further details about [[The_IOIPSL_Library|the IOIPSL library]] and installing it, follow the link and/or use the Search Box at the top of this page)''

=== The XIOS library ===
The Titan PCM uses the XIOS library to manage the outputs of the simulation. To install it, please refer to [[The_XIOS_Library|the XIOS libray]] page.

== GCM Input Datafiles and Datasets ==
In order to run, the GCM needs some inputs, such as initial conditions (values of state variables), external inputs (e.g. optical properties of aerosols) and simulation setup (e.g. specifications on how long to run, which parametrizations should be activated, etc.).

In the spirit of the illustrative example considered here, a set of necessary input data may be downloaded with:
<syntaxhighlight lang="bash">
wget -nv --no-check-certificate
https://web.lmd.jussieu.fr/~lmdz/planets/titan/bench_32x48x55.tar.gz
</syntaxhighlight>

The files needed to run are:
<syntaxhighlight lang="bash">
callphys.def gases.def start.nc startfi.nc traceur.def
datagcm/ run.def z2sig.def iodef.xml context_lmdz_physics.xml
</syntaxhighlight>
* Initial condition NetCDF files ''start.nc'' and ''startfi.nc''; the first containing initial condition values for the dynamics and the second initial condition values for the physics.
* A '''datadir''' directory containing external inputs (aerosol properties, stellar spectra, etc.)
* Some ASCII *.def files containing run parameters, namely:
# [[The_run.def_Input_File | run.def]] : "master def file" containing main run parameters. This file contains the number of days to run. For Titan years, weekly simulations of 11 days are used, except for the last two weeks which are 12 days long, so keep this in mind when setting your run files.
# [[The_callphys.def_Input_File | callphys.def]] : file containing flags and keys for the various physics parametrizations.
# [[The_z2sig.def_Input_File | z2sig.def]] : file describing the sought vertical discretization.
# [[The_traceur.def_Input_File | traceur.def]] : file specifying the tracer number and names.
# [[The_gases.def_Input_File | gases.def]] : file specifying the list of gases (main and trace) in the atmosphere.
# [[The_XIOS_Library#XIOS_output_controls|iodef.xml]] : master file read by XIOS containing specific XIOS parameters.
# [[The_XIOS_Library#XIOS_output_controls|context_lmdz_physics.xml ]]: file containing all fields/grid/file output definitions.

== Compiling the GCM ==
Now that all the prerequisites are fulfilled, it is (almost!) time to compile the GCM

=== Prior to a first compilation: setting up the target architecture files ===
Compiling the model is done using a dedicated Bash script ''makelmdz_fcm'' located in the '''LMDZ.COMMON''' directory. This script however relies on ''architecture files''. These files contain information on which compiler to use, what compilation options to use, where relevant libraries are located etc. In practice, one must thus create these ASCII text files in the '''arch/''' subdirectory of '''LMDZ.COMMON'''. The naming convention is rather straightforward, when the script ''makelmdz_fcm'' is run with the option '''-arch somename''', it will look for files ''arch/arch-somename.env'', ''arch/arch-somename.path'' and ''arch/arch-somename.fcm''. Leaving aside a detailed description for later (see [[The_Target_Architecture_("arch")_Files|this page]]), here we mention that:
* the ''arch*.env'' is an optional file containing ''environment'' information, such as setting up environment variables or loading modules on some machines, e.g.
<syntaxhighlight lang="bash">
export NETCDF_HOME=/path/to/the/netcdf/distribution
</syntaxhighlight>
A more realistic (but more specific) example of a '''arch*.env''' file using "recent" module commands, adapted for compilation and visualisation on a given supercomputer, would look more like the following:
<syntaxhighlight lang="bash">
module purge
module load GCC/10.3.0 OpenMPI/4.1.1
module load netCDF-Fortran/4.5.3
export NETCDF_INCDIR="/opt/ebsofts/netCDF-Fortran/4.5.3-gompi-2021a/include"
export NETCDFF_LIBDIR="/opt/ebsofts/netCDF-Fortran/4.5.3-gompi-2021a/lib"
</syntaxhighlight>
Note that the last two lines above specify paths to the '''include''' and '''lib''' directories used on this system and will certainly vary from system to system. Likewise, the exact module versions will most likely need to be adapted in your specific '''arch*.env''' file.
* the '''arch*.path''' is a mandatory file containing information relative to external libraries such as NetCDF and IOIPSL, e.g.
<syntaxhighlight lang="bash">
ROOT=$PWD

NETCDF_LIBDIR="-L${NETCDF_HOME}/lib"
NETCDF_LIB="-lnetcdf -lnetcdff"
NETCDF_INCDIR="-I${NETCDF_HOME}/include"

IOIPSL_INCDIR="-I$ROOT/../IOIPSL/inc"
IOIPSL_LIBDIR="-L$ROOT/../IOIPSL/lib"
IOIPSL_LIB="-lioipsl"
</syntaxhighlight>
Each library is referenced by a fixed identifier (NETCDF, IOIPSL, XIOS, ...) and 3 trailing strings: '''_LIBDIR''', for the path to the library, '''_LIB''', for the library name(s), and '''_INCDIR''' for the path to the library's ''include'' directory.

* the '''arch*.fcm''' is a mandatory file containing information relative to the compiler and compilation options, e.g.
<syntaxhighlight lang="bash">
%COMPILER gfortran
%LINK gfortran
%AR ar
%MAKE make
%FPP_FLAGS -P -traditional
%FPP_DEF NC_DOUBLE
%BASE_FFLAGS -c -fdefault-real-8 -fdefault-double-8 -ffree-line-length-none -fno-align-commons
%PROD_FFLAGS -O3
%DEV_FFLAGS -O
%DEBUG_FFLAGS -ffpe-trap=invalid,zero,overflow -fbounds-check -g3 -O0 -fstack-protector-all -finit-real=snan -fbacktrace
%MPI_FFLAGS
%OMP_FFLAGS
%BASE_LD
%MPI_LD
%OMP_LD
</syntaxhighlight>
Again, not going into a detailed description (follow [[The_Target_Architecture_("arch")_Files|this link]] for that), just note here that each line corresponds to a keyword (starting with "%") followed by the relevant options. Here, we mention a few of the main ones:
* %COMPILER: The compiler to use (here, gfortran)
* %BASE_FFLAGS: compiler options (always included)
* %PROD_FFLAGS: compilation flags to include if makelmdz_fcm is run with the "-prod" option
* %DEBUG_FFLAGS: compilation flags to include if makelmdz_fcm is run with the "-debug" option
* %BASE_LD: flags to add at the linking step of the compilation

Note that if you are using a recent version of gfortran (10 or more), you have to add an extra option in the %BASE_FFLAGS, that is '''-fallow-argument-mismatch'''

=== Compiling the Titan PCM ===
To compile the GCM at the sought resolution (in LMDZ.COMMON).
<syntaxhighlight lang="bash">

./makelmdz_fcm -arch local -parallel mpi -io xios -d 32x48x55 -b 23x23 -s 1 -p titan

</syntaxhighlight>
Here, we assume that you have generated the '''arch-local.*''' files as per what is suggested in the previous section, and that you will run in parallel using MPI.
The options for ''makelmdz_fcm'' used here imply:
* '''-p titan''': the GCM will use the "titan" physics package (i.e. the titan physics)
* '''-d 32x48x55''': the GCM grid will be 32x48 in longitude x latitude, with 55 vertical levels.
* '''-b 23x23''': the physics radiative transfer will be done using 23 bands in the IR and 23 in the visible.
* '''-io xios''': the GCM will use the XIOS library to write the output file.
For a glimpse at all the possible ''makelmdz_fcm'' options and their meanings, run:
<syntaxhighlight lang="bash">
./makelmdz_fcm -h
</syntaxhighlight>
and/or check the dedicated [[The_makelmdz_fcm_GCM_Compilation_Script|makelmdz_fcm page]].

Upon successful compilation, the executable '''gcm_32x48x55_phytitan_b23x23_para.e''' should be generated in the '''bin''' subdirectory.

To compile more efficiently in parallel, you may add “-j 8” to the compilation line.

=== Known issues ===

* Output frequency: not possible to have 24 outputs per Titan day (the model needs an integer number of seconds).

* The debug mode has problems in 1D, and in 3D with some optical diagnostics and microphysics schemes.

* If the compilation fails, it might be due to the options used in the arch file.
For example, if you are using gfortran prior to 10, you could get an error such as:
<pre>
gfortran: error: unrecognized command line option ‘-fallow-argument-mismatch’; did you mean ‘-Wno-argument-mismatch’?
</pre>
This can be solved by removing the option '''-fallow-argument-mismatch''' from the arch.fcm file.

* If you are using a recent version of gfortran (10 of beyond) without the option '''-fallow-argument-mismatch''', the compilation will probably fail ith the error:
<pre>
136 | . idim_index,nvarid)
| 2
......
211 | ierr = NF_DEF_VAR (nid, "aire", NF_DOUBLE, 2, id,nvarid)
| 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1)
fcm_internal compile failed (256)
</pre>
Add the compilation option in the arch file to solve the issue.

== Running the GCM ==
To run your first simulation, you need to first copy (or move) the executable '''gcm_32x48x55_phytitan_b23x23_para.e''' to the directory containing the initial conditions and parameter files, e.g. '''bench_titan_32x48x55_b23x23''' and run it.
This is usually a two-step process: the (optional) first step is to source the environment architecture file (the very same that was used to compile the model), e.g.,:
<syntaxhighlight lang="bash">
source ../LMDZ.COMMON/arch.env
</syntaxhighlight>
The second step is to execute the model, e.g.,:
<syntaxhighlight lang="bash">
./ gcm_32x48x55_phytitan_b23x23_para.e > gcm.out 2>&1
</syntaxhighlight>

With this command line, the (text) outputs messages are redirected into a text file, '''gcm.out'''. It is convenient to keep this file for later inspection (e.g., to track a bug). If there is no redirection (only '''./gcm_32x48x55_phytitan_b23x23_para.e'''), then the outputs will be directly on the screen.

== Checking the Results of a Simulation ==
Once the simulation is finished, you'll know that all went well ("everything is cool") if the last few lines of the standard text output reads:
<pre>
in abort_gcm
Stopping in leapfrog
Reason = Simulation finished
Everything is cool
</pre>

If not, start looking for an error message and a way to fix the problem...

Apart from the standard text output messages from the GCM, which are mostly for monitoring and checking the simulation progress, the user will more likely be interested in checking the contents of the NetCDF output file produced by the GCM with proper xios options, as it contains values of the main model variables (atmospheric temperature, winds, etc.).

Side note: There are a variety of freely available software that can be used to visualise the NetCDF output file, such as Panoply, Ferret, Ncview, Grads, Python, etc. (see more details in the [[Tool_Box | Tool Box section]])

== Taking Things to the Next Level ==
The short tutorial presented in this page is meant to be useful to get an overview of what is required to install and run the GCM, in addition to checking the results of a simulation. Moving on to a more intensive and problem-specific usage will require diving into additional topics and aspects such as:
* Selecting the appropriate inputs and run parameters for a given study.
* Post-processing and analysis of model outputs.
All these points and much more are detailed in the many pages of this site (do check out the menu on the left and dare use intensively the site's search engine)!

[[Category:Titan-Model]]
[[Category:Titan-LMDZ]]

Overview of the Titan PCM

2025-07-09T08:46:49Z

Emoisan:

== The Titan PCM (Planetary Climate Model) ==
In a nutshell, the Titan Planetary Climate Model is a General Circulation Model (GCM) of the titanian atmosphere. It is in fact a suite of models which may be run in various configurations: with the historical lon-lat (LMDz) dynamics, or as a regional model using [[WRF dynamical core for LES/mesoscale simulations|'''WRF''']] (a limited area dynamical core), or even as a 1D (single column) model.

== Getting started ==
The traditional Titan PCM - LMDz (formerly know as the IPSL Titan GCM) is the most commonly used version. For a first try at installing and running the Titan PCM we recommend you start from the [[Quick Install and Run Titan PCM]] page. You will also most likely be interested in all the pages tagged as "Titan-Model" or "Venus-LMDZ" in the [[Special:Categories|Categories]] section.

== Bibliography ==

==== 2025 ====
* Bruno De Batz De Trenquelléon, Lucie Rosset, Jan Vatant d’Ollone, Sébastien Lebonnois, Pascal Rannou, Jérémie Burgalat, et Sandrine Vinatier. « The New Titan Planetary Climate Model. I. Seasonal Variations of the Thermal Structure and Circulation in the Stratosphere ». The Planetary Science Journal 6, no 4 (1 avril 2025): 78. https://doi.org/10.3847/PSJ/adbbe7.
* Bruno De Batz De Trenquelléon, Pascal Rannou, Jérémie Burgalat, Sébastien Lebonnois, et Jan Vatant d’Ollone. « The New Titan Planetary Climate Model. II. Titan’s Haze and Cloud Cycles ». The Planetary Science Journal 6, no 4 (1 avril 2025): 79. https://doi.org/10.3847/PSJ/adbb6c.
==== 2020 ====
* Vatant d’Ollone, Jan. « Numerical modelling of the seasonal variations in Titan’s atmosphere ». These de doctorat, Sorbonne université, 2020. https://theses.fr/2020SORUS401.
==== 2019 ====
* Lora, J. M., T. Tokano, J. Vatant d'Ollone, S. Lebonnois, and R. D. Lorenz A model intercomparison of Titan's climate and low-latitude environment. Icarus, 333, 113. (2019) https://www.sciencedirect.com/science/article/pii/S0019103518307838?via%3Dihub
==== 2015 ====
* Charnay, Benjamin, Erika Barth, Scot Rafkin, Clément Narteau, Sébastien Lebonnois, Sébastien Rodriguez, Sylvain Courrech du Pont, et Antoine Lucas. « Methane Storms as a Driver of Titan’s Dune Orientation ». Nature Geoscience 8, no 5 (mai 2015): 362‑66. https://doi.org/10.1038/ngeo2406.
==== 2012 ====
* Lebonnois, Sébastien, Jérémie Burgalat, Pascal Rannou, et Benjamin Charnay. « Titan Global Climate Model: A New 3-Dimensional Version of the IPSL Titan GCM ». Icarus 218, no 1 (mars 2012): 707‑22. https://doi.org/10.1016/j.icarus.2011.11.032.
* Charnay, B. and S. Lebonnois Two boundary layers in Titan's lower troposphere inferred from a climate model. Nature Geoscience, 5, 106. (2012) https://www.nature.com/articles/ngeo1374

[[Category:Titan-Model]]

Overview of the Titan PCM

2025-07-09T08:43:05Z

Emoisan:

== The Titan PCM (Planetary Climate Model) ==
In a nutshell, the Titan Planetary Climate Model is a General Circulation Model (GCM) of the titanian atmosphere. It is in fact a suite of models which may be run in various configurations: with the historical lon-lat (LMDz) dynamics, or as a regional model using [[WRF dynamical core for LES/mesoscale simulations|'''WRF''']] (a limited area dynamical core), or even as a 1D (single column) model.

== Getting started ==
The traditional Titan PCM - LMDz (formerly know as the IPSL Titan GCM) is the most commonly used version. For a first try at installing and running the Titan PCM we recommend you start from the [[Quick Install and Run Titan PCM]] page. You will also most likely be interested in all the pages tagged as "Titan-Model" or "Venus-LMDZ" in the [[Special:Categories|Categories]] section.

== Bibliography ==

==== 2025 ====
* Bruno De Batz De Trenquelléon, Lucie Rosset, Jan Vatant d’Ollone, Sébastien Lebonnois, Pascal Rannou, Jérémie Burgalat, et Sandrine Vinatier. « The New Titan Planetary Climate Model. I. Seasonal Variations of the Thermal Structure and Circulation in the Stratosphere ». The Planetary Science Journal 6, no 4 (1 avril 2025): 78. https://doi.org/10.3847/PSJ/adbbe7.
* Bruno De Batz De Trenquelléon, Pascal Rannou, Jérémie Burgalat, Sébastien Lebonnois, et Jan Vatant d’Ollone. « The New Titan Planetary Climate Model. II. Titan’s Haze and Cloud Cycles ». The Planetary Science Journal 6, no 4 (1 avril 2025): 79. https://doi.org/10.3847/PSJ/adbb6c.
==== 2020 ====
* Vatant d’Ollone, Jan. « Numerical modelling of the seasonal variations in Titan’s atmosphere ». These de doctorat, Sorbonne université, 2020. https://theses.fr/2020SORUS401.
==== 2019 ====
* Lora, J. M., T. Tokano, J. Vatant d'Ollone, S. Lebonnois, and R. D. Lorenz A model intercomparison of Titan's climate and low-latitude environment. Icarus, 333, 113. (2019)
==== 2015 ====
* Charnay
==== 2012 ====
* Lebonnois, Sébastien, Jérémie Burgalat, Pascal Rannou, et Benjamin Charnay. « Titan Global Climate Model: A New 3-Dimensional Version of the IPSL Titan GCM ». Icarus 218, no 1 (mars 2012): 707‑22. https://doi.org/10.1016/j.icarus.2011.11.032.

[[Category:Titan-Model]]

Overview of the Titan PCM

2025-07-09T08:22:19Z

Emoisan:

Main Page

2025-07-09T08:13:23Z

Emoisan:

Welcome to the wiki of the Planetary Climate Models (PCM) family! Our numerical climate models cover a wide range of planets described below.

 

* '''With the [[Overview of the Generic PCM|Generic Models]]:'''
# Exoplanets of all kinds (rocky planets, super-Earths, mini-Neptunes, hot Jupiters, etc.)
# Paleoclimates of Solar System planets (e.g., to simulate lakes and glacier on Hesperian/Noachian Mars ; snowball episodes or exploring the Faint Young Sun on Earth ; formation and stability of early ocean on Venus ; episodes of atmospheric collapse on Titan)
# Giant planets (Jupiter, Saturn, Uranus, Neptune)
* '''With the [[Overview of the Mars PCM|Mars Models]]:'''
# Present-day Mars climate (with water and dust cycles)
# Recent-Mars paleoclimates (e.g., during Amazonian epoch, to simulate low and high-obliquity epochs)
# Regional and local weathers on Mars (e.g. to simulate weather near Mars rover landing sites)
* '''With the [[Overview of the Venus PCM|Venus models]]:'''
# Present-day Venus climate
# Regional weather on Venus (e.g. to simulate the convection in the cloud layer)
* '''With the [[Overview of the Titan PCM|Titan Models]]:'''
# Present-day Titan
# Regional and local weather on Titan
* '''With the [[Overview of the Pluto PCM|Pluto/Triton models]]:'''
# Present-day Pluto/Triton climate
# Long-term volatile/ice cycling on Pluto and Triton

 

 '''You can use the menu on the left to navigate across main webpages. For more specific needs, you can use the search bar (top right).''' 

 

Note that each wiki page has "categories" (visible at the bottom of the page) indicating the cases (planet, type of simulations) for which they apply. All existing categories are listed here: https://lmdz-forge.lmd.jussieu.fr/mediawiki/Planets/index.php/Special:Categories. For instance the category 'Generic-DYNAMICO' lists all the pages that apply to numerical climate simulations performed with the Generic PCM (for exoplanets, giant planets or paleoclimates) using the 3-D icosahedral dynamical core DYNAMICO; the 'DYNAMICO' category is focused on the dynamical core only (irrespective of the physics package it might be combined to) and the 'Mars-Mesoscale' category applies to the combined use of the Mars physics package and WRF (Mesoscale) dynamics.

Overview of the Titan PCM

2025-07-09T08:08:26Z

Emoisan: /* The Titan PCM (Planetary Climate Model) */

== The Titan PCM (Planetary Climate Model) ==

[[Category:Titan-Model]]

Overview of the Titan PCM

2025-07-09T08:07:53Z

Emoisan:

== The Titan PCM (Planetary Climate Model) ==

[[Category:Titan-Models]]

Overview of the Titan PCM

2025-07-09T08:07:05Z

Emoisan: /* The Titan PCM (Planetary Climate Model) */

== The Titan PCM (Planetary Climate Model) ==

[[Category:Titan-Model]]

Overview of the Titan PCM

2025-07-09T08:06:22Z

Emoisan: Created page with "== The Titan PCM (Planetary Climate Model) =="

== The Titan PCM (Planetary Climate Model) ==

The makelmdz fcm GCM Compilation Script

2025-03-11T14:32:18Z

Emoisan:

== Overview ==
The '''makelmdz_fcm''' script is the (bash) script (located in '''LMDZ.COMMON''' directory) to use to [[Quick_Install_and_Run#Compiling_the_GCM|compile the GCM]]. It is based on FCM and should be run, with various options (e.g which physics package to compile the model with, what grid resolution to use, etc.) to generate the sought executable.

== makelmdz_fcm options ==
To list available options, run "makelmdz_fcm -h", which should return something like:
<pre>
Usage :
makelmdz_fcm [options] -arch arch_name exec
[-h] : brief help
[-d [[IMx]JMx]LM] : IM, JM, LM are the dimensions in x, y, z (default: 96x72x19)
[-s nscat] : (Generic) Number of radiatively active scatterers
[-b IRxVIS] : (Generic) Number of infrared (IR) and visible (VIS) bands for radiative transfer
[-p PHYS] : set of physical parametrizations (in libf/phyPHYS), (default: lmd)
[-prod / -dev / -debug] : compilation mode production (default) / developement / debug .
[-c false/MPI1/OMCT] : (Earth) coupling with ocean model : MPI1/OMCT/false (default: false)
[-v false/orchidee2.0/orchidee1.9/true] : (Earth) version of the vegetation model to include (default: false)
false : no vegetation model
orchidee2.0 : compile using ORCHIDEE 2.0 (or more recent version)
orchidee1.9 : compile using ORCHIDEE up to the version including OpenMP in ORCHIDEE : tag 1.9-1.9.5(version AR5)-1.9.6
true : (obsolete; for backward compatibility) use ORCHIDEE tag 1.9-1.9.6
[-chimie INCA/false] : (Earth) with INCA chemistry model or without (default: false)
[-cosp true/false] : (Earth) add the cosp model (default: false)
[-sisvat true/false] : (Earth) compile with/without sisvat package (default: false)
[-rrtm true/false] : (Earth) compile with/without rrtm package (default: false)
[-dust true/false] : (Earth) compile with/without the dust package by Boucher and co (default: false)
[-strataer true/false] : (Earth) compile with/without the strat aer package by Boucher and co (default: false)
[-parallel none/mpi/omp/mpi_omp] : parallelism (default: none) : mpi, openmp or mixted mpi_openmp
[-g GRI] : grid configuration in dyn3d/GRI_xy.h (default: reg, inclues a zoom)
[-io ioipsl/mix/xios] : Input/Output library (default: ioipsl)
[-include INCLUDES] : extra include path to add
[-cpp CPP_KEY] : additional preprocessing definitions
[-adjnt] : adjoint model, not operational ...
[-mem] : reduced memory dynamics (if in parallel mode)
[-filtre NOMFILTRE] : use filtre from libf/NOMFILTRE (default: filtrez)
[-link LINKS] : additional links with other libraries
[-j n] : active parallel compiling on ntask
[-full] : full (re-)compilation (from scratch)
[-libphy] : only compile physics package (no dynamics or main program)
[-fcm_path path] : path to the fcm tool (default: tools/fcm/bin)
[-ext_src path] : path to an additional set of routines to compile with the model
[-arch_path path] : path to architecture files (default: arch)
-arch arch : target architecture
exec : executable to build
</pre>
Note that some options are meaningless for the Generic GCM. This is due to the fact that we try to coordinates tools like '''makelmdz_fcm''' between different physics packages.

The only mandatory argument are '''-arch''' and '''exec''', but in practice you'll need to specify many more (as defaults rarely suit all needs)

== Details of main makelmdz_fcm options ==
<pre>-d IMxJMxLM</pre>
As the default is to run on a fixed longitude-latitude grid (set when compiling), option "-d" is necessary to specify the number of grid points iimxjjmxlllm (actually iim is the number of intervals along longitude, jjm is the number of intervals along latitude and llm the number of atmospheric layers).

If compiling one of the 1D models, then only the number of layers (llm) needs be specified, e.g. <code>-d 78</code>.

<pre>-prod / -dev / -debug</pre>
Compilation mode. Default is <code>-prod</code>, i.e. "production" mode, where compiler optimization are on (as defined in the arch files; see [[The_Target_Architecture_("arch")_Files]] for details). When checking/debugging you definitely want to set <code>-debug</code>

<pre>-j n</pre>
With this option one can speed up compilation by letting <code>make</code> compile simultaneously (and if possible) up to <code>n</code> routines in parallel (note that this "parallel compilation" has nothing to do with the code being compiled for serial or parallel use as specified via option <code>-parallel ...</code>). In practice using <code>-j 8</code> or <code>-j 4</code> works well.

<pre>-parallel none/mpi/omp/mpi_omp</pre>
This option is to specify whether the model should be compiled in serial mode (default) or in parallel using MPI (<code>mpi</code>) only, or using OpenMP (<code>omp</code>) only, or both MPI and OpenMP (<code>mpi_omp</code>).

In practice, one most often needs to run in parallel and using both MPI and OpenMP, so <code>-parallel mpi_omp</code> is advised.

<pre>-io ioipsl/noioipsl/mix/xios</pre>
This option specifies which IO (Input/Output) library is going to be used by the model. Default is <code>-io ioipsl</code>, which is becoming depreciated for the GCM but mandatory for the 1D model. Note that when compiling with XIOS: <code>-io xios</code> on still needs to also use the IOIPSL library (which handles the reading of the run.def and companion files). It is also possible to compile without the IOISPL or XIOS libraries by specifying <code>-io noioipsl</code> (using an internal version of the getin() function from reading the *.def files; not recommended, but might help if building IOIPSL is a problem).

<pre>-libphy</pre>
With this option, only the physics package is compiled (the longitude-latitude dynamics routines are excluded) as a library, and no main program is generated. Building this library is a mandatory step to run with other dynamical cores like DYNAMICO or WRF.

<pre>-full</pre>
Impose a full cleanup (i.e. removing past object and library files) to ensure recompiling the model from scratch.

== Details of some specific makelmdz_fcm options ==
One chooses which physics package will be used using the
<pre>-p arg</pre>
option, where <code>arg</code> implies that the corresponding code will be found in '''LMDZ.COMMON/libf/phyarg''' and optionally also in '''LMDZ.COMMON/libf/aeronoarg'''. In practice these are just links to the package '''LMDZ.ARG/libf/phyarg''' and '''LMDZ.ARG/libf/aeronoarg''' (see [[LMDZ.COMMON directory layout and contents]], [[LMDZ.GENERIC directory layout and contents]], etc.).

=== Generic model specific options ===
To compile with the Generic physics package, the adequate argument to <code>-p</code> is <code>std</code>, i.e. corresponding code will be found in '''LMDZ.COMMON/libf/phystd''' and '''LMDZ.COMMON/libf/aeronostd''', which are simply links to '''LMDZ.GENERIC/libf/phystd''' and '''LMDZ.GENERIC/libf/aeronostd''':
<pre>-p std</pre>

Additional options one must provide when compiling with the Generic physics include:
<pre>-b IRxVIS</pre>
Number of bands in the InfraRed and Visible for the radiative transfer. Note that this requires that the corresponding appropriate input files are available (at run time).

=== Mars model specific options ===
To compile with the Mars physics package, the adequate argument to <code>-p</code> is <code>mars</code>, i.e. corresponding code will be found in '''LMDZ.COMMON/libf/phymars''' and '''LMDZ.COMMON/libf/aeronomars''', which are simply links to '''LMDZ.MARS/libf/phymars''' and '''LMDZ.MARS/libf/aeronomars''':
<pre>-p mars</pre>

=== Venus model specific options ===
To compile with the Venus physics package, the adequate argument to <code>-p</code> is <code>venus</code>, i.e. corresponding code will be found in '''LMDZ.COMMON/libf/phyvenus''', which is simply a link to '''LMDZ.VENUS/libf/phyvenus''':
<pre>-p venus</pre>

=== Titan model specific options ===
To compile with the Titan physics package, the adequate argument to <code>-p</code> is <code>titan</code>, i.e. corresponding code will be found in '''LMDZ.COMMON/libf/phytitan''', '''LLMDZ.COMMON/libf/muphytitan''' and '''LMDZ.COMMON/libf/chimtitan''', which are simply links to '''LMDZ.TITAN/libf/phytitan''', '''LMDZ.TITAN/libf/muphytitan''' and '''LMDZ.TITAN/libf/chimtitan''':
<pre>-p titan</pre>

[[Category:Generic-Model]]
[[Category:Mars-Model]]
[[Category:Venus-Model]]
[[Category:Titan-Model]]

Installing Titan mesoscale model on spirit

2024-01-05T14:29:50Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-05T14:28:54Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-05T14:27:31Z

Emoisan: /* Adapt 0_defining file. */

Installing Titan mesoscale model on spirit

2024-01-05T14:27:15Z

Emoisan: /* Create a new branch and adapt it to Titan */

Installing Titan mesoscale model on spirit

2024-01-05T14:26:52Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-05T14:26:06Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-02T14:47:32Z

Emoisan:

Category:Titan-Mesoscale

2024-01-02T14:46:26Z

Emoisan: Created page with "The pages in this category are related to the WRF Titan model."

The pages in this category are related to the WRF Titan model.

Installing Titan mesoscale model on spirit

2024-01-02T14:43:38Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-02T14:43:01Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-02T14:41:47Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-02T14:32:52Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-02T14:31:56Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-02T14:20:30Z

Emoisan:

Installing Titan mesoscale model on spirit

2024-01-02T14:20:05Z

Emoisan: Created page with "== Install FCM == On your home, do: <syntaxhighlight lang="Bash"> mkdir TOOLS cd TOOLS svn checkout https://forge.ipsl.jussieu.fr/fcm/svn/PATCHED/FCM_V1.2 cd vi .bash_profil..."