This is for FAMIS #26366.

Laser Status:
    NPRO output power is 1.85W
    AMP1 output power is 70.39W
    AMP2 output power is 140.0W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 23 days, 19 hr 46 minutes
    Reflected power = 22.42W
    Transmitted power = 106.6W
    PowerSum = 129.0W

FSS:
    It has been locked for 0 days 1 hr and 21 min
    TPD[V] = 0.8066V

ISS:
    The diffracted power is around 3.4%
    Last saturation event was 0 days 3 hours and 1 minutes ago

Possible Issues: None reported

TITLE: 02/28 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.47 μm/s
QUICK SUMMARY:

H1 just recovered from a lockloss and has been in OBSERVING 10min.  Secondary microseism continues to come down, the last 24hrs, from peaking above the 95th percentile & winds are calm.

At 1533utc there was a Verbal for Wifi on in the LVEA, but see that it has been OFF the last hour.

ALSO:  Continue to have a note about limiting activity in the Optics Lab near the Fume Hood which had a termite nest--this is a message from the exterminator.

TITLE: 02/28 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: 1 lockloss with an automated recovery with an IA. We've been locked for 2.5 hours.
LOG: No log

The SQZ PMC PZT voltage is reporting as low and has been dropping over the past 8 hours

• 01:53 UTC lockloss there was an increase in ground motion in the 0.03 - 0.1 EY and CS axis at the time
• 02:33 Initial alignment
• 03:36 UTC Observing

01:53 UTC lockloss

Camilla Sheila Mayank

Currently QPD Trans A is used for sensing the "INJ ANG" DOF, however we want to use ADS for this DOF.

Getting up the ADS  

1. We dithered FC1 and FC2 in Pitch and Yaw

   	Optics	Freq	Amp
   Pitch 1	FC1	10	10
   Pitch 2	FC2	12	10
   Yaw 1	FC1	6	10
   Yaw 2	FC2	8	10

2. Obeserved these frequency peaks on WFS signal ( H1:SQZ-FC_WFS_A_I_SUM_OUT_DQ   H1:SQZ-FC_WFS_B_I_SUM_OUT_DQ)
3. Demodulate Signal (Modified the ADS inmatrix to choose H1:SQZ-FC_WFS_A_I_SUM_OUT_DQ for dmodulation)
4. Fixing the right demod phase : At the right demod phase one of the demod quadratures (Q) will go to zero while the other quadrature (I) will respond to the beam spot movement.
   • This is done by continuoulsy changing the beam spot location* and monitoring the change in I and Q signal. From this change we estimated the phase offset required to bring the phase to right value.
     • If both I and Q move in same direction by approximately same amount the are off by 45/135 degree.
     • if only one of the quadratures move while the other remians constant the we are closer to the righr phase.
   • *Note: We changed the P2L/Y2L coefficient of FC1/FC2 , which amounts to changing relative position between the beam and the center of optics motion.

The ADS was running and we had the error signals. However we ran out of time and hence could not close the loop. We reverted everything to the previous state. We will try to repeat this during next commissioning time.

TITLE: 02/27 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:  Currrently Observing and have been locked for 5.5 hours. Easy day today, relocking when I came in was hands off, and relocking after the next lockloss was hands off besides requesting an initial alignment and TJ lowering the SRC2 P gain during OFFLOAD_DRMI.
LOG:

15:30UTC Relocking
16:14 NOMINAL_LOW_NOISE    
16:15 Observing

16:31 Commissioning

16:36 Lockloss
    - ran initial alignment
    - glitching during DRMI_LOCKED_CHECK_ASC/OFFLOAD_DRMI - SRC2 P gain lowered from 60 to 40 in script
17:42 NOMINAL_LOW_NOISE
    - Going between NLN and NLN_CAL_MEAS for commissioning activities
20:18 Back to Observing

TITLE: 02/27 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.57 μm/s
QUICK SUMMARY:

• We've been locked for 5.5 hours
• The wind is low but the secondary microseism is high

TJ, Eric, Oli

Yesterday TJ noticed that the 3-10 Hz and 10-30Hz seismic blrms for EX X-axis shifted up at some point in time and then later in the day, the values shifted back down(attachment1). The same thing happened today. It looks a lot like something turning on and off, so I tried looking at a bunch of FMC and PEM channels to try and narrow down what could be causing it. Looking through the PEM End Floor summary pages, the noise seems to be seen in the EBAY FLOOR accelerometers much more than in the VEA FLOOR accelerometers(attachment2,attachment3). It also looks like this on/off noise started showing up on February 20th.

