The new RCG3.0 has the ability to report the differences in filter files which have been modified but not loaded. In other words, it a modified filter file is detected, it tells you what would be added/deleted if you were to load the filters.

The !Diff button next to the "Modified File Detected" status opens an xterm which displays the differences. The lines are marked with preceding arrows and are color coded.

Right arrow ">" and BLUE are lines which will be REMOVED when the filters are loaded

Left arrow "<" and MAGENTA are lines which will be ADDED when the filters are loaded

As a test example, I modified the H1PEMMX.txt filter file and deleted the line "# MODULES" and added a line at the end of the file "# this filter will be added when coeff load is pressed". The resulting diff listing is shown below.

liquid levels have been oscillating all day in PID mode, with gain lowered from 6 to 5. I just lowered both to 4 and will test in PID mode overnight.

Ross, Tega, Dave Barker, Joe Betzwieser, Jeff K

We have been using the new fixed phase oscillators on the h1omcpi and h1susetmxpi models. There was an ititial problem where there was an arbitrary phase mismatch between the two oscillators when viewing the two in a time series  in dtt. This was fixed after we realised that the h1omcpi model had not been restarted after the new oscillators were included. After restarting this model they both now seem to be in phase with each other. We will be using these oscillators for the down/up conversion of the omc dcpd signal with the intention of using it for damping PI modes using the ESD at ETMX. I've included an image of the the dtt timeseries data of the two oscillator outputs where the second has twice the gain of the first. Documentation on the new oscillators can be found here https://dcc.ligo.org/LIGO-T1600143

Title:  05/11/2016, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT)
State of H1: IFO unlocked.  
Commissioning: 
Outgoing Operator: N/A
 
Activity Log: All Times in UTC (PT)

15:00 (08:00) Start of shift
15:30 (08:30) Peter – Working in the PSL 
16:02 (09:02) Betsy – Going to End-Y to turn on ESD high power
16:03 (09:03) Joe – Going to End-Y for inventory checks
16:15 (09:15) Jason – Going into the PSL
16:20 (09:20) Betsy – Back from End-Y
16:48 (09:48) Joe – Back from End-Y
16:50 (09:50) Joe – Going into the LAVE for inventory checks
17:07 (10:07) Joe – Out of the LVEA
17:45 (10:45) Jason & Peter – Out of the PSL
17:50 (10:50) Joe – Moving pumps from Mechanical building
18:00 (11:00) Kyle – Going into LVEA vertex to check RGA
18:07 (11:07) Peter & Jason – Working in the PSL
18:15 (11:15) Chandra – Going to both end stations to get parts and tools
18:20 (11:20) Joe – Out of the LVEA
18:20 (11:20) Kyle – Out of the LVEA
18:50 (11:50) Corey – Going into the Squeezer Bay 
19:11 (12:11) Chandra – Back from end stations
20:09 (13:09) Kyle – Going into LVEA to turn off RGA heat
20:14 (13:14) Kyle – Out of the LVEA
20:16 (13:16) Take IFO to DRMI_LOCKED for Sheila
21:42 (14:42) IFO down for PSL work
21:55 (14:55) Dave – Restarting the OMC PI model
21:57 (14:57) Filiberto – Going into the LVEA to check IO table panels
22:00 (15:00) Jason & Peter – In the PSL enclosure working on the ISS 
 
End of Shift Summary:

Title: 05/11/2016, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT)
Support: Sheila, Jenne, Dave, Jim
Incoming Operator: Cheryl 

Shift Detail Summary: Work continues on recovery of the PSL. Commissioning work during the day as the PSL work allowed. Turn over early to Cheryl, to make an appointment in town.    

Jim and Dave

To test the stability of the continuous wave psinject hardware injection, we restarted this program by hand on h1hwinj1. Note the autostart by monit did not work, which we tracked to an accidental activation (patch and/or reboot) of the local firewall blocking EPICS connections. For now we are not running CW under monit control, so if it were to stop it would not be restarted.

A reminder that the CW is an awgstream excitation of the H1:CAL-PINJX_CW_EXC exitation point (channum=25) on h1calex. This excitation is summed with the PCAL excitation signal and sent out via a DAC channel to modulate the PCAL laser.

Had closed N2 and Kr isolation valves ~2 hours prior.

C. Cahillane

I have produced text files containing the All of O1 uncertainty budget.
The text files have frequency vectors between 5 and 3000 Hz.  The frequency vector is log spaced and has density of 250 points.
The text files also have GPSTimes between 1126073460 and 1136649540.  It is linearly spaced and has about two points per day of O1 (245 points). 

The text files have the following format:
First column is the frequency vector.
First row is the GPSTimes.
The rest of the matrix is the Response Function Info.  What info is provided is told in the file title.


        column 1| columns 2 through 246
row 1       0   |       GPSTIMES -->
---------------------------------------------------
                |
