Displaying reports 961-980 of 85916.Go to page Start 45 46 47 48 49 50 51 52 53 End
Reports until 16:20, Monday 13 October 2025
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 16:20, Monday 13 October 2025 (87452)
OPS Eve Shift Start

TITLE: 10/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 14mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.31 μm/s 
QUICK SUMMARY:

IFO is in NLN and OBSERVING (4 hr lock)

Wind is pickign up. Secondary microseism is picking up. Hoping to stay quiet and locked for the shift.

H1 SUS
oli.patane@LIGO.ORG - posted 16:01, Monday 13 October 2025 (87448)
SatAmp Swap Auto Alog
When we're doing the satamp swaps, we always need to write alog comments for each serial number that was updated. The alogs have repetitive text but have multiple values that need to be changed, and it's time-consuming and easy to miss changing something. I've written a script that automatically grabs the info and copies it to your clipboard so you can paste it into an alog.
The script that I made for auto-generating the satamp swap alog is here as r12693:
/ligo/svncommon/SusSVN/sus/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Scripts/satampalog.py
You can run it by entering the serial number of the satamp and using one of the following flags: --uk4ch, --us4ch, or --us8ch for the satamp type.
 
Example:
$ python3 satampalog_4Jeff.py S1100147 --uk4ch
Alog for S1100147 is copied to clipboard. CRTL+V into alog and 'Preview' or 'Save to Draft' to fix formatting.
 
Pasting into an alog initially, it'll look like this
Click 'Save to Draft' to fix the formatting. It'll then look like this
Images attached to this report
H1 SUS (SEI)
oli.patane@LIGO.ORG - posted 13:22, Monday 13 October 2025 - last comment - 15:54, Monday 13 October 2025(87444)
SR3 P Estimator Blend filter swapped (back)

For the SR3 P estimator, we had initially developed and installed blend filters (in H1:SUS-SR3_M1_EST_P_FUSION_MEAS_BP and H1:SUS-SR3_M1_EST_P_FUSION_MODL_BP filter banks), named pit_v1, that blended between the OSEMs on-resonance, and the estimator everywhere else (86452). After a bit, Brian Lantz made a pit_v2 that included OSEM damping at two extra frequencies because we were having issues with extra resonances at 0.65 and 0.75 Hz that weren't being damped (86510)(filter comparisons).
Eventually we realized the reason why those two peaks weren't being damped was because we had forgotten to include the model contribution to P from L, and we installed those needed filters(86567). However, we didn't swap the blend filters back to pit_v1 at the time.
So during relocking today (2025/10/13 19:05:00 UTC), I swapped us back to pit_v1. We will run with this until at least tomorrow morning and then verify that we don't see a difference in the damping of those two peaks.

Images attached to this report
Comments related to this report
brian.lantz@LIGO.ORG - 13:44, Monday 13 October 2025 (87445)

Oli - Thanks for doing this test, I'm looking forward to learning what happens. I think the question here is "how well does it work" and "what do we see" rather than "does it work". I'm hoping this will reduce the RMS a bit, although the analysis is complicated by the cross-coupling w/ length.

H1 General
thomas.shaffer@LIGO.ORG - posted 11:08, Monday 13 October 2025 - last comment - 12:23, Monday 13 October 2025(87441)
Lock loss 1747 UTC

Lock loss 1444412849

While it was during commissioning, it seems like it wasn't any of the activities going on at the time. Looks very much like the most recent lock losses we have that very quickly go.

Comments related to this report
thomas.shaffer@LIGO.ORG - 12:23, Monday 13 October 2025 (87443)

Back to observing at 1917 UTC. Ran initial alignment, but I didn't have to do anything.

H1 ISC
elenna.capote@LIGO.ORG - posted 10:41, Monday 13 October 2025 (87439)
Changing OFI temperature test

Jennie W, Elenna

Today we changed the OFI temperature and monitored the OFI PD A power. At each temperature change, we reran Sheila's OMC fringe wrapping injection to replicate the measurement Sheila and Naoki did in alog 78942.

Results: we did not see a very significant change in the OFI PD A power when we changed the OFI temperature from 37.5 C to 25.5 C. We see a smaller scattering shelf at 25.5 C than we do at 37.5 C.

I saved Sheila's template over into my own directory as /ligo/home/elenna.capote/OFI/OMC_fringe_wrapping.xml

She had old references in that template (different from the alog) that were taken in Sept 2024. Those references indicated that an OFI temperature of 37.5 C had the smallest scattering shelf. Today, Jennie and I saw very little difference between the scattering shelves generated at 37.5 C (nominal temperature), 34.5 C and 30.5 C. Only when we measured at 25.5 C did we see the scatter shelf reduce slightly (plot).

In this plot, I added in Sheila's old references that show the exact opposite result a year ago. Specifically, the 25.5 C measurement from now is very close to the old 37.5 C measurement from a year ago.

