Displaying reports 1-20 of 88591.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 15:34, Thursday 23 July 2026
H1 SPI
jennifer.wright@LIGO.ORG - posted 15:34, Thursday 23 July 2026 (91221)
Re-aligned QPDB on HAM3 using M_C1

Jennie W

 

Today after verifying I didn't need to do any alignment on ISIK itself (SPI bench on HAM3), I used the picomotor on HAM2 (M_C1) to align the beam to the QPD B which resides on ISIK.

I have attached a labelled ndscope showing which channels to look at while changing the M_C1 picomotor.

The yaml files for aligning QPDA and B are saved as QPBa_picos.yaml and QPDB_picos.yaml in userapps/spi/h1/ndscope.

 

One weird thing I noticed while moving the picomotors is that while moving in small steps of 1 count (speed of the picomotor was set to 'jog' which is 50 Hz), the beam would move in the same direction on the QPD while I change direction on the picomotor.

See an example in this image.

Not sure why this happened as it was not a problem when using larger steps of 10 counts on the picomotor.

 

With steps of 10 counts the beam goes down in pitch on QPDB which corresponds to down on picomotor controls (channel Y down on picomotor controller).

To go up in yaw on QPD B you need to go right on picomotor controls (channel X up in magnitude).

Summary: QPD A and B are fairly well centred when HAM 2 and 3 are isolated now.

Images attached to this report
H1 SPI
jennifer.wright@LIGO.ORG - posted 15:10, Thursday 23 July 2026 (91219)
Recentred SPI QPDB using picomotor M

Jennie W

Summary: I didn't move M_M2  picomotor on Friday 17th July.

