Most likely due to a 6.2 EQ in Afghanistan.

O1 day 98

model restarts logged for Thu 24/Dec/2015
2015_12_24 21:00 h1nds1
2015_12_24 21:16 h1nds1

freeze up of h1nds1, looks like the first reboot didn't take?

here is a plot of the free disk space on /ligo for the past three weeks showing the results of yesterday's work. Note that the regular drops in free space happen on Tuesday morning's, it would be good to know what we do during maintenance which takes about 10GB of disk.

I accidentally clicked the Commissioning button that was next to a screensharing window I was working in at 16:16:44 UTC.  I returned it to Observe at 16:16:57 UTC.  Data in this interval should be fine other than the Intent Bit.

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

Incoming Ops: Travis

Support: Daniel

Shift Summary: BNS range was a mess for most of the night. Now that we're entering Christmas morning things are looking much better now. DARM has stopped glitching for the past hour and I haven't seen a visual evidence of RF45 glitching for a very long time (not in the timeseries plot, not on the FOM since 8:30 as I have mentioned in the other log). Santa must have flown by....

Activity:

08:02 Daniel went in the LVEA to wiggle some cables. We were desperate.

Looks like the same one that TJ got an alarm for on Dec22. The value has been flat since Dec22 afternoon. Is it real?

Looks like RF45 has stopped glitching since ~8:30 UTC but BNS range continued to suffer until ~11:40 UTC. The first plot shows timeseries of the BNS range and RF45 AC CTRL channel over the past 10 hours. The second plot shows normalized timeseries (I used Daniel's dtt template with zpk([0;0],[20;20],1,"n") filter) of RF45 and DARM when RF45 is clearly responsible for the range drop (8:00 UTC). The third plot shows the same channel with DARM glitches but not RF45 (9:00 UTC). The forth plot shows the same thing but more recent time. It's not clear to me that RF45 has been responsible for the messed up range from 8:30-11:40 UTC.

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

Outgoing Ops: TJ

Quick Summary: RF45 has been acting up. Daniel went in to wiggle some cables but it didn't help. Went back to Observing at 8:17 UTC.

• TITLE: 12/24: 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC"

• STATE Of H1: Observing at 9Mpc (currently) for 9hrs

• SUPPORT: Daniel

• SHIFT SUMMARY: Good shift till about 6:25 UTC when the RF45 noise began to act up. It hasn't left us since.

• INCOMING OPERATOR: Nutsinee

• ACTIVITY LOG:

• 05:14 H1nds1 hard restart
• 06:25 RF45 noise begin

Briefly showed up around 06:25 UTC, and now we just got another ~15 second burst. Maybe it will go away...

nds1 died and needed a hard reset.

I have increased the heater control at HC1B from 9 to 11ma.

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.