Hal, That's good stuff. Sadly, I've got to convert UTC to your local time to interpret the results, so I haven't done it. Tom's MJD will be even worse.
The reason is that the loads that cause frequency droop occur during workdays. Lost cycles are made up at night, so I need to know when local day and night occur. At the present time (before July 15th), the power dispatching center for an area tries to end the day (perhaps at 7 AM) with exactly 60x60x60x24 cycles of power generated. This keeps the clocks on time, and balances the power budget for the day - no extra cycles given away and no cycles stolen from other areas. The Time Error Correction (TEC) elimination experiment (to find out who notices the loss) is motivated by the number of frequency excursion (not trip) errors that occur when dispatch requests a correction. It costs the generating plants money (nothing else drives change today) to increase power on demand - in fuel and stress on the equipment. With any luck, my next message will be about the frequency control problem. Bill Hawkins -----Original Message----- From: Hal Murray Sent: Sunday, July 03, 2011 11:15 PM I've moved the 60 Hz stuff from http://www.megapathdsl.net/~hmurray/time-nuts/ to http://www.megapathdsl.net/~hmurray/time-nuts/60Hz/ ---------- The main graph is now up to sightly over 4 days. http://www.megapathdsl.net/~hmurray/time-nuts/60Hz/60Hz.png Peak-to-peak is almost 8 seconds. The slew rate is pretty fast in a few places. 1 second in 1/2 hour at hour 64. 4 seconds in 3 hours at hour 13. 2.5 seconds in 3 hours at hour 44. 7 seconds in 7 hours at hour 91. ---------- _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.