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

Search criteria
Section: H1
Task: TCS

REMOVE SEARCH FILTER
SEARCH AGAIN
Reports until 18:08, Tuesday 12 August 2025
H1 TCS (TCS)
corey.gray@LIGO.ORG - posted 18:08, Tuesday 12 August 2025 (86332)
TCSy CO2 Laser Drops H1 From Observing

Just had a couple of drops from Observing due to TCS_ITMY_CO2 guardian saying laser is unlocked and needed to find a new locking point.  (Attached are the two occurrences thus far).

Images attached to this report
H1 TCS
camilla.compton@LIGO.ORG - posted 16:00, Tuesday 12 August 2025 (86328)
TCS CO2Y Chassis Tripped off during Maintenance

Oli told me that the TCS CO2Y Chassis Tripped off during Maintenance this morning. This is not surprising as there was alot of craning work going on near that rack and the CO2 chassis are known to be fussy, see FRS 6639.

When I went to untrip it both indicator lights were red on it but after key-ing off/on, it turned on with no issues. 

H1 TCS (TCS)
ibrahim.abouelfettouh@LIGO.ORG - posted 16:44, Friday 08 August 2025 (86272)
TCS Monthly Trends - FAMIS 28463

Closes FAMIS 28463. Last checked in alog 85690.

CO2 Trends:

HWS FAMIS:

Plots attached

Images attached to this report
H1 TCS
ryan.short@LIGO.ORG - posted 14:11, Thursday 07 August 2025 (86246)
TCS Chiller Water Level Top-Off - Biweekly

FAMIS 27821

No water was added to either chiller as levels are still good, although slowly dropping over the past several weeks. Updated T2200289 tracking sheet.

Filters and steel mesh in both chillers looked good. No water in leak checking cup.

LHO General
ryan.short@LIGO.ORG - posted 07:46, Tuesday 05 August 2025 - last comment - 10:37, Wednesday 06 August 2025(86191)
Ops Day Shift Start

