Ignore:
Timestamp:
Jul 13, 2011, 10:38:37 PM (13 years ago)
Author:
aslmd
Message:

MESOSCALE: user manual. a small bug fix to the previous commit. sorry.

Location:
trunk/MESOSCALE_DEV/MANUAL/SRC
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/MESOSCALE_DEV/MANUAL/SRC/preproc.tex

    r220 r221  
    110110\end{center}
    111111
    112 \end{document}
    113112
    114 \mk
    115 \subsubsection{Meteorological data}
     113\clearemptydoublepage
    116114
    117 \ttt{launch\_gcm}
    118 
    119 \mk
    120 The preprocessing tools generate initial and boundary conditions
    121 from the \ttt{diagfi.nc} outputs of LMD-MGCM simulations.
    122 %
    123 If you would like to run a mesoscale simulation at a given
    124 season, you need to first run a GCM simulation and output
    125 the meteorological fields at the considered season.
    126 %
    127 For optimal forcing at the boundaries, we advise you
    128 to write the meteorological fields to the
    129 \ttt{diagfi.nc} file at least each two hours.
    130 %
    131 Please also make sure that the following fields
    132 are stored in the NETCDF \ttt{diagfi.nc} file:
    133 
    134 \footnotesize
    135 \codesource{contents_diagfi}
    136 
    137 \normalsize
    138 \begin{finger}
    139 \item If the fields
    140 \ttt{emis},
    141 \ttt{co2ice},
    142 \ttt{q01},
    143 \ttt{q02},
    144 \ttt{tsoil}
    145 are missing in the \ttt{diagfi.nc} file,
    146 they are replaced by respective default
    147 values $0.95$, $0$, $0$, $0$, tsurf.
    148 \end{finger}
    149 
    150 \mk
    151 \marge An example of input meteorological file
    152 \ttt{diagfi.nc} file can be downloaded
    153 at \url{http://web.lmd.jussieu.fr/~aslmd/LMD_MM_MARS/diagfi.nc.tar.gz}.
    154 %
    155 Please deflate the archive and copy the \ttt{diagfi.nc} file
    156 in \ttt{\$LMDMOD/TMPDIR/GCMINI}.
    157 %
    158 Such a file can then be used to define the initial
    159 and boundary conditions, and we will go
    160 through the three preprocessing steps.
    161 
    162 \mk
    163 \subsection{Preprocessing steps}
    164 
    165 \mk
    166 \subsubsection{Step 1: Converting GCM data}
    167 
    168 \mk
    169 The programs in the \ttt{PREP\_MARS} directory
    170 convert the data from the NETCDF \ttt{diagfi.nc}
    171 file into separated binary datafiles for each
    172 date contained in \ttt{diagfi.nc}, according to
    173 the formatting needed by the
    174 preprocessing programs at step 2.
    175 %
    176 These programs can be executed by the following
    177 commands:
    178 \begin{verbatim}
    179 cd $LMDMOD/LMD_MM_MARS/your_install_dir/PREP\_MARS
    180 echo 1 | ./create_readmeteo.exe     # drop the "echo 1 |" if you want control
    181 ./readmeteo.exe < readmeteo.def
    182 \end{verbatim}
    183 %
    184 \marge If every went well with the conversion,
    185 the directory \ttt{\$LMDMOD/TMPDIR/WPSFEED}
    186 should contain files named \ttt{LMD:}.
    187 
    188 \mk
    189 \subsubsection{2: Interpolation on the regional domain}
    190 
    191 \mk
    192 In the \ttt{WPS} directory, the \ttt{geogrid.exe} program allows
    193 you to define the mesoscale simulation domain
    194 to horizontally interpolate the topography,
    195 thermal inertia and albedo fields at the domain
    196 resolution and to calculate useful fields
    197 such as topographical slopes.%\pagebreak
    198 
    199 \mk
    200 \marge Please execute the commands:
    201 %
    202 \begin{verbatim}
    203 cd $LMDMOD/LMD_MM_MARS/your_install_dir/WPS
    204 ln -sf ../../TESTCASE/namelist.wps .   # test case
    205 ./geogrid.exe
    206 \end{verbatim}
    207 %
    208 \marge The result of \ttt{geogrid.exe}
    209 -- and thus the definition of the mesoscale
    210 domain -- can be checked in the NETCDF
    211 file \ttt{geo\_em.d01.nc}.
    212 %
    213 A quick check can be performed using the command line
    214 \begin{verbatim}
    215 ncview geo_em.d01.nc
    216 \end{verbatim}
    217 \marge if \ttt{ncview} is installed, or the \ttt{IDL}
    218 script \ttt{out\_geo.pro}
    219 \begin{verbatim}
    220 idl
    221 IDL> out_geo, field1='TOPO'
    222 IDL> out_geo, field1='TI'
    223 IDL> SPAWN, 'ghostview geo_em.d01_HGT_M.ps &'
    224 IDL> SPAWN, 'ghostview geo_em.d01_THERMAL_INERTIA.ps &'
    225 IDL> exit
    226 \end{verbatim}
    227 \marge if the demo version of \ttt{IDL} is installed.
    228 %
    229 Of course if your favorite graphical tool supports
    230 the NETCDF standard, you might use it to check the
    231 domain definition in \ttt{geo\_em.d01.nc}.
    232 
    233 \mk
    234 \marge If you are unhappy with the results or
    235 you want to change
    236 the location of the mesoscale domain on the planet,
    237 the horizontal resolution,
    238 the number of grid points \ldots,
    239 please modify the parameter
    240 file \ttt{namelist.wps} and execute again \ttt{geogrid.exe}.
    241 %
    242 Here are the contents of \ttt{namelist.wps}:
    243 %
    244 \codesource{namelist.wps_TEST}
    245 
    246 \begin{finger}
    247 %
    248 \item No input meteorological data
    249 are actually needed to execute \ttt{geogrid.exe}.
    250 %
    251 \item More details about the database and
    252 more options of interpolation could be
    253 found in the file \ttt{geogrid/GEOGRID.TBL}.
    254 %
    255 \item Defining several domains yields
    256 distinct files
    257 \ttt{geo\_em.d01.nc},
    258 \ttt{geo\_em.d02.nc},
    259 \ttt{geo\_em.d03.nc}\ldots
    260 \end{finger}
    261 
    262 \mk
    263 \marge Once the \ttt{geo\_em} file(s) are generated,
    264 the \ttt{metgrid.exe} program performs
    265 a similar horizontal interpolation
    266 of the meteorological fields to the mesoscale
    267 domain as the one performed by \ttt{geogrid.exe}
    268 for the surface data.
    269 %
    270 Then the program writes the results in
    271 \ttt{met\_em} files and also collects
    272 the static fields and domain parameters
    273 included in the \ttt{geo\_em} file(s)
    274 %
    275 Please type the following commands:
    276 \begin{verbatim}
    277 cd $LMDMOD/LMD_MM_MARS/your_install_dir/WPS
    278 ./metgrid.exe
    279 \end{verbatim}
    280 %
    281 \marge If every went well,
    282 the directory \ttt{\$LMDMOD/TMPDIR/WRFFEED}
    283 should contain the \ttt{met\_em.*} files.
    284 
    285 \mk
    286 \subsubsection{Step 3: Vertical interpolation on mesoscale levels}
    287 
    288 \mk
    289 \marge The last step is to execute \ttt{real.exe}
    290 to perform the interpolation from the vertical
    291 levels of the GCM to the vertical levels
    292 defined in the mesoscale model.
    293 %
    294 This program also prepares the final initial
    295 state for the simulation in files called
    296 \ttt{wrfinput} and the boundary conditions
    297 in files called \ttt{wrfbdy}.
    298 
    299 \mk
    300 \marge To successfully execute \ttt{real.exe},
    301 you need the \ttt{met\_em.*} files
    302 and the \ttt{namelist.input} file
    303 to be in the same directory as \ttt{real.exe}.
    304 %
    305 Parameters in \ttt{namelist.input}
    306 controlling the behavior of the vertical interpolation
    307 are those labelled with \ttt{(p3)} in the detailed
    308 list introduced in the previous chapter.
    309 
    310 \mk
    311 \marge Please type the following commands
    312 to prepare files for the Arsia Mons test case
    313 (or your personal test case if you changed
    314 the parameters in \ttt{namelist.wps}):
    315 \begin{verbatim}
    316 cd $LMDMOD/TESTCASE
    317 ln -sf $LMDMOD/WRFFEED/met_em* .
    318 ./real.exe
    319 \end{verbatim}
    320 
    321 \mk
    322 \marge The final message of the \ttt{real.exe}
    323 should claim the success of the processes and you
    324 are now ready to launch the integrations
    325 of the LMD Martian Mesoscale Model again
    326 with the \ttt{wrf.exe} command as in section
    327 \ref{sc:arsia}.
    328 
    329 \begin{finger}
    330 \item When you modify either
    331 \ttt{namelist.wps} or \ttt{namelist.input},
    332 make sure that the common parameters
    333 are exactly similar in both files
    334 (especially when running nested simulations)
    335 otherwise either \ttt{real.exe} or \ttt{wrf.exe}
    336 command will exit with an error message.
    337 \end{finger}
    338 %\pagebreak
  • trunk/MESOSCALE_DEV/MANUAL/SRC/user_manual_txt.tex

    r220 r221  
     1
     2
     3\mk
     4\subsubsection{Meteorological data}
     5
     6\ttt{launch\_gcm}
     7
     8\mk
     9The preprocessing tools generate initial and boundary conditions
     10from the \ttt{diagfi.nc} outputs of LMD-MGCM simulations.
     11%
     12If you would like to run a mesoscale simulation at a given
     13season, you need to first run a GCM simulation and output
     14the meteorological fields at the considered season.
     15%
     16For optimal forcing at the boundaries, we advise you
     17to write the meteorological fields to the
     18\ttt{diagfi.nc} file at least each two hours.
     19%
     20Please also make sure that the following fields
     21are stored in the NETCDF \ttt{diagfi.nc} file:
     22
     23\footnotesize
     24\codesource{contents_diagfi}
     25
     26\normalsize
     27\begin{finger}
     28\item If the fields
     29\ttt{emis},
     30\ttt{co2ice},
     31\ttt{q01},
     32\ttt{q02},
     33\ttt{tsoil}
     34are missing in the \ttt{diagfi.nc} file,
     35they are replaced by respective default
     36values $0.95$, $0$, $0$, $0$, tsurf.
     37\end{finger}
     38
     39\mk
     40\marge An example of input meteorological file
     41\ttt{diagfi.nc} file can be downloaded
     42at \url{http://web.lmd.jussieu.fr/~aslmd/LMD_MM_MARS/diagfi.nc.tar.gz}.
     43%
     44Please deflate the archive and copy the \ttt{diagfi.nc} file
     45in \ttt{\$LMDMOD/TMPDIR/GCMINI}.
     46%
     47Such a file can then be used to define the initial
     48and boundary conditions, and we will go
     49through the three preprocessing steps.
     50
     51\mk
     52\subsection{Preprocessing steps}
     53
     54\mk
     55\subsubsection{Step 1: Converting GCM data}
     56
     57\mk
     58The programs in the \ttt{PREP\_MARS} directory
     59convert the data from the NETCDF \ttt{diagfi.nc}
     60file into separated binary datafiles for each
     61date contained in \ttt{diagfi.nc}, according to
     62the formatting needed by the
     63preprocessing programs at step 2.
     64%
     65These programs can be executed by the following
     66commands:
     67\begin{verbatim}
     68cd $LMDMOD/LMD_MM_MARS/your_install_dir/PREP\_MARS
     69echo 1 | ./create_readmeteo.exe     # drop the "echo 1 |" if you want control
     70./readmeteo.exe < readmeteo.def
     71\end{verbatim}
     72%
     73\marge If every went well with the conversion,
     74the directory \ttt{\$LMDMOD/TMPDIR/WPSFEED}
     75should contain files named \ttt{LMD:}.
     76
     77\mk
     78\subsubsection{2: Interpolation on the regional domain}
     79
     80\mk
     81In the \ttt{WPS} directory, the \ttt{geogrid.exe} program allows
     82you to define the mesoscale simulation domain
     83to horizontally interpolate the topography,
     84thermal inertia and albedo fields at the domain
     85resolution and to calculate useful fields
     86such as topographical slopes.%\pagebreak
     87
     88\mk
     89\marge Please execute the commands:
     90%
     91\begin{verbatim}
     92cd $LMDMOD/LMD_MM_MARS/your_install_dir/WPS
     93ln -sf ../../TESTCASE/namelist.wps .   # test case
     94./geogrid.exe
     95\end{verbatim}
     96%
     97\marge The result of \ttt{geogrid.exe}
     98-- and thus the definition of the mesoscale
     99domain -- can be checked in the NETCDF
     100file \ttt{geo\_em.d01.nc}.
     101%
     102A quick check can be performed using the command line
     103\begin{verbatim}
     104ncview geo_em.d01.nc
     105\end{verbatim}
     106\marge if \ttt{ncview} is installed, or the \ttt{IDL}
     107script \ttt{out\_geo.pro}
     108\begin{verbatim}
     109idl
     110IDL> out_geo, field1='TOPO'
     111IDL> out_geo, field1='TI'
     112IDL> SPAWN, 'ghostview geo_em.d01_HGT_M.ps &'
     113IDL> SPAWN, 'ghostview geo_em.d01_THERMAL_INERTIA.ps &'
     114IDL> exit
     115\end{verbatim}
     116\marge if the demo version of \ttt{IDL} is installed.
     117%
     118Of course if your favorite graphical tool supports
     119the NETCDF standard, you might use it to check the
     120domain definition in \ttt{geo\_em.d01.nc}.
     121
     122\mk
     123\marge If you are unhappy with the results or
     124you want to change
     125the location of the mesoscale domain on the planet,
     126the horizontal resolution,
     127the number of grid points \ldots,
     128please modify the parameter
     129file \ttt{namelist.wps} and execute again \ttt{geogrid.exe}.
     130%
     131Here are the contents of \ttt{namelist.wps}:
     132%
     133\codesource{namelist.wps_TEST}
     134
     135\begin{finger}
     136%
     137\item No input meteorological data
     138are actually needed to execute \ttt{geogrid.exe}.
     139%
     140\item More details about the database and
     141more options of interpolation could be
     142found in the file \ttt{geogrid/GEOGRID.TBL}.
     143%
     144\item Defining several domains yields
     145distinct files
     146\ttt{geo\_em.d01.nc},
     147\ttt{geo\_em.d02.nc},
     148\ttt{geo\_em.d03.nc}\ldots
     149\end{finger}
     150
     151\mk
     152\marge Once the \ttt{geo\_em} file(s) are generated,
     153the \ttt{metgrid.exe} program performs
     154a similar horizontal interpolation
     155of the meteorological fields to the mesoscale
     156domain as the one performed by \ttt{geogrid.exe}
     157for the surface data.
     158%
     159Then the program writes the results in
     160\ttt{met\_em} files and also collects
     161the static fields and domain parameters
     162included in the \ttt{geo\_em} file(s)
     163%
     164Please type the following commands:
     165\begin{verbatim}
     166cd $LMDMOD/LMD_MM_MARS/your_install_dir/WPS
     167./metgrid.exe
     168\end{verbatim}
     169%
     170\marge If every went well,
     171the directory \ttt{\$LMDMOD/TMPDIR/WRFFEED}
     172should contain the \ttt{met\_em.*} files.
     173
     174\mk
     175\subsubsection{Step 3: Vertical interpolation on mesoscale levels}
     176
     177\mk
     178\marge The last step is to execute \ttt{real.exe}
     179to perform the interpolation from the vertical
     180levels of the GCM to the vertical levels
     181defined in the mesoscale model.
     182%
     183This program also prepares the final initial
     184state for the simulation in files called
     185\ttt{wrfinput} and the boundary conditions
     186in files called \ttt{wrfbdy}.
     187
     188\mk
     189\marge To successfully execute \ttt{real.exe},
     190you need the \ttt{met\_em.*} files
     191and the \ttt{namelist.input} file
     192to be in the same directory as \ttt{real.exe}.
     193%
     194Parameters in \ttt{namelist.input}
     195controlling the behavior of the vertical interpolation
     196are those labelled with \ttt{(p3)} in the detailed
     197list introduced in the previous chapter.
     198
     199\mk
     200\marge Please type the following commands
     201to prepare files for the Arsia Mons test case
     202(or your personal test case if you changed
     203the parameters in \ttt{namelist.wps}):
     204\begin{verbatim}
     205cd $LMDMOD/TESTCASE
     206ln -sf $LMDMOD/WRFFEED/met_em* .
     207./real.exe
     208\end{verbatim}
     209
     210\mk
     211\marge The final message of the \ttt{real.exe}
     212should claim the success of the processes and you
     213are now ready to launch the integrations
     214of the LMD Martian Mesoscale Model again
     215with the \ttt{wrf.exe} command as in section
     216\ref{sc:arsia}.
     217
     218\begin{finger}
     219\item When you modify either
     220\ttt{namelist.wps} or \ttt{namelist.input},
     221make sure that the common parameters
     222are exactly similar in both files
     223(especially when running nested simulations)
     224otherwise either \ttt{real.exe} or \ttt{wrf.exe}
     225command will exit with an error message.
     226\end{finger}
     227%\pagebreak
     228
     229
    1230
    2231
Note: See TracChangeset for help on using the changeset viewer.