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

Severe error when runing metgrid.exe

msotocalvo

New member
I'm having a severe error with wrf 4.4.1 when runing metgrid.exe, it starts processing the domains and suddenly stops. I thougth could be related with my namelist.wps but after this error I cannot execute anymore also the geogrid.exe.

Processing domain 2 of 5
forrtl: severe (64): input conversion error, unit -5, file Internal Formatted Read
Image PC Routine Line Source
metgrid.exe 000000000056DCDB for__io_return Unknown Unknown
metgrid.exe 0000000000593D5B for_read_int_fmt_ Unknown Unknown
metgrid.exe 00000000005926E6 for_read_int_fmt Unknown Unknown
metgrid.exe 0000000000432ADD Unknown Unknown Unknown
metgrid.exe 0000000000452BCB Unknown Unknown Unknown
metgrid.exe 0000000000415F69 Unknown Unknown Unknown
metgrid.exe 000000000040EA62 Unknown Unknown Unknown
libc-2.17.so 00007F19E3A07555 __libc_start_main Unknown Unknown
metgrid.exe 000000000040E969 Unknown Unknown Unknown
 

Attachments

  • namelist.wps
    1,003 bytes · Views: 3
I'm having a severe error with wrf 4.4.1 when runing metgrid.exe, it starts processing the domains and suddenly stops. I thougth could be related with my namelist.wps but after this error I cannot execute anymore also the geogrid.exe.

Processing domain 2 of 5
forrtl: severe (64): input conversion error, unit -5, file Internal Formatted Read
Image PC Routine Line Source
metgrid.exe 000000000056DCDB for__io_return Unknown Unknown
metgrid.exe 0000000000593D5B for_read_int_fmt_ Unknown Unknown
metgrid.exe 00000000005926E6 for_read_int_fmt Unknown Unknown
metgrid.exe 0000000000432ADD Unknown Unknown Unknown
metgrid.exe 0000000000452BCB Unknown Unknown Unknown
metgrid.exe 0000000000415F69 Unknown Unknown Unknown
metgrid.exe 000000000040EA62 Unknown Unknown Unknown
libc-2.17.so 00007F19E3A07555 __libc_start_main Unknown Unknown
metgrid.exe 000000000040E969 Unknown Unknown Unknown
parent_grid_ratio = 1, 3, 10, 10, 10,
I see a possible issue with a grid ratio of 10. Usually WPS and WRF like 3:1 or 5:1 according to this post

If you have any of the log files from the ungrib, geogrid, and or metgrid I have some time to look at them @msotocalvo
 
I see a possible issue with a grid ratio of 10. Usually WPS and WRF like 3:1 or 5:1 according to this post

If you have any of the log files from the ungrib, geogrid, and or metgrid I have some time to look at them @msotocalvo
Thank you for your response @Whatheway.
I also assumed that could be the reason, but now I can't run geogrid to modify the ratios because I get the same error. I attach the metgrid and ungrib logs.
 

Attachments

  • ungrib.log
    681 KB · Views: 1
  • metgrid.log
    622.8 KB · Views: 1
Thank you for your response @Whatheway.
I also assumed that could be the reason, but now I can't run geogrid to modify the ratios because I get the same error. I attach the metgrid and ungrib logs.
Have you tried deleting the files that were created, adjust the namelists and try again?

Also you'll have to change the whole nested domains bc if you change the grid ratios the values for these will need to change. Because they are based on the 10:1
#&geogrid
parent_id = 1, 1, 2, 2, 2,
parent_grid_ratio = 1, 3, 10, 10, 10,
i_parent_start = 1, 13, 3, 39, 80,
j_parent_start = 1, 22, 56, 56, 40,
e_we = 90, 121, 401, 401, 401,
e_sn = 90, 121, 401, 401, 401,
 
Please change the options below:

start_date = '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00',
end_date = '2019-01-07_00:00:00', '2019-01-7_00:00:00', '2019-01-07_00:00:00', '2019-01-07_00:00:00', '2019-01-07_00:00:00'

to

start_date = '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00',
end_date = '2019-01-07_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00'

Also, you may need to run with multiple processors, since this is a big case with multiple domains and large grid numbers.
 
Last edited:
Please change the options below:

start_date = '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00',
end_date = '2019-01-07_00:00:00', '2019-01-7_00:00:00', '2019-01-07_00:00:00', '2019-01-07_00:00:00', '2019-01-07_00:00:00'

to

start_date = '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00',
end_date = '2019-01-07_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00', '2019-01-01_00:00:00'

Also, you may need to run with multiple processors, since this is a big case with domains and large grid numbers.
Thank you so much for your response! Regarding the processors capacity I have 96 cpu for running this case, think should be enough.

best regards
 
Top