Summary of the DQ shift from Thursday 9th March to Sunday 12th March (inclusive), click here for full report:

* The DQ Shift started with a duty cycle of 76%, which increased to 86%, 95% and on Sundaw went back down to 60% due to extreme weather conditions of high Wind and microseism ground motion.

* Range sensitvity mainly around 65 Mpc, with the excepcion of Friday which most time around 60MPc due to strong Winds.
* Weather conditions has had an impact on range sensitivity and range during this DQ shift.
* Not many locklooses; some due to PI ringing up, other was preceded by soft. sat. of H1:LSC-X_ARM_CTRL, others high winds and micoseism ground motion.
* Script 'a2l' has been run quite a few times during this shift due to the common presence of low freq. noise (10-20Hz), which mostly had not impact on range sensitivity.
* A few Earthquakes which caused not much problem.
* IMPORTANT: Driving PI mode 23 (for instance when applying damping filters) caused glitchy narrow lines at (14.5, 64.0, 78.5 and 142.5 Hz), this dominated Omicron glitchgram with a 60-80Hz band of high SNR glitches. Commissioners have noticed this an put in place a practice of not damping this mode anymore unless required for lock acquisition.
* IMPORTANT: The Gold Star Omicron glitch for the whole of Friday was a blip glitch coincident with all quadrants of H1:SUS-ETMY_L2_NOISEMON, and the highest New SNR glitch for Sunday reported by PyCBC? live 'short' was of this type too. This relates to the alog entry by Miriam, Hunter, Andy where it was reported evidence that 'Some blip glitches may be due to ETMY L2 coil drive'.
* Observed high SNR glitches caused by scattering of SUS-SRM and SUS-PRM
* Increased limits of the X and Y arm LSC tidal HEPI off load for tidal control.
* PLS tripped with standard Flow-1 error, which was caused by the drop in flow rate in head 3. This was quickly solved.
* On Sunday high winds and microseism caused repeated tidal alarms "Tidal X/Y error" as the tidal arm servos were railing at their limits (solved by increasing their range), this had an impact in lock acquisition.
* On Sunday 'a2l' script did run with errors due to execution permissions, leaving the Gains to some random values worse than when the script started which increased low frequency noise. The permissions issue will be soon looked up and the script may be modified such that when errors occur the Gain values should be reverted to the ones at the start.