The LHO DCS diskcache server froze this morning around 5 am PST. After several reboots failed to solve the problem, Dan Moraru reboot the main samfs file server too, and we restarted services, including condor, rds, and hoft aggregation and some Disk2Disk processes. All DCS services should be working again, and H1 summary pages should catch up soon.

SudarshanK, ChrisB, DaveB

We installed inverse anti-imaging filter on pcal hardware injection path, channel H1CAL-PINJX_HARDWARE, at FM3. The SDF screen and ODC bit are changed accordingly.

This filter will produce a better estimate of the  hardware injection  at higher frequencies.

Lockloss at 18:11 UTC

The winds have picked up slightly (20mph) and then the ETMX ISI starting moving in the X direction. It settled down for a moment, but then came back and after about 30 secs of some large swings, we lost lock. Jim W wants to try some different settings on the next go around.

Attached are the results of the charge emasurements taken earlier in the week.  Things look OK in charge land - some of the data points have a larger error bar likely because of added foot traffic at the end stations during maintenance.

The output power of the front end seems to have a ~20 minute oscillation in it.  Seems to
coincide with crystal temperature fluctuations.  The crystal fluctuations however do not
coincide with the flow rate.  I cannot determine if it is due to fluctuations in the crystal
chiller flow rate because we do not have enough resolution but the crystal chiller flow rate
appears to be constant.

The fluctuations do not seem to coincide with humidity either.  Nor room temperature.
Possibly fluctuations in the NPRO output power (FrontEndPowerOscillation6.png), it is
hard to tell.  There seems to be a small coincidence with the NPRO second pump diode
(FrontEndPowerNPROD2.png).  There does not appear to coincidence with any of the other 
NPRO signals monitored.

I should mention that the laser power mentioned here is prior to the power stabilisation
sensing.  The same fluctuation is not apparent in the reflected signal from the pre-modecleaner.

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

• STATE Of H1: Observing at 78Mpc for 16+hours

• OUTGOING OPERATOR: Travis

• QUICK SUMMARY: He had a very quiet shift, this is the same lock as the one I left Jeff with yesterday so it doesn't seem that the ISI swinging has returned.

