Following instructions written by Keith Thorn at LLO 
(https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=21998)

I was able to get psinject to run under control of monit.  The same problem existed here as at LLO, including an existing psinject that monit didn't know about.  The ~hinj/Details/pulsar/RELEASE points to O1test at LHO as at LLO.

I have left psinject turned off (via monit) for now.

Joe B, Chris B

Command will be:

awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 SBER8V3_H1.txt 1.0 1129673117 -d -d  > log_stoch.txt

H1 has been locked for the past ~8 hours in Observing Mode.  Just cruising along listening for gravitational waves.

TITLE:  10/23 OWL Shift:  07:00-15:00UTC (00:00-08:00PDT), all times posted in UTC     

STATE of H1:  In Observation at 77Mpc for 4+hrs.

Incoming Operator:  Travis

Support:  Nutsinee, Landry (chatted on phone about status), Kiwamu (on-call, but not called)

Quick Summary:  H1 running in special state for 45mHz Blend Filters due to high useism with low gain on the 

Shift Activities:

• ETMy Saturations:  6:57, 8:40
• 9:23 Nutsinee oscillation seen on tidal, and asc stripTools 
• 9:27 Lockloss
• 10:56 Observation Mode
• 11:21 Corner Station Temperature is LOW Verbal Alarm
• 13:43 GRB

GRB Alarm.

1. This is a real alarm.  A GRB was detected by the SWIFT satellite.  It is listed as E194829 in GraceDB & has been designated as GRB 151023.
2. Stand down time from 13:43 - 14:43UTC
3. Talked with Brian S. at LLO and confirmed they also received the alarm.

In response to Corey's alog I have turned on an additional heater in the LVEA.

HC2B has been set to 9ma or one stage of heat. The discharge air is responding so I know the heater is working.

The power outage earlier this week has messed up our FMCS trending capability and Bubba and I have been trying to sort this out. There are a few bad data samples which mess up the plotting routine and apparently no way to delete these data points according to our vendor!. For the interim we can use data viewer while at LIGO but from home it is difficult to see trends.

LVEA Low Temperatures For Last Three Evenings

Have had a few "CS temperature is low" Verbal Alarms.  Looking at trends (see attached 7-day), it seems like we've had dips in temperature for the last (3) nights.  Sending Bubba & John an email.

H1 Status

Other than the lockloss and slow recovery, H1 has been doing decently at 76Mpc.

Overview

