Attempting to utilize WRF output data derived from WRF run with USGS land use data and NOAH LSM setting, running CMAQ (v5.4 and v5.5) with the corresponding MCIP output results in the error message “Land use scheme not supported” when I set the dry deposition scheme as M3DRY. But it seems CMAQ can run successfully when setting the dry deposition scheme as STAGE (with v5.4).
In order to run CMAQ with M3DRY deposition scheme, I wonder if the WRF run has to be using MODIS land use data and/or applying Pleim-Xiu scheme.
could you please clarify whether your WRF run used the 24 category or 28 category USGS scheme? Using the standard 24 category USGS scheme should not create any issues in CMAQ, but based on the discussions in this thread, using the newer 28 category USGS scheme may cause issues.
Using the USGS24, MODIS, or NLCD40 (NLCD40 over the US, blended with MODIS for non-US portions of North America) land use schemes should all work.
As far as I know, the 24 category USGS land use scheme should work for both M3DRY and STAGE. To help us track down why it doesn’t for M3DRY, could you please post the full error message from the log file - it should show the program (subroutine) name within a few lines of the “Land use scheme not supported” message.
In addition, it would help us if you could please share your GRIDCRO2D, METCRO2D, and LUFRAC_CRO files for one day. You can upload the data to the CMAS data warehouse incoming folder using these instructions.
Regarding the error message, it’s indeed very short. Please find it as follows.
Also trying to upload the files but it seems it doesn’t allow to do so with the link to the Google Drive.
Regards,
Wen
*** ERROR ABORT in subroutine Init_LSM on PE 000
Land use scheme not supported
MPI_ABORT was invoked on rank 1 in communicator MPI_COMM_WORLD
with errorcode 1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
** Runscript Detected an Error: CGRID file was not written. **
** This indicates that CMAQ was interrupted or an issue **
** exists with writing output. The runscript will now **
** abort rather than proceeding to subsequent days. **