Displaying reports 401-420 of 77237.Go to page Start 17 18 19 20 21 22 23 24 25 End
Reports until 14:52, Monday 15 July 2024
H1 OpsInfo (ISC)
thomas.shaffer@LIGO.ORG - posted 14:52, Monday 15 July 2024 (79136)
Added manual_control parameter to lscparams to avoid some automation states when True

Sheila, TJ

In times of heavy commissioning or troubleshooting, we want full control of the IFO and don't want to fight the automation. Sheila suggested that we add a manual_control boolean to lscparams.py that ISC_LOCK will look at to decide whether it will automatically run states like Check_Mich_Fringes, PRMI, Increase_Flashes, etc. When this is set to True, it will avoid these automated state either through a conditional in a state's logic, or by weighting edges to force ISC_LOCK to avoid particular states.

For now we are setting manual_control = True while we troubleshoot the IFO.  We will need to remember to return it when we want fully automatic operation again.

H1 AOS (SEI)
neil.doerksen@LIGO.ORG - posted 12:29, Monday 15 July 2024 - last comment - 15:34, Monday 15 July 2024(79132)
April 18 Seismic Timeline, Lock, Lockloss Summary

Pre April 18

April 18

Post April 18

Comments related to this report
neil.doerksen@LIGO.ORG - 13:18, Monday 15 July 2024 (79133)

Here are some plots around the EQ from April 18, 2024 at which USGS reports coming from Canada at 06:06.

Images attached to this comment
neil.doerksen@LIGO.ORG - 15:34, Monday 15 July 2024 (79138)

Using KAPPA_C channel.

Images attached to this comment
H1 ISC (SQZ)
camilla.compton@LIGO.ORG - posted 12:25, Monday 15 July 2024 (79128)
Translating SQZ beam after IFO alignemt shift

Naoki, Sheila, Camilla

To continue investigating alignment changes: 79105. More details in Sheila's 79127.

We put SRM back to before alignment shift, misaligned SRM2 and ITMs,  injected 1.28mW of SQZ SEED beam (as measured on SQZT7 OPO_IR_PD_DC_POWERMON). Followed as in 78115. Increased AS_AIR camera exposure form 10,000 to 100,000

Translated SQZ beam around last NLN spot, each direction the throughput was getting better but in both pitch directions we saturated ZM4 before moving far. Were able to get all expected 0.9mW throughput by moving ZM5 Pitch and yaw both positive.

Images attached to this report
H1 AOS (DetChar)
mattia.emma@LIGO.ORG - posted 11:52, Monday 15 July 2024 (79129)
Computing the average relock time for O4a

The two attached histograms show the relock times for LIGO Hanford during the whole of O4a.

The average relock time has been 2 hours and 55 minutes, while the median was at 1 hour and 33 minutes.

The relock time was computed as the time for which the ISC_LOCK_N value was consecutively below 580.

The 580 value corresponds to inject squeezing, which is why there were some short "relocks" when we used below 600 for the lockloss threshold, because the squeezer unlocked and relocked automatically.

Link to the github repository with the employed code and data

Images attached to this report
H1 SQZ (IOO, ISC)
sheila.dwyer@LIGO.ORG - posted 11:29, Monday 15 July 2024 (79127)
power estimates for sqz beams

Summary: We think that the sqz beam is seeing similar loss to the IFO beam in th alignment that we were running in until Friday, but double passed. The sqz beam transmission can be restored by moving the beam, and there should be enough power in this beam to be a useful diagnostic in chamber to distinguish between OFI and SRM damage.

Camilla and Noaki have measured 1.3mW coming from HAM7 towards HAM5 with the OPO locked on the seed. SRM transmission is 32.34%, ( 72680 ) so if nothing was damaged we should have something like 0.41mW of the OPO seed beam in transmission of SRM, which we should be able to measure with a power meter. 

The table in 79101 indicates that the single bounce transmission to AS_C has dropped to 64% of what it was last Thursday.  Here's a table of power predictions for the sqz beam arriving in HAM6:

no damage sqz seed beam we expect at AS_C
no damage 1.3mW*(1-0.3234) * 0.99^2 = 0.86mW
single pass of damaged optic with 0.64 transmission 1.3*(1-0.3234)*0.99*0.99 * 0.64 = 0.55mW
double pass of damaged optic with 0.64 tramission 1.3*(1-0.3234)*0.99*0.99 * 0.64 *0.64 = 0.35mW

With the alignment used for observing in recent weeks Naoki and Camilla measured 0.2 mW on AS_C QPD (not well centered on AS_C, but on the diode), which is calibrated into Watts arriving in HAM6.  They moved ZM4 +5 to improve the transmission of the sqz beam to 0.9mW when centered on AS_C.  These numbers don't agree super well with the predictions above, but they seem to suggest that the SQZ beam sees similar damage to the main IFO beam, but double passed.

