(Niko, Hang, TVo, Danny, Keita, with Sheila, Dave Barker, Ryan, TJ and JeffK providing telephone technical and moral support)

• After such a windy night, relocking was not difficult at all in the morning.
• We lost lock once during CARM_TO_TR for unknown reason.
• We lost lock once somewhat after CHARD_BLEND or LOWNOISE_ASC due to 0.8Hz ASC oscillation (probably in DHARD_YAW). See Hang's comment.
• Since OMC SUS was still not settled from the initial kick by the OMC ASC when the second lock loss happened (that was before I realized that this was IFO ASC problem), in the next lock I waited for a while in DC_VIOLINS until OMC ASC settled though this might have been a red herring, anyway after this we were able to go to NOMINAL_LOW_NOISE.
• Two things to note at this point.
  1. Somehow we ended up in POWER_17W in nominal low noise. With a telephone support from Sheila, I put ISC_LOCK to manual, went to POWER_ADJUST, requested POWER_20W to LASER_PWR guardian, requested NOMINAL_LOW_NOISE to ISC_LOCK, and then put ISC_LOCK back into auto.
  2. However, in doing the above, we forgot to AC couple the ISS 2nd loop. Somehow the servo was able to take it, and I didn't care to go back to 17W, AC couple, then 20W, then DC couple, because I wasn't sure if AC coupling from DC coupling is reliable at all. So the power injected into IMC might not be the same as when everything is handled automatically by the guardian.
• We approved everything in SDF. Some are really negligible changes (e.g. diff of 1e-17). We need to go through the SDF files to set appropriate tolerances.
• LOCKLOSS_SHUTTER_CHECK guardian was in HIGH_ARM_POWER but the nominal state was LOW_ARM_POWER due to the change made yesterday. This didn't make sense to me so I changed the nominal to HIGH_ARM_POWER.
• We pressed OBSERVE button, the intent bit was set for a fraction of a second but it was reverted back to COMMISSIONING.
  • We lost about 2 or 3 hours due to this, but it turns out that H1:ODC-AUTO_UNSET_OBS_INTENT needed to be set to zero. This should be good enough for the engineering run for now, but we need to think about what we want to do for ODC in the future.
• H1:ODC-OPERATOR_OBSERVATION_READY was successfully set  to 1 at about 2018-12-15 20:51:00 UTC. .