All buildings are beginning to respond to the lower outdoor temperatures so Bubba and I have turned on heaters in both end stations and the LVEA.

One stage of HC5 is now on in the LVEA. This will impact the input chambers the most. The response appears to be ~0.5 F.

The End stations have variac control so these have been incremented from 4ma(off) up 8.5ma

TIME: 16:39UTC, 9:39PT

STATE OF THE IFO: Unlocked

EXPLANATION:  The IFO did lock and made it past ENGAGE_ASC_PART3, but then another earthquake arrived, and broke the lock, and ground motion is high.

Video0's striptools have been modified, and now they have a red background, due to the channels DHARD_Y and DHARD_P.

When making a change to a screen, it's important to test it in all situations.  Maybe this addition worked quite well during our long lock, but right now with earthquakes and relocking, the change to the striptools have rendered them unusable.

FOM image attached.

Following Sheila's entry (alog 21708), I've tried to figure out which locklosses where due to Earthquakes during the week of Sep 10th (ER8).

Out of the 22 locklosses seen this week, I've counted 6 locklosses due to EQs. Sheila counted 9, I'll double check my conclusions with her.

The ground velocities represent the maximum amplitude predicted by the Seismon software.  These predictions could be inaccurate by a few percents.

Six examples is not enough to do some accurate statistics, but the behavior observed during ER8 doesn't contradict the conclusions drawn from ER7 (see DCC T1500230). My conclusions were:

• Ground motion < 0.6microns/s: very unlikely to trip SEI or loose lock
• 0.6 < Ground motion < 8 microns/s: very unlikely to trip SEI but will probably loose lock
• 8 microns/s < Ground motion: would propbably trip SEI and loose lock

Note: among the 16 remaining locklosses, some of them are due to a high ground motion, but EQ is not the cause (wind? human activity?).

TITLE:  9/24 OWL Shift:  7:00-15:00UTC (00:00-8:00PDT), all times posted in UTC

12:35 H1 Lockloss (nothing obvious:  seismic quiet, and all the H1 strip tools showed nothing obvious before lockloss)

During Lock Acquisition, during 2nd locking attempt, had issues with ALS XARM:

• ALS_XARM Node, there was a Guardian FAULT:  PLL, PDH
  • Symptoms:  Xarm was flashing through all kinds of modes, & guardian was in FAULT state
  • On the PLL medm, the fiber lock temperature controls error signal was in the "Beat Note Error" state (vs "PZT Frequency").  Had no idea how to fix/clear fault, but after a while it appeared to clear up on its own & go to PZT Frequency.
• Waited for DRMI acquisition about 12-15min and then went through Sheila's PRMI procedure:

1) You can either misalign SRM using the SUS_SRM guardian, or use a new state in ALIGN_IFO called SET_SUS_FOR_PRMI_W_ALS. 

2) Request OFFLOAD_PRMI from the DRMI guardian.

• Was in the PRMI_LOCK_WAIT state for a long time (order of 15min?).  How long should we wait for PRMI to lock??

3) Once PRMI locks adjust PRM and BS alignment until you get about 80 counts on POP90 and 50 counts on POP18.  

• PRM finally locked!  PRM was moved the most, a little BS & PR2

4)Realign SRM by undoing whatever change you made in step 1.

5) Request DRMI_1F_OFFFLOADED from the ISC_DRMI guardian.

Waited for DRMI to lock again.  Several times I had a Verbal Alarm which sounded like "Slip Mode"?  What do we do about this?  It looked ugly on AS-AIR video.  Had "Slip Mode" alarms a few times while waiting for DRMI, and then the Vancouver earthquake arrived!

After recovering ISIs and ETMy, took ISC_LOCK to LOCKING_ALS, but haven't made it there yet (the guardian log keeps saying "Waiting for arms to settle").  The 0.03-0.1Hz seismic band was ramping down, but flattened out at 0.3um/s (which is over an order of magnitude from normal quiet levels).  Perhaps we should wait for this to come down to normal levels.

At 13:54 Verbal Alarm posted Earthquake.

Looks like Magnitude 5.5 from Vancouver Island at 13:49.  (Terramon did not alert us to this one.)  0.03-0.1hz seismic has increased 3 orders of magnitude (!) and 0.1-0.3Hz seismic has increased 2 orders of magnitude.

ETMy & all BSC ISIs have Watchdogs have tripped.

H1 had a ~46Hr lock that ended toward the end of Jim's shift.  He noted DRMI was looking pretty ugly.  I waited DRMI a little, but eventually gave Sheila's new PRMI procedure a try, but POP18 & POP90 remained at a flat zero and PRMI never locked.  So went through the Initial Alignment procedure (I went slow & took notes since this is something we do rarely.).  Alignment was and getting to NOMINAL_LOW_NOISE were straightforward.

• H1 was down for ~2hrs (6:30 - 8:34).
• 1hr was alignment (PRMI & Initial), and 1hr was locking
• H1 currently in Observation at ~75Mpc

