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

(Corey, Kiwamu)

After no obvious headway, Jim and I both were thinking another Initial Alignment was looking inevitable.  After he left around 1am, I went about starting an Initial Alignment. 

During the alignment, while in ALS, I noticed one of the control signals not converging (ETMX M0 LOCK Y OUT 16).  Is this normal?  I went ahead and offloaded Green WFS.

Problems locking the Xarm for Input Align

Then when starting Input Align, the Xarm simply would not lock.  Would get fringes which would give powers up to 1.0, but they were less than a second.  The Mode Cleaner would drop out every few minutes as well.  When there were fringes in the Xarm, one could see the ASAIR spot shift in yaw a little.  These were the symptoms.  I waited for about 20min.  Then I woke up Kiwamu at about 1:45am PST.

PR2 Tweaked In Yaw

Since the IMC kept dropping, we addressed input pointing by tweaking PR2 in yaw.  I moved 1.0 units (from 4313.6 to 4312.6)

Dark Offsets

Kiwamu suspected bad dark offsets, so we pitched MC2 to prevent IMC locking, and then ran the dark offset script (/opt/rtcds/userapps/release/asc/common/scripts/setQPDoffsets)

After running this the offsets were not zero (more like 4!).  Found offsets in the SUM filter banks (which are at sitemap/LSC/Photodetectors overview/X_TR_ {A & B} /SUM {full}.  We took these to zero & were now happy with offsets.

At this point, I went to get water while Kiwamu watched X-arm locking.

LSC XARM Gain

We tried to give Xarm a kick by enabling the ETMX M0 LOCK L OFFSET (& also disabled the BOOST [FM4]), but this didn't have much of an effect....

While I was getting water, Kiwamu changed a gain for XARM (located at sitemap/LSC/Overview/XARM).  The gain is usually at 0.05 during INPUT_ALIGN, but Kiwamu took it to 0.1 & this finally locked XARM.  So to get the XARM to lock one doubles the gain, waits for it to lock up, and then drops it back down (i.e. to 0.05).  

At this point we decided I should start over with the alignment, and that Kiwamu would go back to sleep...I think we were on the phone for about 1-1.5hrs.

Back to Initial Alignment & Locking

Ran through an Initial Alignment with no noticeable issues.  (Dark Mich took a while to settle down; that seemed new to me, and Jim noticed this, too when I saw him aligning).

Finally went for locking.  Had issues at various points.  For ALS, there were VCO/PDH Errors popping up on Guardian.  Going to the Yarm VCO showed errors on that screen (ALS_CUST_LOWNOISEVCO.adl).  So, from Sheila's Training powerpoint file, I saw that I should take the Tune Ofs slider to zero, and that took care of that.

ASC Soft FM1 -20dB filters:  OFF!

Since useism has been trending down over the last 12 hrs, and since the BSC-ISI blends are back to the 90mHz ones, I opted to let Guardian Turn OFF the ASC SOFT filters.  This is different from previous lock segments!

Made it to NOMINAL_LOW_NOISE!

After over 4.5hrs H1 was finally back to NLN!  SDF had a few Diffs, so I went through them:

• SUSETMX:  ETMX M0 LOCK L  FM4 (boost) was left OFF, so I re-enabled it.
• ASC:  ASC {D & C} SOFTs for {P & Y}:  These filters had been kept enabled (giving us -20dB) for the last few days, but since useism is lower, I did not enable these & let Guardian do its thing.  I ACCEPTED these.
• OMC:  the LSC OMC matrix element was 0 again (as I noted), so I REVERTED it to 14 & hit LOAD MATRIX.  Why is this slipping through the cracks??  Is Guardian supposed to handle this?  (Kiwamu says we should ACCEPT the 0 value next time we get the chance, since this matrix element is irrelevant, it's an OMCDC to CARM element.)
• ISCEX:  Dark Offset stuff!  I ACCEPTED all of this stuff.
• ISCEY:  Dark Offset stuff!  I ACCEPTED all of this stuff.

O1 CDS Overview RED TIMING ERROR

Before going to Observation Mode, I noticed SUSETMY had a TIMING RED box.  Clicked "Diag Reset" to clear.

Went to Observation Mode at 11:32UTC

[Time for lunch]

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

STATE of H1:  Jim Aligning

Outgoing Operator:  Jim

Support:  On Call-->Kiwamu

Quick Summary:   Arrived to see Jim starting an alignment.  Started attempting to lock.  For DRMI, we had a quick wrong-mode-lock, but could not get powers up, so we tried PRMI, but it this never locked up.  After head scratching, we are figuring out:  To Align (again), Or Not To Align.  I'm trying to lock one more time with this alignment again.  If there is no luck here, I might try another initial alignment.  Stay Tuned.

Title: 10/24 EVE Shift 23:00-7:00 UTC

State of H1: Relocking

Shift Summary:  Locked in Observing Mode for most of the shift, lost lock shortly before Corey arrived

Activity log:

23:06 Lock loss

00:30 Switch back to 90mhz blends, useism and winds are both quiet

1:00 Lock is reacquired

6:37 lock loss, no clear cause, winds are quite, useism still going down, none of the other foms show anything obviously suspicious, I start a new initial alignment because ALS comm beatnote has been trending down (was 2 db at the beginning of the 1:00 lock stretch, was 1db now, with ALS X being difficult to hold)

We're still having operators run A2L before going to Observe or when leaving Observe (e.g. for maintenence), so there's more data to come, but I wanted to post what we do have, so that we can compare with LLO's aLog 21712. 

The 2 plots are the same data:  The first uses the same axis limits as the LLO plot, while the second is zoomed in by a factor of 5.

It certainly looks like we aren't moving nearly as much as LLO is. 

Note that the values for both LLO and LHO are missing a coupling factor of L2P->L3L, which will change the absolute value of the spot position displacements.  However, since we're both wrong by the same factor, our plots are still comparable.  See aLog 22096 (the final comment in the linked thread) for details on the factor that we still need to include.