Displaying reports 1881-1900 of 85743.Go to page Start 91 92 93 94 95 96 97 98 99 End
Reports until 16:11, Tuesday 12 August 2025
H1 SUS
oli.patane@LIGO.ORG - posted 16:11, Tuesday 12 August 2025 - last comment - 13:30, Monday 18 August 2025(86319)
SR3 Y damping estimator test

Ivey, Edgard, and Brian have created new estimator fits (86233) and blend filters (86265) for the SR3 Y estimator, and we have new rate channels (86080), so we were excited to be able to take new estimator measurements (last time 85615).

Unfortunately, there were issues with installing the new filters, so I had to make do with the old filters: for the for the estimator filters, I used the fits from fits_H1SR3_2025-06-30.mat, and the blend filters are from Estimator_blend_doublenotch_SR3yaw.m, aka the DBL_notch filter and not the new skinny notch. These are the same filters used in the testing from 85615.

So the only difference between the last estimator test and this one is that the last test had the generic satamp compensation filters (85471), and this measurement has the more precise 'best possible' compensation filters (85746). Good for us to see how much of a difference the generic vs best possible compensation filters make.

Unfortunately, due to the filter installation issues as well as still trying to re set up the estimator channels following the channel name changes, I also didn't have much time to run the tests, resulting in the actual test with the estimator being only 5 minutes. Hopefully this is okay enough for at least a preliminary view of how it's working and then next week we can run a full test with the more recent filters. Like last time, the transition between the OSEM damping and the estimator damping was very smooth and the noise out of the estimator was visibly smaller than with the regular damping (ndscope1).

Measurement times
SR3 Y damp -0.1
2025-08-12 18:28:00 - 18:44:00 UTC

SR3 Y damp -0.1, OSEM damp -0.4
2025-08-12 18:46:46 - 19:03:41 UTC

SR3 Y damp -0.1, Estimator damp -0.4
2025-08-12 19:09:00 - 19:16:51 UTC

Images attached to this report
Comments related to this report
ivey.zhong@LIGO.ORG - 14:20, Friday 15 August 2025 (86379)SEI, SUS

Attached below are plots of the OSEM yaw signal, the M3 yaw optical lever witness sensor signal, and the drive request from light damping, full damping (current setting), and estimator damping modes from Oli's recent estimator test.

The blue trace is the light damping mode, the red trace is the full damping mode, and the yellow trace is the estimator damping.

The first plot is of the OSEM signal. The spectrum is dominated by OSEM noise. The blue, light damping trace shows where the suspension resonances are (around 1, 2, and 3 Hz). Under estimator damping, the resonances don't show up as expected.

This second plot is of the OPLEV signal. It is much more obvious from this plot that the estimator is damping at the resonances as expected. Between the first and second, as well as the second and third peaks, the yellow trace of the estimator damping mode is below the red trace of the full damping mode. This is good because it is expected that the estimator damping is better than the current full damping mode between the peaks. There is some estimator noise between 3 and 4 Hz from the estimator. The light damping trace also sees a noticeable amount of excess noise between 10 to 15 Hz. We suspect this is due to ground motion from maintenance: third, fourth, and fifth plots show comparisons between ground motion in July (when the light damping trace was 'normal') and August. There is excess noise in X, Y, and Z in August when compared to July.

The sixth plot is of the drive requests. This data was pulled from a newly installed 512 samples/sec channel, while the previous analysis for a test in July (see: LHO: 85745) was done using a channel that was sampling at 16 samples/sec. The low frequency full damping drive request differs significantly between July and August, likely because aliasing effects caused the July data to be unreliable. Otherwise, the estimator is requesting less drive above 5 Hz as expected. We note that the estimator rolls off sharply above 10 Hz.

The last plot is of the theoretical drive requests overlaid onto the empirical drive requests. We see that the major features of the estimator drive request are accounted for, as expected.

Oli intends to install the filter and the new, clean fits (see LHO: 86366) next Tuesday to test the yaw estimator once more. Hopefully the installation is smooth!

Non-image files attached to this comment
oli.patane@LIGO.ORG - 13:30, Monday 18 August 2025 (86425)

I would like to clarify from my initial alog that when I said that "the only difference between the last estimator test and this one is that the last test had the generic satamp compensation filters", that was a lie!! The measurements taken for calibrating and figuring out the correct response drives were taken before the satellite amplifiers were swapped for SR3, so even just the OSEMINF calibration was not done with the new satellite amplifiers in mind, so the calibration we had in there at the time was not very accurate to what we had going on, so we can't really compare this measurement to the last one.

