Displaying reports 1961-1980 of 85662.Go to page Start 95 96 97 98 99 100 101 102 103 End
Reports until 22:06, Sunday 03 August 2025
H1 General
anthony.sanchez@LIGO.ORG - posted 22:06, Sunday 03 August 2025 (86163)
Sunday Eve Shift report.

TITLE: 08/04 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
H1 was locked for a good 6 hours then had an unknown lockloss.
Relocking was interupted at LOWNOISE_COIL_DRIVERS, due to a 6.2 M  earth_quake whcih took H1 to DOWN.

H1 is currently waiting in Earthquake mode.


LOG:
                                                                                                            

Start Time System Name Location Lazer_Haz Task Time End
21:34 SPI Tony PCAL Lab Yes Testing beam Splitter ratio analysis tools 22:13

 

H1 PEM (DetChar)
robert.schofield@LIGO.ORG - posted 17:41, Sunday 03 August 2025 - last comment - 17:35, Tuesday 05 August 2025(86160)
Jitter peaks below 40 Hz remain in cleaned spectra

We have many peaks below 40 Hz that couple, at least partly, through input beam jitter. Last summer Sam and Genevieve determined that a wide variety of site equipment produced these peaks, including the office area air handler, mini-splits in the CER, and chiller compressors for the main HVAC (LIGO-G2402140).  The figure shows that there is coherence between DARM and the IMC WFS that might be used to clean these low frequency peaks, but that they are currently not being cleaned.

Eventually, we would rather not have peaks that need cleaning, but instead, reduce the source vibration and/or the vibration coupling to DARM. I think that the best plan is to reduce the source vibration of the largest peaks, but to mainly focus on reducing the coupling, because many of these peaks are just 2-5 times the vibration background at the coupling sites, so even eliminating the vibration of the sources will not be enough to get us to our design sensitivity.

The coupling of relatively low amplitude vibrations at low frequencies seems to be associated with coupling resonances. For example, when one of the frequencies of the office area air handler drifted into the 35Hz peak frequency of one of these coupling resonances, the peak in DARM was huge, but was greatly reduced by changing the operation frequency of the air handler (82986).  Ill try to map out these low frequency coupling resonances during commissioning periods as a step in understanding their cause.  But for now, it would be nice to see how much we can reduce the peaks with cleaning.

Non-image files attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 10:42, Monday 04 August 2025 (86171)

The nonsens training for the cleaning is set to clean over the band from 20 Hz to 8 kHz. However, the most appreciable cleaning occurs above 100 Hz. I have attached two plots from the recent training Matt and I ran. The first compares the strain before and after the code runs an offline cleaning of the data. Even in the offline cleaning, it does not perform any subtraction below 60 Hz. The contributions plot shows that the code measures a contribution from IMC WFS A pitch and yaw that is approximately 2 orders of magnitude below the strain.

Similarly, the noise budget injections usually indicate a very low jitter coupling below 60 Hz. This plot is the jitter subbudget showing pitch and yaw contributions. I removed the "total H1" line, since it's currently incorrect. However, this plot only shows contributions from IMC WFS A, and jitter is measured using the IMC PZT, which may only allow us to capture one gouy phase.

All of this is to say, despite this coherence, the nonsens algorithm doesn't find anything to subtract at low frequency. Our noise budget also doesn't show significant coupling here.

Adding: Robert and I think it may be a resolution issue. The noise budget resolution is quite broad at 0.3 Hz, so that may be why those peaks are not captured in the injection. I'm not sure how to address or test the nonsens cleaning resolution.

Images attached to this comment
elenna.capote@LIGO.ORG - 17:35, Tuesday 05 August 2025 (86216)

I have iterated through many different parameters in the nonsens algorithm, including length of time, frequency resolution, number of second order sections, maximum permitted Q value, training method, and frequency band. I am unable to achieve subtraction that is comparable to the measured coherence of these lines. At best, I have achieved 40% reduction of two of the many lines. At best I can achieve 10% reduction of some of the broadband noise. Since I am training offline, I don't expect this to be the result of some funny phase delay between the models. I'm not sure why cleaning these features isn't possible.

H1 General
anthony.sanchez@LIGO.ORG - posted 16:50, Sunday 03 August 2025 (86161)
Sunday Eve Shift Start

TITLE: 08/03 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

H1 has been locked for 2 Hours and 20 minutes.
All systems seem to be functioning well.
Hoping for a smooth shift of Observing.

H1 General
oli.patane@LIGO.ORG - posted 16:29, Sunday 03 August 2025 (86159)
Ops Day Shift End

TITLE: 08/03 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently Observing at 155Mpc and have been Locked for a little over 2 hours. One lockloss today and after some issues with ALS not wanting to stay locked (partially due to ground motion, partially unknown), after an initial alignment we were able to relock fine. We dropped out of Observing once due to the squeezer unlocking but it was able to fix itself.
LOG:

