aLIGO LHO Logbook

H1 General

Link

thomas.shaffer@LIGO.ORG - posted 12:19, Monday 29 July 2019 (50890)

Observing 1917 UTC

1st attempt:

Green locked quickly, DRMI looked good, but it wouldn't lock.
Automatic PRMI, DRMI still would not lock. I tried helping out with SRM, but with no luck.

Initial Alignment:

Had to touch up ETMY Y ~5urad to get green to lock.
Quickly tested Jennes SR2 alignment in ALIGN_IFO.

2nd attempt:

Lost lock on CARM_TO_TR

3rd:

All the way up autonomously.

SDFs:

Only a SUS-MC3 high precision

H1 DetChar (DetChar, PSL, SQZ)

Link

beverly.berger@LIGO.ORG - posted 11:34, Monday 29 July 2019 (50892)

DQ shift report 22 July 2019 00:00 UTC to 28 July 2019 23:59 UTC

Shifter: Beverly Berger

LHO fellows: Dripta, Adrian

LHO experienced a power glitch while observing at 03:52 UTC on 2019-07-24 and did not return to observation mode until 17:47 UTC on 2019-07-25. A summary by Jeff Kissel of the recovery effort may be found in alog 50826.
LHO was well behaved during observing time. The behavior mentioned below appeared to be minor.
On Monday, noise at 500 Hz - 2 kHz was seen intermittently. HVeto found a precise correlation with 4 channels: H1:PSL-BES_A_PIT_OUT_DQ, H1:IMC-L_OUT_DQ, H1:SQZ-OPO_FREQ_OUT_DQ, H1:SQZ-PSL_FF_OUT_DQ. This noise was not found during the rest of the week but has been found intermittently since 2019-03-13.
On Wednesday before the power glitch, scattering was visible in h(t) that was likely to be due to high winds. Near the end of the first lock, the scattering in the 20-50 Hz band was picked up in hVeto by H1:ASC-SRC2_Y_OUT_DQ.
The 48 Hz line was visible at some times on some days. So far, the culprit in the instrument is unknown although a baffle and periscope mount in HAM 3 are suspected. Studies are in progress.
The spectra of PCALX and PCALY were compared for Friday, 19 Jul, Monday, 22 Jul, and Friday, 26 Jul. PCALX showed significant changes, PCALY seemed essentially the same.
The same comparisons were made for the plots under DETCHAR/SPECTRA. There were (what appeared to be minor) changes but their significance is not clear.
An earthquake at about 1h UTC on Friday was visible in SEI/BLRMS up to 1 Hz. This may mean that it was relatively nearby. An earthquake of magnitude 4.7 in Little Lake, CA at 00:42:47 UTC is likely to have been the culprit. More interesting is that glitches in h(t) related to this earthquake were picked up by hVeto in H1:LSC-MICH_IN1_DQ and H1:ASC-SRC2_Y_OUT_DQ. These same channels were also found by hVeto during a windy period on Sunday where the noise was also detected acoustically.
Some of the described ground motion appeared to cause significant oscillation in the VCO. At those times, whistles were NOT seen.
On Friday, a new “wandering” line appeared at about 862 Hz. It was visible only for a short time.
Throughout the shift, the violin mode at 511 Hz was seen at the beginning of locks.

For the complete DQ shift report see https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20190722.

H1 General

Link

thomas.shaffer@LIGO.ORG - posted 10:37, Monday 29 July 2019 (50889)

Lock Loss 1720 UTC

No obvious cause. There maybe a ~0.5Hz oscillation seen by MICH P, DHARD, CHARD Y that shows up about 10seconds before lock loss, but it might just be me creating patterns.

1248455995

Images attached to this report

LHO General

Link

thomas.shaffer@LIGO.ORG - posted 09:28, Monday 29 July 2019 (50887)

Morning Meeting Minutes

Maintenance Tues:

(see attached picture of whiteboard)

Safety:

Jeff Jones went over communicatoin readbacks to help aid in remote help.

Bubba and Chris found large yellow jacket nests in EX chiller yard. Please be cautious of wildlife, especially in areas not heavily trafficed.

Images attached to this report

H1 SEI

Link

thomas.shaffer@LIGO.ORG - posted 08:37, Monday 29 July 2019 (50884)

BRS Drift 7 Weeks

FAMIS 6755

BRSY is getting close to its red line limit (at ~11k right now). Aux channels look good.

Images attached to this report

LHO General

Link

thomas.shaffer@LIGO.ORG - posted 08:13, Monday 29 July 2019 (50883)

Ops Day Shift Transition

TITLE: 07/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: Locked for 3.5 hours with a calm environment. Violin mode 13 on ITMX has decreased from last week's value of 4.3, down now to 4.0

H1 General

Link

jeffrey.bartlett@LIGO.ORG - posted 08:01, Monday 29 July 2019 (50882)

Ops Owl Shift Summary

Ops Shift Log: 07/29/2019, Owl Shift 07:00 – 15:00 (00:00 - 15:00) Time - UTC (PT)

State of H1: Locked at NLN, with 116.3Mpc of range from 37.2w of laser power

