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

Problem with Eta Ferrier microphysics

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

momodiallosn

New member
Hi,
Doing the previously given modifications to the code allow outputing the desired sfclay variable. However, For for some run, WRF crashes after more or less 18 hours when Eta Ferrier (5) microphysic is used. The following message appear in rsl.error*: "Invalid memory reference", and WARN5: Nan temperature which is surprisingly related to the use of Eta Ferrier (https://github.com/wrf-model/WRF/blob/master/phys/module_mp_fer_hires.F).
I have performed the following test:

-WRF v4.1.2 with sfclay PBL variables edits , with Eta Ferrier==> crash after 18h run
-WRF v4.0.3 with sfclay PBL variables edits , with Eta Ferrier ==> crash after 18h run
-WRF v4.0.3 with sfclay PBL variables edits , with WSM6 ==> ok
-WRF v4.0.3 without sfclay PBL variables edits , with Eta Ferrier ==> ok

Is there any explanation for this phenomena ? Please find attached to this message the rsl.error file, the namelist and the modification made in WRF v4.0.3 to successfully outptut the desired sfclay PBL variable.

Sincerely yours
 

Attachments

  • module_first_rk_step_part1.F
    103.1 KB · Views: 41
  • module_first_rk_step_part2.F
    51.9 KB · Views: 40
  • namelist.input
    5.7 KB · Views: 44
  • namelist.wps
    1.1 KB · Views: 44
  • Registry.EM_COMMON
    367.4 KB · Views: 38
  • solve_em.F
    245.7 KB · Views: 38
Hi,
I have moved this topic to the WRF Physics topic, as this is a new problem no longer related to the previous section. Someone will respond to your inquiry soon.
 
Hi,

Please examine your wrfout files, find when and where the first NaN value appeared, and trace back to other variables that may possibly lead to the NaN values. I believe it is related to the modification you have made in the codes.
 
Top