Hello, WRF team
I am using wps/3.9.1 and wrf/3.9.1.1 for a simulation using
The problem is that I found the LU_INDEX from the wrfout file is different from the LU_INDEX in the geo_em.d0*.nc file.
I have tested for both single urban land class (LU_INDEX ranged between 1 and 17 in my case) and multiple land class (LOW_DENSITY_RESIDENTIAL, HIGH_DENSITY_RESIDENTIAL, COMMERCIAL_INDUSTRIAL) (LU_INDEX ranged between 1 and 33) in the geo_em.d0*.nc file.
However, after the WRF ran, the LU_INDEX values in the wrfout files from both single and multiple urban classes are changed to between 1 and 18.
Would you please let me know if it is normal to have LU_INDEX changed in the wrfout files?
And why does the single and multiple urban class returned the same LU_INDEX in the wrfout file?
Is there any way to avoid such a problem?
Thanks,
Chang
I am using wps/3.9.1 and wrf/3.9.1.1 for a simulation using
- geog_data_res='default','default','default' in the namelist.wps file.
- input_from_file=.true.,.true.,.true., in the namelist.input file.
The problem is that I found the LU_INDEX from the wrfout file is different from the LU_INDEX in the geo_em.d0*.nc file.
I have tested for both single urban land class (LU_INDEX ranged between 1 and 17 in my case) and multiple land class (LOW_DENSITY_RESIDENTIAL, HIGH_DENSITY_RESIDENTIAL, COMMERCIAL_INDUSTRIAL) (LU_INDEX ranged between 1 and 33) in the geo_em.d0*.nc file.
However, after the WRF ran, the LU_INDEX values in the wrfout files from both single and multiple urban classes are changed to between 1 and 18.
Would you please let me know if it is normal to have LU_INDEX changed in the wrfout files?
And why does the single and multiple urban class returned the same LU_INDEX in the wrfout file?
Is there any way to avoid such a problem?
Thanks,
Chang