TITLE: 03/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY:

Fairly quiet day. a2l was run once. It need to be run again at next opportunity. Some NOISEMON injections were run by Evan and Miriam while Livingston was down. A flurry of small earthquakes late in te shift posed no real threat to our lock. Handing off to TJ
LOG:

15:08 H1 out of Observing for Richard to measure TCS table

15:13 Observing

16:36 Karen driving to VPW

19:24 running a2l

19:25 Miriam wants to run NOISEMON injections for test as per WP#6545

19:45 Betsy and Travis to MY

20:47 KingSoft here to check RO. He knows about Observation protocol for onsite driving.

20:56 Betsy and Travis back

22:45 Big glitch in BNS range (didn't catch it in DARM). h(t) shows glitch as fairly broadband

I have turned off the instrument air compressors at Mid Y. These will remain off until needed, (same as Mid X) but in a stand-by mode.

22:31UTC INJ_TRANS guardian doing it's thing.

Travis left just before the alert to drop some boxes at a Mid station and the balers headed in the direction of Y arm yet they may be by the H2 building. ( I can't find them on the camera)

[Jeff Kissel, Aaron Viets]

Recent issues with the calibration lines and kappa calculations have raised questions about how the h(t)-ok bit is affected by the kappas (see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=35184 ).

For CALIB_STATE_VECTOR documentation, see https://wiki.ligo.org/viewauth/Calibration/TDCalibReview#CALIB_STATE_VECTOR_definitions_during_ER10_47O2.

For each kappa, there is a "median-ok" bit and a "smooth-ok" bit. The "median-ok" bit tells whether the kappas are being gated due to bad coherence (thus "corrupting" the median with previously measured values). The "smooth-ok" bit tells whether the kappa values are in an expected range (1.0 +- 0.2). Since the coherence was bad, but the gating worked during the time documented in the aforementioned aLOG, the median-ok bit was off and the smooth-ok bit was still on. When we apply the kappas, h(t) OK depends on the smooth-ok bits and not on the median-ok bits, so it was unaffected by this. If, on the other hand, we do not apply the kappas, the kappa bits do not affect the h(t) OK bit.

The above description has been the case since the start of ER10, with the exception of one slight change:
On 2016-11-29 Tuesday maintenance (near the start of O2), the smooth-ok bits were generalized further to also mark bad any time when the kappas are equal to their default values (indicating they have not yet been computed by the pipeline). This scenario is only expected to possibly occur at the start of the first lock stretch following a restart of the pipeline. The purpose of this change was to insure that "h(t)-ok" implies "kappas-applied quality" when we are, in fact, applying the kappas. For documentation on this change, see:
https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=29947
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31926

Eric Quintero, Rana

Summary:

Studying coherences between the ground and the LSC drives, we find that we can reduce the longitudinal forces to the mirrors in the 0.1-0.3 Hz band by a factor of ~2-5 in most cases, for both sites.

Details:

The recent success of the length to angle (L2A) feedforward at LLO led us to wonder about the source of so much low frequency motion. The SEI loop feedback and feedforward has been heavily tuned over the years to reduce much of the motion. By looking at the coherence and transfer function between the ground seismometers and the LSC*OUT signals (in a similar manner to what we did with the length to angle in May 2016), we are able to make an upper limit estimate on how much this can be reduced by implementing a global FF (just as we did in early 2010 for the S6 run using HEPI/PEPi).

We took 1 hour of data from 1000 UTC on March 12. The RMS of the ground motion in the 0.1-0.3 Hz band was 0.5 um/s, which is high, but only moderately high for the winter time. The summer time motion is more like 0.1 um/s.

The attached plots show:

upper plot: LSC control signal & LSC control signal after ideal subtraction

lower plot: top 5 signals used in the subtraction (in practice, using ~3 signals is enough to do the biggest part of the subtraction)

This subtraction is done on a bin-by-bin basis in the frequency domain, and as such, its a best case estimate. In reality, implementing a causal filter which avoids injecting too much noise at 3-20 Hz will degrade the subtraction performance somewhat. We are now working on making a frequency dependent weighting so as to make realizable filters.

In the attached channel list, you can see that all ground seismometers and tiltmeters were used.

1. In some cases, the tiltmeters do seem to be useful for doing this FF, although it remains to be seen if their noise at > 3 Hz is too high to preclude using them.
2. As we also see for LLO, much of the motion is coming in through the Z direction. This implies that the vertical to horizontal coupling in the ISI (perhaps due to imbalances in the sensor calibrations?) is the culprit. In any case, we can fix it by FF just to improve the performance of the interferometer in the near term and then address the root cause at a later time.
3. These LSC_OUT signals are just the control signals at the output of the LSC sub-system, but they are not really equivalent to force or displacement, since the filters inside the suspensions distribute the signals among the upper suspension stages with different filter shapes and crossovers: the suspensions do not 'look' like a simple pendulum from the LSC side. Some complicated suspension model + digital filter forensics should be able to convert these plots into physical units so we could figure out how much the motion reduction would really be, but I expect that the bulk of the relative motion between the mirrors and chambers comes from 0.1-0.3 Hz, as does the angular motion that the WFS loops have to deal with. It would be very handy if there was a matlab function that could read in a simplified suspension model and the digital filters / gains for a specified GPS time and return the calibration to go from LSC counts to meters.
4. We will need to do some minor model changes to be able to bring the seismo signals into the LVEA at 2 kHz and then to send out the ~10 Hz BW signals to the various ISIs. There's some discussion between Joe B. and Jenne to clarify precisely what and how many changes.
5. For LHO only, I've also used the BRS channels: H1:ISI-GND_BRS_ETMX_RY_OUT_DQ & H1:ISI-GND_BRS_ETMY_RX_OUT_DQ, which look like they are the right ones. But, it seems that they do not contribute to any significant subtraction during this period. IF they were already being used at this time, then perhaps that just means that their FF filters are already well tuned.

Evan, Miriam,

We continued the blip-like injections as in aLog 35116. This time we could inject a few different shapes.

In the first set we injected a sine-gaussian with frequency 200 Hz. Again we started quiet, only times with * can be seen in DARM:

1174937465

1174937493

1174937520

1174937554 *

1174937649

1174937693 *

1174937758 *

1174937786 *

1174937836 *

In the second set we injected one of the blip glitches that showed a strong residual after the subtraction of the ETMY L2 MASTER signal from the NOISEMON (see aLog 34694). Since we are injecting in the DRIVEALIGN, we took the shape of the blip in that channel and injected that. Times (all can be seen in DARM, they should have three different SNRs):

1174937920 *

1174937956 *

1174938062 *

1174938144 *

1174938198 *

1174938231 *

In the final set, we injected a filtered step function that was sent to us by Andy. The first time was too quiet and did not show up in DARM, the second shows up quietly, and the third was fairly loud:

1174938333.5

1174938365.5 *

1174938397.5 *

Right after injecting the last one, the spectrum was showing some mid frequency (100 - 300 Hz) noise, which can be seen together with the injection in this omega scan. We did not believe this noise was originated by our injection, and we saw similar noise about half an hour later when we were back in observing mode, but we will try to inject it again at another opportunistic time just as a sanity check (L1 came back up after our last injection so we didn't want to take any more time).

NOTE: same as with the set of injections mentioned in the aLog pointed above, and as pointed also in aLog 35223 (first comment), these injections were performed while L1 was down and with H1 in comissioning mode. This means that none of these injections happened in coincident time, and that they are not included in analysis ready segments (as can be seen, for instance, in the summary pages).

19:21UTC

HAM 6 pressure spiked at around 23:00 UTC time on 3/29.

Based on the last two stretches of the BRSY DRIFTMON, this signal is trending down at 180 cts/day, see attached.  It is currently sitting at -13500cts and it looks like this is a pretty good spot in the disturb/recover cycle for forecasting.

Next Tuesday 4 April, it should be at ~-14500cts, that is okay for operation.  If the BRS is not recentered until 11 April, the DRIFTMON will be ~-15700cts.  Not sure if we can wait that long.  Krishna is contemplating coming over for the 4 April Maintenance day for this.

15:13UTC

TITLE: 03/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 16mph Gusts, 12mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.28 μm/s
QUICK SUMMARY:

15:05UTC Richard McCarthy requested access to the LVEA. To make a physical measurement of a TCS table to correct a drawing. This was allowed due to LLO being down. Keita was consulted.

TITLE: 03/30 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Quiet night. Remained in observing except to run a2l after LLO lost lock.
LOG:

09:35 UTC LLO lost lock. Out of observing to run a2l.
09:44 UTC Back to observing.
10:18 UTC Changed sign of gain to damp PI mode 27.
14:09 UTC Chris taking Apollo to mid X and then mid Y.

DQ shif by: Satya Mohapatra, Mentor: Beverly Bereger, LHO fellow: Evan Goetz

• Average bns range over the 3 days: 65 Mpc. Noisy periods the range was dropped to 60 Mpc. Most dropped range tend to be due to passing trucks or other seismic sources.
• Average duty cycle = (93 + 73 + 34)/3. = 66 %
• airplane gltich at 0:58 UTC on 28th, (1174697431).
• Loudest events by PyCBC , short and medium duration templates on 27 and 28, and medium duration on, 29 are blip glitches.
• On 29 most glitches before 4 UTC line up with ETMX oplev yaw glitches (round 2 hveto winner).
• 3 pertinent aLOG during this dq shift:
  • On 29th March, data stretch at 11:10 UTC should be "flagged as garbage by DetChar?, from where bits 13 & 15 ("kappa_TST median" and "kappa_PU median") of the H1:GDS-CALIB_STATE_VECTOR are red during this observational stretch", due to OMC Alignment issues. Link.
  • Important study explaining, the real cause of "range increased by a couple of Mpc when the HVAC was shut down" or "Strong coupling of 8-18 Hz input beam tube vibration to the 70-200 Hz band of DARM." Link.
  • New combs in DARM since 14 March: link.

Details here: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20170327

FAMIS #6891

H1:ISI-ITMX_ST1_CPSINF_V1_IN1_DQ is definitely elevated.

[Cheryl, Daniel, Jenne, Keita, Nutsinee, Kiwamu]

As planned, we locked PRMI with the carrier light resonant. At the very end of the test, we had one good (but short) lock in which the PRC power reached 90% of that for the full interferometer case.

Here is a time line for the last good lock stretch.

• Locking started at 23:35 UTC
• The highest power was achieved (PSL = 57 W) at 23:40 UTC
• Lock was lost at 23:43 UTC

See the attached for trend of POP_A_LF. Assuming a power recycling gain of 30 for the full interferometer, we can estimate the usual PRC power to be 30-ish W * 30 = 900 W during O2. Today we achieved 90% of it according to POP_A_LF. Therefore 900 W * 0.9 = 810 W. Considering the 50% splitting ratio at the BS, ITMX receives ~400 W during the last high power test today. In addition, we had a number of lock stretches that lasted longer but with smaller PSL power prior to the last high power test.

Also, technically speaking, MICH wasn't locked at a dark fringe. Instead it was locked at a slightly brighter fringe using the variable finesse technique (35198). Also also, during the last test, Daniel and Keita unplugged a BNC cable from the trigger PD by HAM6 which triggers the fast shutter in HAM6 such that the shutter can stay closed throughout the test to prevent some optics from damaging. After we finished today's test, Daniel put the cable back in so that we can go back to interferometer locking.

[Kiwamu, Jenne]

How to lock the PRMI-only

1. Start with a well-aligned IFO
   1. Do full initial alignment sequence (can skip the final SRC align)
2. Go to ISC_LOCK state DOWN to ensure starting from good settings
3. Go to ALIGN_IFO state MICH_DARK_LOCKED to set all settings, misalign ETMs and PRM
4. Go to ALIGN_IFO state DOWN
5. Lock MICH at half-fringe using AS AIR DC (following settings should be changed, others should be fine as-is)
   1. PSL power guardian (LASER_PWR): go to state POWER_10W (to get enough SNR on AS AIR DC)
   2. Input matrix: ASAIR_A_LF -> MICH = 0.066 (all other elements to MICH = 0)
   3.  MICH1 offset = -3.0
   4. MICH1 gain = -4000.0  (MICH should now acquire lock, no triggering needed)
   5. MICH1 FM2 on.  (1:0 integrator)
   6. LSC power normalization matrix: POPAIR_A_LF -> MICH = 10 (this assumes POPAIR_A_LF_OUT is near 1.0)
6. Lock PRCL, leaving PRM misaligned to start (following settings should be changed, others should be fine as-is)
   1. Ensure PRM is misaligned, at least SUS-PRM_M1_TEST_Y_OFFSET on, at -3200 counts. 
   2. LSC length triggering: POPAIR_A_DC -> PRCL = 1.  PRCL upper thresh = 0.15.  PRCL lower thresh = 0.07
   3. LSC filter triggering (should already be set to trigger FM2, the 1:0 integrator): PRCL upper thresh = 0.15.  PRCL lower thresh = 0.07.
   4. LSC power normalization matrix: POPAIR_A_LF -> PRCL = 10
   5. PRCL1 gain = -20,000.0 
   6. Ensure ramp times on H1:SUS-PRM_M1_TEST_P_OFFSET and H1:SUS-PRM_M1_TEST_Y_OFFSET are 30 seconds or more.
   7. Turn off offsets H1:SUS-PRM_M1_TEST_P_OFFSET and H1:SUS-PRM_M1_TEST_Y_OFFSET
   8. Note that PRCL should lock on its own, as the PRM comes into alignment.
7. Reduce MICH offset, then switch to ______ RF signal
   1. MICH1 ramp time = 5 sec
   2. Simultaneously, set MICH1 offset = -1.0, MICH1 gain = -12,000. Wait for ramp to complete
   3. Simultaneously, set MICH1 offset = -0.3, MICH1 gain = -22,000. Wait for ramp to complete
   4. Simultaneously, set MICH1 offset = -0.2, MICH1 gain = -42,000. Wait for ramp to complete
8. Increase PSL power to 60W to make POP_A_LF_OUT approximately 19,700 counts, to match the value in NomLowNoise.
   1. Must first ensure OMC Fast Shutter ("toaster") is closed!!!

If unlock, do the following (quickly if possible, to reduce the amount of time we're saturating the optics):

1. MICH1 gain  = 0
2. MICH1 FM2 off
3. LSC power normalization matrix POPAIR_A_LF -> MICH = 0
4. SUS-PRM_M1_TEST_Y_OFFSET on (this one is -3200, pit is only 520, so okay with only doing yaw)
5. If desired, relock starting at step 5.3 of locking sequence.