00:32UTC
After relocking and a2l, Sheila cleared an ETMX bias diff and cleared for Observing.
TITLE: 08/04 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 5mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
H1 humming along. Sheila is doing some noise investigation on ETMX ESD.
TITLE: 08/04 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Most of the day was dedicated to PEM injections and noise hunting. H1 has been locked the entire time and for 22 hours total now. No issues.
LOG:
16:19 Richard to CER power cycling SEI chassis
16:23 Robert to EY PEM injections
16:24 Richard done
19:03 Robert done
20:06 Robert to EX PEM injections
21:25 Robert done, Sheila starting EX BSC cabling investigation
22:01 Sheila done
22:33 Kyle to MY
23:00 Kyle back
We received a GRB alert at 21:53 UTC. However, Sheila was doing some noise hunting at EX at the time. I let her know about the GRB and she stopped what she was doing. I went to Observing at 22:03 UTC, only to find out when Sheila returned that the EX ESD (whose SDF diffs we had to accept to return to Observing) was in a half-connected state. We dropped back out of Observing, reverted the settings, and returned to Observing at 22:09 UTC.
Note for next Operator/lockloss: The ETMx ESD bias will have an SDF diff. This should be ACCEPTED.
For this test, I ramped down the bias, drove the end station, turned off the ESD driver, and started disconnecting ESD cables. Travis took references, which are attached. It is interesting that we got a large noise peak around 60Hz when we had LL and UL disconnected, which went away when I disconnected LR.
After I disconnected LR, we got the GRB alert, I decided to leave the bias off (since it doesn't matter to the noise) and leave the ESD cables as is since I didn't want to risk unlocking the IFO by reconnecting them. I had thought that what I had been doing was probably not impacting the data quality in the half hour before the GRB alert, so that it would still be worth having people analyze the data. Now I see that I was causing large glitches during that time, so this probably isn't useful data.
I had intended not to turn back on the ESD driver in this state, but people in the control room weren't aware and turned it back on. This means that the bias was on although there was no signal sent to the quadrants. (Only the bias and UR cables were connected.) We decided not to leave it like this, so went out of observing to turn off the ESD driver again.
I went out again and disconnected UR (noise on the reference) but disconnecting the bias unlocked the interferometer. the cables I brought out weren't the right gender, so I wasn't able to terminate them.
model restarts logged for Thu 03/Aug/2017 No restarts reported
model restarts logged for Wed 02/Aug/2017
2017_08_02 14:28 h1alsex
2017_08_02 14:28 h1calex
2017_08_02 14:28 h1iopiscex
2017_08_02 14:28 h1iopsusb123
2017_08_02 14:28 h1iopsusex
2017_08_02 14:28 h1iopsusey
2017_08_02 14:28 h1iscex
2017_08_02 14:28 h1pemex
2017_08_02 14:28 h1susbs
2017_08_02 14:28 h1susetmx
2017_08_02 14:28 h1susetmxpi
2017_08_02 14:28 h1susetmy
2017_08_02 14:28 h1susetmypi
2017_08_02 14:28 h1susitmpi
2017_08_02 14:28 h1susitmx
2017_08_02 14:28 h1susitmy
2017_08_02 14:28 h1sustmsx
2017_08_02 14:28 h1sustmsy
2017_08_02 14:35 h1hpietmx
2017_08_02 14:35 h1iopiscex
2017_08_02 14:35 h1iopseiex
2017_08_02 14:35 h1isietmx
2017_08_02 14:36 h1alsex
2017_08_02 14:36 h1calex
2017_08_02 14:36 h1iscex
2017_08_02 14:36 h1pemex
2017_08_02 14:39 h1hpietmy
2017_08_02 14:39 h1iopiscey
2017_08_02 14:39 h1iopseiey
2017_08_02 14:39 h1iscey
2017_08_02 14:39 h1isietmy
2017_08_02 14:39 h1pemey
2017_08_02 14:40 h1alsey
2017_08_02 14:40 h1caley
Restart of all SUS Quad computers as part of noise investigation. Inadvertently restarted all EX and EY models.
model restarts logged for Tue 01/Aug/2017 - Mon 31/Jul/2017 No restarts reported
Attached are trends of the HPO laser head flow rates for the last 3 days. Nothing has changed since the last trends I posted on 8/1/2017; the reported flows are still holding steady, the reading from head 2 is still ragged as usual.
Robert is taking a lunch break from PEM injections while LLO is doing the same. Both LHO and LLO are back to Observing for ~1 hour.
Back to Commissioning at 20:07 UTC for more PEM injections.
If your dataviewer real-time session is showing an xmgr plot with the right margin being clipped [attachment 1], here is a work around to view the complete plot.
1. resize the xmgr window to the right to provide enough space for the plot to "grow into" [attachment 2]
2. in the dataviewer window, while the real time plot is still running, activate a second channel (it doesn't matter which one) [attachment 3]
3. finally, while the real time plot is still running, turn off the second channel. Your plot should now look correct [attachment 4]
Robert starting PEM injections.
The Pit and Yaw plots all within the +/- 10 urad spec. The Sum plot for SR3 shows step down during the past day. ITMx Sum is also showing a trend downwards, and BS Sum is trending upwards.
Everything looks normal except that step down in the SR3 oplev SUM. Looking at the DetChar summary page for the SR3 oplev, the step down corresponds with the beginning of an especially glitchy period for the laser (which also happened to be the 2nd such glitcy period of the day); up until this point the laser was decently quiet, with some small glitches. This laser is now top of the list for replacement. I am finishing up stability tweaks on a laser in the LSB optics lab and will swap it into SR3 as soon as it's ready.
TITLE: 08/04 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
Wind: 2mph Gusts, 1mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY: Locked for 14 hours. No issues.
TITLE: 08/04 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 52Mpc INCOMING OPERATOR: Travis SHIFT SUMMARY: Observing entire shift. No issues. LOG: 07:26 UTC Restarted nuc5 (bottom right SEI BLRMS had disappeared) 12:02 UTC GRB alert 14:39 UTC Bubba to mid X to look at chiller pump 14:52 UTC Bubba back
Have remained in observing. No issues.
TITLE: 08/04 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 4mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.07 μm/s
QUICK SUMMARY: No issues to report.
TITLE: 08/04 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Quiet, except for an earthquake
LOG:
23:30 Chandra to MY
0:30 Lockloss when I switched to an earthquake state during the EQ
4:00 A2L while LLO is down
The attached figure shows a cWB outlier that Brennan H. sent around to DetChar. It is compared to likely raven pecks discussed in this log: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=37630 The match is quite good (see figure), though, in this case, the peck did not produce a very loud sound. But the above log suggests that the coupling path for pecks is not through the air, but through the GN2 vent to the vacuum enclosure. While the sound for the cWB outlier was not that loud, the vibration of the enclosure was strong and sensed by the BSC10 accelerometers. The vacuum enclosure motion likely couples to DARM through the P-Cal periscope (see above log). It looks like there is a broader resonance in the vent/vacuum enclosure system, excited by ice-craving ravens, that overlaps with the 94 Hz resonance of the P-Cal periscope, that is strongly coupled to DARM through scattered light.
I suppose mentioning the previous lockloss would be in order. This occurred at 23:35UTC. It was a Sheila induced lockloss as she was manipulating ETMX ESD.