I am trying to run WRFv4.4.1 using split met_em files (io_form_metgrid = 102 in namelist.wps), but the resulting split met_em files cannot be read by real.exe, even though io_form_input is set to 102. Instead, I get the following error:
FATAL CALLED FROM FILE: <stdin> LINE: 409
error opening met_em.d01.2021-07-24_23_00_00.nc for input; bad date in namelist or file not in directory
All of my met_em files are named met_em.d01.YYYY-mm-DD_HH_MM_SS.nc.XXXX, where XXXX is the processor number. Based on the error message, it sounds like real.exe is looking for a single met_em file for each input time when it really should be looking for multiple, one for each processor. For what it's worth, both metgrid.exe and real.exe are run using 8 processors.
I created a simple example showing this behavior for a 10-km CONUS grid with RAP LBCs/ICs that is run for 1 hour. I uploaded the met_em files, namelist.wps, run_metgrid.sh (script used to run metgrid.exe), namelist.input, run_real.sh (script used to run real.exe), and the rsl.out and rsl.error files to the WRF Forum Nextcloud (file name: smurd_wrf_20221107.tar). My software stack is as follows:
szip/2.1
intel/18.0.5.274
impi/2018.4.274
hdf5/1.8.9
netcdf/4.2.1.1
pnetcdf/1.6.1
nco/4.9.3
ncl/6.5.0
Sidenote: Split met_em files are not really needed for the example I provided, but the goal is to eventually run WRF with a massive domain (several thousand by several thousand gridpoints), and in that case, I don't think having a single met_em is practical because it can be 10+ GB large.
Thanks!
Shawn
FATAL CALLED FROM FILE: <stdin> LINE: 409
error opening met_em.d01.2021-07-24_23_00_00.nc for input; bad date in namelist or file not in directory
All of my met_em files are named met_em.d01.YYYY-mm-DD_HH_MM_SS.nc.XXXX, where XXXX is the processor number. Based on the error message, it sounds like real.exe is looking for a single met_em file for each input time when it really should be looking for multiple, one for each processor. For what it's worth, both metgrid.exe and real.exe are run using 8 processors.
I created a simple example showing this behavior for a 10-km CONUS grid with RAP LBCs/ICs that is run for 1 hour. I uploaded the met_em files, namelist.wps, run_metgrid.sh (script used to run metgrid.exe), namelist.input, run_real.sh (script used to run real.exe), and the rsl.out and rsl.error files to the WRF Forum Nextcloud (file name: smurd_wrf_20221107.tar). My software stack is as follows:
szip/2.1
intel/18.0.5.274
impi/2018.4.274
hdf5/1.8.9
netcdf/4.2.1.1
pnetcdf/1.6.1
nco/4.9.3
ncl/6.5.0
Sidenote: Split met_em files are not really needed for the example I provided, but the goal is to eventually run WRF with a massive domain (several thousand by several thousand gridpoints), and in that case, I don't think having a single met_em is practical because it can be 10+ GB large.
Thanks!
Shawn