30.11.2012 Views

Run CMAQ

Run CMAQ

Run CMAQ

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Run</strong> <strong>CMAQ</strong><br />

1. <strong>Run</strong> MCIP to process the meteorology input for <strong>CMAQ</strong> (see <strong>Run</strong> MCIP). You should<br />

have the following files: GRIDDESC, GRID_CRO_2D, GRID_DOT_2D,<br />

GRID_BDY_2D, MET_CRO_2D, MET_DOT_3D, MET_CRO_3D, AND<br />

MET_BDY_3D. <strong>Run</strong> SMOKE to process emission files for <strong>CMAQ</strong> (see <strong>Run</strong><br />

SMOKE). You should have the following files: EMIS_1 and, if you are using plumein-grid,<br />

MEPSE_1.<br />

2. Go to /phd/data and create a project directory: MMAQ{period}. Within it, create the<br />

following input subdirectories: icin, bcin, phot, procan, and emis and the following<br />

output subdirectories: icon, bcon, jproc, pdm, pacp, and cctm. Within each output<br />

subbdirectory (except jproc and pacp), create file folders for all 8 ensembles<br />

(ens{#}). Change the $M3DATA environmental variables to /phd/data/MMAQ{period}.<br />

3. Edit .tcshrc “Setting environmental variables for this model run” section so that<br />

M3DATA set to “/phd/data/MMAQ{period}”. Make sure this line is uncommented and<br />

comment out settings for other models.<br />

4. ICON generates a gridded binary netCDF file of the chemical conditions in the<br />

modeling domain for the first hour of a simulation.<br />

a. Make sure you have the following inputs: M3BLD, IC_PROFILE OR<br />

CTM_CONC_1, GRIDDESC, MET_CRO_3D, MECH_CONV_FILE if conversion<br />

from a different chem mechanism is required and CTM_PING_1, PING_PDM_1,<br />

and MET_CRO_3D_CRS if plume-in-grid is used.<br />

b. Copy bldit.icon.pgf as bldit_icon_pgf.default. Edit the compilation options in the<br />

bldit script (see MMAQ <strong>CMAQ</strong> Options). Copy the new bldit.icon.pgf as ~/<br />

Documents/bldit_icon_MMAQ{period}.txt.<br />

c. Invoke the build script to create an executable: “./bldit.icon.pgf”. The same<br />

compilation will be used for all ensembles.<br />

d. Copy the run.icon file as run_icon.default. Edit run.icon script (see MMAQ <strong>CMAQ</strong><br />

Options). Copy the new run.icon as ~/Documents/run_icon_MMAQ{period}.txt.<br />

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

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

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

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

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

g. You should see something like the following output in $M3DATA/icon/ens{#}:<br />

ICON_cb05_M_36_2001_profile<br />

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

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

5. BCON generates a gridded binary netCDF file of the chemical conditions along the<br />

horizontal boundaries of the modeling domain.<br />

a. Make sure you have the following inputs: M3BLD, BC_PROFILE or<br />

CTM_CONC_1, GRIDDESC, MET_CRO_3D, MECH_CONV_FILE if conversion<br />

from a different chem mechanism is required and CTM_PING_1, PING_PDM_1,<br />

and MET_CRO_3D_CRS if plume-in-grid is used.<br />

1


. Copy bldit.bcon.pgf as bldit_bcon_pgf.default. Edit the compilation options in the<br />

bldit script (see MMAQ <strong>CMAQ</strong> Options). Copy the new bldit.bcon.pgf as ~/<br />

Documents/bldit_bcon_MMAQ{period}.txt.<br />

c. Invoke the build script to create an executable: “./bldit.bcon.pgf”. The same<br />

compilation will be used for all ensembles.<br />

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

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

run_bcon_MMAQ{period}.txt.<br />

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

~/Documents/bcon_{period}_ens{#}.txt” <strong>Run</strong> BCON for each ensemble. Between<br />

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

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

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

g. You should see something like the following output in $M3DATA/bcon/ens{#}:<br />

BCON_cb05_M_36_2001_profile<br />

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

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

6. JPROC calculates chemical-mechanism-specific clear-sky photolysis rates at fixed<br />

altitudes, hour angles, and latitude bands from tabulated absorption cross-section<br />

and quantum yield (CSQY) data.<br />

a. Make sure you have the following inputs: M3BLD, ET, PROFILES, CSGY, TOMS,<br />

O2ABS, and O3ABS.<br />

b. Copy bldit.jproc.pgf as bldit_jproc_pgf.default. Edit the compilation options in the<br />

bldit script (see MMAQ <strong>CMAQ</strong> Options). Copy the new bldit.jproc.pgf as ~/<br />

Documents/bldit_jproc_MMAQ{period}.txt.<br />

c. Invoke the build script to create an executable: “./bldit.jproc.pgf”. The same<br />

compilation will be used for all ensembles.<br />

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

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

run_jproc_MMAQ{period}.txt.<br />

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

~/Documents/jproc_{period}.txt” <strong>Run</strong> JPROC once for all ensemble.<br />

f. Check jproc.log. (JPROC does not have any notice like “Program JPROC<br />

completed successfully”.) Copy the log as ~/Documents/jproc_{period}.txt”.<br />

g. You should see the following output in $M3DATA/jrpoc: JTABLE_{date}.<br />

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

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

7. PACP generates FORTRAN INCLUDE files for building a version of the CCTM that<br />

can calculate integrated process rates and/or integrated reactive rates for<br />

diagnosing <strong>CMAQ</strong> simulations.<br />

a. Create "PACP_INFILE" to configure PACP (see MMAQ PACP Input File). Save it<br />

as ~/Documents/pacp_infile_{period}.txt.<br />

b. Make sure you have the following inputs: M3BLD and PACP_INFILE.<br />

c. Go to $M3WORK/scripts/procan. Copy bldit.pacp.pgf as bldit_pacp_pgf.default.<br />

Edit the compilation options in the bldit script (see MMAQ <strong>CMAQ</strong> Options). Copy<br />

the new bldit.pacp.pgf as ~/Documents/bldit_pacp.txt. Invoke the build script to<br />

2


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


MET_CRO_3D, and MET_BDY_3D (from MCIP). PACP should already be run if<br />

you want process analysis output.<br />

b. Copy bldit.cctm.pgf as bldit_cctm_pgf.default. Edit the compilation options in the<br />

bldit script (see MMAQ <strong>CMAQ</strong> Options). Copy the new bldit.cctm.pgf as ~/<br />

Documents/bldit_cctm_MMAQ{period}.txt.<br />

c. Invoke the build script to create an executable: “./bldit.cctm.pgf”. The same<br />

compilation will be used for all ensembles.<br />

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

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

run_cctm_MMAQ{period}.txt.<br />

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

~/Documents/cctm_{period}_ens{#}.txt” <strong>Run</strong> CCTM for each ensemble. Between<br />

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

f. Check cctm.log. You should see “Program CCTM completed successfully. Copy<br />

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

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

(1) CCTM_CONC (hourly instantaneous concentration)<br />

(2) CCTM_ACONC (hourly average concentration)<br />

(3) CCTM_CGRID (restart file)<br />

(4) CCTM_DRYDEP (hourly cumulative dry deposition)<br />

(5) CCTM_WETDEP (hourly cumulative wet deposition)<br />

(6) CCTM_AEROVIS (hourly instantaneous visibility)<br />

(7) CCTM_DIAM (instantaneous hourly aerosol diameter)<br />

(8) CCTM_PING (plume-in-grid unmerged plume data)<br />

(9) CCTM_PING_DIAM (plume-in-grid hourly aerosol diameter)<br />

(10) CCTM_PING_DDEP (plume-in-grid dry deposition)<br />

(11) CCTM_IPR_[1-3] (process analysis integrated process rate)<br />

(12) CCTM_IRR_[1-3] (process analysis integrated reaction rate)<br />

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

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

Thursday, June 19, 2008<br />

4

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

Saved successfully!

Ooh no, something went wrong!