Looking at the spectrograms and glitchgrams on the summary pages for January 2nd there seems to be some interesting behaviour from about 10 - 35 Hz at LHO.  The noise drops in this band over the course of the day and glitches in this band become less frequent as well.  It does not seem to correlate to wind speed or ground motion, at least not in an obvious way.  Looking at the ground motion BLRMS page of the summary pages, there do seem to be some spikes between 4 - 6 UTC, in multiple bands.  However these spikes are relatively short-lived and the noise in the spectrograms starts before that.  I've attached a few images showing noise and glitches from the band of interest..  The plots are also visible on the summary pages.

    Noticed SDF was showing a difference for EY ECAT PLC2. The fiber temperature control had switched off at 12:50. Called Sheila. While talking to Sheila noticed two other channels related to fiber temperature  were cycling on an off. Sheila said this would not be a problem maintaining lock but could be a problem for relocking. 

   Sheila noticed that the Fiber Wrong Polarization percentage was close to its limit of 40. It was between 37 and 39 percent. This should not be a problem while we are locked, but should be addressed at the next lockloss.       

Noticed dewar vapor pressure indicating 10 psi which is lower than what I had remembered for the nominal value for this dewar -> Exhaust check valve bypass opened, LLCV bypass opened 1/2 turn ccw, LN2 appeared exiting pipe after ~45 seconds -> let fill for ~2 minutes

    IFO has been locked and Observing for the past 6.5 hours. PSL power is holding at 21.7W, range has been moving around a bit due to several ETM-Y saturations, but is mostly in the high 70s to low 80Mpc. These saturations do not appear to be associated with RF45 glitches. The wind is running at a light to gentle breeze (4-12mph). It is currently snowing and starting to accumulate. Seismic plots are mostly flat and within normal operating bands. The EY Y-axis in the 0.03-0.1Hz band has been climbing over the past 2 hours. Microseism looks normal and is centered around 0.3um/s.      

O1 day 106

model restarts logged for Fri 01/Jan/2016 No restarts reported

   Transition Summary:
Title:  01/2/2016, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)
	
State of H1: 16:00 (08:00), IOF up in Observing mode for last 2.5 hours. Range and power are normal. Environmental conditions are good. 
 
Outgoing Operator: TJ

• Title: 1/2 OWL Shift: 08:00-16:00UTC (00:00-8:00PDT), all times posted in UTC
  

• State of H1: Observing at 78Mpc for 2.5hrs
  

• Shift Summary: One lockloss from an unknown cause, but I got it back up with only a few minor hickups.

• Incoming Operator: Jeff B

• Activity Log:

• 11:42 - Lockloss
• 13:29 - Observing

Had to run through an initial alignment where Mich dark locked would not lock, then some trouble with the PRMI to DRMI transition. But now we are up and observing!

Not sure of the cause; the control signals all looked good, nothing on the seismometers, wind low, need to further investigate after locking.

• Title: 1/2 OWL Shift: 08:00-16:00UTC (00:00-8:00PDT), all times posted in UTC
  

• State of H1: Observing at 78Mpc for 6hrs
  

• Outgoing Operator: Travis S
  

• Quick Summary: Wind <8mph, useism 0.3um/s, CW inj running, PSL 21.7W.

