Hourly and daily averages are low in MADC burst driver
Jerry Annala reports:
I noticed something that took me a while to figure out, even though I think the problem seems to be very simple. The
D:POTDAYvalue is most often smaller than the value you would get by integrating the
POTMINvalue over 24 hours. It turns out that I think what is happening is that you are only adding up the previous 23 hours instead of 24. When you get time, can you look at what the algorithm is doing and see if you think you agree.
The other parameters all look spot on.
#1 Updated by Richard Neswold almost 2 years ago
- Status changed from Assigned to Feedback
Proposed fix: b3a97026
I think the problem is that I checked for the top-of-the-hour before I updated the top-of-the-minute calculation. Now the driver processes the full, 60-minutes of samples before updating the hourly and daily averages. The front-end needs to be rebooted to get the new driver.