At first, I didn't think there was much of a change in the power on OFI PD A. However, looking at the second trend, it looks like maybe the power dropped by a small amount. I might have needed to slow down this test more than I realized (plot). I saved this ndscope template in /ligo/home/elenna.capote/OFI/OFI_TEC.yaml

 

Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:34, Monday 13 October 2025 (87440)
Mon CP1 Fill

Mon Oct 13 10:07:35 2025 INFO: Fill completed in 7min 32secs

 

Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 10:02, Monday 13 October 2025 (87438)
PSL 10-Day Trends

FAMIS 31107

The main changes that can be seen this week are a result of our amplifier pump diode current adjustments on Tuesday (alog87338). Otherwise, no major events this week.

Images attached to this report
LHO General
thomas.shaffer@LIGO.ORG - posted 07:38, Monday 13 October 2025 (87435)
Ops Day Shift Start

TITLE: 10/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 12mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.22 μm/s 
QUICK SUMMARY: Locked for 21.5 hours. No alarms, two GRB shorts overnight.

LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 22:00, Sunday 12 October 2025 (87434)
OPS Eve Shift Summary

TITLE: 10/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is in NLN and OBSERVING (12 hr lock)

We were locked for the entirety of shift.

The range came back over the course of the shiftso did not have to leave OBSERVING to touch up the squeezer.

Wind and ground motion look good

LOG:

 

LHO General
thomas.shaffer@LIGO.ORG - posted 16:30, Sunday 12 October 2025 (87427)
Ops Day Shift End

TITLE: 10/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: One lock loss that only needed initial alignment but full auto. After we thermalized I ran a calibration sweep in coordination with LLO. The range for this most recent lock looks to be trending down slightly. The SQZ blrms see it, but Ibrahim will keep an eye on things.
LOG:

LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 16:02, Sunday 12 October 2025 (87433)
OPS Eve Shift Start

TITLE: 10/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 27mph Gusts, 21mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.22 μm/s 
QUICK SUMMARY:

IFO is in NLN and OBSERVING (6 hr lock).

Range is slowly going down seemingly due to SQZ. Wind is also picking up. If range continues to degrade, will re-tune the squeezer.

H1 TCS
thomas.shaffer@LIGO.ORG - posted 15:47, Sunday 12 October 2025 (87432)
TCS Chiller Water Level Top-Off - Biweekly

FAMIS27825

No water added, values all looked good and were recorded into the sheet T2200289 sheet.

I somehow missed this and its a week late, next one should run next week.

H1 CAL
thomas.shaffer@LIGO.ORG - posted 14:04, Sunday 12 October 2025 (87431)
Calibration Sweep 1958 UTC

Coordinated a calibration measurement with LLO since we couldn't get it done yesterday. Back into observing 2029UTC

Simulines start:

PDT: 2025-10-12 13:04:59.811759 PDT
UTC: 2025-10-12 20:04:59.811759 UTC
GPS: 1444334717.811759

Simulines end:

PDT: 2025-10-12 13:28:25.449920 PDT
UTC: 2025-10-12 20:28:25.449920 UTC
GPS: 1444336123.449920

Files:

2025-10-12 20:28:25,294 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_
SS/DARMOLG_SS_20251012T200500Z.hdf5
2025-10-12 20:28:25,302 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DA
RM_SS/PCALY2DARM_SS_20251012T200500Z.hdf5
2025-10-12 20:28:25,308 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L1_SS/SUSETMX_L1_SS_20251012T200500Z.hdf5
2025-10-12 20:28:25,312 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L2_SS/SUSETMX_L2_SS_20251012T200500Z.hdf5
2025-10-12 20:28:25,317 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L3_SS/SUSETMX_L3_SS_20251012T200500Z.hdf5
 

Images attached to this report
Non-image files attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:25, Sunday 12 October 2025 (87430)
Sun CP1 Fill

Sun Oct 12 10:08:26 2025 INFO: Fill completed in 8min 22secs

 

Images attached to this report
H1 SUS
thomas.shaffer@LIGO.ORG - posted 09:57, Sunday 12 October 2025 (87428)
SRM watchdog trip thresholds updated

We've recently been having some issues with SRM tripping during initial alignment and during DRMI acquisition, alog87370 for example. After consulting with Jeff K, I've bumped up the trip thresholds as listed below. This was based off of the last few trips, so hopefully it has enough of a buffer now. Saved in the safe and observe sdfs.

  Old New
M1 150 250
M2 200 350
M3 225 400

 

Images attached to this report
H1 General
thomas.shaffer@LIGO.ORG - posted 08:31, Sunday 12 October 2025 - last comment - 10:00, Sunday 12 October 2025(87426)
Lock loss 1515 UTC

Lock loss 1444317365

No obvious cause, ended a 29.5hour lock.

Comments related to this report
thomas.shaffer@LIGO.ORG - 10:00, Sunday 12 October 2025 (87429)

