Just to clarify, the linked post above dealt with an issue where the user noticed the wind chill value displayed on his Vantage2 console did not match the wind chill value displayed by WeeWX. The reason was the console displayed the value calculated by the console, but WeeWX displayed the wind chill value calculated by WeeWX (because LOOP1 packets were used by WeeWX the console windchill value was never seen by WeeWX so WeeWX calculated windchill - changing to LOOP2 packets sent the console calculated wind chill to WeeWX and WeeWX used this wind chill value rather than calculating wind chill). Different and unrelated issue to the problem outlined in this thread.
I agree with John's post; the issue is likely due to the loop_hilo setting and the source used for plots and reports. Native WeeWX plots are generated from archive table data. Archive records contain data for each observation that is representative of the archive period concerned, for temperatures this is typically the average value across the archive period. On the other hand, aggregates used in reports are based on the daily summaries which, by default, do record max/min values for each day based on loop packet max/mins. Consequently, it is not unusual (in fact I would say it happens frequently) for a day plot to not accurately show the day max/min. This is usually not an issue given the low resolution of the WeeWX plots (ie you just can't see it), however, I could see situations where there is a noticeable difference (as in this case in this thread). In fact, when it comes to derived obs such as wind chill that are dependent on a rapidly changing observation such as wind speed, it is quite possible there would be a noticeable difference between the day min value shown on a plot and the day min value shown in a report. You could likely get rid of the discrepancy by changing loop_hilo to False, it's a personal preference, but you have to accept then your system will no longer record the max/min values seen in loop packets, rather it will record the max/min archive period average values. My preference is to have loop_hilo = True to record the loop highs and lows so my reporting is accurate and accept the occasional plot discrepancy. Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dee095f2-335d-4d3c-acb8-eb38eb7987e0n%40googlegroups.com.