Intent Bit: Observing

Support: N/A

Incoming Operator: TJ

Shift Summary: With the exception of one lockloss in first part of the shift, the IFO was locked and observing for the Owl shift. Lockloss recovery went well. I had to help ALS-Y with locking, but all other parts of the initial alignment and relocking happened without operator intervention. Current environmental conditions are good and there are no outstanding issues or problems to report.

Activity Log: Time - UTC (PT)

07:00 (00:00) Take over from Corey

09:36 (02:36) Lockloss –

10:10 (03:10) Not getting past DRMI_1F, Spot looks bad Start Initial Alignment

10:30 (03:30) After tweaking ALS-Y, Initial Alignment finished without operator intervention

10:40 (03:40) First lock attempt

10:54 (03:54) Lock attempt broken at CARM_TO_TR

10:55 (03:55) Second lock attempt

11:43 (04:43) Relocked at NLN

11:44 (04:44) Clear MC3 SDF Diffs and back into Observing

15:00 (08:00) Turn over to TJ

H1 PSL (PSL, SUS)

Link

jeffrey.bartlett@LIGO.ORG - posted 07:07, Monday 29 July 2019 (50881)

OpLev Weekly Trends (FAMIS #11228)

Posted are the OpLev trends for last week.

Two items of note: (1). PR3 Sum took a 4000 ct drop on 07/25. It has been stable since. and (2). ITMX is sitting right on the +10urade line all week. All other plots look normal.

Images attached to this report

H1 PSL (PSL)

Link

jeffrey.bartlett@LIGO.ORG - posted 06:51, Monday 29 July 2019 (50880)

PSL Weekly (FAMIS #11023)

    Laser Status:
    Front End Power is 32.02W (should be around 30 W)
    70W Output Power is 69.09W
    Front End Watch is GREEN
    70W Watch is GREEN

    PMC:
    It has been locked 5 days, 3 hr 57 minutes (should be days/weeks)
    Reflected power = 10.33Watts
    Transmitted power = 54.12Watts
    PowerSum = 64.45Watts.

    FSS:
    It has been locked for 0 days 2 hr and 49 min (should be days/weeks)
    TPD[V] = 4.407V (min 0.9V)

    ISS:
    The diffracted power is around 2.2%
    Last saturation event was 0 days 2 hours and 49 minutes ago (should be days/weeks)

Possible Issues:

H1 General

Link

jeffrey.bartlett@LIGO.ORG - posted 04:49, Monday 29 July 2019 (50879)

IFO Relocked & Back to Observing

   After an Initial alignment and one relock fail, relocked the IFO at NLN. Cleared the MC3 SDF Diff (attached below) and back into observing.

Images attached to this report

H1 General

Link

jeffrey.bartlett@LIGO.ORG - posted 04:19, Monday 29 July 2019 (50878)

Ops Owl Mid-Shift Summary

   Ran Initial Alignment after lockloss and problem getting past DRMI_1F. In the process of relocking. 

   Environmental conditions are good for observing after relock.

H1 General

Link

jeffrey.bartlett@LIGO.ORG - posted 00:12, Monday 29 July 2019 (50877)

Ops Owl Shift Transition

Ops Shift Transition: 07/29/2019, Owl Shift 07:00 – 15:00 (00:00 -08:00) - UTC (PT)

State of H1: Locked at NLN

Intent Bit: Observing

Weather: Skies are clear; No rain in the forecast. Temperatures are in the upper 60s, dropping into the upper 50s by dawn. Winds are Calm.

Primary 0.03 – 0.1Hz: 0.009um/s

Secondary 0.1 – 0.3Hz: 0.03um/s

Outgoing Operator: Corey

Quick Summary: IFO has been observing for the past 17 hours. Environmental conditions are good. The range is 115.0Mpc. No apparent problems to report.

LHO General

Link

corey.gray@LIGO.ORG - posted 00:04, Monday 29 July 2019 (50874)

EVE Operator Summary

TITLE: 07/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 118Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

Nice & quiet shift with H1 continuing to be locked from Ed's graveyard shift (for 17+hrs of lock/observing); Just went out of triple coincidence as I see Virgo going to COMMISSIONING. Environmental conditions are also pretty quiet *knock on wood* (low winds & microseism).
LOG:

5:04 5.0 EQ from Panama on Verbal, but it was small. No action taken.
Tried running new washer for first time....looks like it's out of Rinsing Liquid and I couldn't find more of it.
Handing the reins of H1 off to Jeff B.

H1 ISC

Link

cheryl.vorvick@LIGO.ORG - posted 19:56, Sunday 28 July 2019 - last comment - 10:15, Monday 29 July 2019(50875)

glitch paterns from ASC striptool

Images of a few glitches seen today, showing how the ASC responds. Image names have the minute when the glitch happened. The third image has 2 different glitch paterns.

Images attached to this report

Comments related to this report

jeffrey.kissel@LIGO.ORG - 10:15, Monday 29 July 2019 (50888)DetChar, OpsInfo

Link

What we're seeing here is the impulse (i.e. a glitch) response of several slow ASC loops. In this comment, "slow" is defined by human patience, but typically means the unity gain frequencies are below the first suspension resonances, i.e. below 0.5 Hz.

Either an optic, or collection of optics gets a kick, or the the sensor signal is briefly swamped by the glitch, and sends an impulse through the ASC system (I intentionally don't specify a loop because many of the loops are cross-coupled, either in sensor or actuator, or both). Any/every linear, time-invariant, control loop has an impulse response, and these loops are no different. The response will be (roughly) the same every glich, in terms of shape and time of ring-down, because the loop filters and response is the same between them. The variety in character is just a symptom of the magnitude of impulse / glitch.

For the *very slow loops (i.e. those driven by the Alignment Dither System [ADS]), it may be that the glitch drowns out the driven error signal (the ADS lines) in the error signal (DARM / DELTAL EXTERNAL) for an "extended" period of time ("extended" in quotes because it's just "a period of time roughly equivalent to the time scale of 1 / unity gain frequency"). That means the control signal will be bogus -- thus pushing around the ASC system nonsensically, also perhaps looking like a wiggly excursion of an impulse response -- until the error signal is returned with good signal to noise ratio.

Sadly, this repetitive nature unfortunately does not mean that we are able understand the source of the glitch any better.
*BUT* these are quite slow loops, which means they take time and patience to intentionally / actively / quantitatively characterize via driven transfer function. Yet, a loop's impulse response will contain the same information as the driven transfer function. So -- maybe we can use these regular impulses to better characterize / quantify the loops (via offline study)!

LHO General

Link

corey.gray@LIGO.ORG - posted 19:51, Sunday 28 July 2019 (50876)

Mid-Shift Status

Smooth sailing as I ready to cook "lunch". H1's been locked/observing 12.75+ hrs & going on 7+hrs of #LIGOVirgo Triple Coincidence.. Winds have died in the last 2hrs.

LHO General

Link

corey.gray@LIGO.ORG - posted 16:29, Sunday 28 July 2019 (50872)

Transition to EVE Log

TITLE: 07/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.07 μm/s

Thought useism was inching up 24hrs ago, but it's dropped back down to the doldrums. Winds are definitely calmer than last night--Whew!
QUICK SUMMARY:

H1 locked/OBSERVING for almost 9.5hrs with BNS range just under 120Mpc.

H1 General

Link

cheryl.vorvick@LIGO.ORG - posted 16:16, Sunday 28 July 2019 (50873)

OPS Day Summary:

TITLE: 07/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 1mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: locked all shift, range is increasing, with the average at about 118Mpc

H1 General (DetChar, TCS)

Link

edmond.merilh@LIGO.ORG - posted 03:19, Saturday 27 July 2019 - last comment - 08:50, Monday 29 July 2019(50854)

H1 Out of Observing

TCS_ITMX_CO2 node and ISI_HAM3 node have notifications.

10:02 it seems that the TCSX Laser became unlocked. I didn't see any "red" indications of this. Only the SDF diffs (which) I didin't completely understand. I accepted the diffs and this didn't clear the ready bit. By comparison the X looked ok to the Y. THen I opened the TCS_ITMX_CO2 node and saw that it was trying to re-lock. It was successfull and the diffs showed on the SDF so I accepted them (in effect reverting back to the good state, I suppose.

10:14 it just happened again as I'm typing. ugh. .....and it re-locked

10:16 Back to Observing. Hopefully, this is the last of this.

Comments related to this report

edmond.merilh@LIGO.ORG - 03:22, Saturday 27 July 2019 (50855)SEI

Link

Here is the notification from the ISI_HAM3 node (image)

Images attached to this comment

thomas.shaffer@LIGO.ORG - 08:50, Monday 29 July 2019 (50885)

Link

This is the first time that TCSX has lost lock while the IFO was in low noise for O3. We have been having other issues with TCSY.

H1 ISC

Link

jenne.driggers@LIGO.ORG - posted 16:37, Thursday 25 July 2019 - last comment - 11:46, Monday 29 July 2019(50823)

New align SR2 state in ALIGN_IFO

I have created a new set of states for the ALIGN_IFO guardian to do the alignment of SR2 with SRM misaligned. This is something that operators often do by hand when the SRC won't lock. I have not yet tested these states, but hope to on Tuesday when we're recovering from maintenance, or next time I'm around that we need to do an alignment. Once the states are tested we can add some logic to TJ's INIT_ALIGN guardian to give up on SRC locking after some seconds of trying, do SR2 alignment, then go back to SRC alignment.

Comments related to this report

jenne.driggers@LIGO.ORG - 11:46, Monday 29 July 2019 (50893)

Link

[TJ, Jenne]

We took ~5 min during an initial alignment to commission the new SR2 alignment states. The states seem to work well, although I need to think more carefully about the guardian paths to get to them. I have also confirmed that the initial alignment and DRMI guardians reset the SRC1 and SRC2 filter states and in/putput matrices properly after this state is run.

With a bit more thinking on the path situation, we should be able to now include this as part of the auto-initial alignment guardian if SRY isn't locking on its own.