Displaying reports 1-20 of 89655.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 21:18, Friday 16 October 2026
H1 General
anthony.sanchez@LIGO.ORG - posted 21:18, Friday 16 October 2026 (92337)
Friday Eve Shift

TITLE: 10/17 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY:
Tried to lock the IFO a few times And couldn't get all the way up to Prep_ASC_For_Full_IFO.
I started to do an initial alignment and 15 minutes into an initial alignment the ISI BS stage2 Watchdog got tripped by a small localish earth quake. Initial Alignment got stuck and I restarted it after resolve the BS ISI issues. Since then Initial Alignment has not been abel to complete. I did restore the sliders back to their positions 3 hours ago, that did not resolve the issue.  I probably have to push something in a direction.  I'm putting the IFO in down and the IMC in offline. for the weekend.

I'm also trying to reimage the NUC 30 display before I leave and found that NUC30 came up as NUC26 (I guess it's the old NUC26?) which is still running and have to re-image it again and still have to get Puppet installed on it.

TLDR: I broke everything.... and I'm sorry, I'm trying to fix at least one of those things before I leave tonight. 
Update I put the old harddrive back into NUC30 as the Bookworm installed was hanging everytime I tried to re-image.... so Everything is still broken and I'm going home for the weekend.


 

 

H1 General
anthony.sanchez@LIGO.ORG - posted 17:58, Friday 16 October 2026 (92336)
Friday Eve Shift

TITLE: 10/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.30 μm/s 
QUICK SUMMARY:

H1 was held in down while Sheila worked on IMC which was held offline.
When we were ready we started locking.

Held lock in Acquire DRMI while touching up SRM. 
Went up to CARM_TO_TR, before a lockloss.

I took NUC30 down to re-image it.
 

H1 General
ryan.crouch@LIGO.ORG - posted 16:28, Friday 16 October 2026 (92331)
OPS Friday Day shift summary

TITLE: 10/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Tony
SHIFT SUMMARY: We held in DOWN, and with the IMC offline for a bit to investigate the NPRO, Sheila and Daniel increased the IMC diode power x2 and reduced gains, then we resumed locking. The microseism has turned around.
LOG:

Start Time System Name Location Lazer_Haz Task Time End
16:29 FAC Mitch LVEA Y Clean room inspections, biergarten check 17:26
18:23 FAC Matt, Kim MidY N Checkout new building 18:46
18:59 TCS Camilla, Miriam CHETA lab LOCAL CHETA work, Miriam in at 19:04 20:08
19:40 PSL Sheila, Daniel LVEA Y IOT2L IMC diode power increase, Daniel out 20:00 20:01
19:49   Mallika, Alex Xarm N Walkin' 20:13
21:27 TCS Camilla, Miriam CHETA lab LOCAL CHETA work 23:12
21:50 PSL Sheila LVEA Y SR75 PSL racks 22:12
H1 IOO
daniel.sigg@LIGO.ORG - posted 13:17, Friday 16 October 2026 - last comment - 16:51, Friday 16 October 2026(92332)
IMC REFL Power Adjust

Sheila Daniel

The IMC REFL power (IMC_REFL_DC) was 20.2mW when unlocked. We adjusted it to 40.8mW, a good factor of 2 higher.

In detail:

Jan10, 2025: With 60.5W input we had 16.6mW (locked)
Oct 15, 2026: With 10W input we had 0.31mW (locked); scaling this to 60W input and adding 10% for the losses in the JAC, we get ~2.1mW. 

In principle we would be able to run with 8x more power on the PD, since the higher order modes in reflection of the IMC have been reduced significantly by adding JAC. However this would result in a unacceptable high power when unlocked even at 2W input. So we decided to increase the power by a factor of 2 only.

Comments related to this report
sheila.dwyer@LIGO.ORG - 13:35, Friday 16 October 2026 (92333)

I changed the guardian so that the IMC IN1 gain is 6dB lower both for acquiring lock of the IMC and once locked.  This will be adjusted again in CARM to analog, incremented up by 1dB.

