aLIGO LHO Logbook

H1 General

travis.sadecki@LIGO.ORG - posted 02:30, Monday 09 November 2015 - last comment - 06:26, Monday 09 November 2015(23236)

OPS Owl Shift Summary

Title: 11/9 Owl Shift 7:00-15:00 UTC (0:00-8:00 PST). All times in UTC.

State of H1: Locked in NLN, but not in Observing due to RF45 glitching

Shift Summary: RF45 glitching does not appear to be improving. Rather than sit in the chair all night collecting bad data, I'm calling it a night and heading home.

Incoming operator: Ed

Activity log:

None, staring at glitchy data.

Comments related to this report

andrew.lundgren@LIGO.ORG - 06:26, Monday 09 November 2015 (23237)DetChar, ISC

Link

Keita suggested tapping on the EOM box and wiggling the cable alog 23159. In the absence of anything better, that seems like a good idea.

H1 General

Link

nutsinee.kijbunchoo@LIGO.ORG - posted 00:15, Monday 09 November 2015 (23235)

Ops EVE Shift Summary

TITLE: "11/08 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PST), all times posted in UTC"

STATE Of H1: Locked at NLN but not Observing

SUPPORT: Kiwamu, Dave, Mike, Evan, Vern, Jenne

SHIFT SUMMARY: RF45 has been glitching the whole shift. The BNS range has been at 15-20Mpc. I was informed to let the Owl Operator know if thing doesn't get better in couple of hours he can just go home.

INCOMING OPERATOR: Travis

ACTIVITY LOG:

See alog23230 and alog23222 and all the comments therein.

I ran into a few troubles during the first relocking. ALSX VCO railed and Tune Ofs stuck at +5 so I moved the slide bar to somewhere around 0. Later PRMI wouldn't lock after given 20 minutes I adjusted BS and PRM pitch and yaw back to where they were before the lockloss which improved the flashes almost immediately. The second relocking went smoothly. I have been leaving RF45 MOD at 21.2 dB because ETMY saturation alarm was annoying.

Images attached to this report

H1 General

Link

nutsinee.kijbunchoo@LIGO.ORG - posted 19:17, Sunday 08 November 2015 - last comment - 20:39, Monday 09 November 2015(23230)

Lockloss 03:12 UTC

Tidal and ASC (PRCL1, DHARD) was running away.

Images attached to this report

Comments related to this report

nutsinee.kijbunchoo@LIGO.ORG - 20:33, Sunday 08 November 2015 (23231)

Link

The ifo is locked at NLN but not observing. RF45 still glitching.

nutsinee.kijbunchoo@LIGO.ORG - 23:15, Sunday 08 November 2015 (23232)

Link

Lockloss again at 07:00 UTC

DHARD ran away again. I lowered the gain as soon as I noticed the oscillation. The amplitude of the oscillation didn't seem to decrease. Maybe I didn't catch it quick enough?

Images attached to this comment

nutsinee.kijbunchoo@LIGO.ORG - 23:08, Sunday 08 November 2015 (23233)

Link

I also couldn't connect to the nds sever. So no dataviewer.

I will be taking a few minutes to grief.....

Images attached to this comment

nutsinee.kijbunchoo@LIGO.ORG - 23:10, Sunday 08 November 2015 (23234)

Link

Dataviewer seems to work on a different computer. Resume relocking.

jenne.driggers@LIGO.ORG - 11:12, Monday 09 November 2015 (23247)

Link

Hmmm, maybe we just should always be using the lower DHARD gains when we're on the 45mHz ISI blends? I think DHARD Pit is usually 10, and should go to 7. DHARD YAW is usually 15, and should go to 10.

sheila.dwyer@LIGO.ORG - 20:39, Monday 09 November 2015 (23263)

Link

I don't think that the oscillation that nutsinnee shows in the screen shot is the one that can be fixed by lowering the gains, that is around 0.6Hz, while the screenshots show an something happening at around 20mHz. This large low frequency motion of DHARD yaw was happening durring earthquakes durring ER8.

I would be more inclinnded to leave DHARD gains alone or try to increase the low frequency gain for Yaw, depending on what was really happening (was this ground motion or a loop oscillation?). I think that lowering the gain could actually make things worse in either case.

