TITLE: 11/27 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Camilla
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 15mph Gusts, 10mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.57 μm/s
QUICK SUMMARY: useism is >90% and the wind seems to be picking up sporatically. M6.0 EQ on its way.

TITLE: 11/27 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Locked 10h30. Incoming EQ and Microseism high.
LOG:

• 00:13 Liquid Nitrogen truck arrived and traveling to EX
  • It's arriving outside Tuesday Maintenance because the original truck broke down.
• 00:38 LN2 arrived at EX (drove all the way down the arms at 5mph. Maybe he didn't understand our definition of building vs beam tube)
• 00:51 All wind fence crew have left.
• 01:58 LN2 truck starting to move back from EX
• 02:55 Noticed SUS > DRIFT MON has MC1 in the "danger zone"  Maybe this is normal / page is out of date?
• 05:27 Can hear plane from CR
• 07:06 Watching ETMY Violin mode 4 as it's creeping up
• 07.29 Alert for incoming 6.1Mag EQ from Greece: expected ~00:10

All fine, microseism and wind still high. Locked for 6h45.

TITLE: 11/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
INCOMING OPERATOR: Camilla
SHIFT SUMMARY:
LOG:

16:30 Robert to EY

16:30 Gerardo Kyle to EX

16:30 Hugh to HAM5

17:00 Jason tweaking PMC alignmnet

17:00 Marc to mezzanine

17:30 Marc Richard replacing Kepco

20:00 Wind fence crew starts arriving

New ENV_STAT guardian node

TJ, Dave:

TJ started a new guardian node this morning, which generated a new GRD INI file. I restarted the DAQ and h1edc to add the 23 new channels to the DAQ.

CDS Hardware monitor IOC started

Dave:

I have created a new EPICS IOC which monitors the front end hardware status. The HW status was added to the bottom of the CDS Overview MEDM, next to the DAQ block. Currently it scans all the ADC and DAC cards.

Issues with dmtviewer containers on FOM machines

Dave:

Today after rebooting the FOM Nuc computers I found a new issue with our debian-8 singularity dmtviewers, which were not accepting xml files which were not on the local disk drive. I'll investigate this further, but for now I've made a copy of the xml files in /home/controls to get the FOMs active again.

Tested NCAL status on CDS Overview.

When Timesh activated the EX NCAL this morning, I verified that the NCAL status on the CDS Overview screen did go red.

Hugh went out and checked all the stops on HAM5 HEPI this morning. Seems there was a stop that got missed that was causing the 1hz peak. After backing the stop off fully, the peak disappeared. 

Attached plot compares L4C RZ spectra (the direction the peak was most pronounced in) from a period last night (purple), when the peak was louder, to a time after relocking this afternoon (green), after Hugh fixed the stop. 

[R.Schofield, T.Mistry]

During todays' Tuesday maintenance, we powered the encoder and used a portable magnetomoter to investigate various locations. We tested a) On top of the NCAL, next to the motor, b) On top of the encoder box and c) on top of the NCAL Beckhoff controller box. These lcoation are the most likely places to expect stay magntic field coupling into DARM. A more detailed analysis will follow later. We took measurements between 1016 PDT and 1313PDT.

I've tidied up the ndscope that is meant to replace the StripTool on the front wall's center bottom TV.  The colors now match the old striptool colors (and all the other 'scopes we have in the ISC folder), and the scales are set such that the traces *look* the same as they used to. 

To make the traces look similar in scale to the old StripTool I had to scale all of the traces by some value (1/(old StripTool ylimit)), so you can no longer read off what the actual value of any trace is.  For example, POP18 is currently about 36 counts, but on the new ndscope on the front wall it's just a little under 0.2 y-axis units.   Also, ndscope can't do log y-axes (at least, I don't know how), so the TR NORM channels will disappear off the top of the plot when we get to resonance, but the information is still on the plot in the PWR CIRC channels.

If we still like this next week, we can do something similar to the 40 min StripTool on the left wall.

Reduced the CLF power incident on the CLF PD to a nominal 5µW. The CLF waveplate was adjusted, so the that CLF ISS drive offset stayed near 2.7V. This required the following changes:

The CLF ugf was measured to be 2.2kHz, the CLF ISS ugf is 10kHz, and the LO ugf is 4kHz.

TJ, Sheila, Patrick

TJ has written code in the ALS arm guardians that will attempt to move the alignment of the ETM to increase the height of the flashes.  This morning when maintence started and TJ's owl shift ended he started to test the code, after he left Patrick, Jim and I contuinued to test it.  The main message is that this seems promising, we may need to add some steps that optimize the TMS alignment as well.   

The new code is in the ALS arm guardians, there is a new state called INCREASE_FLASHES.  This scans the test offset over a set of offsets (-1 to +1 urad at the moment, based on data that Jim posted 53415), and checks which position gave the maximum flashes.  If it is one of the extremes of the offset list, it will continue to move 1.5 urad more in that direction until it passes the maximum.  Once it finds a maxiumum of the flashes for pitch, it will set the opticalign sliders to that offset.  If the flashes are above some threhsold, (0.8 at the moment), then it will quit.  If the maximum is below that threshold, it will repeat the procedure once for yaw.  We have tested this much of the functionality for ETMX, which is all that is currently written.  

We tried this several times while debugging, and it did do a good job of restoring the ETM after we misaligned it by a few micro radians.  The main change that we made to the code after TJ left is that we edited the variable spot to be the test offset at which we get the maximum flashes, instead of an index, which simplified some things for the case where we need to search further because we didn't reach the maximum. 

When Jim was struggling to get the x arm locking in green, we tried this code out.  It worked, in that it moved the ETM to increase the flashes, but the maximum flash that we found after one round of pitch and one round of yaw was 0.65.  Jim found better flashes manually by also moving TMS.  Three next steps would be to add TMS steps to this code, to try testing this on the Y arm, and to test the integration of this with ISC_LOCK, which TJ has drafted but we didn't test today.

Replaced faulty KEPCO power supply in the CER Mezzanine.  This supply provides power for the +18V rail in ISC-R4.  The fan in the power supply was starting to chirp meaning the ball bearing in the fan was going out, so it was near failure.  We turned off the sequencer on ISC-R4, replaced the supply, verified voltages, and turned the sequencer back on.  All lights are green.

Outgoing Supply: S1201953

Incoming Supply: S1201959

Work completed per WP8476

M. Pirello, R. McCarthy

While resetting the PSL power watchdogs, I noticed that the PMC reflected power was getting a little high, up to 11.7W.  I therefore tweaked the beam alignment into the PMC; this was done with the ISS OFF.  Changes summarized below:

• Before
  • PMC Trans: 52.2W
  • PMC Refl: 11.7W
• After
  • PMC Trans: 52.3W
  • PMC Refl: 11.4W

I turned the ISS back ON, and noticed the diffracted power was below our 2% minimum (~1.4%), so I adjusted the ISS RefSignal from -2.0V to -1.99V.  This brought the diffracted power back to 2%; this change was accepted in both the safe and observe SDF files.

Both PSL power watchdogs were reset at 18:00 UTC (10:00 PST).  This completes FAMIS 10738.

TITLE: 11/26 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Quiet shift, maintenance has started.
LOG:

• 1100 GRB - Fermi. Standing down 15 min.
• 1115 Stand down over
• 1546 Starting PEM inj script
• 1558 Robert to EX to for some camera shots

Started the new node to test different environment conditions. This is just a status node and will not affect the IFO at all.

Overviews have been updated. Added to exclude list for Observing.

Locked for 6 hours range 117Mpc, no issues to report.

TITLE: 11/26 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: Camilla
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.33 μm/s
QUICK SUMMARY: Locked for 1.5hours after earthquake. Wind has calmed down and useism is slowly decreasing.

TITLE: 11/26 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Happily Observing again now after EQ
LOG:

• 23:39 Sharp range drop probably due to winds increasing to 29mph.
• 02:58 Incoming 6.7 EQ from Albania
• 03:07 SEI_CONF  to EQ as ground movement starts (30 minutes before expected R3.5 wave)
• 03:17 Lockloss
  • See alog 53492
• 04:25 Reset the "Access Video" server after noticing that the camreas are down and I can't reconnect. This happened on Saturday to Patrick too: alog 53453
• 05:22 I also notice that the logs from buttons in guardian nodes are blank, can see logs using guardctrl log but not the "log"  button.  Jeff's alog 53456
• 06:31 NLN, Observing!
• 06:43 SEI_CONF to EQ as another incoming EQ from Albania 5.6mag
• 07:23 SEI_CONF back to WINDY

• 02:58 Incoming 6.7 EQ from Albania
• 03:07 SEI_CONF  to EQ as ground movement starts (30 minutes before expected R3.5 wave)
• 03:17 Lockloss #1 from NLN
• 03:24 after 5 minutes of LOCKING_ARMS_GREEN
  • ETMX PIT 65.8 to 67.4
  • ETMX YAW -130.9 to -130.6
  • ETMY PIT 127.4 to 129.3
  • ETMY YAW -136.9 to -136.6
• 03:33 Lockloss #2 at LOCKING_ALS
• 03:36 Lockloss #3 at LOCKING_ALS
• 03:38 Lockloss #4 at LOCKING_ALS
  • Ground movement increasing, switched SEI_CONF to LARGE_EQ
• 04:53 Forced Lockloss #5 from LOCKING_ARMS_GREEN
  • Ground movement settled down but stuck on LOCKING_ARMS_GREEN, WFS grab but loose the signals too soon.
• 04:55 INITAL ALIGNMENT
  • SEI_CONF from LARGE_EQ to EQ
• 05:22 INIT_ALIGN is stuck in OFFLOADING_MICH_BRIGHT
  • ALIGN_IFO log says STALLED, that "MICH IS NOT LOCKING" and keeps going back to DOWN. Maybe it is timing out?
  • Change SEI_CONF from EQ to WINDY
• 05:29 Forced Lockloss #6 from INIT_ALIGN as IFO seems stuck. (DOWN, INIT, wait for READY, request NLN as we've completed most of INITIAL)
• 05:40 Stuck at FIND_IR
  • Adjusted TR_X/Y_QPD_B_SUM to get offsets <0.1.
  • No H1:LSC-TR_X/Y_NORM_INMON signals even with adjusting DIFF and COMM OFFSET. That seemed strange.
  • Noticed that laser power was at 10W! (There was a guardian notification I hadn't spotted) Maybe this was because I had exited from Initial Alignment?!
• 05:51 Forced Lockloss #7 from FIND_IR
• 06:31 NLN, Observing! yay.

DQ Shifter: Sudhagar S

Email: sudhagar.suyamprakasam@ligo.org

Fellow(s): Gavin Wallace

Link to DQ Shift: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20191118

* Summary

• Mean Duty Cycle (85.49% + 66.45% + 79.47% + 83.75% + 89.28% + 86.29% + 83.79% ) / 7 = 82.07%

• Mean BNS Inspiral range ~ 115 Mpc

• PCAL X is not generated on Monday
  • PCAL X shown up broad band variations ~(10 Hz to 1000 Hz) on Wednesday and Thursday.

• Spectra
  • ~2 K Hz line presence on Monday. It disappeared on Tuesday and Wednesday alog=53356
  • Spectra is not available from Thursday on-wards.

• Air compressor noise at 36Hz persists through out the week. alog=53241

• Couple of lock loss due to the Earthquake (Wednesday and Thursday)

• Following noise frequencies shown up this week.
  • ~11 Hz - Monday, Friday and Saturday
  • ~64 Hz - Monday
  • 42 Hz - Friday and Sunday

• H1: ETMX ESD Rack Power: More noisy on many days in a week.

• Violin modes rung up beginning of the lock state