How to generate ptfire for Dec 25, 2016

SMOKE
1

Hi all,
I want to generate emission files for Dec 25 to 31, 2016. Is there any way not to use “SPINUP_DURATION” since SMOKE cannot process emissions over a calendar-year break? I can not run the full month of Dec because of a wall time limit.

setenv RUN_MONTHS "1" # 2 3 4 5 6 7 8 9 10 11 12"
#setenv SPINUP_DURATION "7"
#setenv SPINUP_MONTH_END "Y"
# Emissions modeling year
#  (i.e. meteorological year, not necessarily the inventory year"
setenv BASE_YEAR "2017"
setenv EPI_STDATE_TIME "${BASE_YEAR}-12-25 00:00:00.0"
setenv EPI_ENDATE_TIME "${BASE_YEAR}-12-31 23:59:00.0"

*** ERROR ABORT in subroutine GETPDINFO
No day -specific sources matched the inventory for the time period processed.

Thanks so much.

2

A few questions:

  • Is 12/25/16-12/31/16 the entire modeling period, or are you doing a 2017 modeling scenario and this is just the spinup period?

  • Which modeling platform / package are you using?

  • Are you also using the SMOKE input emissions inventories from that same package, or from another data source?

3

  • Yes, it’s the spinup for 2017.

  • I used NEI 2016 for Dec, 2016 and NEI 2017 for 2017.

  • I used SMOKE input emission inventories.

4

Please review Sections 11 and 12 of this file:

https://gaftp.epa.gov/Air/emismod/2017/2017gb_package_12jul2021_info.txt

Section 11 talks about how to prepare spinup emissions for standard modeling cases, and how EPA typically doesn’t prepare 2016-specific emissions for the spinup of a 2017 case, for example. So to replicate our methods, you wouldn’t need to run fires specifically for the spinup period in the prior year. But, if you still wanted to prepare 2016-specific spinup emissions for fires, or any other sector.

Section 12 talks about how to do a partial month run such as 12/25-12/31, both via the SPINUP_DURATION method and also using the run_settings method. EPA hasn’t tried running fires for a previous year via SPINUP_DURATION before – and are unsure if that would work. However, the run_settings approach described in the info file should work for processing 12/25-12/31, if you were starting from one of the 2016 platform packages.

Whichever method you try (using end of 2017 data for the spinup or using 2016-specific data), please set these two values back to the values from the original scripts for things to work properly:

setenv EPI_STDATE_TIME “${BASE_YEAR}-01-01 00:00:00.0”

setenv EPI_ENDATE_TIME “${BASE_YEAR}-12-31 23:59:00.0”

5

Alison, Thanks so much!