# Really large IPR EMIS results for upper layers

**URL:** <https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562>\
**Category:** CMAQ\
**Created:** [December 6, 2023, 1:04pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562 "2023-12-06T13:04:04Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tris](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/tris/32/1810_2.png) [@Tris](https://forum.cmascenter.org/u/Tris)\
**Post date:** [December 6, 2023, 1:04pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/1 "2023-12-06T13:04:04Z")

</div>

Hi,  
I’m using IPR (CMAQ v5.3.3) to analysis PM2.5 which defined in the pa\_cb6r3\_ae7\_aq.ctl as follow:

```auto
DEFINE FAMILY ATOTI = ASO4I +ANO3I +ANH4I +ANAI +ACLI +AECI
+ ALVPO1I + ASVPO1I + ASVPO2I + APOCI +APNCOMI 
+ ALVOO1I + ALVOO2I + ASVOO1I + ASVOO2I + AOTHRI;

DEFINE FAMILY ATOTJ = ASO4J +ANO3J +ANH4J +ANAJ +ACLJ
+ AECJ +AOTHRJ +AFEJ +ASIJ 
+ ATIJ +ACAJ +AMGJ +AMNJ +AALJ +AKJ
+ ALVPO1J + ASVPO1J + ASVPO2J + APOCJ    
+ ASVPO3J + AIVPO1J + APNCOMJ 
+ AISO1J + AISO2J + AISO3J       
+ AMT1J + AMT2J + AMT3J + AMT4J 
+ AMT5J + AMT6J + AMTNO3J 
+ AMTHYDJ + AGLYJ + ASQTJ            
+ AORGCJ + AOLGBJ + AOLGAJ          
+ ALVOO1J + ALVOO2J + ASVOO1J + ASVOO2J 
+ ASVOO3J + APCSOJ + AAVB1J + AAVB2J 
+ AAVB3J + AAVB4J;

DEFINE FAMILY ATOTIJ = ASO4I +ANO3I +ANH4I +ANAI +ACLI +AECI
+ ALVPO1I + ASVPO1I + ASVPO2I + APOCI +APNCOMI 
+ ALVOO1I + ALVOO2I + ASVOO1I + ASVOO2I + AOTHRI
+ ASO4J +ANO3J +ANH4J +ANAJ +ACLJ
+ AECJ +AOTHRJ +AFEJ +ASIJ 
+ ATIJ +ACAJ +AMGJ +AMNJ +AALJ +AKJ
+ ALVPO1J + ASVPO1J + ASVPO2J + APOCJ    
+ ASVPO3J + AIVPO1J + APNCOMJ 
+ AISO1J + AISO2J + AISO3J       
+ AMT1J + AMT2J + AMT3J + AMT4J 
+ AMT5J + AMT6J + AMTNO3J 
+ AMTHYDJ + AGLYJ + ASQTJ            
+ AORGCJ + AOLGBJ + AOLGAJ          
+ ALVOO1J + ALVOO2J + ASVOO1J + ASVOO2J 
+ ASVOO3J + APCSOJ + AAVB1J + AAVB2J 
+ AAVB3J + AAVB4J;

```

the PA\_BLEV\_ELEV was set to “1 14”, the output of EMIS\_ATOTIJ, EMIS\_ATOTJ and EMIS\_ATOTI had really large values (around 2e+11) at layer 3 and above.

The MCIP files has 34 layers, and the gridded emission files has only 1 layer, and the CTM\_EMLAYS was set to 1 to rule out the possible error caused by plume rise calculation.

The first thought was it might be the DEFINE FAMILY error, but when I check the EMIS\_ANO3J, layer 0 has values around 1 while layer 6 has values around 40, and EMIS\_ASO4J has max values at layer 10, basically the EMIS for variables has really large values at upper layer.

Meanwhile, the multi-layer aconc results seems to be normal.

Any idea how to solve this error?

Thanks a lot!  
Tris

---

<div class="post-metadata">

**Author:** ![hogrefe.christian](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@hogrefe.christian](https://forum.cmascenter.org/u/hogrefe.christian)\
**Post date:** [December 6, 2023, 2:15pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/2 "2023-12-06T14:15:15Z")

</div>

In addition to your gridded emission file(s) that only have 1 layer, do you have any inline point source files specified as input to CMAQ?

---

<div class="post-metadata">

**Author:** ![cgnolte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/cgnolte/32/53_2.png) [@cgnolte](https://forum.cmascenter.org/u/cgnolte)\
**Post date:** [December 6, 2023, 2:47pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/3 "2023-12-06T14:47:16Z")

</div>

Turning on the DESID diagnostic file for ALL streams should help pinpoint which sector(s) are involved.

---

<div class="post-metadata">

**Author:** ![Tris](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/tris/32/1810_2.png) [@Tris](https://forum.cmascenter.org/u/Tris)\
**Post date:** [December 7, 2023, 2:12am UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/4 "2023-12-07T02:12:43Z")

</div>

Thanks for your reply,  
the N\_EMIS\_PT was set to 0, so no point source files.

---

<div class="post-metadata">

**Author:** ![hogrefe.christian](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@hogrefe.christian](https://forum.cmascenter.org/u/hogrefe.christian)\
**Post date:** [December 7, 2023, 3:02pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/5 "2023-12-07T15:02:49Z")

</div>

Thank you for posting this information. I admit that I don’t have a good theory on what might be happening. I suggest you follow the advice by @cgnolte to use DESID diagnostic files to further investigate the issue.

---

<div class="post-metadata">

**Author:** ![cgnolte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/cgnolte/32/53_2.png) [@cgnolte](https://forum.cmascenter.org/u/cgnolte)\
**Post date:** [December 7, 2023, 7:37pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/6 "2023-12-07T19:37:05Z")

</div>

With no point source emission sectors, and CTM\_EMLAYS set to 1, I don’t see how you get any emissions of ATOTI or ATOTJ in upper layers.  
I just tried a run using v5.3.3, with the same PA control file commands you used, and my IPR output shows EMIS\_TOTJ and EMIS\_TOTI are identically zero.  
Perhaps try recompiling in debug mode to see if that reveals an error.

---

<div class="post-metadata">

**Author:** ![cgnolte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/cgnolte/32/53_2.png) [@cgnolte](https://forum.cmascenter.org/u/cgnolte)\
**Post date:** [December 8, 2023, 1:45pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/7 "2023-12-08T13:45:48Z")

</div>

Upon reflection, the fact that EMIS\_ATOTI and EMIS\_ATOTJ are zero in layer 1 as well as upper layers shows that the emissions process is not being reflected at all for aerosol species. I’ll have to check with some colleagues and look at the documentation and code a bit further. In the meantime, could you post your entire PA control file as an attachment? If that does not work, please email it to me at lastname dot firstname at epa dot gov.

---

<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:** [January 4, 2024, 4:27pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/8 "2024-01-04T16:27:08Z")

</div>

Hello,

Thank you for explaining this problem. One simple thing to try that was incorporated into v5.4 –

In vdiffproc.F, find the following line:

```auto
ALLOCATE ( EMIS_PA( NCOLS,NROWS,EMLAYS,N_SPC_DIFF ), STAT = ASTAT )

```

and update EMLAYS to NLAYS as follows:

```auto
ALLOCATE ( EMIS_PA( NCOLS,NROWS,NLAYS,N_SPC_DIFF ), STAT = ASTAT )

```

This should help resolve your use case (with PA\_BLEV\_ELEV set to “1 14”). However, we are still investigating why the code crashes when BLEV is set to a value greater than 1.

---

<div class="post-metadata">

**Author:** ![lizadams](https://avatars.discourse-cdn.com/v4/letter/l/49beb7/32.png) [@lizadams](https://forum.cmascenter.org/u/lizadams)\
**Post date:** [January 24, 2024, 3:27pm UTC](https://forum.cmascenter.org/t/really-large-ipr-emis-results-for-upper-layers/4562/9 "2024-01-24T15:27:16Z")

</div>

We believe the suggestion from @Ben_Murphy in this thread will work. Have you tried to implement it? We are marking this as solved, unless you let us know otherwise. There will also be a code fix that is currently being tested internally in a PR for the next public release.
