We had a long maintenance day today, 46295.  Here are some steps that we took to get through initial alignment and the first few steps of locking.  We finished the basic maintenance  recovery around 8 pm, but we have been having difficulty locking, probably because of the ground motion since.  

• We had some difficulty locking the IMC because the sensor correction wasn't the same between HAM2 and HAM3 when we first started trying to lock. Jeff K fixed this. 
• As Cheryl wrote, the PSL temperature is a little high and slowly coming back to normal, 46298.  We manually adjusted the temperature of the ALSX laser to relock the PLL. 
• Some of our alingments were quite different than before maintence started.  We have a variety of scripts that are meant to restore alignments.  We could package one nicely and put a link on a screen so that we avoid spending time manually trending and restoring sliders. 
• We had some difficulty locking ALS Y, which has been an issue lately.  I reverted some settings which were changed last week, in particular the threshold for calling it locked was set to 80% of the nominal power, which is too tight a constraint when the alignment isn't great and the ground motion is high.  I reduced the threshold back to 0.6, set the locked gain back to 3dB (had been increased to 7), and increased the acquire gain back to -4dB (was changed last week to -10dB).  I also got rid of the guardian states LOCKED_NO_SLOW_NO_WFS, which were just pointing to INITAL_ALIGNMENT, which is misleading. 
• PR3 yaw slider was different by 3 urad from where it was before maintence day, so we restored it, and that brought the alignment back to the way it was.  
• Found a bug in the sus config where it would always have a notifcation that it didn't align a suspension because of a notification (even when there was no notification).  We got rid of this, it no longer checks for notifications and will always make it's request. 
• We had the guardian bug where it repeats the main state when it gets an ezca connection error. 1122  This ezca connection error was caused by the dark offsets in the trans QPDs, and in the TR_X bank, which trigger LSC-XARM filters.  These offsets frequenctly cause us confusion because they aren't set in the dark offset script, but in the guardian in PREP_TR_CARM.  To avoid this confusion in the future Georgia added the adjustment of these offsets to PREP_FOR_LOCKING.  
• We've had many ezca connection errors for channels that the guardian should have been able to connect to so far.  
• CHECK_MICH_FRINGES unlocks the interferometer sometimes.  This state now tries to lock the michelson on a dark fringe, but if the alignment is too bad it can't lock and the beamsplitter saturates eventually causing a lockloss.  We could add some checks to this state to prevent this in the future.  

Further difficulties locking. 

• The microseism is around 0.8 um/second rms, and we can see that the arm cavities when free swinging are moving at about 2 um/second.  There is also wind, it is only gusting up to 20 mph, but on the Y direction at EY the seismometer shows about 0.15 um/second of tilt, which is higher than we normally have for this wind speed.  
• We are having trouble engaging ALS_DIFF, it works every few times.  
• We have had glitches in the Y arm, but we aren't sure if that is the cause of the problems.