Mars 1D testphys1d program - Revision history

Jbclement at 10:55, 3 March 2026

2026-03-03T10:55:32Z

Jbclement: /* Inputs */

2026-02-26T09:48:07Z

‎Inputs

Jbclement: /* Inputs */

2026-02-26T09:34:15Z

‎Inputs

Jbclement: /* Inputs */

2026-02-26T09:33:04Z

‎Inputs

Emillour at 11:23, 20 February 2026

2026-02-20T11:23:33Z

Jbclement: /* Inputs */

2024-06-19T15:06:08Z

‎Inputs

Jbclement: Correction

2023-10-17T16:14:58Z

Correction

Jbclement: /* Inputs */

2023-10-17T16:12:24Z

‎Inputs

Jbclement: /* Outputs */

2023-10-17T16:12:14Z

‎Outputs

Jbclement: Update

2023-10-17T16:11:45Z

Update

@@ Line 23: / Line 23: @@
 In the case of <code>startfiles_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. If the starting files are present, it will read them to initialize the run accordingly. Otherwise, it will start as in the previous (default) case. In any cases, the program will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run.
-The file <code>start1D.txt</code> is specific to the 1D model. An example can be found in <code>LMDZ.MARS/deftank</code>. The content is organized such that each line holds a header, to make the file human readable, and then values.
+The file <code>start1D.txt</code> is specific to the 1D model. An example can be found in <code>LMDZ.MARS/startfiles</code>. The content is organized such that each line holds a header, to make the file human readable, and then values.
 * First line is for pressure variables with header '''ps''' and the values are ''ps'', ''pa'' and ''preff''.
 * The following lines define each tracer, in the same apparition order used in <code>traceur.def</code>. The header is the '''tracer name''' and the values are the ones for each atmospheric layer.

@@ Line 23: / Line 23: @@
 In the case of <code>startfiles_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. If the starting files are present, it will read them to initialize the run accordingly. Otherwise, it will start as in the previous (default) case. In any cases, the program will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run.
-The file <code>start1D.txt</code> is specific to the 1D model. An example can be found in <code>LMDZ.MARS/deftank</code>. The content is organized such that each line holds a header, to make the file human readable, and then values. First line is for pressure variables with header '''ps''' and the values are ''ps'', ''pa'' and ''preff''. The following lines account for each tracer, in the same apparition order used in <code>traceur.def</code>. The header is the '''tracer name''' and the values are the ones for each atmospheric layer. Next two lines are for winds. The headers are '''u''' and '''v''' for zonal and meridional wind respectively, and the values are the ones for each atmospheric layer. Last line is for potential temperature with header '''teta''' and values are the ones for each atmospheric layer.
+The file <code>start1D.txt</code> is specific to the 1D model. An example can be found in <code>LMDZ.MARS/deftank</code>. The content is organized such that each line holds a header, to make the file human readable, and then values.
 == Outputs ==

@@ Line 23: / Line 23: @@
 In the case of <code>startfiles_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. If the starting files are present, it will read them to initialize the run accordingly. Otherwise, it will start as in the previous (default) case. In any cases, the program will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run.
-The file <code>start1D.txt</code> is specific to the 1D model. An example can be found in <code>LMDZ.MARS/deftank</code>. The content is organized such that each line holds a header, to make the file human readable, and then values. First line is for pressure variables with header '''ps''' and the values are ''ps'', ''pa'' and ''preff''. The following lines account for each tracer, in the same apparition order used in <code>traceur.def</code>. The header is the '''tracer name''' and the values are the one for each atmospheric layer. Next two lines are for winds. The headers are '''u''' and '''v''' for zonal and meridional wind respectively, and the values are the one for each atmospheric layer. Last line is for potential temperature with header '''teta''' and values are the one for each atmospheric layer.
+The file <code>start1D.txt</code> is specific to the 1D model. An example can be found in <code>LMDZ.MARS/deftank</code>. The content is organized such that each line holds a header, to make the file human readable, and then values. First line is for pressure variables with header '''ps''' and the values are ''ps'', ''pa'' and ''preff''. The following lines account for each tracer, in the same apparition order used in <code>traceur.def</code>. The header is the '''tracer name''' and the values are the ones for each atmospheric layer. Next two lines are for winds. The headers are '''u''' and '''v''' for zonal and meridional wind respectively, and the values are the ones for each atmospheric layer. Last line is for potential temperature with header '''teta''' and values are the ones for each atmospheric layer.
 == Outputs ==

