The run.def Input File - Revision history

Emillour at 08:47, 30 April 2025

2025-04-30T08:47:11Z

2024-10-18T16:43:22Z

‎Examples run.def for DYNAMCO: H&D link

2024-10-18T16:34:21Z

category dynamico

2024-10-18T16:32:25Z

2023-05-26T08:37:18Z

2023-05-26T08:21:23Z

2023-03-20T16:12:13Z

2023-03-09T10:24:38Z

2022-07-26T14:00:42Z

2022-07-26T13:43:05Z

‎Example of run.def file

@@ Line 111: / Line 111: @@
 # Use a regular grid
    grireg=.true.
 # longitude (degrees) of zoom center

@@ Line 174: / Line 174: @@
 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 DYNAMCO ==
+== Examples run.def for [[DYNAMICO]] ==
 * [[run.def for generic-DYNAMICO]]
 * [[run.def for Venus-DYNAMICO]]

@@ Line 45: / Line 45: @@
 # planet type
-planet_type = generic
+planet_type = generic # for pluto & exoplanets
 # Number of days to run model for
@@ Line 171: / Line 173: @@
 </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 1: / Line 1: @@
 == The run.def input file and its format ==
 The run.def file is a text file that is read at run time by the GCM (and must thus be present in the same directory as the executable).
 It contains the values of various parameters that the user can specify (as "key = value", where "key" is a predefined keyword and "value" may be a real, an integer, a string or a logical) and modify depending on the specific simulation that is intended, e.g. the line:
@@ Line 171: / Line 177: @@
 [[Category:Generic-LMDZ]]
 [[Category:Mars-LMDZ]]

@@ Line 6: / Line 6: @@
 planet_type = generic
 </pre>
-means that when the GCM will run, it will set parameter ''planet_type'' (which identifies the physics package that is used) to ''generic''.
+means that when the GCM will run, it will set parameter ''planet_type'' (which identifies the physics package that is used) to ''generic''. If using a different physics package, like the Mars one then ''planet_type'' should be adapted accordingly.
 Any line starting with # is a comment, e.g.
@@ Line 169: / Line 169: @@
 [[Category:WhatIs]]
-[[Category:Generic-LMDz]]
+[[Category:Generic-LMDZ]]

@@ Line 29: / Line 29: @@
 == 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).
 == Example of ''run.def'' file ==
@@ Line 158: / Line 155: @@
 </pre>
-'''Note''': Lines beginning with a hashtag are not read
+'''Notes''':