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
if(ifi_apcp(i,j)>9e9.or. ifi_apcp(i,j)<-9e9.or. ifi_apcp(i,j)==0) then
ifi_apcp(i,j) = avgprec_cont(i,j)*to_hourly
It causes the post to send junk data from avgprec_cont in situations where precipitation in ifi_apcp is identically zero. With my HRRR tests, junk data gets through sometimes (eg 1.72E+16) . This leads to the UPP IFI producing different precipitation types in its derived fields.
The correct code is:
if(ifi_apcp(i,j) == spval) then
ifi_apcp(i,j) = avgprec_cont(i,j)*to_hourly
Without this bug fix:
Points in the HRRR IFI 1hr apcp field have invalid data in some locations.
UPP sends those values to libIFI, which it then uses as if the data were valid.
The standalone IFI uses -9999 (missing value) in those locations. This results in a mismatch between standalone IFI and IFI in UPP.
The first field that changes is wx_type.
With this bug fix:
Points in HRRR IFI 1hr apcp field appear to be valid.
Standalone IFI and UPP IFI get identical results.
The text was updated successfully, but these errors were encountered:
The bug and its fix are confined to IFI.F, so it'll only affect the IFI fields, and only if libIFI is enabled. (Without libIFI, the fields are all missing values regardless.) My fix in #1127 also updates a comment in another file to match this bug fix, but it is only a comment, so it'll have no effect on results.
This code in IFI.F is incorrect:
It causes the post to send junk data from avgprec_cont in situations where precipitation in ifi_apcp is identically zero. With my HRRR tests, junk data gets through sometimes (eg 1.72E+16) . This leads to the UPP IFI producing different precipitation types in its derived fields.
The correct code is:
Without this bug fix:
With this bug fix:
The text was updated successfully, but these errors were encountered: