The rcm1d.def Input File - Revision history

Jbclement at 14:16, 12 June 2026

2026-06-12T14:16:02Z

Jbclement: Undo revision 3277 by Jbclement (talk)

2026-06-12T14:11:48Z

Undo revision 3277 by Jbclement (talk)

Jbclement: Undo revision 3278 by Jbclement (talk)

2026-06-12T14:11:32Z

Undo revision 3278 by Jbclement (talk)

Jbclement: /* some general comments and disambiguation to start with */

2026-06-12T13:16:22Z

‎some general comments and disambiguation to start with

Jbclement at 13:11, 12 June 2026

2026-06-12T13:11:19Z

Emillour at 13:09, 30 April 2025

2025-04-30T13:09:36Z

Martin.turbet at 09:56, 5 March 2025

2025-03-05T09:56:59Z

Martin.turbet at 09:56, 5 March 2025

2025-03-05T09:56:32Z

Martin.turbet: /* Example of run.def file */

2025-03-05T09:56:10Z

‎Example of run.def file

Martin.turbet: /* Example of run.def file */

2025-03-05T09:55:06Z

‎Example of run.def file

@@ Line 2: / Line 2: @@
 === some general comments and disambiguation to start with ===
-This pages specifically focuses on the ''rcm1d.def'' file used by the 1D version of the Generic PCM.
+This page specifically focuses on the old ''rcm1d.def'' file used by the 1D version of the Generic PCM. The new one is this one [[The_1D_run.def_Input_File|'''this one''']].
 The rcm1d.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file (in fact, rcm1d.def is copied to run.def during execution of the 1D model), with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the rcm1d.def file.

@@ Line 2: / Line 2: @@
 === some general comments and disambiguation to start with ===
-This pages specifically focuses on the ''run.def'' file used by the 1D version of the Generic PCM.
+This pages specifically focuses on the ''rcm1d.def'' file used by the 1D version of the Generic PCM.
-The run.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file, with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the 1D run.def file. Especially, the 1D file has to hold the <code>run_1d=.true.</code> key.
+The rcm1d.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file (in fact, rcm1d.def is copied to run.def during execution of the 1D model), with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the rcm1d.def file.
 == Reference def files ==
@@ Line 10: / Line 10: @@
 == Outputted used_*def files ==
-When the GCM run finishes, for each of the input def files *.def, an ASCII output file '''used_*.def''' is generated (in practice this would be '''used_run.def''' and '''used_callphys.def''' for the 1D simulations). These files contain, along the same format as the *.def input files, the "key = value" that were used, along with comments about whether "value" was read in the input def file or if the code default was used (i.e. the sought "keyword" was not present in the input def files).
+When the GCM run finishes, for each of the input def files *.def, an ASCII output file '''used_*.def''' is generated (in practice this would be '''used_rcm1d.def''' and '''used_callphys.def''' for the 1D simulations). These files contain, along the same format as the *.def input files, the "key = value" that were used, along with comments about whether "value" was read in the input def file or if the code default was used (i.e. the sought "keyword" was not present in the input def files).
-== Example of 1D ''run.def'' file ==
+== Example of ''rcm1d.def'' file ==
 <pre>
@@ Line 18: / Line 18: @@
 # Run parameters for the 1D model #
 #---------------------------------#
 ## Planetary constants
@@ Line 130: / Line 128: @@
 * The parsing is case-sensitive : "thisparameter=" and "ThisParameter=" are identified as two distinct keywords
 * The order in which the parameters are given in the file does not matter (except if a parameter is specified multiple times, clearly a bad idea, and then the last occurrence will prevail).
-* Accessing a parameter and its value from ''run.def'' in the Fortran code is done using the '''getin_p''' routine, e.g.:
+* Accessing a parameter and its value from ''rcm1d.def''/''run.def'' in the Fortran code is done using the '''getin_p''' routine, e.g.:
 <syntaxhighlight lang="fortran">
         call getin_p("keyword",val)

@@ Line 4: / Line 4: @@
 This pages specifically focuses on the ''run.def'' file used by the 1D version of the Generic PCM.
-The run.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file, with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the 1D run.def file. Especially, the 1D file has to hold the key <code>run_1d=.true.</code>.
+The run.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file, with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the 1D run.def file. Especially, the 1D file has to hold the <code>run_1d=.true.</code> key.
 == Reference def files ==

@@ Line 4: / Line 4: @@
 This pages specifically focuses on the ''run.def'' file used by the 1D version of the Generic PCM.
