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

Real produces wrfinput but not wrfbdy

icastorm

New member
Hello,

As the title indicates, I am not getting the wrfbdy file when I run real.exe, which is obviously an issue. I am getting no errors anywhere along the process starting from geogrid as far as I can tell, besides the following when I run real on a single core:

srun: error: PMK_KVS_Barrier duplicate request from task 0

I have attached my rsl.xxx.0000 files and the input namelists, along with the script that describes the process.

More information:
WRF version: 4.4.1
Modules:
gcc/10.1.0
openmpi/4.0.4
netcdf-c/4.7.3-mpi
netcdf-fortran/4.5.2-mpi
hdf5/1.10.6-mpi

Boundary conditions are forced by GEFS forecasts
When I run real with multiple cores (mpirun), real finishes without error, but only outputs the wrfinput file.

Any help figuring out what is going wrong would be appreciated!
 

Attachments

  • namelist.input
    4.5 KB · Views: 3
  • namelist.wps
    617 bytes · Views: 1
  • rsl.error.0000
    1.6 KB · Views: 1
  • rsl.out.0000
    1.9 KB · Views: 0
  • prepInitialPrior.txt
    4.7 KB · Views: 1
Your namelist.input shows the time period as follows;

start_year = 2023, 2023, 2023,


start_month = 07, 07, 07,


start_day = 01, 01, 01,


start_hour = 00, 00, 00,


start_minute = 00, 00, 00,


start_second = 00, 00, 00,


end_year = 2023, 2023, 2023,


end_month = 07, 07, 07,


end_day = 30, 30, 30,


end_hour = 23, 23, 23,


end_minute = 00, 00, 00,


end_second = 00, 00, 00,


interval_seconds = 3600

Your RSL file indicates that REAL.EXE is done successfully over a single time as shown below:
d01 2022-04-01_12:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.4

d01 2022-04-01_12:00:00 Input data is acceptable to use: met_em.d01.2022-04-01_12:00:00.nc

metgrid input_wrf.F first_date_input = 2022-04-01_12:00:00

metgrid input_wrf.F first_date_nml = 2022-04-01_12:00:00

d01 2022-04-01_12:00:00 Timing for input 4 s.

d01 2022-04-01_12:00:00 flag_soil_layers read from met_em file is 1

Max map factor in domain 1 = 1.01. Scale the dt in the model accordingly.

Using sfcprs2 to compute psfc

d01 2022-04-01_12:00:00 No average surface temperature for use with inland lakes

Assume Noah LSM input

d01 2022-04-01_12:00:00 forcing artificial silty clay loam at 277 points, out of 12240

d01 2022-04-01_12:00:00 Timing for processing 0 s.

d01 2022-04-01_12:00:00 Timing for output 24 s.

d01 2022-04-01_12:00:00 Timing for loop # 1 = 28 s.

d01 2022-04-01_12:00:00 real_em: SUCCESS COMPLETE REAL_EM INIT

I am perplexed by this case ....
 
A bit of an update here in the hopes that someone will be able to help me solve this problem:

I have tried running real.exe in environments and on cases that have produced the wrfbdy file before, and have found that they all fail to produce it now. My hunch is that something in our supercomputing environment has changed. I will be in contact with the help desk about that while I test a few other cases.
 
One more update, which should've been posted very soon after my previous update: Issue has been fixed. Through a series of (somewhat embarrassing) blunders, I realized that I had both run time set to 0 and the same start time and end time in the namelist. In turn, real (correctly) surmised that I wouldn't need boundary conditions and only generated the input file. There was no error here but my own!
 
Top