Title: Ops Day Shift: 15:00-23:00UTC, 8:00-16:00PT, all times in UTC

H1 State: locked in ENGAGE_ISS_2ND_LOOP

Help: Sheila and Evan

Overview: H1 lost lock after violin 2nd harmonics rung up about 14 hours ago.  Kiwamu worked on it, then Sheila, and now Sheila and Evan.

Details: Violin 2nd harmonic at 1008.45 has been ringing up for a few days, and last night caused a lock loss.  There is a nearby peak at 1008.49. 

Day was spent working on filter gain and phase to lower peak - time consuming, and within the last 30 minutes, the peak is now coming down in amplitude.  Details in Sheila's alog.

ISI blend filters changed to 45mHz, which helped, given the useism.

No other issues to report.

Elli was here and used about 30 minutes of unlocked IFO time to complete her measurement.  She work from about 17:07-17:38UTC.

Evan, Sheila, Cheryl

We switched blend filters from 90 to 45 mHz in the last several minutes.  There were large glitches in green arm transmissions when I switched ETMX X direction and ETMY Y direction.  It seems like  ETMY direction switched something got misalinged (the Y arm green transmission dropped). Cheryl adjusted transmon Y to recover the build up.

If anyone from seismic is interested in figuring out why switching blends causes glitches, I started switching around 18:50 UTC and finished by 19:01 UTC on October 25.  

The microseims BLRMS is around  0.5 um/sec and the wind had been gusting up nearly up to 20mph over the last hour but is dying down now.  ALthough the arms got misalinged, the build ups are much more stable with 45 mHz blends in these conditions.

Ops Day Shift - 15:00-23:00UTC, 8:00-12:00PT, all times listed are UTC

H1: cannot get back to Low noise due to violin second harmonics around 1008Hz

Current Plans:

- Elli on her way in to do her measurement - takes about 30 minutes and she needs an unlocke IFO

- Sheila on her way in - she had me comment out the line that engages ETMY L2 MODE3 in the ISC Guardian, but suspects that that won't be enough to get back to Low Noise, so is driving in

Changes:

- ETMY L2 MODE3 in the ISC Guardian commented out, and I left a comment in the file that I did this today

Current state of ground motion:

- useism coming up again and upper data points are touching 1 on the seismic plot

- also some anthropogenic noise starting about one hour ago

TITLE:  10/25 OWL Shift:  07:00-15:00UTC (00:00-08:00PDT), all times posted in UTC     

STATE of H1:  ETMy violin mode issues.  H1 currently down.

Incoming Operator:  Cheryl

Support:  Kiwamu (drove onto site)

Quick Summary:  ETMy violin mode (2nd harmonic) has been ringing up over last 2 days.

Shift Activities:

• ETMy Saturations:  8:00, 8:09, 8:37, 8:41, 9:25, 
• The main activity for today were the issues with the ETMy violin mode.  Over the last few days, it has been slowly ringing up and last night it reached a point to drastically affect H1 sensitivity & it will continue to do so until it is damped out.  Damping out violin modes is a slow-going process where one makes a subtle change (waits 20-30min) and then one watches to see if there has been an improvement. 
• I made a few gain changes to the ETMy MODE 3, but then H1 dropped out of lock.

Handing off H1 to Cheryl.  H1 should be able to get up to Engage ASC3 or DC Read out and then one can continue work on damping ETMy violin.  Cheryl will contact Sheila when she gets a chance.  She has experience working on damping these modes, but will give Sheila a call this morning.

Notable changes:

anti whitening (FM1) OFF for OMC DCPDs (A&B)....as Kiwamu notes.

ETMy MODE3 currently at gain of 50 (100 is what used to be nominal, but this rings up ETMy).

State:  Out of Observation Mode and at DC_READOUT for Violin Mode work.

