Mid-SHIFT SUMMARY: IFO locked. Range has been sketchy between 70 and 78Mpc. I switched ETMX from all 90mHz blends to 45mHz on axis to try and reconcile some range and clean up ASC PIT and shaky POP_A_LF. Winds are calm. uSei has been above he 90th percentile range, maxing to .8um/s. I spoke with Livingston a few times regarding their status and also as protocol to the GRB alert.

11:40UTC. Contaced Doug at LLO. They're locked at RF and still dealing with bounce and roll modes. H1 Locked @ 75Mpc. 

Range wasn't looking so good either.

Excerpt from log:

09:40 POP_A_LF_OUTPUT looks ratty and he range has diminished down into low 70-high 60 land. Going to try switching to 45mHz blends at EX. uSei is kinda high bu winds are low.

09:42 Intention bit set to commissioning by SDF when changes to blend made

09:52  Switching blends to 45mHz at ETMX (X) seems to have decreased the amplitude in DHARD_PITCH_OUTMON. This seems to, maybe, have helped the range slightly.

10:02  Intention bit set to Observe. 76Mpc

Range is still up and down. The Inspiral Range Integrand looks a little less than nominal around the 12-13Hz area. The only correlating information I can see is that the Z axis in the 10-30 Hz anthropogenic bands are excessively higher than its X&Y counter-parts. Also, the 3-10Hz Z axis is elevated and uSei is above the 90th percentile mark. ?

TITLE: Dec 29 OWL Shift 08:00-16:00UTC (00:00-08:00 PDT), all times posted in UTC

STATE Of H1: Observing

OUTGOING OPERATOR: Jeff

QUICK SUMMARY: IFO has been locked in the 80Mpc range for 19 minutes. Seismic conditions in the EQ bands are back to nominal after some activity and µSei is ≥ 90th percentile. Wind is ≤5mph. Livingston is down for the night.

Activity Log: All Times in UTC (PT)

00:00 (16:00) Take over from Cheryl
02:35 (18:35) Lockloss – Possibly due to mag 5.6 EQ in Papua New Guinea 
06:50 (22:50) GRB – IFO is being relocked; LLO is down. Ignored alert.
07:55 (23:55) Locked and intent bit set to Observing. Power at 21.7W, range 78Mpc
08:02 (00:02) Turn over to Ed  

End of Shift Summary:

Title: 12/28/2015, Evening Shift 00:00 – 08:00 (16:00 – 00:00) All times in UTC (PT)

Support:  Kiwamu
 
Incoming Operator: Ed

Shift Detail Summary: Lost lock 2.5 hours into the shift, (lockloss probably due to EQs). After seismic settled down tried relocking without an initial alignment, but with no lock. Given the long lock stretch and the two EQs did not think this would work, but it was worth a try. Ran initial alignment and tried relocking. Loosing lock at various stages, and after several tries it became apparent alignment had drifted a bit. Reran initial alignment and was able to relock the IFO with no apparent problems.    

   GRB alert at 06:50 (22:50) - LHO working on relocking after EQ lockloss; LLO is down. Ignored alert.

   Working on relocking the IFO after earlier EQ. Going through initial alignment. 

    02:35 (18:35) Lockloss, possibly due to a mag 5.6 EQ near Papua New Guinea. Seismic jumped up to just over 1.0Um/s. Will try relocking as soon as things settle down.   

Title:  12/28/2015, Evening Shift 00:00 – 08:00 (16:00 – 00:00) All times in UTC (PT)
	
State of H1: 00:00 (16:00), The IFO has been in Observing mode for the past 5 hours (IFO has been locked for over 40 hours, but there was a break in observing). Environmental conditions are good. The wind is calm (0- 1mph); seismic is flat and microseism is centered around 0.3um/s.      

Outgoing Operator: Cheryl

Monthly test call came in at 12:33PT, 20:33UTC, informing us that the test of the sirens would have them running off and on for an hour.

Ops Day Summary: 16:00-23:59UTC, 08:00-16:00PT

State of H1: locked in Observe, range is 77Mpc

On site: Darkhan (fellow), JeffK, Gerardo, Sudarshan, Thomas Vo, Kiwamu (just arrived), and JeffB (incoming Ops, just arrived)

Shift Details:

• H1 has been locked 40 hours 3 minutes
• one unintentional break in Observe occured from 19:03-1925UTC (see earlier alog for details)
• during the break in Observe, there is about 15 minutes of "unofficial undisturbed" time (see same earlier alog for details)
• PSL diode chiller filled
• CP3 filled manually by Gerardo
• Gerardo on site and driving off and on starting from 23:04:36UTC and ending by 00:00UTC (more details in his alog)
• ETMY saturations, 15 total during my shift
• Gamma Ray Burst at 22:47:43UTC

