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

Run WRF 1km using ERA5: lack of SOIL_LAYERS (met_em*.nc)

Zoo

New member
Hi, all
I got a strange problem when I run WRF 1km using ERA5. The detail is the rsl.error.0000 noticed the NUM_METGRID_SOIL_LEVELS = 0, mismatched with the namelist (Fig.1, and namelist attached). I changed it in namelist, but another error came across (Fig.2). It said there's no psfc, so I checked the met_em* and FILE* created in WPS4.0 (FILE_1km.log and met_em_1km.log attached), the Vtable is Vtable.ECMWF, there's no such variables. Also, I tried add sfcp_to_sfcp = .true. in namelist, but it didn't help neither.
However, I use the definitely same ERA5 data to run the same case in 3km and 8km (namelist are just varied the resolution and grids), there's no any problem, and I got the results successfully. So I'm sure the initialization data is quite alright. Also I checked the met_em* and FILE* in WPS, SOIL_LAYERS exist (FILE_8km.log and met_em_8km.log attached).

I really have no idea about this, can you give me some suggestions? Thank you for your help.
 

Attachments

  • namelist_1km.input
    4.4 KB · Views: 1
  • met_em_1km.log
    18.4 KB · Views: 0
  • FILE_1km.log
    70.2 KB · Views: 0
  • Fig.2.png
    Fig.2.png
    52.3 KB · Views: 2
  • Fig.1.png
    Fig.1.png
    40.9 KB · Views: 2
  • namelist_1km.wps
    1.6 KB · Views: 1
  • FILE8km.log
    77.8 KB · Views: 0
  • met_em_8km.log
    22.1 KB · Views: 1
Hi, all
I got a strange problem when I run WRF 1km using ERA5. The detail is the rsl.error.0000 noticed the NUM_METGRID_SOIL_LEVELS = 0, mismatched with the namelist (Fig.1, and namelist attached). I changed it in namelist, but another error came across (Fig.2). It said there's no psfc, so I checked the met_em* and FILE* created in WPS4.0 (FILE_1km.log and met_em_1km.log attached), the Vtable is Vtable.ECMWF, there's no such variables. Also, I tried add sfcp_to_sfcp = .true. in namelist, but it didn't help neither.
However, I use the definitely same ERA5 data to run the same case in 3km and 8km (namelist are just varied the resolution and grids), there's no any problem, and I got the results successfully. So I'm sure the initialization data is quite alright. Also I checked the met_em* and FILE* in WPS, SOIL_LAYERS exist (FILE_8km.log and met_em_8km.log attached).

I really have no idea about this, can you give me some suggestions? Thank you for your h

could be that you are exceeding the ratio for downscaling and need to nest it to 1km resolution. ERA5 is ~9km so a 1:9 ratio is too big, try running two 1:3 nests, so 3km -> 1km and see if that fixes it.
 
could be that you are exceeding the ratio for downscaling and need to nest it to 1km resolution. ERA5 is ~9km so a 1:9 ratio is too big, try running two 1:3 nests, so 3km -> 1km and see if that fixes it.
Thank you for your suggestions. I tried the nest (1km-3km, namelist,wps attached), it didn't work (NUM_METGRID_SOIL_LEVELS = 0).
Following your idea, I interpolated the ERA5 (0.25°) into 0.1° to drive, same results...
 

Attachments

  • met_em_d01.log
    17.4 KB · Views: 0
  • met_em_d02.log
    17.4 KB · Views: 0
  • namelist.wps
    1.6 KB · Views: 1
Hi, everyone
I reload ERA5 dataset with larger area, and that succeed. Maybe it's just a problem with datasets.
 
Top