Shoot, sorry. 

1. The first one with the ETMY PI is me (and should be benign - no actual actuation is going out). 
2.  Not me, but shouldn't matter. 
3. Third one, ETMY lock bias should be set back to 0 at next opportunity.  It got forgotten when we lost lock during the PI Q measurement work earlier (alog forthcoming).
4. These offsets had been off to make looking at the positions on the QPD easier to see (but only on the Xarm).  They were probably on in the SAFE.snap, which is why they came back as on when the computer had its unexpected reboot.  We don't use the DC positions of these QPDs, so this doesn't matter for the IFO.  Perhaps if I remember during a non-observing time tomorrow I'll get rid of the offsets on all TR QPDs.
5. Some me, some must be from the SAFE.snap.
   1. Mode 24 damp  - I had turned on the 1kHz lowpass in FM2.  Good to accept.
   2. Mode 24 tramp - Me, doesn't really matter either way.
   3. OMC-ASC_BEACON_DRIVE matrix setting to 0 - Me, to ensure we weren't driving ETMY with the deacon system.
   4. The other mode gains I would have expected to be zero (which is what their current values seem to be). Probably doesn't matter if they had been non-zero as long as the PI ESD outputs were off, but they're better off with the current value of zero.
6. The AS 36 has been changing every lock, as Jim pointed out yesterday.  I think (but want to confirm for myself) that we're setting that each lock so that the transition for MICH ASC from AS45 to AS36 is more smooth.  If that's true, then we'll unmonitor it as a guardian-controlled channel.

I was wrong on the ETMY ESD bias - Jim checked and found that there was no value in the offset, just the button was on.  So, no impact at all on DARM.