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

regarding error while running real.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
hello everyone,
i am using wrf 4.0
i am getting an error while running real.exe

Domain 1: Current date being processed: 2018-12-31_00:00:00.0000, which is loop # 1 out of 9
configflags%julyr, %julday, %gmt: 2018 365 0.0000000E+00
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 385
error opening met_em.d01.2018-12-31_00:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 385
error opening met_em.d01.2018-12-31_00:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------
wrf_abort


please respond, your suggestion is valuable for me
 
Hi,
Can you please issue this command from your WRF running directory:

ls -ls >& ls.txt

and please attach that ls.txt file, along with your namelist.input file.

Thanks,
Kelly
 
deva_wrf said:
hello everyone,
i am using wrf 4.0
i am getting an error while running real.exe

Domain 1: Current date being processed: 2018-12-31_00:00:00.0000, which is loop # 1 out of 9
configflags%julyr, %julday, %gmt: 2018 365 0.0000000E+00
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 385
error opening met_em.d01.2018-12-31_00:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 385
error opening met_em.d01.2018-12-31_00:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------
wrf_abort


please respond, your suggestion is valuable for me

Have you solve it. I have face same problem. Only the line number is 401

d01 2019-05-05_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2019-05-05_00:00:00 Timing for processing 0 s.
d01 2019-05-05_00:00:00 Timing for output 0 s.
d01 2019-05-05_00:00:00 Timing for loop # 1 = 0 s.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 401
error opening met_em.d01.2019-05-05_06:00:00.nc for input; bad date in namelist or file not in directory
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
 
Please go to your working directory (where you run real.exe), and check whether met_em.d01.2019-05-05_06:00:00.nc is available there. You may try the command:
ncdump -h met_em.d01.2019-05-05_06:00:00.nc

If you get normal output from the above command, please send me your namelist.input and the met_em file to take a look.
 
Ming Chen said:
Please go to your working directory (where you run real.exe), and check whether met_em.d01.2019-05-05_06:00:00.nc is available there. You may try the command:
ncdump -h met_em.d01.2019-05-05_06:00:00.nc

If you get normal output from the above command, please send me your namelist.input and the met_em file to take a look.

I have attached namelist file and met_Em file. But met_em file is not attached properly and it shows "invalid filename".
 

Attachments

  • namelist.input
    3.9 KB · Views: 67
Hi jayantipal,

The error message you said you had shows the following:
Code:
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 401
error opening met_em.d01.2019-05-05_06:00:00.nc for input; bad date in namelist or file not in directory

However, the namelist that you attached has dates
2000-01-24_12:00:00 to 2000-01-25_12:00:00

So it doesn't seem that this is the correct namelist file for this error. Can you try to run this again, first making sure that you are using the correct namelist, and that you have the correct met_em* files linking into your running directory? If you are still having problems, please issue the following:
Code:
ls -ls >& ls.txt
Then please attach that ls.txt file, along with the correct namelist.input file, and please attach the full output log file that shows the error message.

Thanks,
Kelly
 
this dates are for nested domain. the date in first column is for present domain as I have single domain. I have attached ls.txt file. I have data for two days 1.05.2019 and 2.05.2019. those data are 6 hourly data. Input is "NCEP FNL Operational Model Global Tropospheric Analyses, continuing from July 1999". I want to run a 5 day run. WPS doesnt show any error.

I have also attached namelist.input and namelist.wps
 

Attachments

  • ls.txt
    6.4 KB · Views: 70
  • namelist.input
    3.9 KB · Views: 72
  • namelist.wps
    1.3 KB · Views: 59
Can you also please send the new full error log? The original error you sent us was
Code:
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 401
error opening met_em.d01.2019-05-05_06:00:00.nc for input; bad date in namelist or file not in directory

but the new namelists you sent have dates:
Code:
 start_year                          = 2019, 2019, 2019,
 start_month                         = 05,   05,   05,
 start_day                           = 01,   05,   05,
 start_hour                          = 00,   00,   00,
 end_year                            = 2019, 2019, 2019,
 end_month                           = 05,   05,   05,
 end_day                             = 02,   07,   07,
 end_hour                            = 18,   00,   00,

so the dates in the original error message aren't even in your new namelist.input file. Please make sure that you are sending the correct error log for the correct namelist.

Thanks
 
Top