As part of installing a third DAQ framewriter I have written python code to generate a new DAQ Detail MEDM. It is launched by the DETAIL button on the CDS Overview (see attached).
Note that while FW2 is being tested its entry is a placeholder. When FW2 is put into production, the frames from all three framewriters will be checked to ensure they are identical.
The only difference between the old and new MEDM is that the new shows when the framewriters are actively writing their frame files to disk (the BUSY flag).
At 17:40:57 Wed 23apr2025 PDT (GPS 1429490475) some corner station long-range-dolphin IPC receivers got a single receive error from h1susetmx and h1susetmy senders. This is one error in the 16384 packets received in that second.
The 6 receivers in h1oaf and h1calcs are the only receivers of the h1sus[etmx,etmy] senders but they are not the only receivers of channels being sent from h1sus[ex,ey] frontends (h1sus[etmx,etmy]pi sends to h1omcpi). Nor are they the only receivers of signals coming from the end stations; h1lsc and h1asc receive channels from h1isc[ex,ey].
Because these receive errors were at the same time and symetrical between the two end stations, a glitch in the cdsrfm system is suspected.
I have added this event to FRS32032, this is a generic end-station senders, CS receivers ticket now.
TITLE: 04/24 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: MAINTENANCE
Wind: 3mph Gusts, 1mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
IFO is in PLANNED ENGINEERING for the VENT
Today's planned activities:
Work safe!
All 8 pre-filters were swapped out at End-Y AHU-1. Of the 2 Supply Fans, SF-1 was running. The 8 pre-filters on the other side (SF-2) where it wasn't pulling air were still in great condition and left alone. Also, all 8 pre-filters were swapped out at End-X AHU-1. Same situation as E-Y. AHU-2 side was not swapped out. The pre-filters still looked near brand new. Another note worth mentioning is that of the 16 pre-filters that were replaced, the filtration level of each was MERV-12 or MERV-11. They were replaced with 16 new pre-filters that are all MERV-11. This will likely slightly increase the air volume flowing through the unit.
4-22 (Tuesday) activities: - After reaching ~1.3E-6 Torr at the corner, GV2 was opened (the corner was valved together with the X-manifold), that brought down the pressure to ~9E-7 Torr in ~2 hours - The aux carts from GV5, BSC8, and HAM4 have been detached, 2 of them have been staged at HAM1/HAM2 as a preparation for the pumpdown of the annulus volume 4-23 (Wednesday) activities: - The stiffening frame for the 1000 amu RGA is being built - The filter elements were replaced in the EX clean air supply, and it is now running for 24 hours, with a vent valve open in the VEA
TITLE: 04/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
Productive day in which the following tasks were done:
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 14:52 | FAC | Kim | LVEA | N | Technical cleaning | 16:10 |
| 15:09 | FAC | Nellie | LVEA | N | Technical cleaning | 16:10 |
| 15:24 | VAC | Jordan | LVEA | N | Purge Air Checks | 15:57 |
| 15:58 | SEI | Keita, Jeff | Optics Lab | N | SPI Work (Keita out 1814) | 19:00 |
| 16:02 | Jordan, Christina | LVEA | n | Capital i Inventory | 16:24 | |
| 16:04 | SEI | Jim | LVEA | n | HAM1 work | 17:48 |
| 16:05 | IAS | Jason, RyanC | LVEA | n | HAM1 IAS | 17:34 |
| 16:11 | TCS | Camilla | LVEA | n | Looking in the TCS cabinets | 17:47 |
| 16:11 | FAC | Kim, Nellie | EY, EX | n | Tech clean | 18:26 |
| 16:11 | SEI | Mitchell | LVEA | n | HAM1 work | 17:49 |
| 16:25 | PCAL | Tony | Pcal Lab | N | TSB Work | 18:20 |
| 16:33 | FAC | Randy | LVEA | N | HAM1 and 3IFO Craning | 18:34 |
| 17:12 | VAC | Travis | EX | N | Mech room work | 20:00 |
| 17:31 | FAC | Tyler | MX, MY | N | Determination slab measurement | 21:30 |
| 17:51 | VAC | Janos | LVEA | N | Walkabout | 18:28 |
| 18:43 | PCAL | Tony | PCAL Lab | n | Updating software | 19:19 |
| 18:44 | EE | Fil, Daniel, Betsy, Marc | LVEA | N | HAM1 Cablework | 19:17 |
| 18:49 | FAC | Richard | LVEA | N | Walkabout | 22:38 |
| 19:09 | FIT | RyanC | YARM | n | Walking | 19:42 |
| 19:36 | FAC | Randy | LVEA | N | Craning | 20:18 |
| 19:42 | SEI | Mitchell, Jim | LVEA | N | HAM1 Work | 22:57 |
| 19:51 | EE | Marc | LVEA | N | HAM1 Cabling | 21:56 |
| 20:07 | SUS | Betsy | LVEA | N | HAM1 Work | 21:50 |
| 20:07 | EE | Daniel, Fil | LVEA | n | Cabling HAM1 (Fil out 13:15) | 21:56 |
| 20:10 | FIT | Oli | XARM | N | Health Maintenance Check (Walk) | 20:44 |
| 20:38 | VAC | Janos & Vendor | LVEA | N | LVEA Walk through | 21:06 |
| 20:50 | VAC | Jordan, Gerardo | LVEA | N | RGA Frame Build | 23:28 |
| 21:06 | VAC | Janos | MX, MY, EX, EY | N | Measurements | 03:05 |
| 21:57 | EE | Marc, Fil, Daniel | LVEA | N | ISC Work | 03:56 |
| 22:23 | TCS | Camilla, Matt, | LVEA | N | Looking at TCS Cabinet | 22:57 |
| 22:55 | PCAL | Tony | PCAL Lab | y(local) | Unshuttering the shutters | 22:59 |
Jonathan, Dave, We replaced the hardware that is running h2daqfw2 today. This was done to put in a system that had more memory. We pulled a spare daq unit out of the test stand (most recently named x6dc0). While doing that we swapped the memory with a broken daqd system, so that the new h2daqfw2 now has 256GB of ram. The system is up and running again, I'm tracking the setup in puppet so that we have a low rebuild time. This was done to support investigating differences between the frames generated on h1daqfw[01] and hqdaqfw2. I need to be able to run modified versions of daqd to see some of the internal state that is not exposed to be able to understand and fix differences in encoding of the frames. When I ran daqd on the old hardware, it ran out of memory, even after reducing buffer sizes.
After finishing initial alignment this morning, Mitch and I wrapped up the upgrade of the ISI to A+ spec. The last parts to go on were the vertical stops for the new .25mm vertical CPS and the vertical St0 L4Cs. All the sensors look live now, I will take some more detailed data later. Last pieces to be installed will be some spring tuned mass dampers that have been waiting for me to measure in the staging building for a couple weeks now.
Tomorrow, I'll help with the cable routing up the ISI, and ISC can start re-installing the optics.
Marc Fil Daniel
We finished the cabling work for the ISC cables between HAM1, ISCT1, and ISC-R1/2/4. This includes re-labeling of all cables that had no or misleading labels.
Preeti, Gaby, Tabata, Debasmita
Summary:
We calculated the duty-cycle of L1 and H1 in O3, O4a and O4b winters (Nov, Dec, and Jan) on each day and plotted with the median of microseismic ground motion in 0.1-0.3 Hz and 0.3-1.0 Hz. The duty-cycle was modified by removing earthquake times (ground motion in the 0.03-0.1 Hz band above 150 nm/sec) from lock duration and day duration.
Conclusion:
After the ITMY transfer functions I posted Monday(84031), there was some discussion by Edgard and Brian about an extra zero on M0 between L and P ~0.27Hz that maybe seems like it's there when the ISI is isolated and now there when the ISI is in Damped (although he later decided that maybe that didn't make much sense 84068). I took some ITMY M0 transfer functions yesterday afternoon with the ISI in Isolated, to check out any possible correlations there.
Looking at the comparison between Monday and yesterday's measurements(pg 13-14), where the only difference was the ISI in Damped vs Fully Isolated, respectively, that difference alone doesn't seem to account for the disappearence of the extra zero. This further backs up the conclusion Edgard came to this morning.
Data (/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/)
2025-04-22_2300_H1SUSITMY_M0_Mono_WhiteNoise_{L,T,V,R,P,Y}_0p01to50Hz.xml
In SVN as r12271
Results (/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Results/)
2025-04-22_2300_H1SUSITMY_M0_ALL_TFs.pdf
In SVN as r12272
Comparison (/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Data/)
allquads_2025-04-23_ISI-DampedvFullyIso_Apr212025vApr222025_ALLM0_TFs.pdf
allquads_2025-04-23_ISI-DampedvFullyIso_Apr212025vApr222025_ALLM0_ZOOMED_TFs.pdf
In SVN as r12274
Wed Apr 23 10:08:22 2025 INFO: Fill completed in 8min 19secs
There is a ladder section along the X-arm access road between the mid- and end-stations.
The second attached photo was taken looking toward the mid-station from the direction of the end-station.
Thank you Rick. Facilities is aware of the ladder. It was there for easier access during "Tumblegeddon" a couple years back. It got buried at some point during that time. I just recently found it again while tumbleweed mulching recently. We will do something with it ASAP. Thank you for the reminder.
Marc Daniel
One of the coax cables shows a discontinuity at the feedthrough, ISC_RF25-B/3. This is the coax for ASC-REFL_B 9MHz chn 4 (Q4 RF Low). This is feedthrough D1-1D1. We can see the signal going though the pig-tail but terminating at the feedthrough. This could be an issue of the in-air pig-tail or the in-vac cable at the feedthrough side.
Typical In-vacuum RFPD ASC Wiring Chain for aLIGO: https://dcc.ligo.org/LIGO-D1300467
O5 ISC/SQZ Wiring Diagram: https://dcc.ligo.org/LIGO-D1900511
TDR Plot of the cables analyzed.
Found faulty pin on one of the Accu-Glass 5-way coaxial pigtails. Pin 3 seems to have been improperly crimped/seated/damaged. See attached picture. The Pigtail cable was replaced. Initial testing shows all pins are now correct lengths. The cable with issue was ISC-RF25-B/3.
Edgard, Brian.
Following up on the fits for the SR3 estimator. I ran the plotall scripts on the transfer functions we took last Friday [see 84003]. Then ran the attached code to fit the transfer functions.
Figure 1 shows the ISI-M1 fitted transfer function. The Q-factors for the fit were tweaked by hand so I could get a decent fit. The exported M1 to M1 transfer function is shown in the second attachment. I decided it should have the same poles as the ISI one, and the gain was fit so the estimator matches the high-frequency behavior of the measured transfer function. The choice to share poles is because the math indicates that it will lead to some potential modeling errors cancelling out.
The pole information for the two filters is:
Pole Damping Frequency Time Constant
(rad/seconds) (seconds)
-4.38e-02 + 6.38e+00i 6.86e-03 6.38e+00 2.28e+01
-4.38e-02 - 6.38e+00i 6.86e-03 6.38e+00 2.28e+01
-7.64e-02 + 1.44e+01i 5.30e-03 1.44e+01 1.31e+01
-7.64e-02 - 1.44e+01i 5.30e-03 1.44e+01 1.31e+01
-2.97e-02 + 2.13e+01i 1.39e-03 2.13e+01 3.37e+01
-2.97e-02 - 2.13e+01i 1.39e-03 2.13e+01 3.37e+01
And the zpk strings (in MATLAB format) are:
ISI to M1:
zpk([-0.068+20.398i,-0.068-20.398i,-0.099+11.454i,-0.099-11.454i,0,0],[-0.03+21.271i,-0.03-21.271i,-0.076+14.435i,-0.076-14.435i,-0.044+6.384i,-0.044-6.384i],-0.75)'
M1 to M1:
zpk([4745.079,-0.089+8.28i,-0.089-8.28i,-0.113+19.058i,-0.113-19.058i],[-0.03+21.271i,-0.03-21.271i,-0.076+14.435i,-0.076-14.435i,-0.044+6.384i,-0.044-6.384i],-0.015)
I did the fits by using the spectrumest function in MATLAB (which is sadly not available in 2019a). The long term plan is to switch to one of the many python fitting tools that people like for the fits. The code is attached to this logpost for bookkeeping
I added a script to
... SusSVN/sus/trunk/HLTS/Common/FilterDesign/Estimator/
that uses autoquack to add the fits to the Foton file for H1 SR3.
The script is named
make_SR3_yaw_model.m
and it uses the fits mentioned in the logpost above, which are contained in the same folder, as
fits_H1SR3_2025-04-21.mat
The changes are current to the sus svn under revision 12277.
These filters have been loaded into the SR3_M1_YAW_EST_MODL_SUSP_Y_2GAP and SR3_M1_YAW_EST_MODL_DRV_Y_2GAP.
Attached are the plots that came up when I ran the matlab script that loaded them in, along with the log message that was created and the coeff diffs.
Small modification that will not affect the estimator test, so it is here for bookeeping.
I didn't clean up the zpk for the M1 to M1 transfer function, so it has a high frequency zero that is due to floating point errors in my fit.
the real zpks should be:
ST1 to M1
'zpk([-0.068+20.398i,-0.068-20.398i,-0.099+11.454i,-0.099-11.454i,0,0],[-0.03+21.271i,-0.03-21.271i,-0.076+14.435i,-0.076-14.435i,-0.044+6.384i,-0.044-6.384i],-0.75)'
and M1 to M1
'zpk([-0.089+8.28i,-0.089-8.28i,-0.113+19.058i,-0.113-19.058i],[-0.03+21.271i,-0.03-21.271i,-0.076+14.435i,-0.076-14.435i,-0.044+6.384i,-0.044-6.384i],71.17)'
I have uploaded the correct ones to the HLTS/Common/FilterDesign/Estimator with today's date (2025-04-23), svn revision 12279.
That filter change has been loaded in
Here's a quick summary of the Estimator installation from this week (Edgard, Oli, Jeff K, Brian L)
slides with basic info: T2500082
FRS ticket 32526
Installation alogs
Infrastructure installed on HAM2/PR3 and HAM5/SR3, style updates to model, MEDM linked to sitemap - alog 83906
Tools installed in Estimator folder in the SUS SVN alog 83922
We updated the OSEM 10:0.4 calibration filters, but only on SR3 and PR3. alog 83913
Damping filters installed - alog 83926
Tested the fader switch - alog 83982
Designed and installed a blend for SR3 Yaw (DBL_notch in the first filter bank) - alog 84004
Created a new OSEM calibration script - alog 84005
(Edgard is thinking about a general version of this using Python, that is still TBD)
Fitting is well underway, but isn't done yet.
We made much more progress than we expected - thanks Oli and Jeff for all the help. It's not quite ready to go, we need to install the TF fits for the model.
We might have actually been able to test, except the temperature changes from the pumpdown were causing the SR3 optic to move, and the TFs were not very stable. Edgard is working on a log to document this. We have good fits for SR3 yaw taken Friday morning, and we might just try these remotely with Oli's help. We do plan to get a clean set of TFs in a few days when things have stabilized.
-- notes for next steps, thanks to Sheila for this --
We plan to leave the SR3 overall yaw damping gain at -0.5. This means we'll set the 'light damping' to -0.1 and the gain in the estimator to -0.4. Edgard used -0.1 for the fitting, but he notes that the Q's are pretty high so we may need to revisit this.
SR3 oplev channels are : H1:SUS-SR3_M3_OPLEV_{PIT,YAW}_OUT_DQ
Some interesting alogs about the impact of changes to SR damping: alog 72106 and 72130
Elenna's PR3 coherence plots: alog 65495
I've attached a quick spectrum of SR3 yaw and pitch on M3 as seen by the optical lever. It's odd - the yaw looks very lightly damped - but the IFO was in observe. You can not see real motion above the 3.4 ish Hz yaw mode (it should be falling faster that 1/f^6). You might be seeing real motion between the peaks though - and we can use that (peaks at 1, 2.3, 3.4).
(environment was pretty quiet - BLRMS - EQ is 40-100 nm/sec, microseism is 200-400 nm/sec, wind speed below 1 m/s, anthropogenic is 20-30 nm/sec. It's 3 pm Saturday afternoon, local time. )
I've added 2 more plots. The first is to check that the Y damping is on, and it seems to be. This is a spectrum of the Y osem signal. Ignoring seismic input (which is completely fair), the signal here should just be yaw_osem_noise * (1/1-G) (the minus sign assumes you get all the loop gain signs directly from the control). You can see dips at the resonances, so the loop is on, and has some gain, but not much at the 1 Hz mode, more at 3.4 ish Hz. I've also added my yaw noise reference from G2002065 - you can see here that the noise is a bit larger than my estimate above 1 Hz.
LDVW shows that the gain on the M1_DAMP_Y control was already turned down to -0.5 at this time.
Here is a comparison of the spectra of three channels that can be used to monitor the performance of the estimator. We compare the motion when the M0 Yaw damping loop gain is at -0.5, versus when it is at the -0.1 (which is what we are aiming for with the estimator). The equivalent estimator plots should look somewhere in between the purple and blue curves in the images attached.
- The first one is the OPLEV on SR3. If the estimator works, we should be able to see a difference on the mode Qs. The oplev should see that we are able to damp (or control) the modes to the same level as the -0.5 damping.
- The second one is the M1 OSEM spectrum. The closed loop spectrum dips at the resonances of the plant at -0.5 gain (because of the sensitivity function), so we should be able to see that the sensitivity (as seen by the OSEM) is different, but the OPLEV sees good control of the modes.
- The third one is the total drive on M1. We should see that the total drive around the resonances is similar to the drive we get with the -0.5 gain, but the total drive should decrease rapidly above 3 or so Hz. We will need a faster channel than the one shown in the last attachment.
The plan is to make a full list of channels to monitor in conversation with Oli and Jeff, then run a pilot test with the fits from 84041 later in the week.