First screenshot shows the OLG measurement (below the frequency scale) when the IMC guardian is in acquire (IN1 gain -18dB, fast gain 0dB).  This is the situation when the guardian was trying to engage the boost, I swapped the order so that it increased the gain to nominal before engaging the boost.  I hope this will help avoid the annoying difficulties we've been having getting the IMC to lock.  

Final settings in LOCKED are -5dB IN1 gain, 5 dB fast gain, OLG measurement attached.  

Non-image files attached to this comment
sheila.dwyer@LIGO.ORG - 16:51, Friday 16 October 2026 (92335)

Good new/ bad news

We do seem to have helped the problem where the IMC boost coming on knocks it out of lock, so that will make relocking smoother. 

The bad news is that since we increased the power on the IMC refl diode, we have had a lot of trouble with the TR_CARM steps, which had been quite reliable most of this week.  I've now gone back to the table and reduced the power on IMC refl back to 20mW when the IMC is offline, and reset the IN1 gain for locking to -4 and locked to 1.  

Tony has relocked the IMC now and is trying the TR_CARM offset reduction again. 

H1 ISC
sheila.dwyer@LIGO.ORG - posted 13:15, Friday 16 October 2026 (92329)
fast locklosses

Camilla, Sheila, Ryan Crouch

Attached are three screenshots of fast locklosses from last night and this morning (here, here, here) and one more normal lockloss for comparison.  These seem a lot like the locklosses that plauged us in October and Nov of 2024, because AS power drops down before it goes up, and the IMC looses lock at exactly the same time as the light disappears at the AS port. 

Here are some useful alogs to reference the previous problems: 81371 (Vicky also has a comment to this with a useful summary of investigations done)

Ryan Crouch had the IFO in down, with the IMC locked, for an hour (16:53 -17:53 UTC). Screenshot of the hour trends and zoomed in on the biggest glitch seen here. He also had the IMC offline for 1 hour, from 17:55 UTC to 18:55 UTC, trends here.  These can be compared to similar trends from last Nov, for example 81356.  The size of the glitches in the PMC PZT is similar to then, but other signals like PMC mixer mon and FSS fast mon are not glitching now. 

(Will add more info later, posting now so Camilla can add her plots in comments).

 

Images attached to this report
H1 PSL
ryan.crouch@LIGO.ORG - posted 10:43, Friday 16 October 2026 (92330)
PSL investigation

We've been having trouble staying locked recently with lots of fast lock losses so we are looking into the PSL laser.

16:53 UTC after a lockloss at CARM_TO_TR I requested us to stay in DOWN, so we could have just the IMC locked.

17:53 UTC I will bring the IMC to offline after an hour of holding in DOWN.

 

H1 TCS
miriam.ramos@LIGO.ORG - posted 09:57, Friday 16 October 2026 (92328)
More CHETA Y projections!
[Sophie, Camilla, Miriam]
This work was done yesterday (October 16, 2026).
Following the same procedure and layout as written in alog 92311. We went onto an excursion to the CHETA table along the Y-arm.
Our main goal today was to (at each distance away from the CHETA table) measure the beam at three different translation stage settings.
We measure  the translatation stage at -35mm, -10mm (nominal) and +15 mm (those distances were chosen because they were previosuly used in this alog)
 
These are some of the things we did differently than yesterday to improve the photos:
  • Used a more stable laser barrier.
  • Left the tape measure on the floor so it was easier to measure the distance from the laser barrier to the CHETA table.
  • Made sure laser barrier was perpendicular to laser beam path.
  • Tried to keep ruler in horizontal and vertical orientation.
  • Avoided getting the laser beam on the cross hairs of the FLIR camera for easier image processing.
    • Used black and white mode (on the FLIR camera) for easier analysis.

More details and pictures will be posted soon!

H1 General
ryan.crouch@LIGO.ORG - posted 07:30, Friday 16 October 2026 (92327)
OPS Friday Day shift start

TITLE: 10/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.36 μm/s 
QUICK SUMMARY:

LHO General (ISC)
ryan.short@LIGO.ORG - posted 20:22, Thursday 15 October 2026 - last comment - 21:22, Thursday 15 October 2026(92325)
Ops Eve Shift Summary

TITLE: 10/16 Eve Shift: 2330-0300 UTC (1630-2000 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY: I've been picking up where commissioners left off this afternoon trying to engage more full IFO ASC loops.

When we reached PREP_ASC for the first time on my shift, I updated the green alignment references (SDF screenshots attached). My intention tonight was to get the references updated again once more ASC was on, but this proved slow-going as there have been many locklosses in PREP_ASC between 2 and 30 minutes spent in the state. By hand, I was enabling CHARD, INP1, and PRC2 (all P&Y) without any adjustment needed, then I moved PRM in pitch to bring the ADS PIT3 error signal to zero and close it as well. At 01:55 UTC (GPS 1476150918) is when I had all of these loops closed and close to converged. My plan after that was to start moving PRM in yaw to close YAW3, but we lost lock and haven't spent enough time in PREP_ASC on subsequent relocks since then for me to finish that process.

Relocking up to PREP_ASC continues to be smooth, and Sheila is taking over commissioning for the evening.

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 21:22, Thursday 15 October 2026 (92326)

Louis, Sheila

I ran  wfsreliefpast.py 1476150918 to go back to the alignment where Ryan had ADS P3 close to 0 and 8 ASC loops closed.  This worked well, we relocked without an issue and indeed ADS P3 was close to zero.  I ran the QPD scripts before trying to close any asc.  We lost lock quickly, but the scripts were nearly done so Louis and I captured the green references and SDF'd them.  

A large earth quake tripped ISI and HEPI ETMX, Louis reset the watchdogs (including the IOP DACKILL) after things had calmed down a bit.  

 

Images attached to this comment
H1 ISC
elenna.capote@LIGO.ORG - posted 16:59, Thursday 15 October 2026 (92322)
Green references reset, we can close some ASC loops in full IFO

Sheila, Louis, Elenna

We have been repeatedly locking fairly well to prep_asc_for_full_ifo. We have set some green references to a decent alignment. However, we have not been able to set the green references to the alignment that we think is best, which we got to after we walked dofs and closed some loops. However, the attached green references get us close enough.

We have successfully closed CHARD, INP1 and PRC2 P and Y. We tried closing MICH P without problems, but closing MICH Y seems to cause problems either by itself or with MICH P. We also starting walking the PRM to bring ADS3 to zero, but only got about a third of the way before a lockloss.

When we did successfully close MICH P, we did so with half gain, this gives about a 0.5 Hz UGF, based on this somewhat sketchy OLG. The design is for 2 Hz, but we think this is ok for now.

I disengaged PRC1 loop in DRMI ASC for now until we know what PRM alignment we will be happy with in full lock. The PRC1 error signal is set by arbitrary offsets on POP A, and we may prefer a different PRM alignment in full lock.

Sheila, Oli, and I took a look at some of our locklosses. We continue to lose lock while sitting in prep_asc, some we can attribute to alignment engagement going haywire, and others we have no reason for. The lockloss tool seems to be tagging many of these locklosses as "IMC" meaning that the IMC is dropping out within 50 ms of the power drop on AS_C. However, Oli notes that the L2 signals of all four test masses seem to be diverging even before the IMC drops out, so maybe this tag is misleading. The behavior of the coil drives suggests that maybe something is going wrong in DHARD P.

Sheila and I found that there are two DARM boosts we could be engaging, that are usually engaged around DARM offset or PREP DC readout. This might help suppress some low frequency DARM motion that DHARD could also be seeing. I moved both of these boosts to DRMI_TO_POP.

As a side note, we successfully used Stefan's "wfsreliefpast.py" script to revert to some good alignment we had when walking full IFO alignment!

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 16:32, Thursday 15 October 2026 (92318)
OPS Thursday Day shift summary

TITLE: 10/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Commissioners worked on ASC loops and CARM, the IFO can relock up to DRMI pretty quickly with its current alignment.
LOG:

Start Time System Name Location Lazer_Haz Task Time End
16:35 TCS Camilla, Miriam LVEA Y Move CHETA-Y barrier 16:48
17:51 CAL Tony, Caroline PCAL lab LOCAL TSK measurement setup 18:20
20:21   Mallika, Alex, Rachel EndX N Walking 20:44
21:03 TCS Camilla CER Y Grab headsets 21:08
21:22 TCS Camilla, Sophie, Miriam LVEA Y CHETA-Y laser measurements Ongoing
23:02 CAL Tony, Fil EndX N Check on PCAL power supply and Chassis Ongoing
Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 16:09, Thursday 15 October 2026 (92321)
Ops Eve Shift Summary

TITLE: 10/15 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 11mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.25 μm/s 
QUICK SUMMARY: Commissioning continuing, currently in PREP_ASC and setting green alignment references.

LHO FMCS
ryan.crouch@LIGO.ORG - posted 15:43, Thursday 15 October 2026 (92290)
HVAC Fan Vibrometers Check FAMIS

Closes FAMIS85193, last checked in alog92229

For the OUT building fans, EX_FAN2_570_2 (yellow) looks a bit noisier, on MY_FAN2_270_1 (pink), the noise seems more periodic than previously. They're all under 0.7.

For the CS building fans, everything looks fine.

Images attached to this report
H1 PSL (PSL)
ryan.crouch@LIGO.ORG - posted 15:32, Thursday 15 October 2026 (92291)
PSL Status Report - Weekly

Closes FAMIS85193, last checked in alog92117
Laser Status:
    NPRO output power is 1.842W
    AMP1 output power is 70.67W
    AMP2 output power is 139.8W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 23 days, 5 hr 24 minutes
    Reflected power = 29.77W
    Transmitted power = 104.9W
    PowerSum = 134.7W

FSS:
    It has been locked for 0 days 0 hr and 8 min
    TPD[V] = 0.5066V

ISS:
    The diffracted power is around 2.8%
    Last saturation event was 0 days 0 hours and 9 minutes ago


Possible Issues:
    PMC reflected power is high

Images attached to this report
H1 TCS
sophie.muusse@LIGO.ORG - posted 10:04, Thursday 15 October 2026 - last comment - 13:02, Thursday 15 October 2026(92311)
Projecting CHETA beam down LVEA

Camilla, Miriam, Travis, Sophie


First attempt measuring the beam after a long propagation distance using the FLIR camera. Here are the measurement distances, laser power settings and corresponding images. Using the Fintrace model the beamsize at each point was modelled. 

Distance from QCL [m] QCL power [W] image range Modelled Beamsize [x,y] [mm]
5.732  0.2 280-284 7.087,7.233
8.5006  0.2 285-287 10.932,11.4911
15.871  0.2 288-289 21.219,22.868
23.618 0.4 290-291 32.047,34.840
32.216 0.6 292-297 44.069,48.129

note: Nominal distane to ITM is 36.735m but will be subject to exact table placement

Here is a drive with the pictures: https://drive.google.com/drive/folders/153uQSwYIMZdKYFz6KgaSdyBdOywcY-T0?usp=drive_link

A comment will be added with the procedure :)

