Error in SRW Post-processing, when ${fhr} is for example 101

Hello, 

 

I am running a SRW case (v. 2.1.0). However, after the simulation finishes (a month of forecast), I have 744 output files, and when I run ./run_post.sh, after hour 099, post fails with the following error:

 

FATAL ERROR:
ERROR:
  From script:  "exregional_run_post.sh"
  Full path to script:  "/home/wrf/fv3_latest/ufs_intel/ufs-srweather-app/scripts/exregional_run_post.sh"
The ${fhr} variable contains a 3-digit integer whose first digit is not
0.  In this case, it is not clear how to set the variable post_fhr used
in constructing the grib2 file names generated by UPP:
  fhr = "657"
Exiting with nonzero status.
End exregional_run_post.sh at Fri 20 Jan 2023 04:01:45 PM UTC with error code 1 (time elapsed: 00:00:02)
FATAL ERROR:
ERROR:
  From script:  "JREGIONAL_RUN_POST"
  Full path to script:  "/home/wrf/fv3_latest/ufs_intel/ufs-srweather-app/jobs/JREGIONAL_RUN_POST"
Call to ex-script corresponding to J-job "JREGIONAL_RUN_POST" failed.
Exiting with nonzero status.
End JREGIONAL_RUN_POST at Fri 20 Jan 2023 04:01:45 PM UTC with error code 1 (time elapsed: 00:00:03)
 

 

 Is there a way I can fix this, since not all simulations are less than 4 days in lenght?

 

Thank you!

Hello!

Thanks for letting us know about the error, I'll let the team know about the issue, but if you could please post any further questions over on our GitHub Discussion forum as we've moved our support focus there, that would be awesome.  I've already copied this discussion topic over to that forum for you with a link directly to it below, sorry for any confusion!  You can let me know here or via email at shawn.cebula@noaa.gov if you have any issues accessing or making an account with GitHub.  

Link to discussion on GitHub: https://github.com/ufs-community/ufs-srweather-app/discussions/553

Here's a link to the SRW App discussions since this is regarding the SRW: https://github.com/ufs-community/ufs-srweather-app/discussions

Shawn Cebula, EPIC End User Support

Thank you for your support, I managed to figure it out, and also provided a solution on the github post.

Thank you again.