For a rough model of DHARD yaw loop with thee new boost added, see https://alog.ligo-wa.caltech.edu/aLOG/uploads/21768_20150921225603_DHARDYAWOLGwithboost.png

H1 General (OpsInfo)

Link

nutsinee.kijbunchoo@LIGO.ORG - posted 16:51, Sunday 08 November 2015 - last comment - 17:58, Sunday 08 November 2015(23222)

RF45 mod decreased by 2dB

Since the data is probably going to be cat1 vetoed anyway, I decided to help the situation the only way I know how. The RF45 Mod was 23.2 dB, now at 21.2 dB. I dropped out of Observing when I did this. I asked Kiwamu to make sure that it's okay to leave the gain at this value.

The glitches stopped for about 15 minutes. While writing this alog it seems to be coming back again. I might decrease the gain even further if it doesn't stop.

Images attached to this report

Comments related to this report

nutsinee.kijbunchoo@LIGO.ORG - 16:55, Sunday 08 November 2015 (23223)

Link

RF45 mod gain decreased to 20.2 dB.

evan.hall@LIGO.ORG - 16:55, Sunday 08 November 2015 (23224)

Link

If you go more than 2 dB lower than nominal you risk unlocking the interferometer. There is also no clear evidence that reducing the modulation depth fixes this issue, but of course it doesn't hurt to get another data point.

nutsinee.kijbunchoo@LIGO.ORG - 16:58, Sunday 08 November 2015 (23225)

Link

I can see that DHARD isn't happy. I put the gain back to 21.2dB.

nutsinee.kijbunchoo@LIGO.ORG - 16:59, Sunday 08 November 2015 (23226)

Link

I just noticed SUSETMY has timing error. I hit Diag Reset to clear this. ETMY saturation continues.

Images attached to this comment

nutsinee.kijbunchoo@LIGO.ORG - 17:17, Sunday 08 November 2015 (23227)

Link

Observing again at 01:20 UTC. ETMY continues to saturate. I don't think there's anything else I can do to help.... If you have an idea please call the control room.

nutsinee.kijbunchoo@LIGO.ORG - 17:32, Sunday 08 November 2015 (23228)

Link

Decreased RF45 MOD to 20.2 dB again after RF45 amplitude increased and stuck there causing DARM noise floor to rise. Forgot to go out of Observing when changing the gain.

Images attached to this comment

nutsinee.kijbunchoo@LIGO.ORG - 17:58, Sunday 08 November 2015 (23229)

Link

I called Mike and he suggested I take the ifo out of Observing and wait until the RF45 situation gets better. The BSN range is at 15-20 Mpc at the moment. RF45 MOD set to 21.2 dB.

H1 General

Link

edmond.merilh@LIGO.ORG - posted 15:56, Sunday 08 November 2015 (23221)

Shift Summary -Day

TITLE: Nov 6 DAY Shift 16:00-00:00UTC (08:00-04:00 PDT), all times posted in UTC

STATE Of H1: Observing

SUPPORT: Kiwamu

LOCK DURATION: ≈2.5 hrs (this shift)

INCOMING OPERATOR: Nutsinee

END-OF-SHIFT SUMMARY: IFO Locked and very glitchy(too many ETMY saturations to list). High amounts of earthquake activity had us down since Patrick turned over to me. Then another barrage of quakes ensued. µSeism is between .7-1+microns. High ground motion is obvious in POPAIR_LF_90, ASC Yaw signals and in Tidal StripTool Wind is picking up this afternoon exceeding 20mph only for a short while. Handing Nutsinee a locked Interferometer.

ACTIVITY LOG:

16:20 Robert out to LVEA to install a shaker.

17:30 Spent some time on the phone with Kiwamu getting this M2 to M1 SR3 offloading issue handled. Then another 3.9µcron from a 6.4mag in Indonesia. It’s going to be a bumpy day.

19:21 Looks like a good time to try and make something happen. EQ bands are back down in the .1µ region

20:15 after much struggling with alignment, Kiwamu is on site and showed me how close I was and how to overcome my impasse. Alignment commences. EQ bands now below .1µ. Sudarshan is also on site.

21:42 Intent Bit to Undisturbed