TITLE: 04/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventative Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY: H1 just lost lock at the end of in-lock charge measurements (SWAP_BACK_ETMX), ending a 38 hour lock. Maintenance activities have begun.

• Wind and microseism are low
• All other systems nominal

Workstations were updated and rebooted.   This was an OS package update.  Conda packages were not updated.

TITLE: 04/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
H1 is still locked and 30 hours.
Over the past 8 hour we have dropped from Observing twice for short durations due to SQZ_Manager and Camera_Servo Guardians.
We are currently Observing and intend to continue to do so until 1500 UTC.

LOG:

The Camera_servo Guardian, was getting stuck on Dither, Then it stalls.
More specifically ASC-CAM_YAW1_INMON is STUCK.

Which appears to be the BS (26) on h1digivideo2. Contacted Dave to restart the port that the camera is being provided Power Over Ethernet on.

While Dave is doing that Naoki is Running a Scan_SQZANG to optimize the SQZ angle.

Camera is now restarted and we are now in Observing!

TITLE: 04/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:
H1 is still locked but we have fallen into commisioning due to the SQZ ISS Pump.
Looking at Alog 70050 I have requested LOCKED_CLF_DUAL_NO_ISS
I changed the opo_grTrans_setpoint_uW from 80 to 50...

Reloaded and then noticed that the comments said that 50 was too low. I was still reading comments when Naoki got onto TeamSpeak and saved the day.
He said that 70 may be appropriate but 50 is too low due to the SQZ system being tuned for 80. please see alog 72044 .

H1 Is back in Now back in Observing.



 

TITLE: 04/29 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 13mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:
H1 is Locked for 22 hours and is currently Observing. The Plan is to continue this lock throught the night.
 

TITLE: 04/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Mostly quiet observing day today with just one brief break for some measurements. H1 remained locked the whole shift; current stretch is just over 22 hours.

• 21:19 - Dropped observing for commissioning measurements
  • In/out of NLN_CAL_MEAS twice during this time
• 21:58 - Resumed observing

LOG:

I reran the A2L script today during our small on the hop commissioning window.

The new gains have been entered in the guardian via the a2l_gains dictionary in userapps/isc/h1/guardian/lscparams.py

'FINAL':{
            'P2L':{'ITMX':-0.9646, #+1.0,
                   'ITMY':-0.4071, #+1.0,
                   'ETMX':3.2767,
                   'ETMY':4.8886}, #+1.0},
            'Y2L':{'ITMX':2.7253, #+1.0,
                   'ITMY':-2.0093, #+1.0,
                   'ETMX':4.7658,
                   'ETMY':0.9094 },#+1.0},# Centered on the optic #removed offsets from EY IX IY 220705 gm jd ec
                    }#spots that are the center of the optic
            }#close a2l gains dict

and accepted in SDF in OBSERVE.snap, see attached images.

[Jennie, Sheila, Gabriele]

We retuned the SRCL FF, by doing the usual injections. While fitting, we just tried to change the gain of the filter that was running a bit, and that was enough to get an improved subtraction. The new filter module (FM2) is active and in guardian.

H1 dropping observing as of 21:19 UTC for ~30 minutes for quick feedforward measurements.

Jennie W, Annamaria, Sheila

Annamaria suggested we check ASC-POP_A and B trends during the time we got a drop in optical gain before last maintenance Tuesday, as a result of which we had to change our SR2 and SR3 alignment.
We don't see a large change in the sums or the pitch and yaw over the drop in range and optical gain between 18:33:47 UTC on the 22nd and 12:3803 UTC on the 23rd.

From the plot it can be seen that the optical gain dropped by about 5% over this period.

The range dropped by ~10 Mpc.

ASC_POP_B_SUM dropped by 0.1%.

ASC_POP_B_PIT dropped by 0.08%.

ASC_POP_B_YAW dropped by 4.9%.

ASC_POP_A_NSUM dropped by 0.06%.

ASC_POP_A_PIT dropped by 1.3%.

ASC_POP_A_YAW dropped by 0.7%.

Looking at the zoomed out version is seems these are within normal drifts in previous locks.

State of H1: Observing at 146Mpc

Quiet morning of observing, wind picked up slightly over the past few hours. H1 has now been locked for over 18 hours.

Full report available here.

Summary:

