During the annual inspection of the LN2 tanks, we found that the LN2 tank for CP3 had a high vacuum jacket pressure (110 mtorr), see alog 90283.
We placed an ISP500 on the pump out port to get the jacket pressure back below 10 mtorr, this took ~30 hours of pumping to go from 110 mtorr to 9 mtorr.
No other LN2 tank needed pumpdown.
Closing WP 13448
Keita K, Khanh V, Jennie W
Summary: JAC angular control loops work now. We had some set backs this morning and eventually had to change some wiring at the IOT1 table but we have re-measured the phasing, re-measured the sensing matrix and now locked the 4 asc loops.
We tried to get our loops to converge this morning but we were seeing not much change in the loop outputs for large WFS gains (40000 eventually) and then eventually we could not see the two loops we tried (DOF1_P which feeds back to pitch and DOF2_P which feeds back to JM1) makign any improvement to the JAC transmitted power even if we changed the sign.
Keita and I checked the JAC phasing with the template at userapps/ioo/h1/templates/dtt/JAC_WFS_phase.xml and after checking the phase of the TF between the JAC length servo error point and the wavefront sensor error signals he realised that some of these were phased with the wrong sign. I did not think to check these in our previous round of phase measurements last week.
As a check of the signs in the ASC loop we slewed the beam to different quadrants on WFS A and B using JM1 and realised that the degrees of freedom on WFS A were swapped. I found a mistake in the WFS A DC input matrix where pitch and yaw were swapped. This is now fixed and I double checked these input matrixes were correct for both WFS sensors and the WFS B DC screen.
Using our previous phasing template JAC_WFS_phase.xml we used the picomotors in front of each wavefront sensor to check the wavefront sensor quadrant response to the 8Hz length signal. That is, we checked which wavefront sensor quadrant showed the highest magnitude response at 8Hz to the QPD quadrant the beam was in.
Quadrants 1 and 4 in each wavefront sensor show a maximum response to the beam being in quadrant 1 and 4 respectively. Quadrants 2 and 3 appear to be mis-matched between wavefront sensor and qpd. This holds for both WFS A and WFS B.
Keita and I went to the IOT1 table and unplugged WFS A segment 2, the channel H1:JAC-WFS_A_I2_INMON went to 0. The same was true for segment 3 and the channel H1:JAC-WFS_A_I3_INMON. This test was the same for WFS B also.
Since the table feedthrough was the easiest place to swap cables (it is hard to reach the back of the demod boards in the rack so we can't easily do it there) we went ahead and swapped them here.
Checks using the previous method with the 8Hz signal on the length and slewing the beam only into one quadrant of the WFS showed that this cable swap has fixed things.
I want to go back later to try and trace this DOF flip down, wondering if it might be in the jac simulink model or in the demod board connections.
After this swap we re-tuned the WFS phasing after recentering the WFS (with JAC locked). Then we re-measured the input matrix using the method from this (alog #91189), except we did not divide the matrix by the largest coefficient.
Keita and I checked over filters that Sheila had put in for PZT and JM1 feedback. We changed the poles at 0.8 and 0.85 HZ in pitch and yaw to be 0.83 Hz to match the zeros in the JM1 locking filters. We also tuned the gain of the exitsing filters to give a UGF of around 0.1 Hz.
After loading the new coefficients Khanh and I closed each degree of freedom in the ASC in turn. We kept tuning the gain up as the loops were converging very slowly. The final loop settings are shown here.
Here is the ndscope showing the loops converging and making the transmitted power higher.
(Jordan, Travis, Gerardo)
We removed and replaced the AIP for BSC6, no real complications while doing the work. However the joint at the AIP and the isolation valve has a tiny gap towards the bottom, we started pumping down on the system and it appears to be a solid union, we will go and visit tomorrow and see how the pressure is doing. On a side note we did find a flex metal hose that has a leak, it has been removed from circulation.
Went through and consolidated some sdfs for the output arm suspensions. These were for SR2, SRM, SR3, OFI, OMC, OMs, and FC1. Some suspensions had had their sdfs accepted while in SAFE, so I reverted those changes since they were all really just OFFSETs being off and OPTICALIGN sliders being off.
Jenne, Wanda V, Gizem K
Wanda and Gizem arrived today to help set up the DAS (distributed acoustic sensing) system that we're going to test for a few months. We're borrowing DAS interregators from EarthScope, and using spare dark fibers that go down the arms. The DAS will measure strain changes in the fibers. We've got 2 models of DAS interregator on site, however only commissioned one today. Both models are eye-safe, and have been registered with the LHO LSO.
Since we need to connect to the fibers that are buried along the inside of the arms, the interregators are set up in the MSR close to the fiber junction box.
Fil did the actual connection to the LIGO fiber box, connecting some short 10m fibers that Wanda brought. We're using fiber #24 on Xarm (the fiber junction box calls this Right) and fiber #24 on the Yarm (the junction box calls this Left). Gizem took OTDR (optical time delay reflectrometry) measurements of each of our 4km fibers (one on the Xarm, one on the Yarm). The reports are attached here. One of the connectors (likely at the junction box) on one of the arms is a little lossy (0.6 dB loss), but since it's the junction box we're just going to live with it. Also, one of the splices at the midstation is better than the other (I think it's the Yarm that is better). More details are in the attached pdfs from the OTDR measurements.
We elected to just use rack 120V, rather than the UPS 120V, since we don't have long enough UPS-specific power cables. The power here on site is plenty good quality for the DAS.
We watched the data live on the monitor that is set up with the interregator in the MSR, and indeed it's working! We're going to leave it running overnight and have a look tomorrow at the data, particularly to see the quiet time in the middle of the night.
The attached photo is of the setup we've got on the far side of the MSR. The black case is the Febus DAS interregator, and we've got a 21 TB hard drive attached to collect the data. The fibers go up in the overhead tray, then down to the junction boxes which are at the very top of that first rack.
Tomorrow we will start work on the following to-do items:
Elenna, Oli
We spent some time figuring out SDFs for the BBSS. It should be all good to go.
A couple of notable channels that will need to be figured out at some point are:
I've attached a pdf with the full list of sdf diffs that we accepted. The notable channels listed above are highlighted as * and **
WP 13455 and prep for 13457.
Dave has been labeling machines and adnico cards. This will help us put fibers back in the right place after we disconnect them as part of the upgrades tomorrow.
I added the new IPC switches to the DNS today. The switches are staged in their respective buildings with all the optics. Their config has been updated to use the production logging, network time, and to allow polling from our network management host.
We got all the ethernet cards with the proper 1/2 height adapter and added the required optic.
We brought in a W3323 systems from the test stand and staged it in the MSR this will become the new h1seih23, as we need to have another core available for the ethernet IPC. I updated the BMC address so that it can be remotely administered on the production network.
Dave has been to the end stations with Tony to stage equipment and help finalize layouts and plans.
We had a plan review meeting this afternoon.
Dave will probably add some more notes tonight after checking on the SDF status, filter status, and model build status.
Looking at SDFs, on Feb 20th of this year the IMC input offset was changed from -0.38 to -0.07, but not SDF'd. I don't find anything in the alog from that date that would indicate this was an intentional change. For now I will revert the change, but we can keep this in mind, or perhaps change it back if someone remembers doing this intentionally.
Ryan C, Rahul
In preparation for our second replacement of the PSAMS, we have taken SUS ZM5 out of HAM7 chamber and staged it on the table next to it. We took the bottom stage PSAMS out of the suspension cage - this unit has wires shorting inside the mirror housing.
Tomorrow morning we will start replacing it with the unit CIT has shipped us - which was originally installed in ZM5 (LHO) but broke down two weeks ago (Strain Gauge wire leads got loose inside), then got fixed at CIT and re-shipped to us with 65 in-lb torque.
Today I went to check the SDF diffs in the ASC model, and noticed some of the anti-whitening settings were different for ASC-POP_A, ASC-POP_B and ASC-AS_C. Tony directed me to a time when he had checked and ensured the anti-whitening settings matched the whitening settings for all diodes.
However, Keita had changed the settings on those three diodes in this alog, just for BBSS alignment purposes during the vent: 90656.
I adjusted the whitening/anti-whitening settings on the three diodes to be back to the usual settings, which cleared SDF differences.
I also changed a ASC-POP_X NSUM normalization value, which was an arbitrary number from a long time ago when the diode was an air diode, but is likely no longer correct now that it is in-vac. This means that if you trend ASC-POP_X_DC_NSUM, you will see a large change in this diode around this time, due to the fact that we are no longer normalizing by 407.
The remaining ASC SDF diffs are due to the guardian or temporary commissioner changes we do not need to save.
Betsy recommended confirming the status of PR2's M2 and M3 transfer functions to make sure there isn't also a mistake with their feedthrough cabling, and I can confirm that PR2 is cabled up correctly.
I had checked PR2 M2 to M2 and M3 to M3 last week while troubleshooting MC2 but they had bad coherence so I just retook them with better coherence to double check and they look llike they should.
Data
M2: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PR2/SAGM2/Data/2026-07-27_2050_H1SUSPR2_M2_WhiteNoise_L_0p02to50Hz.xml
M3: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PR2/SAGM3/Data/2026-07-27_2100_H1SUSPR2_M3_WhiteNoise_L_0p02to50Hz.xml
r13085
Camilla, Rahul
SUS ZM2 in HAM7 chamber needed a pitch offload since it was using up a lot of DAC output. This morning we went to HAM7 chamber and at first confirmed the beam alignment and its position on the irises. Then I entered in HAM7 chamber and locked the suspension and unlocked the pitch adjuster screw. At first I gave it a full 1 turn anti-clockwise making ZM2 pitch down (and then unlocked the suspension) and Camilla confirmed that the alignment looked better but perhaps we overshot by a small amount. I retracted by 1/4 turn (thus making 3/4 turn anti-clockwise in total) and then the beam looked good on the iris. Before exiting the chamber I locked the screw for pitch adjuster and checked if all EQ stops were set free from the suspension chain.
Finally Camilla adjusted the alignment sliders on ZM2 for fine tuning it.
I took a quick chamber side transfer function measurements and the suspension was found to be healthy.
While I was fine tuning the alignment after this offload, I realized that the PSAMs setting was wrong. It appears that while this ZM2 work was happening that the ZM2 strain gauge reading has been shifted. We still have the same ΔV of 5V but the range used to be 1.2 to 6.2V plot and now is 4.6 to 9.6V plot. CIT has possibly seen this before in T2300426 but the effect was less.
Our nominal was 3.15V before, now I'm assume it should now be 6.55V (4.6V + (3.15V - 1.2V)). We will confirm this with beam scan measurements in chamber.
Ryan and I went to ZM2 PSAMS strain gauge at 6.55V and took data in 2 similar locations to in 91142. The beam size lis very similar to expected so we think ZM2 is fine, just the strain gauge now has an offset. Will look at the data in more detail tomorrow.
Took ZM4,5,6 to SAFE.
Accepted some TCS HWS settings, turned the EY enclosure lights off via medm (already off on table) , unmonitored the CHETA flipper. Attached.
Stil have more SQZ and CO2 to do....
CS_AUX Disabled then reverted picomotor settings, attached. Accepted ISCT6 AS Beam shutter (SHUTTER_M_THRESHOLD) from 1.2V to 2V as it's been this since ~February. Fast shutter (SHUTTER_G) offset accepted.
As a test, HAM3 Ry loop was switched to SUPERSENS6 blend, which includes a newly designed 30mHz CRS blend. It has been running stably for the last 20 minutes.
start_gps = 1468138518
note - to avoid confusing results I also turned off the CPS-DIFF loop
| UTC | Jul 15, 2026 | 08:15:00 | UTC |
As suggested by Huyen, attached in pdf1 is the comparison with all hams remade, including HAM1, which is the only chamber in the vicinity of HAM3 that also has the fine CPS upgrade.
Jim asked to plot a comparison of the CPS Ry channe before/after, which is attached in the 2nd pdf.
Finally, there is a typo in all plots and figure names from the other comments - the blends between the CRS and the GS13 is at 800mHz, not 80mHz (thanks Michael for the catch), so the blend plots and noise budget plots were regenerated, and are attached below as reference.
The loops stayed stable overnight and have been running for ~12 hours.
The overnight data was analyzed (first pdf) and spectra of the GS13 and CRS Ry were compared with the data from last week wtih the CPS/GS13 400mHz blend on the Ry loop. The in-loop CRS shows a factor of 100 improvement in the 0.2-0.5Hz band between the two times (purple vs pink), and the GS13 is now self noise limited up to ~0.8Hz (compare dark blue vs light blue).
A comparison of the Ry dof between all HAMs is also attached in the second pdf as a reference.
A tilt noise estimate used to design the blends is shown in the third pdf. This estimate uses the 3 sensor noises (CPS, GS13 and the updated CRS noise model), as well as (estimated) tilt input, and the 3 way blend. The total platform tilt noise for the new blend is shown in the dark blue dash lines and compared with the in-loop CRS measured spectrum. The dash green line shows the estimate for the 400mHz previous blend, compared with out-of-loop CRS spectrum.
Note the 1-20mHz noise in the measured spectra is from windowing leakage (2582) rather than real tilt. I kept using the same Hanning window to be consistent with the reference data saved in dtt from last week. Eventually we should remake those plots in matlab (or dtt) with bmh windowing.
The blends were designed using Brian's script attached to T2200393 as a starter point. The CRS sensor response is inverted in the blend filter (the same way we do with the GS13). The installed blend filters (including sensor response, as opposed to the plot shown in the main alog above) are shown on the last pdf.
Next, we will assess how this improvement can help reducing the blend frequency in the horizontal loop.
The dtt template, blend script and blend filters are saved under :
/ligo/svncommon/SeiSVN/seismic/HAM-ISI/H1/HAM3/CRS/Templates/dtt/2026-07-25_CRS_Spectra.xml
/ligo/svncommon/SeiSVN/seismic/HAM-ISI/H1/HAM3/CRS/Scripts/make_crs_blends.m
/ligo/svncommon/SeiSVN/seismic/HAM-ISI/H1/HAM3/CRS/Filters/CRS_BLNDS_30mHZ.mat
The SEI_ENV automation guardian transitioned back HAM3-ISI Ry loop to the nominal blend (SUPERSENS4) before an earthquake on July 26 at 01:51 UTC
Analysis time for the CRS in-loop is between July 25 08:15 UTC and July 26 08:51 UTC
I was excited, so I made a comparison of PR2 suspoint motion in pitch and length during Arnaud's test time, which encompasses both the CRS change made here and the CPS improvement made in 91113.
For a comparison time I went back roughly a year ago to August, to a time when we were in observing. Hopefully the seismic environment is fairly similar.
The attached plot shows pitch on the left, length on the right, along with the RMS. The channels are calibrated into rad and m respectively.
Overall, the pitch is the most straightforward: between 0.1 to 1 Hz there is up to a factor of 25 reduction in the motion, and between 1 and 10 Hz roughly a factor of 4 reduction. These plots purposefully don't show anything above 10 Hz because we don't expect improvement there, and we're still returning from the vent so there's lots of ambient noise which could be confusing.
Length has some weird features, which I'm not sure are attributable to the changes in the sensors and blends, but also shows improvement between 0.1-10 Hz.
As a reminder, PR2 is used to control the PRC alignment.
We been commissioning the CRS this week, so far we've done a tilt to tilt measurement:
Summary:
Made some adjustments to the CRS_TransferFunction code which generates the SensInv filter.
Filter is saved in : /ligo/svncommon/SeiSVN/seismic/HAM-ISI/H1/HAM3/CRS/Filters/ CRS_SensInv_Filter.mat