# Different year for CEM/ptegu emissions

**URL:** <https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705>\
**Category:** Emissions Inventory\
**Created:** [May 21, 2019, 2:35pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705 "2019-05-21T14:35:17Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![jschnell](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@jschnell](https://forum.cmascenter.org/u/jschnell)\
**Post date:** [May 21, 2019, 2:35pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/1 "2019-05-21T14:35:17Z")

</div>

I’m using the EPA’s 2016 alpha platform to process emissions. My simulated time period is over the summer of 2018. I’d like to know how to download and format the 2018 CEM data from the EPA Air Markets as inputs instead. It seems I’ll need the FF10 egucems\* files, a “cemsum” file, and HOUR\_UNIT files for each month I want to simulate. What is the recommended approach?

---

<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:** [May 21, 2019, 3:28pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/2 "2019-05-21T15:28:24Z")

</div>

Hi, the beta platform is available now and has more updated data for many sectors.

The inputs for that platform and documentation are here: [  
http://views.cira.colostate.edu/wiki/wiki/10197](http://views.cira.colostate.edu/wiki/wiki/10197)

The 2018 CEMS data are here: [  
https://ampd.epa.gov/ampd/](https://ampd.epa.gov/ampd/)

Go to the Prepackaged Data tab and go to the bottom to find the data in SMOKE format.

Keep in mind that the annual inventory is 2016 and there could be retirements and other changes in the operation of the sources between 2016 and 2018.

---

<div class="post-metadata">

**Author:** ![jschnell](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@jschnell](https://forum.cmascenter.org/u/jschnell)\
**Post date:** [May 21, 2019, 3:35pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/3 "2019-05-21T15:35:32Z")

</div>

Thank you @eyth.alison!

---

<div class="post-metadata">

**Author:** ![lexiewilson](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/lexiewilson/32/2018_2.png) [@lexiewilson](https://forum.cmascenter.org/u/lexiewilson)\
**Post date:** [January 21, 2022, 4:36pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/4 "2022-01-21T16:36:46Z")

</div>

I am trying to use the 2016 v2 platform ptegu scripts to process CEM emissions from 2013. I downloaded the 2013 files from the link you provided on this thread. I ran cemscan with this script:  
[run\_cemscan\_2013.csh](https://forum.cmascenter.org/uploads/short-url/zYruIxw5PZ4dNwiQLguCi28z06f.csh) (525 Bytes)  
When I run the ptegu daily script, I get this error:

```auto
SCRIPT ERROR: Some file patterns not matched for style Hourly
              According to MULTIFILE_NAMEBREAK, the file prefixes are:
                 /uufs/chpc.utah.edu/common/home/daq-group2/SMOKE4_7/2017by_13winter/inputs/cem/HOUR_UNIT
              Check file names and rerun
ERROR: Could not run combine_data.csh for hourly list file in Annual_area

```

I suspect the files I downloaded form AMPD are not quite in the right format for use with this script.  
I see in the 2016v2 platform documentation that “we’ve split  
the data into months and days as needed for our scripts, and run the data  
through a “CEM correct” program.” I found this cem correct program in the 2016 v1 folder:  
[https://gaftp.epa.gov/Air/emismod/2016/v1/2016emissions/cemcorrect\_2.1\_Nov12.zip](https://gaftp.epa.gov/Air/emismod/2016/v1/2016emissions/cemcorrect_2.1_Nov12.zip)  
But I’m unsure how to use the “cem correct” program. Is there guidance for this program?

---

<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:** [January 24, 2022, 2:22pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/5 "2022-01-24T14:22:29Z")

</div>

You can try changing the ptegu daily run script to increase the number of the NAMEBREAK\_HOURLY variable by 1.

If that doesn’t work, please send your list of hourly CEMS files, i.e.:

`/uufs/chpc.utah.edu/common/home/daq-group2/SMOKE4_7/2017by_13winter/inputs/cem/HOUR_UNIT*`

---

<div class="post-metadata">

**Author:** ![lexiewilson](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/lexiewilson/32/2018_2.png) [@lexiewilson](https://forum.cmascenter.org/u/lexiewilson)\
**Post date:** [January 24, 2022, 4:17pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/6 "2022-01-24T16:17:57Z")

</div>

I changed the NAMBREAK\_HOURLY variable from 4 to 5 and am still getting the same error as before. Here is my file list that I input to cemscan:  
[filelist2013.txt](https://forum.cmascenter.org/uploads/short-url/2w7ZHEujMIpGisvm7BWn7R5MBoW.txt) (1.2 KB)

---

<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:** [January 24, 2022, 5:09pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/7 "2022-01-24T17:09:15Z")

</div>

Did you download the files from the SMOKE-ready files area? There are a couple areas of the CAMD site…

---

<div class="post-metadata">

**Author:** ![lexiewilson](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/lexiewilson/32/2018_2.png) [@lexiewilson](https://forum.cmascenter.org/u/lexiewilson)\
**Post date:** [January 24, 2022, 5:19pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/8 "2022-01-24T17:19:39Z")

</div>

Here are the first few lines of my january HOUR\_UNIT file:

```auto
3,"1","130101",0,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",1,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",2,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",3,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",4,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",5,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",6,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",7,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",8,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",9,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",10,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",11,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",12,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",13,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",14,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",15,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",16,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",17,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",18,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",19,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",20,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",21,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",22,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","130101",23,-9,-9,-9,0,-9,-9,-9,,,,,-9

```

Here is a screenshot of where I downloaded the files:

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/3/39c5a531524a3ae29128c2bc802108fe40cb86a5.png)

---

<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:** [January 24, 2022, 6:16pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/9 "2022-01-24T18:16:02Z")

</div>

Do they match the format of the files for the 2016/2017 platforms?

---

<div class="post-metadata">

**Author:** ![lexiewilson](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/lexiewilson/32/2018_2.png) [@lexiewilson](https://forum.cmascenter.org/u/lexiewilson)\
**Post date:** [January 24, 2022, 6:32pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/10 "2022-01-24T18:32:24Z")

</div>

It looks like it - but maybe I am missing something! Here are the first few lines from the january HOUR\_UNIT file from the 2017 platform:

```auto
3,"1","170101",0,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",1,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",2,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",3,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",4,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",5,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",6,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",7,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",8,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",9,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",10,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",11,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",12,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",13,-9,-9,-9,0,-9,-9,-9,,,,,-9
3,"1","170101",14,-9,-9,-9,0,-9,-9,-9,,,,,-9

```

I notice that the 2017 platform files have 2 HOUR\_UNIT files for each month:  
 ![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/1/1574350f5c00b67fad95be297209396413858df6.png)  
while the 2013 files I downloaded only have 1 per month:  
 ![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/0/02f839ac0c4260459491a583a38a56a3173e4125.png)

Is this where the cem correct script might come into play?

---

<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:** [January 24, 2022, 6:39pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/11 "2022-01-24T18:39:45Z")

</div>

So there is an additional step involved in using the files. The SMOKE scripts expect to find two files per month, one with the last day of the month and one with all of the other days of the month, plus an additional file for December 31 of the previous year. A sample script to create these files from the full-month CEMs is pasted below. This script (after modifying for 2013) should be run in the directory with the HOUR\_UNIT\_2013\_\* files. The outputs will go in a subdirectory called SMOKE/, and the SMOKE run scripts should then point to the SMOKE/ files.

A sample script is provided for 2018 as an example. Save this text to an executable .csh file

#!/bin/csh -f

grep 180131 HOUR\_UNIT\_2018\_01.txt \> SMOKE/HOUR\_UNIT\_2018\_01\_31jan\_2018.txt

sed ‘/180131/d’ HOUR\_UNIT\_2018\_01.txt \> SMOKE/HOUR\_UNIT\_2018\_01\_1-30jan\_2018.txt

grep 180228 HOUR\_UNIT\_2018\_02.txt \> SMOKE/HOUR\_UNIT\_2018\_02\_28feb\_2018.txt

sed ‘/180228/d’ HOUR\_UNIT\_2018\_02.txt \> SMOKE/HOUR\_UNIT\_2018\_02\_1-27feb\_2018.txt

grep 180331 HOUR\_UNIT\_2018\_03.txt \> SMOKE/HOUR\_UNIT\_2018\_03\_31mar\_2018.txt

sed ‘/180331/d’ HOUR\_UNIT\_2018\_03.txt \> SMOKE/HOUR\_UNIT\_2018\_03\_1-30mar\_2018.txt

grep 180430 HOUR\_UNIT\_2018\_04.txt \> SMOKE/HOUR\_UNIT\_2018\_04\_30apr\_2018.txt

sed ‘/180430/d’ HOUR\_UNIT\_2018\_04.txt \> SMOKE/HOUR\_UNIT\_2018\_04\_1-29apr\_2018.txt

grep 180531 HOUR\_UNIT\_2018\_05.txt \> SMOKE/HOUR\_UNIT\_2018\_05\_31may\_2018.txt

sed ‘/180531/d’ HOUR\_UNIT\_2018\_05.txt \> SMOKE/HOUR\_UNIT\_2018\_05\_1-30may\_2018.txt

grep 180630 HOUR\_UNIT\_2018\_06.txt \> SMOKE/HOUR\_UNIT\_2018\_06\_30jun\_2018.txt

sed ‘/180630/d’ HOUR\_UNIT\_2018\_06.txt \> SMOKE/HOUR\_UNIT\_2018\_06\_1-29jun\_2018.txt

grep 180731 HOUR\_UNIT\_2018\_07.txt \> SMOKE/HOUR\_UNIT\_2018\_07\_31jul\_2018.txt

sed ‘/180731/d’ HOUR\_UNIT\_2018\_07.txt \> SMOKE/HOUR\_UNIT\_2018\_07\_1-30jul\_2018.txt

grep 180831 HOUR\_UNIT\_2018\_08.txt \> SMOKE/HOUR\_UNIT\_2018\_08\_31aug\_2018.txt

sed ‘/180831/d’ HOUR\_UNIT\_2018\_08.txt \> SMOKE/HOUR\_UNIT\_2018\_08\_1-30aug\_2018.txt

grep 180930 HOUR\_UNIT\_2018\_09.txt \> SMOKE/HOUR\_UNIT\_2018\_09\_30sep\_2018.txt

sed ‘/180930/d’ HOUR\_UNIT\_2018\_09.txt \> SMOKE/HOUR\_UNIT\_2018\_09\_1-29sep\_2018.txt

grep 181031 HOUR\_UNIT\_2018\_10.txt \> SMOKE/HOUR\_UNIT\_2018\_10\_31oct\_2018.txt

sed ‘/181031/d’ HOUR\_UNIT\_2018\_10.txt \> SMOKE/HOUR\_UNIT\_2018\_10\_1-30oct\_2018.txt

grep 181130 HOUR\_UNIT\_2018\_11.txt \> SMOKE/HOUR\_UNIT\_2018\_11\_30nov\_2018.txt

sed ‘/181130/d’ HOUR\_UNIT\_2018\_11.txt \> SMOKE/HOUR\_UNIT\_2018\_11\_1-29nov\_2018.txt

grep 181231 HOUR\_UNIT\_2018\_12.txt \> SMOKE/HOUR\_UNIT\_2018\_12\_31dec\_2018.txt

sed ‘/181231/d’ HOUR\_UNIT\_2018\_12.txt \> SMOKE/HOUR\_UNIT\_2018\_12\_1-30dec\_2018.txt

sed ‘s/181231/171231/g’ SMOKE/HOUR\_UNIT\_2018\_12\_31dec\_2018.txt \> SMOKE/HOUR\_UNIT\_2017\_12\_31dec\_2018.txt

Here is a list of the resulting files that come out for 2018:

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2017\_12\_31dec\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_01\_1-30jan\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_01\_31jan\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_02\_1-27feb\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_02\_28feb\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_03\_1-30mar\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_03\_31mar\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_04\_1-29apr\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_04\_30apr\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_05\_1-30may\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_05\_31may\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_06\_1-29jun\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_06\_30jun\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_07\_1-30jul\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_07\_31jul\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_08\_1-30aug\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_08\_31aug\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_09\_1-29sep\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_09\_30sep\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_10\_1-30oct\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_10\_31oct\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_11\_1-29nov\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_11\_30nov\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_12\_1-30dec\_2018.txt

/work/EMIS/em\_v8.1/2018platform/work/cems/corrected/SMOKE/HOUR\_UNIT\_2018\_12\_31dec\_2018.txt

---

<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:** [January 24, 2022, 6:59pm UTC](https://forum.cmascenter.org/t/different-year-for-cem-ptegu-emissions/705/12 "2022-01-24T18:59:00Z")

</div>

Yes I just sent another post on this topic