Comments related to this report
miriam.ramos@LIGO.ORG - 11:36, Thursday 15 October 2026 (92317)

[Sophie, Camilla, Travis, Miriam]

(This work was done yesterday, October 14, 2026)

The table layout that we used for the projections is this one. Where the distances from the QCL -> M1 -> M2 -> M3 -> M4 are the same distances as per the model that is stored in the cheta_modeling git repo.

The distances from M4 through D are not part of the original CHETA table setup and they were just used and labeled like that for the projections we were doing. The distances in between these mirrors is detailed in the image itself.

Now, before starting the projections we aligned the green laser to the irises on the table, this is to make sure the the green laser is co-aligned with the QCL CHETA laser. We started by projecting the green laser a short distance outside of the table onto a laser barrier to see where it landed, then turned the green laser flipper down to then project the CHETA laser (onto the same barrier) and checked they landed both as close to each other as possible. We moved the laser barrier back several times, each time checking where our green laser landed first. To see the CHETA beam we were using a FLIR camera (EXTECH i5). You can see our amazing pictures (taken at different distances) in the Google folder Sophie shared in this alog.

Camilla was pointing the FLIR camera to the beam (which was hitting the laser barrier) and I was holding a metal ruler which had very skinny pieces of tape taped every centimeter (I was warming up the ruler with my hands in between measurments), the ruler was hold either below or on top of the beam to gauge the beam size at the specific distances we were measuring it at. In this picture, you can see Camilla with the FLIR camera and me with the ruler, artistically framed by Sophie. Sophie was out laser operator. The QCL CHETA laser was always started at minimum power (0.5 A) and then slowly brought to full power until we could see the beam on the barrier/FLIR camera.

