I have installed a new EPICS IOC (dac_overflow_rate_ioc) which for each model calculates the per second increase in the accumulated DAC overflow counter. If the rate is non-zero, the upper block of the DAC Overflow square in the CDS Overview turns yellow. The lower block shows dark green if the accumulated counter is non-zero (i.e. overflows in the past which have not been cleared).
The new IOC runs on the service host cluster, it is monitored by a "DAC OVERFLOW" system block at the bottom of the CDS Overview.
Please note that the accumulated DAC overflows wrap-around at 0x1000000 (just over 16 million) to prevent the number on the MEDM becoming too large to be read.
Jennie W, Sina K, Jim W,
We made good progress today. There was a factor of 4 that we had forgotten in the demodulation that you need to scale the final amplitude by to get the Vpp. Once we put this in we get ~100% for the reference interferometer and 76% for the measurement interferometer.
We debugged the demodulation calculation by turning off the signal input to the REF A IFO and then looking at what heterodyne amplitude it calculated when we injected a signal of 2Vpp into the H1:SPI-H23_IFO_REF_A_DEMOD_SIG filter bank.
See the photo showing the injected signal calibrated into volts in yellow, in purple the amplitude calculated as A = sqrt( I^2 + Q^2), where I and Q are the output of the demodulator, and in red is the out amplitude after multiplying by a factor of 4.
I put this calibration factor into all four H1:SPI-H23_IFO_{REF,MEAS}_{A,B}_HETAMP filter banks as cal_demod in FM0.
We also measured the dark offsets for the four PDs and two QPDs. We did this with the shutter closed. From the input counts, the QPD B segments look a lot noisier than the QPD A segments so I wonder if we are getting scattered light from main IFO beam.
I might redo this dark offset test with the JAC unlocked or with the PSL shuttered in order to verify this. It might also explain why we occasionally get the efficiency calculation of the reference interferometer coming out to 101% if we have stray light on one or more PDs.
The calibration factors and new dark offsets were accpted in SDF.
One of the nights this week we will start our program of calibration measurements using the ISI sensors to calibrate the SPI sensors.
Per WP 13415 I finished migrating the dust monitors and the dewpoint monitor to the IOC cluster (service-host 0,1,2). With this I was able to turn off the old h0epics server. These will now auto start after power outages as well as there are no manual steps in the startup sequence.
One note.
The dewpoint monitor held its files in /ligo/lho/h0/target. As a limit in the container I am running these in it wants the command that is executed to be under /opt/rtcds. So I copied the target area over to /opt/rtcds/lho/h1/target and put a symlink in on /ligo/lho/h0/target/dewpoint.
TJ, Camilla WP #13528
Today we swapped the ITMY HWS SLED as it had degraded, last swapped May 2025 84417.
Following the T1500193 procedure
TITLE: 08/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: After diagnosing some alignment troubles, work has continued towards being able to lock PRMI. The ITMY HWS SLED was swapped, the corner volumes continue to be pumped down, and the LVEA is still Laser HAZARD.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 14:38 | FAC | Randy | LVEA | - | ISI craning prep | 15:31 |
| 14:52 | FAC | Kim | LVEA | - | Technical cleaning | 15:47 |
| 16:35 | PSL | Jason | OptLab | - | Parts search | 16:56 |
| 17:04 | SEI | Jim | FCES | - | HAM8 ISI work | 21:04 |
| 17:07 | FAC | Kim | EY | - | Technical cleaning | 18:07 |
| 18:26 | VAC | Gerardo | LVEA | - | Checking HAM7 | 18:31 |
| 19:52 | FAC | Randy | LVEA | - | Craning scissor lift | 20:52 |
| 20:45 | VAC | Gerardo, Travis | LVEA | - | Prepping to move super sucker from HAM1 to HAM6 | 21:25 |
| 21:22 | SEI | Shoshana, Huyen | LVEA | - | Removing CRS laser copper block | 21:32 |
| 21:42 | DAS | Jenne, Reinhardt | LVEA | - | Running DAS fiber | 22:10 |
| 22:08 | SAF | TJ | LVEA | YES | Transitioning to Laser HAZARD | 22:40 |
| 22:42 | TCS | TJ, Camilla | LVEA | YES | Swapping ITMY HWS SLED | 23:29 |
[Huyen, Shoshana]
We saw worsening CRS noise after adding copper block on top of the laser in an attempted to help with thermal regulation. We went ahead and removed the copper block and saw that the noise improved significantly.
Picture one shows the noise taken over the weekend with copper block on the laser (with capacitive damping on) [ref], and the noise during the day right after the block was removed (with capacitive damping on).
When removing the copper we noticed it was pretty cool to the touch, so it probably wasn't providing much thermal regulation to begin with (i.e. the TEC is doing it's job). Our best guess for why it was worsening the noise is that having some extra weight on the laser was adding some extra stress onto it which was translating to the signal.
Since getting the capacitive damping hooked up, we've been keeping the gain at 100, which seems to damp down the CRS at a reasonable rate without putting to much voltage on it, and we decrease the gain to 50 once the CRS is relatively damped down.
We've been having some confusion in the control room this morning on the IFO alignment as we've been struggling to lock PRMI despite running the usual initial alignment steps successfully and with it having been locked last week. While trending things from last week to see what may have changed, Louis discovered that around 05:45 local time last Monday morning (August 10th), the alignments for the IMs changed notably according to their OSEM readbacks. This lines up with an earthquake that came through at that same time, which tripped the ISI platforms in HAMs 1-5 (noted in the operator shift start alog). It's been seen in the past that a HAM2 ISI trip has caused the IMs to move, so unfortunately this isn't surprising. Also unfortunately, the alignments for the IMs were not restored, so the alignment work that took place later that day to prepare for the peek down the X-arm (alogs 91463 and 91470) would have been done with the assumption the input IFO pointing was good, while in reality it was not.
I have restored the alignments of IMs 1-3 according to their OSEM readbacks before the ISI trip, and Louis confirmed the alignment to the IM4 TRANS and ISS secondloop PDs are good. We will continue to recover alignment in the corner to work towards DRMI locking again.
JAC length dither line at 809Hz is on. I also editted the Guardian so that he won't disable it.
It will keep engaged for a couple of days.
TITLE: 08/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: CALM
Wind: 5mph Gusts, 3mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY: With all chambers now closed and pumpdown ongoing, the focus this week will be continuing corner alignment and improving DRMI locking. The IMC is locked at 2W and the LVEA is Laser SAFE.
All four JAC pico axes (heads A and B, X and Y motors) have been calibrated in counts to beam displacement on the WFS, by non-locked sweeps read through the WFS DC signals. Efficiencies come out at 0.6–1.2e-3 beam radii per count (0.09–0.19 μm, 0.8–1.6 μrad of beam pointing), with a direction dependence of 9–27 %.
The fit gives the efficiency in beam radii (d/w) per count. Beam radii at the QPDs from the JAC reflected-path optical model:
| plane | wx [μm] | wy [μm] |
|---|---|---|
| WFS A | 199.4 | 181.0 |
| WFS B | 150.0 | 155.9 |
Denominator: SYS-MOTION_C_PICO_D_CURRENT_X/Y_POSITION [counts] of the swept motor. "up" / "down" refer to the sign of the count sweep.
| pico / motor | QPD axis | direction | d/w per count | μm per count | μrad per count (beam) |
|---|---|---|---|---|---|
| A / X | A YAW (x) | up | -9.41e-4 | 0.188 | 1.64 |
| A / X | A YAW (x) | down | -7.82e-4 | 0.156 | 1.36 |
| A / Y | A PIT (y) | up | -7.33e-4 | 0.133 | 1.16 |
| A / Y | A PIT (y) | down | -8.05e-4 | 0.146 | 1.27 |
| B / X | B YAW (x) | up | -1.22e-3 | 0.183 | 1.60 |
| B / X | B YAW (x) | down | -9.32e-4 | 0.140 | 1.22 |
| B / Y | B PIT (y) | up | -5.72e-4 | 0.089 | 0.78 |
| B / Y | B PIT (y) | down | -7.00e-4 | 0.109 | 0.95 |
Attachments: per-axis sweep figures (normalized signal against pico counts).
Miranda, Dave:
Friday afternoon we updated the cable labeling for the ACC BNC coax cables at EX, MX and MY. EY cables were already complete.
At EX we reconnected the BNC for H1:PEM-EX_ACC_OPLEV_ETMX_Y_DQ which we had found to be disconnected. Plot shows it had a signal until the 23rd June of this year.
(Travis, Gerardo)
The ion pump for HAM1 was incorporated to the HAM volume yesterday, and today the SS-500 pump cart was isolated from the chamber (turbo pump and SS-500 remain on), and as expected the pressure went up and now we are waiting for the ion pump to take over and maintain the vacuum pressure for HAM1. We will be monitoring the progress of the ion pump.
(Travis, Gerardo)
We stopped pumping against the isolation valve for HAM1 turbo, now the turbo needs to spin down before we can disconect the cable from the magnetically levitated turbo pump. The flex hose was removed and the scroll pump was stopped, but needs to remain on until the turbo stops spinning.
(Travis, Gerardo)
We removed the old gauge a BCG-450 and installed a new one a BPG-552. Since the gauge at this location does not play role with relays and such, the old pigtail did just fine, provided the power to the new gauge. The new gauge is powered on and connected to the same EtherCAT cable as the one that that we removed. Dead volume of this assembly is getting pumped down with a small can turbo pump and an aux-cart, and a very long flex hose, and probably will continue to pump over the weekend.
No issues were encountered while replacing the gauge.
(Travis, Gerardo)
Aux-cart and all other accessories have been removed from this gauge.
We need to leak check the conflat on this new gauge.
(Travis, Gerardo)
Today we leak checked the 2 3/4" CF joint for the new gauge at PT-180. The leak detector did not detect a leak above the background, we connected the leak detector at the XBM main turbo pump and we sprayed the joint with copious amounts of helium. Helium background of 6.0X10-10 Torr*l/sec.
(Travis, Gerardo)
This morning we checked HAM7 annulus system pumpdown and the aux-cart displayed 2.6X10-05 Torr, good progress so it appears to be doing good. We disconnected the SS-500 cart from HAM6 turbo and connected it to HAM7. We checked all ports were "nominal", detached the active purge hose and no blowdown was done, since we had the relay tube valve (RV-2) open, took advantage of this and we let the purge air purge HAM7 overnight out RV-2. After closing RV-2 we started the pumpdown of HAM7. The purge valve (all metal valve) and the roughing valve at the turbo assembly were closed at 3.0X10-05 Torr.
Attached is a plot of the pumpdown thus far.
Jennie W,
Since Daniel put in a TEC controller for the JAC temperature servo we will no longer use the current version of the guardian control loop so I have set JAC_HEATER guardian to SERVO_OFF. The TEC is turned on and the set point is at 25.4 Degrees C.
The servo controller can be reached by going to sitemap->IOO->JAC Overview->Controller. To turn it off select the 'OFF' button in the top right corner of the controller. The loop can be measured by using the excitation button noted in the picture.
I will trial this over the weekend so I can double check it doesn't drive the JAC away from the control point.
I'm running a script called inject_TEC.py which does a swept sine from 0.01 to 100 Hz on the TEC heater servo. This has an amplitude of 0.001V so shouldn't have a big effect on the temperature.
See photo for the control signal, JAC heater drive voltage and the error point.
It will take this voltage away from the DAC output votlage used to drive the JAC heater and so shouldn't disrupt the temperature control of the JAC so it will stay locked.
The current measurement takes 31 minutes and I started it at 04:24:37 UTC.
It stopped at 04:56:03 UTC.
I will leave the JAC Heater servo running as it was working servoing the temperature to 25.4 degrees C all weekend (apart from a brief period when Masayuki unlocked for calibration measurements earlier today.
Camilla, Oli, Caroline, Masayuki, Sheila
During this realignment, SR3 was moved 65urad in Pitch, see attached.
TITLE: 08/11 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: CALM
Wind: 9mph Gusts, 4mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY:
The M2 stage of the BS has been moving a lot since yesterday afternoon ~21:17 UTC, the oplev damping has grown with it.
The BS oplev damping was turned back on by me inadvertently yesterday. The OLDAMP Gain increases happened right as I requested DOWN from the ISC_DRMI guardian. Masayuki and I did notice additional motion on the BS yesterday but we didn't know at the time whether it was due something we did or from something someone else was doing. Now, looking at the timing of the grd state request and confirming by looking at ISC_DRMI.py, I can say that the BS oplev damping was 1.) turned on by accident and 2.) can be / should be turned back off.
I tried to SDF the oplev damping off, see 91267, but I never checked what the guardians do. I recommend we change the guardian code to not engage oplev damping until we can diagnose why it isn't working, specifically, saturating the suspension.
This was messing us up again today. I commented out the BS Oplev DAMP lines in the ISC_DRMI DOWN state.