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

Namelist.input error with WRF 4.6.0 but not with 4.3.3 and real.exe crashes

alainF

Member
Hello, I have installed WRF v4.6.0 to upgrade my previous version wich was 4.3.3. I have been using v4.3.3 for 2 years with the namelist attached to this post. Now, I have a problem with real.exe. It crashes soon after the start by issuing the following error message:

wrf@wrf-virtual-machine:~/WRF/run$ tail rsl.error.0000
taskid: 0 hostname: wrf-virtual-machine
module_io_quilt_old.F 2931 T
------ ERROR while reading namelist physics ------
Maybe here?: grav_settling = 0, 0, 0,
Maybe here?: bl_mynn_tkebudget = 0, 0, 0,
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 11680
ERRORS while reading one or more namelists from namelist.input.
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

Was there any changes in v4.6.0 compared to 4.3.3 ?

I have erased grav_settling and bl_mynn_tkebudget from the namelist and then I get another crash from real.exe and it says :

wrf@wrf-virtual-machine:~/WRF/run$ tail rsl.error.0000
d01 2024-10-11_06:00:00 Timing for input 0 s.
d01 2024-10-11_06:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.06. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libc.so.6 00000E9069C42520 Unknown Unknown Unknown
real.exe 000000000097CA1F Unknown Unknown Unknown

Stack trace terminated abnormally.

I am quite confused,

Thank you for your help
 

Attachments

  • namelist.input
    9 KB · Views: 6
  • namelist.wps
    1.6 KB · Views: 1
Hi,
The issue is this namelist option:

Code:
bl_mynn_tkebudget          = 0, 0, 0,

This option was removed prior to the WRFV4.6.0 release. Since you have that set to 0, it shouldn't be an issue for you to just remove it. In the future if you get errors like this, you can look in the Registry/Registry.EM_COMMON file to see that the parameters still exist.
 
Top