J. Kissel

While opening the PCALX overview screen in hopes of moving around the roaming high-frequency PCALX calibration line, I found the OFS railed. A trend shows that it had been railed since 2016-11-01 at 19:04 UTC, just after maintenance day. Regrettably, due to our problems getting the IFO back up after last Tuesday’s maintenance (see LHO aLOG 31119), that means we did not getting any good data after changing the roaming line to 1001.3 Hz on Oct 31 2016 15:44:29 UTC (see LHO aLOG 31024). 

I've "power-cycled" the OFS loop, by turning OFF then ON the H1:CAL-PCALX_OPTICALFOLLOWERSERVOENABLE switch, and that restored the servo's nominal behavior.

We should stick a DIAG_MAIN monitor of the OFS PDs for both PCALs to monitor for OFS servo malfunctions like this.
Channel to watch: H1:CAL-PCALX_OFS_PD_OUTPUT (the channel comes pre-calibrated into [V], with a range of +/- 10 [V])
Test: If a ~120 sec average of the channel is more than +/- 8 [V], then throw an error. (The mean should typically by around 5 [V])

While trending and thinking about this aLOG, I'd briefly changed the line frequency to 4001.3 Hz, but after realizing we had no good 1001.3 Hz data, I've changed it back to 1001.3 Hz. We'll stay like this for a hours and then resume the sweep at the highest frequency points.

As such, I erase the last 1001.3 Hz start time with the new start time from today:
Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00
4301.3       40k                      10:00       
4501.3       40k                      10:00
4801.3       40k                      10:00  
5001.3       40k                      10:00