Maintenance Tasks Tomorrow:

• one LN2 delivery slated for maintenance tomorrow; CP3 at MY
• weekly GraceDB heartbeats at ~9:00am and ~9:05am, for SNs and GWs, respectively
• PSL watchdog reset

After notifying the operator I drove past CS @ 23:04 and arrived at Y-Mid station @ 23:09.
Started filling CP3 @ 23:15, opened the exhaust check valve bypass valve, then opened LLCV bypass valve 1/2 turn, closed the flow 105 seconds later.  3 minutes later I closed the exhaust check valve bypass valve.

Started driving back from Y-Mid @ 23:28, arrived at the CS @ 23:32.
 

State of H1: locked in Observe, range is 76Mpc

The full report is located here

• The 24th was a very difficult day locking due to problems with ALS, only about 7.6% observing.
• The 25th had a better percentage of duty cycle, however, it's a little misleading because there was a lot of glitching between 06:00 and 16:00.  This could have been due to RF45 but Fred's ALOG suggests it could be something a bit trickier.  For some reason, HVETO did not run this day but it would be very interesting to know which glitches it caught, the range and Omicron look terrible during this time.
• The 26th had very very clean data, the shift went smoothly and we got about 85% observing.
• The 27th was also very clean data and we got  95% observing!

• LVEA temperature crossed 70 degrees F.
• Temperature appears to be leveling off at 70.1F.
• 10 day trend shows overall increase.
• LVEA temperature crossed 70F on 12/25, and returned to a temperature below the alarm level in about 2 hours.

I added 250ml to the PSL Diode chiller today, after PeterK called and pointed out that it was showing a low water level alarm.

Attached is a 42 day plot of the PSL diaode chiller low water level alarm.

I am not able to reconcile the alog entries for filling this chiller with this plot.

I wrongly added the amount I put in the Diode chiller on the Crystal chiller log (paper log in chiller room), so have crossed my entry off that list.

What happened:

An accidental button push took H1 out of Observe at 19:03:46UTC, and H1 was returned to Observe at 19:25:31UTC after the PSL diode chiller was filled.

Timeline Details:

• The filter, ETMY_L3_DRIVEALIGN_L2L FM3, was briefly turned off and back on, and the glitch was visible in H1 DARM.
• The filter was in a non-standard configuration approximately between 1145364642 and 1135364645 GPS time (times taken from dataview plot).
• During that time I was talking to Peter King - he called to let me know that the PSL Diode Chilller was in alarm, low water level.
• Trend of 7 day history of this alarm is attached, and shows that although the chiller was filled on the 24th, it quickly went back into alarm for low water level.
• History is that when filled, the amount added has been 125ml.
• I added 250ml today.
• This alarm should be watched closely in the next 24 hours to insure it doesn't go back into low water level alarm.
• I finished filling the chiller by 19:24:00UTC.
• I returned to the Control Room and returned H1 to Observe at 19:25:13UTC.

Given these activites, after ETMY L2L filter back was restored and resulting glitch in DARM passed, the IFO was not disturbed again until I filled the chiller between 19:19:00UTC and 19:24:00UTC.

Timeline Summary:

• 19:03:46 H1 out of Observe
• approx. 19:03:50, ETMY filter bank was back in standard config.
• H1 undisturbed for approx. 15 minutes
• 19:19:31UTC I take a "before" snapshot of the chiller warning
• I fill the chiller
• 19:23:52UTC I take the "after" snapshot of the chilller and then exit the chiller room
• 19:25:13UTC H1 is returned to Observe

IFO Guardian Log Details:

2015-12-27T08:01:00.52831 IFO [ALL_NODES_OK.enter]
2015-12-28T19:03:46.23209 IFO [ALL_NODES_OK.run] USERMSG: node NOTIFICATION: DIAG_SDF
2015-12-28T19:03:46.35568 IFO state returned jump target: DROP_OK
2015-12-28T19:03:46.35588 IFO [ALL_NODES_OK.exit]
2015-12-28T19:03:46.41705 IFO JUMP: ALL_NODES_OK->DROP_OK
2015-12-28T19:03:46.41724 IFO calculating path: DROP_OK->ALL_NODES_OK
2015-12-28T19:03:46.41748 IFO new target: WAITING_FOR_NODES_OK
2015-12-28T19:03:46.41790 IFO executing state: DROP_OK (5)
2015-12-28T19:03:46.41802 IFO [DROP_OK.enter]
2015-12-28T19:03:46.60496 IFO EDGE: DROP_OK->WAITING_FOR_NODES_OK
2015-12-28T19:03:46.60534 IFO calculating path: WAITING_FOR_NODES_OK->ALL_NODES_OK
2015-12-28T19:03:46.60572 IFO new target: ALL_NODES_OK
2015-12-28T19:03:46.60645 IFO executing state: WAITING_FOR_NODES_OK (20)
2015-12-28T19:03:46.60664 IFO [WAITING_FOR_NODES_OK.enter]
2015-12-28T19:03:47.92328 IFO EDGE: WAITING_FOR_NODES_OK->ALL_NODES_OK
2015-12-28T19:03:47.92369 IFO calculating path: ALL_NODES_OK->ALL_NODES_OK
2015-12-28T19:03:47.92443 IFO executing state: ALL_NODES_OK (100)
2015-12-28T19:03:47.92461 IFO [ALL_NODES_OK.enter]
 