Reason for Lockloss?

I saw nothing obvious from seismic signals when I walked in, everything quiet!  Jim mentioned ASAir/OMC video spots took an odd move prior to lockloss.  H1 was trending down over 6hrs before the lockloss, and Jim mentioned this could be the RF45 issue which has been coming up.

Initial Alignment Notes:

• ALS locking, no issues
  • Comm beatnote ~4.7dBm
• video0 was super slow!  So, it was slow to watch control signals settle (video0 was rebooted after getting to Observation Mode)

TITLE:  9/24 OWL Shift:  7:00-15:00UTC (00:00-8:00PDT), all times posted in UTC

STATE OF H1:   H1 in lock acquisition after ~45hr lock.

OUTGOING OPERATOR:  Jim W. 

SUPPORT:  None

QUICK SUMMARY:  DRMI looked ugly.  Tried Sheila's new procedure for PRMI, but POP90 & POP18 were flat at zero.  Proceeding with an Intial Alignment.

• Title: 9/23 Eve Shift: 23:00-7:00UTC 

• State of H1: Re-locking after loss of 46 hr lock

• Support: Most of the commissioning crew was here when I arrived, Jenne held out till 6 UTC

• Shift Summary: Mostly quiet untill lockloss at 6:30

• Activity Log:

• 23:00 ish JeffK doing PCAL measurements

• 1:00 ish I load new code for event triggers

• 5:00 ish RFAM starts acting up, range starts trending down more

• 6:30 Lock loss, no obvious cause, I start trying to recover

Durring yesterday's maintence window I made some excitations on both transmons to investigate the noise peaks around 75-85 Hz.  The main conculsions are that the coupling from TMS X L drive to DARM is bilinear while the coupling from TMSY is linear, and it seems likely that TMSX motion accounts for some significant part of the unexplained noise in the H1 noise budget (21162) even at frequencies where there is no coherence between DARM and the X QPDs. 

In the first attached screen shot you can see the DARM spectra durring some of my excitations in the upper panel and TMS QPD spectra in the lower panel.  In the QPD spectra, you can see that the X end QPDs have some excess noise compared to Y.  These spectra were from a time when I had a TMSX longitudnal injection at 75 Hz (this is the same time as the yellow DARM trace).  There is a narrow line in the X QPD spectra, but in the DARM spectrum the line that appears is about 1 Hz wide, indicating there is some bilinear coupling.  The excitation either did not show up or was very small in the QPD sums.

I also made a few injections into TMSY longitudnal which produced only narrow lines in DARM, both X and Y injections are shown at 100 Hz for comparison.  

We can attempt to make projections of this noise into DARM using the ratio or the injection line peaks or the rms of the injection peaks to estimte the coupling.  I drove longitudnally and the only good witness sensor we have is an angular sensor.  If the coupling mechanism is something like scatter off the QPDs that goes directly back into the arm, DARM would be mostly sensitive to the longitudnal TMS motion and if the QPDs are only seeing the unintentional length to angle coupling the projection from the normal level of the QPD spectra to the normal level of DARM could be an overestimate. This projection does show that this would be within a factor of 10 of DARM from about 100 Hz down to at least 75 Hz.

Perhaps when we get a chance we can try misaligning TMSX to see if we can reduce the noise in DARM this way. 

Everything quiet on site. Environment quiet. The current lock is approaching 40-some odd hours. 

L1 went out of lock. At H1 we turned off the intent bit and injected some hardware injections.

The hardware injections were the same waveform that was injected on September 21. For more information about those injections see aLog entry 21759

For information about the waveform see aLog entry 21774.

tinj was not used to do the injections.The commands to do the injections were:
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 0.5 -d -d >> log2.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 1.0 -d -d >> log2.txt
ezcawrite H1:CAL-INJ_TINJ_TYPE 1
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 1.0 -d -d >> log2.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 1.0 -d -d >> log2.txt

To my chagrin the first two injections were labeled as burst injections.

Taken from the awgstream log the corresponding times are approximates of the injection time:

1127074640.002463000
1127074773.002417000
1127075235.002141000
1127075742.002100000

The expected SNR of the injection is ~18 without any scaling factor.

I've attached omegascans of the injections. There is no sign of the "pre-glitch" that was seen on September 21.

Durring the maintence window we left the DHARD yaw boost on (21768 and 21708). There was no evidence that it caused any problems, but I was putting excitations onto transmon at the time and there were other maintence activities going on.  We'd like to check that it doesn't impact the glitch rate, so if LLO drops out of lock or if you see an earthquake on the way ( 0.1um/sec or larger predicted by terramon), it would be great if you can turn it on.  You can find it under ASC overview> ASC arm cavities, DHARD YAW FM3 (labled boost). (screenshot) 

It would be good to get more than an hour of data, so if you see that LLO has dropped it would be awesome if you could turn this on util they are back up.  

This is just a temporary request, only for tonight or the next few days.