H1 ISC
jennifer.wright@LIGO.ORG - posted 10:57, Monday 15 July 2024 (79125)
Current dip in output arm gain seems more abrupt compared to previous OFI 'burn' on 22nd April

Sheila asked me to look at the same trends we used to track the damage in the OFI over the 22nd and 23rd of April when it first happened. We think something like this might have happened again on Friday.

Attached you can see the optical gain, coupled cavity pole, range in Mpc, power at the anti-symmetric port, circulating power, and power reflected from the OMC all changed between April the 22nd, when the damage first started affecting the range causing it to decrease slowly.

In the next image we have the same trends from the last couple of days, there doesn't seem to be a slow degradation in range in this case, the range got worse between two locks on the 12th but nothing else seems to have degraded (unlike beforte when we observed a drop in optical gain, circulating power, output power and coupled cavity pole) before we got to the point where we couldn't relock.

Images attached to this report
LHO FMCS (PEM)
ryan.short@LIGO.ORG - posted 09:28, Monday 15 July 2024 (79120)
HVAC Fan Vibrometers Check - Weekly

FAMIS 26315, last checked in alog78896

No appreciable change in any fan's noise levels compared to last check.

Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 09:21, Monday 15 July 2024 (79118)
PSL 10-Day Trends

FAMIS 21008

No major events of note for these trends except for the PSL work done last Tuesday (seen in almost every trend), and, concerningly, a slight rise in PMC reflected power of about 0.3W over 5 days. It seems to have leveled off in the past day or so, however.

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 09:16, Monday 15 July 2024 - last comment - 15:40, Monday 15 July 2024(79119)
Atomic Clock lost sync with timing-system

at 08:50 PDT the MSR Atomic Clock lost sync with the timing system, the comparator is reading a steady 0.24S 1PPS difference. This has happened before, it requires a manual resync of the Atomic Clock to the timing-system 1PPS. This was last done 6th May 2024

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 15:40, Monday 15 July 2024 (79139)

Daniel resynced the Atomic Clock to the timing 1PPS at 15:30 PDT this afternoon. The corner station timing error has gone away.

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 08:11, Monday 15 July 2024 (79115)
Mon CP1 Fill

Mon Jul 15 08:06:22 2024 INFO: Fill completed in 6min 18secs

Jordan confirmed a good fill curbside.

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 07:44, Monday 15 July 2024 - last comment - 09:36, Monday 15 July 2024(79113)
OPS Monday day shift start

TITLE: 07/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

Comments related to this report
ryan.crouch@LIGO.ORG - 08:06, Monday 15 July 2024 (79114)CDS

I'm getting a 502 proxy error whenever I try to load the DCC

david.barker@LIGO.ORG - 08:14, Monday 15 July 2024 (79116)

I'm seeing the same issue from off-site, there is now a message on the page indicating a server issue

Images attached to this comment
david.barker@LIGO.ORG - 09:36, Monday 15 July 2024 (79122)

Jonathan's emailed instructions on how to use the local archived DCC (read-only):
 


1. Goto https://dcc-lho.ligo.org
2. click login
3. Do not click the ligo icon that says fed-proxy (this is what is
broken).
4. Click on the link that says select from a list
5. In the drop down list select the Backup::LHO option
6. Click Ok
7. log on as normal.

This will work.  But you cannot push new documents and it is about a
day out of date.

As for other services, if you get a choice of selecting the backup LHO
login will work that way.  Anything that does not and just goes
straight to the federated proxy (ie like the dcc, you goto a page that
says cilogon.org to select your institution) will not work right now.

This is being worked on and should clear up later.

LHO VE
david.barker@LIGO.ORG - posted 09:15, Sunday 14 July 2024 - last comment - 09:33, Monday 15 July 2024(79108)
Pressure glitch on PT100B HAM1 at 07:25:15 Sun 14 July 2024

There was a pressure glitch on PT100B HAM1 cold-cathode at 07:25:15 PDT this morning. There was no corresponding glitch on any other corner station gauge as far as I can tell.

Pressure increased from 3.3e-08 to 4.0e-08 Torr, recovered in 4 minutes.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:31, Sunday 14 July 2024 (79109)

This is clearly very concerning. 

Attached is a trend of the pressure in the top right, along with several other channels (IMC power in, ISC_LOCK guardian state, RM alignments, DC power levels on all 4 PDs in that chamber), and I don't see anything in any of these channels that looks suspicious.

EDIT to add second screenshot, of in-vac tabletop L4C seismic sensors.  Again, nothing suspicious-looking to me that I see yet.

Images attached to this comment
michael.zucker@LIGO.ORG - 07:41, Monday 15 July 2024 (79112)

Given no lockloss correlation, may not be significant; ~3 orders of magnitude less PV than the June event(s).   Maybe an ion pump burped up some argon.

