TITLE: 11/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Not much
LOG:
Commissioning was just finishing up when I came in, Nutsinee resolved some SDF, been locked and observing ever since. 

TITLE: 11/07 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
LOG:

17:10 Vlad out to Optics Lab

17:20 Brian O'Reilly from Livingston called about an event from yesterday

17:47 Superevent S191105e (repeat from yesterday) was recieved. Brian O'Reilly called with the "heads up". THe Phone call came in as well.

18:47 Dan Brown out to OpticsLab

21:00 H1 out of Observing for Commissioning in conjunction with LLO.

15:45 H1 will remain in commissioning until ~16:00

Following up on work by Beverly, I ran a short Lasso run on today's range drop. The run spans 2019-11-06 02:00-07:00. Clearly very highly correlated channels are as follows:

Channel "Pearson Coefficient"
0.9799929848627831 H1:SQZ-DCPD_SUM_RMS1_MON.mean
0.9725502574463882 H1:SQZ-DCPD_RATIO_1_MON.rms
0.9312747855964804 H1:SQZ-DCPD_SUM_RMS1_MON.rms

The full page output is at https://ldas-jobs.ligo-wa.caltech.edu/~jrsmith/detchar/O3b/lasso-Nov-6-2019-2/ (updated using the fancy new python 3 version)

Figures below show:
1) The range drop from the summary pages.
2) The range and scaled SQZ DCPD channel
3) A scatter plot of range vs SQZ values
4) The other channels that are duplicate of the SQZ winner

I think not much new from what Beverly reported so far. Happy to follow up with further inquiries. 

In conjunction with Livingston, we willgo to TOO commissioning for a period of ~2.5 hours.

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

    PMC:
    It has been locked 1 days, 1 hr 18 minutes (should be days/weeks)
    Reflected power = 11.43Watts
    Transmitted power = 52.63Watts
    PowerSum = 64.06Watts.

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

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

    Possible Issues:

- Grace DB show that this alert is from 14:19UTC. Treating it as ignore. H1 is in nominal Observing and INJ_TRANS is non-functional at this time.

Ethan, Adrian, Sheila

A few minutes before Nov 01 2019 20:41:42 UTC, the instrument air compressor was put on isolation springs in order to mitigate scattering in DARM at 35 Hz (see alog 52879). The first attached plot shows when the compressor was placed on springs. The horizontal red line in the figure it set slightly above 35 Hz.

Following up on this a few days later (Nov 6), we see there is still some scattering at 35 Hz that is consistent with the behaviour of the air compressor. This seen in the second attached figure.

Some work could be undertaken to better isolate the compressor and/or locate the coupling site. 

[Gavin, Jenne]

As part of a study on Acoustic Modal Loss Tomography of the Test Masses I created a python port of the Matlab script used to analyse the Q of the 10.430 kHz PI mode (alog 50550). This script has been generalised for any resonant mode as two functions which can be imported to any python script. The motivation behind this change was in large part to add the functionality of Python to this analysis.

The ringdown function will analyse the H1:OMC-PI_DCPD_64KHZ_AHF_DQ channel and evaluate the Q of the resonant mode at the date, time and bandpass frequencies specified. The ringdown_RMS function will analyse any H1:SUS-PI_PROC_COMPUTE_MODE#_RMSMON channel and evaluate the Q of the resonant mode for the date, time and RMS mode channel specified.

These functions should allow fast, easy analysis of PI Q measurements conducted in the future for any resonant modes of interest chosen.

FAMIS11516

Added 150mL to TCSX, 100mL to TCSY.

The TCSX filter will need replacement soon, it is getting very green.

TITLE: 11/06 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Briefly taken out of observing by squeezer. Two GRBs. No other issues.
LOG:

10:22 UTC Taken out of observing by squeezer
10:26 UTC Squeezer stuck at LOCK_CLF. Hit INIT on SQZ_MANAGER. Squeezer relocked.
10:28 UTC Back to observing
11:31 UTC SubGRB E354051, Latency 9763.140000 sec. Ignore.
~14:03 - 14:11 UTC Set units for PT110 to Torr in Beckhoff, turned on trip points
14:19 UTC GRB-Short E354055
Swift
Trigger duration	0.512
Stand Down
16:00 UTC Set INJ_TRANS to INJECT_SUCCESS

TITLE: 11/06 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Knocked out observing once by squeezer. No other issues.

I've written a mid-level library of functions I always use to quickly get and plot data from nds2 in python 3.  It's called nds2utils.  

If you'd like to use it and provide feedback, I'd welcome it at https://git.ligo.org/craig-cahillane/nds2utils.  There are 11 examples.

It's on PyPi, so you can pip install it in your favorite virtual environment.

pip install nds2utils

TITLE: 11/06 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s 
QUICK SUMMARY: No issues.

TITLE: 11/06 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: Patrick
SHIFT SUMMARY: Multiple earthquakes, but not much else
LOG:

0:00 IFO was locked, but ther was an earthquake coming in, TJ put sei in EQ mode and it stayed ther for next couple hours

1:54 Back to windy

6:20 I noticed asc looking decidedly earthquake-y, so I took sei to eq again, after a couple minutes seismon picked up a 5.0 in Guatemala 

6:34 Back to windy

6:45 or so Dave called and said there was a timing error, he's put in an alog, but if anything range is better, the time he puts as the timing for some chassis going bad roughly correlates with an *increase* in range. huh.

I just noticed an intermittent timing error on the CDS overview. The RF Amp attached to port 8 of CER fanout-A has been showing a locking error on the oven controlled crystal oscillator. Image shows a 24 hour trend of the error signal alongside the Amp MEDM at a time when the system was in error. First error showed around 08:40 PST this morning, the large error stretches in the plot are roughly between 18:30 to 19:30, and from 22:15 to now (23:00).

{Gerardo, Chandra}

Replaced faulty PT-110 pressure gauge (SN 217) on HAM6 today with SN 214; however, the hot filament will not come on after some pressure transitions. I've asked Patrick to try to force it on through software when he is on shift tonight. Here is what we did:

1. isolated gauge from HAM6
2. connected aux cart and hung turbo
3. vented gauge tee with room air
4. replaced gauge
5. pumped back down
6. pressure fell as expected into low e-5 Torr range
7. helium leak checked 2-3/4" CF (no leaks beyond 6e-10 Torr-L/s background)
8. valved out turbo and then valved in gauge to main volume
9. pressure is flat lined at 8e-5 Torr, suggesting the filament is not turning on after a pressure spike from isolating "wet" gauge/tee
10. reset gauge, rebooted power, increased gauge pressure --> none triggered the filament
11. next Patrick will run emissions command in software
12. if that doesn't work we will replace with a different model gauge

Gauge is Inficon BCG450-SE and was tested on pump cart prior to installation. IP14 and small 10 l/s IP on RGA both remain stable.