As Nutsinee was beginning to head out, she noticed (9:23) oscillations on tidal signals & ASC signals.  H1 then had a lockloss within 4mins (see Nutsinee's Lockloss post).  Spent quite a bit of time trying to get back with a mix of different issues.  

ALS troubles

During the 2nd & lock acquisition attempt, saw that the ALS had troubles.  Alignment looked fine, but the arms would oscillate and then H1 went DOWN.  Tried staying DOWN for a while to let mirrors calm down, but not sure what the problem was here.  Eventually, H1 made it through this step, but spent on the order of 15-25min just in ALS.

ISS 2nd Loop "Not Great"

Once ALS issues were behind us, H1 had locklosses at various points during guardian states.  On about the 3rd attempt after ALS issues above, made it all the way to ENGAGE_ISS_2ND_LOOP, but was stuck here on the order of 15-20min.  Nutsinee pointed me to Kiwamu's alog for when we have troubles during this state & we followed Kiwamu's procedure for engaging the ISS by hand.

NOTE:  While we were at this state the ISS diff power was just under 9%.  We tried adjusting the slider to lower this to no avail.  After engaging by hand, this went up, and then came down to about 8.2%.

SDF Differences:  LSC ARM INPUT MATRX 2_2

Once we were at NLN, noticed (2) SDF differences for the LSC.  These were related to an LSC ARM Input Matrix Element 2_2.  The value was 0, but SDF wanted it to be 14.  So we Reverted the two channels, but we actually had to click "Load Matrix" for this Matrix to actually change the element.  Not sure why Guardian missed this.

Summary

So, went through Guardian the way TJ instructed me to at the end of his shift (involving going Manual during ENGAGE_ASC_PART3 & staying in Low gain for ASC SOFT----this is all for running in the special state with Blend filters for high useism).  

Corey, Nutsinee

Few minutes before the lockloess we noticed DHARD, IMC-F_OUT16, and ETMY DRIVEALIGN was running away on the FOM. No earthquake report from USGS within half an hour before/after the lockloss. No seismic activity in the earthquake band. I've attached some lockloss plots below. All the pretty much ASC signal were running away exacpt DSOFT and CSOFT.  WITNESS channels show BS, ETMX, ETMY, PRM, and SR2 running away. I've (temporarily) added IMC-F, ETMX and ETMY DRIVEALIGN to the plot.

Although it's technically Fri morning, I did check on the PSL chiller since its on the Thursday section of the Operator Check Sheet.  Tonight I topped it off with 100mL of water (it was last topped off yesterday with 150mL).

TITLE:  10/23 OWL Shift:  07:00-15:00UTC (00:00-08:00PDT), all times posted in UTC     

STATE of H1:  Observation Mode at 77Mpc

Outgoing Operator:  TJ

Support:  On Call-->Kiwamu

Quick Summary:  TJ walked me through the the special state H1 is in (running 45mHz blends & manual shuffling in the ENGAGE ASC PART3 step); this hub bub is all related to the elevated useism (it's currently around 0.03um/s).  TJ/Sheila felt the Blends were possibly having issues with the Soft Loop FM1 gains, so they are kept ON for this lock (FM1, -20dB gain is ENABLED).

We'll see how we do during the night as to whether we should run with these filters ON or OFF

• Title: 10/22 OWL Shift: 23:00-7:00UTC (16:00-00:00PDT), all times posted in UTC
  

• State of H1: Observing at 78Mpc
  

• Support: Sheila, Jeff K, Jim W.
  

• Shift Summary: Worked for awhile to overcome the useism, eventually seemed to find a working configuration, but lost lock an hour before the end of my shift.

• Incoming Operator: Corey G.

•  

• Activity Log:

• 23:37 Keita to LVEA to electronics racks
• 23:53 Keita back
• 00:00 Keita out again
• 00:12 Kiwamu to CER
• 00:15 Kiwamu and Keita back
• 00:18 Start Initial Alignment
• 00:24 Kiwamu in and out to check lights
• 00:54 Initial Alignment done, starting locking
• 01:57 Switched to 90mHz blends on BSCs
• 02:04 Switched to 45mHz blends
• 02:43 Started switching blends while in DC_READOUT
• 03:45 Nominal Low noise
• 04:17 Observing
• 06:06 Lockloss
• 06:49 Observing

H1:LSC-POP_A_LF_OUTPUT had an oscillation grow.

Useism still high (peaks at 0.5um/s)

Possible eathquake that was trending down that may not have helped (4.5 in Argentina says USGS).

Winds < 10mph

I will post Lockloss plots after I get this up again.

After about 9 hours of being down, we are now in Observing. BUT we are not is our normal configuration setting. Here is what worked/changed:

• Saw that the ASC PRC2 was pushing PR3 and kept running away with the lock. This is a sign of bad alignment so I did an Initial Alignment.
• We played with blends in different configurations and tried to change them while in DC_READOUT(partially unsuccessful, read below for more). The 45mHz blends seemed to work best with this high useism.
• Kept the SOFT loops in Low Gain (accepted in SDF). These are normally changed to high gain in the ENGAGE_ASC_PART_3 step in the ISC_LOCK Guardian. We did not edit the Guardian with these new settings, we just manuvered around in manual and did some by hand. Sheila suggested that we could turn them to high gain later in the locking sequence, but risk dropping the lock. So after waiting in NLN for ~10min, we decided to leave them in low since the range seemed just as stable and the glitches were not any more frequent.

The current configuration settings that are different than our normal are: SOFT loops in low gain and BSC blends at 45mHz. Future operators may need to change these back for future locks, depending on conditions. (OpsInfo tagged)

More on the blend switching

The 90mHz blends seemed to not do well with the ALS during the high useism. Looking at the ALS X/Y power on Striptool, there is visible movement in the power while in the 90's, but not while in the 45Hz. After the the Engage ASC steps, it seemed as though the 45's would become unstable. Sheila thought that the 90's may be better after we have transitioned off of ALS, so we thought to try to switch blends after getting to DC_READOUT.

When we got to DC_READOUT I first changed the ETMX X blend from 45 -> 90. This worked with some disturbance seen in AS90. I moved on, with Jim W giving me some advice, and changed ETMX Y to 90. This also didn't drop us out of lock, but the AS90 trace wasn't getting any better. Next ETMY Y -> 90, same as the last two. And finally what did us in was ETMY X -> 90. Not sure if it just couldn't hold the instability anymore or if that particular dof just didnt agree with the change.

Since the ends were in 90 and the CS was in 45, I figured let's try it like that. ALS power looked slightly better than with 45 all around, but much more jagged and not as consistent of an oscillation as with all 45's. This configuration couldn't make past the first couple of steps, similar to all 90's.

Switched back to 45's and stayed here. When we got to DC_READOUT the next time all seemed well and we moved on to NOMINAL_LOW_NOISE.

TJ, Jeff K, Jim W, Sheila

We are on 45 mHz blends today, with microseism and wind that TJ will post. The first attached screenshot shows that today at least the optical levers show more motion when we are on 90 mHz blends. 

We are also running with low gain in the SOFT loops today.  We struggled with locklosses when turning up the gain in these loops (similar story in alog 22447).  This seems to be related to the 45mHz blends, because the gain peaking with these blends is unfortunately near something a little unstable in these loops with their nominal gains.  So it may be that we are best off to use low gains when we are on 45 mHz blends (FM1 off for all soft loops)  screen shot is attached.  Operators can probably let these come on in ENGAGE_ASC_PART3 and then manualy turn them off.  If this is not woking you can call me, we can add a check on the blend configuration in the guardian.  With low gain in these loops we do not have the large fluctuations in power build ups we had when we locked with 45 mHz blends in the past. The attached screenshot shows that when we used the 45 mHz blends in the past (22477), there were rather large fluctuations in POP LF (500 counts peak to peak)  Tonight with low gain in the SOFT loop the fluctuations are more like 100 counts peak to peak.  

For a good part of the afternoon we were struggling to lock because the recylcing gain was too low when the PRC2 loop came on.  We already had a check on recycling gain in the guardian, but the threshold was set too low, 31.5 (or 1050 in TR_X and TR_Y).  I increased the threshold to 34.5 (or 1150 in TR_X and TR_Y).  This means that the operators are now more likely to get an error message in ENGAGE_ASC_PART1 that says "Low recycling gain! Align by hand or redo Intial alingment"  If this happens people can try to align things by hand, (adjusting PR2 would be a place to start, maybe ITMs).  If we loose lock it is probably best to just redo inital alingment.  

We were also loosing lock when the SRC loops were re-engaged after being turned off for the CARM offset reduction. 22554 We edited the guardian to leave them on all the time, because I don't think that was really the problem with the locklosses durring CARM offset reduction. The good news is that we didn't have any trouble with these locklosses today, despite high ground motion. 

I have taken a look at the recalibrated C01 frames for LLO and LHO.  See LLO alog  21961 , for the LLO version of this.

I grabbed the H1:GDS-CALIB_STRAIN (online) and H1:DCS-CALIB_STRAIN_C01 (recalibrated) data from the Caltech cluster, and generated the ratio of the spectrum at time which we expect both the C01 and C00 to be correct.

The data is stored in the calibration svn at:
https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Runs/O1/H1/Results/C01

It was generated by the script:
https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Runs/O1/H1/Scripts/CHECKS/compare_C00_C01.m

Below I attach a ratio of the strain between C01 and C00, from GPS 1128249017 (Oct 7, 2015 10:30 UTC).  This is a time period when the front end models and GDS pipeline matched our best knowledge of the instrument and were used to generate the recalibrated C01 data.
 
This should be compared to LHO alog  22291 , first attachment.  Similarly to LLO (see LLO alog  21357 ), we believe the small 2% differences at low frequency are due to minor mismatches in the front end filter realization against our full calibration model which the GDS filters match well against.

The large narrow frequency 5% differences are around the DARM calibration line (at 37.3 Hz) is similar to LLO (see  21961 ).  The other higher discrepancy is I believe related to the front end filtering handling of certain notches, which Kiwamu had to reduced the Q for in the calibration.  See LHO alog  21332  and  22738 .

Lockloss @ 18:46 UTC.  Cause is currently under investigation.

Because there have been some indications the now missing HAM3 .6hz line was electronic, I checked that it was still gone after this morning's power outage. It is, so far. Attached spectra are the GS-13s.