We use the minimum QCL power possible to still be able to see the beam, which meant we were chaging the power of the QCL with the rotaiton stage as we were moving away from the table. For the specific power that we used, see Sophie's table above.

We note that tha the laser barrier was flimsy and therefore it was challenging to keep the fabric straight while taking our pictures. Today we will go back to do more projectes and we will use a slightly less flimsy barrier to project the laser into.

Images attached to this comment
miriam.ramos@LIGO.ORG - 13:02, Thursday 15 October 2026 (92319)

This was done for CHETA Y, along the Y-arm inside the LVEA.

H1 CAL (CAL)
anthony.sanchez@LIGO.ORG - posted 15:10, Wednesday 14 October 2026 - last comment - 17:11, Thursday 15 October 2026(92307)
PCAL Post EX GV20 work ES measurment

Caroline C and I went down to EX... again.... (Sorry EY, I know it was your turn, but next time I promise I'll measure you... )
We took the PS4 Working Standard (WS) integrating sphere down to EX.
We found EX's PCAL system is covered in caution tape, like it was in the center of a foreboding crime scene!  

Unfortunately the red Current Limit LED was Lit again, and I trended the channel H1:CAL-PCALX_LASERDIODECURRENT back to find it has been lit up since last Tuesday. Supisiously close to the beckhoff restart time. I'm not sure which channel is best to check for beckhoff restarts yet.  I was able to just move the voltage down a little and back up to rectify this issue before starting the measurement.

We took some pictures of the beam spots before we started to prove our innocence.
Followed instructions on T1500062 and followed it without any deviations from our part. The SEI system was put in ISI Damped HEPI offline for this measurement for other work though. 
Everything went as smooth as it can while dodging lifts, scaffolding, and caution tape.
Took some After measurement beam spot pics to prove our innocence again. 

Overall I don't think the GV20 work had any real impact on PCAL pointing or performance. Shoutout to the GV20 team for doing such a great job! 


Wanna see the Absolute Calibration details of this specific measurement and the commands input and output? :

 

Martel_Voltage_test.png time series of us injecting a known votage into the ADC. 
WS_at_TX.png  timeseries of Working standard in the Transmitter module.
WS_at_RX.png timeseries of Working standard in the Receiver module across the beamtube.
WS_at_RX_BOTH_BEAMS.png  Both inner and out beams at the same time.

@cdsws25: python3 generate_measurement_data.py --WS PS4 --date 2026-10-13
Reading in config file from python file in scripts
../../../Common/O4PSparams.yaml
PS4 rho, kappa, u_rel on 2026-10-13 corrected to ES temperature 299.8 K :
-4.700380443762894 -0.0002694340454223 0.0007505543347185126
Copying the scripts into tD directory...
Connected to h1daqnds1
martel run
reading data at start_time:  1475945650
reading data at start_time:  1475946100
reading data at start_time:  1475946460
reading data at start_time:  1475947100
reading data at start_time:  1475947444
reading data at start_time:  1475947820
reading data at start_time:  1475947998
reading data at start_time:  1475948640
reading data at start_time:  1475949030
Ratios: -0.45984106211593845 -0.46714267909102675
writing nds2 data to files
finishing writing
Background Values:
bg1 =        9.805339; Background of TX when WS is at TX
bg2 =        5.167711; Background of WS when WS is at TX
bg3 =        9.886270; Background of TX when WS is at RX
bg4 =        5.195956; Background of WS when WS is at RX
bg5 =        9.755134; Background of TX
bg6 =        0.367068; Background of RX

The uncertainty reported below are Relative Standard Deviation in percent 

Intermediate Ratios
RatioWS_TX_it      = -0.459841;
RatioWS_TX_ot      = -0.467143;
RatioWS_TX_ir      = -0.454541;
RatioWS_TX_or      = -0.462195;
RatioWS_TX_it_unc  = 0.068338;
RatioWS_TX_ot_unc  = 0.070460;
RatioWS_TX_ir_unc  = 0.074890;
RatioWS_TX_or_unc  = 0.065120;
Optical Efficiency
OE_Inner_beam                      = 0.988231;
OE_Outer_beam                      = 0.989349;
Weighted_Optical_Efficiency        = 0.988790;

OE_Inner_beam_unc                  = 0.046695;
OE_Outer_beam_unc                  = 0.045578;
Weighted_Optical_Efficiency_unc    = 0.065252;

Martel Voltage fit:
Gradient      = 1636.946737;
Intercept     = 0.081815;


 Power Imbalance = 0.984370;

Endstation Power sensors to WS ratios::
Ratio_WS_TX                        = -1.078768;
Ratio_WS_RX                        = -1.391922;

Ratio_WS_TX_unc                    = 0.042184;
Ratio_WS_RX_unc                    = 0.040097;

=============================================================
============= Values for Force Coefficients =================
=============================================================

Key Pcal Values :
GS           =      -5.135100; Gold Standard Value in (V/W)             
WS           =      -4.700380; Working Standard Value             

costheta     =      0.988362; Angle of incidence
c            =      299792458.000000; Speed of Light
             
End Station Values : 
TXWS         =        -1.078768; Tx to WS Rel responsivity (V/V)
sigma_TXWS   =        0.000455; Uncertainity of Tx to WS Rel responsivity (V/V)
RXWS         =        -1.391922; Rx to WS Rel responsivity (V/V)
sigma_RXWS   =        0.000558; Uncertainity of Rx to WS Rel responsivity (V/V)

e            =        0.988790; Optical Efficiency
sigma_e      =        0.000645; Uncertainity in Optical Efficiency

Martel Voltage fit : 
Martel_gradient         =        1636.946737; Martel to output channel (C/V)
Martel_intercept   =        0.081815; Intercept of fit of     Martel to output (C/V)

Power Loss Apportion : 
beta          =        0.998895; Ratio between input and output (Beta)  
E_T          =        0.993829; TX Optical efficiency 
sigma_E_T          =        0.000324; Uncertainity in TX Optical efficiency 
E_R          =        0.994929; RX Optical Efficiency 
sigma_E_R          =        0.000325; Uncertainity in RX Optical efficiency 

Force Coefficients : 
FC_TxPD          =        7.894807e-13; TxPD Force Coefficient 
FC_RxPD          =        6.188002e-13; RxPD Force Coefficient 
sigma_FC_TxPD          =        3.610367e-24; TxPD Force Coefficient 
sigma_FC_RxPD          =        2.777621e-24; RxPD Force Coefficient 

data written to CDS: /ligo/gitcommon/Calibration/pcal/O4/ES/measurements/LHO_EndX/tD20261013


That's cool and all but perhaps you wanna see that data with relation to the End X's history, I gotchu: 
You can see the trends here or go to the git page for this measurement.

Images attached to this report
Non-image files attached to this report
Comments related to this report
anthony.sanchez@LIGO.ORG - 17:11, Thursday 15 October 2026 (92323)

The current limit issue came back again today after I powercycled the PCAL laser.
I left it in that state so Fil and I can go down to EX to check on the powersupply in the racks.
There are 3 potential failure points.
The powersupply in the racks.
The powersupply in the chassis.
Or the laser head it's self.


Fil suggests that since it's likely not the power supply in the racks, perhaps it's time to retire the decade old PCAL laser at EX.
I will start preparing for a laser swap at EX.

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