Changeset 221 for trunk/MESOSCALE_DEV/MANUAL/SRC
- Timestamp:
- Jul 13, 2011, 10:38:37 PM (13 years ago)
- Location:
- trunk/MESOSCALE_DEV/MANUAL/SRC
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/MESOSCALE_DEV/MANUAL/SRC/preproc.tex
r220 r221 110 110 \end{center} 111 111 112 \end{document}113 112 114 \mk 115 \subsubsection{Meteorological data} 113 \clearemptydoublepage 116 114 117 \ttt{launch\_gcm}118 119 \mk120 The preprocessing tools generate initial and boundary conditions121 from the \ttt{diagfi.nc} outputs of LMD-MGCM simulations.122 %123 If you would like to run a mesoscale simulation at a given124 season, you need to first run a GCM simulation and output125 the meteorological fields at the considered season.126 %127 For optimal forcing at the boundaries, we advise you128 to write the meteorological fields to the129 \ttt{diagfi.nc} file at least each two hours.130 %131 Please also make sure that the following fields132 are stored in the NETCDF \ttt{diagfi.nc} file:133 134 \footnotesize135 \codesource{contents_diagfi}136 137 \normalsize138 \begin{finger}139 \item If the fields140 \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 default147 values $0.95$, $0$, $0$, $0$, tsurf.148 \end{finger}149 150 \mk151 \marge An example of input meteorological file152 \ttt{diagfi.nc} file can be downloaded153 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} file156 in \ttt{\$LMDMOD/TMPDIR/GCMINI}.157 %158 Such a file can then be used to define the initial159 and boundary conditions, and we will go160 through the three preprocessing steps.161 162 \mk163 \subsection{Preprocessing steps}164 165 \mk166 \subsubsection{Step 1: Converting GCM data}167 168 \mk169 The programs in the \ttt{PREP\_MARS} directory170 convert the data from the NETCDF \ttt{diagfi.nc}171 file into separated binary datafiles for each172 date contained in \ttt{diagfi.nc}, according to173 the formatting needed by the174 preprocessing programs at step 2.175 %176 These programs can be executed by the following177 commands:178 \begin{verbatim}179 cd $LMDMOD/LMD_MM_MARS/your_install_dir/PREP\_MARS180 echo 1 | ./create_readmeteo.exe # drop the "echo 1 |" if you want control181 ./readmeteo.exe < readmeteo.def182 \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 \mk189 \subsubsection{2: Interpolation on the regional domain}190 191 \mk192 In the \ttt{WPS} directory, the \ttt{geogrid.exe} program allows193 you to define the mesoscale simulation domain194 to horizontally interpolate the topography,195 thermal inertia and albedo fields at the domain196 resolution and to calculate useful fields197 such as topographical slopes.%\pagebreak198 199 \mk200 \marge Please execute the commands:201 %202 \begin{verbatim}203 cd $LMDMOD/LMD_MM_MARS/your_install_dir/WPS204 ln -sf ../../TESTCASE/namelist.wps . # test case205 ./geogrid.exe206 \end{verbatim}207 %208 \marge The result of \ttt{geogrid.exe}209 -- and thus the definition of the mesoscale210 domain -- can be checked in the NETCDF211 file \ttt{geo\_em.d01.nc}.212 %213 A quick check can be performed using the command line214 \begin{verbatim}215 ncview geo_em.d01.nc216 \end{verbatim}217 \marge if \ttt{ncview} is installed, or the \ttt{IDL}218 script \ttt{out\_geo.pro}219 \begin{verbatim}220 idl221 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> exit226 \end{verbatim}227 \marge if the demo version of \ttt{IDL} is installed.228 %229 Of course if your favorite graphical tool supports230 the NETCDF standard, you might use it to check the231 domain definition in \ttt{geo\_em.d01.nc}.232 233 \mk234 \marge If you are unhappy with the results or235 you want to change236 the location of the mesoscale domain on the planet,237 the horizontal resolution,238 the number of grid points \ldots,239 please modify the parameter240 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 data249 are actually needed to execute \ttt{geogrid.exe}.250 %251 \item More details about the database and252 more options of interpolation could be253 found in the file \ttt{geogrid/GEOGRID.TBL}.254 %255 \item Defining several domains yields256 distinct files257 \ttt{geo\_em.d01.nc},258 \ttt{geo\_em.d02.nc},259 \ttt{geo\_em.d03.nc}\ldots260 \end{finger}261 262 \mk263 \marge Once the \ttt{geo\_em} file(s) are generated,264 the \ttt{metgrid.exe} program performs265 a similar horizontal interpolation266 of the meteorological fields to the mesoscale267 domain as the one performed by \ttt{geogrid.exe}268 for the surface data.269 %270 Then the program writes the results in271 \ttt{met\_em} files and also collects272 the static fields and domain parameters273 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/WPS278 ./metgrid.exe279 \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 \mk286 \subsubsection{Step 3: Vertical interpolation on mesoscale levels}287 288 \mk289 \marge The last step is to execute \ttt{real.exe}290 to perform the interpolation from the vertical291 levels of the GCM to the vertical levels292 defined in the mesoscale model.293 %294 This program also prepares the final initial295 state for the simulation in files called296 \ttt{wrfinput} and the boundary conditions297 in files called \ttt{wrfbdy}.298 299 \mk300 \marge To successfully execute \ttt{real.exe},301 you need the \ttt{met\_em.*} files302 and the \ttt{namelist.input} file303 to be in the same directory as \ttt{real.exe}.304 %305 Parameters in \ttt{namelist.input}306 controlling the behavior of the vertical interpolation307 are those labelled with \ttt{(p3)} in the detailed308 list introduced in the previous chapter.309 310 \mk311 \marge Please type the following commands312 to prepare files for the Arsia Mons test case313 (or your personal test case if you changed314 the parameters in \ttt{namelist.wps}):315 \begin{verbatim}316 cd $LMDMOD/TESTCASE317 ln -sf $LMDMOD/WRFFEED/met_em* .318 ./real.exe319 \end{verbatim}320 321 \mk322 \marge The final message of the \ttt{real.exe}323 should claim the success of the processes and you324 are now ready to launch the integrations325 of the LMD Martian Mesoscale Model again326 with the \ttt{wrf.exe} command as in section327 \ref{sc:arsia}.328 329 \begin{finger}330 \item When you modify either331 \ttt{namelist.wps} or \ttt{namelist.input},332 make sure that the common parameters333 are exactly similar in both files334 (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 9 The preprocessing tools generate initial and boundary conditions 10 from the \ttt{diagfi.nc} outputs of LMD-MGCM simulations. 11 % 12 If you would like to run a mesoscale simulation at a given 13 season, you need to first run a GCM simulation and output 14 the meteorological fields at the considered season. 15 % 16 For optimal forcing at the boundaries, we advise you 17 to write the meteorological fields to the 18 \ttt{diagfi.nc} file at least each two hours. 19 % 20 Please also make sure that the following fields 21 are 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} 34 are missing in the \ttt{diagfi.nc} file, 35 they are replaced by respective default 36 values $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 42 at \url{http://web.lmd.jussieu.fr/~aslmd/LMD_MM_MARS/diagfi.nc.tar.gz}. 43 % 44 Please deflate the archive and copy the \ttt{diagfi.nc} file 45 in \ttt{\$LMDMOD/TMPDIR/GCMINI}. 46 % 47 Such a file can then be used to define the initial 48 and boundary conditions, and we will go 49 through the three preprocessing steps. 50 51 \mk 52 \subsection{Preprocessing steps} 53 54 \mk 55 \subsubsection{Step 1: Converting GCM data} 56 57 \mk 58 The programs in the \ttt{PREP\_MARS} directory 59 convert the data from the NETCDF \ttt{diagfi.nc} 60 file into separated binary datafiles for each 61 date contained in \ttt{diagfi.nc}, according to 62 the formatting needed by the 63 preprocessing programs at step 2. 64 % 65 These programs can be executed by the following 66 commands: 67 \begin{verbatim} 68 cd $LMDMOD/LMD_MM_MARS/your_install_dir/PREP\_MARS 69 echo 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, 74 the directory \ttt{\$LMDMOD/TMPDIR/WPSFEED} 75 should contain files named \ttt{LMD:}. 76 77 \mk 78 \subsubsection{2: Interpolation on the regional domain} 79 80 \mk 81 In the \ttt{WPS} directory, the \ttt{geogrid.exe} program allows 82 you to define the mesoscale simulation domain 83 to horizontally interpolate the topography, 84 thermal inertia and albedo fields at the domain 85 resolution and to calculate useful fields 86 such as topographical slopes.%\pagebreak 87 88 \mk 89 \marge Please execute the commands: 90 % 91 \begin{verbatim} 92 cd $LMDMOD/LMD_MM_MARS/your_install_dir/WPS 93 ln -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 99 domain -- can be checked in the NETCDF 100 file \ttt{geo\_em.d01.nc}. 101 % 102 A quick check can be performed using the command line 103 \begin{verbatim} 104 ncview geo_em.d01.nc 105 \end{verbatim} 106 \marge if \ttt{ncview} is installed, or the \ttt{IDL} 107 script \ttt{out\_geo.pro} 108 \begin{verbatim} 109 idl 110 IDL> out_geo, field1='TOPO' 111 IDL> out_geo, field1='TI' 112 IDL> SPAWN, 'ghostview geo_em.d01_HGT_M.ps &' 113 IDL> SPAWN, 'ghostview geo_em.d01_THERMAL_INERTIA.ps &' 114 IDL> exit 115 \end{verbatim} 116 \marge if the demo version of \ttt{IDL} is installed. 117 % 118 Of course if your favorite graphical tool supports 119 the NETCDF standard, you might use it to check the 120 domain definition in \ttt{geo\_em.d01.nc}. 121 122 \mk 123 \marge If you are unhappy with the results or 124 you want to change 125 the location of the mesoscale domain on the planet, 126 the horizontal resolution, 127 the number of grid points \ldots, 128 please modify the parameter 129 file \ttt{namelist.wps} and execute again \ttt{geogrid.exe}. 130 % 131 Here are the contents of \ttt{namelist.wps}: 132 % 133 \codesource{namelist.wps_TEST} 134 135 \begin{finger} 136 % 137 \item No input meteorological data 138 are actually needed to execute \ttt{geogrid.exe}. 139 % 140 \item More details about the database and 141 more options of interpolation could be 142 found in the file \ttt{geogrid/GEOGRID.TBL}. 143 % 144 \item Defining several domains yields 145 distinct 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, 153 the \ttt{metgrid.exe} program performs 154 a similar horizontal interpolation 155 of the meteorological fields to the mesoscale 156 domain as the one performed by \ttt{geogrid.exe} 157 for the surface data. 158 % 159 Then the program writes the results in 160 \ttt{met\_em} files and also collects 161 the static fields and domain parameters 162 included in the \ttt{geo\_em} file(s) 163 % 164 Please type the following commands: 165 \begin{verbatim} 166 cd $LMDMOD/LMD_MM_MARS/your_install_dir/WPS 167 ./metgrid.exe 168 \end{verbatim} 169 % 170 \marge If every went well, 171 the directory \ttt{\$LMDMOD/TMPDIR/WRFFEED} 172 should 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} 179 to perform the interpolation from the vertical 180 levels of the GCM to the vertical levels 181 defined in the mesoscale model. 182 % 183 This program also prepares the final initial 184 state for the simulation in files called 185 \ttt{wrfinput} and the boundary conditions 186 in files called \ttt{wrfbdy}. 187 188 \mk 189 \marge To successfully execute \ttt{real.exe}, 190 you need the \ttt{met\_em.*} files 191 and the \ttt{namelist.input} file 192 to be in the same directory as \ttt{real.exe}. 193 % 194 Parameters in \ttt{namelist.input} 195 controlling the behavior of the vertical interpolation 196 are those labelled with \ttt{(p3)} in the detailed 197 list introduced in the previous chapter. 198 199 \mk 200 \marge Please type the following commands 201 to prepare files for the Arsia Mons test case 202 (or your personal test case if you changed 203 the parameters in \ttt{namelist.wps}): 204 \begin{verbatim} 205 cd $LMDMOD/TESTCASE 206 ln -sf $LMDMOD/WRFFEED/met_em* . 207 ./real.exe 208 \end{verbatim} 209 210 \mk 211 \marge The final message of the \ttt{real.exe} 212 should claim the success of the processes and you 213 are now ready to launch the integrations 214 of the LMD Martian Mesoscale Model again 215 with 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}, 221 make sure that the common parameters 222 are exactly similar in both files 223 (especially when running nested simulations) 224 otherwise either \ttt{real.exe} or \ttt{wrf.exe} 225 command will exit with an error message. 226 \end{finger} 227 %\pagebreak 228 229 1 230 2 231
Note: See TracChangeset
for help on using the changeset viewer.