Other GCM Configurations worth knowing about - Revision history

Emillour at 09:58, 15 May 2026

2026-05-15T09:58:43Z

Emillour: /* Compiling a test case (TRAPPIST-1c) */

2026-02-23T10:51:03Z

‎Compiling a test case (TRAPPIST-1c)

Emillour at 08:15, 23 February 2026

2026-02-23T08:15:40Z

Emillour at 13:54, 4 February 2026

2026-02-04T13:54:51Z

Ptithib01: /* 3D DYNAMICO setup */

2025-12-02T13:06:02Z

‎3D DYNAMICO setup

Ptithib01: /* 3D DYNAMICO setup */

2025-12-02T11:02:45Z

‎3D DYNAMICO setup

Martin.turbet at 11:53, 3 April 2025

2025-04-03T11:53:07Z

Noe clement at 10:52, 5 March 2025

2025-03-05T10:52:16Z

Martin.turbet: /* rcm1d test case */

2025-03-05T09:46:28Z

‎rcm1d test case

Martin.turbet: /* rcm1d test case */

2025-03-05T09:44:34Z

‎rcm1d test case

@@ Line 679: / Line 679: @@
 TBC ML
-= 1D setup =
+= 1D setups =
-== rcm1d test case ==
+== rcm1d program ==
 Running the model in 1D (i.e. considering simply a column of atmosphere) is a common first step to test a new setup. To do so, you first have to compile the 1D version of the model. The command line is very similar to [[Quick_Install_and_Run#Compiling a test case (early Mars)|the one for the 3D]], except for 2 changes:
@@ Line 688: / Line 688: @@
 It will generate a file called '''rcm1d_XX_phyxxx_seq.e''', where ''XX'' and ''phyxxx'' are the vertical resolution and the physics package, respectively.
-Then, copy the executable in your working directory.
+Check out the [[Generic unicolumn rcm1d program| dedicated page about rcm1d]] for more details.
-Note that the '''.def''' files differ a bit from the 3D case: [[The_run.def_Input_File|'''run.def''']] is replaced with [[The_rcm1d.def_Input_File|'''rcm1d.def''']], which contains more general information. Indeed, the 1D model does not use [[The_start.nc_and_startfi.nc_input_files|'''start.nc''']] or [[The_start.nc_and_startfi.nc_input_files|'''startfi.nc''']] files to initialize. Instead it reads everything from the '''.def''' files. You can find examples of 1D configuration in ''LMDZ.GENERIC/deftank'' (e.g. '''rcm1d.def.earlymars''', '''rcm1d.def.earth'''), the best thing is to have a look at them.
+Note that the '''.def''' files differ a bit from the 3D case: [[The_run.def_Input_File|'''run.def''']] is replaced with [[The_rcm1d.def_Input_File|'''rcm1d.def''']], which contains more general information. Indeed, the 1D model generally does not use [[The_start.nc_and_startfi.nc_input_files|'''start.nc''']] or [[The_start.nc_and_startfi.nc_input_files|'''startfi.nc''']] files to initialize. You can find examples of 1D configuration in ''LMDZ.GENERIC/deftank'' (e.g. '''rcm1d.def.earlymars''', '''rcm1d.def.earth'''), the best thing is to have a look at them.
-== kcm1d test case ==
+== kcm1d program ==
 Our 1-D inverse model

@@ Line 179: / Line 179: @@
 * The planet is assumed to be in 1:1 spin-orbit resonance, therefore
-    Diurnal = .false.
+    diurnal = .false.
-    Tlocked = .true.
+    tlocked = .true.
 * The planet equilibrium temperature is about 342 K
     tplanet    = 341.9
-* The host star is a late spectral type M8V, with a stellar flux at 1 AU of 0.7527 [W m-2]
+* The host star is TRAPPIST1, with a stellar flux at 1 AU of 0.7527 [W m-2]
-    startype = 9
+    stelspec_file = spectrum_TRAPPIST1_2022.dat
     Fat1AU = 0.7527
 * Fixed aerosol distribution, no radiative active tracers (no evaporation/condensation of H2O and CO2):

@@ Line 207: / Line 207: @@
     aerovenusUV   = .true.
-The cloud model is prescribed from 1 to 0.037 ''bar'' pressure layers. For each mode, the top/bottom pressure can be modified by hard-coding model routine ''aeropacity.F90''.
+The cloud model is prescribed from 1 to 0.037 ''bar'' pressure layers. For each mode, the top/bottom pressure can be modified by hard-coding model routine ''aerosol_opacity.F90''.
 Here below an example for mode 1 particles, where the top pressure layer and bottom pressure layer are prescribed at 0.1 bar and 1 bar, respectively:

@@ Line 53: / Line 53: @@
 ==== Specific to photochemistry: set hard coded reactions ====
-In '''/LMDZ.GENERIC/libf/aeronostd/chimiedata_h.F90''' you can hard code reaction if needed, for instance because the reaction rate is very specific and out of the generic formula or your photochemical reaction does not use a regular cross section.
+In '''/LMDZ.GENERIC/libf/aeronogeneric/chimiedata_h.F90''' you can hard code reaction if needed, for instance because the reaction rate is very specific and out of the generic formula or your photochemical reaction does not use a regular cross section.
 The TRAPPIST-1e test case use 3 hard coded reactions.
@@ Line 289: / Line 289: @@
   <syntaxhighlight lang="bash">
 cd LMDZ.COMMON/
-     ./makelmdz_fcm -p std -p_opt "-b 20x25" -prod -parallel mpi -libphy -io xios -arch YOUR_ARCH_FILE -arch_path ../ARCH -j 8 -full
+     ./makelmdz_fcm -p generic -p_opt "-b 20x25" -prod -parallel mpi -libphy -io xios -arch YOUR_ARCH_FILE -arch_path ../ARCH -j 8 -full
 cd -
 </syntaxhighlight>
@@ Line 301: / Line 301: @@
   <syntaxhighlight lang="bash">
 cd ICOSA_LMDZ/
-     ./make_icosa_lmdz -p std -p_opt "-b 20x25" -parallel mpi -arch YOUR_ARCH_FILE -arch_path ../ARCH -job 8 -nodeps
+     ./make_icosa_lmdz -p generic -p_opt "-b 20x25" -parallel mpi -arch YOUR_ARCH_FILE -arch_path ../ARCH -job 8 -nodeps
 </syntaxhighlight>
 This last step is a bit redundant with the two previous one, hence ''make_icosa_lmdz'' will execute ''./make_icosa'' (in the '''ICOSAGCM''' directory) and ''./makelmdz_fcm'' (in the '''LMDZ.COMMON''' directory) to create and source the architecture files shared between all parts of the model, as well as create the intermediate file ''config.fcm''. As you have already compiled these two elements, ''make_icosa_lmdz'' should only create the linked architecture files, ''config.fcm'' and compile the interface. Here, ''-nodeps'' option prevents the checking of XIOS and IOIPSL compilation, which saves you from recompiling these two elements again.
@@ Line 310: / Line 310: @@
 All these compiling steps are summed up in ''make_isoca_lmdz'' program that should be adapted to your own computational settings (i.e., through you target architecture file).
   <syntaxhighlight lang="bash">
-./make_icosa_lmdz -p std -p_opt "-b 20x25" -parallel mpi -arch YOUR_ARCH_FILE -arch_path ../ARCH -job 8 -full
+./make_icosa_lmdz -p generic -p_opt "-b 20x25" -parallel mpi -arch YOUR_ARCH_FILE -arch_path ../ARCH -job 8 -full
 </syntaxhighlight>
 Here, ''-full'' option assure the compilation of each part ('''IOIPSL''', '''XIOS''', '''LMDZ.COMMON''', '''ICOSAGCM''' and '''ICOSA_LMDZ''') of the model.

@@ Line 310: / Line 310: @@
 All these compiling steps are summed up in ''make_isoca_lmdz'' program that should be adapted to your own computational settings (i.e., through you target architecture file).
   <syntaxhighlight lang="bash">
-./make_icosa_lmdz -p std -p_opt "-b 20x25 -s 2" -parallel mpi -arch YOUR_ARCH_FILE -arch_path ../ARCH -job 8 -full
+./make_icosa_lmdz -p std -p_opt "-b 20x25" -parallel mpi -arch YOUR_ARCH_FILE -arch_path ../ARCH -job 8 -full
 </syntaxhighlight>
 Here, ''-full'' option assure the compilation of each part ('''IOIPSL''', '''XIOS''', '''LMDZ.COMMON''', '''ICOSAGCM''' and '''ICOSA_LMDZ''') of the model.
@@ Line 317: / Line 317: @@
 Note: If you are using the GitLab file architecture (https://gitlab.in2p3.fr/aymeric.spiga/dynamico-giant), you should be able to compile the model directly from your working directory (for instance ''dynamico-giant/jupiter/'') by using the ''compile_occigen.sh'' program, which has to be adapted to your machine/cluster.
 == Jupiter with DYNAMICO ==

@@ Line 21: / Line 21: @@
 Section [https://lmdz-forge.lmd.jussieu.fr/mediawiki/Planets/index.php?title=Quick_Install_and_Run&action=edit&section=9 ''GCM Input Datafiles and Datasets''] download the TRAPPIST-1e files (instead of the early Mars files):
 <syntaxhighlight lang="bash">
-wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/planets/generic/bench_trappist1e_photochemistry_64x48x30_b38x36.tar.gz
+wget -nv --no-check-certificate https://web.lmd.jussieu.fr/~lmdz/planets/generic/reference_setups/bench_trappist1e_photochemistry_64x48x30_b38x36.tar.gz
 </syntaxhighlight>
@@ Line 165: / Line 165: @@
 <syntaxhighlight lang="bash">
-wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/planets/generic/bench_trappist1c_64x48x50_b32x36.tar.gz
+wget -nv --no-check-certificate https://web.lmd.jussieu.fr/~lmdz/planets/generic/reference_setups/bench_trappist1c_64x48x50_b32x36.tar.gz
 </syntaxhighlight>

@@ Line 630: / Line 630: @@
 == Proxima b with LES ==
-To model the subgrid atmospheric turbulence, the WRF dynamical core coupled with the LMD Generic physics package is used. The first studied conducted was to resolve the convective activity of the substellar point of Proxami-b (Lefevre et al 2021). The impact of the stellar insolation and rotation period were studied. The files for the reference case, with a stellar flux of 880 W/m2 and an 11 days rotation period, are presented
+To model the subgrid atmospheric turbulence, the [[WRF dynamical core for LES/mesoscale simulations|'''WRF''']] dynamical core coupled with the LMD Generic physics package is used. The first studied conducted was to resolve the convective activity of the substellar point of Proxami-b (Lefevre et al 2021). The impact of the stellar insolation and rotation period were studied. The files for the reference case, with a stellar flux of 880 W/m2 and an 11 days rotation period, are presented
 The input_* file are the used to initialize the temperature, pressure, winds and moisture of the domain.