Title: 11/12 Owl Shift 8:00-16:00 UTC (0:00-8:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: Smooth sailing all morning. Only a handful of ETMy saturations, but none related to any RF45 issues.  Wind is calm and microseism trending down slowly.

Incoming operator: TJ

Activity log:

10:40 GRB alert

13:45 GRB alert

15:41 Noticed an ETMy timing error on the CDS overview screen had popped up

15:43 Chris to X arm for beam tube sealing

Observing the entire shift so far.  A few ETMy saturations, but not related to any RF45 glitching.

Activity Log: All Times in UTC (PT)

00:00 (16:00) Take over from TJ
08:00 (00:00) Turn over to Travis 

End of Shift Summary:

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

Support: Jim W.

Incoming Operator: Travis

Shift Summary: A good low noise high range shift. IFO has been locked in Observing mode for the past 8.5 hours. Seismic activity has been low all shift. Microseism had been flat centered around 0.4 um/s for most of the shift, it has been slowly rising for the past 2 hours, and is now centered just below 0.5 um/s. The wind is calm to a light breeze (0 – 7mph). There were 3 ETM-Y saturations during the shift. There were no RF45 or ETM ISI CPS problems.    

I took a quick look at the swept sine measurements Chris made earlier today, in order
to derive a transfer function from H1:CAL-INJ_CW_OUT to H1:GDS-CALIB_STRAIN,
using the same matlab script written recently to analyze L1 measurements>.

Attached are spectrograms of H1:CAL-INJ_CW_OUT and H1:GDS-CALIB_STRAIN for
the period of the measurements, along with the derived transfer function
(see LLO alog entry above for explanation of graphs). Although there is an
odd bump in magnitude response at 610 Hz (due to compensating for a notch 
at a BS 2nd violin harmonic?), things are otherwise smooth between 200 and 1400 Hz,
albeit with phase wrapping at a bit more than 1000 Hz. This measurement seems
at odds with Matt Pitkin's CW hardware injections recoveries (summary plot attached), as is
the case for the recent L1 measurements. 

On the one hand, one could wonder if perhaps the swept sine just isn't sampling the frequency range
finely enough to catch everything that affects the particular frequencies where CW injections
are made, especially given the complexity of the inverse actuation filter Jeff posted here. 

On the other hand, the swept sine points were chosen to coincide almost exactly with
CW injection frequencies (575 and 849 Hz) for which discrepancies between injection 
recovery and the transfer function measurements seem to occur. 

Matt has double-checked and triple-checked the phase definitions he uses in 
injection recovery. So the discrepancies in phase for pulsar 1 and 2 phase remain
mysteries (for both H1 and L1). 

As discussed elsewhere, these lingering discrepancies suggest (to me, anyway) that we 
should simplify CW injections either by using PCAL with its considerably simpler IAF
or by dispensing entirely with an IAF in the current ESD injection mode (i.e., rescale
each CW injection amplitude by the point value of the inverse of the measured
actuation function).

Figure 1 - Spectrogram of H1:CAL-INJ_CW_OUT
Figure 2 - Spectrogram of  H1:GDS-CALIB_STRAIN
Figure 3 - Derived transfer function from H1:CAL-INJ_CW_OUT tp H1:GDS-CALIB_STRAIN
Figure 4 - Summary of CW hardware injection recoveries

   A good first half of the shift. IFO has been locked in Observing for the past 5 hours with a range around 78 to 81 Mpc. Seismic activity is quiet. The microseism centered around 0.4 um/s. Wind around the site is a light breeze (4-7mph). 

  There have been 2 ETM-Y saturations. There have been no ring up of the ETM ISI CPSs.      

In my previous entry 23283 I only reported results for 3rd and 4th harmonic because for the 21 hours of data analysed there the damping filters of the fundamental and second harmonics for the test masses were activated.

As described in 23085 on 2015-11-04 we were allowed to turn off the damping filters for the fundamental and 2nd harmonics of ITMX and ITMY and we managed to get a 10 hours continuois lock of the detector. This happened from (UTC) 2015-11-04 06:35:00 to (UTC) 2015-11-04 16:15:00. (See attached plots of the damping filter GAINs nulling during the interval of interest and a detector state graph showing lock during the time of interest).

I looked at channel H1:OMC-DCPD_SUM_OUT_DQ downsampled to 8192Hz in order to be able to handle the considerable amount of data.

The attached spectrum of the 10 hours of data on a 0.5mHz resolution and 33 averages identifies (in red) the dominant peaks at the fundamental violin mode frequencies corresponding to the violin modes previously assigned to ITMX and ITMY (as per 17610).

Like in 23283 I used a line tracker (iWave) to track the frequency and amplitude of each fundamental mode of the violin modes of ITMX and ITMY. Attached are the summary plots for the locked modes at the top is the frequency as a function of time and at the bottom is the Log of the amplitude as a function of time. A first order polynomial is fitted to Log(Amp) in order to obtain the Q of that mode.

Looking at the iWave plot results we observe that very few modes show a clear ringdown (these are highlighted in bold on the table below), also some modes show actually an amplitude increase:

            Frequency                       Q                Delta_Q

   1.0e+09 *

   0.000000500053540                   0                   0

   0.000000500211188                   0                   0

   0.000000501090622   1.099263893173578   0.001406678163595

   0.000000501206991   0.387149689289317   0.000525686495200

   0.000000501255024                   0                   0

   0.000000501451642   0.836253670431456   0.000578382636001

   0.000000501607755                   0                   0

   0.000000501684000                   0                   0

   0.000000501748284                   0                   0

   0.000000501811170   0.672273711595517   0.000373649058032

   0.000000502622036                   0                   0

   0.000000502745387   0.287935668815574   0.000095512884649

   0.000000503007120   0.296739931868312   0.000046580713516

   0.000000503119439                   0                   0

   0.000000504805141                   0                   0

   0.000000504871717                   0                   0

NOTE: The Q of the trustworthiest ringdowns in this analysis are between 0.3 and 0.8 e9, in comparison with the 3rd and 4th harmonic measurements in 23283 which range 0.6 and 1.5 e9.

O1 days 53,54

model restarts logged for Tue 10/Nov/2015
2015_11_10 11:55 h1susauxex
2015_11_10 11:55 h1susauxey
2015_11_10 12:00 h1broadcast0
2015_11_10 12:00 h1dc0
2015_11_10 12:00 h1nds0
2015_11_10 12:00 h1nds1
2015_11_10 12:00 h1tw0
2015_11_10 12:00 h1tw1

Maintenance day, susaux model changes. DAQ restart: resync to susaux, add sdf chans to edcu.

model restarts logged for Mon 09/Nov/2015

no restarts reported

This is a belated report on comparing DARMOLGTF and PCAL2DARMTF measurements taken on Oct 28, 2015 (LHO alog 22928) vs. DARM model.

The comparison showed that measured sensing function residual have reduced to under 1% in a band [~30 ~500] Hz when comparing to a κtst and κC corrected DARM model. Also κ_pu is close to unity and cc pole frequency calculated from cal lines just before we started taking the TF measurements is 10 Hz higher than the one around October 15 TF measurements, and closer to 341 Hz, a value in the canonical DARM model. For previous kappa values see reports from previous similar analysis: LHO alog 22571, LHO alog 22552, LHO alog 22071.

Kappas used in the kappa corrected parameter file H1DARMparams_1130094627_kappa_corr are given below (notice that at this point we only apply κ_tst and κ_C). These are 60 minute mean kappas calculated from 60 s FFT SLM data starting at GPS 1130091000.

κ_tst = 1.012713
κ_pu = 1.003557
κ_A = 1.015523
κ_C = 0.980036
f_c = 344.154643 [Hz]

An updated comparison script and parameter files for the most recent measurements were committed to calibration SVN (r1759):

/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1130094627.m (r1751)
/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1130094627_kappa_corr.m
/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/CompareDARMOLGTFs_O1.m
/trunk/Runs/O1/H1/Scripts/CAL_PARAM/plotCalparameterFromSLMData.m

Comparison plots were committed to CalSVN (r1779):

/trunk/Runs/O1/H1/Results/DARMOLGTFs/2015-10-28_H1DARM_O1_cmp_*.pdf

Title:  11/11/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 locked at NOMINAL_LOW_NOISE, 22.1w, 77Mpc.  

Outgoing Operator: TJ

Quick Summary:  IFO is in Observing mode. Seismic activity is below 0.1 um/s. Microseism is centered around 0.4 um/s, however the slope is upward. Wind is calm to a gentle breeze (0 – 10 mph). 

yesterday I commited all outstanding svn local modifications to the userapps repository. This mainly covered filter files and observe.snap files, plus yesterday's susaux model files.

yesterday evening the observe.snap files for lsc,asc, omc,iscex and iscey were modified to accept the changes made when the dark offset script was ran. I have just checked these into SVN. Perhaps channels which are changed via MEDM or scripts should not be monitored by SDF, even though they are changed infrequently.

My first LSC fellow shift, and it didn't disappoint.

Arrived at 8am PST with IFO coming up to ~78 Mpc. Quiet running until a couple of ETMY DAC saturations. The GPS times of saturations are:
1131299869
1131301016
My understanding is that this is a frequently observed glitch, but the mechanism is not well understood.

After LLO lost lock, Chris was doing some opportunistic injections requested by the CW group. Unfortunately, not all of the injections were completed when H1 lost lock.

During the next lock stretch, while there were no observed ETMY DAC saturations, an unfortunate oscillation developed at 13:48 PST (21:48 UTC), observed strongly in H1:ISI-ETMX_ST1_CPS_X_LOCATION and also observed in H1:ASC-DHARD_Y_OUTMON/H1:ASC-DHARD_P_OUTMON. This continued for several minutes, looked to be settling down, but then increased to the point that we decided to try a test increase on the DHARD gain (we took H1 out of observing mode before this test). This was unsuccessful and H1 fell out of lock.

Following the lock loss, H1:ISI-ETMX_ST1_CPS_X_LOCATION continued to oscillate for ~10 more minutes before suddenly settling down without input from the operator. Investigations are ongoing by local site experts.

H1 has now resumed operating at ~78 Mpc.

• TITLE: "11/11 DAY Shift: 16:00-00:00UTC (08:00-16:00 PDT), all times posted in UTC"

• STATE Of H1: Observing at 79Mpc for almost an hour

• SUPPORT: Keita, Evan G, Jim W, Nutsinee, Cheryl

• SHIFT SUMMARY: Had a few issues with the ETMX ISI  swinging around. This seemed to also have been my problem with relocking yesterday. After lockloss, I would just wait for it to settle and then begin the normal relocking efforts.

• INCOMING OPERATOR: Jeff B

• ACTIVITY LOG:

• 16:08 Joe - To Xarm beam sealing
• 17:50 Karen - To mech room
• 18:04 Karen - Out
• 18:51 Odd 100Hz hump in DARM, and the RF45 noise seemed to pick up very slightly. This lasted only about 30 sec.
• 19:22 Lockloss - See alog
• 20:22 Observing
• 21:15 - Joe to Xarm beam sealing
• 21:54 - Start of odd ISI movement, this will later cause a lockloss
• 22:01 - Control signals look as though it will break lock at any moment so we added 3dB to the DHARD gains (suggested by Nutsinee)
• 22:02 - Lockloss
• 23:23 - Joe - back
• 22:31 - PRMI to DRMI transition Failed
• 23:18 - Observing

Observing at 79Mpc

After the last lockloss, I let the IFO sit in DOWN and waited for the ETMX ISI relax back to normal. I then resumed locking, and only had one hiccup where I had to adjust the recycling gain by hand during ENGAGE_ASC_PART1. This went well and after waiting for violin modes to damp a bit, we are at Nominal Low Noise and Observing.

An investigation on teh reason for the last lockloss is still ongoing.

I have turned off the violin mode damping filters for IX and IY by zeroing their gains. Patrick accepted these into SDF so that we can go to observing.

This is meant to be temporary, i.e., for this one lock only.

The next time the interferometer comes into lock, the Guardian will turn on the normal violin mode damping settings. These settings will appear as SDF diffs (two on IX, and six on IY). These should be accepted into SDF.

We do not expect these modes to ring up during the course of the lock. However, if the mode height on the control room DARM spectrum around 500 Hz rises above 10⁻¹⁶ m/rtHz, the damping should be turned back on:

1. Make sure the ramp times for the damping filter modules are at least a few seconds (currently they seem to be set to 10 s).
2. The filters should already be configured to provide the right damping phase, so changing the filters should not be necessary.
3. Start typing in gain settings. Refer to the values listed below. If the violin mode amplitude is much much higher than usual (e.g., it's off the scale on the control room DARM spectrum), it is wise to start with a small gain (e.g, gain of ±1) in order to make sure the suspension drive does not saturate. Then you can increase the gain in several steps, until the nominal setting is achieved.

A screenshot of the nominal IY damping settings is attached (I didn't take one for IX).

ITMX:

• MODE3 gain: −100
• MODE6 gain: +200
• all others zero

ITMY

• MODE1 gain: −200
• MODE2 gain: −200
• MODE3 gain: +100
• MODE4 gain: −50
• MODE5 gain: +400
• MODE6 gain: +50
• all others zero