Displaying reports 921-940 of 88149.Go to page Start 43 44 45 46 47 48 49 50 51 End
Reports until 07:43, Tuesday 07 April 2026
LHO General
corey.gray@LIGO.ORG - posted 07:43, Tuesday 07 April 2026 - last comment - 07:51, Tuesday 07 April 2026(89800)
Tues DAY Ops Transition

TITLE: 04/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.15 μm/s 
QUICK SUMMARY:

Things on the menu for today, HAM1's +y door, venting the corner, and a lot of prep (HAM3 doors should also be coming off this week & more prep for BBSS work!). 

h1seih7 is still down (so HAM7 SEI & SUS systems are all red). 

The Ops Overview also continues to have "IMC INPUT POWER" flashing from 0-200W (but I was assured this was not real and purely a calculation error; light pipes have been closed since last Fri morning).

OPS Note:  I will leave the con around 1045amPDT for a tour and then to attend a BBSS preparation meeting at 1pm PDT and RyanC has graciously offered to cover for me.

Comments related to this report
corey.gray@LIGO.ORG - 07:51, Tuesday 07 April 2026 (89801)PEM

Ran the dust monitor check and LAB2 has  error (known issue) and all else looks good.

H1 CDS
david.barker@LIGO.ORG - posted 07:24, Tuesday 07 April 2026 - last comment - 13:29, Tuesday 07 April 2026(89797)
CDS Maintenance Summary: Monday 6th April 2026

WP13100 Add 3 ADC to h1seih7 for h1susauxh6

Marc, Jeff, Corey, Jim, EJ, Erik, Dave:

After being tested on the DTS, 3 ADCs were added to h1seih7 for HAM6 SUSAUX. We took the opportunity to upgrade the firmware on the timing card and replace its sync-ribbon.

After the upgrade the single 16bit-DAC on this system ran immediately into a FIFO-EMPTY state and the IOP has a permanent DAC status. We verified the card and cable seating, all good but no change. We removed the 3 new ADCs, no change. We removed the 3 new ADC Interface cards, no change.

At this point we ran out of time, Jim said it was OK to leave HAM7 SEI down for the night. We will try timing card and DAC swapouts Tuesday.

WP13115 Reduce susb13 SWWD trip times

Jeff, Corey, Dave:

I installed a modified h1iopsusb13 which reduced the total SWWD SUS trip times for the ITMs from 20 mins to 15 mins ( from 5+15 to 5+10).  All models on h1susb13 were restarted, no DAQ restart was needed.

WP13132 Add ADC to h1susb2h34

Marc, Erik, Jeff, Corey, EJ, Dave:

After being tested on the DTS, an additional ADC was added to the h1susb2h34 IO Chassis. The timing card sync-ribbon was also replaced.

The h1iopsusb2h34 model was modifed to add the ADC. A DAQ restart is needed (pending).

WP13133 Add ADC to h1susauxb2h34

Marc, Erik, Jeff, EJ, Dave:

After being tested on the DTS, an additional ADC was added to the h1susauxb2h34 IO Chassis. The timing card sync-ribbon was also replaced.

The h1iopsusauxb2h34 model was modifed to add the ADC. A DAQ restart is needed (pending).

No DAQ Restart Was Done

Due to the h1seih7 issues we did not restart the DAQ on Monday. This means we have bad DAQ data for the models:

h1iopsusb2h34, h1iopsusauxb2h34, h1spih23.

Tuesday we will fix the h1seih7 issue, then restart the DAQ to resync INI for the two B2H34 models and add the new models h1spih23, h1suslo12, h1susauxh6.

 

Comments related to this report
erik.vonreis@LIGO.ORG - 13:29, Tuesday 07 April 2026 (89808)

SN of ADCs added to h1seih7

ADC2 S2500762

ADC3 S2500755

ADC4 250520-01

ADC Adapter cards are 

S2101465, S2101462, S1102541

but I'm not sure of the order.

 

SN of new ADC and adapter for h1susb2h34

ADC: S2500748 Adapter: S1301436

 

SN of new ADC and adapter for h1susauxb2h34

ADC: S2500761  Adapter: S1900074