H1 TCS
camilla.compton@LIGO.ORG - posted 16:00, Tuesday 12 August 2025 (86328)
TCS CO2Y Chassis Tripped off during Maintenance

Oli told me that the TCS CO2Y Chassis Tripped off during Maintenance this morning. This is not surprising as there was alot of craning work going on near that rack and the CO2 chassis are known to be fussy, see FRS 6639.

When I went to untrip it both indicator lights were red on it but after key-ing off/on, it turned on with no issues. 

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 14:15, Tuesday 12 August 2025 - last comment - 15:54, Tuesday 12 August 2025(86324)
Lockloss

Lockloss at 2025-08-12 21:12UTC after 25 minutes locked

Comments related to this report
camilla.compton@LIGO.ORG - 15:24, Tuesday 12 August 2025 (86325)

Oli, Elenna, Keita, Sheila, Jennie, Camilla

Oli noticed that ICS_LCOK had a check that the fast shutter didn't fire. Elenna and Oli then confirmed this.

We found that the fast shutter did not fire because the threshold of light at the AS port was not high enough to fire it. There was no danger here and  it should not have fired. This is a rare occurrence where the light goes towards the input rather than output and is caught by baffles.

See plots of today's lockloss with no spike of light and no fast shutter closing via HAM6 GS13 vs a normal (earthquake) LL where the light spikes (especially as seen on Keita's 81080 VP power monitor) and the fast shutter closes.

It is unusual that we have had this rare type of lockloss twice in a couple of months (27th June: 85383). So this can be monitored, I added this plot to the "lockloss select" command by putting it into /sys/h1/templates/locklossplots

Keita requested we checked the power on ASC-AS_C is at it's normal level with a 2W DRMI lock. It is within the normal range of the last three locks, see attached.

Images attached to this comment
oli.patane@LIGO.ORG - 15:54, Tuesday 12 August 2025 (86326)

I checked the vacuum channels and there was no excursion around the lockloss time so we didn't burn anything

Images attached to this comment
oli.patane@LIGO.ORG - 15:54, Tuesday 12 August 2025 (86327)

Back to Observing 22:46 UTC

H1 SQZ
camilla.compton@LIGO.ORG - posted 14:05, Tuesday 12 August 2025 (86323)
SQZ Pump Path Alignment Adjusted

Sheila, Jennie, Matt, Camilla. WP#12750

Followed what we did in 82881, but did not need to adjust alignment through the EOM. 

Starting with:

Then with 0V on ISS AOM controlmon, increased to 73mW (85% throughput). Then put 5V on controlmon and started to maximize the 1st order beam. We decided to not completely maximize 1st order as this reduces overall throughput and our current aim is to increase total green throughout, not ISS AOM range.

Ended with:

Sheila then adjusted the alignment into the fiber and maximized H1:SQZ-OPO_REFL_DC_POWER from 1.55 to 2.8. 

This allowed us to have an OPO setpoint of 80uW with 20mW going into the fiber, wirth 5 on the controlmon and a spare 20mW that we could give to the fiber.  Note that after ~1hour when we got to NLN, the controlmon had decreased from 5 to 2.5. So the power to the AOM may need to be increased next time we loose lock. Maybe with SQZT0 temperature changes now doors are on and fans are off. 

There was a high pitched noise in SQZT7, close to the -Y side of the table, we couldn’t figure out what it was and maybe will have someone from EE help us with it another week. 

I ran the SCAN_OPOTEMP guardian state (twice as it was far off) once we wer close to NLN.

H1 CDS
david.barker@LIGO.ORG - posted 13:09, Tuesday 12 August 2025 - last comment - 07:38, Wednesday 13 August 2025(86322)
CDS Maintenance Summary: Tuesday 12th August 2025

WP12746 h1omc0 Low Noise ADC Autocal Test

EJ, Jonathan, Dave:

For a first test we restarted h1iopomc0 three times to run an autocal on the low-noise ADC -- each time the autocal Failed. Next test will be to power cycle existing card leading to possible replacement.

WP12755 TW1 Raw Minute Trend Offload

Dave:

h1daqtw1 was configured to write it raw minutes into a new local directory to isolate the last 6 months of data from the running system. The NDS service on h1daqnds1 was restarted to serve these data from this location while the file transfer progresses.

