J. Kissel for the entire staff

One of the suspicions of one of the things going wrong (we suspect 3 things), is that the coil drivers are glitching. 
The suspicion arises because one of Corey's consistent places of lock loss last night was the transition to LOWNOISE_COIL_DRIVERS. 
As such, I've take a time when the FSS was freaking out for hundreds of seconds (a sadly common bunch of lemons that inhibits iteration on problems higher in the acquisition sequence a few times a day) -- so we know there is no ISC drive to the suspensions -- and searched for glitches in the analog voltage / current monitors for all the QUADs.

I find no evidence for QUAD coil or esd driver glitching for 300 seconds surrounding 2019-08-15 17:38 UTC.

Attached are NDSCOPE trends of the UIM (row 0), PUM (row 1), and ESD (row 2) driver monitors, against (row 3) 
    - (col 0) the transmitted power in ALS X (whatever is glitching is showing up quite clearly in all X arm sensors and in ALS DIFF sensors, which kills ALS while we're going through DRMI acquisition -- this we think is problem 1 going wrong), 
    - (col 1) the L2 coil driver state (always going to the acquisition state 2 in these plots)
    - (col 2) the PSL FSS FAST (PZT) MON indicating that the FSS has railed (railed is +13 V, OK is ~0 V)
    - (col 3) the ISC LOCK guardian lock state (to show that we are DOWN)