Sun Aug 13 10:15:26 2023 INFO: Fill completed in 15min 22secs

TITLE: 08/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 8mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY: H1 has been locked for 31 hours. Dropped out of observing twice at 09:09 and 09:22 from the TCS CO2 X laser losing lock. On both occasions observing resumed automatically within 2 minutes. (Tagging TCS)

• CDS, SEI, SUS, dust all look good

TITLE: 08/13 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: Austin
SHIFT SUMMARY:

Overall a quiet and calm night! Going on 23hrs 21mins Locked.

Timeline:

23:00 Detector in Observing and Locked for 15.5 hrs

00:00 Verbal alarm for WAP On in LVEA, EX, and EY, but it isn't actually on (this has happened a few times recently)

4:58 Earthqake mode activated due to earthquake from Papua New Guinea
5:08 Back to CALM

LOG:

no log

We have been Locked for 19hrs 20mins. At 00:00UTC, we did get a notification on Verbals that WAP was on in the LVEA, EX, and EY, which it wasn't, but it's been quiet besides that.

However I did notice that the temperature of Rack 2 in the Y EBay has been rising in temperature over the past day, starting possibly around 8/11 23:19UTC (attachment1), and the current temp reads as almost double the nominal temp. Attachment2 gives a zoomed out timeline, showing that besides the power glitch that resulted in a partial power outage from August 5th (72000) and a period of time 17 days ago(unsure of the cause of that), the rack temperature has not gotten this high in multiple months. Tagging PEM and SYS (not sure if SYS should be tagged).

TITLE: 08/12 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 12mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Taking over for Ryan S. Detector in Observing and Locked for 15.5hrs.

TITLE: 08/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: H1 has been locked for 15 hours; quiet the entire shift. Only out of observing a handful of times due to SDF diffs (below).

• Dropped observing for 3 seconds from syscssqz SDF diffs at:
  • 16:35, 17:36, 17:59, 20:43

LOG:

No log for this shift.

State of H1: Observing at 148Mpc

H1 has been locked for 11 hours. Quiet morning with the usual Saturday tour groups passing through. We've dropped out of observing three times so far from SDF diffs on syscssqz; the rate of this seems to be higher than normal today (tagging SQZ).

Sat Aug 12 10:16:34 2023 INFO: Fill completed in 16min 29secs

TITLE: 08/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 has been locked for over 7 hours. Looks like we dropped observing for 3 seconds at 14:00:37 for two SDF diffs on syscssqz, but observing was resumed automatically (tagging SQZ).

• CDS, SEI, SUS, dust all okay

TITLE: 08/12 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Austin
SHIFT SUMMARY:

Lost lock 30 minutes ago(72168) and currently locking back up. ALSY was having trouble holding a lock but I was able to help it along.

23:00UTC Observing and Locked for 3hrs

23:41:09 Taken out of Observing due to SDF Diffs in syscssqz. I used this as a chance to reload the H1LSC model to load in the changed Elenna had made (72163)
23:42:34 I put us back into Observing

LOG:                                                                                                                                                                                                                                                                                                                                                                                                                                                                 

Lockloss at 6:28UTC

Closes FAMIS #25594, last checked in 71978

Corner Station Fans (Attachment1)
Corner station fans all well within range. The line ~2.5 days ago was due to the corner station fans shutting off from the Fire Alarm(72097).

Outbuilding Fans (Attachment2)
All outbuilding fans well within range.

Other observations
-On August 5th at 18:07UTC, something happened to MY_FAN1_270_1/2 that caused MY_FAN1_270_1 to go from ~0.7 to ~0.3.

During Tuesday maintance this week, we moved the upper (inner) beam of the Xend Pcal system down from it's nominal location by 2.5 mm on the surface of the ETM (see aLog entry 72063).

The observed change in the Pcal X/Y comparison should give a measurement of the vertical component of the displacement of the interferometer beam from the center of the ETM.  This displacement, denoted by the b_y, is given by

Delta_XY =  c/2 * b_y * M / I

where Delta_XY is the observed change in the Pcal X/Y comparison (after minus before), c is the change in the vertical position of upper Pcal beam, the factor of 1/2 results from only moving one of the two Pcal beams,  b_y is the vertical component of the displacement of the interferometer beam from the center of the optic, M is the mass of the optic, and I is the moment of intertia of the ETM for rotation about an axis parallel to the face of the optic and and through the center of the face of the optic.

Thus the interferometer beam displacement can be estimated by b_y  = 2* Delta_XY / (c * M / I).

