6.16.3. Files and Environment Variables

6.16.3.1. Input Files
6.16.3.2. Input Environment Variables
6.16.3.3. Other Input
6.16.3.4. Output Files

Figure 6.22. Temporal input and output files for area sources

Temporal input and output files for area sources

Figure 6.22, “Temporal input and output files for area sources” shows the input and output files for the Temporal program for area sources. The input files include the inventory file output from Smkinven (AREA), the temporal profiles file (ATPRO), the temporal cross-reference file (ATREF), the country, state, and county codes file (COSTCY), the holidays file HOLIDAYS), and optional process date file (PROCDATES).

Temporal outputs an hourly emissions file (ATMP), a temporal allocation supplemental file (ATSUP), and a log file (LOGFILE).

Figure 6.23. Temporal input and output files for mobile sources

Temporal input and output files for mobile sources

Figure 6.23, “Temporal input and output files for mobile sources” shows the input and output files for the Temporal program for mobile sources. The input files include the country, state, and county codes file (COSTCY), the holidays file (HOLIDAYS), the optional process date file (PROCDATES) and, if activity data are used, the inventory data table (INVTABLE). Temporal also uses the inventory file output from Smkinven (MOBL), the temporal profiles file (MTPRO), and the temporal cross-reference file (MTREF). For mobile sources, Temporal reads the mobile codes file (MCODES).

Temporal outputs a log file (LOGFILE), an hourly emissions file (MTMP), and a temporal allocation supplemental file (MTSUP).

Figure 6.24. Temporal input and output files for point sources

Temporal input and output files for point sources

Figure 6.24, “Temporal input and output files for point sources” shows the input and output files for the Temporal program for point sources. The input files include the country, state, and county codes file (COSTCY), the holidays file (HOLIDAYS) and the optional process date file (PROCDATES). If using day-specific data, the PDAY file is read, and the PHOUR file is read when using hour-specific data. Temporal also uses the inventory file output from Smkinven (PNTS), the temporal profiles file (PTPRO), and the temporal cross-reference file (PTREF).

Temporal outputs a log file (LOGFILE), an hourly emissions file (PTMP), and a temporal allocation supplemental file (PTSUP).

6.16.3.1. Input Files

File Name Format Description
[AREA|MOBL|PNTS] SMOKE map Intermediate inventory file produced by Smkinven
[A|M|P]TPRO ASCII Temporal profiles
[A|M|P]TREF ASCII Temporal cross-reference file
COSTCY ASCII Country/state/county codes file, used to determine counties that do not use Daylight Saving time.
HOLIDAYS ASCII Holidays file by Gregorian date, for applying holiday temporal profiles.
PROCDATES (optional) ASCII Processes user specified Gregorian dates
INVTABLE (optional) ASCII Inventory data table listing pollutant and activity names; required only if activity data are used
MCODES (optional) ASCII Mobile codes file for converting road class numbers and vehicle type numbers to SMOKE internal standard
PDAY (optional) I/O API NetCDF Day-specific intermediate inventory file created by Smkinven (required if DAY_SPECIFIC_YN is set to Y)
PHOUR (optional) I/O API NetCDF Hour-specific intermediate inventory file created by Smkinven (required if HOUR_SPECIFIC_YN is set to Y)

