WRF 3.9 DFI broken?

All other topics about postprocessing model data (GrADS and other software), about other numerical weather prediction software (including WRF-NMM and WRF-ARW discussion unrelated to UEMS/WRF EMS), and general meteorology talk go in this forum.
Post Reply
meteoadriatic
Posts: 1574
Joined: Wed Aug 19, 2009 10:05 am

WRF 3.9 DFI broken?

Post by meteoadriatic » Fri Apr 21, 2017 7:57 am

Hello,

Had anyone tried WRF 3.9 with DFI filter? It seems to me it is broken in a sense that it can't continue after DFI finishes (might have something with broken restart capability described in "known problems" for the release)?

Question is not EMS related.

thx

surgeon
Posts: 46
Joined: Wed Dec 08, 2010 1:34 pm
Location: Poland
Contact:

Re: WRF 3.9 DFI broken?

Post by surgeon » Sun Apr 23, 2017 10:06 am

I use DFI and it's working fine like in 3.8.1.

meteoadriatic
Posts: 1574
Joined: Wed Aug 19, 2009 10:05 am

Re: WRF 3.9 DFI broken?

Post by meteoadriatic » Sun Apr 23, 2017 10:34 am

OK, thanks, I should find a mistake then.

meteoadriatic
Posts: 1574
Joined: Wed Aug 19, 2009 10:05 am

Re: WRF 3.9 DFI broken?

Post by meteoadriatic » Tue May 02, 2017 7:46 pm

I'm getting segmentation fault right after DFI finishes and model tries to start to integrate normally from initial time:
...
Writing out initialized model state
mediation_integrate.G 1728 DATASET=HISTORY
mediation_integrate.G 1729 grid%id 1 grid%oid 1
Timing for Writing wrfout_d01_2016-06-18_00:00:00 for domain 1: 4.76986 elapsed seconds
Timing for processing lateral boundary for domain 1: 0.12908 elapsed seconds
forrtl: severe (174): SIGSEGV, segmentation fault occurred
With 3.8.1 this does not happen. Strange...

meteoadriatic
Posts: 1574
Joined: Wed Aug 19, 2009 10:05 am

Re: WRF 3.9 DFI broken?

Post by meteoadriatic » Tue May 02, 2017 8:12 pm

OK, new information. It seems I get seg fault only if I use physics_suite = 'conus'. However, it 'conus' works without DFI. Will try to narrow down the cause, probably one of physics settings from 'conus' make problem.

meteoadriatic
Posts: 1574
Joined: Wed Aug 19, 2009 10:05 am

Re: WRF 3.9 DFI broken?

Post by meteoadriatic » Tue May 02, 2017 8:25 pm

Well, it looks like it is not a particular setting within 'conus' suite, but actually physics_suite is the cause. Funny, but that my tests show.

If I set old way all physics from 'conus' and remove physics_suite from namelist.input, then everything works with DFI. If I use physics_suite and remove traditional entries defined in it, run segfaults after DFI phase. On the other hand as I wrote physics_suite = 'conus' works fine if no DFI is used. :twisted:

I guess, case closed for me.

yandy
Posts: 2
Joined: Mon Dec 03, 2018 6:14 pm

Re: WRF 3.9 DFI broken?

Post by yandy » Mon Dec 03, 2018 6:33 pm

Hello
I am running into a similar problem here.
No physical_suit was set for my case, just set physical options in the old fashion way.
Program exits with exit code 11 after trying to write: Writing out initialized model state for domain 3 of a three two-way nesting set of domains
Here is the backtrace info:

Writing out initialized model state
Writing out initialized model state
Writing out initialized model state

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x7F39BE6D16F7
#1 0x7F39BE6D1D3E
#2 0x7F39BDBD824F
#3 0x11124A1 in output_wrf_
#4 0x108880D in __module_io_domain_MOD_open_w_dataset
#5 0x114C881 in dfi_write_initialized_state_
#6 0x114C9CF in dfi_write_initialized_state_recurse_
#7 0x114C9F8 in dfi_write_initialized_state_recurse_
#8 0x114C9F8 in dfi_write_initialized_state_recurse_

Running in a cluster with mpi and 40 processors.
Also, after turning of dfi_write_filtered_input and running again I got the same when trying to write wrfout again for domain 3 for analysis time. Here the backtrace info:

Timing for Writing wrfout_d01_2017-02-26_00:00:00 for domain 1: 2.80144 elapsed seconds
Timing for processing lateral boundary for domain 1: 0.39290 elapsed seconds
Timing for Writing wrfout_d02_2017-02-26_00:00:00 for domain 2: 2.81932 elapsed seconds

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x7F7555FA06F7
#1 0x7F7555FA0D3E
#2 0x7F75554A724F
#3 0x11124A1 in output_wrf_
#4 0x108880D in __module_io_domain_MOD_open_w_dataset
#5 0x11792D9 in open_hist_w_
#6 0x117B0BC in med_hist_out_.part.1 at mediation_integrate.f90:?
#7 0x117BA0F in med_before_solve_io_
#8 0x4721E1 in __module_integrate_MOD_integrate
#9 0x47282B in __module_integrate_MOD_integrate
#10 0x47282B in __module_integrate_MOD_integrate
#11 0x407A13 in __module_wrf_top_MOD_wrf_run

Below is main namelist.input info:

&time_control
input_from_file = .true.,.true.,.true.,
fine_input_stream = 0, 2, 2,

&domains
time_step = 15,
time_step_dfi = 15,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_dom = 3,
i_parent_start = 1, 80, 80
j_parent_start = 1, 80, 80
e_we = 240, 241, 241
e_sn = 240, 241, 241
vert_refine_method = 0,0,0
e_vert = 38, 38, 38
parent_time_step_ratio = 1, 3, 4,
feedback = 1,
smooth_option = 0

&physics
mp_physics = 8, 8, 8
cu_physics = 0, 0, 0
ra_lw_physics = 4, 4, 4,
ra_sw_physics = 4, 4, 4,
sf_sfclay_physics = 1, 1, 1,
sf_surface_physics = 1, 1, 1,
bl_pbl_physics = 1, 1, 1,
sf_urban_physics = 1, 1, 1,

&dfi_control
dfi_opt = 3
dfi_nfilter = 7
dfi_write_filtered_input = .false.
dfi_write_dfi_history = .false.

NOTE: Interesting to add though. This configuration runs fine when DFI is TURNED OFF *************


Any ideas...??????? Could that be a ram memory issue????
thanks a lot in advance

meteoadriatic
Posts: 1574
Joined: Wed Aug 19, 2009 10:05 am

Re: WRF 3.9 DFI broken?

Post by meteoadriatic » Tue Dec 04, 2018 5:07 pm

Just quick idea, did you unlimited stack size?

http://www2.mmm.ucar.edu/wrf/users/FAQ_ ... ntime.html

(Question 8)

yandy
Posts: 2
Joined: Mon Dec 03, 2018 6:14 pm

Re: WRF 3.9 DFI broken?

Post by yandy » Wed Dec 05, 2018 5:43 pm

Hi, thanks for your replay but
stack size was already unlimited. The problem was solved. Additional info can be found in this post:
http://forum.mmm.ucar.edu/phpBB3/viewto ... 1464#p1464

Thanks

Post Reply