I’m trying to evaluate my daily WRF precipitation using the run_prism_comp.csh script. I ran a 5.5-day chunk of WRF with 12 hours of spinup and output into 12-hour files. Based on run_prism_comp.csh, it seems like the script expects a wrfout file beginning at 00z instead of 12z, and that the output files should be in hourly increments?
I keep getting the following error when I execute run_prism_comp.csh:
Reading PRISM monthly precip: /uufs/chpc.utah.edu/common/home/daq-group2/AMET_v14/obs/MET/prism_daily/2017/PRISM_ppt_stable_4kmD2_20170704_asc.asc
Reading WRF output: /uufs/chpc.utah.edu/common/home/daq-group2/AMET_v14/model_data/MET/June062021_run5_D02_wrf/wrfout_d02_2017-07-04_12:00:00
Reading WRF output: /uufs/chpc.utah.edu/common/home/daq-group2/AMET_v14/model_data/MET/June062021_run5_D02_wrf/wrfout_d02_2017-07-10_00:00:00
Error in Rsx_nc4_get_vara_double: NetCDF: Index exceeds dimension bound
Var: RAINC Ndims: 3 Start: 23,0,0 Count: 1,291,291
Error in ncvar_get_inner(ncid2use, varid2use, nc$var[[li]]$missval, addOffset, :
C function R_nc4_get_vara_double returned error
Calls: wrf_precip → ncvar_get → ncvar_get_inner
I’ve tried running the script for WRF simulations that have hourly output files, and for a MODEL_START wrf file at 00z, but I get the same error for RAINC. I added emphasis to the “reading PRISM monthly precip” because I’ve selected daily analysis (the loaded file prefix reflects this). I’ve also tried running a whole month to see what happens and I get the same RAINC errors. Has anyone had any luck with this?
Thanks for your time!