Displaying reports 1-20 of 88609.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 15:05, Friday 24 July 2026
H1 TCS
madison.simmonds@LIGO.ORG - posted 15:05, Friday 24 July 2026 (91241)
EX HWS re-measured location of optics

Madi, TJ

This week, TJ and I went down to EX to re-measure the location of all components within the EX HWS path. The updated measurements are in the attached file. 

We each measured the distances, to give some indication of the uncertainty on each measurement. 

Non-image files attached to this report
H1 SEI
arnaud.pele@LIGO.ORG - posted 14:49, Friday 24 July 2026 (91240)
CRS sensInv filter clean up

Shoshana, Arnaud

We cleaned up the SensInv filters in the CRS filter bank. Those invert the CRS sensor response so the signal is still calibrated in urad below 50mHz. 

* fm9 is the reference filter (based on a fit of this measurement)
* fm1 is the running filter, which is a modified version of fm9 with lower Qs, to reduce ring down time during a filter reload or a step in the signal (see step response in fig2, red is fm1, blue is fm9). 

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 14:45, Friday 24 July 2026 (91238)
PRMI alignment this morning

Before the JAC PZT problem, I did get an hour or so of alignment time in.  Summary: we now have light on LSC POP and POP X for the same PM1 alignment, and ITMX is back to the alignment that should point down the arm.

These screenshots show MICH fringes with 10W input power, where I started and where I ended.  The idea was to move to the ITMX alignment that Jenne Driggers found using the arm beam here: 89738.  I watched the mich fringes and AS camera while moving the ITM, moved the beam splitter to keep the michelson fringes, and as Keita suggested moved PR3 to keep the beams on the ISCT1 refl camera.  This did cause the michelson fringes on the LSC pop diode to get smaller, when that happened I paused, went to the PR2 spot move guardian state, and adjusted PR3 to bring the fringes back on LSC POP.  After bringing the ITMX yaw alignment back I could see that there is now light on POPX and LSC POP A for the same PM1 alignment.  

When I walked ITMX pitch, I had to also adjust yaw several times as I went along to keep the mich fringes.  I also adjusted PRM to keep PRX alignment good as I moved along. Looking at this screenshot of the brief time when PRMI was flashing, the POP A LF flash was about the O4 power level (91211), as was reflair A, but popair has too little power.   The result of this was that PR3 started the day 56urad away from the O4 slider, but is not -15urad.  PR3 yaw started the day close to the O4 slider but is now -47urad.

I also adjusted the POP X dark offsets so that this QPD will be less confusing to read, SDF screenshot attached. 

 

Images attached to this report
H1 AOS
sheila.dwyer@LIGO.ORG - posted 13:10, Friday 24 July 2026 - last comment - 15:44, Friday 24 July 2026(91235)
electronics problems time line

Summary:

JAC PZT outputs were turned off, this lead to hours of confusion.  It shows up in HAM1 suspensions because light was sparying all over HAM1.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 15:44, Friday 24 July 2026 (91244)

After turning the PSL PZT back on with the same offsets before, JM1 was brought back to the position right before the problem started according to OSEM.

This didn't bring back the beam on JAC REFL diode so I steered PZT until JAC REFL see some light, and refined from there.  In the end, JM1 didn't move that much

  before problem after recovery difference
H1:SUS-JM1_M1_DAMP_P_INMON -668 -680 -12
H1:SUS-JM1_M1_DAMP_Y_INMON -920 -917 +3
H1:SUS-JM1_M1_OPTICALIGN_P_OFFSET -537 -634 -97
H1:SUS-JM1_M1_OPTICALIGN_Y_OFFSET -1471 -1434 +37

JM1 OSEMs are drifting as I write this but it seems to be consistent with diurnal changes.

PZT output changed mostly in PIT, much larger than I expected from hysterisis. I don't know why but I leave it as is for now. Note that JAC-PZT_PIT_OFFSET and YAW_OFFSET  move the beam in PIT and YAW in JAC basis, in the PSL room coordinate it is YAW and PIT.

  before problem after recovery difference
