Error in running MCIP4.2 using WRFV3.8 outputs

Dear @wong.david-c, @tlspero, @lizadams, @bbaek, @Akhila, @hogrefe.christian, @cgnolte, @cjcoats

I am having problems with MCIP. I used MCIP4.2 (the one that accompanied CMAQ5.0.2) to process WRF3.8 wrf files but got this error:


*** SUBROUTINE: SETGRIDDEFS
MCIP output interval cannot be shorter than input
User-defined MCIP output interval = 60
Meteorology output interval = 61.0


 *** ERROR ABORT in subroutine SETGRIDDEFS
 ABNORMAL TERMINATION IN SETGRIDDEFS
 Date and time  0:00:00   Dec. 31, 2015   (2015365:000000)

Error running mcip

Attached are my WRF namelist.input and MCIP scripts. In my namelist.input script, I used 60 mins interval but I don’t know why the error. Can’t MCIP4.2 process WRF3.8 files?

Your help would be really appreciated.

Thanks.

namelist.input.txt (3.8 KB) run_mcip_olanew.csh (21.1 KB)

Catalyst

@Catalyst2682

Your error results from using a time step of 216 seconds in WRF (which is 6 times your delta-x of 36-km). This is ok by WRF standards for setting the time step, but it does not result in the output landing neatly on the hour. Therefore, MCIP read your output, and it determined that you had 61 minutes between output steps (because WRF will not round backwards).

An easy solution is to use a time step of 180 seconds in WRF, if you are able to re-run WRF here. Otherwise, write back and I’ll see what we can do…

–Tanya

Dear @tlspero,

Thanks for the prompt response. What confuses me much is that I have been using the same time step (216 s) with WRF4 and MCIP4.5 and MCIP5.0 without having this kind of error. I 'll use 180 as you suggested to run a day simulation and get back to you shortly.

Thanks sir.

Catalyst

Dear @tlspero ,

I just ran a day simulation now using 180 s. That error wasn’t encountered again but instead another error as shown below:


*** SUBROUTINE: GETLUSE
*** UNKNOWN LAND USE SOURCE AND MAX CATEGORIES
*** LAND USE SOURCE = MODIFIED_IGBP_MODIS
*** NUMBER OF CATEGORIES = 21


 *** ERROR ABORT in subroutine GETLUSE
 ABNORMAL TERMINATION IN GETLUSE
 Date and time  0:00:00   Dec. 27, 2015   (2015361:000000)

Error running mcip

Attached is my namelist.wps script. I used “default” for my geog_data_res. Could this be the cause of the error?

namelist.wps.txt (1.4 KB)

What should I do?

Thanks sir.

Catalyst

@Catalyst2682

This bug was fixed in MCIPv4.4. You should consider updating MCIP to ensure that you have all of the bug fixes in your version of MCIP.

I know you tried to use MCIPv5.0 at one point. Did you ever get that working?

–Tanya

1 Like

Dear @tlspero,

When I used 24 land categories instead of the default 21, it ran perfectly.

Thanks a lot and regards,

Catalyst

hi ,could you tell me how and where to change the number of categories from 21 to 24?thank you verymuch

Hello @peng,

Are you talking of WRF or MCIP? Your question isn’t really clear to me.

Regards,

Catalyst

sorry,@Catalyst2682 I’m a very beginner ,and I just run into the same problem as yours
" ** SUBROUTINE: GETLUSE
*** UNKNOWN LAND USE SOURCE AND MAX CATEGORIES
*** LAND USE SOURCE = MODIFIED_IGBP_MODIS
*** NUMBER OF CATEGORIES = 21

*** ERROR ABORT in subroutine GETLUSE
ABNORMAL TERMINATION IN GETLUSE

and you said "When I used 24 land categories instead of the default 21, it ran perfectly."
could you describe it in more detail please ? Thank you very much !

@peng,

You can make use of this as your resolution in your namelist.wps file:

geog_data_res = ‘usgs_30s+default’, ‘usgs_30s+default’, ‘usgs_30s+default’,

Then, you need to rerun the wrf and later mcip.

Let me know how it goes.

Regards,

Catalyst

1 Like

@Catalyst2682
thanks for your attention
it was worked with d01,but crashed when run d02 image could you please give me some hints?

image

@peng

MCIP inherits the land use from WRF, so you don’t change the number of land use categories via MCIP. The 21-category MODIS (which is now the default in WRF) includes a lake category that is fairly new, and it was not originally handled in MCIP. As I mentioned earlier in this thread, MCIP was corrected to handle the lake category in MODIS (which was formerly 20 categories rather than 21 categories).

–Tanya

@peng

The error with your I/O API files for d02 is because you are trying to overwrite the d01 files. If you move the d01 files to another directory, then d02 should work with MCIP.

–Tanya

@peng

I don’t know what your GRIDOUT error is caused by. You need to provide much more information than that to get some help.

–Tanya

@tlspero @Catalyst2682 Thanks for your advice and follow your advice ,I got it through .
I also willing to share my experience here if asked.
Regard
-Peng

1 Like