# SMOKE:Run time setting, Error in netCDF reading time step flag

**URL:** <https://forum.cmascenter.org/t/smoke-run-time-setting-error-in-netcdf-reading-time-step-flag/4150>\
**Category:** SMOKE\
**Tags:** smoke\
**Created:** [June 2, 2023, 11:53pm UTC](https://forum.cmascenter.org/t/smoke-run-time-setting-error-in-netcdf-reading-time-step-flag/4150 "2023-06-02T23:53:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Elsa](https://avatars.discourse-cdn.com/v4/letter/e/838e76/32.png) [@Elsa](https://forum.cmascenter.org/u/Elsa)\
**Post date:** [June 2, 2023, 11:53pm UTC](https://forum.cmascenter.org/t/smoke-run-time-setting-error-in-netcdf-reading-time-step-flag/4150/1 "2023-06-02T23:53:44Z")

</div>

Hi,

I have issue with the runtime setting. I have observation data from 2023, so I want to run simulation to compare with my observation data. I already I WRF output data for 2023. So I’m thinking to run SMOKE scripts based on my meteorological year which is 2023. Then I did the following change with the this run script: Monthly\_ag\_12US1\_2017gb\_17j.csh  
 ![Screen Shot 2023-06-02 at 4.47.24 PM (2)](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/d/d8aba63abaa93498d9d6bec9aa027c87414f8a5c.png)

then I run this script, but got the follow error:  
 ![Screen Shot 2023-06-02 at 4.49.39 PM (2)](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/c/caa6f85263e600d4fa38faa50c9ddac739c65bd4.png)

But, when I did the same editing of running time for the Annual\_rwc\_12US1\_2017gb\_17j.csh script,  
it works well and have emission out put of 2023 for rwc.

Any thought on this issue? Thanks!

---

<div class="post-metadata">

**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\
**Post date:** [June 7, 2023, 5:19pm UTC](https://forum.cmascenter.org/t/smoke-run-time-setting-error-in-netcdf-reading-time-step-flag/4150/2 "2023-06-07T17:19:06Z")

</div>

You are trying to model 2023 (as in met year=2023) but the Gentpro profiles are for a different year. The easiest solution is to use m3tshift to change the dates in the ATPRO\_HOURLY\_NCF file to 2023. This will effectively mean using met-based profiles from 2017 in 2023. Since you don’t have a full year of met data for 2023, running Gentpro for 2023 to produce a new ATPRO\_HOURLY\_NCF is not straightforward.