• Daily observing duty cycle: 66.7%, 32.1%, 61.5%, 57.7%, 70.6%, 82%, 75.1%. Week average: 63.7%
• Range typically hovered between 150-160 Mpc, occasionally pushing a few Mpc above 160
  • Thursday Apr 18 saw abnormally low sensitivity in the middle of the day, unclear why it happened but was fixed after switching FD squeezing off/on
• Occasional high winds throughout the week which depressed sensitivity or led to lock-losses/difficulty re-locking. Microseism mostly calm throughout week
• Nearby earthquake on UTC April 20 did not cause lock-loss
• On Sunday noticed increased rate of glitches near 4 kHz, difficult to spot in a spectrogram
  • Generated omegscans which show that the glitch time/frequency structure does not extend down to lower frequencies
• Saw high-frequency broadband noise on some days lasting about 1 hr after the start of each lock segment, intermittent noise at ~33 Hz potentially related to ground vibrations in CS
• Several summary page (range, strain) plots on Friday Apr 19 are blank after 6:30 UTC due to frame issues

Mon Apr 29 10:08:54 2024 INFO: Fill completed in 8min 51secs

Gerardo confirmed a good fill curbside.

TJ, Ryan S.

We've been occasionally seeing some SDF differences come up after relocking related to the ALS Y REFL servo (most recently in alog77478), where the input gain and compensation boosts are being turned off during SHUTTER_ALS. After not finding any Guardian that does this, we decided it must be Beckhoff-controlled, but still wanted to understand why this only happens during some lock acquisitions and not others. When doing some trending, we saw that the gain and compensation boosts are turned on when the arm cavity is locked and turned off again when unlocked, but not turned off when shuttered (everything gets cleaned up after a lockloss). In some cases, after switching actuation from ALS WFS to DHARD, the green arm alignment drifts to the point where an arm (usually Y) unlocks and the input gain and compensation boosts are turned off before ALS is shuttered. As seen in the attachment, there's a ~5 second gap between when the arm nodes move to their SHUTTERED states and the light is actually shuttered, which we tracked down to a 6 second wait time in ISC_LOCK and believe is a remnant of old code. This wait time has been lowered from 6 seconds down to 1 second as there's really no reason to wait here anymore.

SDFs are correctly set and ISC_LOCK.py changes have been committed to svn, but the node will need to be loaded when next out of observing.

Another picket fence issue at 03:37 UTC, I think the third in the past few weeks. I restarted the process on nuc5.

There had been a suggestion (passed to me by Sheila) that we should measure the beam positions on SRM and SR2 after the big move that we made this week (which is summarized in alog 77427). 

We don't have a premade script to do this like we have for the test masses, so I just did it by hand.  One at a time, I put in a line using the ADS screen to SR2 or SRM pit or yaw, then changed the corresponding A2L element to minimize the line height in CAL-DELTAL_EXTERNAL.  I was also watching SRCL_IN1 and SRCL_OUT, but the lines disappeared in the SRCL signals before they disappeared in the DARM signal, so I just used DARM. 

All A2L values for SR2 and SRM had been 0.0, so I'm not going to bother putting in a 'before' column in the table below since they were all the same value of zreo.

After finding those values, I ran /opt/rtcds/userapps/release/isc/common/scripts/decoup/BeamPosition/CalcSpotPos.py to get from A2L coefficient to beam spot.  This script had been made for IMC optics, but since SRM and SR2 are the same style, the calculation should be the same.  Reminder of where this calc comes from (it's referenced in the script): alog 31402.

We don't have any 'before' measurements to compare to, but at least we now have some amount of information of where we are on these optics after the big move.

I'm pretty sure that these new A2L values can only be good, so I've accepted them in both safe and observe snaps for SR2 and SRM (see first and second attachments, only 2 rows per SDF table are accepted).  These A2L gains for non-test mass suspensions are not under guardian control, so this should be good enough to keep them in place.

In the table below, the Cal-Deltal line reduction factor ends up really just being the ratio of the peak height in DARM before I started doing anything to that dof, and the noise level.  To do a better job of measuring this, I would have had to increase my excitation amplitude, but that didn't seem important enough to do given the limited commissioning time we had. 

I don't have time right now to think through the whole left-vs-right sign convention (it's discussed in alog 31402), but it does look like we're rather 'diagonal' in the SRC now, since the signs of the spot positions are opposite for SR2 vs SRM (eg one positive P2L and one negative P2L means the beam is on opposite sides of center).