I plotted the EX EBAY FLOOR accelerometer channel along with the 3-30Hz blrms channels and when the blrms channels are sitting higher, the EX floor accelerometer is less noisy, which seems backwards to me(attachment4). The fan accelerometer readings also match with this movement(attchment5). There also seems to be somewhat of a correlation between the acceleration and whether the EX_AH_DSCHRG temperature is higher or lower; when the acceleration is larger, the discharge air temperature is generally lower and vice versa, but that doesn't seem to be true 100% of the time.

I also don't know if this noise couples into DARM - I briefly checked the range blrms and didn't visually see any obvious drops or rises in the different bands with the changes in acceleration. I also didn't see any glitches on the glitchgram from when things go from on->off/higher->lower output/whatever is changing. I've told Eric about it.

J. Betzwieser, V. Bossilkov, L. Dartez, J. Kissel

We've updated the calibration to account for the errors that have been in play for a while, as discussed in LHO aLOG 82804, and this after trying last week but running into issues; see 82935, and 83083. The highlights for this change are:
    (1) Employing a detuned sensing function for the first time in O4.
    (2) Updating the computational delay in the actuation stages
    (3) Updating the UIM distribution filters to match what's installed in the true ETMX_L1_LOCK bank
    (4) Making sure the ETMX L3 DRIVEALIGN GAIN is self-consistent everywhere.

The model parameter set pushed includes measured interferometer parameters based on the 20250222T193656Z measurement (i.e. (1) and (2)), but the other two changes (3) and (4) are digital filters and settings self-consistency additions that are done by hand.

The summary of the resulting change in systematic error is shown in the only attachment, with black as "before" and blue and red being the "after" where blue is with not-yet great TDCFs, and red being after 15 minutes of TDCF "burn in."

