30.11.2012 Views

Run CMAQ

Run CMAQ

Run CMAQ

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.

create an executable: “./bldit.pacp.pgf”. This program only needs to be compiled<br />

once.<br />

d. Copy the run.pacp file as run_pacp.default. Edit run.pacp script (see MMAQ<br />

<strong>CMAQ</strong> Options). Copy the new run.pacp as ~/Documents/<br />

run_pacp_MMAQ{period}.txt.<br />

e. Execute ./run.pacp in emacs compile mode. For longer runs, enter “./run.pacp ><br />

~/Documents/pacp_{period}.txt” <strong>Run</strong> PACP once for all ensembles. (The {period}<br />

in the log file is necessary in case I choose to change PACP_INFILE).<br />

f. Check pacp.log. You should see “Program PACP completed successfully”. Copy<br />

the log as ~/Documents/pacp_{period}.txt”.<br />

g. You should see the following outputs in $M3DATA/pacp/: PA_CTL.EXT,<br />

PA_CMN.EXT, PA_DAT.EXT, and PA_REPORT.<br />

h. Examine PACP output files using TextEdit.<br />

i. This step is only done once for all periods and all ensembles.<br />

8. PDM is the plume-in-grid preprocessor, which generates plume dynamics, such as<br />

dimensions and location, from special emissions input files generated by an<br />

emissions model for plume-in-grid simulations.<br />

a. Make sure you have the following inputs: GRIDCRO2D, GRIDDOT2D,<br />

METCRO2D, METDOT3D, METCRO3D, and GRIDDESC from MCIP,<br />

STACK_MEPSE from SMOKE, and PDM_PING_O if restarting the simulation.<br />

PACP should already be run if you want optional diagnostic output.<br />

b. Copy bldit.pdm.pgf as bldit_pdm_pgf.default. Edit the path directories. Copy the<br />

new bldit.pdm.pgf as ~/Documents/bldit_pdm.txt.<br />

c. Invoke the build script to create an executable: “./bldit.pdm.pgf”. This program<br />

only has to be compiled once.<br />

d. Copy the run.pdm file as run_pdm.default. Edit run.pdm script (see MMAQ<br />

<strong>CMAQ</strong> Options). Copy the new run.pdm as ~/Documents/<br />

run_pdm_MMAQ{period}.txt.<br />

e. Execute ./run.pdm in emacs compile mode. For longer runs, enter “./run.pdm > ~/<br />

Documents/pdm_{period}_ens{#}.txt” <strong>Run</strong> PDM for each ensemble. Between<br />

each run, change the OUTDIR to the next ensemble subdirectory.<br />

f. Check pdm.log. You should see “Program PDM completed successfully”. Copy<br />

the log as ~/Documents/pdm_{period}_ens{#}.txt”.<br />

g. You should see the following outputs in $M3DATA/pdm/ens{#}: PDM_PING_1<br />

and NFOUT_3 (Optional diagnostic plume rise output). If optional diagnostic files<br />

are requested: NFOUT_2 (plume paramters) and NFOUT_1 (plume rise).<br />

h. Examine PDM output files using ncdump or ncview.<br />

i. This step must be repeated for a new time period and for each ensemble.<br />

9. CCTM integrates the output from all of the preprocessing programs, including the<br />

emissions and meteorology models, to simulate continuous atmospheric chemical<br />

conditions.<br />

a. Make sure you have the following inputs: M3BLD, OCEAN_1 (from $M3HOME/<br />

data/emis/2001/), EMIS_1 and MEPSE_1 (from SMOKE), PDM_PING_1 (from<br />

PDM), ICON_{filename} (from ICON), BCON_{filename} (from BCON),<br />

JTABLE_{date} (from JPROC), and GRID_CRO_2D, GRID_CRO_3D,<br />

GRID_DOT_2D, GRID_BDY_2D, MET_CRO_2D, MET_DOT_3D,<br />

3

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

Saved successfully!

Ooh no, something went wrong!