TITLE: 11/05 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Aquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

- Started off with running an IA, which ran through with no issue

• Lockloss at FIND_IR (COMM beanote was at -12, DIFF at -6), IMC unlocked, then again at LOCKING_ALS, same reason...
• I noticed that ALS DIFF was VERY noisy when trying to acquire IR, it was at its resonant peak but would not actually catch and just oscillate around it, despite me trying to manually walk it
  • I would assume this oscillation of DIFF and it not REALLY being found caused issues that Ryan saw last night once they got further into the locking sequence - scope attached
• Tried running through CHECK SDF to see if maybe a bad offset was implemented, but ran into the same issue
• The IMC also is continuously losing lock during reaquisition, unsure why
  • Since the IMC is having issues as well, I have attached witness sensors for PR2/3/M as well as MC1/2/3 just to be thorough, seems like there is some shift in MC2/3 and PR2, but I'm not entirely convinced it is a drift/alignment issue (especially since we can lock COMM and ALS with relative ease)

- Went through the rotating call list: contacted Daniel, left a message, then called Jim who noticed that all 4 quad ISI SC guardians had not been reset since the master timing was swapped

• This fixed the issue, these SC offsets being off for all quads coupled with high microseism (which can cause issues during CARM offset stages according to Jim), made it near impossible to lock H1
• To prevent this from happening in the future, Jim pointed out that if we ever do a reboot of any of the front ends containing any BSC ISI to take SEI ENV to MAINT then back to CALM once the front ends come back up - his alog here

- After the issue was solved, relocking was automated, back to NLN @ 19:47/OBSERVE @ 20:10

• SQZ MANAGER message: "SQZ ASC AS42 not on?? Please RESET SQZ ASC"
  • Cycled the guardian which fixed the issue
• TCS POWER message on DIAG MAIN: "CO2 powers are not in nominal state"
  • However when I checked the TCS guardians, all the guardians were reading back green and happy - not sure why this message is showing but was still able to go into observing nonetheless - Tagging TCS
  • Attached ss of ethercat TCS channels - not sure if these are nominal so leaving for team TCS to look at on Monday
  • Also attaching CO2 overview for both arms

- H1 went into COMMISSIONING @ 21:50 to adjust SQZ temperature/check SQZ angle - attached SDF

• Back to OBSERVE @ 22:04

- Lockloss @ 22:58, cause unknown

- Relocking:

• ALS DIFF still looks wobbly but was high enough to catch and move forward without intervention
• Went through PRMI locking
• Rest of locking was automated, back to NLN @ 23:57

LOG:

No log for this shift.