jordan.vanosky@LIGO.ORG - 09:33, Monday 15 July 2024 (79121)

IP13 ion current/pressure spiked up ~1 second before the PT100B gauge did, see attached. Likely argon instability of the pump

Images attached to this comment
H1 General (ISC, OpsInfo)
ryan.short@LIGO.ORG - posted 01:04, Sunday 14 July 2024 - last comment - 08:42, Monday 15 July 2024(79105)
Comparisons before/after alignment changes

I've gathered several trends comparing the before and after of the alignment shift the IFO saw in the past couple of days, likely on Friday the 12th.

On all of these plots, I use y-cursors to indicate the levels each signal was at the appropriate time leading up to the last lock H1 had fully up to Nominal Low Noise, which lasted from 10:14 to 16:45 UTC on July 12th, in order to compare to what was likely the last time H1 was behaving "well."

DRMI signals with OM1/2 OSEMs:

The last DRMI acquisition before NLN, POP18 was around 66 counts while POP90 was around 11 counts.

The most recent DRMI acquisition, POP18 has dropped to 42 counts while POP90 has risen to 16 counts. The only significant alignment difference I see is with OM1 Y being about 70 counts different.

Optic alignments during 10W single-bounce: (times all taken from when ALIGN_IFO was in the state SR2_ALIGN [58])

The last SR2 alignment before NLN (P/SRC optics; large optics), AS_C_NSUM signal was at 0.0227 counts.

The next time in this configuration (P/SRC optics; large optics), AS_C_NSUM signal had dropped to 0.018 counts. The most obvious alignment changes are with PR2Y, PRM, some SR2, and SRM.

The most recent time in this configuration (P/SRC optics; large optics), AS_C_NSUM signal had dropped again to 0.014 counts. The same optics are off in alignment as before, but PRM has now flipped to being off in the opposite directions for both pitch and yaw.

OFI and KAPPA_C:

I recreated trends like Camilla did in alog78399 to check the behavior of the OFI. See attached for multi-day trend, zoomed in on shakes during high-state locklosses, and zoom in on one of these shakes.

HAM6 vacuum pressure:

Out of an abundance of caution, I trended the pressure gauge on HAM6 since we've seen pressure spikes somewhat recently, and I don't see anything that hasn't been previously noted on a 21-day timescale (the pressure rise ~20 days ago was noted to be because of the OM2 thermistor in alog78829).

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 08:42, Monday 15 July 2024 (79117)ISC

Looking more at the OFI TEC/temperature sensor, it seems like the alignment through the OFI changed, into probably a worse alignment that clipped somewhere (requiring more OFI temperature control as we powered up), at a time between the 2024/07/12 16:45UTC IFO unlock (looked normal, maybe 10-20% larger than normal temp swings) and the Power up at 17:45UTC. See attached. This is before we explicitly changed the SRC alignment.

Images attached to this comment
H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 09:52, Friday 12 July 2024 - last comment - 09:05, Monday 15 July 2024(79073)
Lockloss at 16:44 UTC

16:44 UTC lockloss. PRCL was oscillating at about ~3.6 Hz.

Comments related to this report
ryan.crouch@LIGO.ORG - 12:55, Friday 12 July 2024 (79078)

We've lost it at PREP_DC_READOUT twice in a row, during different points of the OMC locking process. Lockloss tool tags ADS_EXCURSION

camilla.compton@LIGO.ORG - 09:05, Monday 15 July 2024 (79111)

We turned on a PRCL FF the day before: 79035. But this 3.6Hz PRCL wobble is normal, it was constant throughout the lock plot and locks before the feedforward was installed (example).

This lockloss looked very normal, AS_A then IMC loosing lock, as usual, plot.

Images attached to this comment
H1 ISC
sheila.dwyer@LIGO.ORG - posted 16:11, Wednesday 24 April 2024 - last comment - 10:21, Monday 15 July 2024(77392)
we suspect that something in OFI has changed

LHO control room crew-

We suspect that something about the output Faraday has changed. 

The only thing that seems common to these two is the OFI, a baffle in it's vicinity or something like a wire from the fast shutter impacting the beam on the way to OM1.  We'd actuated the fast shutter and see no change in the AS camera, so we don't think that the fast shutter is the issue, which points us to looking at the OFI.

Editing to add that Keita points out something like a bad spot on OM1 is also a possibility.

Images attached to this report
Comments related to this report
ryan.crouch@LIGO.ORG - 10:21, Monday 15 July 2024 (79124)

Recreating this trend for our current situation, power drops aren't as big? Comparing a lock before last Thursday (07/11) to our most recent lock.

Images attached to this comment
Displaying reports 401-420 of 77237.Go to page Start 17 18 19 20 21 22 23 24 25 End