29.01.2015 Views

CALPUFF and Postprocessors

CALPUFF and Postprocessors

CALPUFF and Postprocessors

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

F.15.7 Debug Puff-Tracking File (DEBUG.DAT)<br />

<strong>CALPUFF</strong> contains a debug option to report much information about each selected puff as it is<br />

transported <strong>and</strong> sampled over a number of modeling periods. Most of this extra information is written to<br />

the <strong>CALPUFF</strong> list file (see Section F.15.1). A limited set of puff information is also written to<br />

DEBUG.DAT each sampling step when the debug option is selected. The purpose of this file is to<br />

provide puff characteristics at the end of each sampling step so that its location <strong>and</strong> size can be reviewed<br />

to visualize the combined effects of transport <strong>and</strong> diffusion at specific times.<br />

The DEBUG.DAT file is a sequential, formatted data file (see Table F-60 for an example) consisting of<br />

two types of records: two header records <strong>and</strong> a variable number of sets of data records. The header<br />

records name the variables that are reported in the data records (see Table F-61). Each data record<br />

provides information about a single puff at the end of a single sampling step. While there may be many<br />

sampling steps over the course of an hour, the time reported for each is the end-time of the current hour.<br />

A series of nested loops controls the sequence in which the data records are written to the file. The<br />

outermost loop is over the number of modeling periods (hours) for which debug output is selected.<br />

Within this is a loop over the range of puffs that has been selected. The innermost loop is over the<br />

sampling steps for each of these puffs. Because the puff ID <strong>and</strong> the date <strong>and</strong> time are included in each<br />

record, this structure is readily discerned.<br />

Records for individual puffs are written during the selected modeling period only while that puff exists on<br />

the computational grid. It is not tracked before it is emitted, <strong>and</strong> it is not tracked once it leaves the<br />

modeling domain.<br />

MAR 2006 – <strong>CALPUFF</strong><br />

F-266

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!