FranciscoL, SheilaD, JoeB
In summary:
I regenerated the mcmc fit on report 20250327T160138Z at 5, 10 and 20 Hz, to compare how the mcmc model would change given different frequency ranges for the fit. We see that the residual of the measurement to the model is better as we increase the minimum frequency threshold. We think this is due to external effects, aside SRC, confusing the model.
We want to give more validity to our observations on alog 83592 -- that the sensing model at low frequencies is a good descriptor of the sensing function. On 83592, I claimed that the observed changes in the sensing function come from changes in SRCL detuning. This is backed up by a low residual on the measured/modeled sensing function. In today's alog, we evaluate how well the model describes the sensing function by (1) having a *low* residual and (2) decreasing the optical spring frequency.
The first three figures attached ('sensing_mcmc_compare_*Hz.png') are the sensing function plots generated by pydarm for measurement 20250327T160138Z. This measurement is not a representation of a calibrated interferometer, since we tuned the SRCL detuning (83585).
From the transfer function on the left, the green dots represent the measurement, the orange trace is the mcmc model from the measurement, and the blue trace is the mcmc model from the last validated calibration measurement (20250222T193656Z). The residual from the measurement to both models are plotted on the right, matching the colors of the respective models. We are interested in the change of the orange trace when we modify the frequency range of the fit.
Each figure has a pair of vertical lines denoting the limits on the frequency range used for the fit. I regenerated the measurement report for 05, 10, and 20 Hz for the minimum frequency. The maximum frequency at 1200 Hz was not changed.
For the residual plots, we see that the magnitude is largest when fitting to 5 Hz, and that the change between the 10 and the 20 Hz fits is negligible. For illustration purposes, I plotted the different sensing models, along with the measurement, together in the last figure (20250327T160205Z_compare_models). The phase plot is not the same as the plots given by pydarm due to missing factors. We see that the three models match above 30 Hz in magnitude.
For the optical spring frequency, we see a decrease from 2.19 Hz to 0.43 Hz when fitting to 10 Hz, and 20 Hz, respectively. This decrease on the SRC spring suggests that the model does not fit the sensing function well, below 20 Hz.
So, regenerating the sensing model shows that the model is good when we see anything above 20 Hz. But we see from the measurement that the SRCL detuning does change the sensing function at low frequencies. The model, however, cannot fit the data from the measurements at these frequencies. We have seen before (80267) that angle to length cross coupling influences the sensing function in the low frequencies. A scenario of cross coupling affecting the sensing function could explain why the model cannot fit the measurement.
Repeating the analysis on cross-coupling, as done in 80267, could improve the sensing function.
TIL; pydarm edition:
The approach that enabled me to regenerate pydarm reports, albeit messy, was to
Modify the pydarm_cmd_H1.yaml
that is in the report to be regenerated, in this case 20250327T160138Z. In particular, the mcmc_fmin
value.
Once the YAML file is configured, run
This command will re-run the calibration report, and, by using the configuration that lives in that directory, make a new model to the sensing function measurement.
TITLE: 04/25 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: 1mph Gusts, 0mph 3min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
IFO is in PLANNED ENGINEERING for VENT
Some planned tasks for today:
Work safe!
Jordan, Janos, 04-24-2025, ~15:00 The wire gaskets for VBO-C and VBO-D have been leaking continuously for a very long time. Lots of vendors have been contacted, and after a lot of unsuccessful tests, it seems that we finally found the good one manufactured by Torr Scientific (UK). This gasket is extremely annealed, butter-soft, needs super careful handling, but even after some suboptimal installation steps (mea culpa), it finally sealed a new chamber successfully. We tested it right after receiving (had a thriller with customs) with a new C+B chamber, pumped it down and tested on the same day. After the test, we let the pump running during the weekend just to see the ultimate pressure it can reach. They are still very pricey though, 193 GBP (= 257 USD)/pc., even in the case of purchasing 100 pcs., it's 147 GBP (= 196 USD)/pc. So, certainly not an optimal, long-term solution, but a good bridge between having nothing and manufacturing our own.
Good news! Let's take some detailed measurements (as possible), also how close they fit over the flange lip, etc. Will help us when we start fabrication in house.
Oli, Matt, Camilla
Late entry, Jim and I worked the last few half days to lace up all of the cabling for SUS, SEI, and IO/ISC in prep for the main reinstall of table components. Fil, some Richard, and I did preliminary ground loop checks on all SUS and IO/ISC cables so we have a handle on the situation before complicating with components. I routed cables on the table top in an attempt to be near where things plug in but also not in the way of landing objects. Further dressing and coiling will be needed after troubleshooting plugins with components as we go. Pics of the pre round of cabling.
Oli, Camilla
This morning we swapped the direction of HW1 so that it is facing the same as before. We also placed L2, M15, LSC POP A and ASC POP X although the diodes are not cabled up yet. They can be next week as Daniel confirmed chassis are powered off.
ASC POP X is new, the box is marked D1102004-v6 S/N 016 S1300637, ICS link. Have added this to the D1000313 BOM googledoc and HAM1 ICS assembly.
Tagging with EPO to document the process.
TITLE: 04/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
IFO is in PLANNED ENGINEERING for VENT
Productive day where most of the work was spent on HAM1 cabling, followed by RM1 install.
Of note:
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
14:39 | FAC | Kim | LVEA | N | Tech clean | 15:52 |
14:39 | FAC | Nellie | LVEA | N | Tech clean | 15:52 |
15:45 | VAC | Jordan | LVEA | N | Purge air checks | 16:03 |
15:45 | SUS | Betsy | LVEA | N | Cabling HAM1 | 18:59 |
15:52 | FAC | Nellie | H2 | N | Tech clean | 16:07 |
16:07 | SUS | Randy | YARM | N | QUAD Moving | 23:24 |
16:33 | SUS | Richard | LVEA | N | Cabling/H.O.R.S.E. | 17:03 |
16:50 | SUS | Mitchell | EX, EY | n | FAMIS tasks | 22:50 |
16:56 | SUS | Travis | LVEA | N | Cabling | 17:06 |
17:07 | FAC | Kim, Nellie | MY, MX | N | Tech clean | 18:51 |
17:53 | VAC | Jordan | MX, MY | N | Emergency Pump Survey | 18:38 |
17:53 | VAC | JaNos | MX,MY | N | Emergency Pump Survey | 18:37 |
18:23 | ISC | Camilla, Matt | LVEA | N | Measuring viewport heights | 18:54 |
18:39 | PCAL | Tony | PCAL Lab | N | TSA to France + stickers | 20:07 |
19:01 | SUS | Jim | LVEA | N | Cabling | 23:00 |
19:31 | FIT | Ryan C | LVEA | N | Respiratory and Perspiratory Regulation Test (Walk) | 20:04 |
19:56 | ISC | Matt, Rahul, Camilla, Oli | LVEA | n | HAM1 ISC installation | 23:23 |
19:59 | VAC | Jordan | MY, MX | N | Turbo Pump Checks | 22:50 |
20:00 | SUS | Betsy | LVEA, Opt Lab | N | Walkabout + Feed Through Cable Work | 21:56 |
20:03 | VAC | Travis | Opt Lab | N | Feedthru Cable Work after turning compressor off | 22:48 |
20:19 | VAC | Janos | LVEA | N | VAC checks | 20:28 |
20:41 | CDS | Fil, Dave | FCES | N | HAM8 Post Outage Glitch | 22:59 |
21:07 | VAC | Vacuum Convoy | YARM | N | Beam Tube Experiment Walkabout | 21:56 |
21:49 | PCAL | Tony | PCAL | N | Measurements and general lab affairs | 22:22 |
22:59 | EE | Fil | HAM1 | N | helping Rahul | 23:24 |
23:24 | SUS | Betsy. Fil, Rahul, Daniel | LVEA | N | RM1 Things | 23:40 |
Ibrahim, Dave:
RM1 exceeded its RMS motion limit, and 5 minutes later the HAM1 DACs were DACKILLed, stopping all h1isiham1 and h1hpiham1 drives.
We have bypassed RM1 and SEI-HAM1 watchdogs indefinitely for now.
RM2 started ringing up, so I've bypassed everything for HAM1 now.
Thu Apr 24 10:07:42 2025 INFO: Fill completed in 7min 39secs
Gerardo confirmed a good fill curbside.
Jennie Wright, Sheila, Keita, Camilla
Jennie has been working on modeling of our arm to OMC mode matching, and while she was looking for some distances we noticed a discrepancy between the as built numbers and the mode matching design. It seems possible that there was a mix up, where design documents call for a distance of 97cm between the OMC waist and OM2, and the as built distance is 97 cm between the OMC input coupler and OM2 (so, the OMC seems to be translated by 14 cm from where the mode matching design expected it to be). If we have the q parameter used in the design (ROC matched to SRM, beam size there is 2.1mm), this would introduce a 1% mismatch between the OMC mode and the SRC mode (the impact could be larger for a different q parameter). Note that the analysis done in 71145 was using the design distances, so we will want to revisit that. I've attached an a la mode script below.
Editing to add more information:
I initially did this with the design ROC for OM2, which is 1.7meters, which is also what is in Finesse. This results in an overlap for the design locations of 99.95% and 99% for the as built locations, with the as built waist location 12cm from the OMC waist location (there are differences in the other distances that partially cancel the 14cm difference between OMC input coupler and OMC waist location), and a waist size of 545um compared to the OMC eigenmode of 509um. In 71145 Keita says that the OM2 ROC is 2m cold and 1.75m hot.
If we change the OM2 curvature for the as built path to 2 meters, the overlap becomes 93.8%, and the waist location becomes 14.3cm from the OMC waist location, with a waist size of 649um. Using the hot ROC of 1.75m, the overlap becomes 98.5% and the waist is 563um 11.5cm from the OMC waist. So, if our q parameter was the design one at SRM, the error in OM2 curvature would be compounding the error in the OMC placement to make the mode matching worse. The single bounce measurements agree that the mode matching is worse with OM2 cold than hot, but the full IFO measurements are the opposite.
Summarizing distances:
T1200410 says we should have:
.yaml file, which is based on E2100383:
Camilla looking at edrawings (which agree with photos):
To compare the solid works to the photos we looked at D0901822 and compared it to OM3 photo and this photo of OM2 when it was a tip tilt.
Using the beam q from table 1 of T1200410 for just after SRM, and propagating it through the distances from T1000317, gives an overlap with the OMC waist of 99.96%. Adjusting the SRM to OM1 distance to agree with T1200410 gives 99.95%, so that difference between the two design documents isn't significant.
Here's a version of the script that I used to make the plot above. a la mode is a matlab beam propagation and mode matching code written by Nic Smith that is available here. If you download that in the control room it will give some errors, I have a copy of the directory I use in matlab2019a in the control room here
Morning dry air skid checks, water pump, kobelco, drying towers all nominal.
Dew point measurement at HAM1 , approx. -42C
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.
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