H1:JAC-PZT_PIT_OFFSET 6407.5 2546 -3861.5
H1:JAC-PZT_YAW_OFFSET 26025 26605 +580

 

H1 CAL (CAL)
joseph.betzwieser@LIGO.ORG - posted 12:56, Friday 24 July 2026 (91236)
Updated pydarm install to 20260724.0 tag
I'm followed the pydarm deployment instructions here, to update the LHO pydarm install.  However, the deploy script is slightly out of date, and currently owned by Jamie, so used a modified version to point at environment-py39.py (a change in the setup allows for different python version installs).  I need to get this fixed longer term.

This is the 20260724.0 tag for pydarm, which pulls in fixes from the last year or so, aimed at allowing for an up to date test of calibration export functionality on Monday.

This is not the default cds conda environment, but the default you get when typing pydarm at a command line, or specifically invoking by running "conda activate /ligo/groups/cal/conda/pydarm"
H1 CDS
david.barker@LIGO.ORG - posted 11:50, Friday 24 July 2026 (91234)
JM1 jump at 10:30
Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 10:57, Friday 24 July 2026 (91233)
FW0 went unstable.

Tony, Dave:

At 10:33 FW went unstable, restarting itself after writing a new frames.

I restarted the daqd process at 10:44 (systemctl restart rts-daqd) which so far appears to have fixed it.

Images attached to this report
H1 SPI (SEI, SPI)
jeffrey.kissel@LIGO.ORG - posted 10:09, Friday 24 July 2026 (91229)
Both H1SPIH23 QPDA and QPDB Centered
J. Kissel

Seeing the "first light," calibrated SPI Optical Lever amplitude spectral densities in  and , and thinking about ADC noise limitations and the calibration models assumption that the spots are centered on the QPDs drove me to re-check the spot positions on the QPDs. 

Timeline of centering:
    2026-07-17 17:00 UTC (LHO:91124) -- Jennie turned on the SPI laser for the first time since doors went on and the ISIs were isolated, and re-centered *only* QPDB with M_C1 (and thought she had adjusted QPDA centering with M_M1, thought she had mistakenly moved M_M2, but confirmed later she did not; LHO:91219).
    2026-07-23 14:00 UTC (LHO:91218) -- Jim unlocks and restores function of HAM2 HEPI, such that now both HAM2 and HAM3 are fully functional, and remain ISOLATED with corner station sensor correction ON as their nominal condition.
    2026-07-23 20:30 UTC (LHO:91221) -- Jennie re-centered (only) QPDB again using M_C1.
    2026-07-24 16:05 UTC (this aLOG) -- Not knowing that Jennie had yet recentered any QPDs, and finding QPDA PIT's normalized beam displacement at +0.23 [rad], I recentered *both* QPDA and QPDB.

I attach a similar trend of relevant channels including both Jennie's centering work from 2026-07-23 and mine this morning. Similar to Jennie's plots but with thick lines, light mode, and with the y-axes labeled.
I saved this template to 
    /opt/rtcds/userapps/release/spi/h1/ndscope/QPD_Centering.yaml  (rev 35598).


Here're the DC values of the QPDs after this morning's centering (done with the precision one can achieve with a picomotor STEP SIZE of 1 [ct]):
$ gpstime now;z avg -30 H1:SPI-H23_OL_QPD_A_PIT_OUT_DQ H1:SPI-H23_OL_QPD_A_YAW_OUT_DQ H1:SPI-H23_OL_QPD_B_PIT_OUT_DQ H1:SPI-H23_OL_QPD_B_YAW_OUT_DQ -s

t = 
PDT: 2026-07-24 09:27:44.113664 PDT
UTC: 2026-07-24 16:27:44.113664 UTC
GPS: 1468945682.113664