6.16.3.2. Input Environment Variables

  • DAY_SPECIFIC_YN: See description in Section 6.13.3.2, “Input Environment Variables”

  • FULLSCC_ONLY: See description in Section 6.2.3.2, “Input Environment Variables”. In this context, this option affects cross-referencing for the temporal cross-reference files by preventing left-7 SCC assignments.

  • HOUR_SPECIFIC_YN: See description in Section 6.13.3.2, “Input Environment Variables”

  • OUTZONE: : [default: 0]

    Indicates offset from Greenwich Mean Time (GMT) for episode start date and time. OUTZONE should be set to the standard time for the time zone of interest; SMOKE will adjust to Daylight Saving time for episodes that are during periods and in regions where Daylight Saving time applies.

    Table 2.8, “Example OUTZONE settings and their associated time zones” provides allowed values for OUTZONE. The CMAQ and MAQSIP models expect OUTZONE to be 0, while other models such as UAM-IV, UAM-V, REMSAD, and CAMX often use time zone 5. All models expect that the emissions and the meteorology data provided to the model will have a consistent time zone. SMOKE expects that the meteorology data will be in GMT.

    Note that SMOKE expects OUTZONE to be set as a positive number for time zones in the Western Hemisphere, although standard notation would list these as negative values. For example, Eastern Standard Time is -5:00 hours from GMT, but OUTZONE for EST in SMOKE is 5.

  • RENORM_TPROF: [default: Y]

    Defines whether Temporal normalizes the temporal profiles or uses them as they exist in the data file. If the profiles are specified as decimal values and sum to 1, then specify N. Otherwise, specify Y and the program will sum the values associated with each profile and then divide each value by the sum, thereby creating a normalized profile.

    • Y: Normalize the temporal profiles

    • N: Use the temporal profile values as they exist in the data file

  • REPORT_DEFAULTS: See description in Section 6.2.3.2, “Input Environment Variables”

  • SMK_AVEDAY_YN: See description in Section 6.2.3.2, “Input Environment Variables”

  • SMK_EF_MODEL: [default: MOVES]

    Name of the emission factor model to use. NOTE: At this time only the default value can be used.

  • SMK_MAXERROR: See description in Section 6.13.3.2, “Input Environment Variables”

  • SMK_MAXWARNING: See description in Section 6.13.3.2, “Input Environment Variables”

  • SMK_SOURCE: See description in Section 6.2.3.2, “Input Environment Variables”

  • UNIFORM_TPROF_YN: [default: N]

    Defines whether to use uniform temporal profiles for all sources.

    • Y: Use uniform temporal profiles

    • N: Use temporal profiles file and temporal cross-reference file

  • USE_MCODES_SCC_YN: [defual:Y]

    Define whether or not the program use MCODES input file to build internal SCC based on vehicle type and road type numbers. See detail information in Section 8.9.2.11, “MCODES: Mobile source codes file”

    • Y: Construct internal SCC using vehicle type and road type numbers

    • N: Do not construct internal SCC

  • ZONE4WM: [default: Y]

    Defines whether Temporal applies weekly and monthly temporal profiles using time zones. If SMOKE does not apply the profiles using the sources’ time zones, then all sources change from one day to the next or one month to the next at the same hour. This is what other emission processing systems have typically done, and it is a minor distinction in most cases.

    • Y: Use time zones

    • N: Do not use time zones

6.16.3.3. Other Input

Optionally, Temporal may be run using PROCDATES. This enables the processing of sequential or non-sequential user specified days. If PROCDATES is not assigned, the defaults apply.

When running Temporal interactively, the following inputs will be requested. The default values for these are set by the G_STDATE, G_STTIME, and G_RUNLEN environment variables.

  • Start date: Starting date of simulation in Julian (YYYYDDD) or Gregorian (YYYYMMDD) formats

  • Start Time: Starting time of simulation in HHMMSS

  • Duration: Simulation duration in hours

PROCDATES: See description in Section 8.3.4, “PROCDATES: Procdates date list”.

6.16.3.4. Output Files

As of SMOKE version 2.3, two new environmental variables [A|M|P]TMPNAME and [A|M|P]TSUPNAME are required to set the directory and file prefix used to dynamically name the output files [A|M|P]TMP and [A|M|P]TSUP.

File Name Format Description
[A|M|P]TMP I/O API NetCDF Hourly emissions by source; if using elevated point sources as part of point-source processing, this file contains only the layer-1 emissions
[A|M|P]TSUP ASCII Temporal allocation supplemental file
LOGFILE ASCII Log generated from executing Temporal