No data or very low values on CMAQ simulation

Hi all!

we are working on running a high-res simulation using SMOKE and CMAQ for a domain located in Paraguay (South America).

We ran a 24 hour simulation in CMAQ and we are seeing either no data (meaning zero values) or very low values in the CMAQ output.

We are using SMOKE v4.8.1 and CMAQ v5.3.2 to do our simulations and our process was like this:

  • We focused on July 2019 for this first simulation
  • We generated emissions in SMOKE for 5 sectors: Energy, Industry, Residential, Ships and Transport
  • We ran into quite a few issues with SMOKE but we were able to reach a point where we could run the model for 5 days periods, anything longer and the model didn’t completed successfully, so to complete the month we had to run the model 5 times (to complete the whole month)
  • Since we have 5 .ncf files for every sector, we used the ncrcat tool to concat all 5 files into a single .ncf sector file
  • We then configured CMAQ to use the 5 emission files and ran the model for 24 hours (July 1st, 2019)

I’ve uploaded the following to a Google Drive folder:

  • Emission files for each sector
  • bldit_cctm.csh script
  • run_cctm_ASUNCION.csh and its output run_cctm_ASUNCION.log
  • the CTM_LOG for each processor

Anyone had a similar issue in the past?

Thank you!

CMAQ, SMOKE, and related models use the I/O API, which is an interface. The underlying file format is usually (virtually always) netCDF, but these models do not call netCDF I/O routines directly.

In using ncrcat, one of the netCDF Operators (NCO), you have gone outside the I/O API interface. The resulting outputs do not conform to the I/O API, so errors ensue. Instead you should use programs built on the I/O API, such as m3xtract, COMBINE, or other related programs.

thanks @cgnolte for the quick response, where do I find documentation on those tools you mentioned? I’ll re-process our files with those tools and re-try again.

Lots of documentation is available at the CMAS website and EPA’s GitHub. These links describe the specific tools I mentioned.

perfect thank you very much @cgnolte !