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

data was not created while runninf ./wrf.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.

A

Anonymous

Guest
hi,

i am getting trouble while running ./wrf.exe ,
when i am running mpirun -np 2 ./wrf.exe. these 2 rsl.file was generated attached below,
i am not getting an output file.

if you get time please take a look

rsl.error.0000

taskid: 0 hostname: localhost.localdomain
module_io_quilt_old.F 2931 F
Quilting with 1 groups of 0 I/O tasks.
Ntasks in X 1 , ntasks in Y 1
*************************************
Configuring physics suite 'conus'

mp_physics: 8 8
cu_physics: 6 6
ra_lw_physics: 4 4
ra_sw_physics: 4 4
bl_pbl_physics: 2 2
sf_sfclay_physics: 2 2
sf_surface_physics: 2 2
*************************************
WRF V4.0 MODEL
*************************************
Parent domain
ids,ide,jds,jde 1 37 1 37
ims,ime,jms,jme -4 42 -4 42
ips,ipe,jps,jpe 1 37 1 37
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 63174544 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use: wrfinput_d01
Timing for processing wrfinput file (stream 0) for domain 1: 0.00659 elapsed seconds
Max map factor in domain 1 = 1.06. Scale the dt in the model accordingly.
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 33 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
Skipping over LUTYPE = USGS
LANDUSE TYPE = MODIFIED_IGBP_MODIS_NOAH FOUND 20 CATEGORIES
INPUT SOIL TEXTURE CLASSIFICATION = STAS
SOIL TEXTURE CLASSIFICATION = STAS FOUND 19 CATEGORIES
ThompMP: computing qr_acr_qg
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
wrf.exe 0000000003004D23 Unknown Unknown Unknown
libpthread-2.17.s 00007FC19FADF5D0 Unknown Unknown Unknown
wrf.exe 0000000000968862 Unknown Unknown Unknown
wrf.exe 0000000001CDB4A1 Unknown Unknown Unknown
wrf.exe 0000000002306428 Unknown Unknown Unknown
wrf.exe 00000000022F3A17 Unknown Unknown Unknown
wrf.exe 0000000001C32ABA Unknown Unknown Unknown
wrf.exe 00000000018504AB Unknown Unknown Unknown
wrf.exe 0000000001321366 Unknown Unknown Unknown
wrf.exe 0000000000409213 Unknown Unknown Unknown
wrf.exe 0000000000407FC5 Unknown Unknown Unknown
wrf.exe 0000000000407F62 Unknown Unknown Unknown
libc-2.17.so 00007FC19F4233D5 __libc_start_main Unknown Unknown
wrf.exe 0000000000407E69 Unknown Unknown Unknown



and in rsl.out.0000


taskid: 0 hostname: localhost.localdomain
Quilting with 1 groups of 0 I/O tasks.
Ntasks in X 1 , ntasks in Y 1
*************************************
Configuring physics suite 'conus'

mp_physics: 8 8
cu_physics: 6 6
ra_lw_physics: 4 4
ra_sw_physics: 4 4
bl_pbl_physics: 2 2
sf_sfclay_physics: 2 2
sf_surface_physics: 2 2
*************************************
WRF V4.0 MODEL
*************************************
Parent domain
ids,ide,jds,jde 1 37 1 37
ims,ime,jms,jme -4 42 -4 42
ips,ipe,jps,jpe 1 37 1 37
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 63174544 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use: wrfinput_d01
Timing for processing wrfinput file (stream 0) for domain 1: 0.00659 elapsed seconds
Max map factor in domain 1 = 1.06. Scale the dt in the model accordingly.
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 33 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
Skipping over LUTYPE = USGS
LANDUSE TYPE = MODIFIED_IGBP_MODIS_NOAH FOUND 20 CATEGORIES
INPUT SOIL TEXTURE CLASSIFICATION = STAS
SOIL TEXTURE CLASSIFICATION = STAS FOUND 19 CATEGORIES
ThompMP: computing qr_acr_qg
~
~
~
~
 
Hi,
Can you attach your namelist.input file, as well as your full rsl.out.0000 and rsl.error.0000 files?

Thanks,
Kelly
 
Dear kelly,
Thanks for your kind response,
i have already given the rsl.error.0000 and rsl.out.0000 file. please find the namelist.input file attached blow.

thanks.
 

Attachments

  • namelist.input
    3.7 KB · Views: 59
Thanks. It's hard to determine the exact cause of the problem with the information that is available, but it's possible that this is crashing because your domains are way too small. We recommend never having a domain smaller than 100x100. Whether or not that is causing the failure, it's something that should be corrected. For best practice information on the basic namelist settings, and for setting up a 'good' domain, see these pages:
http://www2.mmm.ucar.edu/wrf/users/namelist_best_prac_wps.html
http://www2.mmm.ucar.edu/wrf/users/namelist_best_prac_wrf.html

