Error in Test-data run in WRF-CMAQ 4.1.1 - 5.3.1

Hi dudes,
I compiled WRF-CMAQ (4.11,5.3.1) using the following link and wrf.exe created well.

Now I want to run this model for test. When I ran ./run_twoway_sf_Bench_2016_12SE1.csh >& out.txt, I received some error in running model. The rsl.error.000 is attached.
Anyone can help me to run this test-data?

Thanks

CC: https://forum.cmascenter.org/u/lizadams

rsl.error.000:

taskid: 0 hostname: stiphen-virtual-machine
 module_io_quilt_old.F        2931 F
Quilting with   1 groups of   0 I/O tasks.
 Ntasks in X            1 , ntasks in Y            1
WRF V4.1.1 MODEL
 *************************************
 Parent domain
 ids,ide,jds,jde            1         113           1          93
 ims,ime,jms,jme           -4         118          -4          98
 ips,ipe,jps,jpe            1         113           1          93
 *************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
   alloc_space_field: domain            1 ,             433788632  bytes allocated
 RESTART run: opening wrfrst_d01_2016-07-02_00:00:00 for reading
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     242
program wrf: error opening   wrfrst_d01_2016-07-02_00:00:00 for reading
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=1
:
system msg for write_line failure : Bad file descriptor

I don’t recognize the file wrfrst_d01
That must be a restart file. You must be running for longer than 1 day. I will try to reproduce this error and get back to you.

Liz

1 Like

Thanks for reply Liz,
I’m waiting for your coming and solution.
But what the difference between sf and nf?
Also in the input data file we have a directory in the name of “land”. How could I produce this data to input in WRF-CMAQ? Also emis directory produce with the following link?

Look at here Liz,
I received another error when run ./twoway_model_411_532_sf_run_script.csh that you sent.
My rsl.error.000 is as follow:

taskid: 0 hostname: stiphen-virtual-machine
 module_io_quilt_old.F        2931 F
Quilting with   1 groups of   0 I/O tasks.
 Ntasks in X            1 , ntasks in Y            1
WRF V4.1.1 MODEL
 *************************************
 Parent domain
 ids,ide,jds,jde            1         113           1          93
 ims,ime,jms,jme           -4         118          -4          98
 ips,ipe,jps,jpe            1         113           1          93
 *************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
   alloc_space_field: domain            1 ,             433788632  bytes allocated
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:      70
 program wrf: error opening wrfinput_d01 for reading ierr=       -1021
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=1
:
system msg for write_line failure : Bad file descriptor

I think wrfinput_d01 is not correct.

Hi Stiphen,

I was able to successfully run a two day benchmark for the nf case.

Can you confirm that you successfully ran the first day of the benchmark case to completion?
In my case, there are rsl.error* and rsl.out* files in two subdirectories of the output
2016183
The output directory name is specified by

output_direct_name =

If you use the following command

tail rsl.out.0000

You should see the following at tthe bottom.

     |>---   PROGRAM COMPLETED SUCCESSFULLY   ---<|
     ==============================================
     Date and time 0:00:00   July 2, 2016   (2016184:000000)
Timing for main: time 2016-07-02_00:00:00 on domain   1:    4.62124 elapsed seconds
 W A R N I N G : Problem opening output.var.txt
Timing for Writing wrfout_d01_2016-07-02_00:00:00 for domain        1:    0.39265 elapsed seconds
 W A R N I N G : Problem opening output.var.txt
 W A R N I N G : Problem opening output.var.txt
Timing for Writing restart for domain        1:    2.61669 elapsed seconds
d01 2016-07-02_00:00:00 wrf: SUCCESS COMPLETE WRF

I ran again ./twoway_model_411_532_nf_run_script.csh that you sent and receive these error. It should be noting that I compile two way with WRF4.1.1 and 5.3.1.
I attached two rsl* files.
I think wrfinput_d01 is not correct.

rsl.out.0000.txt (780 Bytes) rsl.error.0000.txt (994 Bytes)

You will need to edit the script that I provided you to specify paths that are on your machine.
Specifically the ROOT_PATH and INPDIR

Absolutely my edited csh file is as follow:
twoway_model_411_532_nf_run_script.csh.txt (44.2 KB)
I think there is problem with wrfinput_d01.

Do you have any suggestion?

list of files in output_12km_nf_rrtmg_20_5_1_v411532 is as follow:

2016183 namelist.output SOILPARM.TBL wrffdda_d01
CCTM_v411532_20160701.cfg ozone.formatted tr49t67 wrfinput_d01
ETAMPNEW_DATA ozone_lat.formatted tr49t85 wrflowinp_d01
GENPARM.TBL ozone_plev.formatted tr67t85 wrfsfdda_d01
landFilenames RRTM_DATA VEGPARM.TBL
LANDUSE.TBL RRTMG_LW_DATA wrfbdy_d01
namelist.input RRTMG_SW_DATA wrf.exe

Please find the directory where the input files are located on your machine.
The script should be linking to that input directory. Verify that this link is correctly pointing to the files that you obtained from the google drive.

Hi, I have same problem. Did you fix that? How? Thank you. There is my rls.error.0000

taskid: 0 hostname: node02
module_io_quilt_old.F 2931 F
Quilting with 1 groups of 0 I/O tasks.
Ntasks in X 4 , ntasks in Y 4
WRF V4.1.1 MODEL


Parent domain
ids,ide,jds,jde 1 113 1 93
ims,ime,jms,jme -4 35 -4 30
ips,ipe,jps,jpe 1 28 1 23


DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 51488372 bytes allocated
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: LINE: 70
program wrf: error opening wrfinput_d01 for reading ierr= -1021

application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

Were you able to resolve this issue of not finding the wrfinput_d01 file? If not, please start a new issue, and follow these best practices. PLEASE READ before posting