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

Obs nudging - Unknown regime type 0.0

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.

wallis

Member
Unknown regime type 0.0 at grid coordinate i = 96 j = 505
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 476
fddaobs_driver: compute_VIH STOP
-------------------------------------------

I get this error very often with observation nudging, does anyone know what causes it or how to fix it?
 
Nudging config:
obs_nudge_opt = 1,1,
max_obs = 190000,
fdda_end = 6000,6000
obs_twindo = 0.6667,0.6667
obs_ipf_errob = .true.,
obs_nudge_temp = 1,1,
obs_nudge_mois = 1,1,
obs_nudge_wind = 1,1,
obs_coef_temp = 6.E-4,6.E-4,
obs_coef_wind = 6.E-4,6.E-4,
obs_coef_mois = 6.E-4,6.E-4,
obs_rinxy = 144.,48.,
obs_rinsig = 0.1,
obs_prt_freq = 1,1,
obs_ipf_nudob = .true.,
obs_ionf = 10,10,
obs_idynin = 0,
obs_scl_neg_qv_innov = 1,
/

Nudging using MADIS information.
 
Hi,
The value of REGIME cannot be zero. In your case, it seems that regime=0, which leads to the model crash. Please track back from phys/module_fddaobs_driver.F to dyn_em/module_first_rk_step_part2.F, looking at REGIME value at the grid point i= 96 j = 505. It could be that some errors are introduced during the OBS nudging that result in unreasonable value of REGIME.
 
Top