CALPUFF and Postprocessors
CALPUFF and Postprocessors CALPUFF and Postprocessors
F.15 CALPUFF Output Files F.15.1 List File (CALPUFF.LST) The general list file for your CALPUFF run, CALPUFF.LST, is an ASCII text file that may be viewed by any standard text editor, or printed to any standard printer. It provides the primary means of documenting the CALPUFF application, and it also contains all warning messages that may have been generated by the application. Note that some problems detected by CALPUFF result in fatal error messages (the requested modeling period is not simulated), while other problems are not severe enough to halt the run, and warning messages are written to the list file. Warning messages may be located throughout the file, whereas fatal error messages are at the end (because the run is halted). Therefore, the list file should always be reviewed. The contents of the control file are echoed to the first part of the list file, and header records from each external data file for the run follow. In the case of CALMET.DAT, the header records include all of the time-invariant data fields, so that the file can become quite large when large CALMET grids are used. The remainder of the list file contains any hourly concentrations and deposition fluxes that are selected for output to the “printer”. This selection is made in Input Group 5 (see Section F.1) where ICPRT, IDPRT, and IWPRT identify the types of data selected; ICFRQ, IDFRQ, and IWFRQ identify the interval (in hours) between the data written to the list file; and IPRTU identifies the units used for this output. The species written are also explicitly selected here. Because the primary data files produced by CALPUFF are CONC.DAT, DFLX.DAT. and WFLX.DAT, which are processed by CALPOST, any data sent to the list file are generally for making spot-checks prior to the post-processing step, or for viewing the results of very short runs. The debug option, controlled by LDEBUG, IPFDEB, NPFDEB, NN1, and NN2 in Input Group 5, also places a good deal of information in the list file. Much of this uses internal parameter names, and is most useful for those who are tracing the treatment of a few specific puffs through the many CALPUFF subroutines, or for those who are preparing a run and want to obtain more information during the setup phase (use ITEST=1 in Input Group 1 to stop the run before going into the computational phase). If many puffs are traced (NPFDEB) over many modeling periods (NN1 to NN2), the list file will become huge. A limited set of puff information is also written to DEBUG.DAT each sampling step when the debug option is selected. This file is described in Section F.15.7. F.15.2 Restart File (RESTARTE.DAT) Information for all puffs that are still within the computational grid at the end of a CALPUFF run can be saved to disk in RESTARTE.DAT to initialize a continuation run. This allows CALPUFF to properly account for “old” material within the modeling domain at the start of the continuation run. This restart file may also be refreshed periodically during a run, as configured by NRESPD in Input Group 1 of the control file (see Section F.1). RESTARTE.DAT is an unformatted data file that contains information MAR 2006 – CALPUFF F-205
about the modeling grid, the date and time at the end of the period simulated, and all of the internal puff array data at the end of the simulation. Note that this file becomes the RESTARTB.DAT input file for the continuation run, and that all CALPUFF output files for the continuation run are “new”. For example, if a full year is simulated in four quarterly CALPUFF runs with three restart files, there will be four concentration files rather than one. F.15.3 Concentration File (CONC.DAT) The CONC.DAT file is an unformatted data file containing concentrations of one or more species simulated by CALPUFF at each receptor, for each period in the run. The creation and contents of the CONC.DAT file are controlled by user-specified inputs in Input Group 5 of the control file (see Section F.1). The control file variable ICON must be set equal to one in order to create the CONC.DAT file, and the file will contain only those species that are specifically “saved on disk”. CONC.DAT File - Header Records The CONC.DAT file consists of as many as NCOM+15 header records followed by a set of data records. The header records contain information describing the version of the model used in the run creating the file, horizontal and vertical grid data, a user-input title, a list of the species combinations stored in the output file, receptor information, and source names (see Table F-52). NCOM, provided in record 2, defines the number of comment records that are present. Comment records are used to transfer the image of CALMET and CALPUFF control files used in the simulation for documentation and QA purposes. Sample FORTRAN read statements for the header records are: READ(iunit) DATASET,DATAVER,DATAMOD READ(iunit) NCOM DO n=1,NCOM READ(iunit) COMMENT ENDDO READ(iunit)CMODEL,VER,LEVEL,IBYR,IBJUL,IBHR,IBSEC,XBTZ, 1 IRLG,IAVG,NSECDT,NXM,NYM,DXKM,DYKM,IONE,XORIGKM,YORIGKM,NSSTA,IBCOMP,IECOMP, 2 JBCOMP,JECOMP,IBSAMP,JBSAMP,IESAMP,JESAMP,MESHDN,NPT1,NPT2,NAR1,NAR2,NLN1,NLN2, 3 NVL1,NVL2,MSOURCE,NREC,NCTREC,LSAMP,NSPOUT,LCOMPR, 4 I2DMET,IUTMZN,FEAST,FNORTH,RNLAT0,RELON0, 5 XLAT1,XLAT2,PMAP,UTMHEM,DATUM,DATEN, 6 CLAT0,CLON0,CLAT1,CLAT2 READ(iunit)TITLE READ(iunit)CSOUT IF(NDREC.GT.0) READ(iunit)XREC,YREC,ZREC IF(NCTREC.GT.0) READ(iunit)XRCT,YRCT,ZRCT,IHILL IF(NPT1.GT.0) READ(iunit)ISTYPE,CNAMPT1 IF(NPT2.GT.0) READ(iunit)ISTYPE,CNAMPT2 IF(NAR1.GT.0) READ(iunit)ISTYPE,CNAMAR1 IF(NAR2.GT.0) READ(iunit)ISTYPE,CNAMAR2 IF(N LN1.GT.0) READ(iunit)ISTYPE,CNAMLN1 IF(NLN2.GT.0) READ(iunit)ISTYPE,CNAMLN2 IF(NVL1.GT.0) READ(iunit)ISTYPE,CNAMVL1 IF(NVL2.GT.0) READ(iunit)ISTYPE,CNAMVL2 MAR 2006 – CALPUFF F-206
- Page 158 and 159: Table F-29 VOLEMARB.DAT - Header Re
- Page 160 and 161: Table F-29 (Continued) VOLEMARB.DAT
- Page 162 and 163: VOLEMARB.DAT File - Data Records Th
- Page 164 and 165: Table F-30 VOLEMARB.DAT - Time-Inva
- Page 166 and 167: Table F-31 (Concluded) VOLEMARB.DAT
- Page 168 and 169: values in time provided in Input Gr
- Page 170 and 171: Table F-32 (Continued) Boundary Con
- Page 172 and 173: Table F-32 (Continued) Boundary Con
- Page 174 and 175: Table F-33 BCON.DAT File Inputs Var
- Page 176 and 177: Table F-33 (Concluded) BCON.DAT Fil
- Page 178 and 179: Table F-34 Sample User-Specified De
- Page 180 and 181: Table F-35 Sample Hourly Ozone Data
- Page 182 and 183: Table F-36 OZONE.DAT - Header Recor
- Page 184 and 185: Table F-37 OZONE.DAT - Time-Invaria
- Page 186 and 187: F.10 User-Specified Chemical Transf
- Page 188 and 189: F.11 Site-Specific Turbulence Data
- Page 190 and 191: Table F-40 Sample CTDMPLUS Terrain
- Page 192 and 193: Table F-42 HILL.DAT File - Record G
- Page 194 and 195: F.13 Subgrid Scale Coastal Boundary
- Page 196 and 197: COASTLN.DAT File - Header Record Th
- Page 198 and 199: COASTLN.DAT File - Data Records The
- Page 200 and 201: Table F-47 COASTLN.DAT - Data Recor
- Page 202 and 203: Table F-48 Sample Mass Flux Boundar
- Page 204 and 205: Table F-49 FLUXBDY.DAT - Header Rec
- Page 206 and 207: Table F-50 FLUXBDY.DAT - Data Heade
- Page 210 and 211: where the following declarations ap
- Page 212 and 213: Table F-52 (Continued) Unformatted
- Page 214 and 215: Table F-52 (Continued) Unformatted
- Page 216 and 217: Table F-52 (Continued) Unformatted
- Page 218 and 219: Table F-52 (Continued) Unformatted
- Page 220 and 221: Table F-52 (Concluded) Unformatted
- Page 222 and 223: Table F-53 Unformatted CONC.DAT Fil
- Page 224 and 225: F.15.4 Dry Flux File (DFLX.DAT) The
- Page 226 and 227: Table F-54 Unformatted DFLX.DAT fil
- Page 228 and 229: Table F-54 (Continued) Unformatted
- Page 230 and 231: Table F-54 (Continued) Unformatted
- Page 232 and 233: Table F-54 (Continued) Unformatted
- Page 234 and 235: Table F-54 (Continued) Unformatted
- Page 236 and 237: DFLX.DAT File - Data Records The DF
- Page 238 and 239: Table F-55 (Concluded) Unformatted
- Page 240 and 241: Character*132 COMMENT Character*80
- Page 242 and 243: Table F-56 (Continued) Unformatted
- Page 244 and 245: Table F-56 (Continued) Unformatted
- Page 246 and 247: Table F-56 (Continued) Unformatted
- Page 248 and 249: Table F-56 (Continued) Unformatted
- Page 250 and 251: Table F-56 (Concluded) Unformatted
- Page 252 and 253: Table F-57 Unformatted WFLX.DAT Fil
- Page 254 and 255: F.15.6 Relative Humidity File for V
- Page 256 and 257: Table F-58 Unformatted VISB.DAT fil
about the modeling grid, the date <strong>and</strong> time at the end of the period simulated, <strong>and</strong> all of the internal puff<br />
array data at the end of the simulation. Note that this file becomes the RESTARTB.DAT input file for the<br />
continuation run, <strong>and</strong> that all <strong>CALPUFF</strong> output files for the continuation run are “new”. For example, if a<br />
full year is simulated in four quarterly <strong>CALPUFF</strong> runs with three restart files, there will be four<br />
concentration files rather than one.<br />
F.15.3 Concentration File (CONC.DAT)<br />
The CONC.DAT file is an unformatted data file containing concentrations of one or more species<br />
simulated by <strong>CALPUFF</strong> at each receptor, for each period in the run. The creation <strong>and</strong> contents of the<br />
CONC.DAT file are controlled by user-specified inputs in Input Group 5 of the control file (see Section<br />
F.1). The control file variable ICON must be set equal to one in order to create the CONC.DAT file, <strong>and</strong><br />
the file will contain only those species that are specifically “saved on disk”.<br />
CONC.DAT File - Header Records<br />
The CONC.DAT file consists of as many as NCOM+15 header records followed by a set of data records.<br />
The header records contain information describing the version of the model used in the run creating the<br />
file, horizontal <strong>and</strong> vertical grid data, a user-input title, a list of the species combinations stored in the<br />
output file, receptor information, <strong>and</strong> source names (see Table F-52). NCOM, provided in record 2,<br />
defines the number of comment records that are present. Comment records are used to transfer the image<br />
of CALMET <strong>and</strong> <strong>CALPUFF</strong> control files used in the simulation for documentation <strong>and</strong> QA purposes.<br />
Sample FORTRAN read statements for the header records are:<br />
READ(iunit) DATASET,DATAVER,DATAMOD<br />
READ(iunit) NCOM<br />
DO n=1,NCOM<br />
READ(iunit) COMMENT<br />
ENDDO<br />
READ(iunit)CMODEL,VER,LEVEL,IBYR,IBJUL,IBHR,IBSEC,XBTZ,<br />
1 IRLG,IAVG,NSECDT,NXM,NYM,DXKM,DYKM,IONE,XORIGKM,YORIGKM,NSSTA,IBCOMP,IECOMP,<br />
2 JBCOMP,JECOMP,IBSAMP,JBSAMP,IESAMP,JESAMP,MESHDN,NPT1,NPT2,NAR1,NAR2,NLN1,NLN2,<br />
3 NVL1,NVL2,MSOURCE,NREC,NCTREC,LSAMP,NSPOUT,LCOMPR,<br />
4 I2DMET,IUTMZN,FEAST,FNORTH,RNLAT0,RELON0,<br />
5 XLAT1,XLAT2,PMAP,UTMHEM,DATUM,DATEN,<br />
6 CLAT0,CLON0,CLAT1,CLAT2<br />
READ(iunit)TITLE<br />
READ(iunit)CSOUT<br />
IF(NDREC.GT.0) READ(iunit)XREC,YREC,ZREC<br />
IF(NCTREC.GT.0) READ(iunit)XRCT,YRCT,ZRCT,IHILL<br />
IF(NPT1.GT.0) READ(iunit)ISTYPE,CNAMPT1<br />
IF(NPT2.GT.0) READ(iunit)ISTYPE,CNAMPT2<br />
IF(NAR1.GT.0) READ(iunit)ISTYPE,CNAMAR1<br />
IF(NAR2.GT.0) READ(iunit)ISTYPE,CNAMAR2<br />
IF(N LN1.GT.0) READ(iunit)ISTYPE,CNAMLN1<br />
IF(NLN2.GT.0) READ(iunit)ISTYPE,CNAMLN2<br />
IF(NVL1.GT.0) READ(iunit)ISTYPE,CNAMVL1<br />
IF(NVL2.GT.0) READ(iunit)ISTYPE,CNAMVL2<br />
MAR 2006 – <strong>CALPUFF</strong><br />
F-206
Change language