Evan and Keita are disconnecting the RF AM monitor in the PSL enclosure.
Running a2l.

The ISC_LOCK guardian was stuck at DC Readout Transition because the OMC wasn't ready, although the guardian log only said "not ready", and there was no notification that popped up.  Patrick re-requested the OMC guardian to go to Ready For Handoff (which worked), but I also added a notify to the ISC_LOCK guardian to say "OMC not ready" if this happens again.

Lost lock trying to engage ISS second loop by hand.

SUS SR2 saturating 17:48:35 UTC

Did this yesterday afternoon (11/18) but forgot to log it then.

17:10 UTC Out of observing for Keita to test grounding configurations for RF AM monitor. Not going into PSL enclosure. (WP 5616)

TITLE:   Nov 19 Owl Shift 08:00-16:00UTC (00:00-08:00 PST), all times posted in UTC

STATE Of H1: Observing at 80 Mpc

SUPPORT: David, Laura, TJ, Andy, Dan (sorry if I missed any of you!)

LOCK DURATION: 7 hrs 53 mins

INCOMING OPERATOR: Patrick

END-OF-SHIFT SUMMARY: We have nasty stationary lines between ~100-1000Hz since we started locking 12 hours ago. Few Detcharians gathered this morning to follow this up. Keita arrived and shed the light to this mystery that it is in fact the newly installed RF monitor injecting noise into DARM (alog 23555).

ACTIVITY LOG:

15:16 Bubba driving along the arms to check on tumbleweed

15:29 Bubba back. The landscape crew is taking care of it. They're working from 250m from EX towards Corner station.

TITLE: 11/19 [DAY Shift]: 16:00-24:00 UTC (08:00-16:00 PDT), all times posted in UTC
STATE Of H1: Observing @ ~ 80 MPc.
OUTGOING OPERATOR: Nutsinee
QUICK SUMMARY: From the cameras the lights are off in the LVEA, PSL enclosure, end X, end Y and mid X. I can not tell if they are off at mid Y.
Earthquake seismic band is between ~ 0.01 and 0.03 um/s. Microseism has been coming down and is between 0.1 and 0.4 um/s.
Winds are between ~ 0 and 5 mph.
ITMX, ITMY and BS ISI blends are on 45mHz. EMTX X and ETMY Y ISI blends are on 45mHz. ETMX Y and ETMY X ISI blends are on Quite_90.

I've been noticing all night but not sure where from. Those nasty little lines seem to have come with a broad peak at 1040Hz. It's not the violin mode second harmonics (which ends at ~1010Hz).

Found damp settings for 1009.0273 Hz and 1009.6825 Hz (ETMY). Both lines have very low amplitudes to begin with (only a magnitude above the noise floor) so once I was able to damp them slightly I turned the damping off. Here's the table. The BP filters live in ETMY L2 DAMP MODE4 FM7 and FM10.

Livingston seems to be having problems with their front end and won't be up for a while. I'll take some time to work on the 2nd harmonics violin modes.

11/19 Owl Shift 08:00- 16:00 UTC (00:00-08:00 PST)

State of H1: Observing

Out going Ops: Ed

Quick Summary: The ifo lost lock the minute I walked in (after abandoned it early for two nights in a row I don't think it likes me anymore). We are now observing again at 08:35 UTC. I ran into a small problem with the Guardian during Engage ISS 2nd Loop. After 4 minutes Guardian gave me a message that Engaging ISS 2nd Loop fail and once I successfully engaged the loop by hand ISC_LOCK Guardian didn't seem to recognize it. I had to re-request ENGAGE_ISS_2ND_LOOP and do it again.

TITLE:    Nov 18 DAY Shift 00:00-08:00UTC (04:00-00:00 PDT), all times posted in UTC

STATE Of H1: Locking

SUPPORT: Kiwamu

LOCK DURATION: ≈3.5 hours

INCOMING OPERATOR: Nutsinee

END-OF-SHIFT SUMMARY: Lots of little issues that are documented in my activity log. Nutsinee arrived right as the Oklahoma quake broke our lock

ACTIVITY LOG:

01:25 begin initial alignment after Kiwamu re-aligned beam pointing in IMs and MCs

03:13 Locking sequence gave me trouble for a while at DRMI after it locked and dropped. Reverted back to PRMI to tweak. Transistioned to DRMI locked almost immediatley. Stopped at ASC_PART3. made it to Bounce_Violin_Mode_Damping and then broke

03:39 Have had to tweak th COMM VCO due to poor X buildup in FIND_IR. Now haveing Cage Servo issues. Kiwamu is on it.

03:55  back to locking again…

04:23  Diag reset on H1IOPASC0 Timing Error

04:47  IFO locked at NLN/75Mpc. Kiwamu cleaning up SDF after his work.

05:04  Noticed that the Lock Timer wasn’t running so I started it. Not sure if it supposed to be from NLN or Intent bit. It’s ≈10 minutes behind the intent bit.

08:00  Down due to Earthquake. Handing of to Nustsinee.

07:52UTC 

4.7mag in Oklahoma

USGS event link

Ed, Kiwamu,

During the course of relocking effort today, we ran into three issues associated with the guardian automation. Two of them are fixed/improved by editing the guardian codes while we were not able to fix the last one.

Here is some notes.

• Issue 1 (fixed), INPUT_ALIGN of IFO_ALIGN does not lock the X arm.
  • We found that this was due to a too high gain which had been increased in this afternoon (alog 23532) with an aim to improve the loop stability. We reverted the gain back to the nominal of 0.05 in lscparams.py.
  • The new code is submitted to SVN. It works fine with the nominal gain so far. We have no idea why it needed to be increased by a factor of 3. Perhaps related to the bad input pointing (alog 23538) ?
• Issue 2 (fixed), OMC_LOCK was consistently unable to find the carrier resonance.
  • This was found to be due to a unfortunate PZT scan range -- the peak-finding algorithm was unable to identify three high peaks (two from 45 MHz sidebands and one from the carrier). We have been mitigating this issue by adjusting the scan range so that the three peaks are separately captured in different segmented time series. This time, one of the segmented data chunk tended to capture one of the 45 MHz sideband as well as carrier. This situation ended up forcing the algorithm to pick only one of them and abondon the other. This in turn let the algorithem think there were only two peaks. I changed the scan starting voltage from -30 to -24 V so that three peaks are captured in different segments.
  • The latest code (OMC_LOCK.py) and parameter file (omcparams.py) are checked into SVN.
• Issue 3 (not fixed), CAGE_SERVO did not warn us that it was railing.
  • No idea why. It is supposed to give us a notification message when the amount of feedback is high. However it did not behave that way and simply kept servoing SR3 without giving a notification/warning message. We reloaded the code, but it did not seem to enter the if statement in which the warning message is given.
  • We manually offloaded the control signal to the upper stage in SR3.