%%%%% Process %%%%
After Joe / Louis / Vlad concocted a model parameter set they were happy with, and they've tagged is as "valid," we:
(Quotes of command lines that start with 
   - "$" indicate that it's on the LHO control room workstation
   - "@" indicate that it's on the LHO LDAS cluster)

- Confirmed that I *don't* need to activate any special conda environment on the local LHO control room workstations,

- Checked the pydarm version to ensure it is what Louis wants it to be:

$ pydarm --version
20250227.0
i.e. this "tag" of the pydarm code: https://git.ligo.org/Calibration/pydarm/-/tags/20250227.0.
(Note, to find these tags, go to the pydarm homepage https://git.ligo.org/Calibration/pydarm, then use the sidebar to navigate to "code" > "tags")

- Locally checked the about-to-be-pushed calibration parameter set with
     $ pydarm export 20250222T193656Z
Here, I trusted that all the "various darm model transfer function values at calibration line frequencies" -- so called "EPICs records" had been validated by Joe / Louis / Vlad, but we went through the expect filter changes together.

- Also looked thru (a bit more) human readable .json file for the report in the report directory,
     /ligo/groups/cal/H1/reports/20250222T193656Z $ firefox foton_filters_to_export.json
and sanity checked that version of what was about to be exported.

- HIT GO ON THE EXPORT
    $ pydarm export --push 20250222T193656Z
which implicitly includes addressing highlight (2) from about, since this is in the pushed model parameter set

Addressing highlight (1) from above,
- By hand, loaded filter coefficients on CALCS model to install the new 3 DARM_ERR filters for the updated (inverse) sensing function model.

- By hand, turned on the new FM8 SRCD2N filter in the CAL-CS_DARM_ERR bank (FM9 and FM10 for the [inverse] cavity pole and optical gain were already on, since they've been used consistently throughout the O4 run).

- In the CALCS SDF OBSERVE.snap file (which is the same as the safe.snap file), I individually accepted the CAL-CS_DARM_ERR FM8 filter being ON first. THEN accepted the ~80 "EPICs records" for the "model values at calibration line frequencies."

Addressing highlight (4) from above,
- We collectively reviewed that 
    . H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN (real, in loop value)
    . H1:CAL-CS_DARM_FE_ETMX_L3_DRIVEALIGN_L2L_GAIN (CALCS replica actuation model value)
    . [actuation_x_arm] pydarm parameter tst_drive_align_gain (the pydarm parameter replica of the actuation model value)
were all self-consistently the current value of 198.664.

Addressing highlight (3) from above,
- By hand, Louis copied over the H1:SUS-ETMX_L1_LOCK_L FM6 "aL1L3" filter coefficients over into the equivalently named replica H1:CAL-CS_DARM_FE_ETMX_L1_LOCK_L FM6 filter coefficients, and load filter coefficients in CALCS model again.

Then on to restarting the GDS pipeline,
- accepted H1CDSSDF table to capture CALIB_REPORT_ID, HASH, and GDS HASH

- Joe pushed the valided report the the LHO LDAS cluster,
     $ pydarm upload 20250222T193656Z

- I logged into the LDAS cluster and made sure that the report made it to the cluster OK,
    $ ssh jeffrey.kissel@ldas-grid.ligo-wa.caltech.edu

    @ cat /home/cal/archive/H1/reports/last-exported/id
    20250222T193656Z

- Back on the workstation, I printed out the checksum for the GDS filters we were about to restart the GDS pipeline with,
    $ cd /ligo/groups/cal/H1/reports/20250222T193656Z/
    $ sha256sum gstlal_compute_strain_C00_filters_H1.npz
    3c12baf1aac516042212f233d3f2f574a8b77ef25a893da9a6244a2950c42d1e  gstlal_compute_strain_C00_filters_H1.npz

- HIT GO ON RESTARTING THE GDS PIPELINE, back on the work station
    $ pydarm gds restart
and watched the output to command line for the check-sums it spit back about what it installed, to make sure it was the same as above,
    [...]
    target GDS filter file sha256 checksum: 3c12baf1aac516042212f233d3f2f574a8b77ef25a893da9a6244a2950c42d1e
    [...]
    target GDS filter file sha256 checksum: 3c12baf1aac516042212f233d3f2f574a8b77ef25a893da9a6244a2950c42d1e
    [...]
    Connection to h1guardian1 closed.
    2025-02-27 10:39:23 PDT ==============

- Waited 12 minutes, look for data from H1 on web sites, and running 
    $ pydarm gds status

- Now started to validate whether the push worked:
    . Went to to NLN_CAL_MEAS

    . ran excitation template, 
         $ diaggui /ligo/home/louis.dartez/pcaly2darm_bb_excitation.xml &
    . Let the 300 average, ~10 minute excitation, run to completion, but ignored the answer from it, since it's a poorly calibrated DELTAL_EXTERNAL / PCAL TF.

    (A) After 4 to 6 minutes of running the excitation template, waiting for PCAL to show up in the DTT accessible frames, we ran the better calibrated template, 
         $ diaggui /ligo/home/louis.dartez/pcaly2darm_broadbands/pcaly2darm_broadbands_compare.xml &
updating the date and time within the time of the above excitation BB template, saving the answer to 
         /ligo/home/jeffrey.kissel/2025-02-27/2025-02-27_185617UTC_H1_PCAL2DELTAL_BB_300avgs.xml

    (B) Using the same "better calibrated offline measurement" template, we also gathered "before" data during from last saturday's suite.

    . We thought (A) is definitely better than before (B), but see a hump at ~70 Hz. So, suspecting it was GDS kappa's not yet burned in at a good measured value, we turned on the calibration lines for ~15 minutes, allowing GDS to compute good updated kappa values to be used during the broadband measurement.

    (C) Took it again after having calibration lines ON for ~15 minutes.
        2025-02-27_192525UTC_H1_PCAL2DELTAL_BB_300avgs.xml

The results are attached -- see 2025-02-27_192525UTC_H1_PAL2GDSL_BB_300avgs.png.
This transfer function, a measure of the systematic error in the calibration, has much less error below 50 Hz, which was the goal.
We're sad that there's still a ~2% error hump at 70 Hz, and that in inverted from before, but we consider this good enough.

The observing segment that started 2025-02-27 20:18 UTC has this new calibration.

For final clean up, I committed the following affected files to the userapps repo:
CALCS filter file
     /opt/rtcds/userapps/release/cal/h1/filterfiles
         H1CALCS.txt
CALCS SDF safe / observe file
     /opt/rtcds/userapps/release/cal/h1/burtfiles
         h1calcs_safe.snap

CDSSDF SDF safe / observe file
     /opt/rtcds/userapps/release/cds/h1/burtfiles/h1cdssdf/
         h1cdssdf_safe.snap rev 30829

We ran the a2l_min_multi_pretty.py script again today since we made changes to the OMC offsets (alog83087). There were minimal gain changes, the only one I updated in lscparams.py was ETMY P from 5.49 -> 5.52.

The range coherence template we normally use was giving odd results during the quiet commissioning times after the OMC reverting, no coherence above 20Hz is seen. Sheila mentions that this is something she has seen before and isn't physical. We ran the script expecting changes but didn't see much change in gains or to the range.

RESULTS

|      |   | Initial | Final |  Diff |
| ETMX | P |   3.23  |  3.24 |  0.01 |
| ETMX | Y |    4.9  |   4.9 |   0.0 |
| ETMY | P |   5.49  |  5.52 |  0.03 |
| ETMY | Y |   1.35  |  1.34 | -0.01 |
| ITMX | P |  -0.53  | -0.54 | -0.01 |
| ITMX | Y |   3.21  |  3.22 |  0.01 |
| ITMY | P |   0.06  |  0.05 | -0.01 |
| ITMY | Y |  -2.74  | -2.75 | -0.01 |
 

We've been having some issues with SRC2 P starting to go unstable after engaging for DRMI (alog83080, alog82997). Ryan C tested out lower the gain from 60 -> 40 on Sheila's suggestion yesterday and it seemed to work (alog83078), and I also bashed it in during a relock today that started to go unstable. Since this seems to work and the gain is brought back to 60 later in ENGAGE_ASC_FOR_FULL_IFO, we've made the change in ISC_DRMI and loaded the guardian.

J. Freed

ETMY shows strong coupling of BOSEM noise between 9-14Hz by about a factor of 20 below DARM from most sensors.

Today I did damping loop injections on all 6 BOSEMs on the ETMY M0. This is a continuation of the work done previously for ITMX, ITMY, PR2, PR3, PRM, SR2, SR3, SRM, and ETMX. As with PRM, gains of 300 and 600 were collected for SR3 (300 is labled as ln or L).  Calibration lines were off. Data was colected in two parts, as such, f1,f2,f3 had a different background than lf,rt,sd bosems.

Jennie W, Sheila

Since our range has been decreasing over the last week and the OMC QPD offsets did not definitely give us a clear gain long term in kappa C, we have reverted the change we did on Monday.

We might want to improve these offsets again once we sort out any other problems that are making larger impacts on our range currently.

See the below ndscope for how this affected the range and optical gain in the short term - this picture is slightly confusing as the calibration was being updated so kappa C will have been reset at the some point before or during our measurements.

The other two attached images show the QPD offsets being accepted in OBSERVE and SAFE snap files.

Jennie Siva Keita Mayank

Following our previous attempt  here .  We opened a new ISS PD array (S.N. 1202965).
This unit is in great condition. i.e. 

1) No sign of contamination.
2) All the optics are intact (No chipping)

We tried interfacing the QPD-cable S1203257 with the QPD but it turned out that they are not compatible.
We will look for the updated version of the QPD cable.   

Jennie W, Rick S, Mayank C, Keita K

We went into the optics lab today with the intent for Rick to review the ISS array assembly we unboxed the other day (LHO alog #82731) on which we found some particulate contaminsation and some detached parts.. Rick and Keita are unsure how the support rods (first picture) were bent during transit and they appear to have bent at the top and deformed the cover piece (D1300717) they were attached to as they came unfixed at the other end and so were just resting on the top of the QPD mount plate (D1300719). They appear to have moved around and scored the surface of this platform. Maybe this happened in transit or storage but it seems like it would have had to be a large force and Rick says the storage containers were packed in form during transit.

1st package: Base piece (D1101074-v2 S/N 004) is double-bagged in my office and I have put in a clean and bake order as this spacer is site specific in height and some of our ISS spares will have a spacer set to the L1 beam height instead so we may need to swap it out.

2nd package: Cover piece D1300717 with the spacing posts attached is not bagged properly as we probably do not want to reuse this and so it is in Keita's office.

3rd package: Array and mirror assembly with PDs still attached was wrapped in foil with dry sealed clean room wipes protecting top optic in periscope, then double-bagged. Shown in center left of this image. This will need re-cleaned if we want ot scavenge parts form it.

4th package: All the other parts from assembl y shown in this image ( apart from PD assembly, baseplate, tool pan and top cover) have been packaged up in foil and double bagged in one package. These will also need recleaned if reused.

These last two packages are stored in the cabinet that the spare ISS array units are in, situated in the vacuum bake prep area next to the PCal lab. The shipping cover and base plate for the array are also back in this cupboard.

For reference the assembly drawing can be found here.

The assembly we worked on has the dcc ref S12020967

For mirror identification, see attached.

ASC-REFL_A replacement.

The new one is D1102004-V6 S/N 005 S1301248 (ICS ASSY-D1102002-001), the old one is S/N 012, S1301242.

With the old one, one of the differential output for DC4 segment failed and we've been using H1:ASC-REFL_A_DC_SEG4_GAIN=2 to compensate. With the new one, this didn't seem to be the case and we changed the digital gain to 1.

Daniel used the external RF injection ports to confirm that RF circuits are connected.

DC centering loops worked.

Beam dump relocation.

POP_air BDV reflection was hitting the corner of the V of the V-shaped beam dump.

ASC_REFL_A and ASC_REFL_B reflection were hitting the corner of the V of the V-shaped beam dump.

We moved these beam dumps so the beam hits one of the panels, not the corner.

We weren't able to see the LSC POP_A reflection. We might want to increase the power to 10W or so after everything is done so we can at least see the flashes.

We forgot to check the LSC REFL_A and REFL_B beam dumps.
Swapping the optic in M2.

This is one of the corner mirrors in the REFL in-vac path, and we swapped the HR with the 50:50. We made sure that the wedge orientation is correct (thinner edge is close to [+X, +Y]) For the 50:50 using the laser pointer. Since HR doesn't have any wedge, we had to manually adjust M2 to restore the REFL path.

The AOI of that optic is not accurately known but I eyeballed it to be 50 degrees, and based on that I measured the reflectivity of the 50:50 in the lab before installation (alog 63404). It was about 43% reflection at 50degrees, 35.6% at 55 degrees.

In situ, we got 41.1%, so AOI is probably a bit larger than 50 degrees.

We put a beam dump to catch the ghost beam of the new optic.

Power measurements, continued.

We're done. If we can carrier-lock PRMI we could do more, but we couldn't.

Looking at the direct reflection of PRM when IMC_PWR_IN=1.001W, the power between M5 (2" HR at [-X,-Y] corner downstream of RM2) and M6 (REFL LSC-ASC splitter) is 5.96mW after we swapped the optic.

At See Craig/Ryan's comments.

Clipping check in REFL path.

Nothing was clipping in the REFL path, but the beam was pretty high on M5 (that's the 2" HR at [-X, -Y] corner), M6 (ASC-LSC splitter), L1 (1" lens in front of LSC REFL sensors) and 2" lens on the WFS sled.

The beam height was ~105mm in front of M6 (see Georgia's picture), that's ~3.4mm higher than nominal, and the beam looks uncomfortably high on L1 because of the smaller aperture but it's not clipping.

We're leaving it as is because we don't want to touch the WFS sled and the only quick solution is to make the lens higher using a shim, then use M6 so steer the beam down on the LSC sensors.

Searching for the ghost beam of the main septum viewport.

The main PSL beam is reflected by the AR of the HAM1-HAM2 septum viewport and land inside the nozzle of the PSL-HAM1 viewport at around 4 or 5 o'clock position viewed from inside the chamber. See Georgia's pictures. We haven't done anything yet, we need help from people to assemble and install nozzle baffle.

Catching a snake.

That was big.

We tested a replacement in-vac WFS for 9MHz/45MHz (ICS ASSY load D1102002-001, S1301248) in preparation for the upcoming HAM1 vent (E2200228).

Rich will write about the details, but in short we have tested that the DC power supply current was good, DC responded as expected, and RF outputs made sense for 9MHz and 45MHz. We used screw-on type ISC AM laser head for this test.

Attached show the LOW (9MHz) and HIGH (45MHz) results measured using the network analyzer. In these pictures, reference trace (green) is Q3 and the live (yellow) is either Q2, Q1 or Q4. All in all these look good in that there's no reason to suspect that they aren't working as intended.

Minor detail is that there are differences not just in overall level because the beam is not centered on the diode and the beam is not circular either, but sometimes in the shape of the traces (for example look at the Q2 HIGH at around the shoulder of 45MHz peak). We've confirmed that both the level and the shape changed when Rich rotated the AM laser head. Don't know why the shape changes but Rich mentioned that the modulation might not uniform across the beam, or maybe we're somehow saturating something (but it didn't change much when we reduced the modulation current by 10dB w/o rotating the head).