Difference between revisions of "Mars 1D testphys1d program"
(→Outputs) |
(→Inputs) |
||
| Line 16: | Line 16: | ||
* <code>callphys.def</code> for the definition of parametrizations that the user wants the model to run with; | * <code>callphys.def</code> for the definition of parametrizations that the user wants the model to run with; | ||
* <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>. | * <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>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. | ||
| + | |||
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>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. | ||
Revision as of 17:12, 17 October 2023
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.
Compilation
The main program testphys1d is compiled using the same 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 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:
makelmdz_fcm -arch somearch -d 54 -p mars testphys1d
Inputs
Like the gcm program, the testphys1d program needs some inputs to be able to run. The needed files are:
-
z2sig.deffor the definition of vertical levels; -
traceur.deffor the definition of tracers that the user wants the model to run with; -
callphys.deffor the definition of parametrizations that the user wants the model to run with; -
run.deffor 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, calledrun.def.1d, is available inLMDZ.MARS/deftank.
Unlike the gcm program, the testphys1d program can run without starting files, that is without startfi.nc and start.nc. This is the case by default (startfile_1D=.false.). 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 startfi.nc file initialized with the default settings.
In the case of startfile_1D=.true. set in the run.def, the program will look for starting files, that is a startfi.nc file and a start1D.txt file. The latter is specific to the 1D model and an example can be found in LMDZ.MARS/deftank. If the starting files are present, it will read them to initialize the run accordingly and it will create a restartfi.nc file and a restart1D.txt 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 diagfi.nc and stats.nc files. Just like for the 3D PCM model, the optional diagfi.def and stats.def files can be respectively added to specify which variables need be outputted.
As described in the previous section, if startfile_1D=.true. in the run.def, then testphys1d will create a restartfi.nc file and a restart1D.txt file at the end of the run.
This option is particularly useful when one wants to make chained simulations with the 1D model.