H1 CDS
erik.vonreis@LIGO.ORG - posted 07:02, Tuesday 07 April 2026 - last comment - 07:32, Tuesday 07 April 2026(89796)
Workstations updated

Workstations were updated and rebooted.  This was an os packages update.  Conda packages were not updated.

Comments related to this report
corey.gray@LIGO.ORG - 07:32, Tuesday 07 April 2026 (89798)

one of the ops work stations (cdsws29) was stuck on the reboot, so I rebooted the machine (I think I choose Debian "something" while bringing it back up) and it came up ok.

nuc25 appears to be missing some spectra.  (Re-running the launch script [w/ a " ./startup/launch.sh "],  did the trick.)

LHO General
corey.gray@LIGO.ORG - posted 16:40, Monday 06 April 2026 (89786)
Mon Day Ops Summary

TITLE: 04/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

GV2 was hard closed, one of HAM1's doors (-y) was installed (+y tomorrow). 

Suite of CDS tasks were started in the afternoon (had issues with restoring SEIH7).

Please Ignore:  "IMC INPUT POWER" Ops Overview  (Jennie mentioned the calculation is not correct on this medm.)

LOG:

H1 SYS
betsy.weaver@LIGO.ORG - posted 14:13, Monday 06 April 2026 - last comment - 16:28, Monday 06 April 2026(89793)
BSC2 Cross Flow cleanroom and eMOD platform access
Randy has been hard at work adding temp handrails and the eMod garbing cleanroom to the BSC2 platform access area.  Its pretty workable now.  The temp handrails have a pretty large footprint so I might make changes to those in the next incarnation of this, so the walkway from the eMod to the BSC2 platform is pretty narrow.  This platform and eMod placement will service BSC1 and BSC3 as well however, so we will rework or remove some handrails as we add those sections.  The tent is easy to pull back when we need the dome and cartridge to be craned away.
Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 16:28, Monday 06 April 2026 (89795)EPO

tagging for EPO photos

H1 AOS
betsy.weaver@LIGO.ORG - posted 14:06, Monday 06 April 2026 (89792)
Ham1 closeout again, Trello Plan for next few weeks - BBSS vent start
Now that HAM1 is closing again (doors going on with VAC team now), we are turning attentions back to the CDS and BBSS work slated in line next.  Attached is the snapshot of the Trello with the next vent actions queued up.  We anticipate venting the corner chamber volume and also opening HAM3 this week.
Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 12:09, Monday 06 April 2026 (89791)
PSL 10-Day Trends

FAMIS 31132

The broken anteroom fan was swapped last Wednesday, so there are changes seen on several trends at that time. The ISS diffracted power increased, so I've just adjusted the RefSignal slightly to bring the diffracted power back down to around 4% and the PMC transmission back up to what it was before the fan swap.

Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:48, Monday 06 April 2026 (89790)
Mon CP1 Fill

Mon Apr 06 10:07:21 2026 INFO: Fill completed in 7min 18secs

 

