We removed the BSC1 temperature sensor to run some testing in the lab. Will reinstall next week.
J. Kissel Today Dave installed all the simulink front-end code infrastructure that Oli and I built for PM1 (see LHO:83214), Oli created a generic MEDM macro for PM1 and attached a call to that file with the generic HTTS MEDM screen to the sitemap yesteday. That meant I had everything in place for me to completely fill out the PM1 infrastructure: - Populated OSEM2EUL, SENSALIGN, and EUL2OSEM matrices with generic HTTS values - Populated OSEMINF filter banks with standard OSEM calibration filters and turned them ON with a gain of 1.0 for now - Populated the DAMP filter with standard (recently improved) HTTS damping filters - Populated the COILOUTF filter bank with HAM-A coil driver frequency response compensation, and turned the filters on with magnet polarity compensating gains of UL LL UR LR = +1, -1, -1, +1' - Populated and turned on the RMS filtering to support the watchdog trigger signals, and set the threshold to 150 [urad_RMS] as is the case for other HTTS - Turned on the on-diagonal elements of the DRIVEALIGN matrix - Set the calibration gain of the OPTICALIGN alignment offsets to 1.0, which is not the right number, but standard for HTTS. Turn the offset ON. Then monitored and accepted all the settings in the h1sushtts_safe.snap, expect the OPTICALIGN offsets. The committed the safe.snap and filter file to the userapps repo. All we need now is PM1 itself!
Annual groundwater sampling took place today. The well pump near EY ran for 20 minutes from 8:46a-9:06a PT. T. Guidry
New models have been installed for h1asc, h1suspr3, h1iopsush2b, h1susim, h1sushtts and h1susauxh2. The DAQ was restarted for these model changes (no EDC) between 08:22 and 08:30.
h1seih16 was fenced from Dolphin and powered down for H16 rack power work, fixing IO Chassis Adnaco backplane and installing ISI-HAM1 ADC/BIO cards.
J. Kissel ECR E1700228 WP 12370 I've executed the PR3 Optical Lever QPD AA Cable move from SUS-C4 U11 D9 Port 7 to SUS-C4 U32 D9 Port 8 described in more detail a few days ago (LHO:83168) in order to make room for the incoming PM1 (per ). See LHO:83168 for "before" pictures; I attach "after" pictures here: - 2025-03-11_SUS-C4_PR3OplevMove_U11_AAChassis_After_1 shows that D9 port 7 and 8 of U11 AA chassis are now vacant, - 2025-03-11_SUS-C4_PR3OplevMove_U11_AAChassis_After_2.jpg shows that this AA chassis is serial number S1202339. - 2025-03-11_SUS-C4_PR3OplevMove_U32_AAChassis_After_1.jpg shows the big-picture scene around U32 AA chassis, - 2025-03-11_SUS-C4_PR3OplevMove_U32_AAChassis_After_2.jpg shows the cable, "H1:OP LEV_PR3_AA" or "H1:SUS-HAM2_88" specifically, connected into to U32 AA chassis D9 port 8, the last "IN29-31," spigot of this AA chassis that supports sush2a's ADC1. - 2025-03-11_SUS-C4_PR3OplevMove_U32_AAChassis_After_3.jpg shows that this U32 AA chassis is serial number S1202340
Proof that (after we restored the alignment offsets at the M1 stage) PR3 optical gross function has returned. From the trends alone, I see that - the pitch signal is a bit noisier, maybe 0.1 [urad] more RMS. - the yaw signal is drifting slowly at a super small slow 0.02 [urad/minute]. The total SUM of the QPD segments have returned to the identical value tho. Will gather more data, e.g. ASD, to confirm if, and at what frequency, the performance is worse in pitch. Will wait patiently in yaw to see if the trend is something interesting or some transient that doesn't matter. I suspect that this change in character won't matter at all. Recall we DO NOT use the PR3 optical lever for any controls, only for monitoring and driven characterization.
Here's a look at the amplitude spectral density of the PITCH and YAW signals before and after the change.
In short: No concern -- the optical lever performance is equivalent as before
Also -- hidden beneath the comparison of
"read out by U11 AA chassis, ADC0 of sush2b, then shipped over to sush2a via IPC to be processed by PR3 model"
vs.
"read out by U32 AA chassis, ADC1 of sush2a, directly processed by PR3 model"
is that the "after" time period is during maintenance day when site-wide sensor correction is turned OFF.
So, the only substantial change in performance (and the increase in RMS I mentioned in the above LHO:83290) is in PITCH but it's because sensor correction is now off, vs. the before data both in the trends and the reference traces here where it was on.
(Good job sensor correction!)
Also in pitch, there's a bit of broadband increase in noise between 5 and 20 Hz, but this may be where the optical lever QPD is ADC noise limited. But also, a slight increase in noise doesn't really matter -- because the optical lever is much noisier compared to the real motion of the suspension. Even during driven measurements, we struggle to get coherence in this region.
There're some minor improvements in character of sharp features in both pitch and yaw above 10 Hz.
This lock loss from 15 hours ago had a rather large ETMX glitch that caused the lock loss. Upon returning to low noise, the violins were rung up. There was no earthquake during that time, but there was a lock loss from Resonance [410] during reacquisition. The violin modes that were rung up, are still damping ~15 hours and two lock reacquisitions later. I'm not sure if the lock loss itself caused them to ring up, or the fall from the Resonance state.
TITLE: 03/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: SEISMON_ALERT
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.26 μm/s
QUICK SUMMARY: Locked for 3 hours, two relocks overnight. Violins are elevated. The range has been slowly decreasing from the start of the lock. No alarms, calm environment. PEM magnetic injections are running at the moment to start off this maintenance day.
Workstations were updated and rebooted. This was an OS packages update. Conda packages were not updated.
TITLE: 03/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 9mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.26 μm/s
SHIFT SUMMARY:
I started my shift with H! locked and observing.
H1 dropped from observing, for a few minutes while the SQZ_man cycled throught its locking states. It returned to obsering automatically. alog 83281
Lockloss caused by the ETMX glitch, but it wasn't caught by the lockloss tool. alog 83282
Relocked without an Initial_Alignment.
H1 has been locked for 3.5 hours.
LOG:
no log
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 6mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.25 μm/s
QUICK SUMMARY:
Lockloss at 00:14 UTC
Unsure of what happened here. No sign of ground motion, wind, Pis, or SUS saturations.
There is a small ETMX Glitch on the lockloss page, but it is below the threshhold to trigger an ETMX glitch flag.
H1 Returned to Observing at 01:35 UTC
J. Freed
This is the summary page for the investigations at LHO into the First Stage BOSEM damping contributions to DARM. PR3 shows the strongest contribution to DARM by about a factor of 10 below DARM between 8Hz - 25Hz. ETMX and ETMY shows cotributions to DARM by a factor of 20 between 10Hz - 14Hz below DARM. SR2, SRM, and PR2 shows strong contribution between 7Hz - 12Hz by factors between 4 to 10 below DARM. Where as BS, ITMX, ITMY shows little to no contributions.
This is a summary of the work done previously for BS, ITMX, ITMY, PR2, PR3, PRM, SR2, SR3, SRM, ETMX, and ETMY. Starting with PR3, data was take with excitation gains of 300 ontop of the 600 gains to help check against any noise gained independant of excitation during data collection. This summary page only uses the 600 gains however as extra data was not collected for all suspentions.
The plots and code are located at /ligo/home/joshua.freed/bosem/sum/scripts. I used the code located under /ligo/home/joshua.freed/bosem/sum/scripts/osem_budgeting.py to produce the sum of all contributions as well as the individual plots.
Below are the graphs showing the estimated contributions from each bosem on each suspension:
TITLE: 03/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 13mph Gusts, 7mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.27 μm/s
QUICK SUMMARY:
H1 is currently Locked for 1 Hour and 20 minutes.
All systems seem to be opperating well.
I expect to be Observing until Maintenance tomorrow morning.
SQZ_manager dropped to LOCK_PMC[10] at 23:56 UTC, and came back 23:59 UTC.
TITLE: 03/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY:
Maybe 2hrs of Observing today, with locking at the start, getting to Observing a few minutes, dropping out for Commissioning, observing for a few minutes, then a lockloss due to a power supply dying at EY and then getting back to observing!
LOG:
Attached are two examples where it seems that ALS losses lock after the ESD linearization hits its saturating limit, there are several more examples like this.
With the linearization on, we measured the transfer function from drivealign L out to LL master out to be -2.3. Taking into account the gain of 0.25 in the eul2esd matrix, we would need to add a gain of -9.2 in the drivealign matrix to try locking ALS without the linearization.
I've added in lscparams use_ESD_linearization, which is set to True right now to keep things the same as they currently are. I've added an if statement for this in the ALS_DIFF guardian that will set the ETMX_L3_DRIVEALIGN gain to -9.2 if it is set to False.
The linearization used to be turned on in ISC_LOCK's PREP_FOR_LOCKING state, but TJ commented several things out of this state that were redundant with things that SDF would take care of when safe.snaps get reverted. Since we want to use a flag to determine how this is set, I've put it back into PREP_FOR_LOCKING that checks the flag in lscparams.
Sheila, Mayank, Camilla
The SQZ ang servo has been off since Feb 18th 82891. Today it was turned back on in sqzparams.py and with SQZ_ANG_ADJUST nominal state is now ADJUST_SQZ_ANG_ADF. We expect this to work better than in 82891 as we adjusted H1:SQZ-ADF_VCXO_PLL_PHASE to 25deg so that the AFD H1:SQZ-ADF_OMC_TRANS_SQZ_ANG error signal is in a linear range where our best SQZ is. This should improve the squeezing and keep it more stable.
Range was better last night with the SQZ angle servo keeping the squeezing tuned around 350Hz (yellow BLRMS), plot attached.
I assembled the 45MHz WFS unit in the optics lab. Assembly drawing: D1102002.
BOM:
I confirmed that the baseplate and the WFS body are electrically isolated from each other.
There were many black spots on the WFS body (2nd pic) as well as the aluminum foil used for wrapping (3rd pic). It seems that this is a result of rubbing of aluminum against aluminum. I cannot wipe it off but this should be aluminum powder and not some organic material.
QPD orientation is such that the tab on the can is at 1:30 o'clock position seen from the front (4th pic). You cannot tell it from the picture but there's a hole punched to the side of the can.
Clean SMP - dirty SMA cables are in a bag inside the other clean room in the optics lab. DB25 interface cable is being made (or was made?) by Fil.
This WFS Assembly (D1102002) has been given the dcc-generated Serial Number of: S1300637 (with its electronics installed & sealed with 36MHz & 45MHz detection frequencies). As Keita notes, this s/n is etched by hand on the WFS Body "part" (D1102004 s/n016).
Here is ICS information for this new POP WFS with the Assembly Load here: ASSY-D1102002-S1300637
(NOTE: When this WFS is installed in HAM1, we should also move this "ICS WFS Assy Load" into the next Assy Load up: "ISC HAM1 Assembly" (ICS LINK: ASSY-D1000313-H1)
Tested the in-vac POP_X sensor in the optics lab:
All electronics tests passed! We are ready for installation.
After testing in the lab, the sensors are working as designed, outputs are clean. We reinstalled the BSC1 temperature sensor but left it floating (not attached to BSC1). The BSC3 sensor we isolated from BSC3 with a thermal pad, and the power supply was isolated from the pier it is resting on. This is an effort to remove ground loops on these systems. Will revisit next week.
M. Pirello, F. Clara
After review of the data over the week, we saw a marked improvement in temprature information so we reapplied the BSC1 sensor to the chamber along with a thermal pad to maintain electrical ground isolation. We also isolated the power box for both supplies.
M. Pirello, F. Clara, D. Barker