TITLE: 02/08 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:
LOG: Still going for 12 hours, at 67 Mpc.
All seems good. almost 9hours around 68Mpc.
TITLE: 02/08 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 8mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.38 μm/s
QUICK SUMMARY: Observing for 4 hours at 66Mpc. Roads clear on 240 and route 10, but a bit of snow in town.
TITLE: 02/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Observing for ~3 hours after relocking post-Maintenance Day and Sheila's OMC work. PI modes have been better behaved than my previous shift.
LOG: See previous aLogs.
In alog 33915 I used my images of the steering mirror under the thin film polarizers to identify possible clipping.
In alog 33986 I posted images of the clipping I found today.
This shift in the beam on the steering mirror would come about from a Nothward shift in the beam on the thin film polarizers, which would indicate an Eastward shift in the beampath of the EOM.
Here are images supporting the beam shift:
Attachment 1: images of the wedge in the EOM path shows the beam moved Eastward
Attachment 2: images of the steering mirror shows the beam moved Northward
Attachment 3: image of the iris down stream of the bottom periscope mirror shows the beam moved Southward
Attachment 4: Drawing that shows that all of these beam changes are consistent.
Both of our locks since today's maintence period have had large glitches at low frequency. In the first lock we also had a reappearance of the 1083Hz OMC length glitches (and the corresponding peak in our spectrum).
The OMC length feature coming back may be due to more low frqeuency motion of the interferometer because BRSY is not in use, https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=33978
I added a boost to the OMC length loop to keep it on resonance better, measurements attached. This seemed to help the 1083 Hz peak. I turned the boost off from 4:14 UTC to 4:21 UTC Feb 8th UTC
If we want to make this boost permanent we should rearrange filters in OMC-LSC_SERVO and update the OMC guardian. For now I have put it in OMC-LSC_I_SWSTAT FM3. Travis accepted this in SDF, and has gone back to observing. This data may be ususable because of the huge glitches.
Operators: If you have to relock later tonight, you can engage the boost for the OMC by turning on FM3 in OMC-LSC_I (you can find this under OMC> CONTROL> green button saying I in the center near the top).
We have had several (~6-8) instances tonight of the PSL FSS PZT oscillating and knocking the IMC out of lock. I have been toggling the Autolock on/off to fix it. I had the same issues last night while relocking.
J. Kissel I've gathered this week's effective bias voltage measurement which provides an alternative confirmation that the actuation strength of the electrostatic drive (ESD) systems is not varying significantly over time from the accumulation of charged particles. This is no longer an issue because of the regular sign flipping of the ~400 [V] of requested bias that we began in November of last year (see LHO aLOG 31929 for ETMY and LHO aLOG 31172). Attached are plots showing the effective bias voltage trend over the past year for each quadrant of control, as measured by the optical lever, in both pitch and yaw. The first is for ETMX, and the second for ETMY. One can see the marked change in effective bias voltage accumulation starting in November, as the trend turns over and becomes flat over the past few months. The last two plots re-cast this trend in terms of relative actuation strength of the ESD systems. One can see that the relative actuation strength change caused by the accumulation of charge remains small and static in time, at the level of a few percent. We can use this confirmed static angular actuation strength as a proxy to confirm that the longitudinal actuation strength remains static, as shown in LHO aLOG 24241. That means the actuation strength we use in our model of the interferometer's differential arm length control system when it was updated last in January (see LHO aLOG 33004) is still valid, and time-independent filters we used to calibrate the real-time output of the detector -- which are based on that model -- are accurate to within these limits. (Any remaining small time-dependent change has been corrected for in the almost-real-time, low-latency correction algorithm since the start of O2; see LHO aLOG 31732.
Sheila is working on OMC length dither while LLO is down.
Python standard environment work
Jim
HVAC networking between OSB and LSB
Carlos, Jim, Apollo
Installed a new HVAC unit on the network link between OSB and LSB
Remove timing status of DTS fanout from Beckhoff SDF
Dave
Modifed the ecatc1plc1 observe.snap to make IFO observation mode agnostic to DTS status.
Patch and reboot h1dmtlogin
Dave:
The debian 2FA authentication machine for DMT was patched. It had been running for 245 days, so it was rebooted. It came back quickly, indicating an FSCK completed quickly or was not ran.
Note to control room, the EPICS readback of H1 range goes to -1.0 when h1dmtlogin is rebooted, it acts as the proxy server for this GDS data.
Conlog channel lists
Patrick
Generation of the channel list for conlog was improved.
TITLE: 02/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 14mph Gusts, 11mph 5min avg
Primary useism: 0.21 μm/s
Secondary useism: 0.41 μm/s
QUICK SUMMARY: Just finishing up IA after Maintenance Day.
I modified the CDS overview to:
1. show the top level status of the Timing system, plus the associated information string
2. conlog has returned
Ops Shift Log: 02/07/2017, Day Shift 16:00 – 00:00 (08:00 - 16:00) Time - UTC (PT)
Jim sat cross legged looking through a 1.5" viewport for close to 5 hours attempting to move a few gram bar a few microns with no tactile knowledge that he was actually touching it. Back and forth, back and forth. Jim has successfully done this before; I never have. Krishna and Michael have done so many times. Finally we decided that at least in the current position it will drift into a useable place in a few weeks. It is a little hard to predict with all the thermal activity but historically, this is where we believe we are.
We, commissioners, may decide we need to speed this along with another intervention but with the fickleness of this we can make no promises.
As such, the normal WINDY configuration in SEI_CONF won't run. Operators should use WINDY_NOBRSY or VERY_WINDY_NOBRSXY. These should be fine while the microseism is ~.5 micron RMS. If the micrsoseism comes up, I'll come up with something else.
Cheryl, Kiwamu, Sheila
This morning Cheryl went into the PSL and saw that the rejected beam from the thin film polarizer after the rotation stage was hitting the edge of the steering mirror which sends it to a beam dump. (She has nice photos of this). This aftrernoon she, Kiwamu and I went into the PSL to fix this.
We first adjusted the position of the iris after the bottom periscope mirror, and added two steering mirrors, and iris and a beam dump to the path to the OSA so that we would have good alingment references for the beam leaving the table. We then turned the power down before the PMC, and using base plates as markers moved the entire TFP assembly 5 mm closer to HAM1. Kiwamu took some photos of the resulting beam position on the steering mirror which are on Cheryl's camera. The beam was then high on the beam dump apperature, so we changed the spacer in the beam dump mount for a thicker one. We turned the power back up, and checked the beam on the irises and the persicope PD.
Cheryl's photos from this morning suggested that there could be clipping on the output apperature of the EOM. We tried to determine if this was clipping or a back reflection, but can't say for sure. Now we are out of the PSL, the IMC relocked without problems, and Jeff B has started inital alingment.
Kiwamu's image of the beam nicely centered after he and Sheila moved the houseing for the Thin Film Polarizers and the steering mirror.
PyCBC analysts, Thomas Dent, Andrew Lundgren
Investigation of some unusual and loud CBC triggers led to identifying a new set of glitches which occur a few times a day, looking like one or two cycles of extremely high-frequency scattering arches in the strain channel. One very clear example is this omega scan (26th Jan) - see particularly LSC-REFL_A_LF_OUT_DQ and IMC-IM4_TRANS_YAW spectrograms for the scattering structure. (Hence the possible name SPINOSAURUS, for which try Googling.)
The cause is a really strong transient excitation at around 30Hz (aka 'thud') hitting the central station, seen in many accelerometer, seismometer, HEPI, ISI and SUS channels. We made some sound files from a selection of these channels :
PEM microphones, interestingly, don't pick up the disturbance in most cases - so probably it is coming through the ground.
Note that the OPLEV accelerometer shows ringing at ~60-something Hz.
Working hypothesis is that the thud is exciting some resonance/relative motion of the input optics which is causing light to be reflected off places where it shouldn't be ..
The frequency of the arches (~34 per second) would indicate that whatever is causing scattering has a motion frequency of about 17Hz (see eg https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=154054 as well as the omega scan above).
Maybe someone at the site could recognize what this is from listening to the .wav files?
A set of omega scans of similar events on 26th Jan (identified by thresholding on ISI-GND_STS_HAM2_Y) can be found at https://ldas-jobs.ligo-wa.caltech.edu/~tdent/wdq/isi_ham2/
Wow that is pretty loud, seems like it is even seen (though just barely) on seismometers clear out at EY with about the right propagation delay for air or ground propagation in this band (about 300 m/s). Like a small quake near the corner station or something really heavy, like the front loader, going over a big bump or setting its shovel down hard. Are other similar events during working hours and also seen at EY or EX?
It's hard to spot any pattern in the GPS times. As far as I have checked the disturbances are always much stronger in CS/LVEA than in end station (if seen at all in EX/EY ..).
More times can be found at https://ldas-jobs.ligo-wa.caltech.edu/~tdent/wdq/isi_ham2/jan23/ https://ldas-jobs.ligo-wa.caltech.edu/~tdent/wdq/isi_ham2/jan24/
Hveto investigations have uncovered a bunch more times - some are definitely not in working hours, eg https://ldas-jobs.ligo-wa.caltech.edu/~tjmassin/hveto/O2Ac-HPI-HAM2/scans/1169549195.98/ (02:46 local) https://ldas-jobs.ligo-wa.caltech.edu/~tjmassin/hveto/O2Ab-HPI-HAM2/scans/1168330222.84/ (00:10 local)
Here's a plot which may be helpful as to the times of disturbances in CS showing the great majority of occurrences on the 23rd, 26th-27th and early on 28th Jan (all times UTC). This ought to be correlated with local happenings.
The ISI-GND HAM2 channel also has loud triggers at times where there are no strain triggers as the ifo was not observing. The main times I see are approximately (UTC time)
Jan 22 : hours 13, 18 21-22
Jan 23 : hours 0-1, 20
Jan 24 : hours 0, 1, 3-6, 10, 18-23
Jan 25 : hours 21-22
Jan 26 : hours 17-19, 21-22
Jan 27 : hours 1-3, 5-6, 10, 15-17, 19, 21, 23
Jan 28 : hours 9-10
Jan 29 : hours 19-20
Jan 30 : hours 17, 19-20
Hmm. Maybe this shows a predominance of times around hour 19-20-21 UTC i.e. 11-12-13 PST. Lunchtime?? And what was special about the 24th and 27th ..
Is this maybe snow falling off the buildings? The temps started going above the teens on the 18th or so and started staying near freezing by the 24th. Fil reported seeing a chunk he thought could be ~200 lbs fall.
Ice Cracking On Roofs?
In addition to ice/snow falls mentioned by Jim, thought I'd mention audible bumps I heard from the Control Room during some snowy evenings a few weeks ago (alog33199)....Beverly Berger emailed me suggesting this could be ice cracking on the roof. We currently do not have tons of snow on the roofs, but there are some drifts which might be on the order of a 1' tall.
MSR Door Slams?
After hearing the audio files from Thomas' alog, I was sensitive to the noise this morning. Because of this, thought I'd note some times this morning when I heard a noise similar to Thomas' audio, and this noise was the door slamming when people were entering the MSR (Mass Storage Room adjacent to the Control Room & there were a pile of boxes which the door would hit when opened...I have since slid them out of the way). Realize this isn't as big of a force as what Robert mentions or the snow falls, but just thought I'd note some times when they were in/out of the room this morning:
I took a brief look at the times in Corey's previous 'bumps in the night' report, I think I managed to deduce correctly that it refers to UTC times on Jan 13. Out of these I could only find glitches corresponding to the times 5:32:50 and 6:09:14. There were also some loud triggers in the ISI-GND HAM2 channel on Jan 13, but only one corresponded in time with Corey's bumps: 1168320724 (05:31:46).
The 6:09 glitch seems to be a false alarm, a very loud blip glitch at 06:09:10 (see https://ldas-jobs.ligo-wa.caltech.edu/~tdent/wdq/H1_1168322968/) with very little visible in aux channels. The glitch would be visible on the control room glitchgram and/or range plot but is not associated with PEM-CS_SEIS or ISI-GND HAM2 disturbances.
The 5:32:50 glitch was identified as a 'PSL glitch' some time ago - however, it also appears to be a spinosaurus! So, a loud enough spinosaurus will also appear in the PSL.
Evidence : Very loud in PEM-CS_SEIS_LVEA_VERTEX channels (https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=155306) and characteristic sail shape in IMC-IM4 (https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=155301).
The DetChar SEI/Ground BLRMS Y summary page tab has a good witness channel, see the 'HAM2' trace in this plot for the 13th - ie if you want to know 'was it a spinosaurus' check for a spike in HAM2.
Here is another weird-audio-band-disturbance-in-CS event (or series of events!) from Jan 24th ~17:00 UTC :
https://ldas-jobs.ligo-wa.caltech.edu/~tdent/detchar/o2/PEM-CS_ACC_LVEAFLOOR_HAM1_Z-1169312457.wav
Could be someone walking up to a piece of the instrument, dropping or shifting some heavy object then going away .. ??
Omega scan: https://ldas-jobs.ligo-wa.caltech.edu/~tdent/wdq/psl_iss/1169312457.3/
The time mentioned in the last entry turns out to have been a scheduled Tuesday maintenance where people were indeed in the LVEA doing work (and the ifo was not observing, though locked).