For the Xend ETM, M / I = 0.94e-4 / mm^2 and c = - 2.5 mm.  Thus b_y = -0.85e4 * Delta_XY mm

Using DTT to analyze data (1024 sec FFTs, 50% overlap, 10 avgs) during a lock stretch the day before we moved the beam, 08/07 from about 08:00 to 23:00 UTC, and after the move on 08/09 between 00:30 and 06:30 and between 11:30 and 15:30.  We observe a change in the X/Y comparison of about - 24e-4 (see attached plot).  This would indicate an interferoemter beam offset of about 20.7 mm in the positive y direction, ABOVE the center of the optic.

Info provided by JenneB (seel below) indicated that the pitch measurements using the electrostatic acutators indicate that the interferometer beam is offset by about 14.3 mm BELOW the center of the ETM.

We will look at more data from before and after the beam position move and double-check our calcuation to make sure we aren't missing a minus sign somewhere.

Next Tuesday, we plan to move the beam back to it's nominal vertical potition and offset it to the left (when viewing the fact of the optic from the BS side) by 2.5 mm to assess the horizontal component of the interferometer beam offset from center.

TITLE: 08/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 10mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Taking over for Ryan S. Observing and Locked for 3 hours.

TITLE: 08/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Shift started troubleshooting locking issues eventually tracked down to recently modified SR2/3 damping gains (see alog 72152). Two short lock stretches in the morning to do some PEM injections while L1 was down. Back to observing by early afternoon, now locked for almost 3 hours.

• 1455 Holding in DRMI_LOCKED_PREP_ASC to fix SR2/3 damping gains
• 1600 NLN; automatic acquisition after DRMI
  • Robert starting injections @ EY
• 1641 Lockloss, seemed fast, cause unknown
• 1740 Back to NLN, automatic acquisition
  • Continuing EY injections
• 1900 Lockloss, seemed fast, cause unknown
• 1924 While relocking, locklosses at CHECK_AS_SHUTTERS and FIND_IR
• 2009 NLN, automatic acquisition
• 2028 Observing

LOG:

Follow up on previous tests (72106)

First I injected noise on SR2_M1_DAMP_P and SR2_M1_DAMP_L to measure the transfer function to SRCL. The result shows that the shape is different and the ratio is not constant in frequency. Therefore we probably can't cancel the coupling of SR2_DAMP_P to SRCL by rebalancing the driving matrix. Although I haven't thought carefully if there is some loop correction I need to do for those transfer functions. I measured and plotted the DAMP_*_OUT to SRCL_OUT. transfer functions. It might still be worth trying to change the P driving matrix while monitoring a P line to minimize the coupling to SRCL.

Then I reduced the damping gains for SR2 and SR3 even further. We are now running with SR2_M1_DAMP_*_GAIN = -0.1 (was -0.5 for all but P that was -0.2 since I reduced it yesterday). Also SR3_M1_DAMP_*_GAIN = -0.2 (was -1). This has improved a lot the SRCL motion and also improved DARM RMS. It looks like it also improved the range.

Tony has accepted this new configuration in SDF.

Detailed log below for future reference.

Time with SR2 P gain at -0.2 (but before that too)
from    PDT: 2023-08-10 08:52:40.466492 PDT
        UTC: 2023-08-10 15:52:40.466492 UTC
        GPS: 1375717978.466492
to      PDT: 2023-08-10 09:00:06.986101 PDT
        UTC: 2023-08-10 16:00:06.986101 UTC
        GPS: 1375718424.986101

H1:SUS-SR2_M1_DAMP_P_EXC  butter("BandPass",4,1,10) ampl 2
from    PDT: 2023-08-10 09:07:18.701326 PDT
        UTC: 2023-08-10 16:07:18.701326 UTC
        GPS: 1375718856.701326
to      PDT: 2023-08-10 09:10:48.310499 PDT
        UTC: 2023-08-10 16:10:48.310499 UTC
        GPS: 1375719066.310499

H1:SUS-SR2_M1_DAMP_L_EXC  butter("BandPass",4,1,10) ampl 0.2
from    PDT: 2023-08-10 09:13:48.039178 PDT
        UTC: 2023-08-10 16:13:48.039178 UTC
        GPS: 1375719246.039178
to      PDT: 2023-08-10 09:17:08.657970 PDT
        UTC: 2023-08-10 16:17:08.657970 UTC
        GPS: 1375719446.657970

