Following on from Patrick's entry regarding the reference cavity transmission falling below 0.9 V ...

Attached are two plots of the reference cavity transmission and the Laser Room temperature as measured
by a sensor on the table, along with an image of the various spots from the pre-modecleaner and reference
cavity.  Since I didn't save any previous camera image, I will simply have to go on memory.  The
pre-modecleaner reflected spot looks like it's drifted to the right in yaw (as you look at the image).
The reference cavity reflected spot has moved up in pitch.  Both alignments were tweaked during last
Tuesday's maintenance period.

Also attached is a plot of the U100 mirror mount drift due to temperature and similar data from the
Newport website for their Suprema series mirror mount.  The plots suggest that pitch suffers with
any temperature variation, although it's hard to quantify given the ~0.5 degC temperature change.  The
plot for the U100 mount, suggests that the pitch adjustment does not recover.

The degradation in the transmission signal seems to coincide with colder temperatures of late.  Prior
to last week the last time the alignment was tweaked was mid-July.

Another possible reason might be that the reference cavity is slipping in its suspension, for whatever
reason.  Given the fact that the transmission can almost always be corrected for by a pitch alignment
I don't think this is a likely reason.  The reference cavity is the same as that used for the Initial
LIGO H1 PSL and I do not recall any mention of frequent alignment tweaks to preserve the transmission
signal.

Observing 11:58 UTC at 80Mpc.

Had some sissues with finding the 45MHz carrier on the OMC, see alog23821.

Violin modes took a longer time than usual to damp. Wasn't any one in particular, all of them seemed to have started out pretty high.

At ENGAGE_ASC_PART3, I noticed that the OMC_LOCK was not in READY_FOR_HANDOFF. Re-requesting it did not seem to help. There was a notification that it could not find the 45MHz sideband. I went through the code and saw that adjusting the OMC-PZT2_OFFSET slider while watching H1:OMC-PZT2_MON_DC_OUT and H1:OMC-DCPD_SUM_OUT could work. I thought I got it to where it needs to be, I manually moved past the FIND_CARRIER step and all seemed well until DC_READOUT.

The initial voltage scan for the PZT was changed from -30 to -24 on Nov 18, I found the sidebands to be at an offset voltage of 25.25V. Not sure if I even really got it, but perhaps this initial value needs to be changed slightly?

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

• STATE Of H1: Observing at 80 Mpc for 7hours.

• OUTGOING OPERATOR: Patrick

• QUICK SUMMARY: Cold as usual, wind is low, useism = 0.5 um/s, LVEA/VEAs lights off. TPD flashing on Ops Overview, this wasn't noticed until after going into observing but should still be okay.
  

TITLE: 11/29 [EVE Shift]: 00:00-08:00 UTC (16:00-00:00 PDT), all times posted in UTC

STATE Of H1: Observing @ ~ 80 MPc.
SHIFT SUMMARY: Quiet since locking at NLN. 45mHz ISI blends made all the difference. Winds have increased slightly to between ~ 0 to 10 mph. Earthquake band has come down slightly to between ~ 0.02 and 0.1 um/s. No significant change in microseism.
SUPPORT: Kiwamu
INCOMING OPERATOR: TJ
ACTIVITY LOG:

00:52 UTC Switched ISI blends to 45mHz
01:12 UTC NLN
01:28 UTC Observing

No problems since going to observing. SUS ETMY saturations on occasion.

The strip chart was freezing on and off and the camera images were frozen. I did not restart the strip chart because it is the same as the one on nuc2.

Kiwamu, Patrick

Switching the ISI blends to 45 mHz made all the difference. Accepted the SDF differences for the blends. (See attached screenshots). No problems as soon as we did that.

There is a yellow box with 'TPD' written in it flashing in the PSL area of the Ops overview. Kiwamu looked at the medm code and it appears when H1:PSL-FSS_TPD_DC_OUTPUT < 0.9. It is currently around 0.86.

There is still a testpoint open on H1LSC.

TITLE: 11/29 [EVE Shift]: 00:00-08:00 UTC (16:00-00:00 PDT), all times posted in UTC