Title: 1/1 Eve Shift 0:00-8:00 UTC (16:00-24:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: Started the shift with the PSL down and being worked on by Jason and Corey (T. Vo was covering OPS duties).  Within the first hour of my shift, they had completed their work and I began initial alignment.  After a surprisingly straightforward alignment and locking, made it to NLN at 2:29 UTC.  Other than some excess noise from 10-30 Hz, range has been the typical ~80 MPc for the past 6 hours.  Environment is calm.

Incoming operator: TJ

Activity log:

In addition to the PMC diff that Betsy took care of here, I accepted a diff for H1:IMC-REFL_SERVO_IN1GAIN (setpoint -2.00, epics -1.00) in order to proceed to Observing.  I (actually T.Vo did, since he was already logged onto another workstation) also switched the omcparams.py starting voltage back to -24, which worked to get past the same problem described by Corey here.  Note: I did NOT commit the change in omcparams.py to the SVN.

svn up at .../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production

All current model features are summarized in a table in G1401132.

Update to existing features

The main change in existing features is that the top mass damping now sees both the suspension and the cage, as in real life because we use OSEMs. Consequently, if you input seismic noise to a damped suspension it will enter both mechanically as usual, as well as through the damping loops. See Seismic_Noise_Propagation_2016_01_01.pdf. Page 1 shows longitudinal transfer functions from seismic noise to the test mass with and without the OSEMs seeing the cage. The second page shows the ratio of these transfer functions. Note that the ratio is greater than a factor of 2 at 4.5 Hz. Beyond 10 Hz the maximum is about 20% at about 10.5 Hz.

Two new features 

1. Additional inputs and outputs added to reflect the relative nature of the OSEMs - i.e. they measure relative displacements and actuate between two points

2. Suspension point reaction forces

The discussion above is one consequence of the first new feature. Another is that you can now make transfer functions between seismic noise and the top mass OSEMs, which is dramatically different from the seismic noise to top mass transfer function. See Seismic_to_Top_OSEMs_2016_01_01-2.pdf. These are obtainable in the model with the new 'toposem' field in the 'out' structure given by the generate_QUAD_Model_Production function.

The second new feature is that there are now outputs for the suspension point reaction forces on the ISI. These are obtainable in the model with the new 'suspoint' field in the 'out' structure given by the generate_QUAD_Model_Production function. These reaction forces allow us to dynamically couple the quad model to the ISI model. Thus, if we wanted, we can make one big ISI-SUS model.

Under-the-hood updates

This update includes significant under-the-hood modifications to how the pieces of the model are put together. Essentially, Simulink files now define the connections and signal flow, where previously this was all done with append/connect commands in the generate script. The motivation for this change is to make the model more extensible and maintanable by humans. The append/connect commands had become virtually unreadable with the dozens of inputs and outputs now in the model. Now someone can look at a more intuitive graphical representation in a simulink file to read or modify how the model is layed out.

There are 4 simulink files defining the 4 possible layouts of the quad model:

For reference, this is a summary of the history of model revisions in 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.

rev 7920: big update - added sus point reaction forces, top OSEMs act between cage and sus, replaced append/connect command with simulink files

* 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.

Observing for 2 hours at 75-80 MPc.  There seems to be a bit of excess noise below ~30Hz in DARM which seem to correlate with some excess noise in PRCL and MICH.  Wind and seismic are both calm. 

In getting back to Low Noise, I had to change the OMC PZT starting voltage in omcparams.py back to -24 from the -30 that Corey changed it to earlier today.  I did NOT commit the changes to SVN since they seem to be in flux.

Because the H1:PSL-PMC-REF slider was adjusted to land on a value with much larger precision than the SDF file can deal with, it was in alarm out to the 10e-16 digit which could not be cleared with the ACCEPT button.  The correct way to clear this bug is to write the epics slider to a smaller precision value (truncate it to the 10 e-8 or something digit).  However, we are all the way back to Nom LOW Noise, and didn't want to risk this minute slider adjustment - SO, we set the channel to be NOT MONITORED until the next lock loss, when we should:

- Set this channel (H1:PSL-PMC-REF) to be MONITORED again in SDF

- Type in the SDF setpoint value (1.18615) into the slider value and check that it is no longer in error on SDF.

J. Oberling, C. Gray

At 21:01:51 UTC the PSL NPRO shut off (see attached trend of NPRO diode power, NPRO power, and PSL power watchdog), reason unknown.  The PSL watchdog tripped 3 seconds later at 21:01:54 UTC, so the NPRO definitely shut off first.  After Corey's phone call I drove to the site to reset the PSL.  The only thing I found wrong was that the NPRO power supply was ON, but not sending power to the NPRO (key ON, power supply OFF).  The UPS the NPRO power supply is plugged into did not show an error, and there were no other obvious indications that something went wrong, so I turned the NPRO back ON.  It powered up without issue, and we turned the 35W FE laser on from the LDR.  After fiddling with the PMC and FSS (as usual after a laser shutdown), everything with the PSL was locked and operating properly.  It is still unknown why the NPRO shut off.  At this point I suspect a glitch with the UPS; we have seen this behavior before, where a glitch in the UPS causes the NPRO to shut off with no idication of what went wrong.

At this point we noticed the FSS TPD was down to ~1V, which is getting close to the point where ALS becomes unhappy.  A 7 day trend of the RefCav TPD is attached.  At that rate of decay the FSS might not have lasted until maintenance day on 1-5-2016, so we decided (with M. Landry's permission) to go in and do a quick adjustment of the RefCav alignment.  I will detail that in a follow up alog.