FAMIS#7416
Laser Status:
SysStat is good
Front End Power is 34.36W (should be around 30 W)
Front End Watch is GREEN
HPO Watch is GREEN
PMC:
It has been locked 0.0 days, 0.0 hr 6.0 minutes (should be days/weeks)
Reflected power is 14.17Watts and PowerSum = 75.1Watts.
FSS:
It has been locked for 0.0 days 0.0 hr and 6.0 min (should be days/weeks)
TPD[V] = 2.18V (min 0.9V)
ISS:
The diffracted power is around 3.314% (should be 5-9%)
Last saturation event was 0.0 days 0.0 hours and 6.0 minutes ago (should be days/weeks)
Possible Issues:
PMC reflected power is high
wiki: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20161208 Below I summarise the main highlights of this shift: duty cycle 65.2%, the range is 70 - 75Mpc. on Thursday 8th lockloss due to multiple earthquakes keeping occuring to morning on Friday Software saturation - H1:LSC-X_ARM_CTRL [1] at ~11:00UTC on Thursday 8th 18kHz PI modes strong peak at 11:07UTC and 12:10UTC on Thursday 8th, at ~8:00UTC, ~ 9:00UTC, ~ 10:30UTC and at ~12:30 on Friday 9th. the planned stochastic injection at 00:10UTC Thursday 8th quiet on Saturday 10th and Sunday 11th
The PSL Enclosure phone has been switched off. A reminder that it needs to be re-enabled when work is being done in the Laser Area Enclosure. The power supply for it is in Rm 163.
TITLE: 12/13 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 73.1393Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:
Operator-less for the first 90min, but rest of the shift saw me here watching a nice performing H1 on a quiet Earth.
LOG:
Ops Shift Transition:12/13/2016, Day Shift 16:00 – 00:00 (08:00 - 16:00) - UTC (PT)
Andy, Tom Dent, Josh Nutsinee (alog 32159) and Patrick (alog 32163) both reported a string of glitches during their shifts on Dec 4th. These showed up again in connection with an investigation into some PyCBC loudest events. At Tom's suggestion, we listened to the PSL microphone, which is one of many PEM channels seeing a huge disturbance at these times. I've attached the wav file of the PSL center mic. It seems like the PSL intercom (or some other phone) rings twice and afterwards forwards the call somewhere else. You can hear a faint third ring, and Josh has another file where talking can be heard after the faint ring. When this happened at LLO during an ER, (L1 alog 8451 the intercom would answer and then make a busy signal. It's not clear why we haven't seen this more often, or when the intercom could have gotten connected. This is in the middle of a long stretch of science mode. Edit: To be clear, the loud rings make something very strong in DARM. We're investigating to what extent the quieter stuff shows up.
Here's a spectrogram of the PSL Mic annotated. The second set of more distant rings followed by auto answer starts around second 19. Also attached is the STRAIN spectrogram. The coupling to STRAIN is clear for the PSL rings and it looks like there is faintly also the second set of rings seen. Also attached is the longer Wav file with the speakerphone and talking for the first call and the rings of the second call a minute later.
Opend FRS Ticket 6923
Both PSL Phones have been disabled, see LHO aLOG 32508. FRS Ticket 6923 closed. Tagging other relevant subsystems to envoke L-Mail.
Have had a decent night tonight. However at around 12:30utc noticed H1 range taking a noticeable dip from 70Mpc down to 62Mpc. All of this happened within an hour time frame (appears to be coming back up near 70Mpc. There is nothing obvious in the BLRMS seismic traces (well, for high freq the Corner Station seismometer there is a bump which sort of lines up...but the corner station has many of these bumps and the other ones don't drop the range.) Anyway, it was a curiousity.
There was a small EQ around this time, but it was after the fact and fairly quick.
Overall the H1 range tends to show very slow oscillations in range values and one would think it was useism, but they also don't match up. I'm just curious about why our range fluctuates on a slow time scale like this & how it's curious it doesn't match seismic (L1's range appears to follow seismic more obviously...atleast from my glances at their range and seismic screenshots.)
Attached is a look at the last 12 hrs for the H1 range & also the 3-10Hz & 10-30Hz seismic bands. It's looks like the range drop mentioned above corresponds with the bump seen on both seismic bands. I'd like to know what this could be.
It's interesting that other "bumps don't have noticeable effects on H1 range. So I'm guessing it's a specific line we're sensitive to, and I'm curious what it could be.
See the DQ shift aLog where we report
The excess noise appears to extend up to about 100 Hz and can easily cause the range drop. Today's example of an h(t) spectrogram is attached.
Noticed L1 dropping out of lock at around 13:42 & around this time noticed elevated noise on our EQ BLRMS signal (also notice it on LLO EQ band screenshots). Nothing observed on Terramon or USGS website (and other websites). I did notice a 4.4 in Baja California here: http://www.emsc-csem.org/Earthquake/earthquake.php?id=552372
Noticed Terramon finally reported this earthquake. But it must have been 1-2hrs after we saw it on our seismometers.
Since the start of O2, we have had some pesky dropouts of OBSERVING due to SDF channel changes for some ALS channels from a Beckhoff computer at each of our End Stations (sysecatx1plc2 & sysecaty1plc2). Below, I wanted to list each of the occassions, the amount of time we were out of Science mode, channels involved, and their current state.
Should UNMONITOR (3) ALS-Y Channels
Above we can see all of the channels we noticed/caught/UNMONITORED. I would suggest we take the preemptive action of UNMONITORING (if not already done so) the following channels for sysecaty1plc2 next time we are out of OBSERVING:
Done.
Filed an FRS for this (#6932). I CLOSED it, but there is always the possibility that rogue channels which haven't been addressed can drop us out in the future.
TITLE: 12/13 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 72.9978Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
Wind: 10mph Gusts, 8mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.15 μm/s
QUICK SUMMARY:
8:11-9:30UTC (12:11-01:30amPST): No Operator Coverage (Due to Winter Weather this week, I'll be taking the OWL shift for next 3 nights.)
Arrived to an H1 in OBSERVING & a quick scan looks like we have optimal conditions (range is at 70Mpc). Glancing at range over last 12hrs, range has 8hr period of going up to 75Mpc & down to 70Mpc(now) & I don't see anything seismically which matches that (useism has had a constant trend down over the last 24+hrs). There are also a few more glitches (i.e. drops in range) for this lock.
Low Useism: Seismically, we appear to be a tad under the 50percentile for useim (a comparison personal note between 90+percentile over the weekend & now is that the Tidal striptool is virtually flat vs over the weekend you would definitely see useism waves/oscillations at 90+%).
Violin Modes: Fundamental(~500Hz) looks to be just above 1e-19 on DARM. Second Harmonic (~1kHz) is just above 1e-15, this is the only notable feature on the "H1Glitches(DMT Omega)" tool on nuc0 (perhaps this is something which could be damped at an opportune time [Maintenance Day?]).
Talked with Fyffe @LLO to inform they are no longer flying solo.
Weather Conditions: No precipitation & cloudy.
Road Conditions: (driving in via Twin Bridges) Other than my driveway at home & driveway on-site, the roads were dry and clear (able to easily drive speed limit); made it to site in the standard 20-25min. I did come across a heard of deer right near the bridges.
TITLE: 12/13 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC STATE of H1: Observing at 70.922Mpc INCOMING OPERATOR: None SHIFT SUMMARY: Locked for over 10 hours. Only out of observing to run a2l. Two GRB alerts. There will not be an owl shift operator due to inclement weather. I will leave the IFO in observing unattended. I have allowed remote access for the users that Keita requested. LOG: 21:44 UTC At NLN. Had to set LOCKLOSS_SHUTTER_CHECK node request to HIGH_ARM_POWER in order to go to observing. Have 'TCS_HWS: HWSY Code Stopped Running' diag message. 21:55 UTC Observing 22:13 UTC Out of observing to run a2l. '/opt/rtcds/userapps/release/isc/common/scripts/decoup/a2l_min_LHO.py' 22:19 UTC Observing 23:00 UTC Changed phase for PI mode 26 23:27 UTC Requested INJECT_KILL for the INJ_TRANS guardian 00:35 UTC Requested INJECT_SUCCESS for the INJ_TRANS guardian 01:50 UTC Changed sign of gain for PI mode 28 07:05 UTC GRB alert. LLO not locked.
Nutsinee has requested that someone reload the DIAG_MAIN guardian if the IFO loses lock we go out of observing. (see whiteboard)
Have remained locked at NLN since 21:44 UTC. Stood down for a GRB at 23:20 UTC. It appeared that the injections were not automatically blocked for the GRB, so I set the INJ_TRANS guardian node to INJECT_KILL manually. Requested INJECT_SUCCESS at 00:35 UTC. Damped PI modes 26 and 28. Ran a2l near beginning of lock.
About the GRB, it turns out that the guardian was doing the right thing.
The alert was received at 2016-12-12 23:20:22 UTC, but the actual GRB event was at 2016-12-12 15:38:59, hours before the alert.
Since the alert came after our standard window of one hour, the guardian didn't block the injeciton.
We just got another GRB alert at 07:05 UTC. This time the event time is around the same time as the created time. The INJ_TRANS guardian did not change again. Perhaps this is because LLO is not locked?
I and Patrick looked at the trend of H1:GRD-INJ_TRANS_STATE_N, and actually GRB made the guardian transition to state 30 (EXTTRIG_ALERT_ACTIVE) for an hour (attached).
The GRB event is this one: https://gracedb.ligo.org/events/view/E265603
The "2nd phone" heard in the audio recording from DetChar is the phone in the PSL enclosure anteroom. It is important to note that there is no call forwarding involved, both phones always ring if you call the PSL enclosure extension. The anteroom phone always lags behind the laser room phone though, which is why it appears to be forwarding the call. It sounds so faint because of the acoustic damping of the laser room (these phones are quite loud). Switching off the PSL enclosure phone turns off both the laser room and anteroom phones. This was tested this morning, as we can hear the anteroom phone from outside of the PSL enclosure; when the enclosure extension was called, no ringing was heard. To my knowledge neither of the PSL enclosure phones have the capability to auto-answer, they will continue to ring until physically answered or the caller hangs up.