It seems like you have some priority=0 or priority=1 messages. You can look up what those warnings/errors are in the reports/log_analyzer “level 1” report, and see if those warnings are on the list of “acceptable” warnings included in the README, or if they are otherwise not important.
Hi @eyth.alison Thank you so much for the response. In the “level 1” report, I have only “Value for SMK_MAXERROR” and “Value for DEFAULT_CONV_FAC_ERROR not defined”.
So, I guess these are not important. And I can safely ignore these messages
Those two messages should be filtered out by the log analyzer “known messages”, and should not have triggered the “level 1 errors or level 0 warnings found” message. Can you please post your 1 file for our review?
But I didn’t find anything about “Time step error for file: PHOUR” in that link. Is that error similar to
" Error reading netCDF time step flag for PHOUR" from that link?
Can you also provide the smkinven_ptertac_winter_[month]_daily_2026fj_16j logs?
We suspect your hourly data does not cover the full time period required for each month – e.g. it is missing the last day of the previous month (which is needed for time zone shifting reasons) – but the Smkinven logs would confirm this.
For December, the last line in the Smkiven log is:
Timestep written to PHOUR for date and time 2016366:070000
So data is not bring written out for all of 12/31/16, which probably means there are no emissions on that date in the hourly FF10.
For January, the first PHOUR timestep is:
Timestep written to PHOUR for date and time 2016001:050000
To cover the first few hours of January, include a second hourly FF10 which includes December, in which the #YEAR in the header is the previous year (2015 in this case).