Channel                        t-30 sec average       t-30 standard deviation
H1:SPI-H23_OL_QPD_A_PIT_OUT_DQ -0.0024822048842906954 4.722167842008142e-06
H1:SPI-H23_OL_QPD_A_YAW_OUT_DQ  0.0030039884615689514 5.884913671432033e-06
H1:SPI-H23_OL_QPD_B_PIT_OUT_DQ -0.0022898733150213957 8.094109742945136e-05
H1:SPI-H23_OL_QPD_B_YAW_OUT_DQ  0.008859152471025783  4.6337990240392655e-05

$ gpstime now;z avg -30 -s H1:SPI-H23_OL_QPD_A_PIT_OUT_DQ H1:SPI-H23_OL_QPD_A_YAW_OUT_DQ H1:SPI-H23_OL_QPD_B_PIT_OUT_DQ H1:SPI-H23_OL_QPD_B_YAW_OUT_DQ H1:SPI-H23_OL_QPD_A_SUM_OUT16 H1:SPI-H23_OL_QPD_B_SUM_OUT16

t0 = 
PDT: 2026-07-24 09:54:54.983607 PDT
UTC: 2026-07-24 16:54:54.983607 UTC
GPS: 1468947312.983607

Channel                        (t0-30 sec) average       (t0-30 sec) standard deviation
H1:SPI-H23_OL_QPD_A_PIT_OUT_DQ  -0.002713  3.4e-05
H1:SPI-H23_OL_QPD_A_YAW_OUT_DQ   0.003265  4.2e-05
H1:SPI-H23_OL_QPD_B_PIT_OUT_DQ  -0.002033 10.0e-05
H1:SPI-H23_OL_QPD_B_YAW_OUT_DQ   0.009682 5.3e-05
H1:SPI-H23_OL_QPD_A_SUM_OUT16   25.846691 0.003820814636259141
H1:SPI-H23_OL_QPD_B_SUM_OUT16   29.265472 0.004081774857250754

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 08:15, Friday 24 July 2026 - last comment - 10:53, Friday 24 July 2026(91228)
TW1 offload, moved NDS1 to new archive, started old file deletion

WP13433 TW1 offload

As Tony mentioned, I did a quick NDS1 restart at 07:57 to get it to serve the past 6 months of minute trends from the archive following this week's copy.

At 08:09 I started the deletion of the old data from TW1's SSD-RAID. This typically takes a few hours. At the start of deletion disk usage was 93%.

Comments related to this report
david.barker@LIGO.ORG - 10:53, Friday 24 July 2026 (91232)

File deletion completed at 10:10 (took 2hr01min). WP13433 has been closed.

H1 General
anthony.sanchez@LIGO.ORG - posted 08:07, Friday 24 July 2026 - last comment - 10:21, Friday 24 July 2026(91227)
Friday Morning Ops shift report.

TITLE: 07/24 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: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s 
QUICK SUMMARY:
 

The Vacuum pressure is still being pumped down.

CDS team needed to reboot the NDS server again so the NDScope screen shots may stop beifly.

SUS: First stage of PRM seems to be pushing a bit harder than I'd expect given that it's misaligned.

 

Comments related to this report
david.barker@LIGO.ORG - 10:21, Friday 24 July 2026 (91231)

Restarting some stuck IOCs:

MX weather station has been down since the power outage Thu16jul2026. This runs as a containerized IOC on the service host cluster. I restarted its PCS resource, it is running again.

The CDS Rack Smart Power Strip IOC has been down for a few days. It runs as a systemd service on cdsioc0. I restarted pwr_strip_ioc.service, it is running again.

H1 SUS (ISC)
oli.patane@LIGO.ORG - posted 18:43, Thursday 23 July 2026 (91226)
MC2 back in action!! M2 and M3 feedthrough cables swapped

Jeff, Sheila, Fil, Elenna, Oli

The feedthrough cables (air side) for MC2 M2 and M3 have been swapped and now MC2 is back to behaving how we expect it to. Transfer functions for M1 to M1, M2 to M2, and M3 to M3 are correct (red traces) and crossover plots for MCL and M2/M3 are looking good.
Current correct cable numbering for MC2 at the HAM3 D6 feedthrough port is:
D6-F1 -> MC2 M3 (HAM3_020)
D6-F2 -> MC2 M1 (HAM3_001)
D6-F3 -> MC2 M2 (HAM3_019)

