5.9.2. Files, configuration, and environment variables

5.9.2.1. PDM input files
5.9.2.2. PDM compilation options
5.9.2.3. PDM compilation
5.9.2.4. PDM execution options
5.9.2.5. PDM output files

Figure 5.7. PDM input and output files

PDM input and output files

Figure 7 shows the input and output files for the PDM. The input file PDM_PING_O is only used when continuing a simulation from a previous day. Additional output files may also be written, in addition to the file shown in Figure 7. These diagnostic outputs are activated by setting the IPRFLG environment variable to “T” during execution.

5.9.2.1. PDM input files

Table 5.13. PDM input files

File Name Format Description
STACK_MEPSE GRDDED3 GMajor emitting point source emissions file that identifies the elevated emissions sources to receive PinG treatment in the CCTM; output from and emissions program such as SMOKE or CONCEPT
GRID_CRO_2D GRDDED3 Time-independent 2-D cross point meteorology file; this file is output by MCIP
GRID_DOT_2D GRDDED3 Time-independent 2-D dot point meteorology file; this file is output by MCIP
MET_CRO_2D GRDDED3 Time-dependent 2-D cross point meteorology file; this file is output by MCIP
MET_DOT_3D GRDDED3 Time-dependent 3-D dot point meteorology file; this file is output by MCIP
MET_CRO_3D GRDDED3 Time-dependent 3-D cross point meteorology file for defining the vertical layer structure of the model grid; this file is output by MCIP
PDM_PING_O GRDDED3 Previous day PinG output file for restarting the simulation
GRIDDESC ASCII Horizontal grid description file for defining the model grid; this file is output by MCIP or can be created by the user

5.9.2.2. PDM compilation options

The configuration options listed here are set during compilation of the PDM executable. None of these options will affect the results of the PDM simulation; they only control the behavior of the program M3BLD in creating the PDM executable.

  • Opt:[default: verbose]

    Defines the action to be taken by the program M3BLD when extracting source code from CVS and compiling an executable.

    • compile_all: force compile, even if all the object files are current
    • clean_up: remove all source files upon successful compilation
    • no_compile: do everything except compile
    • no_link: do everything except link
    • one_step: compile and link in one step
    • parse_only: checks configuration file syntax
    • show_only: shows requested commands but does not execute them
    • verbose: shows requested commands as they are executed
  • MakeOpt:

    Uncomment to build a Makefile to compile the executable

5.9.2.3. PDM compilation

Section 3.3 provides an overview of how to install and compile the CMAQ programs for the tutorial simulation. While the tutorial does not contain an exercise on using the PDM, the steps required to compile the PDM are virtually the same as those required to compile the other CMAQ programs, such as BCON. Follow these steps to compile the PDM:

  1. If you have not already done so, build the CMAQ source code and compilation management program (M3BLD); this only needs to be done the first time you install CMAQ
  2. Install and compile the I/O API and MPICH libraries; if these are already available from a previous CMAQ compilation, configure the PDM build script to use the available libraries
  3. Configure the PDM build script for your system by setting the correction name and location of the Fortran compiler
  4. Invoke the build script to create an executable:

                    ./bldit.pdm.pgf

5.9.2.4. PDM execution options

  • EXEC: [default: PDM_${CFG}]

    Executable to use for the simulation

  • LOGFILE: [default: $BASE/$APPL.log]

    Uncomment to capture CCTM standard output to a log file; the LOGFILE variable sets the name and location of the log

  • STDATE: [format: YYYYDDD]

    Beginning date of the PDM simulation

  • STTIME: [format: HHMMSS]

    Beginning time of the PDM simulation

  • NSTEPS: [format: HH]

    Duration of the PDM simulation

  • IOLDFIL: [default: 0]

    Continuation flag; set to 0 for the first simulation day and 1 for all other days

  • ICHUST: [default: 1]

    Methods for calculating the standard deviation of the turbulent component v and the Lagrangian time scale method

    • 1: Hanna et al. [1982]
    • 2: Hicks [1985] for convection boundary layer; Nieustadt [1984] for stable boundary layer; Arya [1984] for neutral boundary layer
  • ICHUSY: [default: 2]

    Methods for calculating the standard deviation of the turbulent component y

    • 1: Irwin [1984]
    • 2: Weil [1988] and Venkatram [1988]
  • ISHEAR: [default: 1]

    Wind shear effects on plume

    • 1: calculate wind shear effects
    • 0: omit wind shear effects
  • IMETHD: [default: 1]

    Interpolation method [need more description]

    • 1: Linear
    • 0: PBL
  • IDPLUM: [default: 0]

    Plume thickness calculation methods [need more description]

    • 0: Turner Method
    • 1: Temperature gradient method
  • IPRFLG: [default: F]

    Flag for activating the creation of additional diagnostic files

    • F: omit extra diagnostic files
    • T: print extra diagnostic files
  • IPARTFLG: [default: 0]

    Vertical partitioning flag [need more description]

  • FACTC: [default: 1.0]

    Plume hand over criteria [need more description]

  • INITC: [default: 1000]

    Plume initialization width (m)

  • DDIRC: [default: 1.8]

    Cross-plume wind-shear factor [need more description]

  • DSPDC: [default: 0.7]

    Wind speed shear factor [need more description]

  • SPRFA: [default: 15]

    Vertical plume spread factor [need more description]

  • SZOFA: [default: 3.545]

    Width factor for plume sections [need more description]

  • HSIZE: [default: 1000]

    Starting plume width size (m) [need more description]

  • DISP: [default: keep]

    Controls the maintenance of existing log files.

    • delete: delete output log if it already exists
    • keep: abort simulation if output log exists
  • OUTDIR: [default: $M3DATA/pdm]

    PDM output file directory location

  • GRIDDESC: [default: ../GRIDDESC1]

    Grid description file for setting the horizontal grid definition

  • GRID_NAME:

    Name of the grid definition contained in the GRIDDESC file that specifies the horizontal grid for the current application of the model

  • LAYER_FILE:

    Name and location of a MET_CRO_3D file for specifying the vertical layer structure for the current application of the model

5.9.2.5. PDM output files

Table 5.14. PDM output files

File Name Format Description
PDM_PING_1 GRDDED3 Name and location of the time-dependent, 3-D active plume file
NFOUT_1 Optional diagnostic plume rise output
NFOUT_2 Optional diagnostic plume parameters
NFOUT_3 Standard diagnostic plume parameters

The default location of the PDM output files is the $M3DATA/pdm directory, controlled by the OUTDIR variable in the run script. The default naming convention for all PDM output files uses the APPL environment variable in the file name. All of the file naming variables for PDM outputs are set in the run script.