No issues other than the EY CRC error.

Verbal Alarms announced an "EY CRC Error" at 9:51 UTC.  Following Dave's instructions, I successfully restarted the HofT calibration code.  GWIstat is now reporting that LHO is green and "OK+Intent", where before it was yellow and "HofT Bad".  The DMT SPI page never showed an issue with the calibration (it was always green).  I'll check the Detchar summary page when it refreshes to make sure it has greened up.

TITLE: 04/21 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 9mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:  No issues handed off.

TITLE: 04/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY: Observing entire shift. Nearly lost lock upon arrival of 5.4 magnitude earthquake in Tonga. One very large random glitch that saturated the OMC DCPD.
LOG:

~23:44 UTC 5.4 mag earthquake in Tonga arrived
03:56 UTC LLO notified us that they are not recording data
04:41 UTC Huge glitch with OMC DCPD saturation
04:47 UTC LLO back

Have remained in observing. Came close to losing lock but managed to ride through a 5.4 magnitude earthquake in Tonga.

5.4 Pangai, Tonga

Was it reported by Terramon, USGS, SEISMON? Yes, Yes, No

Magnitude (according to Terramon, USGS, SEISMON): 5.4, 5.4, NA

Location: 112km SE of Pangai, Tonga; 20.568°S   173.644°W

Starting time of event (ie. when BLRMS started to increase on DMT on the wall): ~23:44 UTC

Lock status? L1 remained locked. H1 remained locked, but looked on the verge of losing lock. Large glitches and corresponding ring ups of PI mode 23.

EQ reported by Terramon BEFORE it actually arrived? Not sure

TITLE: 04/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 56Mpc
OUTGOING OPERATOR: Nutsinee
CURRENT ENVIRONMENT:
    Wind: 16mph Gusts, 13mph 5min avg
    Primary useism: 0.16 μm/s
    Secondary useism: 0.22 μm/s 
QUICK SUMMARY:

No known issues.

The 4.7kHz line was reasonably high, but wasn't ringing up. Evan and Sheila thought it might be corrupting the data so we tried to damp it. The original setting of +30 deg phase didn't do much so I turned on -60deg filter as Patrick suggested. The line went down on DARM ASD but rang back up very quickly. I didn't have my dtt opened but I believe what happened was -60 + 30 deg phase worked well with one of the lines but quickly rang up the other line. I turned off the -60deg and was able to damped the other line with +30 deg. Right now the gain is left at 0. I accepted the SDF diff and went back to Observe.

If 4.7kHz doesn't ring up by the end of EVE shift, I would like to comment out the line in the guardian that turn on the gain for this mode.

TITLE: 04/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC

STATE of H1: Observing at 56Mpc

INCOMING OPERATOR: Patrick

SHIFT SUMMARY: Commissioning first half of the shift. We lost about an hour possibly due to the ALSX fiber polarization being very close to the limit. After we turned down the polarization we had no issue relocking. 

LOG:

16:00 Commissioning started

16:11 Karen+Christina fork lifting in mechanical area/LSB

16:15 Robert to LVEA

16:46 Chandra to LVEA

16:54 Chandra out, heading to Mid stations

17:03 Fork lifting done. Sheila done. Robert to LVEA

17:17 Kyle banging something loud in the vacuum lab. Asked him to postpone until Robert measurement is done.

18:13 Robert out

18:22 Chandra back

20:23 Robert out. Done for the day.

20:30 Back to Observe

21:03 Karen left VPW  (drove there like an hour ago)

22:56 Out of Observe to address 4.7kHz violin mode.

23:07 Back to Observe

[Vaishali, Jenne]

We used the last few minutes of commissioning time today to measure the ASC sensing matrix.  This is the first time that we have made this measurement since POPX was installed.  Per JeffK's suggestion, we turned off the 7.9Hz calibration line to avoid confusion with our 8.125Hz measurement frequency (we used his new guardian state that actually turns off all the Pcal lines, then turns them back on before we go to NLN).  

Vaishali is looking at this data to compare with previous measurements, and her Finesse model.

Recall that in the table below, elements that are grayed out have lower coherence.

Sensing Matrix, [W/rad]

Sheila found two issues when modifying the H1ASC.txt filter file this morning:

 1. A change to an existing filer caused foton to freeze up

 2. Loading a change to a filter (which was turned off) onto h1asc caused lock loss

I suspect both issues were due to the fact that today was the first time the h1asc filterfile was being handled by the new version of foton (with the higher number of significant digits in the gain).

issue 1) We later found that the foton freeze up could not be reproduced, perhaps it was because the old format file was being read and modified? We'll see if this error appears in other systems.

issue 2) Since every gain was recalculated with the higher number of digits, perhaps loading all the filters glitched the system enough to cause lock loss? One suggestion is that if a filter file is being changed to the new format for the first time, we should only load all of  the filters on a Tuesday morning (or perhaps perform this full load on every model at that time).

It looks like the drives during ALS DIFF to ETMX are about a factor of 2.5 times larger than they were 2 years ago. 

Kyle, Chandra 