Images attached to this report
H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 09:09, Monday 06 April 2026 (89789)
SEI ground seismometer mass position check - Monthly (#39345)

Monthly FAMIS Check (#39345)

T240 Centering Script Output:

Averaging Mass Centering channels for 10 [sec] ...
2026-04-06 09:03:52.267253
There are 11 T240 proof masses out of range ( > 0.3 [V] )!
ETMX T240 2 DOF X/U = -1.862 [V]
ETMX T240 2 DOF Y/V = -1.903 [V]
ETMX T240 2 DOF Z/W = -1.191 [V]
ITMX T240 1 DOF X/U = -2.423 [V]
ITMX T240 1 DOF Z/W = 0.37 [V]
ITMX T240 3 DOF X/U = -2.723 [V]
ITMY T240 3 DOF X/U = -1.215 [V]
ITMY T240 3 DOF Z/W = -3.11 [V]
BS T240 3 DOF X/U = -0.38 [V]
HAM8 1 DOF Y/V = -0.456 [V]
HAM8 1 DOF Z/W = -0.766 [V]

   All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = -0.079 [V]
ETMX T240 1 DOF Y/V = -0.076 [V]
ETMX T240 1 DOF Z/W = -0.114 [V]
ETMX T240 3 DOF X/U = -0.097 [V]
ETMX T240 3 DOF Y/V = -0.159 [V]
ETMX T240 3 DOF Z/W = -0.087 [V]
ETMY T240 1 DOF X/U = 0.027 [V]
ETMY T240 1 DOF Y/V = 0.07 [V]
ETMY T240 1 DOF Z/W = 0.259 [V]
ETMY T240 2 DOF X/U = -0.204 [V]
ETMY T240 2 DOF Y/V = 0.238 [V]
ETMY T240 2 DOF Z/W = 0.042 [V]
ETMY T240 3 DOF X/U = 0.267 [V]
ETMY T240 3 DOF Y/V = 0.048 [V]
ETMY T240 3 DOF Z/W = 0.007 [V]
ITMX T240 1 DOF Y/V = 0.28 [V]
ITMX T240 2 DOF X/U = 0.119 [V]
ITMX T240 2 DOF Y/V = 0.163 [V]
ITMX T240 2 DOF Z/W = 0.263 [V]
ITMX T240 3 DOF Y/V = 0.143 [V]
ITMX T240 3 DOF Z/W = 0.057 [V]
ITMY T240 1 DOF X/U = -0.045 [V]
ITMY T240 1 DOF Y/V = 0.16 [V]
ITMY T240 1 DOF Z/W = -0.038 [V]
ITMY T240 2 DOF X/U = 0.052 [V]
ITMY T240 2 DOF Y/V = 0.2 [V]
ITMY T240 2 DOF Z/W = 0.036 [V]
ITMY T240 3 DOF Y/V = -0.021 [V]
BS T240 1 DOF X/U = 0.043 [V]
BS T240 1 DOF Y/V = -0.119 [V]
BS T240 1 DOF Z/W = -0.038 [V]
BS T240 2 DOF X/U = 0.235 [V]
BS T240 2 DOF Y/V = -0.134 [V]
BS T240 2 DOF Z/W = 0.132 [V]
BS T240 3 DOF Y/V = -0.158 [V]
BS T240 3 DOF Z/W = -0.169 [V]
HAM8 1 DOF X/U = -0.297 [V]
Assessment complete.

STS Centering Script Output:
Averaging Mass Centering channels for 10 [sec] ...
 
2026-04-06 09:04:04.266410
There are 2 STS proof masses out of range ( > 2.0 [V] )!
STS EY DOF X/U = -4.57 [V]
STS EY DOF Z/W = 2.369 [V]

   All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.496 [V]
STS A DOF Y/V = -0.768 [V]
STS A DOF Z/W = -0.628 [V]
STS B DOF X/U = 0.152 [V]
STS B DOF Y/V = 0.942 [V]
STS B DOF Z/W = -0.444 [V]
STS C DOF X/U = -0.995 [V]
STS C DOF Y/V = 0.908 [V]
STS C DOF Z/W = 0.636 [V]
STS EX DOF X/U = 0.606 [V]
STS EX DOF Y/V = -0.511 [V]
STS EX DOF Z/W = -0.372 [V]
STS EY DOF Y/V = 1.135 [V]
STS FC DOF X/U = 0.153 [V]
STS FC DOF Y/V = -1.192 [V]
STS FC DOF Z/W = 0.629 [V] 
Assessment complete.

H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 09:00, Monday 06 April 2026 (89788)
H1 ISI CPS Noise Spectra Check - Weekly (FAMIS #39345)

FAMIS Link:  39345 

Only CPS channels which look higher at high frequencies (see attached) would be the following:

  1. ITMx_ST1 V1
  2. ETMy_ST1 H2

In the bash window got ZERO notes.

Non-image files attached to this report
LHO General
corey.gray@LIGO.ORG - posted 07:42, Monday 06 April 2026 - last comment - 08:14, Monday 06 April 2026(89785)
Mon Day Ops Transition

TITLE: 04/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.14 μm/s 
QUICK SUMMARY:

Lots of activities on the docket for today.  HAM1 is set for door re-install, but could wait until after corner vent + HAM3 door removal.  Lots of staging for HAM3 opening and BBSS@BSC2.  Also a list of various CDS activities.  

Comments related to this report
corey.gray@LIGO.ORG - 08:14, Monday 06 April 2026 (89787)

Richard noticed we the PSL was at 10W, so it was taken down to 0W.  TJ noticed MC2 was saturating (nuc23); so IMC was taken to OFFLINE.

LHO VE
david.barker@LIGO.ORG - posted 10:20, Sunday 05 April 2026 (89783)
Sun CP1 Fill

Sun Apr 05 10:05:09 2026 INFO: Fill completed in 5min 6secs

 

Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 11:12, Saturday 04 April 2026 (89782)
Sat CP1 Fill

Sat Apr 04 10:06:55 2026 INFO: Fill completed in 6min 52secs

 

Images attached to this report
H1 SUS (DetChar, SUS)
georgia.mansell@LIGO.ORG - posted 17:01, Friday 03 April 2026 - last comment - 08:22, Tuesday 07 April 2026(89780)
Investigating violin mode frequency spacing and amplitude in DARM

Hi everyone it's been a while since I posted!

Julia Rice and I had a chat with Peter F today about motivating the electrostatic violin mode damper we've been building at Syracuse. We came away with a couple of questions to answer:

1. What's the actual displacement of the fibers when the violin modes are excited, and is our shadow sensor noise low enough to measure the modes.

2. What is the origin of the two violin modes per fiber? Is it fiber ellipticity built into the fibers themselves or asymmetry their attachment points AKA the ear/horn. If it's the former, we'd expect the main oscillation axis of the modes to be randomly oriented. If it's the latter we'd expect 4 modes per test mass to be dominant in DARM, and 4 modes to be much weaker, we'd also perhaps expect to see a regular spacing between pairs of modes.

I still have remote access (thanks Dave for helping me get my ports sorted with NoMachine), so I logged in to grab some plots of violin modes excited vs damped times.

I found an excited time and a quiet time by plotting the ISC_LOCK guardian state and the monitor for ITMY MODE5 which I know is a problematic mode (first plot). I used 5 November 2025 17:59:09 UTC, gps 1447264767 for the modes excited time since this was after many locking attempts with the mode5 monitor was ~20k counts. I used 17 November 2025 20:57:12 UTC, GPS 1447448250 as my quiet time AKA t=0 on the first plot.

Second plot is the money plot! When the modes are excited their amplitudes in DARM range between 1e-16m/rt(Hz) and 1e-14m/rt(Hz), we can roughly convert this to fiber displacement by multiplying by the fiber to test mass mass ratio. We did some back of the envelope calculations with Stefan and there's a factor of 2pi in there somewhere too.

I labelled the plot referencing this handy violin mode spreadsheet from Rahul et al, which set me thinking about the violin mode origin in question 2 above...

I can see the regular spacing with one large mode and one smaller mode in the ETMs for the excited spectrum. BUT it's not like there is 4 modes visible in DARM and 4 that are totally anti-aligned: the smaller modes are still very much visible in the DARM spectrum.

ETMX9 (516.781 Hz) has a small buddy ETMX7 (516.678)
ETMX1 (511.2993 Hz) had a small buddy ETMX6 (511.18)
ETMX3 (508.938 Hz) has a small buddy ETMX4 (508.844)
ETMX8 (507.36) has a small buddy ETMX2 (507.493)

For the first 3 pairs, the bigmode is higher in frequency, not sure if significant. Also, in the damped spectrum the larger modes can become sufficiently damped that the smaller mode is now louder in DARM, I wonder if that might be because we have spent many more hours tuning and damping the settings for the large modes?

There are also some modes that break the trend: ETMY1 and ETMY6 are very close together.

For the ITMs, things are less clear. ITMY1 and ITMY2 are similar height in DARM, same with ITMX8 and ITMX7, and ITMX3 and ITMX5. Things are confusing around the clusters of modes 504 Hz and 508 Hz.

I had previously always assumed that ITMY mode5 and mode6, the extremely close modes, are on the same fiber. But perhaps mode5 is on the same fiber as mode7, and mode6 is on the same fiber as mode8!

To better visualise the data, I made a table of the mode "buddies" and their frequency separations here, check it out if your interested. There is a goofy plot in there with no x-axis and mode spacing on the y-axis. The frequency spacing of pairs of modes is centered around 0.1Hz.

I do think there is scientific value to having a shadow sensor at the fiber: it's clear that the modes are not perfectly aligned or anti-aligned with the DARM axis, I was able to identify all 32 modes. In the egregious case of ITMY, at least 7 of the 8 modes are large in DARM. That being said, the regularity of the spacing means I am quite confident (for most modes!) which two modes are on the same fiber.

Please let me know if I've missed something or if you have any thoughts!

Images attached to this report
Comments related to this report
peter.fritschel@LIGO.ORG - 06:42, Monday 06 April 2026 (89784)

Please quote all numbers for fiber motion and put all plots in 'meters' (either rms or pk), not meters/sqrt(Hz). It is the former that has physical meaning, can be compared to calculation, and is not dependent on the resolution bandwidth one might choose for a spectrum.

georgia.mansell@LIGO.ORG - 14:27, Monday 06 April 2026 (89794)

Good point and important for when we are calibrating our sensitivity to fiber displacement. Here's the main plot converted to meters RMS!

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 08:22, Tuesday 07 April 2026 (89802)CSWG, SUS
@Georgia, welcome to the violin mode life cycle! 

I hope you're using Alan Cummings as a resource. He was super helpful in understanding the mode splitting back in 2022:

TL;DR -- the answer to your second question ("2. What is the origin of the two violin modes per fiber?") is known: dictated be asymmetries, offsets and angles in the fibre necks, ends and welds; not any ellipticity.

Full conversation:
 Kissel
[...] 
Can you model the driven transfer function coupling between PUM drive and the violin mode?
We've recently taken two data sets that either don't make sense, or are incoherent, see
   - Swept Sine LHO:63083
   - Broad Band LHO:63089
> and we're left wondering if it even makes sense to expect to see something on resonance. This would likely require not only your exquisite FEA that includes fiber profiling and pictures of the welds, but also understanding exactly where the PUM magnets are, and the bending bodes of the PUM. Let us know if you need any help in gathering enough information to support such detail, or if you think you've got enough already.


 Cumming
This may well be possible with the FEA, although it's not something I've personally ever done. However, it probably warrants a little caution as to any manage any expectation of what might be possible with FEA (as does all the high precision v-mode stuff) - the precise coupling of a v-mode will likely be very dependent on the direction of oscillation, and this will most likely be dictated be asymmetries, offsets and angles in the fibre necks, ends and welds [what it's not is: general fibre ellipticity - proven previously with FEA that this would have to be so large that we'd see it in profiler measurements]. All of that isn't perfectly characterised, and also can't easily/at all be modeled in FEA, which is where we start to become limited.

Also there is the fibre tensions - these are all assumed to be the same in the FEA, which in reality may not be the case. Indeed in LHO:57649 the comparison of ITMY's fibres measured fundamentals with FEA implies that there's a possibility fibre S1800746 may well be under more tension than the others as compared the projected FEA trends. That's not totally definitive as the reason, but it's certainly possible. I suspect again these are things that might start affecting the coupling at the levels of precision you are interested in.

Practical point - currently the FEA models that exist for the S18XXXX era fibred ITMY are single fibre stiffness models to compare base frequencies of the v-modes that come from the differing fibre geometries. We don't yet have a 4 fibre ITMY model with the individual fibres [at that time you guys were still trying to choose the tranche of good-guy 'a-list' fibres, so it was not known which individual suspects would actually be used in ITMY. Looking at the alog links, it's clear you did ultimately install the a-list fibres S1800721 ,S1800751, S1800649, S1800746.]

H1 SPI (SPI)
sina.koehlenbeck@LIGO.ORG - posted 13:47, Wednesday 01 April 2026 - last comment - 17:12, Friday 03 April 2026(89740)
LIGO-SPI Pathfinder ISIK/ISIJ Picomotor Test: All Motors Operational

Sina, Jim

We tested the functioning of the picomotors in the LIGO-SPI Pathfinder ISIK and ISIJ assemblies. All motors are working (see attached video).

Non-image files attached to this report
Comments related to this report
sina.koehlenbeck@LIGO.ORG - 17:12, Friday 03 April 2026 (89781)

The images show the test equipment used. 

Images attached to this comment
Displaying reports 921-940 of 88149.Go to page Start 43 44 45 46 47 48 49 50 51 End