TITLE: 01/06 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 119Mpc
INCOMING OPERATOR: Camilla
SHIFT SUMMARY:
Quiet shift. Quick OBSERVING drop due to connection issue to a Slow Control computer at EX. Microseism has taken a small step up during the shift.
LOG:
Laser Status:
Front End Power is 32.26W (should be around 30 W)
70W Output Power is 70.5W
Front End Watch is GREEN
70W Watch is GREEN
PMC:
It has been locked 4 days, 12 hr 34 minutes (should be days/weeks)
Reflected power = 11.64Watts
Transmitted power = 51.83Watts
PowerSum = 63.47Watts.
FSS:
It has been locked for 0 days 14 hr and 39 min (should be days/weeks)
TPD[V] = 5.415V (min 0.9V)
ISS:
The diffracted power is around 2.4%
Last saturation event was 0 days 14 hours and 39 minutes ago (should be days/weeks)
Possible Issues:
None.
At 2:27:09, H1 dropped out of OBSERVING. Looking at the ISC_LOCK log, it appears we had a connection error in Beckhoff/Slow Controls land (for h1ecatx1 specifically). Connection was re-established 2-seconds later.
2:27:38 Went back to OBSERVING.
Below is the log for ISC_LOCK showing the connection error:
2020-01-05_17:30:35.886414Z ISC_LOCK [NOMINAL_LOW_NOISE.main] ezca: H1:ASC-ADS_YAW5_DOF => ON: LIMIT
2020-01-06_02:27:09.449357Z CA.Client.Exception...............................................
2020-01-06_02:27:09.449357Z Warning: "Virtual circuit unresponsive"
2020-01-06_02:27:09.449357Z Context: "h1ecatx1.cds.ligo-wa.caltech.edu:5064"
2020-01-06_02:27:09.449357Z Source File: ../tcpiiu.cpp line 947
2020-01-06_02:27:09.449357Z Current Time: Sun Jan 05 2020 18:27:09.448494623
2020-01-06_02:27:09.449357Z ..................................................................
2020-01-06_02:27:09.514405Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: CONNECTION ERRORS. see SPM DIFFS for dead channels
2020-01-06_02:27:09.568101Z ISC_LOCK EZCA CONNECTION ERROR. attempting to reestablish...
2020-01-06_02:27:09.568760Z ISC_LOCK CERROR: State method raised an EzcaConnectionError exception.
2020-01-06_02:27:09.568760Z ISC_LOCK CERROR: Current state method will be rerun until the connection error clears.
2020-01-06_02:27:09.568760Z ISC_LOCK CERROR: If CERROR does not clear, try setting OP:STOP to kill worker, followed by OP:EXEC to resume.
2020-01-06_02:27:11.145579Z ISC_LOCK [NOMINAL_LOW_NOISE.run] USERMSG 0: IMC_LOCK: has notification
2020-01-06_02:27:11.193648Z ISC_LOCK connections reestablished
Summary: correlations, noise estimates, and movies suggest that some scattering noise seen at LHO and LLO is due to micron-scale relative motion of test and reaction masses. The maximum frequency is increased by multiple reflections, possibly between the ESD traces on the RM and the HR coating on the ETM face. Driving R0 to reduce this relative motion, and/or offloading to ISI or HEPI, may mitigate the scattering noise.
Timesh, Matthew, Adrian, Jenne, Anamaria, Robert
At LHO we are noticing more scattering shelves in DARM with the seasonal increase in the microseism. The noise reaches nearly 100 Hz, several hundred times higher in frequency than the 0.15 Hz seismic motion produced by counter-propagating ocean waves. This requires high velocities of the reflector relative to the cavity and multiple strong reflections, but I think it can be accounted for by standard scattering mechanisms.
The relative velocity of the test and reaction masses is correlated with scattering arches and can account for their frequency spacing
The relative motion between test and reaction masses is not measured, but, at low frequencies, it should be similar to the relative motion of the penultimate masses, L2 and R2, measured by BOSEMs. Figure 1 shows that the relative velocity of the EX PUMs during high microseism reached about 5 microns per second, fast enough to produce the concurrent ~10 Hz gap between scattering arches. This large velocity is associated with the DARM and tidal offloading signals sent to L1 and L2. Figure 1 also shows that the ETMX L2 length witness signal correlates in time and amplitude with the scattering arches in DARM. DetChar scattering tools, and DetChar members have also identified this and similar channels as correlated with scattering arches, e.g. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=53887 and https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=46057
Movies of test masses during lock show light amplitude modulation correlated with relative motion of test and reaction chains
Light modulation is evident in movies of H1 ETMX and ETMY in lock, suggesting that nearby moving reflectors are reflecting/scattering a lot of light into the test mass. To better understand the motion that produces the visible modulation, I took the difference between the pixel values in successive frames of several movies and calculated the standard deviation of the differences in pixel values to provide a single number indicating the degree of frame-to-frame variation. Figure 2 shows that the light variation in a movie of ETMY is correlated with the slope of the local ETMY L2 length witness, but not with the L2 length witness of ETMX. This supports the argument that the motion between the chains is modulating light so much that it is visible. I posted the movie of ETMY used in Figure 2, sped up by a factor of ten so that the light modulation would be more obvious (https://youtu.be/WkNR89ItXF8 ). The correlation in Figure 2 is for the central region of this movie, but the variation was similar in the 4 close-ups that I examined. Frame analyses of other movies supported this conclusion. I also made movies during 0.1 Hz injections at R0, and spectra of the changes in the movie frames showed a strong peak at 0.2 Hz.
Multiple reflections rather than harmonics
Figures 1 & 2 show that scattering arches are stacked evenly in frequency. Two mechanisms can account for this equal spacing, first, multiple reflections, and second, harmonics of a modulation frequency. These can be distinguished by whether or not the spacing changes as the amplitude of motion changes (https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=31898 ). If the spacing is associated with harmonics of the modulation frequency, then the spacing of the arches doesn’t change as the amplitude of the motion changes. In Figure 1 and in 0.1 Hz ISI injections that I made, the spacing of the arches gets smaller as the amplitude decreases, consistent with the multiple reflection hypothesis and not the harmonic series hypothesis.
The higher-frequency arches from multiple reflections would have relatively smaller amplitudes because of losses at each reflection. Figure 3 shows that each successive shelf in DARM during high microseism has roughly 0.3 of the amplitude of the preceding lower frequency shelf. This suggests a power factor of roughly 0.1 per reflection, more like partial specular reflection than a more lossy path that requires scattering with each cycle, such as scattering from a beam spot to a shiny metal surface and back.
Reflections from the ESD traces can roughly account for the scattering noise and may also provide a multi-reflection mechanism
Hiro’s estimate of scattering noise from the ESD traces (https://dcc.ligo.org/LIGO-T1500455) assumed much smaller relative motion between the cavity and the reaction mass. An updated estimate using the measured motion suggests that the noise is visible or nearly visible in DARM. In addition, photographs in Figure 4, suggest that there is a lot of additional scattered light at the radius of the ESD traces that may end up scattering into the TEM00 mode.
A possible multi-reflection path that could increase the maximum frequency due to ETM-RM relative motion by a factor of several would be multiple reflections between the ESD traces and the HR coating on the front of the test mass. I think a 0.1 power factor per cycle is not unreasonable for this HR-ESD optical path.
There are four alternative paths that I considered that don’t work as well: back and forth between the TM and its cage, the TM and the TMS, the TM and the ACB, or the TM and chamber walls. These other paths would likely have more losses with each reflection then the proposed TM-RM path. In addition, the arch spacing would not fit the witnessed velocity as well as the reaction mass path does because the test mass moves half as much relative to these alternate reflectors (offloading low frequency DARM at L1 and L2 moves the main and reaction chains roughly equal amounts in opposite directions). These other paths may nevertheless produce noise (reaching half the frequency) that doesn’t currently dominate.
Possible mitigation
Driving at R0 in order to minimize the relative motion of the two chains would mitigate noise from the test mass - reaction mass path. Jenne suggested offloading to the ISI or HEPI, which could also mitigate noise from the cage, ACB and the TMS path. I think Jenne, Sheila, Jeff and others are starting to think about this.
Some noise at LLO may have a similar source
While the DARM offload system is different at LLO, at least some of the noise associated with the microseism appears to have a similar source as the noise at LHO. Figure 5 shows that the relative motion of the test and reaction chains predicts the scattering arch spacing and is correlated with the appearance of shelves in DARM.
Because of the non-linear nature of scattered light noise, this low frequency motion may also increase scattering noise from higher frequency motion, even when the scattering arches from the ~0.1 Hz motion are not visible, and mitigation may thus help with, e.g., anthropogenic-band scattering noise. Finally, it might be worth looking into using the TM-RM velocities to improve past data.
Movies of light modulation at the test masses, with illuminated stills for orientation:
ETMY side view used in frame analysis discussed above: https://youtu.be/WkNR89ItXF8
ETMY 45 degree view: https://youtu.be/JghBSjQ2xV4
ETMX 45 degree view: https://youtu.be/EHyjzE8XIXM
TITLE: 01/06 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 119Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 14mph Gusts, 10mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.44 μm/s
Microseism is the lowest I've seen in my stint of the last 7-days (but still squarely between the 50th-90th precentile). Looks like we just had some winds, but they are now hovering at 10mph and below (but EY is moving a round currently).
QUICK SUMMARY:
Almost 7hrs of lock for H1. SEI_CONF is at WINDY & SEI_DIFF is at FULL_DIFF_CPS. BNS range is holding at roughly 119Mpc.
TITLE: 01/05 Day Shift 16:00 – 00:00 (08:00-16:00), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Lost lock early during shift, reached NLN after one lockloss and a little intervention.
LOG:
16:09 (08:09) Sudden lockloss, unsure of the cause
17:30 (09:30) At NLN, entering Observing
Ops Shift Transition: 01/05/2020, Day Shift 16:00–00:00 (08:00-16:00) - UTC (PT)
State of H1: Locked
Intent Bit: Observing
Weather: 5-15 mph wind
Primary 0.03 – 0.1Hz: 0.01 um/s
Secondary 0.1 – 0.3Hz: 0.2 um/s
Outgoing Operator: Jeff
Quick Summary: Locked 38 hours, Observing for 17.5 hours. Microseism declining.
All is well. The range is 121.0Mpc, the wind is down and microseism is coming down. No problems or concerns to report.
TITLE: 01/05 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 120Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:
Nice quiet shift (minus the Mexico rumbler) with our lock just passing the 30hr mark. Winds have cooperated with us and we have a nice flat ~120Mpc range for the last ~11hrs.
LOG:
H1's been locked 26+hrs & has a range hovering around 120Mpc. Winds are under 20mph which is nice. DMT Omega & DARMblrms are showing a glitchy 20-35Hz.
TITLE: 01/05 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 122Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 13mph Gusts, 10mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.45 μm/s
Winds have died down over the last hour. Microseism is around/just below the 90th percentile.
QUICK SUMMARY:
H1's been locked 22.5+hrs.
There's no road access to MX on X1. And X2 to EX probably looks worse! Sorry, Chris & Tyler (seems like the #Tumlbegeddon tumbleweeds have finally been freed up from SR 240 and taken residence on our X-arm road! (see Jeff B's photos).
And now that we are 24hrs into our better sensitivity-H1, it's looking like whenever we get sustained winds around the 20mph range, we'll see that in our range. (but should also note we have the fairly high microseism, too). So just hope for less wind!
Sorry to ignore Y-arm, but it appears to be much better with no real change from Wed. It's dark now, but from what I can see, you can drive down most of Y1 to MY. Then immediately after MY there's a multi-car length tumbleweed pile blocking the road (this pile looks a like it's grown a little since Wed). Then looking from EY's camera in the dark, I see fairly clear road access on Y2 (on Wed there were two more multi-length tumbleweed piles).
Attached is a sunset photo I took from the roof. If one zooms in, one might see a few tumbleweed piles on Y1, but otherwise it's fairly clear.
Summary: Y-arm has a couple of blockages, which would require a little bit of time, but X-arm is almost entirely blocked the length of the 4km & is worse than it looked on Wed!
TITLE: 01/04 Day Shift 16:00 – 00:00 (08:00-16:00), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Quiet shift, high microseism/wind reducing range, causing 20-34 Hz glitches. Locked 22 hours, Observing 1.5 hours.
LOG:
16:33 (08:33) Out of Observing briefly after switching SEI_DIFF to CORNER_DIFF_CPS (was not supposed to take us out)
16:34 (08:34) Back in Observing
22:36 (14:36) Out of Observing briefly after switching SEI_DIFF to FULL_DIFF_CPS
22:38 (14:38) Back in Observing
In order to bring SEI_DIFF to the FULL_DIFF_CPS state without knocking us out of Observing, I am unmonitoring the following channels from SEIPROC:
Unmonitoring H1:ISI-DIFF_BS_CPS_X_GAIN after switching SEI_DIFF from FULL_DIFF_CPS to CORNER_DIFF_CPS casued an sdf change in that channel that knocked us out of Observing.
Ops Shift Transition: 01/04/2020, Day Shift 16:00–00:00 (08:00-16:00) - UTC (PT)
State of H1: Locked
Intent Bit: Observing
Weather: 10-20 mph wind
Primary 0.03 – 0.1Hz: 0.01 um/s
Secondary 0.1 – 0.3Hz: 0.3 um/s
Outgoing Operator: Jeff
Quick Summary: Locked 14 hours, Observing for 8 hours. Wind is dying down.
The word for this morning is wind. The base winds are in the high 20 to low 30s, with several gusts topping 60mph. The building is groaning and creaking with each gust. The range which recovered from the Evening shift dip, came back up to the 118-120Mpc range until the wind picked up. It was down in the 70Mpc range for a while. Right now it is around 106Mpc. Switch off the ISI_DIFF, which appears to have helped with the low frequency glitches a bit. Was thinking about switching the SEI_CONF to VERY_WINDY_NOBRSXY or MORE_WINDY, but was worried about this breaking lock (Nom vs EQ SE Outputs showing mostly red). Since the lock is holding and the wind has fewer high speed gusts, will hold off on this for now. As one might expect, the tumbleweeds have been a tumbling across the site! Most of yesterday's X-Arm de-tumbleweeding has been re-tumblweeded.