Restarts

Tue12Aug2025
LOC TIME HOSTNAME     MODEL/REBOOT
09:06:26 h1omc0       h1iopomc0   <<< three ADC AUTOCAL tests
09:08:12 h1omc0       h1iopomc0   
09:08:58 h1omc0       h1iopomc0   
09:09:12 h1omc0       h1omc       <<< start user models
09:09:26 h1omc0       h1omcpi     
11:51:19 h1daqnds1    [DAQ] <<< reconfigure for TW1 offload
 

Comments related to this report
david.barker@LIGO.ORG - 07:38, Wednesday 13 August 2025 (86333)

TW1 offload status as of 07:30 Wed: 70% complete. ETA 15:15 this afternoon.

H1 General
camilla.compton@LIGO.ORG - posted 13:07, Tuesday 12 August 2025 (86321)
LVEA Swept following T1500386

Unplugged an unused extension cord by the PSL racks. 

High bay and LVEA and entrance lights turned off, paging system off. Oli checked WAP is off.

Everything else looked good.

H1 ISC
elenna.capote@LIGO.ORG - posted 13:06, Tuesday 12 August 2025 - last comment - 16:36, Friday 15 August 2025(86320)
Beamsplitter ADS convergence in initial alignment taking too long

Today Oli and I saw that the ADS convergence checker for the beamsplitter was taking forever to return True during initial alignment, despite the fact that the signals appeared well-converged. The convergence threshold is set on line 1158 of ALIGN_IFO.py, and it is 1.5 for both pitch and yaw. Watching the log, the yaw output seemed to quickly be below this value, while the pitch output hovered between about 1.8 to 6. I tried raising the value to 5, but pitch still stayed mostly above that value. I finally changed it to 10, and the state completed. Overall, we were waiting for convergence for over 16 minutes. It seems like the convergence values for pitch and yaw should be different. It took about two minutes for the pitch and yaw ADS outputs to reach their steady value. On ndscope minute trend, the yaw average value appears to be around zero, while for pitch the average value is around -4. The convergence checker averages over 20 seconds.

The value is still 10, but that might be too high.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 16:36, Friday 15 August 2025 (86383)

As TJ, Elenna, and Sheila had chatted about, I think this is due to the 'slow let-go' integrator being turned off on the BS pit M1 stage. 

I suggest that on Monday (or maybe Tuesday?) we modify the gen_PREP_FOR_MICH state of ALIGN_IFO to engage FM1 of H1:SUS-BS_M1_LOCK_P so that we have the integrator engaged for all of the MICH alignment use cases (MICH bright which we actually use for initial alignment, MICH dark which we used to use for init alignment, and MICH with ALS, which we use for aligning MICH when the green arms are locked). 

It probably doesn't matter if the integrator in FM1 is left on or not, since these states are only used at low power, and the DOWN state of ISC_DRMI gets it turned off. 

I'll coordinate with other commissioners to make that change early next week.

H1 SUS
filiberto.clara@LIGO.ORG - posted 12:51, Tuesday 12 August 2025 (86318)
Field Cabling for JAC Tip/Tilts

WP 12749
Drawing D0902810-v11

Installation of the field cabling for the JAC tip/tilts completed. Cables pulled from the CER SUS-C3 rack to the SUS-R1 field rack. The DB25 cables going from the Sat Amp chassis were pulled to to the HAM1 D4 and D6 flanges.

F. Clara, M. Pirello, D. Sigg

H1 CDS (SUS)
filiberto.clara@LIGO.ORG - posted 12:48, Tuesday 12 August 2025 (86317)
Field Rack SUS-R7

WP 12756
Rack and Cable Tray Layout D1002704-v8

A new electrical rack was positioned next to the SUS-R4 rack. The new rack will be designated as SUS-R7. Installation of cable tray, DC power strips, power junction box will be installed in the upcoming weeks.

Randy, F. Clara, J. Figueroa, and M. Pirello

H1 PSL
jason.oberling@LIGO.ORG - posted 10:49, Tuesday 12 August 2025 (86315)
PSL FSS RefCav Tune-up (WP 12751)

The FSS RefCav TPD has been on a downward trend again, so I tuned up the alignment on the PSL table this morning.  All work was done with the ISS ON and diffracting ~3.8% unless otherwise noted.  As usual, I began with a power budget of the FSS path:

