CALPUFF and Postprocessors
CALPUFF and Postprocessors CALPUFF and Postprocessors
G.2 APPEND The APPEND program is designed to combine a set of sequential CALPUFF output data files into a single file with the same format, covering the entire period of the original collection of files. The files combined must be of the same type, containing either concentrations, wet deposition fluxes, dry deposition fluxes, or relative humidity data. The periods contained in the files should either overlap, or meet exactly (files start with the time period that follows the last period in the preceding file). Table G-8 lists the input and output files for one application of APPEND. Both the control file name (APPEND.INP) and the list file name (APPEND.LST) are set in the program, so the user cannot change these. All CALPUFF output file names must be provided by the user, and these are placed in the control file. The control file structure is listed in Table G-9, and a sample control file is listed in Table G-10. To run this program, place the executable and the control file (edited to reflect your application) in the same directory or folder, and enter the following command-line: APPEND The program will open the control file for your application, and follow the instructions. Messages appear on the screen as the program runs, and full documentation for the run is written to the list file. A sample list file is presented in Table G-11. MAR 2006 -- PostProc G-26
Table G-8 APPEND Input and Output Files Unit File Name Type Format Description io5 APPEND.INP input formatted Control file containing user inputs io6 APPEND.LST output formatted List file containing APPEND application information io10 MODEL.DAT output unformatted CALPUFF output data file containing modeled concentration or deposition flux or relative humidity data, containing all periods io21 MODEL1.DAT input unformatted First sequential CALPUFF output data file containing modeled concentration or deposition flux or relative humidity data io21 +(n-1) MODELn.DAT input unformatted Last of "n" sequential CALPUFF output data files containing modeled concentration or deposition flux or relative humidity data MAR 2006 -- PostProc G-27
- Page 262 and 263: Table F-58 (Continued) Unformatted
- Page 264 and 265: Table F-58 (Continued) Unformatted
- Page 266 and 267: VISB.DAT File - Data Records The VI
- Page 268 and 269: Table F-59 (Concluded) Unformatted
- Page 270 and 271: Table F-60 Sample Debug Puff-Tracki
- Page 272 and 273: F.15.8 Mass Flux List File (MASSFLX
- Page 274 and 275: F.15.9 Mass Balance List File (MASS
- 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 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 326 and 327: The name and full path of each file
- 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
G.2 APPEND<br />
The APPEND program is designed to combine a set of sequential <strong>CALPUFF</strong> output data files into a<br />
single file with the same format, covering the entire period of the original collection of files. The files<br />
combined must be of the same type, containing either concentrations, wet deposition fluxes, dry<br />
deposition fluxes, or relative humidity data. The periods contained in the files should either overlap, or<br />
meet exactly (files start with the time period that follows the last period in the preceding file).<br />
Table G-8 lists the input <strong>and</strong> output files for one application of APPEND. Both the control file name<br />
(APPEND.INP) <strong>and</strong> the list file name (APPEND.LST) are set in the program, so the user cannot change<br />
these. All <strong>CALPUFF</strong> output file names must be provided by the user, <strong>and</strong> these are placed in the control<br />
file. The control file structure is listed in Table G-9, <strong>and</strong> a sample control file is listed in Table G-10.<br />
To run this program, place the executable <strong>and</strong> the control file (edited to reflect your application) in the<br />
same directory or folder, <strong>and</strong> enter the following comm<strong>and</strong>-line:<br />
APPEND<br />
The program will open the control file for your application, <strong>and</strong> follow the instructions. Messages appear<br />
on the screen as the program runs, <strong>and</strong> full documentation for the run is written to the list file. A sample<br />
list file is presented in Table G-11.<br />
MAR 2006 -- PostProc<br />
G-26