Jim, TJ, Robert
We damped the periscope on ISCT1 by removing the dog clamps one by one and inserting a strip of 1/16" viton between the dog clamp and the base of the periscope before retightening, making sure that the strips crossed the corner of the base. This is not the most effective way of damping the periscope but it was the fastest, safest and most simple damping we could do. Jim measured the Q to be around 1000, so we didn't have to do much to get an improvement. In Jim's first transfer functions after the damping, the peak looked a little wider.
Fil, Keita, Daniel, Camilla WP12598 WP12584
We swapped the old REFL Analog Camera to a Gige Digital Camera (Basler acA720-290g m S/N 40477593) on ISCT1 and cabled to the table feedthrough. There was no beams today so the alignment may need to be touched up.
Keita and Daniel also removed the MCL steering mirror, controller and the in-air POP-X WFS (S1300511, now stored in the EE shop) with mirror and lens from ISCT1. MLC controller and PZT will be stored in mid station storage. The beamsplitter towards the old POP-X path stayed but was blocked with the beam dump that used to be dumping the POP-X reflection.
Table layout D1201103 not yet updated. Photo of table attached.
Complete MCL PZT/controller inventory at LHO
Note 1: Each Mad City Labs PZT is supposed to be paired with a matching controller. Their manufacturer's serial number starts with MCLS (PZT) or MCLC (controller) but share the same number (e.g. MCLS02218 and MCLC02218). In the table below I only wrote down the number part.
Note 2: Each PZT and controller originally came in two separate boxes. These boxes for the units that are in use (or was at some point in time) weren't found in the MY storage except for one EX green WFS PZT/controller and another pair for EY.
Note 3: The PZT assembly for the old in-air POP-X that we pulled comprises the PZT, ALS Mad-City Labs base (D1300607), Mad-City Labs spacer (D1300608), Modified UPA1 holder (D1300124), and 1064nm HR 1" mirror. See 1st attachment.
Location | Purpose | S/N | Notes | Boxes? |
EX | Green inj | 02218 | alog 8080 | Not found |
02720 |
These replaced the high power unit (MCLC02219, the last row of this table), which was "to be replaced". alog 8080 |
Not found | ||
Green WFS | 02717 | at MX, top shelf (3rd pic) | ||
02719 | Not found | |||
EY | Green inj | 02718 | alog 8080 | Not found |
02722 | alog 8080 | Not found | ||
Green WFS |
02721 | at MX top shelf (3rd pic) | ||
02724 | Not found | |||
MY storage | H1 Spare | 02723 | "H1 Spare" written on the open box, mid shelf (3rd pic) | In the original boxes |
03126 |
Pulled from ISCT1 in Jun/2025. Used to be for old in-air POP-X. Mid shelf (1st/3rd pic). PZT is stored as an assembly with ALS Mad-City Labs base (D1300607), Mad-City Labs spacer (D1300608), Modified UPA1 holder (D1300124), and 1064nm HR 1" mirror in a gray plastic bin, on which the controller is directly placed. |
PZT assy in a gray bin. | ||
3IFO | 02725 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | |
03125 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | ||
03127 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | ||
03132 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | ||
03133 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | ||
03134 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | ||
03135 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | ||
03136 | All stacked up, "3IFO ISC" on the box (2nd pic) | In the original boxes | ||
Spare of spare | MCLC02219 |
Top shelf (3rd pic). Controller only (no PZT was found), high-power version (Nano-Drive 85), old EX unit which was replaced. alog 8080 This is 2U-high, accepts 110V AC rather than LIGO 3-pin DC and looks different from the rest of the controllers. |
No box |
WP 12572
The 24V power for the table enclosure lights on ISCT1 and IOT2L were rerouted through the Interlock/Lighting patch panel D1201535. Panel has a power switch and Status On/Off indicator. The dimmer functional was left in place and requires both the panel power switch and dimmer in the ON position for LEDs to power on.
WP 12574
New GigE camera was installed in ISCT1, alog 84866. Camera is connected to the new CER switch, port 12. Three ports on the SUS-R1 patch panel are available for new GigE cameras.
Power to the three IOT2L analog cameras was disconnected:
Power cable did not have a dedicated Feedthrough. Analog cameras are no longer used. The 18V power cable is on top of IOT2L if power needs to be reconnected.
HWS servers now point to /ligo/data/hws as the data directory.
The old data directory, h1hwsmsr:/data, is now moved to h1hwsmsr:/data_old
The contents of the old directory were copied into the new directory, except H1/ITMX, H1/ITMY, H1/ETMX, H1/ETMY, under the assumption that these only contain outputs from the running processes.
HWS processes on h1hwsmsr, h1hwsmsr1, h1hwsex were stopped and restarted and are writing to the new directory.
h1hwsey had crashed previously and wasn't running. It was restarted and is also writing to the new directory
This is a very quick first look at the ASC performance with the HAM1 ISI. Jim is still working on bringing the ISI up to full performance, but the first attached plot compares the INP1 P and CHARD P error spectra from March 31 just before the vent and yesterday, when we locked to full power and low noise with HAM1 in the isolated state.
Before the vent, we were running feedforward of the HAM1 L4Cs to CHARD, INP1 and PRC2. PRC2 is now on the POP sensor, and CHARD and INP1 both use a combination of the REFL WFS 45 MHz signals. The large peak around 20 Hz before the vent appears to have reduced in INP1 P and shifted down in frequency in CHARD P. The second attachment shows that large peak in CHARD P is coherent with the HAM1 GS13s, from about 10 to 20 Hz, especially with RX, RY, RZ, and Z.
There is also a peak at 6 Hz, which we know is a vertical resonance of the RMs, 84712.
WP12596
Daniel, Vicky, Kevin, EJ, Erik, Dave:
We have installed new h1ioplsc0 (RCG5.1.4) and h1omcpi(RCG5.3.0) models. This led to a small IPC receive error rate on h1omcpi. To correct for this we upgraded h1omc0 from RCG5.3.0 to the latest RCG5.5.0, rebuilding all the models [h1iopomc0, h1omc, h1omcpi] against this RCG. Erik booted h1omc0 from the new boot server h1vmboot5-5 (and removed it from h1vmboot0). We are letting it sit for a while to ensure there are no IPC errors before a DAQ restart.
DAQ restart for model changes and RCG upgrade for h1omc0: 0leg 11:02, 1leg 11:80. No problems.
Fri Jun 06 10:04:56 2025 INFO: Fill completed in 4min 52secs
For FAMIS #26389: All looks well for the last week for all site HVAC fans (see attached trends).
To investigate the 70Hz feature in HAM1 chamber, which Jim reported in his alog (LHO 84638) I started looking into the structural resonances of the periscope which is installed in HAM1 (see two pictures which TJ sent me, was taken by Corey here - view01, view02) .
Betsy, handed me a periscope (similar but not exactly the same) for investigation purpose, which is now setup in staging building. I attached an accelerometer to the top of the periscope and connected it to the front end of the B&K setup for hammer impact measurements - see picture of the experimental setup here.
At first I used two dog clamps to secure the periscope. The results of the two dog clamp B&K measurement is shown in this plot (data from 0.125 to 200Hz)) - one can see a 39Hz feature in the Z hit direction. See zoomed-in (30-100Hz) figure here.
Next, I attached a third dog clamp, just like in HAM1 chamber and took a second round of measurements (especially for Z direction impact).
This plot compares the two vs three dog clamps scenario on the periscope and one can see that the resonance mode has been pushed up from 39Hz to 48Hz.
FAMIS28948
The quarterly reminder came at a good time for us to restart fresh for observation next week. Reboot went as expected, no hiccups. Reboot started at 1553UTC.
Closes FAMIS26502
2025-06-06 08:41:32.265177
There are 2 STS proof masses out of range ( > 2.0 [V] )!
STS EY DOF X/U = -4.667 [V]
STS EY DOF Z/W = 2.386 [V]
All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.521 [V]
STS A DOF Y/V = -0.607 [V]
STS A DOF Z/W = -0.719 [V]
STS B DOF X/U = 0.2 [V]
STS B DOF Y/V = 0.974 [V]
STS B DOF Z/W = -0.422 [V]
STS C DOF X/U = -0.857 [V]
STS C DOF Y/V = 0.855 [V]
STS C DOF Z/W = 0.629 [V]
STS EX DOF X/U = -0.034 [V]
STS EX DOF Y/V = -0.051 [V]
STS EX DOF Z/W = 0.072 [V]
STS EY DOF Y/V = 1.164 [V]
STS FC DOF X/U = 0.195 [V]
STS FC DOF Y/V = -1.134 [V]
STS FC DOF Z/W = 0.628 [V]
Closes FAMIS26423
Laser Status:
NPRO output power is 1.85W
AMP1 output power is 70.39W
AMP2 output power is 140.3W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 18 days, 0 hr 26 minutes
Reflected power = 23.16W
Transmitted power = 105.5W
PowerSum = 128.6W
FSS:
It has been locked for 0 days 1 hr and 12 min
TPD[V] = 0.801V
ISS:
The diffracted power is around 3.8%
Last saturation event was 0 days 13 hours and 21 minutes ago
Possible Issues:
PMC reflected power is high
Randy, TJ, Fil, Richard, Camilla, WPs: 12593, 12594
After Fil and Richard un-cabled ISCT1, TJ and I added guillotines to HAM1 +Y VPs, removed bellows and attached yellow VP covers. Randy then fork-lifted ISCT1 away from HAM1 and placed it next to IOT2L.
At the end of the day on Friday, Randy fork-lifted ISCT1 back to HAM1. Location and height was adjusted to match markings. We left the yellow VP covers on and bellows off as HAM1 VAC had started pumping.
TITLE: 06/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 11mph Gusts, 5mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
I wrangled some SDFs before Daves LSC and OMC model restarts, for SQZ and SQZ_ASC I did not accept them.
Ryan and I decided to temporarily accepted H1:SQZ-FC_ASC_SWITCH as OFF so that FC optics aren't pulled away after restarts. This will need to be re accepted as ON before we go to Observing.
I noticed that the LLCV is railing at its top value, 100% open, it can't open no more. This is a known issue, but it appears as if the valve is reaching 100% sooner than expected, meaning when the tank is almost half full. First, I'm going to try a re-zero the LLCV actuator and await for the results. First attachment is a 2 day plot of LLCV railing today and yesterday. The second plot is a 3 year history looking at the tank level and the LLCV, it rails at 100% a few times.
BURT restore? PID tuning ok? CP2 @ LLO PID parameters attached for comparison.
Thanks Jon. However, this system has a known issue, it turns out that the liquid level control valve is not suitable for the job, that is the reason why it reaches 100% sooner than later, but it appears as if something slip, now it reaches 100% at a higher level, this is the reason why I want to re-zero the actuator.
Attached is the Fill Control for CP7 The issue was mentioned here for the first time aLOG 4761, but I never found out who discovered this is only briefly mentioned by Kyle. Another entry on aLOG 59841.
Dirty solution of solving the issue with the LLCV getting railed at 100% open, we used the bypass valve, opened it up by 1/8 of a turn and that did the job. Not a single shot, but eventually we settle on that turn number. PID took over and managed to settle around to 92% open for the LLCV. Today we received a load for the tank for CP7. We are still going to calibrate the actuator.
Bin Wu, Julia Rice
We have been working on writing a new Guardian script that will allow us to switch off the dither loops sooner in the power up process and instead use cameras.
We first looked at the error signals in the ASC cameras to see if we could adjust offsets to better values. We did this for the CAMERA_SERVO guardian, and added new intermediate states, including TURN_ON_CAMERA_25W_OFFSETS and TURN_ON_CAMERA_MOVESPOTS_FIXED_OFFSETS. We've attached screenshots showing the graph before and after our additional states. Below are the values we used for offsets for each. The weight from DITHER_ON to TURN_ON_CAMERA_25W_OFFSETS is set to be 10.
TURN_ON_CAMERA_25W_OFFSETS
PIT1 | -233 |
PIT2 | -168 |
PIT3 | -217 |
YAW1 | -248 |
YAW2 | -397 |
YAW3 | -338 |
TURN_ON_CAMERA_MOVESPOTS_FIXED_OFFSETS
PIT1 | -232 |
PIT2 | -159 |
PIT3 | -226 |
YAW1 | -248 |
YAW2 | -431 |
YAW3 | -351 |
We also adjusted the offsets for TURN_ON_CAMER_FIXED_OFFSETS:
PIT1 | --230 |
PIT2 | -181 |
PIT3 | -226 |
YAW1 | -245 |
YAW2 | -418 |
YAW3 | -353 |
These are added in lscparams.py. We also added the necessary code into CAMERA_SERVO.py.
We also added a parameter in lscparams.py for new ADS camera CLK_GAIN at 25W ('ads_camera_gains_25W', screenshot included)
Right now the new states are not requestable, so they will need to be ran manually to test. We haven't made any change to the ICS_LOCK guardian.
Also added lines in CAMERA_SERVO.py under DITHER_ON to check if ISC_LOCK is at 25W when proceeding through self counter loop, see attached.
Adding A2L gains for reference, first chart clarifies dither loop actuators and cameras.
Beam pointing actuator | ADS Dither | Cam Sensor |
PRM PIT | Dither ITMX: ITMX P2L | BS Cam 1 PIT |
PRM YAW | Dither ITMX: ITMX Y2L | BS Cam 1 YAW |
X SOFT PIT | Dither ETMX: ETMX P2L | ETMX Cam 2 PIT |
X SOFT YAW | Dither ETMX: ETMX Y2L | ETMX Cam 2 Yaw |
Y SOFT PIT | Dither ETMY: EMTY P2L | ETMY Cam 3 PIT |
Y SOFT YAW | Dither ETMY: ETMY Y2L | ETMY Cam 3 Yaw |
GRD State | A2L Gain | Cam Offset |
POWER_25W [506] | P2L ITMX: -1.25 | -233 |
P2L ETMX: 0.85 | -168 | |
P2L ETMY: 0.85 | -217 | |
Y2L ITMX: 0 | -248 | |
Y2L ETMX: 0 | -397 | |
Y2L ETMY: 0 | -338 |
GRD State | A2L Gain | Cam Offset |
MOVE_SPOTS [508] | P2L ITMX: -1.8+1.0 | -232 |
P2L ETMX: 4.0 | -159 | |
P2L ETMY: 3.6+1.0 | -226 | |
Y2L ITMX: 2.1 | -248 | |
Y2L ETMX: 4.4 | -431 | |
Y2L ETMY: 2.2+1.0 | -351 |
GRD State | A2L Gain | Cam Offset |
MAX_POWER [520] | P2L ITMX: -0.54 | -230 |
P2L ETMX: 3.31 | -181 | |
P2L ETMY: 5.57 | -226 | |
Y2L ITMX: 3.23 | -245 | |
Y2L ETMX: 4.96 | -418 | |
Y2L ETMY: 1.37 | -353 |
I was only able to take the broadband measurement due to an earthquake that knocked us out of lock a minute later. We had been at full power for around 5 hours at the time this measurement was run. Unfortunately since we weren't able to take the Simulines measurements, I am not able to run the report.
Broadband:
Start time: 1433118749 (2025-06-05 00:32:11 UTC)
End time: 1433093874 (2025-06-05 00:37:36 UTC)
Data found in: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250605T003226Z.xml
I haven't had time to post this because of the wind fence work, but I haven't been able to finish the commissioning of the HAM1 ISI because of a 70-ish hz feature in mostly the X and RZ plants. I didn't see or appreciate how large this 70hz feature was in my close out measurements before doors went on, and it's making the loop design very difficult. I was trying to notch the loops to make the ISI work, but 70hz is very close to the nominal 30hz loop ugf. The X,Y,RZ and Z loops are marginally stable right now, and the 70hz feature gets injected into the IMC when ALS is locked. I think that I can get the loops working, but probably with less gain than we would otherwise get.
Attached PDFs are the loops currently installed, the ISI is set to not use the RX and RY loops, but the X loop is probably ringing at 70hz when the ISI is isolated. We are currently running with just the damping loops though.
I was able to get the ISI running yesterday, by adding notches to the loops at ~72hz, reducing the boost gain and reducing the ugf of the loops to generally around 22-25hz. The ISI was running most of yesterday and through the night, until I shut it off for the HAM1 vent this morning. Attached are the loop design plots for the loops that are running now.