Chandra had freed a bird that had got itself stuck in the "sticky mat" used to trap insects at the X-mid earlier today.  Unfortunately, it flew into the VEA.  Following Keita's Thursday 1 O-clock'ish meeting, we followed up by opening all of the roll-up doors and, with the lights off, persuaded it to exit.  We had to "bump" the crane bridge a few times to encourage the bird to leave - which it eventually did.  (Don't get me wrong.  I'm all for recycling and liberating caught birds etc. but if she next finds a struggling beached whale along the X-arm access road - she's on her own!)

Link to full report: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20170417

Summary below (see full report for details):

• Percentage of time spent observing (95.5%+51.6%+63.4%)/3 = 70.2%
  • planned commissioning in addition to regular maintenance reduced this percentage
• Typical BNS range of around 65-70 Mpc, but degraded a bit by the end of the day on Wednesday (just under 60 Mpc)
• Relatively quiet 50 hz - 100 hz glitching is continuing (reported in previous DQ shift)
• A population of glitches around 25-50 hz appeared on Wednesday, witnessed by the ETMY OpLev? (similar glitches have been noticed before)
  • Also coincident with FEC overflows
  • OpLev damping is OFF.

Yesterday morning I did a few tests of misaligning the OMC and putting excitations on the alignment loops. (see LLO alogs 32885 and comment and 28979 ).  Depending on which method you use to estimate the normal RMS OMC alignment fluctuations, the OMC jitter noise is at least a factor of 2 below DARM or better.

• Misalignments of the OMC did not produce any reproducible noise in DARM without an excitation (first attachment).  The misalignments that I used are smaller than was recently used at LLO. 
• There are three ways (that I know of) to estimate how large the offset was compared to the normal RMS alignment fluctuations: using the in loop error signal, looking at the motion on the QPDs, and the method that Koji described in his alog where the coupling from an an excitation is increased until it the coupling becomes linear and much larger than the coupling due to the normal alignment fluctuations. 

• According to the QPDs and in loop error signals, my offsets were large enough compared to the RMS that we don't need to worry about this noise source. 
• The normal RMS fluctuations that I would estimate based on the change in the coupling of the excitation would be much larger, meaning that this test only assures us that this noise is below the level of DARM by the coupling increase factor.

You can see that the behavior of POS Y is different from the other loops, this is the only loop where my offset was large enough to measure coherence between the excitation and DARM, but it was a small change in the optical gain.  My excitations were not large enough to change the RMS seen on the QPDs (second attachment shows excitation sizes). Our OMC alignment loops are very slow, it takes 2-3 minutes for them to respond to a change in offset.

Some notes on what I think is implied in the LLO alogs:

When we are locked on DC readout the ratio of the optical gains for the misaligned/aligned OMC is the square root of what the ratio of transmitted powers would be if DARM were not locked on the DCPDs (thanks Keita): 

• If we misalign the OMC when we are not locked on DC readout, the ratio of the transmitted power misaligned over aligned is (1-A).
• The power on the OMC DCPDs is held constant by the DARM loop, so the DARM offset changes from L0(aligned) to L1 (misaligned) (P=alpha L0^2=alpha(1-A) L1^2)  This means L1=L0/sqrt(1-A)
• We can measure the ratio of the optical gain for the misaligned OMC/ aligned OMC (kappaC1/kappaC0=(1-A)L1/L0=sqrt(1-A))

My understanding of Koji's method for estimating the rms: (Delta theta is normal alignment fluctuations, dtheta is the excitation, and theta0 is the offset. )

1. Normal contribution to DARM noise is proportional to DeltaTheta^2 (should be smaller than DARM, gold is upper limit)
2. Contribution to DARM noise with excitation but no misalignment is proportional to dtheta^2+2dTheta*DeltaTheta (forest green curves in first attachment) (DARM will not be coherent with the excitation in this case)
3. Contribution to DARM noise with offset but no excitation 2*DeltaTheta*theta0 (should be small, fuchsia curves would be larger than gold reference otherwise)
4. excitation and offset- (2)+(3)+2theta0*dTheta (mint green curves) (DARM will be coherent with excitation if this term dominates over DeltaTheta*dTheta)

I think that what Koji is doing is taking the ratio of (4)/(2) (coupling increase in the table above) and estimating that that is the ratio of the offset/normal RMS. 

Spring enabled the EE shop to work on setting up power for the LEMIs, and I had a look at the new signals. The top plot in the figure shows that we can see Schumann Resonances quite well, up to quite close to 60 Hz. The bottom two plots show some transient signals that might interfere with a feed-forward system.

It looks like the signals are degraded by wind. I am not surprised because we see wind noise in buried seismometers. I think we would have this vibration problem even on a perfect flat because of the variation in Bernoulli’s forces associated with gusts. It may be that a LEMI signal is generated by the wind because of slight motions of the magnetometers in the earth’s huge DC magnetic field. We buried the LEMIs about 18 inches deep (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=29096). I think we might be able to mitigate the noise some by going much deeper.  Once we have the vault seismometer working, it would be a good project to test the wind vibration hypothesis by comparing the LEMI and seismic signals.

There also seem to be some transients, some long and some short, possibly self inflicted by our system. It would be good to look into which transients would be a problem, and for those, details such as whether they are correlated with time of day, the average time between transients, etc., in order to help determine their source.

Finally, I would like to get the full system calibrated by comparing to a battery powered fluxgate magnetometer.