Bug #20154

Hourly and daily averages are low in MADC burst driver

Added by Richard Neswold almost 2 years ago. Updated 9 months ago.

Start date:
Due date:
% Done:


Estimated time:


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:POTDAY value is most often smaller than the value you would get by integrating the POTMIN value 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.

#2 Updated by Richard Neswold almost 2 years ago

Does the calculation seems better? (I know it's hard to tell during the shutdown, but it ran for almost a month before.)

#3 Updated by Richard Neswold 9 months ago

  • Status changed from Feedback to Closed

No feedback. Closing this issue for now (the new driver has been running for a year without complaints.)

Also available in: Atom PDF