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

USING DEFAULT URBAN MORPHOLOGY warning despite using GloUCP dataset instead of NUDAPT44_1km

luyixiao

New member
I am encountering an issue with urban canopy parameterization while running wrf.exe with the GloUCP dataset. Here's my setup and the problem I'm facing:

Background

  • I am using GloUCP dataset as a replacement for NUDAPT44_1km to provide urban morphology parameters.
  • GloUCP is structured similarly to NUDAPT44_1km and includes 132 urban categories, which I verified by checking the URB_PARAM variable in my met_em files.

Issue

When running wrf.exe, I get the following warning:

USING DEFAULT URBAN MORPHOLOGY

This suggests that WRF is not recognizing my custom urban parameters from GloUCP(details can be checked in rsl.out.0000).

What I've Checked

  1. met_em files:
    • The URB_PARAM variable exists and contains 132 layers, matching NUDAPT44_1km's structure.
  2. wrfinput files:
    • Variables like URBAN and LU_INDEX are present (shows in the image), but HGT_URB2D, HI_URB2D, and LF_URB2D (mentioned in the NUDAPT44_1km documentation) are missing.

My Questions

  1. Is WRF actually using my GloUCP dataset?
    • How can I confirm if the model is using my custom urban parameters or falling back to defaults?
  2. How do I resolve the USING DEFAULT URBAN MORPHOLOGY warning?
    • Are there additional steps required to properly integrate GloUCP with WRF?
    • Do I need to modify the registry files or namelist options to recognize GloUCP's urban parameters?
 

Attachments

  • 1750382009584.png
    1750382009584.png
    222.8 KB · Views: 5
  • rsl.out.0000
    17.9 KB · Views: 3
Top