1659 Observing. Needed an initial alignment, but all auto.

H1 ISC
elenna.capote@LIGO.ORG - posted 11:58, Thursday 02 October 2025 - last comment - 11:57, Monday 13 October 2025(87260)
Camera spot calibration

Today I began calibrating the camera servo signals into spot positions. I ran the A2L script at the nominal camera spot positions. Then, I changed the camera offset and waited for the camera servo to converge. Then I remeasured the A2L gain. Using the a2l_lookup function in /opt/rtcds/userapps/release/isc/common/scripts/decoup/BeamPosition the A2L gain can be converted into a spot position in mm. This is a slow process so it will take time to get the conversions for all.

  Camera offset A2L gain Conversion
ETMY Pitch start: -230, end: -231 start: 5.62, end: 5.92

(-23.2 mm - -21.8 mm)/-1ct 

= 1.4 mm/ct

ITMX Pitch start: -230, end: -231 start: -0.45, end: -0.56

(6.46 mm - 5.96 mm)/-1ct  

= -0.5 mm/ct

 

Comments related to this report
elenna.capote@LIGO.ORG - 10:23, Monday 06 October 2025 (87313)

I continued today following the same process stated above.

  Camera offset A2L gain Conversion
ETMX P start: -173, end: -172 start: 3.04, end: 2.92

(-9.38 mm - -9.93 mm)/ 1ct 

= 0.55 mm/ct

ETMY Y start: -349.5, end: -348.5 start: 1.41, end: 1.06

(3.90 mm - 5.18 mm) / 1ct 

= -1.28 mm/ct

ETMX Y start: -422, end: -421 start: 4.85, end: 4.68

(17.22 mm - 17.84 mm)

= -0.62 mm/ct

elenna.capote@LIGO.ORG - 11:57, Monday 13 October 2025 (87442)

I reran the ITMX beam spot calibration following the same method described above, but this time I checked how the beam spot moved on both ITMX and ITMY when I changed the BS camera offset. Turns out, they give the same answer, so that's good.

  Camera Offset A2L gain Conversion
ITMX P (ITMY P) start: -230 ct, end: -231 ct start: -0.45 (0.19), end: -0.55 (0.09)

(6.41 mm - 5.96 mm)/-1 ct

= -0.45 mm/ct

ITMX Y (ITMY Y) start: -236 ct, end: -237 ct start: 3.18 (-2.75), end: 3.06 (-2.63)

(11.26 mm - 11.70 mm)/ -1ct

= 0.44 mm/ct (-0.44 mm/ct for ITMY)

 

H1 SUS (ISC)
jeffrey.kissel@LIGO.ORG - posted 16:20, Tuesday 08 July 2025 - last comment - 14:30, Monday 13 October 2025(85639)
H1SUSITMY L2DAMP P and R Open Loop Gain TFs
E. Capote, J. Kissel, S.Dwyer

The ~1 Hz ring-up that had been marginally stable and transient is now fully unstable during the lock acquisition sequence as we recover from maintenance. The suspicion is that the change in ITM M0/R0 satamps might have changed the top mass damping loop OLGTF enough to augment the damped plant that's the plant for the never-really-well-designed L2DAMP that takes the L2 (or PUM) OSEMs and feeds back their sensor signal to the reaction chain top mass OSEMs actuators. But also, we've never measured these loops in any substantial form, so we wanted to just see what they were doing.

Attached are the results. Here're the templates:
    /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/
        2025-07-08_2240UTC_H1SUSITMY_R0_WhiteNoise_0p02to50Hz_L2DAMP_OLGTF_P.xml
        2025-07-08_2240UTC_H1SUSITMY_R0_WhiteNoise_0p02to50Hz_L2DAMP_OLGTF_R.xml

Very little loop gain and only at 3.3 Hz. The loop stability is questionable at that frequency -- for a few averages the suppression (i.e. the gain peaking) looks really sharp around 3.3 Hz. 
T'was really tough to get good coherence; the excitation is pretty well tailored, but it's tough to fight the 1/f^6 suppression of the physical suspension and dirt coupling.
I had to turn OFF the R0 alignment offsets to get this data for pitch. (They were ON for the Roll measurement).

So -- perhaps not the source of the ~1 Hz IFO instability, but boy could this loop use some TLC in order to more effectively achieve its goals...
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 14:30, Monday 13 October 2025 (87447)
FYI, we also took ITMX data for these loops as well.
    /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data
        2025-07-08_2240UTC_H1SUSITMX_R0_WhiteNoise_0p02to50Hz_L2DAMP_OLGTF_P.xml
        2025-07-08_2240UTC_H1SUSITMX_R0_WhiteNoise_0p02to50Hz_L2DAMP_OLGTF_R.xml
Images attached to this comment
Displaying reports 961-980 of 85916.Go to page Start 45 46 47 48 49 50 51 52 53 End