Quick Install and Run Venus PCM - Revision history

Emillour at 16:11, 10 April 2026

2026-04-10T16:11:22Z

Lebonnois at 12:13, 2 April 2026

2026-04-02T12:13:05Z

Lebonnois: updating the venus-inputs archive

2026-01-06T08:28:06Z

updating the venus-inputs archive

Lebonnois: /* Taking Things to the Next Level */

2025-08-13T09:02:45Z

‎Taking Things to the Next Level

Lebonnois: /* Taking Things to the Next Level */

2025-08-13T08:57:30Z

‎Taking Things to the Next Level

Lebonnois: /* Taking Things to the Next Level */

2025-08-13T08:55:09Z

‎Taking Things to the Next Level

Lebonnois: /* Taking Things to the Next Level */

2025-08-13T08:50:11Z

‎Taking Things to the Next Level

Lebonnois: /* Taking Things to the Next Level */

2025-08-13T08:45:36Z

‎Taking Things to the Next Level

Emillour: /* GCM Input Datafiles and Datasets */

2024-08-13T13:27:49Z

‎GCM Input Datafiles and Datasets

Emillour: /* FCM */

2024-06-12T10:33:35Z

‎FCM

@@ Line 4: / Line 4: @@
 Note that there is a dedicated, install script, that attempts to do all these steps (up to and including running the simulation) that you can obtain here: https://web.lmd.jussieu.fr/~lmdz/planets/install_lmdz_venus.bash
 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 ==

@@ Line 208: / Line 208: @@
 To run our reference simulation in 96x96x50 (no chemistry, limited to 95 km altitude), you can find here:
 * initial states: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/start-96x96x50.nc?ref_type=heads start-96x96x50.nc] and [https://web.lmd.jussieu.fr/~lmdz/planets/venus/startphy-96x96x50.nc?ref_type=heads startphy-96x96x50.nc]
-* needed inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/venus-inputs-Jan2026.tgz?ref_type=heads venus-inputs-Jan2026.tgz]
+* needed inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/venus-inputs-Avr2026.tgz?ref_type=heads venus-inputs-Avr2026.tgz]
 * readme for inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/readme-inputs.txt?ref_type=heads readme-inputs.txt]

@@ Line 208: / Line 208: @@
 To run our reference simulation in 96x96x50 (no chemistry, limited to 95 km altitude), you can find here:
 * initial states: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/start-96x96x50.nc?ref_type=heads start-96x96x50.nc] and [https://web.lmd.jussieu.fr/~lmdz/planets/venus/startphy-96x96x50.nc?ref_type=heads startphy-96x96x50.nc]
-* needed inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/venus-inputs-Mar2025.tgz?ref_type=heads venus-inputs-Mar2025.tgz]
+* needed inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/venus-inputs-Jan2026.tgz?ref_type=heads venus-inputs-Jan2026.tgz]
 * readme for inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/readme-inputs.txt?ref_type=heads readme-inputs.txt]

@@ Line 207: / Line 207: @@
 To run our reference simulation in 96x96x50 (no chemistry, limited to 95 km altitude), you can find here:
-* initial states: https://web.lmd.jussieu.fr/~lmdz/planets/venus/start-96x96x50.nc and https://web.lmd.jussieu.fr/~lmdz/planets/venus/startphy-96x96x50.nc
+* initial states: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/start-96x96x50.nc?ref_type=heads start-96x96x50.nc] and [https://web.lmd.jussieu.fr/~lmdz/planets/venus/startphy-96x96x50.nc?ref_type=heads startphy-96x96x50.nc]
-* needed inputs: https://web.lmd.jussieu.fr/~lmdz/planets/venus/venus-inputs-Mar2025.tgz
+* needed inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/venus-inputs-Mar2025.tgz?ref_type=heads venus-inputs-Mar2025.tgz]
-* readme for inputs: https://web.lmd.jussieu.fr/~lmdz/planets/venus/readme-inputs.txt
+* readme for inputs: [https://web.lmd.jussieu.fr/~lmdz/planets/venus/readme-inputs.txt?ref_type=heads readme-inputs.txt]
 For such a run, these features will be essential:

@@ Line 211: / Line 211: @@
 * readme for inputs: https://web.lmd.jussieu.fr/~lmdz/planets/venus/readme-inputs.txt
-For such a run, it will be crucial to:
+For such a run, these features will be essential:
 * Compiling and running in parallel (MPI) to run faster: [[Running the Venus PCM in parallel]]
 * Using [[The XIOS Library|the XIOS library]] (instead of IOIPSL) to handle PCM outputs: [[Managing the Venus PCM outputs]]

@@ Line 204: / Line 204: @@
 == 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:
+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.
-* Selecting the appropriate inputs and run parameters for a given study.
 * Compiling and running in parallel (MPI) to run faster: [[Running the Venus PCM in parallel]]
 * Running with advanced configurations of the physics packages, e.g. adding chemistry, thermospheric processes, etc.
-To run our reference simulation in 96x96x50 (no chemistry, limited to 95 km altitude), you can find here:
+* Selecting the appropriate inputs and run parameters for a given study.
 * Compiling and running with the other dynamical cores (DYNAMICO and WRF)
-* post-processing and analysis of model outputs.
+* 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:Venus-Model]]
 [[Category:Venus-LMDZ]]

@@ Line 98: / Line 98: @@
 wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/planets/venus/bench_48x32x50.tar.gz
 </syntaxhighlight>
-Note that this is a quite low resolution case, mostly for simple tests or checking that the model was well installed. For scientific work the model is typically run at higher resolution.
+Note that this is a quite low resolution case, mostly for simple tests or checking that the model was well installed. For scientific work the model is typically run at higher resolution (e.g. 96x96x50; in fact the same directory can be found a bench_96x96x50.tar.gz file).
 Nonetheless this ''bench_48x32x50'' example already provides insights on the required input files one needs:
@@ Line 104: / Line 104: @@
 * a ''z2sig.def'' ASCII file, which is read at runtime and contains information about the vertical levels of the PCM
 * a ''traceur.def'' ASCII file, which contains the list of tracers the PCM will use
-* a ''start.nc'' and a 'startphy.nc'' NetCDF files which respectively contain the initial conditions for the dynamics and the physics
+* a ''start.nc'' and a ''startphy.nc'' NetCDF files which respectively contain the initial conditions for the dynamics and the physics
 * Input datasets (read at run-time by the PCM) ''ksi_global.txt'' and ''SolarNetFlux_RH.dat''

@@ Line 33: / Line 33: @@
 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
+svn checkout https://forge.ipsl.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: