TITLE: 02/28 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventative Maintenance
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.18 μm/s
QUICK SUMMARY:  Locked for 49 hours 42 minutes at the time I took the IFO down.  I asked Keita if we could keep the IFO up to better our new O2 lock record but he said "Take it down!."

   IFO in Observing for some 48.5 hours. A2L and PIs are OK. Weather and environment are good. Other than one large glitch, no operational troubles noted. 

   Reset Timing error on H1IOPASCO

• EQ seen at:
  • USGS: Listed as occurring at 07:49utc
  • Seis BLRMS: ~08:00utc
  • Terramon: 00:25 arrival estimate
• Magnitude: 5.6
• Location: Namie, Japan
• Lock Status: H1 no apparent effect.

TITLE: 02/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Observing the entire shift other than a quick a2l.
LOG:

• 04:44 Out of Observing to run a2l while LLO is down.
• 04:50 Back to Observing

LLO just unlocked so Im currently running a2l. We have been locked for 38.5hrs.

[Keita, Dave, Kiwamu]

WP 6506, ECR E1700074 (waiting for approval as of now)

We have added a subblock at the top level of h1asc.mdl to accommodate the newly installed bullseye sensor (34154). If the ECR is approved, this change will be implemented tomorrow during the maintenance period at earliest. The channel names will be PSL-DIAG_BULLSEYE_*.

We made sure that the model compiles without errors. So the model is ready to install. This is an H1-specific change. We didn't change the ASC_MASTER model at all for this change [don't be confused with Jenne's activity which edited the ASC_MASTER model (34444) and is orthogonal to our activity]. The attached are screenshots showing how h1asc.mdl looks like with the addition of the bullseye block.

LLO has been using an offshoot of the ASC_MASTER simulink model that generates almost all of our ASC and ADS channels.  It seems that the only thing they added was several extra ADS filter rows, so that they could use some of them for spot centering, and still have others available for other things. 

By using an offshoot though, they have missed out on many of the upgrades that have gone into the LHO ASC. 

This is something that has an issue tracker open in FRS 7287.  Once we both do an svn checkout and are using the main ASC_MASTER block, this issue should be close-able.

I have replaced the LHO ADS part with the LLO version, which includes 10 each ADS filters for pitch and yaw, rather than 5 each.  This also removes several inputs that we had been using for testing during commissioning time over the summer, but no longer need (AS36 channels).  The modified ASC_MASTER part is checked into the svn, ready for LLO to pull.

Unfortunately, LLO also had re-ordered the input matrix to make the order make a bit more sense.  Since they have calls to this matrix interleaved several places in their guardian, and we only use it in ENGAGE_SRC_ASC, I have prepped the guardian code to handle the change.  In ISC_LOCK, lines 2470-2476 should be commented out (or deleted), while lines 2482-2489 should be un-commented.  The first set of lines is our existing code, and the second set is the re-ordered version for the new input matrix.  This must be done after the ASC model is restarted tomorrow, before we get to ENGAGE_SRC_ASC in the lock aquisition sequence. 

Note that LLO should need to do no work, and make no code changes, to keep the same functionality that they currently have, since I've chosen LHO to be the ones to change the guardian code.  The only thing they should need to do is change the link in l1asc.mdl to the ASC_MASTER block, rather than the offshoot they've been using.  They'll have a few extra epics channels floating around that they won't use (like RF90 centering, which we will again use after the post-O2 vent), but everything should work as before.

If there are problems with ENGAGE_SRC_ASC tomorrow and I'm not in the control room, call me.  But hopefully we'll finish maintenance early enough that we can go through that state before the end of the day.

This reconcilliation was done under work permit 6505.  After we restart the ASC model and the DAQ, we can close out this permit.

WP 6503

Plan today was to re-terminate the HV ion pump connector. The old connector was cut off and cable tested with a volt meter. No short. A more valid test would be to HiPOT the cable with no connector installed to ensure no other cable issues. Since this requires access to the mechanical room at EY, work was put on hold for tomorrow's maintenance window. See alog 34386 for troubleshooting of cable last Friday.

F. Clara, R. McCarthy, G. Moreno

TITLE: 02/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 31mph Gusts, 19mph 5min avg
    Primary useism: 0.17 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY: Winds are up but we are still observing at 61Mpc on a lock going on 33+hours.

TITLE: 02/27 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 55Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

H1 locked and Observing, going on 33hr35min. Winds starting to pick up to near 40mph
LOG:

17:55 Travis and Betsy to MX

18:08 Fil and Gerardo to y-28 to fix a cable

18:55 Timing error in EX (known issue/in consequential). reset itself.

18:56 Travis and Betsy to MY

19:30 Richard out to Fil and Gerardo

19:38 King Soft on site to service RO water.

19:45 Richard back from visiting Gerardo and Fil

20:00 Fill and Gerardo back

20:33 Automated phone call from Hanford Emergency regarding monthly testing from 12:20PST to 2:30PST. Area sirens will be sounding at approximately 1:15PM.

22:08 Jason and Betsy goin to MY

