1 | \chapter{1D version of the generic model} |
---|
2 | |
---|
3 | \label{sc:rcm1d} |
---|
4 | |
---|
5 | The physical part of the model can be used to run 1D radiative-convective simulations (one atmospheric column / globally averaged climate). In practice, the simulation is controlled from a main program called \verb+ rcm1d.F+ which, after initialization, then calls the master subroutine of the physics \verb+ physiq.F90+ described in the previous chapters. |
---|
6 | |
---|
7 | \section{Compilation} |
---|
8 | {\bf -} For example, to compile the generic model in 1D with 25 layers, type (in compliance with the makegcm function manual described in section \ref{sc:compil1}) |
---|
9 | |
---|
10 | \begin{verbatim} |
---|
11 | makegcm -d 25 -t 1 -b 32x36 -p std rcm1d |
---|
12 | \end{verbatim} |
---|
13 | |
---|
14 | You can find executable {\bf rcm1d.e} (the compiled model) |
---|
15 | in the directory from which you ran the makegcm command. |
---|
16 | |
---|
17 | \section{1-D runs and input files} |
---|
18 | |
---|
19 | The 1D model does not use an initial state file (the simulation must be long enough to obtain a balanced state). Thus, to generate a simulation simply type: |
---|
20 | |
---|
21 | \begin{verbatim} |
---|
22 | > rcm1d.e |
---|
23 | \end{verbatim} |
---|
24 | |
---|
25 | The following example files are available in the {\tt deftank} directory |
---|
26 | (copy them into your working directory first): |
---|
27 | |
---|
28 | - {\bf callphys.def}~: controls the options in the physics, |
---|
29 | just like for the 3D GCM. |
---|
30 | |
---|
31 | - {\bf z2sig.def}~: |
---|
32 | controls the vertical discretization |
---|
33 | (no change needed, in general), functions as with the 3D GCM. |
---|
34 | |
---|
35 | - {\bf traceur.def}~: |
---|
36 | controls the tracer names (this file may not be present, as long |
---|
37 | as you run without tracers (option {\tt tracer=.false.} in |
---|
38 | callphys.def) |
---|
39 | |
---|
40 | - {\bf run.def}~: controls the 1D run parameters and initializations |
---|
41 | (this is actually file {\tt run.def.1d} the {\tt deftank} directory, |
---|
42 | which must be renamed {\tt run.def} to be read by the program).\\ |
---|
43 | |
---|
44 | The last file is different from the 3D GCM's {\tt run.def} input file, |
---|
45 | as it contains options specific to the 1D model, as shown in the example |
---|
46 | below: |
---|
47 | \input{input/run.def.1d.tex} |
---|
48 | Note that, just as for the 3D GCM {\tt run.def} file, input |
---|
49 | parameters may be given in any order, or even not given at all |
---|
50 | (in which case default values are used by the program). |
---|
51 | |
---|
52 | |
---|
53 | \section{Output data} |
---|
54 | |
---|
55 | During the entire 1D simulation, you can obtain output data for any |
---|
56 | variable from any physical subroutine by using subroutine \verb+ writeg1d+. |
---|
57 | This subroutine creates file \verb+ g1d.nc+ that can be read by GRADS. |
---|
58 | This subroutine is typically called at the end of subroutine |
---|
59 | \verb+ physiq +. \\ |
---|
60 | |
---|
61 | Example of a call to subroutine {\tt writeg1d} requesting |
---|
62 | temperature output: |
---|
63 | (\verb+ ngrid+ horizontal point, \verb+ nlayer + layers, variable |
---|
64 | \verb+ pt + called ``T'' in K units): |
---|
65 | |
---|
66 | \begin{verbatim} |
---|
67 | CALL writeg1d(ngrid,nlayer,pt,'T','K') |
---|
68 | \end{verbatim} |
---|
69 | |
---|
70 | |
---|