Displaying reports 1-20 of 87370.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 16:58, Friday 17 April 2026
H1 General
oli.patane@LIGO.ORG - posted 16:58, Friday 17 April 2026 (89941)
Ops DAY Shift End

TITLE: 04/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: No further work was done regarding BSC2
LOG:

Start Time System Name Location Lazer_Haz Task Time End
14:51 FAC Nellie, Kim LVEA n Tech clean, Nellie out 15:51 15:55
15:51 FAC Nellie EY n Tech clean 16:35
16:37 PEM Robert EX n Grounding 00:25
17:13 PCAL Tony, Erik EX, EY n Trying to get PCAL laser back up 17:57
18:29 PCAL Tony PCAL Lab y(local) Fixing broken chassis 19:09
18:33 EPO Jeff, friend LVEA n Tour of LVEA 19:35
18:38 VAC Jordan LVEA n Turning HAM1 AUX carts off 18:42
20:07 EPO Jeff, friend LVEA n Tour 21:26
22:02 VAC Jordan, Mitchell LVEA n Decoupling AUX carts 22:25
22:40 VAC Jordan LVEA n Turning on RGA for CP1 22:54
LHO VE
david.barker@LIGO.ORG - posted 10:31, Friday 17 April 2026 (89938)
Fri CP1 Fill

Fri Apr 17 10:10:13 2026 INFO: Fill completed in 10min 9secs

 

Images attached to this report
H1 PSL
oli.patane@LIGO.ORG - posted 09:16, Friday 17 April 2026 (89936)
PSL Status Report Weekly FAMIS

Closes FAMIS#39760, last checked 89840
Laser Status:
    NPRO output power is 1.83W
    AMP1 output power is 70.39W
    AMP2 output power is 137.9W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 6 days, 23 hr 13 minutes
    Reflected power = 27.09W
    Transmitted power = 104.3W
    PowerSum = 131.4W

FSS:
    It has been locked for 6 days 23 hr and 13 min
    TPD[V] = 0.4872V

ISS:
    The diffracted power is around 3.6%
    Last saturation event was 1 days 19 hours and 33 minutes ago
Possible Issues:
    PMC reflected power is high

H1 CDS
david.barker@LIGO.ORG - posted 09:05, Friday 17 April 2026 - last comment - 10:08, Friday 17 April 2026(89935)
SUSEY timing/DAC error Thursday 17:32 PDT

h1susey reported a DAC error with both its LIGO-DACs at 17:32 Thursday 16apr2026 PDT. This was caused by a large timing glitch seen on h1iopsusey and h1susetmy at this time, cpu_max of >200uS were seen on both models. This was a recoverable error and DAC0 continues to drive.

The lights were not on at EY at this time, so it does not appear to be related to any in-rack work.

dmesg:

[Thu Apr 16 17:32:21 2026] h1iopsusey: ERROR - LIGO_28AO32(0) DAC error detected, 0x30070086, DAC error counter: 19, is_locked: 1
[Thu Apr 16 17:32:21 2026] h1iopsusey: ERROR - LIGO_28AO32(1) DAC error detected, 0x30070086, DAC error counter: 19, is_locked: 1
 

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 10:08, Friday 17 April 2026 (89937)

We chose to not restart the IOP. All the ADC/TIM/IPC latched errors cleared with DIAG_RESETs with no problems.

H1 General
oli.patane@LIGO.ORG - posted 07:37, Friday 17 April 2026 (89934)
Ops DAY Shift Start

TITLE: 04/17 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, 1mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s 
QUICK SUMMARY: BSC2 ISI work today

H1 IOO (IOO, OpsInfo)
jennifer.wright@LIGO.ORG - posted 17:21, Thursday 16 April 2026 - last comment - 17:06, Friday 17 April 2026(89924)
JAC TRANS A LF calibration

Jennie W, Sheila D, Jenne D

 

