I have converted the local climate zone (LCZ) of wudapt to geogrid using the w2w package and divided it into 41 categories. After successfully running real.exe, the error occurred while running wrf.exe. I checked that the NUM_LAND_CAT in the file generated by metgrid was already 41.
I realized that this may be related to the different indexes of different versions of WRF. I tried switching WRF from 4.3 to 4.5 and changing land-use categories from 41 to 61, but the error still exists. I noticed that when converting LCZ by W2W in d03 (which was my smallest region), it warned "FRC_URB and LCZs in LU_INDEX do not cover same extent".I have checked these two parameters and found that there was a significant difference between them and some of LU_INDEXs were even "null". Is the bug of WRF due to this warning by W2W? How should I do, could you please help me? Thank you all.
Describe your issue
Hi @matthiasdemuzere @andreazonato
I have converted the local climate zone (LCZ) of wudapt to geogrid using the w2w package and divided it into 41 categories. After successfully running real.exe, the error occurred while running wrf.exe. I checked that the NUM_LAND_CAT in the file generated by metgrid was already 41.
I realized that this may be related to the different indexes of different versions of WRF. I tried switching WRF from 4.3 to 4.5 and changing land-use categories from 41 to 61, but the error still exists. I noticed that when converting LCZ by W2W in d03 (which was my smallest region), it warned "FRC_URB and LCZs in LU_INDEX do not cover same extent".I have checked these two parameters and found that there was a significant difference between them and some of LU_INDEXs were even "null". Is the bug of WRF due to this warning by W2W? How should I do, could you please help me? Thank you all.
Hanguang
namelist.input.txt
w2w --version
w2w 0.5.0
nc-config --all
Installed Packages
Traceback
No response