Hello everyone, I would like to ask you a question. I encountered an error while running CCTM and hope to get your help
Some errors are as follows:
*** ERROR ABORT in subroutine retrieve_grid_cr on PE 003
Error interpolating variableLUFRAC_01 from GRID_CRO_2D
PM3EXIT: date&time specified as 0
Date&time specified as 0
The version I use is as follows: CMAQ5.4；WRF4.1.1;The MCIP I use comes with CMAQ5.4；The script I use is run_cctm_2010_4CALIF1.csh。
run_cctm_2010_4CALIF1.csh (36.7 KB)
If you used the MCIP version that came with CMAQ5.4, you need to define the LUFRAC_CRO variable in your run script to point to your LUFRAC_CRO_* file, along with defining the other variables pointing to the MCIP output files.
To do so, change this line
#setenv LUFRAC_CRO $METpath/LUFRAC_CRO.$GRID_NAME.${NZ}L.$YYMMDD
in run_cctm_2010_4CALIF1.csh to
setenv LUFRAC_CRO $METpath/LUFRAC_CRO_${APPL}.nc
analogous to the setting for the other MCIP output files in this example CCTM run script.
Thanks for your reply, I uncommented the comment and rerun it, but it still works differently. I checked the LOG, but no error was found. I hope you can help me check it. Thank you very much!
If you examine your log file, you will see that the program is trying to open the LUFRAC_CRO file generated by the version of MCIP that comes with CMAQv5.4 but cannot find and open the file.
"GRID_CRO_2D" opened as OLD:READ-ONLY
File name "/disk1/scl/CMAQ/CMAQ-5.4/data/mcip/202001/GRIDCRO2D_china1.nc"
File type GRDDED3
Execution ID "mcip"
Grid name "china1_CROSS"
Dimensions: 128 rows, 188 cols, 1 lays, 6 vbles
NetCDF ID: 131072 opened as READONLY
Time-independent data.
"GRID_DOT_2D" opened as OLD:READ-ONLY
File name "/disk1/scl/CMAQ/CMAQ-5.4/data/mcip/202001/GRIDDOT2D_china1.nc"
File type GRDDED3
Execution ID "mcip"
Grid name "china1_DOT"
Dimensions: 129 rows, 189 cols, 1 lays, 9 vbles
NetCDF ID: 196608 opened as READONLY
Time-independent data.
LUFRAC_CRO :/disk1/scl/CMAQ/CMAQ-5.4/data/mcip/202001/LUFRAC_CRO.china1.29L.200103
>>--->> WARNING in subroutine OPEN3
File not available.
>>--->> WARNING in subroutine gridded_files_se on PE 003
Could not open LUFRAC_CRO file
Solution: Reading Land Use Fractions from GRID_CRO_2D file
Because land use fractions are contained in LUFRAC_CRO rather than GRIDCRO2D in this version of MCIP, CCTM later fails when it cannot obtain land use fraction. [CCTM does not fail right away when not being able to open LUFRAC_CRO to allow for backward compatibility with older versions of MCIP that did not create this file but had land use fractions included in GRIDCRO2D].
This points to an error in your run script in how you specify that file. Looking at the naming convention for your other MCIP files (e.g. /disk1/scl/CMAQ/CMAQ-5.4/data/mcip/202001/GRIDDOT2D_china1.nc), the script should be looking for /disk1/scl/CMAQ/CMAQ-5.4/data/mcip/202001/LUFRAC_CRO_china1.nc, but it seems you configured it to look for /disk1/scl/CMAQ/CMAQ-5.4/data/mcip/202001/LUFRAC_CRO.china1.29L.200103 which doesn’t exist.
Updating the script to look for the correct file should fix this issue. You can examine the log file to verify that LUFRAC_CRO was opened successfully.
I apologize, but I still haven’t been able to resolve this issue. You mentioned ‘Because land use fractions are contained in LUFRAC_CRO rather than GRIDCRO2D in this version of MCIP,’ but when I checked the files generated by running MCIP, I didn’t find this LUFRAC_CRO. So, did I encounter a problem during the MCIP execution? I apologize if this is a very simple question as I am just starting to learn the CMAQ model, but I would really appreciate your help. Thank you very much!
The following images are the output files of MCIP
If you are indeed using MCIP that was released with CMAQv5.4, then yes, you should have a LUFRAC_CRO after running MCIP.
Did you make sure to use the run script that was included in the folder “PREP/mcip/scripts/” of the CMAQv5.4 package, not a run script you might have had on your system from an earlier CMAQ version? Specifically, did your MCIP run script contain the following code block that includes the specification of the LUFRAC_CRO output file?
setenv GRID_BDY_2D $OutDir/GRIDBDY2D_${APPL}.nc
setenv GRID_CRO_2D $OutDir/GRIDCRO2D_${APPL}.nc
setenv GRID_DOT_2D $OutDir/GRIDDOT2D_${APPL}.nc
setenv MET_BDY_3D $OutDir/METBDY3D_${APPL}.nc
setenv MET_CRO_2D $OutDir/METCRO2D_${APPL}.nc
setenv MET_CRO_3D $OutDir/METCRO3D_${APPL}.nc
setenv MET_DOT_3D $OutDir/METDOT3D_${APPL}.nc
setenv LUFRAC_CRO $OutDir/LUFRAC_CRO_${APPL}.nc
setenv SOI_CRO $OutDir/SOI_CRO_${APPL}.nc
setenv MOSAIC_CRO $OutDir/MOSAIC_CRO_${APPL}.nc
Thanks for you reply.
and i make sure i use the run script that was included in the folder “PREP/mcip/scripts/” of the CMAQv5.4 package. Besides, i check the run_mcip.csh, it also contain the following code. I don’t know why it’s not generated the LUFRAC_CRO output. 
Hi @Sunchanglei!
@hogrefe.christian is correct that you should have the fractional land use after running MCIP in the file LUFRAC_CRO. However, you need to ensure that you provided the fractional land use information from WRF to MCIP in order to make those data available for CMAQ.
There are two pathways to provide the fractional land use data from WRF to MCIP: via the WRF output or via the output from Geogrid, which defines the simulation domain for WRF. The fractional land use data are not written to WRF output (wrfout) by default, so you would need to intentionally request (through the WRF Registry) that those data are written. If you (or whoever ran WRF) modified the Registry to include fractional land use (LANDUSEF) data in the wrfout files, then the data would be there and would be processed by MCIP. If WRF was run without writing LANDUSEF to wrfout, then instead you can provide the WRF Preprocessing System (WPS) Geogrid output (geo_em) file to MCIP via the script (and toggle the switch in the script to read that file), and MCIP can pull those data from there.
If you need to rerun MCIP to create the LUFRAC_CRO file, you only need to rerun one time step (not the full length of your WRF simulation) because the fractional land use does not change over time.
Hope this helps!
–Tanya