Summary: JAC TRANS A LF calibration gives correct ratio now but PD is too noisy to give us sensible values when the light pipe is closed.

On Tuesday I changed the scaling filter in JAC-TRANS_A_LF to give us an output calibrated in W out of HAM1. The previous calculation (alog #89805) gave us too large a value.

When we checked the power on the JAC-TRANS PD in chamber (alog #89251) we did not monitor the JAC input power between successive measurements and since we had purge air on I think the input power drifted.

To avoid confusion  I just took a time when the output power was measured in chamber and used the JAC TRANS LF OUTPUT power at that time to give the calibration into HAM2 W.

When we measured 96mW out of HAM1, the JAC-TRANS_A_LF filter bank was roughly calibrated into mW (using standard values for V/count, A/V, mW/A) but had not been calibrated using in-chamber measurements.

For 96mW we got 0.00120mW on JAC_TRANS_A_LF_OUTPUT on 2026/02/24 at 20:30:10 UTC, see image.

We want the output in W so the calibration factor is 80000/1000. This value is now in FM10 in the filter bank. Unfortunately the signal still is too nosiy to give a sensible looking value and so changes from -20 to 20 W.

Jenne and I put a 0.01Hz pole to low pass the noise in the FM7 filter, and also tuned the offset on the filter bank.

This channel still seems too noisy though (image) and changes between -0.5 W and 0.5.

So maybe we need a filter that goes down to lower frequency, or its just too noisy a PD to use as a JAC input power monitor.

I'm going to revisit this after the BSC2 work when we next have an opportunity to open the light pipe.

 

 

 

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 17:25, Thursday 16 April 2026 (89933)

I accepted the sdf diffs for JAC-TRANS_A_LF - filters, offset and tramp.

I also turned off the FM1 and FM2 filters  in JAC-L_SERVO as Jenne noticed the integrator hwas causing a large value at the output of the servo. Checking the 'DOWN' state in the JAC guardian these should not be on so I accepted them as off in sdf.

Images attached to this comment
jennifer.wright@LIGO.ORG - 17:06, Friday 17 April 2026 (89942)

Today i noticed the output of the JAC SERVO wa son so i turned it off and sdfed it. This should also be the case when in DOWN.

Images attached to this comment
H1 PEM (DetChar, PEM)
samantha.callos@LIGO.ORG - posted 17:10, Thursday 16 April 2026 (89929)
PEM November 2025 Injection Coupling Analysis Complete

Samantha Callos, Genevieve Connolly, Robert Schofield, Ryan Short, Carlos Campos

The detchar presentation summarizing the injection analysis can be found on the DCC at: https://dcc.ligo.org/LIGO-G2600768

A PDF of this report has also been attached to this alog along with a spreadsheet of the injections.

Non-image files attached to this report
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 16:38, Thursday 16 April 2026 - last comment - 17:17, Thursday 16 April 2026(89922)
BSC2 Dome is Removed

(Travis, Jordan, Randy, Betsy, Corey, Mitchell, Kim, Gerardo)

During the end of last week, Thursday and Friday, and during this week we had a chance to prepare the dome for its removal.  The annulus system was vented with nitrogen. Most bolts were removed last week, Jordan and Corey did a good job with that task.  Wiring for comms and electrical were removed early this week, as were the wires for the gauge pair and the annulus ion pump.  Electrical conduits were detached from the dome and pushed down and out of the way.
Today we were given the go ahead to remove the dome, dust monitor was checked, all zeroes, then the tent was removed, cables and counterweights were attached to the dome, spreader bar (with load cell) was attached to dome lifting lugs.  We already had a good gap at some points of the dome, but the O-rings were still very sticky, dome would not let go.  After prying from multiple points we were able to separate the dome from the chamber, the O-rings were checked and found to be stuck in a few spots, lifted the dome some more until we only had a little bit of play at the four remaining bolts.  We managed to unstick the O-rings with the O-ring tool without problems, once the O-ring was cleared, we removed the bolts and picked up the dome slowly, to make sure the O-ring was indeed free, since no issues were noted, Randy picked up the dome to almost clearing the top of the ISI, the O-ring protectors went on, then we installed a tall C3 cover on the ISI, it took 3 of us to accomplish that. We finished with the chamber cover fastened at the chamber flange with no issues, pretty soon the C3 cover billowed up due to the purge air.  Then our attention went to cover the dome opening, we then handed the dome over to Randy and Mitchell.  The tent went back up without problems and Randy parked the dome at the north bay floor, over some dunnage.

Thank you all for your help.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 17:16, Thursday 16 April 2026 (89930)EPO

Photo & Video Shoot for the Dome Removal

Had a few cameras set-up (in addition to the one Fil installed earlier in the week, #89887).  

Fixed cameras:

  • Richard's iPad (closest to eMod) filming time lapse
  • My iPad near Hi-Bay roll-up door (also filming time lapse)
  • Canon60D on tripod also at Hi-Bay roll-up door, this was was only recording video, but it stopped/died before the actual Dome move started.
  • My old GoProMAX (360 camera), clamped on rail of bridge over the X-arm, filming time lapse.  

Mobile camera: 

  • My iphone, for roamong photos & video (ighlights attached to this entry).

Here is a link to all the video & photo files from the bulleted cameras listed above:  BSC1 Dome Removal Folder

  • To view file list with thumbnails, select Grid List button on the upper right.
  • Folder has 4-subfolders with all the files

Here is a funky look of the Dome Removal via the a full 360 file (unedited):  Trippy 360 clip

And here is a rough widescreen edit of the full-360 file above (to big to uploade to alog):   Widescreen rough cut of the above 360-file

Images attached to this comment
albert.lazzarini@LIGO.ORG - 17:17, Thursday 16 April 2026 (89932)
Great job! Kudos to the team.
LHO General
ryan.short@LIGO.ORG - posted 16:35, Thursday 16 April 2026 (89927)
Ops Day Shift Summary

TITLE: 04/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: The BSC2 dome is off as of this morning! Work is now ongoing on the ISI to prep for cartridge removal, which is currently scheduled for late next week. The TCS X chiller tripped off with a "high pressure warning" at 22:56; Camilla is investigating.
LOG:

Start Time System Name Location Lazer_Haz Task Time End
14:39 FAC Kim, Nellie LVEA N Technical cleaning 15:36
15:18 FAC Randy LVEA N Checking cleanroom in East bay 16:31
15:38 CDS Tony LVEA N Laptop inventory 17:55
16:03 FAC Kim, Nellie LVEA N Technical cleaning 16:52
16:15 PEM Robert EX N Grounding 19:09
16:28 CDS Fil LVEA N Repositioning BSC2 camera 17:18
16:34 VAC Jordan, Gerardo, Travis, Randy LVEA N BSC2 dome removal 19:08
16:45 TCS Camilla LVEA/OptLab N Property inventory 17:18
16:45 SEI Jim, Mitchell LVEA N Prep for BSC2 dome removal 16:47
16:52 SEI Jim, Mitchell EX N Looking for HEPI parts 17:50
16:54 AOS Betsy LVEA N Parts staging for dome removal 18:15
17:04 EPO Corey LVEA N Dome removal documentation 19:08
17:23 FAC Kim LVEA N Stocking wipes 17:59
17:29 AOS Mike, Jenne, Amber +1 LVEA N Tour 17:42
17:56 CDS Tony EX, EY N Laptop inventory 18:39
18:18 FAC Mitchell LVEA LVEA BSC2 dome removal 19:01
18:18 SAF Jenne LVEA N Hardhat sign checks 18:29
18:27 EE Marc MEZ N Move over a power supply 18:52
18:35 FAC Tyler LVEA N BSC2 dome removal 18:40
19:51 FAC Randy LVEA N Putting away parts 20:08
20:08 SEI Jim, Mitchell LVEA N BSC2 HEPI 23:32
20:21 SUS Fil MER N Rack wiring 22:18
20:28 ISC Elenna, Oli OptLab N PZT cabling checks 21:37
20:30 CDS Marc EX, EY N Staging power supplies 21:37
21:01 FAC Randy, Tyler LVEA N Cleanroom work near HAM6 21:15
21:29 VAC Jordan LVEA N Prep for CP1 regen 23:06
22:01 VAC Travis LVEA N Check HAM1/2 AIP 22:11
22:11 VAC Travis MY N Collecting parts 23:00
22:19 PEM Robert EX N Grounding Ongoing
22:19 TCS Camilla, Madi EX YES ALS/HWS table work 23:06
22:50 TCS Ibrahim MER N TCS chillers check 23:06
23:32 TCS Camilla LVEA/MER N Checking chiller lines Ongoing
H1 TCS
ibrahim.abouelfettouh@LIGO.ORG - posted 16:04, Thursday 16 April 2026 - last comment - 17:25, Thursday 16 April 2026(89926)
TCS Chiller Water Level Top-Off - BiWeekly FAMIS 28639

Closes FAMIS 28639

Last checked in alog 89720

TCSX read 30.8 - nothing added

TCSY read 10.6 - nothing added\

No water in small cup under the slow leak

TCSX is reading HIGH PRESSURE FAULT. See attached picture. 

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 17:25, Thursday 16 April 2026 (89931)

Betsy and I locked and tagged out the CO2X chiller, it will remain off until all needed repairs and safety documents have been completed next week. 

At 15:44UTC the chiller tripped off with a HIGH PRESSURE fault, as found by Ibrahim.  The CR verbal machine also alerted Ryan with a "low flow" warning.

I went out to the LVEA inspecting the pipes and found that the outgoing CO2X line was disconnected at the quick-connect, image. There was no water on the floor, so the quick-connect did it's job. Maybe this was already loose and we need to add the the pipe inspection FAMIS to inspect these connections, but. there was also lot of work in that area today. I inspected and reconnected the quick-connect, it did not seem damaged.

At out weak point in the chiller lines at the flexible baffle in the pipe bridge, the plastic sheeting that had been attached to catch any spilled water had a small amount of water in it photo, but none leaking out. Expect this water would have been pushed out a small break in the rubber while the chiller was trying to push water around the incomplete lines before the high pressure sensor in the chiller tripped it off. We will inspect and probably repair this part next week. In the meantime with water dripping out of the pipe bridge connection, we are fine to leave the chiller locked out with water in the lines. 

Images attached to this comment
H1 AOS (SEI, SUS, SYS)
jason.oberling@LIGO.ORG - posted 15:45, Thursday 16 April 2026 - last comment - 15:59, Thursday 16 April 2026(89913)
Survey of WBSC2 ISI, BS SUS, and ITM Elliptical Baffles (WP 13171)

J. Oberling, R. Crouch, J. Warner, B. Weaver, I. Abouelfettouh

This week we surveyed the position of the components that reside in WBSC2: The BS SUS cage (BSS), the ISI optics table (ISI Stage 2), and the 2 ITM Elliptical Baffles.

BS and the SUS Cage

The first picture shows our FARO survey of points on the BS SUS cage, chiefly along the bottom of the main support structure.  These were surveyed by holding the FARO SMR against the hole being measured; the PolyWorks software handles the compensation from the center of the SMR to the point being measured.  As can be seen, each point is very close in both X and Y axis position, being less than 0.1mm from its nominal location.  The Z axis deviations are larger, but the largest of them is just over 0.25 mm, so every point is well within the positioning specifications used during installation and alignment in 2013.

Line 1 in the picture was created from the first and last survey points and represents the pointing of the BS SUS cage; all angles are reported in degrees.  Some things to note here: I'm using the Acute Angle datum in PolyWorks, which is the angle measured from the closest axis.  For the HR surface normal of the BS, the X Acute Angle is measured from the -X axis, the Y Acute Angle is measured from the +Y axis, and the Z Acute Angle is measured from the +Z axis.  Since Line 1 is roughly perpendicular to the surface normal of the BS HR face, the axes the angles measure from are changed: The X Acute angle is now measured from the +X axis, the Y Acute Angle is still from the +Y axis, and the Z Acute Angle is now from the -Z axis.  In addition, since Line 1 is nominally perpendicular to the BS HR surface normal I would expect the X and Y Acute angles to be swapped (BS X Acute = Line 1 Y Acute; BS Y Acute = Line 1 X Acute), but they aren't exactly.  This appears to be a small error in the CAD model, if we make the assumption that the BS HR surface and the HR side of the BS SUS cage are nominally pointing in the same direction.  This does, however, change the deviations for the X and Y Acute angles for Line 1.  The table below shows what the data for Line 1 should be:

  Nominal Measured Deviation
X Acute Angle 44.9699 44.9073 -0.0626
Y Acute Angle 45.0301 45.0927 0.0626
Z Acute Angle 90.0000 89.9661 -0.0339

This means the BS SUS cage is yawed 0.0626°, or ~1.09 mrad, in the clockwise (CW) direction when looking from the top down (since Line 1 is closer to the +X axis than it should be).  The Z Acute Angle represents a slight counterclockwise (CCW) roll of the SUS cage, when looking directly at the HR surface of the BS.

To attempt to better locate the BS in the IFO coordinate system, several measurements were taken with a ruler from points on the "Figure 8" section of the BS SUS cage to the BS optic itself.  All measurments except one were done using a scale with 0.5 mm tic marks (so accurate to +/- 0.25 mm).  The 10:00 "Figure 8 face to BS HR face" measurement had to be done using the side of the scale in inches, with 1/32" tic marks (so accurate to +/- 1/64") and then converted to mm (so accurate to +/- 0.4 mm).  The measurements positions are listed like the BS HR surface is a clock, and assumes you are looking directly at the HR surface.  The below table gives those results:

  Outside Edge of Figure 8 to BS optic edge (mm) Front face of Figure 8 to BS HR face (mm)
3:00 (-X/-Y) 6:00 (-Z) 9:00 (+X/+Y) 2:00 6:00 10:00
Measurement 49.0 48.75 48.5 24.75 27.0 26.2
CAD Nominal 49.0 49.0 49.0 26.2 26.2 26.2
Deviation 0.0 -0.25 -0.5 -1.45 +0.8 0.0

The BS sits decently centered in the Figure 8 portion of the SUS cage, a little bit low and to the +X/+Y side.  I would say not as much horizontally as it looks from the table, given the inherent error with reading the scale (the BS is not wider than its 370.0 mm specification, it's actually 0.15 mm narrower at 369.85 mm).  The pointing implied by this measurement, however, is more than a little alarming.  The 2:00 and 10:00 measurements show a significant yaw of the BS optic w.r.t. the SUS cage, and in the same direction as the yaw of the SUS cage as measured by the FARO.  There is ~320.0 mm between the 2:00 and 10:00 positions on the BS, so that 1.45 mm difference in depth is a 4.53 mrad CW yaw.  When added to the CW yaw of the SUS cage, this measurement shows that the BS optic is yawed 5.62 mrad CW from its nominal yaw.  Even assuming the errors fall in our favor (so the 2:00 at 25.0 mm and the 10:00 at 25.8 mm), that's still a 3.59 mrad CW yaw (2.5 mrad BS and 1.09 mrad SUS cage).  In addition, the 6:00 measurement implies a significant downward pitch of potentially several mrad, although with no way to measure the top of the optic we can't actually measure it.  I have to be honest, I'm having a very hard time believing this measurement; we will revisit this once the BS cartridge has been moved to the test stand, where we have a better field of view for the FARO, more room to work and much better lighting around the BS, and can take direct measurements of the BS position and pointing using a total station and laser autocollimator (although there is no guarantee that the optic will be pointing in exactly the same direction after being craned across the LVEA).  More to come on this.

ISI Optics Table

The second attachment shows the ISI positions as measured by the FARO.  I've corrected the Z axis positions for the length of the rod we use to hang the SMR from the ISI so they give a better idea of the Z axis position.  Not much can be said here, as LLO discovered that while these rods are good for measuring the Z axis position, they are not at all good at measuring X and Y.  This makes sense as they were designed to be accurate in length and only length, so there's no guarantee that X and Y are repeatable.  We plan on measuring the X and Y errors of this particular set of rods in the coming days (align to a table with a known hole pattern, attach the rod and measure with the FARO, repeat multiple times to see how the X and Y positions change).  For now, we can say that the ISI is lower on the -X side vs the +X side, and lower on the +Y side vs the -Y side.  I'm not alarmed by the deviations in Z axis position, as this ISI was supposed to be lower by ~2.5 mm (to place the BS in proper Z axis position, since it's lower in the IFO coordinate system but the SUS is the same length as the QUADs), but this was never captured in the CAD files.

ITM Elliptical Baffles

The final four attachments show our survey of both ITM elliptical baffles.  Our view of the baffles and available fiducials to take measurements from were both limited, but we can say a few things.

ITMx Elliptical Baffle

We were able to get two points along the +Y bottom edge of the baffle, a single point along the +Y top edge, and single point near the center of the -X bottom edge of the baffle.  From this I made a couple of planes that represent the +Y and bottom sides of the baffle and are shown in the third and fourth attachments; I, J, and K are the direction cosines of the surface normal of the plane, while the listed angles are the angle from the surface normal to the +X, +Y, and +Z axes. Interestingly, the point on the top edge looks very well aligned, within 1.0 mm all around, while the points along the bottom of the baffle are all low by several mm.  In addition, there appears to be a significant upward pitch to the baffle.  Jim did note that when attaching the transport bracket he had to push the baffle in the +X direction to clear ~0.5 mm at the point where the bracket attaches to the suspended portion of the baffle.  This point is roughly 476 mm away from the baffle's suspension blade, so this is an ~1.05 mrad angle.  Applying this same angle along the bottom of the baffle box gives an ~ -0.33 mm Z axis move of that bottom -X edge of the baffle, so this does not account for the measured deviation.  In addition to the pitch, the bottom plane also shows a large roll (CCW when looking at the ITMx in WBSC3), while the side plane shows a large yaw (CCW when looking from the top down).  We know these baffle panels aren't exactly straight, so it's hard to say if this significant pointing is also present on the elliptical hole of the baffle (we couldn't see it, so we couldn't measure it directly).

ITMy Elliptical Baffle

Similar to the ITMx baffle, we were only able to get a handful of points along the -X side and the bottom of the baffle.  I made planes from these points representing the -X side and the bottom of the baffle (fifth and sixth attachments).  As seen with the ITMx baffle, the points along the top of the baffle all look good while the points on the bottom are too low by several mm.  There is a significant upward pitch to this baffle as well, as well as a large roll (CCW when looking at ITMy in WBSC1) and yaw (CCW when looking from the top down), although none are as large those as seen on the ITMx elliptical baffle.  Again, we could not see the elliptical hole in the baffle to measure it, so we can't say if this pointing is an artifact of the panels or also present on the actual baffle portion of the baffle.

This completes our in-chamber measurements of the WBSC2 cartridge assembly, and closes LHO WP 13171.

I also want to note, Ryan and I also preformed some in-chamber FARO measurements in WHAM3 (ISI, MC2 SUS cage, PR2 SUS cage, MC2 and PR2 baffles) on April 10th; I will post those as soon as I get a chance to process the data in PolyWorks.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 15:59, Thursday 16 April 2026 (89925)EPO

Some action photos while Jason & RyanC were chamberside at HAM3.

Images attached to this comment
H1 CDS
david.barker@LIGO.ORG - posted 15:29, Thursday 16 April 2026 - last comment - 13:25, Friday 17 April 2026(89923)
ISI Watchdog Trip Plotting Working Again

FRS37572 ISI HAM and BSC WD Plots Not Working

Ryan C, Erik, Dave:

The MEDM buttons to plot the latest ISI WD trips (see attached) have not been working for some time.

We found the issue was due to the wd_plot python code running in the conda environment had pydv issues, but if ran in native debian it worked.

Fixing the conda pydv issue would take significant resouces, so we chose to change the MEDM launcher to explicitly run local /usr/bin/python3.

The common MEDM file ISI_CUST_CHAMBER_WATCHDOG.adl in the isi/comon/medm/[hamisi, bscisi]/ directories were changed accordingly.

I tested with HAM2 and BSC3.

Images attached to this report
Comments related to this report
brian.lantz@LIGO.ORG - 13:25, Friday 17 April 2026 (89939)

Thanks Dave, those plots are useful diagnostic tools.
I dropped a note in the LLO log so we can be sure this fix gets used at both sites 

-Brian

H1 AOS (DetChar)
sheila.dwyer@LIGO.ORG - posted 15:22, Friday 17 November 2023 - last comment - 16:15, Friday 17 April 2026(74256)
SQZ angle sweeping

Naoki, Camilla, Sheila

We had another look at some signals that we could use to track or servo the SQZ angle.  

We turned the ADF back on, making a line at 1.3kHz in DARM, and tuned the demod phase for the ADF so that the SQZ angle readout was 0 for the angle we've been using for observing in this lock.  Camilla added a bandstop at 1.3kHz in the SQZ BLRMS4, sum and null channels and checked that the ADF isn't dominating those.  We did a sweep of the CLF6 demod phase like this, with the dither amplitude reduced comapred to Wed (0.01 instead of 0.03 CLK gain).  

In the first attachment we are using BLRMS 4 to demodulate for the noise lock signal, the second cursor shows that the zero crossing of the ADF SQZ angle and the noise lock both correspond roughly with the minimum of noise in the BLRM4 (1kHz BLRMs).  This isn't the same phase as the one that minimizes the brown trace, a blrms centered at 350 Hz. This means we have a frequency dependence of the SQZ angle, so we should probably look into things like the SRCL offset that might be causing this. 

Naoki then turned the ADF phase with the SQZ angle set to minize BLRMS3, as shown in the second screenshot from Camilla (at the begining here you can see that Naoki set the ADF phase so SQZ ANG was zero for CLF demod phase of 145).  We repeated the sweep and see that we have lower SNR for the noise lock using this lower frequency BLRMS, and that the ADF as it is now wouldn't make a good error signal for this sqz angle because it doesn't really go negative. 

Detchar:  We are planning to leave the ADF on over the weekend, which will create a line at 1.3kHz.  We are hoping to use this to track changes in the squeezing angle over time.  

 

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 12:17, Monday 20 November 2023 (74316)

The ADF calculated SQZ angle (H1:SQZ-ADF_OMC_TRANS_SQZ_ANG) seems to follow our SQZ BLRMs over the weekend, plot attached. Unsure why the SQZ is different lock to lock, i.e. sometimes changes over first 6 hours (1 day ago) and is sometimes is stable (-12 hours ago).

Images attached to this comment
sheila.dwyer@LIGO.ORG - 16:15, Friday 17 April 2026 (89940)

The Wensday work that is referenced above is described with helpful detail in 74223

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