TITLE: 08/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 6mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 has been locked for 17 hours, but looks like there were three brief drops from observing between 11:33 and 11:40 UTC (I'm assuming SQZ-related, but will look into it). Magnetic injections are running and in-lock charge measurements will happen right after before maintenance begins at 15:00 UTC.

Comments related to this report
ryan.short@LIGO.ORG - 09:36, Tuesday 05 August 2025 (86196)

Lockloss happened during in-lock charge measurements, specifically during the 12Hz injection to ETMX. The lockloss tool tags IMC for this one, and it certainly looks like the IMC lost lock first, but I can't say for sure why.

camilla.compton@LIGO.ORG - 14:18, Tuesday 05 August 2025 (86209)TCS

The three drops from Observing that Ryan points out were actually from the CO2 lasers loosing lock, first CO2Y and then CO2X lost lock twice, all between 11:33 and 11:40UTC ~4:30amPT. Both PZTs and laser temperatures started changing ~5minutes before CO2Y last lock. Unsure what would make this happen, LVEA temperature and chiller flowrates as recorded in LVEA were stable, see attached.

Unsure of the reason for this, especially as they both changed at the same time but are for the most part independent systems (apart from shared RF source). We should watch to see if this happens again.

Images attached to this comment
thomas.shaffer@LIGO.ORG - 10:37, Wednesday 06 August 2025 (86221)TCS

My initial thought was RF, but the two channels we have to monitor that both looked okay around that time. About 4 minutes before the PZTs start to move away there is maybe a slight change in the behavior of the H1:ISC-RF_C_AMP10M_OUTPUTMON channel (attachment 1), but I found a few other times it has similar output and the laser has been okay, plus 4 minutes seems like too long for a reaction like this. The pzts do show some type of glitching behavior 1-2 minutes before they start to drive away that I haven't found at other times (attachment 2). This glitch timing is identical in both laser's pzts.

I trended almost every CO2 channel that seemed worthwhile, I looked at magnetometers, LVEA microphones, seismometers, mainsmon, and I didn't find anything suspicious. The few people on site weren't in the OSB. Not sure what else to look for at this point. I'm wondering if maybe this is some type of power supply or grounding issue, but I'd expect to see it other places as well then. Perhaps places I just haven't found yet.

Images attached to this comment
H1 TCS (ISC, SQZ)
jennifer.wright@LIGO.ORG - posted 16:33, Monday 04 August 2025 (86184)
Calculating curvature of SR3 when heated up by 2W.

Jennie W, Camilla C

 

A while ago we heated up then cooled down the SR3 heater (alog #84749).

As part of measurements using this data I calculated the curvature change, following the approach at LLO by Aidan given iin alog #27262. Matlab code is below.

 

%calculate SR3 spherical lens

Pin = 2;%W

double_pass = 2;

SR3_t = (3*3600) + (11*60); % Time for cooldown in s.

delta_ITMY = -2.67e-5;% decrease in defocus of ITMY according to Hartmann sensor.

D_ITMY = delta_ITMY./double_pass;% defocus change in Dioptres

D_ITMY_error = 5e-6;% error on defocus in Dioptres.

R_SR3 = 36.013;% cold radius of curvature in m

delta_R = (2./((2/R_SR3)+D_ITMY))-R_SR3; % change in curvature during cooldown in m/

delta_delta_R = D_ITMY_error.*(2./((2./R_SR3)+D_ITMY)); % error on curvature change.

 

This means the rate of defocus change is 6.6750uD per Watt.

The final curvature change is + 0.0087 m +/- 0.0002 m as the mirror becomes less curved due to cooldown.

 

H1 TCS
thomas.shaffer@LIGO.ORG - posted 10:23, Monday 28 July 2025 (86017)
TCS Chiller Water Level Top Off - Biweekly

FAMIS27820

No water was added to either chiller, both at good levels. Updated T2200289 sheet.

Filters all looked good.

No water in leak detection Dixie cup.

H1 TCS (ISC)
camilla.compton@LIGO.ORG - posted 13:46, Tuesday 22 July 2025 (85921)
10.215kHZ PI that we pass over during Thermlalization

TJ noticed the DCPD signals rising ~25 minutes into the lock, we found this was a PI t 10.215kHz. Matt notes that we've seen this at the start of each lock even before we changed the ring heaters last. It just damps down again by itself, we expect as the HOM pass over it. Plots attached. This PI doesn't appear to be in our monitored PI list.

Images attached to this report
H1 General (Lockloss, TCS)
ryan.crouch@LIGO.ORG - posted 21:04, Sunday 13 July 2025 - last comment - 21:39, Sunday 13 July 2025(85730)
Lockloss 04:00 UTC

TCS CO2Y tripped and dropped us out of Observing at 03:58 UTC then we lost lock 2 minutes later, lockloss. The lockloss appears to have been an ETMX glitch.

Comments related to this report
ryan.crouch@LIGO.ORG - 21:39, Sunday 13 July 2025 (85731)

Following the WIKI and TJ's instructions I went into the LVEA (TJ was my phone buddy) to restart the controller than I went into the mechanical room and reset the power supply which was reading a current and voltage of 0 when I arrived. There were no flow/chiller alarm nor RTD/IR sens alarm.

H1 TCS
oli.patane@LIGO.ORG - posted 11:05, Friday 11 July 2025 (85690)
TCS Monthly Trends FAMIS

Closes FAMIS#28462 , last checked 84837

CO2 Trends (ndscope1)

Everything is looking good

HWS Trends (ndscope2)

Everything is generally looking good, with both ITMX and ITMY SLEDPOWERMON slowly going down, which they tend to do. The only possible concern I can see would be that zooming out to almost a year ago (ndscope3), it looks like the level that ITMX SLEDPOWERMON is at now is a lower value than it has been in the past year.

Images attached to this report
H1 TCS (TCS)
ibrahim.abouelfettouh@LIGO.ORG - posted 19:28, Wednesday 09 July 2025 (85663)
TCS Chiller Water Level Top Off - FAMIS 27819

Closes FAMIS 27819. Last checked in alog 85440

CO2Y:

Before: 10.3ml

After: 10.3ml

Water Added: 0ml

CO2X:

Before: 30.4ml

After: 30.4ml

Water Added: 0ml

 

No water leaking in our leak detection system (aka dixie cup)

LHO General
corey.gray@LIGO.ORG - posted 07:39, Thursday 03 July 2025 - last comment - 08:49, Thursday 03 July 2025(85518)
Thurs DAY Ops Transition

TITLE: 07/03 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

H1 had (3)  ~2-hr locks overnight (looks like no wake-up calls for Oli!).  H1 is currently locking (just powered up to 25W).  Winds stepped down at about 130amPDT (837utc).

Today is Thurs Commissioning from 8am-12pmPDT (15-19utc).  H1 won't be thermalized until about 1030-11amPDT, so no calibration...hopefully H1 short locks won't be an issue for calibration where we need H1 thermalized 3hrs.  Robert and Sheila will probably start their work

Comments related to this report
elenna.capote@LIGO.ORG - 08:23, Thursday 03 July 2025 (85520)

Just want to add a note that all three locks from last night were nearly the exact same length, 1:51, and the locklosses are all tagged with "PI monitor". A ring heater was changed yesterday, 85514, which may have caused this problem.

corey.gray@LIGO.ORG - 08:29, Thursday 03 July 2025 (85521)SUS, TCS

Additionally, each of the 3 locklosses were from PI28/29 according to VerbalAlarms (the Ring Heater change yesterday was made to address PI24 which riddled our 7hr lock for the last hour before the ultimate lockloss).

elenna.capote@LIGO.ORG - 08:49, Thursday 03 July 2025 (85522)

While we have been running PIMON live on nuc25, it appears the data from the lockloss hasn't been saved. The newest file in the /ligo/gitcommon/labutils/pimon/locklosses folder is from December 2024. I'm not sure what's going on. We think our problem is an 80 kHz PI, so this would be useful data to have.

H1 TCS
matthewrichard.todd@LIGO.ORG - posted 16:13, Wednesday 02 July 2025 (85514)
ETMY Ring Heater Change

M. Todd, S. Dwyer, C. Gray, A. Sanchez


We decided to set the ETMY ring heater back to 1W, as we were seeing PI24 having repeated dramatic ring ups. We expect this to set our LG10 y-arm mode to sit at 10490Hz once thermalized (fingers crossed). There are quite a few peaks around this region as well, but hopefully we move far enough away from PI24.

Saved the changes in SDF

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 15:52, Tuesday 01 July 2025 - last comment - 07:53, Friday 11 July 2025(85482)
Early report on HWS cameral control

Camilla, TJ, Dave:

Last Thursday 26th June 2025 alog85373 I restarted the HWS camera control code. We hoped this would improve the 2Hz noise comb in DARM. Initial results for F-Scan (observing) suggest it has not made much, if any difference. 

Attached F-Scans show the spectra on sun22jun2025 and mon30jun2025. The 2Hz comb (blue squares) look unchanged.

More investigation is needed to verfiy we are indeed disabling the frame aquisition on all HWS cameras when H1 is in observation.

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 16:33, Thursday 10 July 2025 (85678)DetChar, TCS

Looking at the HWS camera data, Dave's code was successfully stopping the HWS camera dueing NLN from 27th June, as expected 85373.

However, looking at the f-scans from the last week, the 2Hz comb was there until 3rd July but was gone on 4th July and hasn't returned since.

Nothing HWS related should have changed on the 3rd July (ops shift log 85519).

Images attached to this comment
evan.goetz@LIGO.ORG - 07:53, Friday 11 July 2025 (85683)DetChar
Excellent, thank you Camilla and Dave! This is very helpful.
H1 TCS
oli.patane@LIGO.ORG - posted 12:55, Monday 30 June 2025 (85440)
TCS Chiller Water Level Top-Off FAMIS

Closes FAMIS#27818, last checked 85024 (I am a week late)

TCSX: 30.5, no water added

TCSY: 10.6, no water added

No leak in water cup

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 10:54, Wednesday 25 June 2025 - last comment - 13:47, Wednesday 25 June 2025(85327)
Lockloss

Lockloss during commissioning at 2025-06-25 17:52UTC after over 5.5 hours Locked. Cause not known, but probably not commissioning related.

Comments related to this report
oli.patane@LIGO.ORG - 12:56, Wednesday 25 June 2025 (85334)

18:48 Back to NOMINAL_LOW_NOISE

camilla.compton@LIGO.ORG - 13:47, Wednesday 25 June 2025 (85335)TCS

Within the same ~15 seconds of the lockloss, we turned the CO2 powers down form 1.7W each to 0.9W each. In the hope of doing the thermalization tests we tried last week 85238.

We checked the lockloss today and LSC channels at the time last week we turned the CO2s down and see no glitches corresponding with the CO2 waveplate (out of vac) change, we think the lockloss was unrelated.

H1 TCS (DetChar-Request)
camilla.compton@LIGO.ORG - posted 13:20, Monday 23 June 2025 - last comment - 11:58, Thursday 26 June 2025(85247)
2Hz Comb in DARM from ITMX HWS Camera?

Ansel, Sheila, Camilla

Last week, Ansel noticed that there is a 2Hz comb in DARM since the break, similar to that that we've seen from the HWS camera sync frequency and power supplies and fixed in 75876.  The cabling has not been changed since, the camera sync frequency has been changed.

Our current camera sync frequencies are: ITMX = 2Hz, ITMY = 10Hz. We have typically seen these combs in H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ. With a 0.0005Hz BW on DTT I can't easily see these combs, see attached.

Images attached to this report
Comments related to this report
evan.goetz@LIGO.ORG - 13:31, Monday 23 June 2025 (85254)DetChar
It may be difficult to see in a standard spectrum, but can be clearly seen in Fscan plots linked off of the summary pages. For the "observing" Fscan, the interactive spectrum plot shows the 2 Hz comb marked automatically. See the attached image of H1:GDS-CALIB_STRAIN_CLEAN
Images attached to this comment
camilla.compton@LIGO.ORG - 17:04, Tuesday 24 June 2025 (85306)

Verifed that the cabling has not changed since 75876.

Next steps we should follow, as listed in 75876 would be to try using a different power supply or lowering the voltage to +12V. Or, there is a note suggesting Fil could make a new cable to power both the camera and CLink's via the external supply (14V is fine for both). 

evan.goetz@LIGO.ORG - 18:30, Tuesday 24 June 2025 (85312)DetChar
Thanks Camilla. If anything can be done more rapidly than waiting another week, it would be very much appreciated. Continuing to collect contaminated data is bad for CW searches.
camilla.compton@LIGO.ORG - 15:11, Wednesday 25 June 2025 (85341)

Matt and I turned down the Voltage supplied from 14V to 12V for each camera at ~22:00UTC when the IFO was relocking. Verified HWS cameras and code still running.

We also will plan to have Dave reimpliemnt the hws_camera_control.py script he wrote in 74951 to turn the HWS's off in Observing until we fix this issue.

kiet.pham@LIGO.ORG - 11:58, Thursday 26 June 2025 (85361)

The 2 Hz comb is still present in H1:GDS-CALIB_STRAIN_CLEAN after the voltage change (before the software update)

Images attached to this comment
H1 TCS
matthewrichard.todd@LIGO.ORG - posted 14:26, Wednesday 07 May 2025 - last comment - 16:48, Monday 11 August 2025(84306)
Estimating surface defocus of test masses and absorption from HOM spacing

M. Todd, S. Dwyer


As derived in previous alogs, we are able to relate the HOM spacing observed in each arm to the surface defocus of the test masses -- which is a combination of self-heating and ring heater power (ignoring CO2 affects on the ITM RoC). From the fits we've made of the HOM spacing / surface defocus change as a function of ring heater power we can get a value for the ring heater to surface defocus coupling factor.

Theoretically from this we should be able to solve for the self heating contribution in the test masses as well -- allowing us to constrain things like the coupling of absorbed power to surface defocus at the ITMs if we assume to know the arm power and absorption values (from HWS).


Upper Limits

If we assume no absorption in ETMs (obviously not physical), and we assume the HWS values for the ITM absorptions are correct, then with a HOM spacing measurement from each arm we can get an upper limit of the coupling factor of self-heating to surface defocus for each ITM (they shouldn't be different but this is a good exercise).

Assuming alpha is the absorption coefficient, i subscript is for the ITM, and x/y is which arm. P_y,i_rh is the itmy ring-heater. G-factors are the product of ITM and ETM g-factors. Then from the formula in section 1.2 of the notes file : Gy = Gyc - B*L*gyic*(Pyerh+Pyirh) - L*(Ai*alpha_yi*Pyarm*gyec + beta*Ai*alpha_e*Pyarm*gyic), we can solve for Ai which is the coupling factor of self-heating to surface defocus.

Parameter Value Notes
alpha_x,i 430 ppm from alog 76937
alpha_y,i 375 ppm from alog 76937
alpha_x,e 0 ppm  
alpha_y,e 0 ppm  
P_y,i_rh 0.000 W T0 = 1417899757
P_x,i_rh 0.850 W  
P_x,e_rh 1.950 W  
P_y,e_rh 2.146 W  
P_yarm
385159 W
T0 = 1417899757
P_xarm 385159 T0 = 1417899757
Gx 0.8149 T0 = 1417899757
Gy 0.8198

                    TMS * pi

G    =   cos2 (   ----------------   )

                      FSR

Ai_y -26 uD/W  
Ai_x -39 uD/W  

Middling Values

If we assume quoted absorption in ETMs (measured by LIGO, on galaxy), and we assume the HWS values for the ITM absorptions are correct, then with a HOM spacing measurement from each arm we can get a more realistic value of the coupling factor of self-heating to surface defocus for each ITM (they shouldn't be different but this is a good exercise).

Assuming alpha is the absorption coefficient, i subscript is for the ITM, and x/y is which arm. P_y,i_rh is the itmy ring-heater. G-factors are the product of ITM and ETM g-factors. Then from the formula in the notes file : Gy = Gyc - B*L*gyic*(Pyerh+Pyirh) - L*(Ai*alpha_yi*Pyarm*gyec + beta*Ai*alpha_e*Pyarm*gyic), we can solve for Ai which is the coupling factor of self-heating to surface defocus.

Parameter Value Notes
alpha_x,i 430 ppm from alog 76937
alpha_y,i 375 ppm from alog 76937
alpha_x,e 200 ppm  
alpha_y,e 210 ppm  
P_y,i_rh 0.000 W T0 = 1417899757
P_x,i_rh 0.850 W  
P_x,e_rh 1.950 W  
P_y,e_rh 2.146 W  
P_yarm
385159 W
T0 = 1417899757
P_xarm 385159 T0 = 1417899757
Gx 0.8149 T0 = 1417899757
Gy 0.8198

                    TMS * pi

G    =   cos2 (   ----------------   )

                      FSR

Ai_y -16 uD/W  
Ai_x -26 uD/W  

Summary

Both of these values indicate there is certainly an overestimation of the self-heating impact on surface defocus.

For reference, the current TCS-SIM values for this coupling factor are Ai_y = Ai_x = -36.5 uD/W.   More examination is required into this.


Links to previous alogs:

  1. Estimating HOM spacing shift from self-heating alone:  https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=84172
Non-image files attached to this report
Comments related to this report
matthewrichard.todd@LIGO.ORG - 16:48, Monday 11 August 2025 (86307)

Absorption values here should be ppb, not ppm.

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