Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

How to make sure my URBAPARM.TBL is read

Kecheng Zhao

New member
I used Python code to replace urban category 13 in the geo_em file with 31 (low-density residential), 32 (high-density residential), and 33 (commercial). I also made corresponding modifications in LANDUSE.TBL and VEGPARM.TBL.

For example, I added entries like these:

  • 31, 10., .10, .97, 80., 3., 1.67, 18.9e5, 'Low Intensity Residential'
    32, 10., .10, .97, 80., 3., 1.67, 18.9e5, 'High Intensity Residential'
    33, 10., .10, .97, 80., 3., 1.67, 18.9e5, 'Commercial'


And also definitions like:

  • LOW_DENSITY_RESIDENTIAL
    31
    HIGH_DENSITY_RESIDENTIAL
    32
    COMMERCIAL
    33


After setting surface_input_source to 3, my wrfinput file also contains land use categories 31, 32, and 33.


So, I started running WRF, but I found the following two sections in rsl.error:

  • USING DEFAULT URBAN MORPHOLOGY
    USING DEFAULT URBAN MORPHOLOGY
    USING DEFAULT URBAN MORPHOLOGY

and

  • USING DEFAULT URBAN MORPHOLOGY
    WARNING, FRC_URB2D = 0 BUT IVGTYP IS URBAN
    WARNING, THE URBAN FRACTION WILL BE READ FROM URBPARM.TBL
    USING DEFAULT URBAN MORPHOLOGY
    WARNING, FRC_URB2D = 0 BUT IVGTYP IS URBAN
    WARNING, THE URBAN FRACTION WILL BE READ FROM URBPARM.TBL
    USING DEFAULT URBAN MORPHOLOGY
    WARNING, FRC_URB2D = 0 BUT IVGTYP IS URBAN
    WARNING, THE URBAN FRACTION WILL BE READ FROM URBPARM.TBL


This makes me confused about whether URBPARM.TBL was actually read. Why is 'DEFAULT URBAN MORPHOLOGY' being used? Shouldn't all settings be read from URBPARM.TBL?


Thank you for your answer.
 
Not sure if/when it is read, but there is a very simple test to figure it out. Delete it and rerun. If you get the same results, it is not being read. Otherwise, it is.
 
Top