This should be updated in the flange layout D1002874, which I don't see the altium file for. Next time we open up HAM3, we should fix this lineup so F1/F2/F3 line up with MC2 M1/M2/M3.


Full troubleshooting:
After lots of troubleshooting and my MC2 M2 and M3 measurements from yesterday, Jeff noted that the M2 to M2 TFs looked a lot like the M3 to M3 Tfs, and vice versa. This was also very suspicious because back in May (90185) there had been a feedthrough swap for the feedthrough that MC2's M1 (T1/T2/T3/LF), M2, and M3 were all connected to, and M1 and (we thought) M2 had been found to be plugged in incorrectly on the vac side. After the plugs going into F1 and F2 had been swapped, we had measured only M1 to confirm that the swap was successful.

A (silly) mistake:
Fil and I went out to HAM3 D6 flange and meant to swap the M2 and M3 cables, but since the flange layout was still listing F1 -> M1, F2 -> M2, F3 -> M3, we swapped the cables connected to F2 and F3, which were actually M1 and M3, respectively. We determined that this was wrong because M1 to M1 and M3 to M3 looked horrible but M2 to M2 looked the same as before (wrong but not different), which means that M2 must have been in the F1 port and so hadn't actually been swapped with M3. We noticed later that this lineup was written in the May 8th MC2 'fix' alog(90185).

Actual fix:
We plugged M3 (HAM3_020) into F1, M1 (HAM3_001) into F2, and M2 (HAM3_019) into F3. Here's a diagram/timeline of this mistake and fixing it.
Everything is looking good for MC2 and it seems like we've been able to go back to using MC2 to lock the IMC normally.

I'll add plots next week comparing MC2 M2 to SRM M3 and vice versa

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 15:05, Thursday 23 July 2026 - last comment - 18:01, 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
Comments related to this report
ibrahim.abouelfettouh@LIGO.ORG - 18:01, Thursday 23 July 2026 (91225)

Continued work on DRMI - nothing further to add.

JAC_HEATER Guardian is off. IMC is offline. IFO is open to anyone who wants to take measurements.

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 22:36
22:34 TCS Camilla CHETA lab/ LVEA N Parts grab 22:59
22:37 VAC Gerardo, Jordan LVEA YES Checking on BSC2 pump 23:01
22:53 PEM Robert, Miranda LVEA YES Setting up shakers for solar farm analysis 23:16
23:08 SEI Jim LVEA YES Rack retrieval HAM3 23:14
00:04 VAC Jordan MY N Pump closure 00:15
00:59 VAC Gerardo LVEA YES Picture 01:59
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 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
LHO VE (VE)
travis.sadecki@LIGO.ORG - posted 09:57, Monday 20 July 2026 - last comment - 14:25, Friday 24 July 2026(91121)
HAM5/7 relay tube viewport adapter installed

This is a late entry from last Friday.  We have removed the relay tube between HAM5 and HAM7 and replaced it with the adapter/viewport assembly on the HAM5 side.  The assembly is being pumped down independently by a small turbo/aux cart.  The GV should not be opened until the pressure in the viewport assembly is approximately the same as the corner pressure and the aux cart is valved out.

Comments related to this report
gerardo.moreno@LIGO.ORG - 14:25, Friday 24 July 2026 (91239)VE

The adapter's isolation valve was opened, then the adapter was leak checked, no leaks were found.  Adapter and accessories will remain until we are given the OK to remove them.

Images attached to this comment
H1 SEI
arnaud.pele@LIGO.ORG - posted 22:27, Thursday 25 June 2026 - last comment - 10:00, Friday 24 July 2026(90763)
HAM3 CPS card setting

Shoshana, Jim, Arnaud

The x6 HAM3 new CPS boards have been set to the following configuration (as per E2200455): 

  board SN probe SN Location