@@ Line 21: / Line 21: @@
 When the program ends, it will produce by its own a <code>startfi.nc</code> file initialized with the default settings.
-In the case of <code>startfiles_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. The latter is specific to the 1D model and an example can be found in <code>LMDZ.MARS/deftank</code>. If the starting files are present, it will read them to initialize the run accordingly and it will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run. If these starting files are not present, it will start as in the previous (default) case but it will still create the restarting files at the end.
+In the case of <code>startfiles_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. If the starting files are present, it will read them to initialize the run accordingly. Otherwise, it will start as in the previous (default) case. In any cases, the program will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run.
 == Outputs ==

@@ Line 17: / Line 17: @@
 * <code>run.def</code> for the run configuration, which is similar to the one for the 3D PCM described here [[The run.def Input File]]. It has to be be adapted to the 1D case. An example file, called <code>run.def.1d</code>, is available in <code>LMDZ.MARS/deftank</code>.
-Unlike the ''gcm'' program, the ''testphys1d'' program can run without starting files, that is without <code>startfi.nc</code> and <code>start.nc</code>. This is the case by default (<code>startfiles_1D=.false.</code>). However, in this setting, it needs the profiles of each tracer. They consist in files called ''profile_sometracername'' containing column-wise the initial values of the considered tracer. Then, the first line corresponds to the surface tracer and the following lines correspond to the layers. When the program ends, it will produce by its own a <code>startfi.nc</code> file initialized with the default settings.
+Unlike the ''gcm'' program, the ''testphys1d'' program can run without start files, that is without <code>startfi.nc</code> and <code>start.nc</code>.
 In the case of <code>startfiles_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. The latter is specific to the 1D model and an example can be found in <code>LMDZ.MARS/deftank</code>. If the starting files are present, it will read them to initialize the run accordingly and it will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run. If these starting files are not present, it will start as in the previous (default) case but it will still create the restarting files at the end.
 == Outputs ==

@@ Line 17: / Line 17: @@
 * <code>run.def</code> for the run configuration, which is similar to the one for the 3D PCM described here [[The run.def Input File]]. It has to be be adapted to the 1D case. An example file, called <code>run.def.1d</code>, is available in <code>LMDZ.MARS/deftank</code>.
-Unlike the ''gcm'' program, the ''testphys1d'' program can run without starting files, that is without <code>startfi.nc</code> and <code>start.nc</code>. This is the case by default (<code>startfile_1D=.false.</code>). However, in this setting, it needs the profiles of each tracer. They consist in files called ''profile_sometracername'' containing column-wise the initial values of the considered tracer. Then, the first line corresponds to the surface tracer and the following lines correspond to the layers. When the program, it will produce by its own a <code>startfi.nc</code> file initialized with the default settings.
+Unlike the ''gcm'' program, the ''testphys1d'' program can run without starting files, that is without <code>startfi.nc</code> and <code>start.nc</code>. This is the case by default (<code>startfiles_1D=.false.</code>). However, in this setting, it needs the profiles of each tracer. They consist in files called ''profile_sometracername'' containing column-wise the initial values of the considered tracer. Then, the first line corresponds to the surface tracer and the following lines correspond to the layers. When the program, it will produce by its own a <code>startfi.nc</code> file initialized with the default settings.
-In the case of <code>startfile_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. The latter is specific to the 1D model and an example can be found in <code>LMDZ.MARS/deftank</code>. If the starting files are present, it will read them to initialize the run accordingly and it will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run. If these starting files are not present, it will start as in the previous (default) case but it will still create the ''restart'' files at the end.
+In the case of <code>startfiles_1D=.true.</code> set in the <code>run.def</code>, the program will look for starting files, that is a <code>startfi.nc</code> file and a <code>start1D.txt</code> file. The latter is specific to the 1D model and an example can be found in <code>LMDZ.MARS/deftank</code>. If the starting files are present, it will read them to initialize the run accordingly and it will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run. If these starting files are not present, it will start as in the previous (default) case but it will still create the ''restart'' files at the end.
 == Outputs ==
 The program ''testphys1d'' can output <code>diagfi.nc</code> and <code>stats.nc</code> files. Just like for the 3D PCM model, the optional <code>diagfi.def</code> and <code>stats.def</code> files can be respectively added to specify which variables need be outputted.