As noted earlier, we had rung up violin modes.  Kiwamu is now on site.  We are pausing Guardian so we can address the ETMy 2nd order violin mode.  (was not sure what to mark this as with Observatory Mode....used Preventative Maintenance at first, but then switched to Corrective Maintenance.   We will stay here until we are able to bring down these huge violin modes.

• 9:25 OMC DCPD alarms begin
• 9:59 Went out of Observation Mode (since I saw LLO was out...they were running A2L to help L1)
  • At this point I was on phone with Kiwamu.  We determined we had a violin mode rung up, and ultimately found it to be ETMy's 2nd order mode (1008.45Hz).  We referenced Dan/Nutsinee/Evan's 2nd Order Violin Mode Table Alog 20345.
  • Started to address this.
  • When first alarms occurred, the range was fine, but as the violin mode rung up more, the range began to nosedive (from 80Mpc eventually down to 30Mpc).
  • We found that for ETMy, MODE3 was obviously noisy with HUGE outputs
• Started to look at ETMy.  Changed gain to try and bring down violin mode (gain started at 100, I took to 50 and saw no effect.  I went to -100, and H1 broke lock.).  While doing this, Kiwamu said he was going to come in.
• 10:41 Lockloss

Note:  at the beginning I trended a channel which was red in the ODC Overview (H1:0MC-DCPD_A_INMON) & over the last day, these dcpds have been noticeably getting big during the last two locks (starting at 10/24 11:00 utc).  See attached plot for these PDs getting rung up (presumeably due to the ETMy violin).

At 9:25, started getting OMC DCPD Saturation alarms.  Not sure what to do here.  Can only see issue on the ODC overview & I'm getting Verbal alarms every few minutes.  The range is also taking a dive.

I don't have the rf45 template up because nuc5 had issues.  And I don't know where to find the dtt session for it.  So not sure if the issue is related to that.

The DMT Viewer sessions (for seismic trends) on NUC5 had been closing out the last few days.  The NUC5 instructions say this is probably due to memory loss, so rebooted the computer by clicking the button on the nuc computer.  

Unfortunately, I didn't obviously see the computer come up on the TVs.   Luckily Jim was here and tinkered with the TVs and saw that the TV switched to a different input source.  So, had to switch it to HDMI (also had to switch the upper TV, which required a ladder).  

I couldn't log in to the computer, so I had to pull a keyboard and mouse from another computer & logged in.  (after this I could share the screen remotely).

I opened up the seismic DMT sessions.  I wasn't sure how to open the rf45 session (Cheryl posted the link to that file...but do I need to ssh into a different session to run this?).

Final note:  I could not get the mouse onto the bottom TV screen.

TITLE:  10/25 OWL Shift:  07:00-15:00UTC (00:00-08:00PDT), all times posted in UTC     

STATE of H1:  H1 In Observing @ 79 Mpc

Outgoing Operator:  Jim

Support:  On Call-->Kiwamu until 7am & then Sheila from 7am - 4pm

Quick Summary:  H1 running nicely with a high range hovering at 80Mpc (due to low useism?).  Jim mentioned a peak on the running DARM spectra which looked new (and not seen on our 10/14 reference).  This peak is ~16.75Hz  (What is this?).

TITLE:  23:00-7:00UTC

STATE of H1:  Locked in Observation Mode @ 77Mpc

Support: I ran into Kiwamu in the kitchen? Miquel was here.

Quick Summary:  lost lock half way through, relocking was kind of slow

Shift Activities:

3:10 Lock loss, I was making food at the time, but I suspect RF45?

3:45 DRMI and PRMI are no good, start initial alignment

4:15 Initial alignment done

5:00 relocked, A2L run, it leaves some diffs in OMC that I revert, which brings up a change in LSC ARM input matrix. Not sure what it does, but the IFO is running so I accept it.

RF45 has been slightly noisy tonight, seems to coincide with ETMY saturations. I couldn't find the directions on how to deal with it, someone threw away the sticky on the ops workstation, and it seems the directions haven't made it into the ops wiki.

Lost lock at about 3:00 UTC, and was struggling a little to get it back. IFO is relocked now, I'm running A2L before resuming observing, should be just a couple more minutes.

TITLE:  15:00-23:00UTC, 8:00-12:00PT, all times in UTC

STATE of H1:  Locked in Observation Mode @ 77Mpc

Incoming Operator:  Jim

Support:  Jordan Palamos (fellow)

Quick Summary:  H1 locked entire shift

Shift Activities:

Glitches in the range:

17:36:19UTC - ETMY saturation, glitch in range, 17:38:00UTC

18:38:00UTC - glitch in range, not announced as ETMY

18:55:00UTC - glitch in range, not announced as ETMY

18:04:01UTC - ETMY saturation, glitch in range, 18:06:00UTC

19:03:20UTC - ETMY saturation, glitch in range, 19:05:00UTC

19:28:19UTC - ETMY saturation, glitch in range, 19:30:00UTC

20:35:16UTC - ETMY saturation, glitch in range, 20:37:00UTC

21:04:00UTC - glitch in range, not announced as ETMY

22:00:56UTC - ETMY saturation, glitch in range - NONE

22:21:00UTC - glitch in range, not announced as ETMY

Quiet shift with no earthquake activity, and only one burst of wind around 18:50UTC that got up to 20mph.

The 45 MHz FOM is userapps/isc/h1/scripts/H1_45MHz_Demod_FOM.xml

The six-panel seismic FOM screen is /ligo/home/controls/FOMs/Seismic_FOM.xml

TITLE:  10/24 OWL Shift:  07:00-15:00UTC (00:00-08:00PDT), all times posted in UTC     

STATE of H1:  Locked in Observation Mode @ 76Mpc

Incoming Operator:  Cheryl

Support:  Kiwamu (on-call, and on phone for 1.5-2hrs)

Quick Summary:  H1 back with 90mHz Blends for BSC-ISIs & ASC Soft filters OFF---> Since useism has been trending down over the last 24hrs (it's currently about 0.18um/s).

Shift Activities:

• ETMy Saturations:  11:35, 13:23,
• 8:30 Started Initial Alignment
• 11:30 Observation Mode

Chris B, Joe B

After LLO had locked again, Joe and I took the opportunity to perform the coherent stochastic injection. CW injections were off at both sites. And the intent bit was off at both sites.

For the LLO couterpart aLog entry see: LLO aLog 21999.

Waveform:

The waveforms injected were: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/stoch/Waveform/SBER8V3.txt

Injection:

At H1 Chris performed the injection with the command:
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 SBER8V3_H1.txt 1.0 1129673117 -d -d  > log_stoch.txt

I've attached the log.

As we were doing the injection we noticed a range drop of ~10%.

IMPORTANT ACTION ITEM:

The end of the stochastic waveform was not tapered. So when the injection ended it introduced a large transient into the ETMY. Robot voice was activated. This needs to be fixed. The beginning was properly tapered.