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

Not able to restart WRF from wrfrst.

M

Manuarii

Member
Hi,

I recently attempted to use WRFv4.5.1 with the new BEP_BEM parametrization that work with SMS-3DTKE. The model ran without any issues initially, but when I tried to restart the simulation due to a timeout, I encountered problems and couldn't rerun it. This is the first time I've faced this issue, and it occurs when calling spectral nudging. I also tried restarting the simulation from scratch, but the same problem persisted. Do you have any insights into what might be causing this issue? I have attached the rsl.error files and namelist.input for your reference.

Note : I have modified the original tables from MPTABLE, VEGPARM, LANDUSE, and URBPARAM. Specifically, for the first three tables, I updated the classes based on a configuration previously used for WRFv4.4 with BEP_BEM. This modification allows the tables to work with 41 classes, as I am using LCZ with USGS. But not sure if it is the issue.

Thanks,
 

Attachments

  • namelist.input
    12.6 KB · Views: 1
  • rsl.error.zip
    2.8 MB · Views: 0
Ming Chen said:
We are aware of an issue when LCZ urban is used with USGS. Please take a look at the bug fix below:

github.com

Bug fix for overwriting of LCZ urban cells in LU_INDEX with default USGS urban category. by lpilz · Pull Request #2153 · wrf-model/WRF

TYPE: bug fix KEYWORDS: LCZ, USGS SOURCE: Lukas Pilz (Heidelberg University) DESCRIPTION OF CHANGES: Problem: As shown in #2152, for USGS data the wrfinput LU_INDEX field has major differences to t...
github.com github.com

I am suspicious that this might be the reason?
Click to expand...

Thank you for your response. Upon reviewing the bug fix, we recognize that we have previously encountered and resolved this issue in other simulations. Our solution involved "transplanting" the value of LU_INDEX from met_em to wrfinput, adjusting the water mask (from 28 to 16), and updating IVGTYP with the LU_INDEX value from the met_em file. This approach resolved the problem and allowed us to run WRF successfully. However, this was done using WRF version 4.4 with an older version of BEP_BEM, which did not support the 3D scheme such as SMS-3DTKE.

I have since spoken directly with the developer who works on BEP_BEM, who provided me with the newer version of WRF, v4.5.1, which now supports SMS-3DTKE. Given that we have already resolved this issue using a Python script, I do not believe the current problem stems from the same cause. Nevertheless, I appreciate the bug report, as it allows us to address the issue directly within the WRF code, eliminating the need for the Python script workaround.

Here, with the newer version of WRF, combine with newer version of BEP_BEM, it seems that, even with same parameter from the last version we use, I can't restart wrf from my restart file.
 
Last edited:
Hi,

Recently, I attempted to determine if the issue was due to the nesting configuration by running only the first domain. Additionally, I experimented with replacing the 3D turbulence scheme, SMS-3DTKE, with different parameters and tried using an alternative PBL scheme. However, the problem persisted. It seems that the provided WRF configuration might be the root cause of the issue.
 
You must log in or register to reply here.
Top