18:05 Lockloss
    - Lockloss from PRMI/DRMI multiple times due to ALSX or Y unlocking
    - Ran an initial alignment
21:19 NOMINAL_LOW_NOISE
    21:21 Observing
    22:10 Out of Observing due to SQZer unlock
    22:15 Back into Observing

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 11:24, Sunday 03 August 2025 - last comment - 14:22, Sunday 03 August 2025(86157)
Lockloss

Lockloss at 2025-08-03 18:05UTC after over 7.5 hour locked

Comments related to this report
oli.patane@LIGO.ORG - 14:22, Sunday 03 August 2025 (86158)

21:21 UTC Back to Observing

LHO VE
david.barker@LIGO.ORG - posted 10:16, Sunday 03 August 2025 (86156)
Sun CP1 Fill

Sun Aug 03 10:08:00 2025 INFO: Fill completed in 7min 56secs

 

Images attached to this report
H1 General (SQZ)
thomas.shaffer@LIGO.ORG - posted 08:49, Sunday 03 August 2025 (86155)
Back to Observing WITH Squeezing

After LLO dropped out, Jenne gave the OK to try to get squeezing back. The FC took a handful of minutes of trying and failing but then just worked. I used <a href="https://cdswiki.ligo-wa.caltech.edu/wiki/ObservationWithOrWithoutSqueezing">Ryan S's script</a> to get us back to being able to observe with sqz and we are back to Observing.

Out of Observing from 1539-1546UTC.

LHO General
thomas.shaffer@LIGO.ORG - posted 07:39, Sunday 03 August 2025 (86154)
Ops Day Shift Start

TITLE: 08/03 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 130Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: The IFO is still in Observing without squeezing as Corey had left it. I'll give a squeezer a call as soon as I can organize my already impromptu morning.

H1 SQZ (SQZ)
corey.gray@LIGO.ORG - posted 06:05, Sunday 03 August 2025 (86153)
OWL Shift Wake Up Due To SQZ FC At 3:33amPDT....Eventually Went To Observing WITHOUT SQZ

Looks like H1 went down due to an EQ (probably M6.8 Russia EQ) 4+hrs ago, and was at NLN but having SQZ Issues:

Frustration NOTES: 

Images attached to this report
H1 General
anthony.sanchez@LIGO.ORG - posted 22:00, Saturday 02 August 2025 (86152)
Saturday Ops Shift End

TITLE: 08/03 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
H1 has reached 24 Hours of continuous lock!
All systems lookin good.
No issues all night.
Passing Corey a locked IFO for his OWL shift.
 
LOG:                                                                                                           

Start Time System Name Location Lazer_Haz Task Time End
00:00 SPI Tony PCAL Lab Yes Testing slides 00:05

 

H1 General
anthony.sanchez@LIGO.ORG - posted 16:52, Saturday 02 August 2025 (86151)
Saturday Ops Eve Shift Start

TITLE: 08/02 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 10mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:
H1 has been Locked for 19 Hours now with decent range.
No issues to report.

 

 

H1 General
oli.patane@LIGO.ORG - posted 16:31, Saturday 02 August 2025 (86150)
Ops Day Shift End

TITLE: 08/02 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:We are Observing at 149 Mpc and have been Locked for almost 19 hours. Besides the calibration measurement today, we've been Observing the rest of my shift.
LOG:

14:30UTC Observing and have been Locked for 9:44 hours
    14:30 Earthquake mode activated
    15:25 Back to CALM
    18:18 Earthquake mode
    18:31 Left Observing to run calibration suite
    18:31 NLN_CAL_MEAS
    19:03 NOMINAL_LOW_NOISE
    19:03 Observing
    20:25 Superevent S250802dn

H1 SUS
oli.patane@LIGO.ORG - posted 14:01, Saturday 02 August 2025 (86149)
Satamp swap OSEM noise part 4 (MC1, MC3, ETMY M0/R0, TMSY)

On July 22nd, Fil swapped the satamps for MC1, MC3, ETMY M0/R0, and TMSY (85922). Here are the differences in the noise performance for each before and after the swap.

Finding times where ISC control wasn't on and the chambers were in nominal states (not earthquake or maintenance) was hard to do because of all the earthquakes we've been having. ETMY M0 and R0 both were hard to find good times for, so a couple of times chosen are not the best showcase of the new noise floor. For example, ETMY M0 L 'after' still has a lot of lower frequency noise that I wasn't able to regress out, and ETMY R0 L, T, and V 'after' also all clearly all have excess low frequency noise remaining due to an earthquake going through at the time. I think you can still generally get an idea of how much better the noise is though. I can run them again when we get a better comparison time.

MC1
Results:
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC1/SAGM1/Results/allDampRegressCompare_H1SUSMC1_M1_NoiseComparison_1437192600vs1437240215-1200.pdf
r12495
Data:
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC1/SAGM1/Data/dampRegress_H1SUSMC1_M1_1437192600_1200.mat
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC1/SAGM1/Data/dampRegress_H1SUSMC1_M1_1437240215_1200.mat
r12495