Once you do that, you'll need to re-run through geogrid and metgrid, real, and then wrf. If it still fails immediately, this could be a problem with your input data. You should then check your wrfinput_d0* files and perhaps your met_em* files to see if anything looks bad.
 
Dear kelly,
Thanks for your kind response,

Earlier we run the model with outer domain size (10degree X 10degree), and inner domain with (2degree X2degree), at that time we don't face any problem, so i don't think that was the problem, but i will check it again, please correct me if i were wrong in some place, which information do you need to check the problem, you can ask.

please respond

thanking you
 
Dear kelly,
thanks for your reply
i got this error message while running wrf.exe, do you have any idea please respond.
mpirun -np 1 ./wrf.exe

starting wrf task 0 of 1

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= EXIT CODE: 174
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
 
Hi,
This error means that the test failed. You will need to check inside your rsl.* files for the actual error.

As for the domain size, I was referring to the number of grid cells in each domain. Yours are:

Code: 
e_we                                = 37,    22,
e_sn                                = 37,    22,

and each of those should be at least 100x100. Regardless of whether this is causing the new error, this is something that needs to be fixed first. It's best to troubleshoot when you're using best practices, so that we can rule out any problems that may be stemming from bad practices.

Kelly
 
Dear Kelly,
Sorry to disturb you again, but I Don't understand what's the problem with domain size. i don't know much about WRF. So correct me if i were wrong.
 
Dear kelly,
please find the namelist.WPS and namelist.input fine attached below, if you find anything wrong please correct me, i am doing a test run only .

please respond
 

Attachments

  • namelist.wps
    1.3 KB · Views: 51
  • namelist.input
    3.7 KB · Views: 43
Hi,
If you're simply running a test and will not be using it for any real analysis, then it is probably okay to keep the domains so small. In any real cases, you would want the domains to be larger so that as things propagate across the domain they have time to use the physics, etc. that you specify in your namelist to develop any realistic outcome. Otherwise, because of how quickly things will move across such small domains, you are just basically using the boundary/initial conditions, which in that case, it is pointless to even run the WRF model on top of the input data from whatever model you are getting it from. I previously sent some links to help you out with a domain design. You can use those when you are ready to create some real domains for your study.

As for now, I ran a quick test with your namelists and I am able to run them without any problems. If you are still getting as segmentation fault when running wrf, then you should check a few things:
1) make sure that you have enough disk space to write out data - you may need to check with your systems administrator at your institution about this.
2) check your input data - use something like 'ncview' to look over your met_em* files and make sure nothing looks wrong.
3) If neither of those seem to be the problem, please send me the first time period of met_em* files (for both domains) so that I can test your data. You can package those into one *.tar file and attach it here.

Kelly
 
hi
thanks for your time and concern
i understand your suggestion but one last time can you help me to test with the data file attached below, otherwise i am going to change the domain configuration.

thanking you

please find the attachments
 
Hi,
Can you actually also send me the met_em* files for the next time period so that I can create a full boundary file to do a short run (past the initial time)? If you could send the next boundary time, likely:
met_em.d01.2018-12-31_06:00:00
met_em.d02.2018-12-31_06:00:00

that should help. Sorry about that. I should have asked for those to begin with.

Thanks,
Kelly
 
hi,
initial value is created but error found when running ./wrf.exe
please find the attachments
 

Attachments

  • met_em.tar.gz
    1.4 MB · Views: 38
Hi,
With your namelist.input file, your met_em.d0* files, and with version 4.0 of the code, I am not having any problems running. This seems to indicate a problem with either your environment or your compile of WRF. I would suggest the following:
1) If you didn't check yet to see whether you have enough disk space where you are running/writing files, then you should do that.
2) It may be worth trying to recompile the code so that you have a clean version. If you have made any modifications to the code, itself, try to run a version without any modifications to see if that works, and then you can narrow it down to the mods you made.
3) If neither of the above 2 suggestions help, then I would recommend discussing the problem with your systems administrator at your institution. Unfortunately because we are able to run the case here with no problems, it doesn't seem to be particular to the WRF code, itself.

If you figure out a solution, please let us know so that it may help a future WRF user.

Thanks,
Kelly
 
Dear kelly,

hi, thank you very much for your concern, its a great experiences to learn about wrf regarding this problem,
i will run this configuration in server, earlier i am running simulation in my computer.

i will update my result as soon as my simulation complete

thanking you
 
You must log in or register to reply here.
Top