H1 29536 22777 Slot 1 in crate +Y side
V1 38690 22781 Slot 2 in crate +Y side
H3 12563 22779 Slot 3 in crate +Y side
V3 38494 22775 Slot 4 in crate +Y side
H2 23370 22778 Slot 1 in crate -Y side
V2 11950 22780 Slot 2 in crate -Y side

There was some glitching noticed on the channels that were in range prior to this work, which was fixed after this setting change (see attached). Two of the cards were set to Master before and Jim is confident this would have created problems. 

Left to do : 

1- Label the cards at the front of the boards with module SN and corner #
2- Disconnect the grounding to the chamber of the crate on the +Y side 
3- Label the in-air lemo cables with H1, V1, H2 ...
4- Update ICS with the new boards SN
5- Gather the cards that were removed from WHAM3 to send back to microsense for recalibration with a new set of sensors (RMA)

The tracking spreadsheet for this ECR was updated here: E2500184 

Images attached to this report
Comments related to this report
arnaud.pele@LIGO.ORG - 10:00, Friday 24 July 2026 (91230)
H1 TCS
camilla.compton@LIGO.ORG - posted 09:28, Wednesday 09 March 2022 - last comment - 15:07, Friday 24 July 2026(62121)
ETMX HWS Laser Source Replacement - Day 2

Vicky, Austin, Camilla. Follows yesterdays alog 62089. Summary: aligned but weren't able to see any baffles and beam is smaller than ideal.

Austin and I measured distances between optics (all measurements attached and key ones below): 

  INCHES mm
L3 to L2 41 1041
L2 to L1 21 533
L1 to LPM 60 1524
HWS to L3 58 1473

We started with translation stages at: Collimating lens @ 1.44; HWS:L2 @ 12.39. Later Vicky and I moved the L2 on it's translation stage upstream ~ 1.5" (starting location attached). 

Vicky and I realigned the beam to remove the majority of the ITM reflection. Once we were finished and ETM was misaligned we could still see faint rings reflected off ITMX (that moved when ITMX adjusted) photo here. So more alignment could be done to get rid of those. We adjusted the CCD camera to try nd focus better but didn't see a difference so replaced in original position. 

We adjusted the collimating lens and L2 to try and get the retro-reflected beam at the iris after ALS-M11 D1800270 to be a similar size as the outgoing beam - it is ~ double the size which is the best we could get with the 40mm collimating lens. The waist of the beam is still just after L3. 

Adjusted wave plate to maximize beam to LPM from 270 to 292. This might have been the cause of reflected beam streaks we see on the camera. In the final image. 

Final beam after yesterday is attached. It still seems to small to me so maybe we need to go back to the 50mm lens. Once we are happy we need to dither the ETM to measure the magnification. 

Images attached to this report
Non-image files attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 15:06, Wednesday 09 March 2022 (62144)

From a controls tmux session on zotws24 I'm running a ETMX 0.5W ring heater test 2am-4am. Script will close ALS EX, EY shutters at the start. >>  python3 /opt/rtcds/userapps/release/tcs/common/scripts/power_adj_scripts/ring_heater_schedule_shutterALS.py ETMX -s  1330941618 -d 2 -p 0.5"   Robert will shutter ALS and when he turns the ring heaters back to thier nominal O3 values tonight. 

This morning I replaced the Hartmann plate but didn't track down the source of the scattered light shown in alog 62121 photo yet. 

aidan.brooks@LIGO.ORG - 15:27, Wednesday 09 March 2022 (62145)

The baffle is a 190mm circular aperture that should appear around 9.3mm in diameter on the HWS camera (assuming magnification of ~20.5X) - see aLOG 60937.

The aperture that appears in the HWS images looks plausible as the baffle shadow.

camilla.compton@LIGO.ORG - 11:22, Friday 11 March 2022 (62185)

The ring heater test  doesn't look like it's showing us anything much see attached. The spherical power is noisy and doesn't show any change. The TOTAL_PIXEL_VALUE does decrease.  

Images attached to this comment
madison.simmonds@LIGO.ORG - 15:07, Friday 24 July 2026 (91243)

Madi, TJ

These on-table distances were re-measured 22nd July 2026, and posted 91241

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