-The run.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file, with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the 1D run.def file. Especially, the 1D file has to hold the <code>run_1d=.true.</code> key.
+The run.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file, with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the 1D run.def file. Especially, the 1D file has to hold the key <code>run_1d=.true.</code>.
 == Reference def files ==

@@ Line 2: / Line 2: @@
 === some general comments and disambiguation to start with ===
-This pages specifically focuses on the ''rcm1d.def'' file used by the 1D version of the Generic PCM.
+This pages specifically focuses on the ''run.def'' file used by the 1D version of the Generic PCM.
-The rcm1d.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file (in fact, rcm1d.def is copied to run.def during execution of the 1D model), with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the rcm1d.def file.
+The run.def file is very similar to the [[The_run.def_Input_File|'''run.def''']] file, with the difference that the 3D options (linked to the dynamic core) are not used, and a whole bunch of new 1D-specific options (information contained in the start and startfi files) are now in the 1D run.def file. Especially, the 1D file has to hold the <code>run_1d=.true.</code> key.
 == Reference def files ==
@@ Line 10: / Line 10: @@
 == Outputted used_*def files ==
-When the GCM run finishes, for each of the input def files *.def, an ASCII output file '''used_*.def''' is generated (in practice this would be '''used_rcm1d.def''' and '''used_callphys.def''' for the 1D simulations). These files contain, along the same format as the *.def input files, the "key = value" that were used, along with comments about whether "value" was read in the input def file or if the code default was used (i.e. the sought "keyword" was not present in the input def files).
+When the GCM run finishes, for each of the input def files *.def, an ASCII output file '''used_*.def''' is generated (in practice this would be '''used_run.def''' and '''used_callphys.def''' for the 1D simulations). These files contain, along the same format as the *.def input files, the "key = value" that were used, along with comments about whether "value" was read in the input def file or if the code default was used (i.e. the sought "keyword" was not present in the input def files).
-== Example of ''rcm1d.def'' file ==
+== Example of 1D ''run.def'' file ==
 <pre>
@@ Line 18: / Line 18: @@
 # Run parameters for the 1D model #
 #---------------------------------#
 ## Planetary constants
@@ Line 128: / Line 130: @@
 * The parsing is case-sensitive : "thisparameter=" and "ThisParameter=" are identified as two distinct keywords
 * The order in which the parameters are given in the file does not matter (except if a parameter is specified multiple times, clearly a bad idea, and then the last occurrence will prevail).
-* Accessing a parameter and its value from ''rcm1d.def''/''run.def'' in the Fortran code is done using the '''getin_p''' routine, e.g.:
+* Accessing a parameter and its value from ''run.def'' in the Fortran code is done using the '''getin_p''' routine, e.g.:
 <syntaxhighlight lang="fortran">
         call getin_p("keyword",val)

@@ Line 52: / Line 52: @@
 # Number of sols to run
 ndt            = 1000
-# Number of steps between each writting in diagfi
+# Number of steps between each writing in diagfi
-ecritphy=100
+diagfi_output_rate=12
@@ Line 138: / Line 138: @@
 [[Category:Generic-LMDZ]]

@@ Line 133: / Line 133: @@
 </syntaxhighlight>
 will look for the line with "keyword = " in file ''run.def'' and extract trailing value which will be use to set the value of the  '''val''' variable in the code.
 [[Category:Inputs]]
@@ Line 147: / Line 138: @@
 [[Category:Generic-LMDZ]]

@@ Line 12: / Line 12: @@
 When the GCM run finishes, for each of the input def files *.def, an ASCII output file '''used_*.def''' is generated (in practice this would be '''used_rcm1d.def''' and '''used_callphys.def''' for the 1D simulations). These files contain, along the same format as the *.def input files, the "key = value" that were used, along with comments about whether "value" was read in the input def file or if the code default was used (i.e. the sought "keyword" was not present in the input def files).
-== Example of ''run.def'' file ==
+== Example of ''rcm1d.def'' file ==
 <pre>
@@ Line 134: / Line 134: @@
 will look for the line with "keyword = " in file ''run.def'' and extract trailing value which will be use to set the value of the  '''val''' variable in the code.
-== Examples run.def for [[DYNAMICO]] ==
+== Examples rcm1d.def for [[DYNAMICO]] ==
 * [[run.def for Held&Suarez test case]]

@@ Line 78: / Line 78: @@
 cpp            = 0.
 # Molecular mass in g mol-1 [only used if force_cpp = T]
-mugaz          = 0.
+mugaz          = 18.
 # Albedo of bare ground
 albedo         = 0.1