-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minor bug fix in JREGIONAL_RUN_PYTHON_GRAPHICS for RTMA #414
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to think about the case of 15min output? Would 15, 30, 45 mins all end up as 0 hour instead of separate forecast lengths?
Good question. For the cases you mentioned, I think we need modifications inside the python graphic packages. That would be a better way to handle this situation. Looking forward to @christinaholtNOAA's inputs. |
We need this fix to get the RTMA workflow run through. I just limited the bug fix to RTMA since RTMA will not do any meaningful forecasts in the foreseeable future. @terraladwig Does this work for you? |
@guoqing-noaa Do you still need this bug fix? |
Yes, RTMA still needs this bug fix. Thanks! |
Can anyone help to review this PR? It has already sat here for 19 days. |
Thanks, @hu5970 |
When fcst_length is NOT an integer (e.g. sub-hourly), it will stop the graphic workflow. This PR adds a floor()-like function to ensure fcst_length is an integer.