All SR2 damping at -0.2, all SR3 damping at -0.5
start   PDT: 2023-08-10 09:31:47.701973 PDT
        UTC: 2023-08-10 16:31:47.701973 UTC
        GPS: 1375720325.701973
to      PDT: 2023-08-10 09:37:34.801318 PDT
        UTC: 2023-08-10 16:37:34.801318 UTC
        GPS: 1375720672.801318

All SR2 damping at -0.2, all SR3 damping at -0.2
start   PDT: 2023-08-10 09:38:42.830657 PDT
        UTC: 2023-08-10 16:38:42.830657 UTC
        GPS: 1375720740.830657
to      PDT: 2023-08-10 09:43:58.578103 PDT
        UTC: 2023-08-10 16:43:58.578103 UTC
        GPS: 1375721056.578103

All SR2 damping at -0.1, all SR3 damping at -0.2
start   PDT: 2023-08-10 09:45:38.009515 PDT
        UTC: 2023-08-10 16:45:38.009515 UTC
        GPS: 1375721156.009515

Benoit, Ansel, Derek

Benoit noticed that for recent locks, the 102.13 Hz calibration line is much louder than typical for the first few hours of the lock. An example of this behavior is shown in the attached spectrogram of H1 strain data on August 5 - this is the first day this behavior appeared. Ansel noted that this feature includes a comb-like structure around the line that is only present in the H1:GDS-CALIB_STRAIN_NOLINES channel and not H1:GDS-CALIB_STRAIN (see spectra for CALIB_STRAIN and CALIB_STRAIN_NOLINES on Aug 5). This issue also visible in the PCAL trends for the 102.13 Hz line. 

We are not sure if the excess noise near 102.13 Hz is from the calibration line itself or another noise source that is near the line. However, the behavior has been present for every lock since 12:30 UTC on August 5 2023. 

Lockloss @ 1:50 UTC, was noticing some instability in the ASC loops on the CR screen, particuarlly for the SRC and HARD loops, though can't say for certain if this caused the lockloss.

[Keita, Nutsinee, Sheila, Jenne]

We went in to HAM6 today, and believe that we have finished all ISC/SQZ related tasks, and are ready to begin closeout procedures tomorrow.  (Betsy, who has the final say, will write an alog or talk to the relevant folks for the actual final start of closeout.)

After Richard opened the PSL shutter and Ed locked the IMC, we pretty easily were able to get beam onto AS_C.  To check our alignment, Sheila aligned the Michelson, then made sure we were still centered on AS_C.  Since we don't have arms, we just assumed that the input beam is pretty close to its usual, and only adjusted ITMs and BS for MICH.  Around this time, Keita noticed that there was a bit of a 'tail' on the beam as seen on an IR card.  Sheila walked SR2 and SR3 until the tail was gone, but we were still centered on AS_C.  After this we aligned SRY (restored SRM, misaligned ITMX) to get good fringes, so that we could trust the SRM position for squeezer-related work.  We also took the IMC offline (which misaligns MC2) to remove the main IFO beam, injected the SQZ beam, ran the squeezer's ASC loops, and noted that the ZM1 actuators were very close to the edge of their ranges (as Sheila made a quick note about in alog 52405).  We deferred action on this until after the main IFO path checks were complete.

Once we were happy with all of our alignments we brought the main IFO beam back and Nutsinee took photos of the beam in several different places, including the septum window, the position on OM1, the position relative to the fast shutter's wire, the position on OM2, the position going into and returning from the OMC shroud, and some photos to ensure that we don't see any obvious scattered light at the shroud apertures. 

Having completed this, and deciding that it was still quite early in the day, we began work on relieving the ZM1 actuator.  Sheila noted that the pico that is on/near the OFI is closer in Gouy phase to ZM2 than ZM1, so would not be a satisfactory way of relieving ZM1.  Sheila and Keita went in and adjusted the last steering mirror on the VOPO platform that sends the beam to ZM1 about 1/4 of a turn in yaw, clockwise if you are standing at the endcap. After I damped the VOPO we re-ran the squeezer alignment loops, and found that instead of having outputs of nearly 29k the ZM1 outputs were at most about 7k.  Excellent!  We note that the ZM2 outputs are around 22k, but this is the same that they were during O3a, it hasn't drifted, and if we need to we can relieve ZM2 using the pico, so we are leaving things as-is.

With these 2 sets of checks and work, I believe that we are done with ISC/SQZ work in HAM6.  Nutsinee will comment with her photos.