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

ndown.exe

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.

tugiyo

New member
Hi,
I did ndown.exe based on the wrf 4.2 user's guide
and got this error:

--- NOTE: num_soil_layers has been set to 4
NDOWN_EM V3.9.1.1 PREPROCESSOR
*************************************
Parent domain
ids,ide,jds,jde 1 127 1 115
ims,ime,jms,jme -4 132 -4 120
ips,ipe,jps,jpe 1 127 1 115
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 413457348 bytes allocated
wrfout_d01_2021-11-13_12:00:00
=========
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 413457348 bytes allocated

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

Backtrace for this error:
#0 0x7fdab00f0d3a
#1 0x7fdab00efed5
#2 0x7fdaafd7620f
#3 0x7fdaafebe6e2
#4 0x7fdab293693a
#5 0x7fdab0bc8328
#6 0x7fdab085ff51
#7 0x7fdab0854002
#8 0x7fdaafd570b2
#9 0x7fdab085403d
#10 0xffffffffffffffff

could anyone help me coping with this error?
 

Attachments

  • namelist.input
    3.6 KB · Views: 28
  • rsl.error.txt
    1.8 KB · Views: 22
  • rsl.out.txt
    1.5 KB · Views: 21
Set debug = 100
more information come out:
....
Entering ext_gr1_ioinit
wrfout_d01_2021-11-13_12:00:00
ndown_em main: calling open_r_dataset for wrfout_d01_2021-11-13_12:00:00
module_io.F: in wrf_open_for_read
-------->>> Processing data: loop= 1 date/time = 2021-11-13_12:00:00
loopmax = 2 ending date = 2021-11-13_15:00:00
module_io.F: in wrf_get_next_time
file date/time = 2021-11-13_12:00:00 desired date = 2021-11-13_12:00:00 status = 0
wrf: calling input_history
module_io.F: in wrf_get_previous_time

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

Backtrace for this error:
#0 0x7fbc65330d3a
#1 0x7fbc6532fed5
#2 0x7fbc64fb620f
#3 0x7fbc650fe6e2
#4 0x7fbc67b7593a
#5 0x7fbc65e07328
#6 0x7fbc65a9ef51
#7 0x7fbc65a93002
#8 0x7fbc64f970b2
#9 0x7fbc65a9303d
#10 0xffffffffffffffff
 
ncdump -v Times wrfout_d01_2021-11-13_12:00:00
...
data:

Times =
"2021-11-13_12:00:00",
"2021-11-13_13:00:00",
"2021-11-13_14:00:00",
"2021-11-13_15:00:00" ;

only 4
 
CALL wrf_debug( 500, 'module_io.F: in wrf_get_previous_time' )

Status = 0
CALL get_handle ( Hndl, io_form , for_out, DataHandle )
IF ( Hndl .GT. -1 ) THEN
IF ( multi_files( io_form ) .OR. .NOT. (for_out .AND. use_output_servers_for(io_form)) ) THEN
SELECT CASE ( use_package(io_form) )
CASE ( IO_NETCDF )
IF ( multi_files(io_form) .OR. wrf_dm_on_monitor() ) CALL ext_ncd_get_previous_time( Hndl, DateStr, Status )
IF ( .NOT. multi_files(io_form) ) THEN
CALL wrf_dm_bcast_bytes( Status, 4 )
len_of_str = LEN(DateStr)
CALL wrf_dm_bcast_string ( DateStr , len_of_str )
ENDIF
CASE ( IO_GRIB1 )
IF ( multi_files(io_form) .OR. wrf_dm_on_monitor() ) CALL ext_gr1_get_previous_time( Hndl, DateStr, Status )
IF ( .NOT. multi_files(io_form) ) THEN
CALL wrf_dm_bcast_bytes( Status, 4 )
len_of_str = LEN(DateStr)
CALL wrf_dm_bcast_string ( DateStr , len_of_str )
ENDIF
CASE DEFAULT
Status = 0
END SELECT
ELSE IF ( io_form .GT. 0 .AND. for_out .AND. use_output_servers_for(io_form) ) THEN
CALL wrf_quilt_get_previous_time( Hndl, DateStr, Status )
ELSE
Status = 0
ENDIF
ELSE
Status = WRF_ERR_FATAL_BAD_FILE_STATUS
ENDIF
RETURN
END SUBROUTINE wrf_get_previous_time
 

Attachments

  • code.txt
    1.4 KB · Views: 28
Hi,
Segmentation faults can occur for many different reasons and can sometimes be difficult to track down. These are some things I can recommend right now.

1) ndown.exe should be run for both domains. You have max_dom = 1, which may or may not cause an error like this. Set that to =2 to see if you still get the error.
2) Do NOT turn on debug_level. Please set that back to =0. We have found that this option is not usually useful and adds a lot of junk to the files, making them difficult to read. We have removed the option from the default namelist in V4.0
3) Check to make sure you have available disk space on your system.
4) If none of the above are helpful, please try to run this with the latest model version (V4.3.3). There are often bugs that have been ironed out in older version.

For future reference, you may also find this FAQ regarding seg-faults useful.
 
Top