Ran Bruco now we' ve moved spot on PR2 (alog 78878) 2024/07/10 16:18 UTC (1404663547) from when our range was ~156MPc: Link: GDS_CLEAN_1404663547/

In last week's bruco 78879, Sheila pointed out that the LVEA accelerometers and HAM2 coherence has around 30-40Hz.

• CHARD PITCH and especially YAW - bad below 25Hz
• HAM2 - Coherence < 20Hz, 30-40Hz better than last week. 
• LVEA Floor Accel XCYRO -last weeks 30-40Hz coherence mostly gone 
• PRCL - better than last week, still broad coherence at 0.1 level.
• SRCL -13, 17, 20Hz coherent peaks
• MICH -  20Hz coherent peak

Wed Jul 10 08:14:48 2024 INFO: Fill completed in 14min 44secs

Jordan confirmed a good fill curbside.

I noticed this at the end of my shift yesterday, and now that the IFO has had a longer lock it has confirmed that ITMY mode 6 is slowly ringing up through the lock. These modes are right on top of each other so we have always struggled to damp them well, but we have found settings that have worked for most of O4. Whatever changes we've made with the IFO recently have made those settings not work.

I'm mainly writing this as a reminder for operators to keep an eye on these modes. Hopefully I'll find a setting that will work, but these ones are always a headache.

TITLE: 07/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 6mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY: Locked for almost 6 hours after the earthquake passed through. range is much better than yesterday, tipping into the 160's a bit.

TITLE: 07/10 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently relocking and at MOVE_SPOTS. We were knocked out by a large earthquake and it kept us from trying to lock for two hours. I ran an initial alignment and relocking is going quickly. The two other locklosses from my shift are a mystery to me, but from the first lock we can clearly see that our range is lower after today's activities, although the second lock of my shift, the 36 minute one, we did get up to 155Mpc pretty fast, so maybe it was just that first lock back.

And maybe this already has an alog somewhere, but Gerardo noticed that a peak at 20 Hz was pretty big during our first lock back after maintanence. Looking back, it first appeared on may21st, and although its height fluctuates, the past week and a half it seems to have gotten progressively larger.

LOG:

23:00 Detector Observing at 147 Mpc
00:29 Out of Observing to tune sqz
00:39 Back to Observing

01:20 Lockloss
01:47 We were cycling through MICH_FRINGES so I took us to DOWN to start an initial alignment
02:11 Initial alignmet done, relocking
02:57 NOMINAL_LOW_NOISE
03:00 Observing

03:37 Lockloss
    - going to run initial alignment again since during the last one we had some ground motion that might've affected alignment
    - ALS_XARM had to adjust the fiber polarization
04:06 Initial alignment done, relocking
05:04 NOMINAL_LOW_NOISE
05:06 Observing

05:16 Lockloss from earthquake, staying in downn while earthquake passes
07:26 Starting an initial alignment
07:45 Initial alignment done, relocking