Plots attached:

1. ETMY filter (approx. 3 seconds)
2. PSL Diode Chiller Low Alarm (30 minutes)
3. Both channels plotted together, showing the time in between where H1 is undistrubed, but not in Observe (23 minutes total, approx. 15 minutes of "unofficial undisturbed" time)

Summary

I updated the quad matlab model parameter file with SolidWorks estimates of the test mass and PUM rotational inertias. Previously these values were output from a fitting algorithm using the measured resonance frequencies, see log 10089.

The updated parameter files are quadopt_fiber.m (the generic quad file) and h1etmy.m. quadopt_fiber.m is the general quad file, h1etmy.m is specific to H1ETMY. They are currently identical since we have the most measurements from H1ETMY. Both live in this directory

.../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production

Discussion

This update was done because there has been some discussion on the accuracy of the test mass inertias in the model. The solidworks mass values for the test mass and PUM agree with the measured weights to 0.2% and 0.07% respectively. This doesn't tell us the error for the inertias, but since they are small, it is a good sign. Previosuly, the inertias were chosen by the aforementioned fitting algorithm. These had differed from solidworks by 2% in roll (I3x) and yaw (I3z), and 7% in pitch (I3y). Further, Shivaraj pointed out that the pitch inertia from the fit was smaller than the yaw, which can't be true due to the flats on the optic. The assumption is that the solidworks estimates are more accurate.

With the updated inertias on the PUM and test mass, I made a new fit of the model, floating all the d's of each stage, the inertias of the top mass and UIM, the spring stiffnesses, and the vertical stiffness of the fibers. I wouldn’t put too much faith into the accuracy of these values. The best we can do is try to make a model that matches the information we have. If we ever get new or better information (such as good L-P coupling data) we can update the model with that then.

The plots in the first pdf show a comparison of the measured H1ETMY transfer functions to the previous model fit and the new one. They all match pretty well. The new fit appears to match the top mass L to P measurement better.

The plots in the second attached pdf show the ratios of the new fit to the old fit for the damped L to L TFs from all stages to the test mass. The damping loops were imported from those currently running at LHO. These ratios all appear to be within 10% of unity.

For reference, this is a summary of the history of model revisions on the svn:

* generate_QUAD_Model_Production.m

rev 7359: now reads foton files for main chain and reaction damping

rev 7436: Changed hard coded DAMP gains to get the correct values for LHO ETMX specifically.

rev 7508: Restored damping filter choice for P to level 2.1 filters as opposed to Keita's modification. Cleaned up error checking code on foton filter files, and allowed handling of filter archive files and files with the full path.

rev 7639: renaming lho etmy parameter file

rev 7642: Adding custom parameter file for each quad. Each one is a copy of h1etmy at this point, since that one has the most available data.

rev 7646: added ability to read live filters from sites, and ability to load custom parameter files for each suspension

rev 7652: updated to allow damping filters from sites from a specific gps time (in addition to the live reading option)

planned future revision - seismic noise will progate through the damping filters as in real life. i.e the OSEMs are relative sensors and measure the displacement between the cage and the suspension.

* ssmake4pv2eMB5f_fiber.m

no recent (at least 4 years) functional changes have been made to this file.

* quadopt_fiber.m

- rev 2731: name of file changed to quadopt_fiber.m, removing the date to avoid confusion with Mark Barton's Mathametica files.

- rev 6374: updated based on H1ETM fit in 10089.

- rev 7392: updated pend.ln to provide as-built CM heights according to T1500046

- rev 7912: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit.  Same as h1etmy.m.

* h1etmy.m

- rev 7640: created the H1ETMY parameter file based on the fit discussed in 10089.

- rev 7911: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit. Same as quadopt_fiber.m.