Table of Contents - The Atmospheric Studies Group at TRC
Table of Contents - The Atmospheric Studies Group at TRC Table of Contents - The Atmospheric Studies Group at TRC
Section 7: Prognostic Meteorological Interfaces The output from TAPM is an ASCII file and is machine-independent. CALTAPM simply transforms the data into the correct file format compatible with CALMET. CALTAPM is easily executed on a pc. Detailed information about TAPM settings is included in the list file (CALTAPM.LST) as shown in Table 7-33. Information needed for consistency in CALMET is included in the 3D.DAT header records as well. CALTAPM preprocessor requires a set of common block and parameter files for compiling. It needs one user-input file to run (CALTAPM.INP, hard-wired filename), and produces two output files (CALTAPM.LST and 3D.DAT). Output filenames are determined by users. CALTAPM Input Files TAPM.OUTA - TAPM ASCII output file of the type *.OUTA TAPM The following steps below must be followed in order to generate a 3-Dimensional data file (3D.DAT) from TAPM using CALTAPM. 1. First run TAPM according to the instruction manual prepared by CSIRO (Hurley 2005). It is recommended to run TAPM using multiple nested grids, at least 3 nests with > 30 vertical levels. 2. Once TAPM has finished executing, use the Utilities command found on the File Menu Command of the TAPM GUI to convert the TAPM binary output file, *.OUT to an ASCII *.OUTA file. Usually the innermost nest is converted since it has the finest resolution and detail. CALTAPM Control File CALTAPM.INP In CALTAPM.INP, the user can specify the input and output file names and the period to extract. The boundaries of the domain are not required as CALTAPM will transform the entire domain. It is up to the user to select the correct model domain when creating a 3D.DAT file from TAPM model output. A sample CALTAPM.INP is shown in Table 7-26 and a description of each input variable is provided in Table 7-6. CALTAPM Output Files CALTAPM.LST The list file contains information about the TAPM file and reports on CALTAPM processing, including warnings and error messages. A sample list file is shown in Table 7-26. 3D.DAT A sample 3D.DAT file is shown and described in section (7.7). 7-62
Section 7: Prognostic Meteorological Interfaces Table 7-28: CALTAPM Sample Control File (CALTAPM.INP) TAPM.OUTA ! TAPM OUTA file created from TAPM GUI TAPM.DEF ! Default file which stores model selections TAPM.TOP ! TAPM topography file CALTAPM.LST ! CALTAPM output list file containing information about TAPM file CALTAPM.M3D ! 3-Dimensional data output file 2001010101 : beginning date for processing (LST time - YYYYMMDDHH) 2001010105 : ending date for processing (LST time - YYYYMMDDHH) 7-63
- Page 197 and 198: Section 7: Prognostic Meteorologica
- Page 199 and 200: Section 7: Prognostic Meteorologica
- Page 201 and 202: Section 7: Prognostic Meteorologica
- Page 203 and 204: Section 7: Prognostic Meteorologica
- Page 205 and 206: Section 7: Prognostic Meteorologica
- Page 207 and 208: Section 7: Prognostic Meteorologica
- Page 209 and 210: Section 7: Prognostic Meteorologica
- Page 211 and 212: Section 7: Prognostic Meteorologica
- Page 213 and 214: Section 7: Prognostic Meteorologica
- Page 215 and 216: Section 7: Prognostic Meteorologica
- Page 217 and 218: Section 7: Prognostic Meteorologica
- Page 219 and 220: Section 7: Prognostic Meteorologica
- Page 221 and 222: Section 7: Prognostic Meteorologica
- Page 223 and 224: Section 7: Prognostic Meteorologica
- Page 225 and 226: Section 7: Prognostic Meteorologica
- Page 227 and 228: Section 7: Prognostic Meteorologica
- Page 229 and 230: Section 7: Prognostic Meteorologica
- Page 231 and 232: Section 7: Prognostic Meteorologica
- Page 233 and 234: Section 7: Prognostic Meteorologica
- Page 235 and 236: Section 7: Prognostic Meteorologica
- Page 237 and 238: Section 7: Prognostic Meteorologica
- Page 239 and 240: Section 7: Prognostic Meteorologica
- Page 241 and 242: Section 7: Prognostic Meteorologica
- Page 243 and 244: Section 7: Prognostic Meteorologica
- Page 245 and 246: Section 7: Prognostic Meteorologica
- Page 247: Section 7: Prognostic Meteorologica
- Page 251 and 252: Section 7: Prognostic Meteorologica
- Page 253 and 254: Section 7: Prognostic Meteorologica
- Page 255 and 256: Section 7: Prognostic Meteorologica
- Page 257 and 258: Section 7: Prognostic Meteorologica
- Page 259 and 260: Section 7: Prognostic Meteorologica
- Page 261 and 262: Section 7: Prognostic Meteorologica
- Page 263 and 264: Section 7: Prognostic Meteorologica
- Page 265 and 266: Section 7: Prognostic Meteorologica
- Page 267 and 268: Section 8: CALMET Model Files (e.g.
- Page 269 and 270: Section 8: CALMET Model Files Table
- Page 271 and 272: Section 8: CALMET Model Files descr
- Page 273 and 274: Section 8: CALMET Model Files Table
- Page 275 and 276: Section 8: CALMET Model Files Table
- Page 277 and 278: Section 8: CALMET Model Files Table
- Page 279 and 280: Section 8: CALMET Model Files Table
- Page 281 and 282: Section 8: CALMET Model Files Table
- Page 283 and 284: Section 8: CALMET Model Files Table
- Page 285 and 286: Section 8: CALMET Model Files Table
- Page 287 and 288: Section 8: CALMET Model Files Table
- Page 289 and 290: Section 8: CALMET Model Files Table
- Page 291 and 292: Section 8: CALMET Model Files Table
- Page 293 and 294: Section 8: CALMET Model Files Table
- Page 295 and 296: Section 8: CALMET Model Files Table
- Page 297 and 298: Section 8: CALMET Model Files Table
Section 7: Prognostic Meteorological Interfaces<br />
<strong>The</strong> output from TAPM is an ASCII file and is machine-independent. CALTAPM simply transforms the<br />
d<strong>at</strong>a into the correct file form<strong>at</strong> comp<strong>at</strong>ible with CALMET. CALTAPM is easily executed on a pc.<br />
Detailed inform<strong>at</strong>ion about TAPM settings is included in the list file (CALTAPM.LST) as shown in<br />
<strong>Table</strong> 7-33. Inform<strong>at</strong>ion needed for consistency in CALMET is included in the 3D.DAT header records<br />
as well. CALTAPM preprocessor requires a set <strong>of</strong> common block and parameter files for compiling. It<br />
needs one user-input file to run (CALTAPM.INP, hard-wired filename), and produces two output files<br />
(CALTAPM.LST and 3D.DAT). Output filenames are determined by users.<br />
CALTAPM Input Files<br />
TAPM.OUTA - TAPM ASCII output file <strong>of</strong> the type *.OUTA<br />
TAPM <strong>The</strong> following steps below must be followed in order to gener<strong>at</strong>e a 3-Dimensional d<strong>at</strong>a file<br />
(3D.DAT) from TAPM using CALTAPM.<br />
1. First run TAPM according to the instruction manual prepared by CSIRO (Hurley 2005). It is<br />
recommended to run TAPM using multiple nested grids, <strong>at</strong> least 3 nests with > 30 vertical levels.<br />
2. Once TAPM has finished executing, use the Utilities command found on the File Menu<br />
Command <strong>of</strong> the TAPM GUI to convert the TAPM binary output file, *.OUT to an ASCII<br />
*.OUTA file. Usually the innermost nest is converted since it has the finest resolution and detail.<br />
CALTAPM Control File<br />
CALTAPM.INP<br />
In CALTAPM.INP, the user can specify the input and output file names and the period to extract. <strong>The</strong><br />
boundaries <strong>of</strong> the domain are not required as CALTAPM will transform the entire domain. It is up to the<br />
user to select the correct model domain when cre<strong>at</strong>ing a 3D.DAT file from TAPM model output.<br />
A sample CALTAPM.INP is shown in <strong>Table</strong> 7-26 and a description <strong>of</strong> each input variable is provided in<br />
<strong>Table</strong> 7-6.<br />
CALTAPM Output Files<br />
CALTAPM.LST<br />
<strong>The</strong> list file contains inform<strong>at</strong>ion about the TAPM file and reports on CALTAPM processing, including<br />
warnings and error messages. A sample list file is shown in <strong>Table</strong> 7-26.<br />
3D.DAT<br />
A sample 3D.DAT file is shown and described in section (7.7).<br />
7-62