[Wrf-users] problems when set eta_levels
朱丽
superzhuli1994 at 163.com
Tue Mar 27 06:53:10 MDT 2018
Dear friends,
I am having problem to run WRFV3.9.1 . My domain includes Tibetan Plateau, a steep terrain shown below. My e_vert is 35, but when i don't give eta_levels number it can stable integral ,and SUCCESS COMPLETE WRF appear! But when i set eta_levels number like this ( eta_levels = 1.00, 0.9975, 0.995, 0.9925, 0.99, 0.985, 0.98, 0.975, 0.97, 0.965, 0.96, 0.95, 0.94, 0.93, 0.92, 0.91, 0.90, 0.89, 0.88, 0.87, 0.86, 0.85, 0.84, 0.82, 0.80, 0.75, 0.70, 0.65, 0.60, 0.50, 0.40, 0.30, 0.20, 0.10, 0.00,),the process always interrupt after one or two seconds it starts compute. I have tested time_step=81/54/27/18. All tries are failed.
I am looking forward to your suggestion. Thank you!
This is the error information :
[proxy:0:0 at c21n14] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:902): assert (!closed) failed
[proxy:0:0 at c21n14] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[proxy:0:0 at c21n14] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event
[proxy:0:5 at c20n06] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:902): assert (!closed) failed
[proxy:0:5 at c20n06] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[proxy:0:5 at c20n06] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event
[proxy:0:6 at c20n09] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:902): assert (!closed) failed
[proxy:0:6 at c20n09] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[proxy:0:6 at c20n09] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event
[proxy:0:7 at c05n04] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:902): assert (!closed) failed
[proxy:0:7 at c05n04] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[proxy:0:7 at c05n04] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event
[proxy:0:2 at c20n02] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:902): assert (!closed) failed
[proxy:0:2 at c20n02] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[proxy:0:2 at c20n02] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event
[proxy:0:3 at c20n03] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:902): assert (!closed) failed
[proxy:0:3 at c20n03] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[proxy:0:3 at c20n03] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event
[proxy:0:4 at c20n05] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:902): assert (!closed) failed
[proxy:0:4 at c20n05] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[proxy:0:4 at c20n05] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event
[mpiexec at c21n14] HYDT_bscu_wait_for_completion (tools/bootstrap/utils/bscu_wait.c:76): one of the processes terminated badly; aborting
[mpiexec at c21n14] HYDT_bsci_wait_for_completion (tools/bootstrap/src/bsci_wait.c:23): launcher returned error waiting for completion
[mpiexec at c21n14] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:218): launcher returned error waiting for completion
[mpiexec at c21n14] main (ui/mpich/mpiexec.c:331): process manager error waiting for completion
rsl.error.0000 file
Timing for main: time 2016-08-15_00:03:48 on domain 4: 0.22201 elapsed seconds
Timing for main: time 2016-08-15_00:03:48 on domain 3: 1.03475 elapsed seconds
Timing for main: time 2016-08-15_00:03:50 on domain 4: 0.22653 elapsed seconds
Timing for main: time 2016-08-15_00:03:52 on domain 4: 0.22165 elapsed seconds
Timing for main: time 2016-08-15_00:03:54 on domain 4: 0.23293 elapsed seconds
Timing for main: time 2016-08-15_00:03:54 on domain 3: 1.07861 elapsed seconds
Timing for main: time 2016-08-15_00:03:54 on domain 2: 3.22250 elapsed seconds
Timing for main: time 2016-08-15_00:03:56 on domain 4: 0.23117 elapsed seconds
Timing for main: time 2016-08-15_00:03:58 on domain 4: 0.22715 elapsed seconds
Timing for main: time 2016-08-15_00:04:00 on domain 4: 0.22784 elapsed seconds
Timing for main: time 2016-08-15_00:04:00 on domain 3: 1.08610 elapsed seconds
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
wrf.exe 0000000001C198ED Unknown Unknown Unknown
wrf.exe 0000000001BC5219 Unknown Unknown Unknown
wrf.exe 0000000001BBF616 Unknown Unknown Unknown
wrf.exe 0000000001BB5559 Unknown Unknown Unknown
wrf.exe 000000000176723D Unknown Unknown Unknown
wrf.exe 000000000184F1FA Unknown Unknown Unknown
wrf.exe 0000000001212274 Unknown Unknown Unknown
wrf.exe 00000000010C5296 Unknown Unknown Unknown
wrf.exe 00000000004D041C Unknown Unknown Unknown
wrf.exe 00000000004D0A3D Unknown Unknown Unknown
wrf.exe 00000000004D0A3D Unknown Unknown Unknown
wrf.exe 00000000004D0A3D Unknown Unknown Unknown
wrf.exe 000000000040C8F3 Unknown Unknown Unknown
wrf.exe 000000000040C8A7 Unknown Unknown Unknown
wrf.exe 000000000040C83C Unknown Unknown Unknown
libc.so.6 00000030AE61ECDD Unknown Unknown Unknown
wrf.exe 000000000040C739 Unknown Unknown Unknown
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ucar.edu/pipermail/wrf-users/attachments/20180327/b0bb6994/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ??1.png
Type: image/png
Size: 269498 bytes
Desc: not available
URL: <http://mailman.ucar.edu/pipermail/wrf-users/attachments/20180327/b0bb6994/attachment-0001.png>
More information about the Wrf-users
mailing list