You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was found that both model and post file names do not reflect the correct output time when the non-integer output time is used. The issue on model history files was fixed. Now the history files have filename format:
atmfHHH-MM-SS
sfcfHHH-MM-SS
for non integer forecast time. Post file name may need to have similar format when full time stamp is needed.
The text was updated successfully, but these errors were encountered:
@junwang-noaa I have been testing UPP for your request. I propose the inline post output file name conversion would be
{datasetname}F{forecast hour}-{forecast min}-{forecast sec}, like NATLEVF006-00-00. Please let me know your comments. Thanks!
It was found that both model and post file names do not reflect the correct output time when the non-integer output time is used. The issue on model history files was fixed. Now the history files have filename format:
atmfHHH-MM-SS
sfcfHHH-MM-SS
for non integer forecast time. Post file name may need to have similar format when full time stamp is needed.
The text was updated successfully, but these errors were encountered: