Generic unicolumn rcm1d program - Revision history

Jbclement: /* Inputs */

2026-06-12T14:06:10Z

‎Inputs

Jbclement: /* Inputs */

2026-06-12T13:17:56Z

‎Inputs

Jbclement: /* Inputs */

2026-06-12T13:09:34Z

‎Inputs

Jbclement: /* Inputs */

2026-06-12T13:09:16Z

‎Inputs

Jbclement: /* Inputs */

2026-06-12T12:50:38Z

‎Inputs

Jbclement: /* Outputs */

2026-06-12T12:32:50Z

‎Outputs

Jbclement: /* Inputs */

2026-06-12T12:32:39Z

‎Inputs

Jbclement: /* Inputs */

2026-06-12T12:32:17Z

‎Inputs

Jbclement: /* Inputs */

2026-06-12T12:30:21Z

‎Inputs

Emillour: Created page with "It is possible to run the Gneric PCM in a uni-column (aka "single-column") configuration: this can be done via the '''rcm1d''' program; quite useful form some first studies bu..."

2026-05-15T09:52:32Z

Created page with "It is possible to run the Gneric PCM in a uni-column (aka "single-column") configuration: this can be done via the '''rcm1d''' program; quite useful form some first studies bu..."

New page

It is possible to run the Gneric PCM in a uni-column (aka "single-column") configuration: this can be done via the '''rcm1d''' program; quite useful form some first studies but also when developing and testing parametrizations.

== Compilation ==
The main program '''rcm1d''' is compiled using the same compilation script, [[The makelmdz fcm GCM Compilation Script|makelmdz_fcm]], as for the 3D Generic lon-lat PCM. Nevertheless, there are few modifications:
* the ''-d'' option requires only one argument, the number of vertical levels;
* the main program to compile is ''rcm1d'' rather than ''gcm''.
So for instance to compile a case for 26 vertical levels one would run something like:
<syntaxhighlight lang="bash">
makelmdz_fcm -arch somearch -d 26 -p generic rcm1d
</syntaxhighlight>
Note that it is possible to compile and run with the XIOS library, which will require compiling in "mpi" mode (required by XIOS), even though the run will be serial:
<syntaxhighlight lang="bash">
makelmdz_fcm -arch somearch -d 26 -p generic -parallel mpi -io xios rcm1d
</syntaxhighlight>

== Inputs ==
Just like the 3D GCM, the ''rcm1d'' program needs some inputs to run. The needed files are:
* <code>z2sig.def</code> for the definition of vertical levels;
* <code>traceur.def</code> for the definition of tracers 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>rcm1d.def</code> for the run configuration, which is similar to the 3D [[The run.def Input File|run.def]]; see [[The rcm1d.def Input File]]. In practice the <code>rcm1d.def</code> file is in fact copied as <code>run.def</code> by the rcm1d program when it runs.

Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart1D.nc''' which can be used as an initial condition for a following run.

If <code>restart=.true.</code> in <code>rcm1d.def</code> then the program will look for start files '''start1D.nc''' and '''startfi.nc''' and use these as initial conditions.

== Outputs ==
If compiled without XIOS then ''rcm1d'' will output <code>diagfi.nc</code> and <code>stats.nc</code> files, just like the 3D GCM and the optional <code>diagfi.def</code> and <code>stats.def</code> files can be respectively added to specify which variables need be outputted.
Likewise if compiled with XIOS then ''rcm1d'' will output all files as specified in the relevant xml files, just like the 3D GCM.

As mentioned above, at the end of a simulation <code>rcm1d</code> also outputs a '''restart1D.nc''' file containing the final computed state.

[[Category:Generic-Model]]
[[Category:Generic-1D]]

@@ Line 19: / Line 19: @@
 * <code>traceur.def</code> for the definition of tracers 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 suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the 1D file has to hold the key <code>run_1d=.true.</code>.
+* <code>run.def</code> for the run configuration, which is suitable for 1D: see [[The 1D run.def Input File]]. Especially, the 1D file has to hold the key <code>run_1d=.true.</code>.
 Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart.nc''' which can be used as an initial condition for a following run.

@@ Line 19: / Line 19: @@
 * <code>traceur.def</code> for the definition of tracers 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 suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the file has to hold the <code>run_1d=.true.</code> key.
+* <code>run.def</code> for the run configuration, which is suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the 1D file has to hold the key <code>run_1d=.true.</code>.
 Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart.nc''' which can be used as an initial condition for a following run.

@@ Line 19: / Line 19: @@
 * <code>traceur.def</code> for the definition of tracers 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 suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the file has to hold the <code>run_1d.def=.true.</code> key.
+* <code>run.def</code> for the run configuration, which is suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the file has to hold the <code>run_1d=.true.</code> key.
 Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart.nc''' which can be used as an initial condition for a following run.

@@ Line 19: / Line 19: @@
 * <code>traceur.def</code> for the definition of tracers 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 suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the file has to hold the 'run_1d.def=.true.' key.
+* <code>run.def</code> for the run configuration, which is suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the file has to hold the <code>run_1d.def=.true.</code> key.
 Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart.nc''' which can be used as an initial condition for a following run.

@@ Line 19: / Line 19: @@
 * <code>traceur.def</code> for the definition of tracers 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 suitable for 1D: see [[The rcm1d.def Input File]].
+* <code>run.def</code> for the run configuration, which is suitable for 1D: see [[The rcm1d.def Input File]]. Especially, the file has to hold the 'run_1d.def=.true.' key.
 Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart.nc''' which can be used as an initial condition for a following run.

@@ Line 29: / Line 29: @@
 Likewise if compiled with XIOS then ''rcm1d'' will output all files as specified in the relevant xml files, just like the 3D GCM.
-As mentioned above, at the end of a simulation <code>rcm1d</code> also outputs a '''restart1D.nc''' file containing the final computed state.
+As mentioned above, at the end of a simulation <code>rcm1d</code> also outputs a '''restart.nc''' file containing the final computed state.
 [[Category:Generic-Model]]
 [[Category:Generic-1D]]

@@ Line 21: / Line 21: @@
 * <code>run.def</code> for the run configuration, which is suitable for 1D: see [[The rcm1d.def Input File]].
-Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart1D.nc''' which can be used as an initial condition for a following run.
+Unlike the 3D GCMs, the ''rcm1d'' program can run without any start files, which is its default (<code>restart=.false.</code>). In this setup, one can (and often needs) needs to provide initial profiles of each tracer. These 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. At the end of a 1D simulation, ''rcm1d'' outputs a restart file '''restart.nc''' which can be used as an initial condition for a following run.
 If <code>restart=.true.</code> in <code>rcm1d.def</code> then the program will look for start files '''start.nc''' and '''startfi.nc''' and use these as initial conditions.