The rcm1d.def Input File - Revision history

Emillour at 13:09, 30 April 2025

2025-04-30T13:09:36Z

2025-03-05T09:56:59Z

2025-03-05T09:56:32Z

2025-03-05T09:56:10Z

‎Example of run.def file

2025-03-05T09:55:06Z

‎Example of run.def file

2025-03-05T09:54:44Z

‎Example of run.def file

2025-03-05T09:54:27Z

‎Example of run.def file

2025-03-05T09:54:17Z

‎Example of run.def file

2025-03-05T09:53:02Z

‎Outputted used_*def files

2025-03-05T09:52:24Z

@@ 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

@@ Line 51: / Line 51: @@
 day_step       = 40
 # Number of sols to run
-ndt            = 10000
+ndt            = 1000
 # Number of steps between each writting in diagfi
-ecritphy=400
+ecritphy=100

@@ Line 40: / Line 40: @@
 obliquit       = 0.
 ## SURFACE PRESSURE in Pa
-psurf          = 700000.
+psurf          = 100000.
 ## Time integration parameters

@@ Line 15: / Line 15: @@
 <pre>
-	#---------------------------------#
+#---------------------------------#
 # Run parameters for the 1D model #
 #---------------------------------#

@@ 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 these would be '''used_run.def''' and '''used_callphys.def'''). 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 ''run.def'' file ==

← Older revision		Revision as of 09:52, 5 March 2025
Line 5:		Line 5:

	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 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.
−
−	~~== *.def files included in run.def ==~~
−
−	~~The run.def file can include other files (based on the same format, lines containing "key = value" or comments) using the INCLUDEDEF keyword, e.g.:~~
−	~~<pre>~~
−	~~INCLUDEDEF=callphys.def~~
−	~~</pre>~~
−	This is a convenient way to separate related sets of parameters in separate files; common practice is to put dynamics related parameters in '''run.def''' and physics related parameters in '''callphys.def'''

	== Reference def files ==		== Reference def files ==