Only item to report is the BS SUS which is RED on CDS, but this is a known issue. It is locked down, but it was damped before yesterday and tripped yesterday (TJ later informed me this is related to new Guardian state for allowing SUS to ride through earthquakes better...it's being worked on by TJ & Sheila).
Dust Monitors fine this morning.
Maintenance has already started with (1) Ken has started work in LVEA for installing electrical outlets for CP1/2, and (2) Christina has started LVEA cleaning.
A quick comment on the SUS Guardian WDs. It looks like they acted as we expect them to; a WD stage(s) will trip, the SUS Guardian will go to the tripped state and notify the operator of which stage(s) are tripped, any stages above the tripped stage(s) will continue to damp, until the tripped stage(s) are reset by an operator then it will stay in the TRIPPED state. This allows for at least a bit of damping if it is safe for the suspension to do so. Previously, if one stage would trip, the SUS Guardian would then shut down the entire chain and sit in the TRIPPED state until the operator reset the suspension. Sheila proposed this solution and then loaded it on Nov. 10 (alog39392), but we haven't had much chance to test this much.
What does surprise me, is that while the suspension was locked down it was still able to do some damping. The BS was locked on Nov. 30 and the Guardian logs indicate that the suspension was last untripped and brought back to ALIGNED at 21:52 UTC on Nov. 30. I'm not sure when it was locked, but the Guardian stayed in the ALIGNED state until yesterday, Dec. 4 23:05 UTC. Seems odd that it could be locked and damped at the same time for 4 days...