Another :(

Lockloss @ 07/10 05:16UTC due to an incoming 6.7 earthquake. We had been locked for only 12 minutes :(

We were knocked out by the S waves, the R waves aren't coming for another hour so we are going to be down for a good while.

FranciscoL

After one week of having the inner beam centered on the Rx sensor (LHO:78810), on July 09, we moved the beam from center to the right.

This movement was done to double check the changes seen after our move on May 14 (LHO:77840). LHO_XY_Comparison_dataVmodel_1399180506-1404571480.pdf shows the full cycle and nominal results of our series of pcal beam movements, which ended on 24-07-09 @ 08:00 PT. The plot legend shows the value given by the weighted mean of each week using the mean value of each observing stretch for the distribution. The *raw* data for each observing stretch is plotted in gray but, for scaling purposes, some of that data is outside the range of the plot. The black line is what we expected the X/Y comparison to yield from the beam movements that we made. EDITORS NOTE: The vertical axis on the plot is in HOPs (Hundreth of a percent). Although some changes are unexpected, these are not concerning or significant changes that will affect LHO calibration. It is also an ongonig investigation, we are learning as we go.

The movement done in May 14 is seen on the first step of the plot, a week after having both beams centered, where the weighted mean yields a value of 0.99747 – a change of -25 HOPs from the previous week. However, as seen in the model, we expected the line to change by +19.2 HOPs. The rest of the movements *agree* with our model. Further analysis and diagnostics are pending but the main takeaway is that the data does not match the model for this one move, which motivates repeating the measurement.

During this procedure, we used keithley DVM (KVM) 1424277 instead of the FLUKE handheld DVM.

EndStationLog.pdf lists the voltage values after each significant step of procedure T2400163. The steps represent writing down a voltage value after a particular change to the beam position. Some highlights from the recorded values.

• (Both beams) We gained a digit by using the KVM but it fluctuates by ±0.0002V.
• (Target off) Finalized beam movement and recorded the voltage from the Rx sensor with the inner beam only. See InnerBeamAfter.jpg for visual proof of the movement. Voltage of 1.6820V is 10 HOPs lower to previous position (1.6836V). Fine adjustments to pitch and yaw did not improve the amplitude of the signal.
• (Both beams) The measurement was recorded after removing beam block on outer beam and removing the target. See BothBeamsAfter.jpg for the final state of the pcal beams incident on the input port of the Rx sensor. The measurement of 3.3832V is lower by 4 HOPs from the initial measurement (3.3847V).

The KVM was calibrated using a Martel voltage/current calibrator (Martel) after the procedure. The KVM was configured to a range of 10V and a resolution of 6.5 "FAST digits ("FAST" is referred to the time it takes for the ADC on the KVM to integrate; a 6.5 FAST resolution corresponds to an integration time of 16s) . The following table lists the voltages provided by the Martel and the corresponding readings displayed on KVM 1424277.

In summary, (1) using a KVM increased the resolution of our measurements for the beam movement procedure. (2) The 'Initial' measurement changed by 8 HOPs from the last voltage measurement from the previous movement (3.382V), done on July 02 (LHO:78810). (3) The initial and final voltage measurement during today procedure changed by 4 HOPs.

Lockloss @ 07/10 03:37

Lockloss @ 07/10 01:20UTC

07/10 00:29 UTC I took us out of Observing to tune the squeezer since we have now been locked for over three hours.

WP11970 h1susex 28AO32 DAC

Fil, Marc, Erik:

Fil connected the upper set of 16 DAC channels to the first 16 ADC channels and verified there were no bad channels in this block. At this point there were two bad channels; chan4 (5th chan) and chan11 (12th chan).

Later Marc and Erik powered the system down and replaced the interface card, its main ribbon cable back to the DAC and the first header plate including its ribbon to the interface card. What was not replaced was the DAC card itself and the top two header plates (Fil had shown the upper 16 channels had no issues). At this point there were no bad channels, showing the problem was most probably in the interface card.

No DAQ restart was required.

WP11969 h1iopomc0 addition of matrix and filters

Jeff, Erik, Dave:

We installed a new h1iopomc0 model on h1omc0. This added a mux matrix and filters to the model, which in turn added slow channels to the DAQ INI file. DAQ restart was required.

WP11972 HEPI HAM3

Jim, Dave:

A new h1hpiham3 model was installed. The new model wired up some ADC channels. No DAQ restart was required.

DAQ Restart

Erik, Jeff, Dave:

The DAQ was restarted soon after the new h1iopomc0 model was installed. We held off the DAQ restart until the new filters were populated to verify the IOP did not run out of processing time, which it didn't. It went from 9uS to 12uS.

The DAQ restart had several issues:

both GDS needed a second restart for channel configuration

FW1 spontaneously restarted itself after running for 9.5 minutes.

WP11965 DTS login machine OS upgrade

Erik:

Erik upgraded x1dtslogin. When it was back in operation the DTS environment channels were restored to CDS by restarting dts_tunnel.service and dts_env.service on cdsioc0.

Lockloss @ 07/09 01:46UTC after 8.5 hours locked

Lock loss 1404445312

5 hours and 42 mins seems like a standard lock for this week. LSC-DARM saw an odd wiggle before lock loss, normally I see an ETMX output that matches this but I didn't see that this time.