CMAQ/MCIP/WRF/emission grid definition


#1

Hi all,

I am using WRFv3.7.1 to create met files for CMAQv5.2.1. My domain is over India, so the emissions input file are not generated by SMOKE. I know that WRF setups the grid and domain for CMAQ, but I am unclear on some of the specifics.

I have successfully run some WRF and CMAQ with the grid specifications below. My primary question is this: if I add a larger outer domain in order to nest my original smaller domain, and the coordinates of the lower-left corner change but the center stays the same, does the emission grid need to change somehow? That is could I update WRF in this manner and run CMAQ with the same, unchanged emission files?

WRF

  • e_we, e_sn = 160
  • dx, dy = 4000
  • map_proj = lambert
  • ref_lat = 28.0338
  • ref_lon = 77.2786
  • truelat1 = 26.0
  • truelat2 = 32.5
  • stand_lon = 77
  • lower-left corner lat = 25.15879
  • lower-left corner lon = 74.13348

EMIS/MCIP files

  • NCOLS, NROWS = 147
  • XCENT = 77
  • YCENT = 28.0338
  • XORIG = -266500
  • YORIG = -294000
  • BTRIM = 5
  • WRF_LC_REF_LAT = 28.0338

I’m not sure if I’ve described my question clear enough. Please let me know if I should provide more information.

Thanks,
B


#2

It sounds like you are looking to rerun WRF with a coarse (e.g., 12 km) outer domain, process it with MCIP, use that to drive CMAQ, and then use those time-varying coarse fields as inputs to BCON to derive boundary condition files that you will use as input in a rerun of your 4 km CMAQ simulation. For your coarse CMAQ simulation, you want to aggregate your existing fine-scale emissions onto the coarse grid.

I have not reverse-engineered a coarse grid myself, but it is possible. You of course have to ensure that your grids are aligned. To do this, you can use ref_x and ref_y in conjunction with ref_lat and ref_lon, as described in the WRF WPS user guide.
http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/users_guide_chap3.htm
Alternatively, you can create two nested WRF domains at once, where the inner domain is specified using i_parent_start and j_parent_start. Keep playing around with rerunning geogrid and tweaking your WPS namelist until your resulting geo_em.d02.nc matches the original geo_em.d01.nc file from your standalone 4km domain.

This may just be repeating what you already know, in which case it isn’t much help (sorry). Maybe someone else can provide further specifics, or possibly on the WRF user’s forum.

When you do get this worked out, it would be a great use case for us to have documented as one of our tutorials.