I am running the 2019 NEI ptagfire emissions (re-dated to 1980 for my study) and I seem to be able to run the one time script without any errors but when I run the daily script SMOKE fails when running ELEVPOINT. I have attached the last few lines of the log file to show the error message. It appears the starting time the program is looking for does not match starting time of the first entry in PDAY? ACRESBURNED, as well as all of the other categories appear to be have been properly detected and included. I should note that I was not able to create the stack group file so the error may be earlier in the process though no error messages were generated.
Any suggestions on how to solve this would be greatly appreciated.
This looks like maybe a GMT-vs-local-time issue: the requested date&time is Jan 1 at 0:00:00 (midnight) GMT, but the PDAY file starts at 05:00:00 GMT – which would be midnight for EST.
A standard work-around is to create a new file starting at 0:00 GMT, with the last 5 hours of the original file copied onto the first 5 hours of this new file, and then the original file copied into the rest of the time steps for the year… M3Tools program m3tshift** can be used to do this…
Thanks for the suggestion. I understand how to time shift the pday file using m3tshift but I am puzzled why this error is occurring in the first place? I can’t find an instruction in any of the scripts that set the starting time to 0500 hrs rather than 0000 hrs so I am not sure where the 0500 offset is being set.
Typically the TZ offset is accounted for at the inventory level by providing a “previous day” inventory file when running smkinven for January. This can be actual data (e.g. Dec 31 2018 emissions) or duplicated Jan 1 data with dates changed to Dec 31st of the previous year. For ptagfire in the 2019 emissions modeling platform this file is “ptday_agfire_CONUS_2019ge_prevdec_03jan2022_v0”.
I had re-dated the 2019 inventory file to 1980 but forgot to re-date the pre-2019 inventory file to 1979. Many thanks for the reminder. The ptagfire script is running now.