STATE Of H1: Lock acquisition
OUTGOING OPERATOR: Corey
QUICK SUMMARY: Kiwamu is here and has been working with Corey to help try to relock.
From the cameras:
The lights are off in the LVEA.
The lights are off in the PSL enclosure.
I can not tell if the lights are on or off at mid X and mid Y.
The lights are off at end X.
The lights are off at end Y.

The 0.03 - 0.1 Hz (earthquake) seismic band is between ~ 0.02 and 0.1 um/s.
The 0.1 - 0.3 Hz (microseism) seismic band is between ~ 0.2 and 0.8 um/s.

The winds are between ~ 0 and 5 mph.

The ISI blends are on Quite_90.

From pinging:
CDS WAP is off at the LVEA.
CDS WAP is on at mid X.
CDS WAP is on at mid Y.
CDS WAP is off at end X.
CDS WAP is off at end Y.

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

STATE of H1:  Lock Acquisition

Incoming Operator:  Patrick 

Support:  Kiwamu over the phone and then

Quick Summary:

  Rough shift which hopefully just related to issues with alignment (i.e. input pointing restoration?).  Right now we are waiting to see how H1 proceeds through lock aquisition.  Kiwamu has been here to help & is here to assist Patrick.

Shift Log:

• 14:30 arrived to cover part of the OWL shift 
• Continued Lock Acquisition
• Moved on to make another small change in input alignment & started Initial Alignment...but had issues (as noted earlier).
• ~21:15 Kiwamu arrives to help with H1
• During acquisition ran PRMI alignment at 22:32 (& it locked within a minute)
• Locking DRMI, but has been dropping shortly after...troubleshooting continues.

Attached is a plot of the last 24hrs covering restoration attempts for the Input Alignment.  Additionally there is a plot also looking at the last 30days.

A bit of a frustrating morning.

Since Alignment was decent enough to get through DRMI, I opted to look at Input Alignment again.  Patrick pretty much restored the IM4 Trans Pit/Yaw to where they should be (good thing!).  I thought the yaw could be moved a little more though.  I decided to move the IM3 in yaw a bit.  (Talked with Kiwamu and he felt this was good to try).

Since the input pointing was changed, I then started an Initial Alignment.  Unfortunately, I ran into issues at the beginning with ALS.  I could have sworn both ALSx & y were fine at first, but after waiting a few minutes for control signals to converge, I noticed ALSy was in a completely bad alignment state.  I spent way too much time trying to get an alignment back, could never get much above 0.5 & when I did WFS drove the alignment off.  After talking with Kiwamu, he suggested taking guardian to LOCKED NO SLOW NO WFS & tweak on ITMy & ITMy.  Finally, made some progress here and took the arms up to 1.05, went to INITIAL ALIGNMENT (which enables wfs), and Y-arm looked great....

...but then ALSx all of a sudden looked ugly.  It had a 0:0 mode, but it's power was oscillating from 0.4 -0.8 with a period of 6-7sec.  (on the Tidal strip tool, the ALS x & y REFL control signals are oscillating with this period.  useism doesn't look bad (under 90 percentile & there's no wind).  Asked whether the tidal issues Patrick had last night could be an issue here, but since we aren't fully locked it should not.  So moving on...

Oh, and within a few minutes, I lost ALSy again!!

SO:  Going to work on ALSx & then ALSy (probably with no WFS).  Kiwamu said another knob I can use is the ALS WFS GAIN for each arm, if needed.

OK, back at it.

Had a sick OWL shift operator last night.  Although Nutsinee offered to accept a call to come in to cover the shift last minute, Mike & I opted to not call someone in at short notice with freezing condition.  At the time, H1 was in the middle of a long lock, but unfortunately H1 dropped out of lock before midnight.  Patrick fought valiantly and stayed a bit beyond his shift (see his alogs for the play-by-play); I talked with him before going to bed & opted it would be better to get sleep before coming in early.  

Walked in at 14:35UTC (6:35am), to H1 trying to lock DRMI, and it did within a few minutes.  Right now it is stuck trying to go to REDUCE CARM OFFSET, but there is a Guardian message of:  NO IR in arms!!