MC3
Results:
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC3/SAGM1/Results/allDampRegressCompare_H1SUSMC3_M1_NoiseComparison_1437115850vs1437282002-1200.pdf
r12496
Data:
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC3/SAGM1/Data/dampRegress_H1SUSMC3_M1_1437115850_1200.mat
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC3/SAGM1/Data/dampRegress_H1SUSMC3_M1_1437282002_1200.mat
r12496

TMSY
Results:
/ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSY/SAGM1/Results/allDampRegressCompare_H1SUSTMSY_M1_NoiseComparison_1437213557vs1437257352-1200.pdf
r12497
Data:
/ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSY/SAGM1/Data/dampRegress_H1SUSTMSY_M1_1437213557_1200.mat
/ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSY/SAGM1/Data/dampRegress_H1SUSTMSY_M1_1437257352_1200.mat
r12497

ETMY
M0
Results:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGM0/Results/allDampRegressCompare_H1SUSETMY_M0_NoiseComparison_1436521059vs1437280243-1200.pdf
r12498
Data:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGM0/Data/dampRegress_H1SUSETMY_M0_1436521059_1200.mat
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGM0/Data/dampRegress_H1SUSETMY_M0_1437280243_1200.mat
r12498

R0
Results:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGR0/Results/allDampRegressCompare_H1SUSETMY_R0_NoiseComparison_1435436097vs1437438025-1200.pdf
r12499
Data:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGR0/Data/dampRegress_H1SUSETMY_R0_1435436097_1200.mat
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGR0/Data/dampRegress_H1SUSETMY_R0_1437438025_1200.mat
r12499

Non-image files attached to this report
H1 CAL
oli.patane@LIGO.ORG - posted 12:11, Saturday 02 August 2025 (86148)
Calibration Measurement August 02, 2025

This set of measurements was taken 13 hours into a lock so we were well thermalized.

Report generated and can be found at /ligo/groups/cal/H1/reports/20250802T183908Z/H1_calibration_report_20250802T183908Z.pdf

Broadband
start: 18:32:06 UTC (1438194744)
end: 18:37:24 UTC (1438195062)
output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250802T183213Z.xml

Simulines
start: 18:39:07 UTC (1438195165)
end: 19:02:14 UTC (1438196552)
output:
/ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250802T183908Z.hdf5
/ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250802T183908Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250802T183908Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250802T183908Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250802T183908Z.hdf5

Images attached to this report
Non-image files attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:26, Saturday 02 August 2025 (86147)
Sat CP1 Fill

Sat Aug 02 10:09:10 2025 INFO: Fill completed in 9min 6secs

 

Images attached to this report
H1 General
oli.patane@LIGO.ORG - posted 07:31, Saturday 02 August 2025 (86145)
Ops Day Shift Start

TITLE: 08/02 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

Currently Observing at 155 Mpc and have been Locked for almost 10 hours. One earthquake just started coming in and now it's really coming in and we just went into earthquake mode

H1 General
anthony.sanchez@LIGO.ORG - posted 22:02, Friday 01 August 2025 (86144)
Friday Eve Shift End Report.

TITLE: 08/02 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
Inherited a Locked IFO.
At 02:57:54 UTC H1 lost lock.

I allowed H1 to try to relock itself, ISC_lock ended up in Aquire_PRMI with wonky flashes. So I did an Initial_Alignment.
I reverted the SEI SDF diffs I accepted earlier today.

The Initial_Alignment was mared with a tripped SRM Watchdog, but it seemed to complete and offload well enough.

H1 was relocked at 4:51:05 UTC. 

LOG:
No Log

 

H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 21:30, Friday 01 August 2025 - last comment - 10:22, Monday 04 August 2025(86143)
Lockloss from NLN

Lockloss from NLN 2025-08-02 02:57:54
Looks like maybe it's an ASC excursion?

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 10:22, Monday 04 August 2025 (86169)

This lockloss does seem to be the result of some big kick that at least the ASC loops see, although it appears stronger in pitch and does not have the same behavior as our yaw excursion locklosses that we linked to the TMSX suspension.

H1 General (SEI)
anthony.sanchez@LIGO.ORG - posted 16:52, Friday 01 August 2025 - last comment - 21:05, Friday 01 August 2025(86140)
Friday Eve Shift Strarting Report.

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

Observing reached at 23:43:12 UTC But only after spending 13 min trying to determine why there is are SEI SDF Diffs.
We, (TJ, Oli, Me) decided to just accept them and hope for the best.

 

Images attached to this report
Comments related to this report
anthony.sanchez@LIGO.ORG - 21:05, Friday 01 August 2025 (86142)

I reverted all of these SDF's for the SEI GS13 on HAM 2, 3, 4, & 5 once we lost lock because Mr. Crouch said that those are older version of the filters.

Images attached to this comment
Displaying reports 1961-1980 of 85662.Go to page Start 95 96 97 98 99 100 101 102 103 End