# Problem with emission reading in DESID module of CMAQ 5.4+ for cross-day simulations

**URL:** <https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438>\
**Category:** Run Time Errors and Issues\
**Tags:** cmaq, emissions\
**Created:** [September 27, 2023, 6:56pm UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438 "2023-09-27T18:56:24Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![wli31](https://avatars.discourse-cdn.com/v4/letter/w/f08c70/32.png) [@wli31](https://forum.cmascenter.org/u/wli31)\
**Post date:** [September 27, 2023, 6:56pm UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/1 "2023-09-27T18:56:24Z")

</div>

I just want to discuss if this is a potential bug for emission reading on a new day when doing a cross-day simulation. This points to the diagnostic part of the codes in the [DESID\_DRIVER](https://github.com/USEPA/CMAQ/blob/642e81395472d5887b54f601b60ee607ed39bf09/CCTM/src/emis/emis/desid_module.F#L32) subroutine, which further links to the [GR3D](https://github.com/USEPA/CMAQ/blob/642e81395472d5887b54f601b60ee607ed39bf09/CCTM/src/emis/emis/desid_module.F#L932) subroutine. My understanding is that the ‘DESID\_STREAM\_DATE( FSTREAM )’ will not update to the new date and that would cause wrong interpolation ratios in the centralized IO module.

Another small thing is that if I activate the ‘hrdebug’ macro, there will be an error in [hrsolver](https://github.com/USEPA/CMAQ/blob/642e81395472d5887b54f601b60ee607ed39bf09/CCTM/src/gas/ebi_cb6r5_ae7_aq/hrsolver.F#L262) when compiling the model. It seems the dimension of RXRAT is wrong.

---

<div class="post-metadata">

**Author:** ![Ben\_Murphy](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@Ben\_Murphy](https://forum.cmascenter.org/u/Ben_Murphy)\
**Post date:** [September 27, 2023, 7:43pm UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/2 "2023-09-27T19:43:24Z")

</div>

Hello,

We tested this behavior before the release of CMAQv5.3 and the day for the emissions does advance. See 936 in the GR3D subroutine. If you come across a specific case where this issue occurs, we would be happy to look further into it.

Best wishes,  
Ben Murphy

---

<div class="post-metadata">

**Author:** ![wli31](https://avatars.discourse-cdn.com/v4/letter/w/f08c70/32.png) [@wli31](https://forum.cmascenter.org/u/wli31)\
**Post date:** [September 28, 2023, 4:34am UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/3 "2023-09-28T04:34:11Z")

</div>

Thanks for the reply. I guess my case is indeed specific because I am using the same TSTEP(1) and TSTEP(2), which is 3min. I think that is the issue.

Best,  
Wei Li

---

<div class="post-metadata">

**Author:** ![wong.david-c](https://avatars.discourse-cdn.com/v4/letter/w/bcef8e/32.png) [@wong.david-c](https://forum.cmascenter.org/u/wong.david-c)\
**Post date:** [October 3, 2023, 7:01pm UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/4 "2023-10-03T19:01:10Z")

</div>

Hi Wei,

```
I wonder you can share your input and we can do a test at the EPA machine.

```

Cheers,  
David

---

<div class="post-metadata">

**Author:** ![wli31](https://avatars.discourse-cdn.com/v4/letter/w/f08c70/32.png) [@wli31](https://forum.cmascenter.org/u/wli31)\
**Post date:** [October 4, 2023, 3:55am UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/5 "2023-10-04T03:55:34Z")

</div>

Hi David,

Thanks for the reply. I am running NOAA’s AQM model and it only uses CMAQ’s emission processing the chemistry, so I guess you cannot use the input. I tested to use a different TSTEP(1), and the error disappeared. So, I think they cannot be set the same.

Best,  
Wei

---

<div class="post-metadata">

**Author:** ![wong.david-c](https://avatars.discourse-cdn.com/v4/letter/w/bcef8e/32.png) [@wong.david-c](https://forum.cmascenter.org/u/wong.david-c)\
**Post date:** [October 4, 2023, 1:09pm UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/6 "2023-10-04T13:09:31Z")

</div>

Hi Wei,

```
Could you be more specific what you meant "cannot be set the same"? All emission input time step must be the same or all input? After will your clarification, I will look into the cio implementation.

```

Cheers,  
David

---

<div class="post-metadata">

**Author:** ![wli31](https://avatars.discourse-cdn.com/v4/letter/w/f08c70/32.png) [@wli31](https://forum.cmascenter.org/u/wli31)\
**Post date:** [October 4, 2023, 2:58pm UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/7 "2023-10-04T14:58:09Z")

</div>

Hi David,

I got the error when I used the same TSTEP(1) and TSTEP(2), which is 3 mins. I solved it after I set a different TSTEP(1), (e.g., 1h) with TSTEP(2) keeping 3 mins. I am not sure if this is an issue in cio or desid.

Best,  
Wei

---

<div class="post-metadata">

**Author:** ![wong.david-c](https://avatars.discourse-cdn.com/v4/letter/w/bcef8e/32.png) [@wong.david-c](https://forum.cmascenter.org/u/wong.david-c)\
**Post date:** [October 4, 2023, 5:11pm UTC](https://forum.cmascenter.org/t/problem-with-emission-reading-in-desid-module-of-cmaq-5-4-for-cross-day-simulations/4438/8 "2023-10-04T17:11:03Z")

</div>

Hi Wei,

```
I see now. Yes typically we set TSTEP(1) = 10000 and it is not related to cio. Once I have time, I will try to set it be the same as TSTEP(2) to see whether we can reproduce the problem.

```

Cheers,  
David
