TITLE: 11/06 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 2mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.49 μm/s
QUICK SUMMARY:
Walked in to see TJ waiting for H1 to lock DRMI (after a BS tweak in CHECK MICH FRINGES, he got DRMI to lock). Then took H1 immediately to NLN (Guardian took it to 35W) with no issues....EXCEPT it broke lock within 30 sec! On ASC StripTools could see ASC CSOFT Yaw getting noisy & bigger for a minute before the lockloss (to a smaller extent the DHARD Yaw Error signal grew about 12sec before the lockloss.) [Attaching screenshots of the ASC StripTools (sorry the CONTROL one has the channels chopped off...just note that the noisy CSOFT YAW is the avocado green trace)].
-->Contemplating going to 25W...we'll see how we look on the next lock.
- Other Locking Notes: ITM Ring Heaters continue to be OFF (per Sheila's request to TJ)
- useism has been visually trending down for the last 8hrs.
Making 2nd Lock attempt now.
2nd Attempt looked similar with ASC CSOFT CONTROL signal getting noisy.
(after this lockloss, the ITMy is oscillating [took about 10min to settle down on its own]. Will wait it out.)
What to try to stay at Nominal Low Noise:
- 25W (instead of 35W)
- Check SDF/Guardian when we are NLN to see if anything looks awry.
- Turn on ITM Ring Heaters
- Open to suggestions...
For #1 above, on the ISC_LOCK_STATE Guardian Node's "lscparams.py" file, I have:
- Uncommented/commented out the appropriate power_setpoint values for 25W (lines 13 & 14).
- Saved file
- LOADed ISC_LOCK_STATE