The AOM's single pass diffraction efficiency was a little low, so I touched up the AOM alignment to improve it.  I also tweaked the alignment of mirror M21 (that reflects the RefCav beam back through the AOM for the double pass) to improve the double pass diffraction efficiency (since the AOM moved).  Finally I slightly tweaked the EOM alignment to center the beam on the input and output apertures and measured the power transmitted through the EOM:

I then tweaked the alignment into the RefCav using the alignment iris and manually tweaking the picomotor-equipped mirror mounts.  The RefCav locked on the first attempt, with an initial TPD of ~0.735 V.  I then used the picomotors to fine tune the alignment and managed to get a TPD of ~0.845 V.  To end, I unlocked the RefCav and tweaked the beam alignment onto the RefCav's RFPD, then measured the RefCav visibility using the RFPD voltage:

I then turned off the ISS (we turn it off while the enclosure returns to thermal equilibrium, because during this process the PMC transmission can change; we don't want the ISS to actuate on the laser power until things stabilize), left the enclosure, and returned it to Science Mode operation.  I let the enclosure return to thermal equilibrium for about an hour and then checked on things.  When I turned the ISS back ON I had to increase the ISS RefSignal from -1.99 V to -1.98 V to hold our diffracted power at ~4%.  I then did on final tweak of the RefCav alignment using our picomotor mirrors; I was able to get the RefCav TPD up to ~0.854 V.  At this point the RefCav tune up is complete and the PSL is ready for post-maintenance IFO recovery.  This closes LHO WP 12751.

LHO VE
david.barker@LIGO.ORG - posted 10:37, Tuesday 12 August 2025 (86316)
Tue CP1 Fill

Tue Aug 12 10:07:51 2025 INFO: Fill completed in 7min 48secs

 

Images attached to this report
H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 08:03, Tuesday 12 August 2025 - last comment - 09:49, Tuesday 12 August 2025(86313)
Lockloss

Lockloss at 2025-08-12 14:57UTC right before the start of maintenance. Haven't looked yet to see if it was caused by the SUS charge meaurements or by something else

Comments related to this report
camilla.compton@LIGO.ORG - 09:49, Tuesday 12 August 2025 (86314)Lockloss

Oli, Camilla

This lockloss occurs while the excitation on ETMX ESD was ramping up but doesn't look related to this. It looks like am ETM_GLITCH type lockloss.

Interestingly, at this time our DARM to L3 control has been moved from ETMX to ITMX and you can clearly see the glitch in ITMX_L3, see attached. As Sheila has been telling us al along, this is a clear indicator that the issue has nothing to do with the ETMX SUS glitching and is caused by DARM with the SUS just being the witness.

Images attached to this comment
H1 General
oli.patane@LIGO.ORG - posted 07:39, Tuesday 12 August 2025 (86312)
Ops Day Shift Start

TITLE: 08/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 6mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

Currently have been Locked for over 5.5 hours and out of Observing to run injections

LHO General
corey.gray@LIGO.ORG - posted 21:57, Monday 11 August 2025 (86310)
Mon EVE Ops Summary

TITLE: 08/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

Very easy shift with H1 locked over 11.5hrs (we've also "cooled" down to 85degF!)
LOG:  n/a

 

X1 DTS (ISC, OpsInfo, SQZ, SUS)
jeffrey.kissel@LIGO.ORG - posted 20:29, Monday 11 August 2025 (86311)
SPi Optomechanics: Picomotor Assembly Components
J. Kissel, C. Compton

Camilla and I took some pictures of what supply of picomotor assembly materials we (existing ICS Supply vs. what SPI) have and in what state of assembly they are in order to familiarize myself with the process of building up new assemblies. 

To the best of my knowledge, there's no assembly procedure. Instead, we have the Picomotor Fact Page (E2100196) [which I've, as of this aLOG, heavily updated / curated]:
    - A well-labeled exploded assembly drawing with only minor assembly errors, (Page 2 of D2100433)
    - a hand illustration from Rich on the wiring connections for an IXM100.C2, right-handed mount (D1400279) 
    - the expected two-motor pinout of the receiving D25M to 4x MM4F quadrapus cable (D1101516) 
    - Some instruction on how dis-mount and re-mount fully assembled picomotors (E2500163)
and thru a linear combination of these, you could fumble your way through it.

The picomotors themselves have evolved over the years as the original prefer vendor, New Focus, was bought out by Newport. 
:: First picture shows the difference between an old picomotor (left), and the modern 8301-UHV-KAP that we buy now (right). I've created D2500246 (as opposed to the old, non-specific E1000197) that captures the specific features of this model. The key differences between old vs. new being
    - The wires' insulation is kapton, not colored teflon
    - The wire lengths is a nice healthy 7 [in], not a short 2 [in] that required icky extension
    - The label of which wire is which is stamped into the metal (a "-" in the lower-left corner to indicate that the wire closest to that stamp is the negative lead, or "return") vs. indicated by color of wire.

:: Second picture shows the modern 8301-UHV-KAP picomotor by itself. Note, the "1" in 8301 indicates that we've chosen the 0.5" throw.

:: Third picture shows the cable unfurled and compared against the 1 [in] hole pattern of the optical table beneath the foil.

OK, now that you've gotten to know the raw picomotor, let's talk about cnonnectorizing and modifying it to suit our needs. We only have the old style picomotor fully assembled to picture as example, but it'll serve the purpose.

:: Fourth picture shows the real manifestation of Rich's artist impression of the fully connectorized two-motor system.

:: ECR E1400327 has us install a motion limiting shaft collar along the throw of the picomotor to limit the motion from the edge of its range where it's been found to get stuck. The collar was originally a custom D1400189 per -v1 of the ECR, but now it's a stock McMaster Carr shaft collar (6436k131, with the black-oxide steel #4-40 x 3/8 [in] L SHCS replaced with a stainless, otherwise identical, SHCS, 92196A108). The stock collar is then modified to be a bit thinner, per D1800220. Finally, to prevent the shaft collar from freezing against the picomotor body, we install a slip-on LIGO-cut kapton "washer" (D1400226; cut from 12 [in] x 12 [in] x 0.005 [in] sheet stock) around the threaded adjustment screw.
    - Fifth and Sixth pictures show how the shaft collar is shaved thinner,
    - Seventh picture shows the Kapton washers,
    - Eighth picture shows the collars assembled on the motor, and where the washer would be placed (these didn't have washers at the time of the picture, but we've since installed the on their to form a complete, albiet not-so-vacuum-compatible assembly).

:: Once connectorized, per Rich's drawing, to the 4-pin MMF connnector 803-003-07M6-4PN-598A, then the connector is secured to a custom L-bracket D1002763 via the connector's thumb screw. That L-bracket then secures to the optic mount's "other" 1/4"-20 mounting hole (with "the" 1/4"-20 mounting hole, 90-deg away, is presumably used to secure the mount to a post or breadboard). Note -- the L-bracket's thru-hole for the MM connector is keyed, but it's not sized for any feature on the actual connector, so you're free to orient the connector in any way in within the bracket. Of course, each socket connector on the legs of the quadrapus it'll connect to are much better keyed, so there's no worry of pin-clocking or anything nasty like that.
    - Ninth picture shows the D1002763 L-bracket. Note -- this a D1002763-v2 Type 1 bracket, so it's mounting hole is threaded for 1/4"-20 bolt (rather than Type 2 which has a thru-hole requiring a nut).
    - Tenth, Eleventh, Twelth, and Thirteenth pictures show how the MM connector is assembled on to that portion of the D1002763 L-bracket.

Finally, just because it came up during the pre-clean-and-bake inspection (see discussion in CNB:2225), 
    - Fourtheenth picture shows the inside of the 803-003-07M6-4PN-598A MM connector -- a  black plastic that Glenair calls a "High Grade Rigid Dialectric," without specifying the material (see table in Section 3.1 on page 2 of Mighty_Mouse_Series 80_performance-test-report-iaw-mil-dtl-810.pdf from T2500025). 
I mostly show the picture of the old connectorized picomotor system to indicate that we've indeed been using this connect and its inner material for a long time, and the Clean-and-bake process (T2100001) appears to be enough (see e.g. bake loads ICS:10543 and ICS:10557).

Images attached to this report
H1 AOS
corey.gray@LIGO.ORG - posted 17:10, Monday 11 August 2025 (86309)
Mon Eve Ops Transition

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

H1's been locked almost 7hrs and Tony took care of the SQZ guardian thing they discovered during the day shift (yay!).  With just that said, it's smooth sailing thus far.

Displaying reports 1881-1900 of 85743.Go to page Start 91 92 93 94 95 96 97 98 99 End