-As described in the previous section, if <code>startfile_1D=.true.</code> in the <code>run.def</code>, then ''testphys1d'' will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run.
+As described in the previous section, if <code>startfiles_1D=.true.</code> in the <code>run.def</code>, then ''testphys1d'' will create a <code>restartfi.nc</code> file and a <code>restart1D.txt</code> file at the end of the run.
 This option is particularly useful when one wants to make chained simulations with the 1D model.
 [[Category:Mars-Model]]
 [[Category:Mars-1D]]

@@ Line 1: / Line 1: @@
-== Overview ==
+It is possible to run the Mars PCM in a "single-column" configuration: this is the so-called 1D Mars PCM whose program is '''testphys1d'''. It is quite useful for some studies and or when developing and testing parametrizations.
-== Compiling testphys1d ==
+== Compilation ==
-The main program ''testphys1d'' is compiled using the same compilation script [[The makelmdz fcm GCM Compilation Script|makelmdz_fcm]] than the 3D model except that:
+The main program '''testphys1d''' is compiled using the same compilation script, [[The makelmdz fcm GCM Compilation Script|makelmdz_fcm]], as for the 3D Mars PCM. Nevertheless, there are few modifications:
-* the ''-d'' option requires only one argument, the number of vertical levels
+* the ''-d'' option requires only one argument, the number of vertical levels;
-* the main program to compile is ''testphys1d'' rather than ''gcm''
+* the main program to compile is ''testphys1d'' rather than ''gcm''.
-So for instance to compile a case for 54 vertical levels one would run something like
+So for instance to compile a case for 54 vertical levels one would run something like:
 <syntaxhighlight lang="bash">
 makelmdz_fcm -arch somearch -d 54 -p mars testphys1d
 </syntaxhighlight>
-== testphys1d inputs ==
+== Inputs ==
-Just like the gcm the 1D model needs some inputs to run. The main difference is that it does not require a ''start'' (initial conditions) file. Some ''def'' files are however needed:
+Like the ''gcm'' program, the ''testphys1d'' program needs some inputs to be able to run. The needed files are:
-* z2sig.def : definition of vertical levels
+* <code>z2sig.def</code> for the definition of vertical levels;
-* traceur.def : definition of tracers the model will run with. Note that at run time testphys1d looks for optional ''profile_sometracername'' files which contain initial values (surface value on the first line and then one value for each layer to describe the profile) of the tracer quantities.
+* <code>traceur.def</code> for the definition of tracers that the user wants the model to run with;
-* callphys.def : definition of parametrizations to switch on (just like in the 3D PCM)
+* <code>callphys.def</code> for the definition of parametrizations that the user wants the model to run with;
-* run.def : the run configuration file; similar to the one for the 3D PCM described here [[The run.def Input File]], but adapted to the 1D case. Note that there is an example of a ''run.def'' file for testphys1d in LMDZ.MARS/deftank (file ''run.def.1d'')
+* <code>run.def</code> for the run configuration, which is similar to the one for the 3D PCM described here [[The run.def Input File]]. It has to be be adapted to the 1D case. An example file, called <code>run.def.1d</code>, is available in <code>LMDZ.MARS/deftank</code>.
-== testphys1d outputs ==
+== Outputs ==
-Testphys1d can output diagfi.nc and stats.nc files, and just like for the GCM optional ''diagfi.def'' and ''stats.def'' ASCII files can be used to specify which variable needs be outputted.
+The program ''testphys1d'' can output <code>diagfi.nc</code> and <code>stats.nc</code> files. Just like for the 3D PCM model, the optional <code>diagfi.def</code> and <code>stats.def</code> files can be respectively added to specify which variables need be outputted.
 [[Category:Mars-Model]]
 [[Category:Mars-1D]]