Last Friday (LHO alog #91124) I centred the QPDB on HAM3 spi bench using M_C1 picomotor (picomotor B  ch7 which is controller 5) on HAM2.

I wrote the log the week after and checking back in the H1:SYS-MOTION_C_PICO_G_CURRENT_X_POSITION I thought I had also moved M_M2 (CH7) on picomotor driver G.

Checking back it turns out the 2000 count jump I was seeing was just the 2000 count difference between the values stored for ch8 and ch7 when I switched the selected motor to channel 7.

See the ndscope picture where the second cursor shows when the green channel H1:SYS-MOTION_C_PICO_B_SELECTEDMOTOR changed from 8 to 7 and you can see that the the yellow channel H1:SYS-MOTION_C_PICO_B_CURRENT_X_POSITION changed up by 2000 counts.

Looking at the Beckhoof screen you can see that when ch8 is selected this stored value (-2000) appears on the screen and is not there when ch7 is selected. I mistakenly thought these were reset when the selected motor was changed.

So no re-alignment of M_M2 is needed.

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 15:05, Thursday 23 July 2026 (91220)
Ops Day Shift Summary

TITLE: 07/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Good progress today towards DRMI, see commissioning notes in alog91211. HEPI was unlocked for HAMs 1 & 2; see alog91218. Dust alarms throughout the day in the LVEA and optics lab. The LVEA remains Laser HAZARD and corner volumes are still pumping down.
LOG:

Start Time System Name Location Lazer_Haz Task Time End
14:41 FAC Kim, Dawn LVEA, OptLab - Technical cleaning 15:31
15:27 VAC Jordan MY - Reset pump 15:53
15:57 FAC Kim LVEA - Technical cleaning 16:27
16:26 SPI Jennie LVEA - Checking electronics in SUS rack 17:37
16:28 FAC Kim MX - Technical cleaning 17:29
16:35 ISC Sheila LVEA Y ISCT1 alignment 17:09
17:04 TCS Camilla OptLab - Looking for camera cans 17:20
17:20 VAC Jordan LVEA - Cleanup by CP1 18:53
18:02 SPI Jennie LVEA - Checking electronics in SUS rack 18:26
18:06 TCS Camilla, TJ LVEA - Attaching camera cans 18:58
18:51 ISC Sheila LVEA Y ISCT1 alignment 19:08
19:03 TCS Camilla, Jackie PrepLab - CHETA work 19:37
19:26 SEI Jim LVEA - Unlocking HEPI, BSC2 tests 20:03
20:46 CDS Fil LVEA - Terminating cables 21:40
21:14 SUS Oli LVEA - MC2 cable swaps 21:40
21:24 TCS Camilla PrepLab - Checking cables 21:41
21:34 VAC Jordan, Gerardo EY - Prepping for pump swap Ongoing
H1 SEI
jim.warner@LIGO.ORG - posted 14:15, Thursday 23 July 2026 (91218)
HAM1&2 HEPI unlocked, restored to running config

Over lunch I went to HAM1&2 to unlock HEPI. Not much to say, stops unlocked, signs flipped, iso gains reverted to 1 and everything turned right back on. I can now try to find time to commission St0 ff for HAM2.

 

H1 ISC
sheila.dwyer@LIGO.ORG - posted 12:41, Thursday 23 July 2026 - last comment - 16:52, Thursday 23 July 2026(91211)
PRMI checks
  POP A LF POPAIR B LF REFLAIR A LF MICH IN1 (REFLAIR A 45 Q) PRCL IN1 (REFLAIR A 9I) POPAIR B RF18
PRMI O4 200-400 200 2-10 +/-6000 +/-600 80-100
PRMI now 100 6 2.5-4 +/-20 +/-100 5
PRX O4 0.5          
PRX now 0.5          
Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 16:52, Thursday 23 July 2026 (91224)

In order to fix this alignment issue, Sheila, Keita, and I had some different ideas, and it was hard to determine the best path.

Here is the one we tried:

  • Sheila found the alignment slider positions from O4, and noticed that PR3 and ITMX pitch are bother very different now versus then. So is ITMX yaw.
  • I suggested we use PR2 spot move to move the PR3-PR2 axis, and see if we can follow with PM1 to better align the beam onto POP LF. Then, we can adjust ITMX and beamsplitter.
  • Moving PR3 pitch to the O4 alignment causes the beam to fall off POP X, and it does not go back onto POP A LF. I tried moving the PM1 slider to the "good for POP A LF" setting above, but that does not bring the beam back.
  • When in the "good for POP X" setting, PM1 saturates both LL and UR, so it is not obvious if the problem is pitch or yaw.
  • I tried moving ITMX around, and PR3 as well, but ITMX moves cause us to fall off ISCT1 refl camera, and PR3 moves do not bring us back on that camera.
  • Overall, Keita and I agree that we need to think more about this.

This is the state of the alignment as I am leaving it tonight:

  • PM1 is in the "good for POP A LF" state, which means it is not saturating, and there is no beam on POP X
  • PR3 alignment (as well as the corresponding IM4, PR2 and PRM alignment)  is reverted to where it was before I started this particular adventurew
  • ITMX alignment and BS alignment are also reverted.

Screenshot attached of all these settings.

Earlier we did some OMC scans and got weird results. We tracked this down to an incorrect DCPD whitening setting. Keita fixed it, and we reran the scans, the carrier peak heights are now correct compared to the blue reference.

Oli tracked down the problem with MC2. All crossovers are fine now and the mode cleaner locks with normal gain settings. They will alog the details.

Images attached to this comment
elenna.capote@LIGO.ORG - 12:44, Thursday 23 July 2026 (91216)

Centering on POP X DC with PM1 pulls beam off POP A LF

Right now we have an alignment that can bring the beam to both POP A in vac and to the POPAIR diodes on ISCT1 in a PRMI, or with either PRX or MICH locked.

However, the beam was very far off of POP X WFS DC, suggesting PM1 is not well-aligned. I spent a bunch of time trying to move PM1 while keeping the beam on POP A LF and improving the POP X alignment while we are locked on MICH DARK, which brings a lot of light to the POP port.

I gave up on keeping the beam on POP A and instead did much larger moves of PM1, which brought the beam to all four segments of POP X DC and increased the POP X sum. I finally got the beam well enough aligned that I could engage the DC6 centering loop, which aligns PM1 to POP X.

We are now well centered on POP X, but have lost the beam on POP A. PM1 is also unfortunately close to saturation at this alignment.

Here are the PM1 slider values that put the beam on POP X:

P: -868.5, Y: -2076.5

Here are the PM1 slider values that put the beam on POP A LF:

P: 213.5, Y: -258.5

Assuming the sliders have a decent calibration to urad, this is a 1 mrad difference in pitch and 1.8 mrad difference in yaw.

Images attached to this comment
H1 SPI (SEI, SPI)
jeffrey.kissel@LIGO.ORG - posted 11:44, Thursday 23 July 2026 - last comment - 12:21, Thursday 23 July 2026(91210)
Calibrating the SPI Optical Levers in to ISI Rotation (Modeled Version); QPD A -- (ISIHAM3 PIT / QPDA Normalized Spot Position) = 209.6e-4 [rad/rad]
J. Kissel

As it stands now, QPDA on ISI HAM2's ISIJ reflector is measuring the rotation of the ISI HAM3. The channels H1:SPI-H23_OL_QPD_A_{PIT,YAW}_OUT_DQ are still in "normalized position of the beam, s" [V/V = "radians"], as SEG1, SEG2, SEG3, and SEG4 have been converted from ADC counts to ADC volts with the transimpedance whitening stage compensated (see LHO:91157), and the PIT (lower - upper) and YAW (left - right) in [V] are divided by the SUM in [V].

Executive Summary: 

Modeling the PITCH calibration of QPDA's normalized spot position, s, into ISIHAM3 rotation angular displacement, \alpha, yields 209.6e-4 [rad/rad], excellently similar to Arnaud's measured 240e-4 [rad/rad] from 91194. 

Thanks to Arnaud's excellent sharing/bookkeeping, I opened his template, and updated the calibration and post the plot again here. I also attach the updated calibration window parameters for the SPI channel, in the updated template whcih has been committed to 
    /ligo/svncommon/SeiSVN/seismic/HAM-ISI/H1/HAM3/CRS/Templates/dtt/https://alog.ligo-wa.caltech.edu/aLOG/uploads/91210_20260723113040_2026-07-23_H1SPIH23_ASD_DTTCalibration.png
(Note to future users, the QPD's whitening compensation is *included* in the calibration of this template because 2026-07-18 06:00UTC was before I turned on the front-end compensation for it on 2026-07-23 LHO:91157. So if you measure the ISI *after* 2026-07-23, then you don't need the (z:p) = (39.8:0.039) [Hz] zero-pole compensation in the DTT calibration. Also beware - after this aLOG I'm going to install the [rad/rad] calibration into the front-end too.)

This doesn't change the answer much (see updated plot below): the H1SPIH23 optical lever measure of ISI HAM3 PITCH is dominated by ADC noise up the 1-10 Hz region, as (sadly) expected from the SPI final design; see Figure Figure 1biii.2 of T2400145. This is because the beam spot is so large at HAM2 QPDA, and *that's* because we didn't have room on the HAM3 ISIK transceiver to include a beam reducing telescope that would decrease the spot size at ~15.5 [m] away.

The model, math, and calculation: 

Sign conventions -- assume QPDA "+x" is -Y IFO coordinates and +YAW = +RZ of ISIHAM3, and QPDA "+y" is + Z IFO coordinates, and +PIT = +RY of ISIHAM3.

Thru integrating the power of the Gaussian beam at the QPD, P_y(x,y), from -infinity (the -y, i.e. -Z edge of the QPD) to the top / bottom (i.e. that between S1+S2 and S3+S4) boundary, one gets 

                       / +inf   / y        2 P_{0}       w_{0}^{2}        2 (x^{2} + y^{2})
    P_y^{lower}(x,y) = |        |       --------------   ---------  exp( ------------------ ) dx dy
                       / -inf   / -inf   pi w_{0}^{2}      w^{2}                w^{2}
    
                              pi      2 P_{0}    / y               y^2
                     = sqrt( ---- )  ----------  |       exp( - 2 -----) dy
                               2      pi w^{2}   / -inf            w^2

                         P_{0}                     y
    P_y^{lower}(x,y) =   ----- (1 + erf ( sqrt(2) --- ) )
                           2                       w

with y being the spot position of the beam, with power, P_{0}, and radius, w, at the detector. erf is the well-defined Gaussian Error Function. Assuming the beam is centered on the QPD, that means the power on the top and bottom halves are equal, and thus s_pit as
              P_y^{lower} - P_y^{upper}
    s_{pit} = ---------------------
                       P_{0}

                          y
    s_{pit} = erf( sqrt(2) ---  )
                          w
 
                 erf(z) ~ 2 z / sqrt(pi)

              2 sqrt(2)  y
    s_{pit} = --------  --- 
              sqrt(pi)   w

Importantly, s is a dimensionless quantity. Regardless of whether the QPD segments are (a) uncalibrated, (b) calibrated into ADC volts proportional to photocurrent, or (b) calibrated into milliWatts of incident power, if you create a creating PIT and YAW signal, that's normalized by the SUM in the same units, then you *always* gets you the "right" normalized spot position units. Some folks are even so bold as to refer to the QPDs as "self-calibrating" because of this. 

But there's more to calibrating the QPD if you want to interpret the normalized spot position as an angle from somewhere. We do so by first solving for the spot displacement at the QPD, y, (converting 2 sqrt(2) = sqrt(8) along the way)

              pi     
    y = sqrt( --- )  w  s_{pit}
               8     

and then assume a very scalene right-triangle and the small-angle approximation convert the beam displacement to +\theta_PIT = +RY in [radians]. That process ends with "just" dividing by the "lever arm," L_{OL} distance between the HAM3 ISI center of rotation and the QPDA's curve mirror on the +X face of the HAM2 ISI,

                      y           1            pi     
    \theta_{PIT} =  -----   =   -----   sqrt( --- )  w  s_{pit}
                    L_{OL}      L_{OL}         8

One can run through the same math to get the similar answer for \theta_{YAW), if one assumes no astigmatism in the beam:

                      x           1            pi     
    \theta_{YAW} =  -----   =   -----   sqrt( --- )  w  s_{yaw}
                    L_{OL}      L_{OL}         8

     

So generically, we can compute one number to calibrate normalized spot position at the QPD in [radians] into displacement angle of the ISI from which the lever beam was launched in [radians]:

    \alpha_{PIT,YAW}                          pi      w 
    ---------------- =  \kappa_{OL}  =  sqrt( --- ) -----  
       s_{pit,yaw}                             8    L_{OL}


So, let's compute this number for the QPDA system.

From T2400304, the centers of rotation to the opposing side wall distance is 15.4274 [m]. Subtracting a the little bit of length of the ISIJ reflector 0.12 [m] for HAM2 for completeness, that's

    L_{OL} = 15.4274 - 0.12 [m] = 15.3074 [m], 

Using the measured beam waists from LHO:89181, assuming no astigmatism for now and this the waist radius is w_{0} = 1.034e-3 [m] (and thus an uniform "type B" error bar of +/- 0.005e-3 [m]), the beam radius of the meas beam propagated to 15.3074 [m],

    w(z = 15.3074 [m]) = 5.119e-3 [m] +/- 0.02e-3 [m]

    ,

Then the calibration from normalized beam spot displacement units to angle of ISI HAM3 is
 
                        pi     5.119e-3 [m]
    \kappa_{OL} = sqrt( --- ) ------------  
                         8     15.3074 [m]

                = 2.096e-4 [m/m] or [rad/rad]
                = 209.6e-6 [rad/rad] 
    \kappa_{OL}   = 209.6 [urad/rad]

This number is consistent with what Arnaud measured as 240 [urad/"ct"] with the driven transfer function in LHO:91194 (he didn't know that it's not "ct" but the normalized spot position "rad").
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:21, Thursday 23 July 2026 (91214)SEI, SPI, SYS
Here's the YAW ASD (sans a CRS of course), with GS13 and CPS calibrated with the same Arnaud calibration, and SPI OL YAW calibrated with the same 209.6 [urad/rad].

As expected -- more coherence than PIT, measuring real (but different) signal below ~0.5 Hz.
Compare with Figure 1biii.3 from the Final Design Doc T2400145. 
The SPI ISI HAM3 OL YAW likely loses coherence below 0.01 Hz because the QPD again becomes dominated by ADC noise, because of the large spot.
Images attached to this comment
H1 SPI (CDS)
jennifer.wright@LIGO.ORG - posted 11:44, Thursday 23 July 2026 (91213)
Checking grounding of SPI 80MHZ RF splitter

Jennie W, Fil C,

Summary: RF splitter signal shields are connected to rack electrically - but we probably don't care.

I went out to the SUS-R2 rack to check if the SPI RF splitter (little blue box on left of pic) was grounding to the rack. This was following up on Josh's alog here (LHO alog #90790).

I checked and all three shields of the signals connected to the spitter are electrically connected to the rack (verified with a voltmeter). The body of the splitter is electrically isolated (which makers sense as it is coated with a insulating materrial).

I undid the zip ties holding it to the rack and made sure there was an air gap between the spitter and the rack and these sheilds are still connected electrically to the rack. After consulting with FIl he thinks that the connector coming out of the double mixer (D2400315) with the 80 MHz signal (shown here) is not the correct type to isolate the shield from the box, and therefore the rack.

If we wanted to fix this we would have to change the type of RF connector we are using for the 80 MHz signal coming out of the double mixer. After consulting with Jeff we have decided that for now this doesn't matter to us so we are leaving it like this.

I zip tied the RF splitter back to the rack. For reference I have included a photo of the double mixer and the RF amplifier which also connects to this splitter.

Images attached to this report
H1 SEI
arnaud.pele@LIGO.ORG - posted 11:20, Thursday 23 July 2026 - last comment - 16:04, Thursday 23 July 2026(91212)
BS ISI health check

I used the earthquake down time from the weekend to look at the health of the BSC2-ISI sensors.

Sensors look OK (including the newly replaced H1 L4C - see alog 90840) except for CPS ST2 H1 (see red curve on the last plot) with large noise below 1Hz. This will need an investigation (I would start by swapping cables at the field box to see if it's an in-chamber issue).

Dtt Template lives under /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/BS/Data/Spectra/Undamped/bs_all_sensors.xml 

Images attached to this report
Comments related to this report
jim.warner@LIGO.ORG - 13:46, Thursday 23 July 2026 (91217)

I had already done this test several years ago trying to diagnose the issue with BSC2, which, contrary to my comment in the alog Arnaud linked to, still has alot of flat looking excess noise in the 1-10hz. Arnaud's spectra here doesn't make me think this noise is due to a broken cps, the high frequency noise floor is unchanged, there's no evidence of glitching, unless it is some new failure mode.

Knowing that I would have few chances to try swapping in the near future, I did this over lunch when I went out to also unlock HAM1&2 hepi. I put BSC2 in damped, collected St2 CPS spectra, swapped the St2 H1 cps with a spare sensor, and got a comparison spectra. No change, see first attached spectra, refs are with the old H1 cps, live spectra are with the new sensor. I have left the spare sensor in for now, I will try to swap it back to the old sensor so we can preserve our ISI alignment (the new sensor reads a slightly different location that the old), but physically there should be no difference, the BSCs just use the free hanging position for the cps reference, unlike the HAMs. 

Performance is no better with the new cps, as well, see second plot, refs are with the new cps, live is before the swap.

Images attached to this comment
arnaud.pele@LIGO.ORG - 16:04, Thursday 23 July 2026 (91222)

As dicussed with Jim on the phone it would be interesting to see the result of swapping H1 and V1 at the lemo input of the field cables - V1 noise is low enough between 10mHz-100mHz when the ISI is damped that the H1 noise would be obvious if it followed the cable.

Images attached to this comment
H1 CDS
david.barker@LIGO.ORG - posted 09:25, Thursday 23 July 2026 (91209)
Adjustment of EDC to DAQ timing to mitigate occassional 0leg CRC errors

Jonathan, Erik, Dave:

Following the upgrade of EDC and its front end (h1susauxb13) to Deb13/RCG-5.6.5 on Tuesday, we initially had EDC CRC errors on both legs at a rate of 1-6Hz. This had not been seen at LLO during their upgrade. The main difference is the number of EDC channels, LLO=45k, LHO=61k.

Erik changed two parameters, the EDC delay (D ) and the EDC cps-xmit delay (X), both in mS. Originally we had D=10,X=34. This gave the EDC CRC error rate after the upgrade. Erik tried reducing X to 5mS, no change. He then reduced D to -10mS and the errors stopped. To minimize the impact on the other frontends, X was put back to 34mS with no immediate problem.

Over the next day we had two sets of 0-leg CRCs on h1susauxb13 and h1susauxh2. Interestingly the CRCs on h1susauxb13 were only for the models (h1iopsusauxb13 and h1susauxb13) and not the EDC.

On Wednesday 22jul2026  at 14:13 Erik changed D to +1mS. We have had no CRC events since then, +19 hours and counting.

H1 AOS
camilla.compton@LIGO.ORG - posted 08:47, Thursday 23 July 2026 (91197)
New ZM2 alignment, Power check through OPOS, PD BD Checks, ZM5 iris placed

Ryan S, Camilla

ZM2 alignment
After the alignment mystery yesterday 91183 where I must have moved the ZM2 cable adjusting it's alignment, today I found the new ZM2 alignment for the beam to be retroreflected in the FC path, nominal alignment sliders attached. Also moved to the "new" ZM2 beam location (beam closer to 5.75" high at ZM2) plus the amount I needed to move ZM2 to account for the ZM2 bump. The beam was retroreflected fine, sliders of the "new ZM2" location attached.  In this new location the H1:FEC-160_DAC_OUTPUT s are around 20k which slightly better than before I bumped ZM2. 
 
Power Budget 
Ryan and I took power budgets through the OPOS. We got between 4.5 and 7.5% power drop from out fo the OPO before A:DC1 to after B:M4 for both the nominal and "new ZM2" alignments, see below. In 90573 we got between a 2% and 5.5% power drop, so although we thought his was fine at the time, but maybe it isn't. 
ZM5 iris
We added an iris after ZM5, to assist in realignment of ZM5 once it is swapped next week. 
 
Power Meter and beamdumps checked
We digitally checked that the three fiber rejected powermeters F:BD1, G:BD1 and H:BD1 we reading power in medm when the beams were on them. We did not check the centering on the PDs. We did check the centering on the beamdumps: G:BD1 and H:BD1 were fine, the beam was very close to the gap between panels for F:BD1 so we adjusted it, before and after attached. 
Images attached to this report
H1 SQZ
eric.oelker@LIGO.ORG - posted 08:16, Thursday 23 July 2026 (91205)
More HAM7 astigmatism analysis

I went back through more of the recent mode matching measurements in HAM7 to help us track how the changes we're making are impacting the astigmatism of the squeezed field going into the interferometer.

Below I tabulate the 1D overlap between the vertical and horizontal q parameters.  Since the PSAM settings seem to cause higher order aberrations in addition to astigmatism, I also tabulate the M2 values for each set of measurements, though its less clear what we can conclude from the M2 parameter alone since it doesn't tell us what higher order mode content is being generated by the PSAMs.

 

Jun 26:  aLog 90783

For this set of measurements, we were using the nominal setting for the ZM2 PSAM and taking measurements on SQZT7 after the beam diverter using the Thorlabs beam profiler.

XY 1D overlap:

ZM4\ZM5 SG (V) -4.5 -2.0 0 2.0
2.0 0.995 0.996 0.990 0.991
4.0 0.996 0.994 0.992 0.991
6.0 0.995 0.995 0.993 0.993
8.0

0.995

0.994 0.994 0.994

M2:

ZM4\ZM5 SG (V) -4.5 -2.0 0 2.0
2.0 1.35, 1.32 1.27, 1.23 1.17, 1.18 1.17, 1.19
4.0 1.33, 1.29 1.24, 1.21 1.16, 1.16 1.16, 1.17
6.0 1.32, 1.29 1.22, 1.20 1.16, 1.16 1.16, 1.17
8.0 1.31, 1.27 1.20, 1.19 1.16, 1.16 1.17, 1.18

It appears that the astigmatism gets worse for higher values of the ZM5 strain but the M2 gets better.  The dependence on ZM4 is less obvious, but that is expected since the beam spot size on ZM4 is only 1 mm.

 

Jun 30:  alog 90827 For this set of measurements, we were measuring the beam using a pickoff mirror between ZM4 and ZM5.  Given that we don't expect ZM4 to have that large of an impact due to the small spot size, one assumes that the astigmatism and M2 values will be similar to the data right before ZM4 taken on Jun 29:  see the data in alog 90815 and the analysis in alog 91185

Oddly, it doesn't work out this way.  The astigmatism still seems worse when ZM2 is changed from its nominal value, but the astigmatism coming from ZM2 (assuming that is the source) seems lower in this dataset than in the Jun 29 dataset.  However, the M2 values are significantly higher.  Perhaps there's some hysterisis or other non-stationarity in the astigmatism and higher order abarations coming from the PSAMs?  This seems plausible for a strain induced effect like this.  

Another possibility is that the beam was clipping somewhere.  That could explain a high M2 value.  Unfortunately, that sort of thing can happen with an improvised pick-off path like this one.

Data with ZM2 = 3.15 V

ZM4 SG (V) 1D Overlap X/Y M2
2.0 .995 1.78, 1.73
4.0 .999 1.81, 1.73
6.0 .999 1.84, 1.75
8.0 .998 1.90, 1.81

 

Data with ZM2 = 4.5 V

ZM4 SG (V) 1D Overlap X/Y M2
6.2 .986 1.79, 1.64

 

Jun 30_2:  alog 90841

This dataset looks at the mode after the beam diverter.  The ZM2 setting has been changed to 2.4 V for most of this dataset, a value which may give improved mode matching into the Filter cavity.  We expect that changing the ZM2 settings will impact the beam quality at this location.  This dataset is difficult to compare with the others since there isn't much overlap in the settings. The M2 values after ZM5 look much better than in the data taken before ZM5 earlier in the day.  Odd, since higher order aberrations aren't something that can be easily undone.

Data with ZM2 = 2.4 V

ZM4, ZM5 SG (V) 1D Overlap X/Y M2
2.0, 0.8 .993 1.24, 1.26
4.0, 0.8 .991 1.20, 1.23
4.0, 2.0 .997 1.33, 1.30
6.0, 2.0 .992 1.30, 1.30

Data with ZM2 = 3.15 V

ZM4, ZM5 SG (V) 1D Overlap X/Y M2
2.0, 4.4 .998 1.39, 1.32

 

July 10: alog 90986

These measurements were taken after the beam diverter on SQZT7 shortly after the ZM4 preloading was adjusted.  In the first two measurements, the beam spot postion on ZM2 is varied to see the impact on the outgoing mode:

ZM2 Spot Position 1D Overlap X/Y M2
5.85" (nominal) .995 1.35, 1.35
5.75" .997 1.28, 1.25

Centering the spot better does seem to improve things a bit.  

Next, they did a sweep of ZM4 and ZM5 with the new ZM4 preloading.  It is unclear from the aLog which ZM2 spot position was used for this dataset.  Note that the ZM5 strain gauge was broken for this measurement, so I record the bias voltage for ZM5 instead

ZM4 SG, ZM5 Bias (V) 1D Overlap X/Y M2
-4.1, 20 .997 1.41, 1.34
-4.1, 100 .995 1.31, 1.28
-2.9 , 100 .996 1.29, 1.26
-1.1, 100 .996 1.28, 1.25
-1.1, 20 .996 1.37, 1.33
1.0, 100 .996 1.26, 1.23
2.7 , 100 .995 1.25, 1.23
2.7, 20 .997 1.37, 1.31
LHO General
ryan.short@LIGO.ORG - posted 07:44, Thursday 23 July 2026 (91204)
Ops Day Shift Start

TITLE: 07/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.16 μm/s 
QUICK SUMMARY: Work continues towards DRMI locking today. JAC and IMC were left offline overnight, and there was a short stint in EQ mode since sensor correction is still on.

H1 IOO
jennifer.wright@LIGO.ORG - posted 17:32, Wednesday 22 July 2026 - last comment - 16:33, Thursday 23 July 2026(91199)
JAC Heater Guardian Take 2

I tried the heater guardian today with a gain of 0.003 and a set point of 25 degrees seeing as it seems to have reached equilibrium around this value with no loop running and 1W input overnight. It looks like it overshot initially and is turning around and coming back to the set point of 25 degrees C now. Thermistor 1 is the loop sensor but I have marked the turning point on thermistor 2 in the attached picture. We still have some range on the PZT actuator (JAC-PZT_DRIVER_VOLTS is low rate channel from Beckhoff voltage driver and JAC-PZT_DRV_OUT_DQ is front-end PZT feedback channel for fast feedback) and the temperature actuator (JAC-HEATER_POWER_SET). I will get the operator to switch it off when they leave so we don't cause any pressure spikes overnight.

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 16:33, Thursday 23 July 2026 (91223)

I did another test today with the same gain but the set point at 25.1 degrees C (the temperature of the thermistor 1 when I switched it on). It still overshot so we might want to test with a lower gain but it stopped the JAC from unlocking due to the PZT running out of range.

Attached is the trends from today (vertical cursor when i switched on the controller, horizontal showing the setpoint on the thermistor).

Summary: let's test tomorrow with a smaller gain.

Images attached to this comment
H1 SPI
jeffrey.kissel@LIGO.ORG - posted 12:37, Tuesday 21 July 2026 - last comment - 09:10, Thursday 23 July 2026(91157)
H1SPIH23 QPD Whitening Compensation Turned ON
J. Kissel

The QPD channels in the H1SPIH23 PD array have a z:p = 0.39:39.6 Hz whitening filter in their analog transimpedance amplifier (D1001974-v8). As such, I've installed and turned on an "antiWh" compensation filter = zpk([39.8],[0.39],1,"n") in FM2 of all the H1:SPI-H23_OL_QPD_{A,B}_SEG{1,2,3,4} banks, and accepted the turn on in the SDF system and committed the filter filter to the userapps repo rev 35564.
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:10, Thursday 23 July 2026 (91207)
Here's a screenshot of the SEG filters after the whitening is turned ON. 
The output of the SEG filters are therefore calibrated into units of ADC volts, proportional to the photocurrent and thus the power from each segment.
Eventually, we may install a [mW/V] calibration based on LHO:90105 to turn this (and mostly the SUM) into [mW], but for now, we stick with ADC [V].
Images attached to this comment
H1 ISC (VE)
camilla.compton@LIGO.ORG - posted 13:27, Wednesday 08 July 2026 - last comment - 09:22, Thursday 23 July 2026(90949)
VP for ITMY IR camera moved up in X-arm Adapter Plate. CHETA VP not added.

Gerardo, Camilla. Done in Y-arm in 90917

Gerardo and I removed the blank from the X-arm adapter plate A-1C VP5 (T1200220) and swapped the D2000285-v2 type 01 SN 004 nozzle baffle to D2000285-v3 type 07 SN 002 nozzle baffle plate Mitch had prepared, all existing hardware reused and orientation kept the same. Photos before and after attached.  

The fused silica VP for the ITMY IR camera (not currently used for locking of in NLN but we want to keep) was then moved up to this A-1F VP2 location. The camera can itself has not yet been reinstalled, the camera in the can will need to be lowered, a yellow VP cover is there for now. 

We had issues with the CHETA VP ZnSe, so the planned D1700340-type002 VP assembly was not installed in the lower A-1C VP4, a blank was installed instead. A D2000285-v2 type09 SN 003 nozzle baffle plate with a high 2" aperture was installed, this was swapped for a solid D2000285-v2 type01 SN 004 nozzle baffle, see photos before and after

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 09:22, Thursday 23 July 2026 (91208)

This alog is for the ITMX IR camera, not ITMY as the title states. 

There is also a typo: The fused silica VP for the ITMY IR camera (not currently used for locking of in NLN but we want to keep) was then moved up to this A-1C VP5 location. The camera can itself has not yet been reinstalled, the camera in the can will need to be lowered, a yellow VP cover is there for now. 

The only two VPs touched were A-1C VP4 and VP5. Thanks Melina for catching this typo. 

Displaying reports 1-20 of 88591.Go to page 1 2 3 4 5 6 7 8 9 10 End