CMAQ 5.2_running run_cctm.csh

CMAQ
1

Hi,

Can anyone suggest the reason for this error message in CMAQ 5.2 and how it can be resolved?

—>> WARNING in subroutine OPEMIS on PE 000
Emissions species NO2 not found on EMIS_1
M3WARN: DTBUF 0:00:00 Jan. 1, 2017 (2017001:000000)

 >>--->> WARNING in subroutine OPEMIS on PE 000
 Emissions species NO2 not found on EMIS_1
 M3WARN:  DTBUF 0:00:00   Jan. 1, 2017  (2017001:000000)

 >>--->> WARNING in subroutine OPEMIS on PE 000
 Emissions species NO2 not found on EMIS_1
 M3WARN:  DTBUF 0:00:00   Jan. 1, 2017  (2017001:000000)

 >>--->> WARNING in subroutine OPEMIS on PE 000
 Emissions species NO2 not found on EMIS_1
 M3WARN:  DTBUF 0:00:00   Jan. 1, 2017  (2017001:000000)

 >>--->> WARNING in subroutine OPEMIS on PE 000
 Emissions species NO2 not found on EMIS_1
 M3WARN:  DTBUF 0:00:00   Jan. 1, 2017  (2017001:000000)

 >>--->> WARNING in subroutine OPEMIS on PE 000
 Emissions species NO2 not found on EMIS_1
 M3WARN:  DTBUF 0:00:00   Jan. 1, 2017  (2017001:000000)

 >>--->> WARNING in subroutine OPEMIS on PE 000
 Emissions species NO2 not found on EMIS_1
 M3WARN:  DTBUF 0:00:00   Jan. 1, 2017  (2017001:000000)

 >>--->> WARNING in subroutine OPEMIS on PE 000
 Emissions species NO2 not found on EMIS_1
 M3WARN:  DTBUF 0:00:00   Jan. 1, 2017  (2017001:000000)

Kindly looking forward to your response

Thanks

John

2

What is EMIS_1 ? (the log-message from OPEN3 should tell you) And is that file available, with appropriate permissions?

What does % ncdump -h [this file] say about the variables in the file? Is NO2 one of the variables?
If not, something is probably wrong with your emissions-setup.

If so, is date&time 2017001:000000 one of the time-steps for the file (look at SDATE, STIME, TSTEP, and the time-dimension)? If not, you probably have an incorrect date-and-time setup…

3

Thanks for the rapid response, EMIS_1 is the emission file from smoke + megan

ncdump -h shows that NO2 is contained in the file and the time is also contained in the emission file.

Best wishes,

John

4

It has now been resolved thanks