CALPUFF and Postprocessors
CALPUFF and Postprocessors CALPUFF and Postprocessors
The name and full path of each file (except one) is assigned in the control file. The exception, the control filename itself, is assigned on the command line. For example, on a DOS system, POSTUTIL d:\MYWORK\UTIL1.INP will execute the POSTUTIL code in the current working directory, and read the input and output filenames for the current run from the control file UTIL1.INP in the directory d:\MYWORK. If the control filename is not specified on the command line, the default control filename (i.e., POSTUTIL.INP in the current working directory) will be used. The total number of characters in the path and filename can be up to 70 characters. The POSTUTIL control file is configured using any standard text editor (e.g., NOTEPAD). It uses the general CALPUFF control file structures, containing several input groups with module inputs set within a pair of special delimiter characters (!). All documentation associated with these inputs is written outside of these delimiters. A description of each input variable is shown in Table G-17. A sample control file that illustrates a common POSTUTIL application for obtaining total sulfur and total nitrogen deposition fluxes is provided in Table G-18. The top of the control file contains three lines that are reserved for identifying the application. These lines are written to the output file, and become part of the documentation in subsequent processing. Input Group: 0 Input Group 0 identifies the input and output files for the application. The output consists of a list file that documents how this application of POSTUTIL is configured, and a data file that is identical in form to the binary data files created by CALPUFF. In this sample, the data file is given the generic name 'cpuf.flx' (!UTLDAT = CPUF.FLX!) to indicate that wet and dry fluxes are summed, and that total sulfur and total nitrogen are added the list of species in the file. The list file is given the default name (!UTLLST = POSTUTIL.LST!). More specific names should be used in typical applications. Input files include one or more CALMET meteorological data files and one or more CALPUFF binary files. A CALMET file is not needed for this application because no nitrate partitioning will be calculated (MNITRATE=0), but is included in the control file to illustrate the format. Two CALPUFF binary files are needed for this application: one for the dry deposition flux, and one for the wet deposition flux. Therefore !NFILES = 2! and two filenames are provided in Subgroup 0b: ! MODDAT =WFLX.DAT ! !END! ! MODDAT =DFLX.DAT ! !END! MAR 2006 -- PostProc G-40
Table G-17 POSTUTIL Control File Inputs - Input Group 0 Input and Output File Names Variable Type Description Default UTLLST character*70 File name of list file of information output from POSTUTIL application, including path if desired UTLDAT character*70 File name of CALPUFF format data file created by POSTUTIL application, including path if desired POSTUTIL.LST MODEL.DAT NMET integer Number of CALMET data files input for processing 0 NFILES integer Number of CALPUFF data files input for processing 1 LCFILES logical Control flag for converting file names to lower case if T, or to upper case if F UTLMET character*70 NMET file names of CALMET data files needed by POSTUTIL application, including path if desired (used only if MNITRATE = 1) MODDAT character*70 NFILES file names of CALPUFF data files processed by POSTUTIL application, including path if desired T MET.DAT CALPUFF.DAT MAR 2006 -- PostProc G-41
- Page 276 and 277: F.16 OPTHILL When the subgrid scale
- Page 278 and 279: The following procedure is recommen
- Page 280 and 281: Table F-64 OPTHILL Input and Output
- Page 282 and 283: Figure F-2 Map of terrain surroundi
- Page 284 and 285: Table F-67 OPTHILL Output File for
- Page 286 and 287: This process is simplified somewhat
- Page 288 and 289: G.1 PRTMET Meteorological Display P
- Page 290 and 291: Table G-1 PRTMET Input and Output F
- Page 292 and 293: Table G-2 (Continued) PRTMET Contro
- Page 294 and 295: Table G-2 (Concluded) PRTMET Contro
- Page 296 and 297: Table G-3 Sample PRTMET Control Fil
- Page 298 and 299: Table G-3 Sample PRTMET Control Fil
- Page 300 and 301: Table G-4 Sample PRTMET List File (
- Page 302 and 303: Table G-4 Sample PRTMET List File (
- Page 304 and 305: Table G-4 Sample PRTMET List File (
- Page 306 and 307: Table G-4 Sample PRTMET List File (
- Page 308 and 309: Table G-4 Sample PRTMET List File (
- Page 310 and 311: Table G-6 Sample vector plot file x
- Page 312 and 313: G.2 APPEND The APPEND program is de
- Page 314 and 315: Table G-9 APPEND Control File Struc
- Page 316 and 317: Table G-11 Sample APPEND List File
- Page 318 and 319: G.3 CALSUM The CALSUM program is de
- Page 320 and 321: Table G-13 CALSUM Control File Stru
- Page 322 and 323: Table G-15 Sample CALSUM List File
- Page 324 and 325: G.4 POSTUTIL POSTUTIL operates on o
- Page 328 and 329: Table G-17 (Continued) POSTUTIL Con
- Page 330 and 331: Table G-18 Sample POSTUTIL Control
- Page 332 and 333: Table G-18 (Continued) Sample POSTU
- Page 334 and 335: INPUT GROUP: 2 -- Species Processin
- Page 336 and 337: 1 g of SO 2 contributes 0.500000 g
- Page 338 and 339: Table G-19 (Continued) Sample POSTU
- Page 340 and 341: Table G-19 (Concluded) Sample POSTU
- Page 342 and 343: When CALPOST is directed to perform
- Page 344 and 345: Table G-20 (concluded) CALPOST Inpu
- Page 346 and 347: G.6 CALPOST Input Files G.6.1 User
- Page 348 and 349: Table G-21 CALPOST Control File Inp
- Page 350 and 351: Table G-21 (Continued) CALPOST Cont
- Page 352 and 353: Table G-21 (Continued) CALPOST Cont
- Page 354 and 355: Table G-21 (Continued) CALPOST Cont
- Page 356 and 357: Table G-21 (Concluded) CALPOST Cont
- Page 358 and 359: Table G-22 (Continued) Sample CALPO
- Page 360 and 361: INPUT GROUP: 2 -- Visibility Parame
- Page 362 and 363: Table G-22 (Continued) Sample CALPO
- Page 364 and 365: Table G-22 (Concluded) Sample CALPO
- Page 366 and 367: Table G-24 Sample Background Concen
- Page 368 and 369: Table G-26 Sample Nephelometer File
- Page 370 and 371: G.7.4 Time-series File(s) CALPOST c
- Page 372 and 373: Table G-27 (Continued) Sample CALPO
- Page 374 and 375: Table G-27 (Concluded) Sample CALPO
Table G-17<br />
POSTUTIL Control File Inputs - Input Group 0<br />
Input <strong>and</strong> Output File Names<br />
Variable Type Description Default<br />
UTLLST character*70 File name of list file of information output from<br />
POSTUTIL application, including path if desired<br />
UTLDAT character*70 File name of <strong>CALPUFF</strong> format data file created by<br />
POSTUTIL application, including path if desired<br />
POSTUTIL.LST<br />
MODEL.DAT<br />
NMET integer Number of CALMET data files input for processing 0<br />
NFILES integer Number of <strong>CALPUFF</strong> data files input for processing 1<br />
LCFILES logical Control flag for converting file names to lower case if<br />
T, or to upper case if F<br />
UTLMET character*70 NMET file names of CALMET data files needed by<br />
POSTUTIL application, including path if desired (used<br />
only if MNITRATE = 1)<br />
MODDAT character*70 NFILES file names of <strong>CALPUFF</strong> data files processed<br />
by POSTUTIL application, including path if desired<br />
T<br />
MET.DAT<br />
<strong>CALPUFF</strong>.DAT<br />
MAR 2006 -- PostProc<br />
G-41
Change language