rows      Freq  | Response Function Info
2        Vector | (Either R_C02/R_C03 Mag or Phase
through    ||   |  or Sigma R_C02 Mag or Phase)
251        ||   |
           \/   |
                |


For the LLO All of O1 Uncertainty Text Files, please see LLO aLOG 26104

11:45 am local

1/2 turn open LLCV bypass valve. Took 12:00 min to overfill CP3 today at 20% LLCV open. 

Attached are some beam profiles of the high power oscillator taken from around its current
working point.

m6Clicks.png is 6 clicks (0.6A) lower than the operating point
m3Clicks.png is 3 clicks (0.3A) lower than the operating point
OperatingPoint1.png is where the laser was before doing these profiles
p3Clicks.png is 3 clicks (0.3A) higher than the operating point
p6Clicksa.png is 6 clicks (0.6A) higher than the operating point
OperatingPoint2.png is back to the operating point again

This morning I started the ETMX Charge measurement.  As Sheila mentioned in her log 27102 yesterday, I had to drive to Y-End in order to turn on the HV ESD drivers which had been flipped off presumably during Beckhoff chaos over the last week9??).  We also then found that the BIO HI/LO VOLTAGE and HI VOLT DISCONNECT medm switches were OFF when they should be ON.  The SDF for these, while looking at the DOWN state is now showing red and in the incorrect state.  This SDF is confusing to me, so will sort out with Jenne/Jeff K soon.  After switching all of this ON, I was able to run the ETMY SUS charge measurments.

Digital gain for the following PDs that could be useful (unless nothing is connected) have been zero for at least 30 days. The output of these seem to be recorded in the frame, so I set the gains to 1.

H1:PSL-OSC_PD_ISO_DC

H1:PSL-OSC_PD_INT_DC

H1:PSL-OSC_PD_BP_DC

SEI – Working on BRS and filter development
	 Developing Guardian configuration nodes for the end stations (WP #5877)

SUS – Running charge measurements on both ETMs

VAC – Continuing baking RGA in vertex
	   Several issues with vacuum gauges after yesterday's maintenance
	   Working on a grounding/power problem in LVEA

FMC – Beam tube sealing
	       
Comm: Waiting for the PSL ISS to be repaired

No safety meeting today.	

State of H1: reliably locking DRMI, losing lock around REDUCE CARM OFFSET MORE

Commissioners: Sheila

Activities:

• PSL Noise Eater reset
• Chandra to EX, EY, and back to EX to read RGA temperatures (BRS was OK'd to stay on earlier, so I left it on now)
• lockloss tool is broken and returns a guardian error "unrecognized arguments: --dump"
• Kyle to LVEA vertex to read RGA temperatures
• Chandra to the LVEA
• PSL transitioned to science mode
• Patrick left CP5 and CP6 in PID control, and they've been stable
• one earthquake at a great distance probably cause a lock loss, but nothing else
• oddly, about 4:15UTC, 21:15PT, the EX X-axis velocity trace on nuc5 (top plot) had a spike that closely resembles someone walking in the VEA, but no one that we know of was out there

FSS, when it needs help relocking, has shown a pretty consistent pattern of:

• oscillating and locking after turning the autolocker off and then on
• --- OR ---
• railing
• transitioning to oscillating, after turning off/on the loop autolocker multiple times
• locking when turning the loop autolocker on after letting it oscillate for about 30 seconds

I would like to leave them on PID to see if they recover. I'm heading out.

Jenne told me this afternoon that the laser had tripped.  The crystal chiller indicated an error with
flow sensor 1.  All the flow sensors in the chiller are the vortex style and have no moving parts
and are not likely to fail in the same manner as the old turbine ones.  My guess is that after ~31k
hours of service, it's time to start scheduling a time where we switch the chiller out for the spare
and send this unit back to Termotek for servicing - who recommend that the servicing be done annually.

    This is the second time in about 4 days that the laser has tripped because of this problem.

I just pushed a minor upgrade to guardian to fix a small issue with the guardlog client when following node logs.  The new version is r1542.

The client was overly buffering stream data from the server, which was causing data from the stream to not be output in a timely manner.  This issue should be fixed in the version I just pushed.

As always make sure you have a fresh session to get the new version:

jameson.rollins@operator1:~ 0$ which guardlog
/ligo/apps/linux-x86_64/guardian-1542/bin/guardlog
jameson.rollins@operator1:~ 0$ 

Since there seem to be some confusions about which PD has what kind of analog filtering and sent to which channel, here it is.

I'm quite certain about HPO output before AOM (which is "Power monitor PD" in D1002929) and ISS 1st loop monitors, but not that sure about "monitor PD"s in D1002164. E-travellers are incomplete (they don't say which one is installed where), so I'm just listing the nominal values for these "monitor PD"s.