23:56 Jason and Betsy are back.

Data was good throughout the four days.  Hyperlinks are behaving strangely for me in the html editor so here's the URL of the shift report:

https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20170223

Overall Summary:

- Duty cycle of 82.2% for the four days.
- First two days were hit with many EQs and aftershocks. Our duty cycle was actually pretty good considering how many spikes there are on the summary page's seismic BLRMS plots, but they did cause some locklosses.
- Work was done to damp PI modes at times and they were noted in the aLogs but they were not blamed for any locklosses.
- Evening of the 24th some opportunistic commissioning was done.
- PSL tripped at 8:38 on the 25th. Expert was needed to get things working and were out of Observing for a little more than 3 hours.
- Interesting 3.5M EQ from central Washington on Sunday the 26th knocked us out of lock but did not show up in the normal EQ band seismic noise plots. Instead, large spikes showed up in all of the higher frequency ground motion plots (> .3 Hz).

Apollo is working at Mid X on the HVAC controls upgrade and have the supply fans for the building off until sometime tomorrow. May see some slight temperature excursions until the fans are operable again. 

I repeated the analysis in alog 33561 to update the included time segments. 

I identified two suggested DQ vetoes, described in the attachment.

• Suggested snow plow flag time:
  • H1:DCH-SNOW_PLOW (v3): Feb 09 2017 13:05-16:30 UTC
• Bonus DQ flag: 
  • H1:DCH-HIGH_WIND_EY: Feb 10 2017 06:30-09:30 UTC (lock loss at 07:43 UTC: alog 34035)

Suggestion for detchar follow-up: test the effect of thresholding H1:PEM-EY_WIND_ROOF_WEATHER_MPH on 30 MPH using Omicron triggers and consider adding an automated DMT DQ flag. 

Thank you operators for posting good notes in the alog! 

Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 800 seconds. LLCV set back to 16.0% open.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 593 seconds. LLCV set back to 37.0% open.

[Vaishali, Kiwamu, Sheila(remotely)]

WP 6497

Sheila suggested us doing an interesting test today during the commissioning time window. The measurement we did is a coherence measurement between the bullseye sensor and DARM while changing the PR3 spot position.

The result suggests that a part of the broadband lump in 200 Hz-1 kHz is due to beam size jitter with a caveat that we couldn't fully reproduce the broadband lump.

[Background]

Back in pre-O2 commissioning, we had unidentified broadband noise in 200 Hz - 1 kHz (e.g. alog 30752) which was found to be a function of the PR3 spot position. One hypothesis was beam size jitter somehow coupling to OMC DCPDs.

[The measurements and results]

We tested three different PR3 spot positions, all of which is characterized by POP_A QPD readouts as follows.

• Configuration (A): POP_A_PIT = POP_A_YAW = 0, PRG = 30-ish (a.k.a no action)
• Configuration (B): POP_A_PIT = -0.4, POP_A_YAW = +0.3, PRG = 32.5
• Configuration (C): POP_A_PIT = -0.3, POP_A_YAW = +0.15, PRG = 33.3

Our intention was to reproduce what Sheila observed in this past November (31628) with a hope to reproduce the broadband lump. However, we didn't get drastic increase in the frequency band -- we only obtained a 18% increase at around 400 Hz. See the second attachment for the increased DARM noise. Despite different alignment, configurations (B) and (C) gave almost identical DARM noise. Increased noise below 30 Hz is presumably due to mistuned A2L couplings, as we have moved the spot position.

The first attached figure shows the coherence between the bullseye sensor (sorry for any confusion, but PIT = beam size jitter, YAW = horizontal pointing jitter). The dashed lines are the ones from configuration (A). Notice that they are almost at the same level as the previous measurement (31628). The solid lines are the ones from configuration (B). Those from configuration (C) are not shown as they are almost identical to configuration (B). As we have moved the PR3 spot position, the coupling of beam size jitter increased while the horizontal jitter coupling reduced. The coherence for beam size jitter became 0.05-ish above 300 Hz corresponding to a fractional contribution of 22 % to the DARM amplitude spectral density. Also, at the same time, the power recycling gain improved which is consistent with what Sheila observed.

These results indicate that broadband noise is more or less reproducible, and also, a part of broadband noise is due to beam size jitter.

Later, we tried further exploring the parameter space of the PR3 spot position to see if we can further elevate noise in 200 Hz - 1 kHz. This lead to a lockloss presumably due to too much misalignment on PRM when we were at (POP_A_PIT, POP_A_YAW) = (-0.3, +0.6). We couldn't find a location where the broadband lump becomes more prominent.

[A minor change in bullseye signals]

Besides, we made minor modifications on the bullseye settings.

• we changed the sensing matrix for beam size jitter such that the sum of the outer segments and inner segment balance with a hope to reject intensity noise.
• we found that the sum signal didn't have a low pass. This was causing an extra intensity noise coupling to the PIT and YAW readouts. We installed a low pass (two poles at 30 mHz) which drastically reduced the coherence with intensity down to 0.01 or even less.