We are clipping on IM4 trans. I trended the position of IMs 1-3 over the past few months and it appears they moved significantly from their position before and after the vent. The t1 marker on these plots marks the approximate time that the positions changed which corresponds to the end of O4a and the start of the vent.
As a note, this means our PRG channel is untrustworthy right now.
The location mons on Hepi and the ISI suggest that thos have not moved, but IM4 pitch has a large shift.
I trended the IM4 trans beam position and NSUM along with the IMC input power. The overall pitch position in IM4 trans has changed significantly, and the NSUM value in lock for the same 60W of PSL input power has dropped from 57.4 to 54.4.
TITLE: 03/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 14mph Gusts, 12mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.73 μm/s
QUICK SUMMARY:
Last week I scanned the SHG temperature for more data points to confirm the dip in the middle of the sinc function. A rough fit to the side lobes suggests we should have about 160mW of green output. A few days before we improved the PMC alignment we measured 230mW of 1064 input into the SHG. 160 mW would be 69.5% conversion efficiency. This number isn't too far off from the conversion efficiency measurement we took when we first installed the SHG 6 years ago. We have known for sometime that we are missing a lot of green power for the amount of 1064 we put in. This plot makes the picture a bit more clear that we have been indeed losing more than half the green power. The cause is unclear. We have been suspecting the gray tracking in the SHG cryatal to be the cause even though we have a low green finess in the SHG.
The equation I used to create the fit was A*(np.sinc((T-T0)/width))**2
Where A is the input 1064 power, T0 is 34.9 C, and the 'width' of the sinc function is arbituary set to 2.5.
Sun Mar 10 10:11:07 2024 INFO: Fill completed in 11min 3secs
We reran the DARM offset step test around GPS 1394062645, similar to alogs 71913, 68870, 64974.
Our current measured contrast defect is slightly higher than in alog 71913, but overall pretty similar.
Matt will comment with the calibration of X0 offset cts into picometers.
Contrast Defect: 2.1 mW
Nominal Total Amps from DCPDs: 40 mA
Responsivity = e λ / c h = 0.858 A/W
Nominal Total Power on DCPDs: 46.6 mW
Nominal Homodyne Angle: 12.2 degrees
To get the offset in picometers from this plot, we use the quadratic factor from the fit, b, along with P_AS, and the contrast defect.
Using the data at 255Hz we find b = 0.672 mW / pm^2, P_AS = 46.6 mW, P_junk = 2.058 mW, which we then use to calculate the offset DeltaL_DC which we call x.
P_as - P_junk = P = ax^2
g = dP/dDeltaL_DC = 2ax
P = b g^2 = 4a^2bx^2 = ax^2, therefore 4ab = 1
We can then solve for x = 2 sqrt(P * b) = 2*sqrt( (46.6mW-2.058mW) * .672 pm^2/mW) = 10.94 pm
We can also calculate the mW / pm^2 [a] factor from the product of interferometer parameters: PRG, SRG, P_in, Reflectiviity of the arms, and the wavenumber; only I did not know them at the time (except the wavenumber).
I want to clarify here that 40 mW is the nominal DCPC power for O4a and now. I trended the DCPD sum output for the recent lock and the many months of O4a to confirm this is true.
OMC DCPD SUM has units of milliamps. One must divide by the responsivity to get milliwatts, which we have done here.
Matt, Criag, Sheila
We want to use this DARM offset stepping to look at the mode matching of the OMC.
In alog71141, Sheila stepped the DARM offset and looked at the OMCrefl power [H1:OMC-REFL_A_LF_OUT16] in order to estimate the mode matching level, which was estimated to be around 96% for cold OM2 [GPStime = 1371902599], and 85% for hot OM2 [GPStime = 1371910040]
When we looked at the same channels during this recent DARM offset step (3/9/24) [GPStime = 13940633389] we see much less change in the OMCrefl, which may be interpreted as better mode matching than the previous cold OM2. Because I cannot resolve any power changes in the noise, it is hard to give a percentage for the mode matching figure but we expect better than 96%.
A couple of notes on the recent DARM offset OMC reflected power: the reflected power is higher than before, as well as the noise, which may be concealing some of these power changes; another thing to note is the time spent ramping on each DARM step, which was much shorter in the previous analysis, and having a slower step may lead to less prominent power fluctuations in the OMCrefl.
change in HAM6 throughput estimated by AS_C
As done in Sheila's alog where she estimates the excess HAM6 losses, I have estimated that we have an additional 10% loss in HAM6 throughput.
Adding up the known losses for HAM6 we expect the throughput to be around 97%
Calibrating DCPD_SUM into mW and dividing by its change from DARMoffset by the AS_C change, we can estimate the losses in the OMC; the DCPDsum change was around 40.4 mW, while the AS_C change was around 46.3 mW, this gives us a ratio of 87%.
Given the ideal throughput of HAM6 being around 97% given known losses [ 0.993(OM1)*0.985(OM3)*0.9926(OMC QPD) = 97% ], this means that we have an additional 10% of losses in the OMC.
DCPD_SUM is converted from mA to mW by the responsivity: 0.858 mA/mW.
Using alogs 47217 and 45734 as a guide, we measured/calculated a new
OMC-DCPD_MATRIX.
Note: this might have to be redone if we update the anti-TIA filtes for the DCPDs, see alog 76228.
We measured the coherent signal amplitude ratio g = PD_A/PD_B above 30Hz (i.e. above the TIA transfer function imbalance), so the matrix is optimized where we actually care.
g=
1.0471
We measure the shot noise signal amplitude ratio h = PD_A/PD_B above 400Hz to avoid thermal noise and correlations from the feedback.
h=1.0247
This produced the new output matrix (see secript)
0.99861 1.00139
0.97725 -1.02328
For reference, old matrix:
0.99963 1.00040
0.98198 -1.0184
The new matrix was loaded, but not yet tested - the IFO lost lock due to 43kts wind gust.
J. Kissel, S. Ballmer, The ISC_LOCK guardian "SDF REVERT" state pushes the safe.snap file for the h1omc model (and others) after every lock loss. Stefan had saved the balance matrix numbers in the OBSERVE.snap, but not in the safe.snap. Together, we've saved the numbers to the safe.snap as well now.
SFD forgot the matrix again, so I updated the matrix and saved it to SDF.
THis one is duned for signal matching around 100Hz.
0.99785 1.00215
0.97800 -1.02249
Georgia, Trent, Elenna
We lost lock on the interferometer (most likely from 50mph gusts of wind) and had to align the arms. The y-arm proved difficult and we could not get the flashes on ALS-C_TRY_A_LF_OUT_DQ above 0.6 counts. To help the arm along in locking we changed the pdh auto-locker threshold to 0.55. We then decided to run an initial alignment.
During the initial alignment we got red dust warnings for the corner station.
After the intial alignment, the y-arm green flashes reaches 0.73 and we didn't need to change the pdh auto-locker again.
Today we saw in CAL-DELTAL_EXTERNAL_DQ some kinda weird hump in the DARM spectrum around 100 Hz. It made us curious about the calibration, so we measured the DARM OLG and sensing functions (PDF one). 1. The nominal DARM open loop gain unity gain frequency is around 80 Hz. The loop suppression has a factor of 3 gain around 100 Hz. This is higher than I recall, seems like we're over the phase bubble for sure. We lowered LSC-DARM1_GAIN from 400 to 285 to make DARM sit at the top of its phase bubble at 60 Hz. This affects the way that CAL-DELTAL_EXTERNAL_DQ looks, which is expected, but is overall not impacting our GDS sensitivity significantly (PNG one and two). 2. The DARM sensing function seems to exhibit significant detuning, with an anti-spring kicking in lower than 12 Hz. 3. We have 10^10 W/m DARM sensitivity. That's super high compared to one year ago, increased by the increased amount of OMC DCPD light. Seems to indicate the current OMC is pretty healthy.
Meashured the transfer function between DCPD_A and DCPD_B usinng a broadband injection. There is a slight frequency-dependent disagreement (0.2dB) between the two diodes, right around 25Hz, where the TIA has its complex poles.
It looks like one or both Anti-TIA filters are slightly mismateched. We won't tweak it today because we don't know with one is the culprit.
this looks to be related to the TIA response drift reported in LHO:75986.
The template used for this measurement can be found here:
/ligo/home/controls/sballmer/20240311/AoverBmeasurement.xml
Note: the max peak-peak deviation between DCPD_A and DCPD_B is 2.5%.
Sat Mar 09 10:12:00 2024 INFO: Fill completed in 11min 56secs
Naoki, Vicky, Nutsinee, Matt
We recovered the FDS and got 4.5dB squeezing in IFO with 40 times more CLF power as shown in the attached figure.
First we restored the ZM1/2/3 and FC1/2 OSEM positions to the values in O4a. Then we found the FC green trans in camera and PD. We aligned FC1 and FC2 and successfully locked the FC green. We went to SQZT8 and centered the green camera and green QPD.
Since we aligned the green QPD, the green QPD offset value is not valid anymore so we removed the beam spot control from FC ASC. We made a flag for the beam spot control in sqzparams and it is set to False now. We also set the ADF servo flag to False since the ADF demod phase might not be correct. After we figure out the optimal green QPD offset and ADF demod phase, we should revert them.
We reduced the FC IR gain from -3.5 to -0.1 and reduced the FC ASC gain from 0.1 to 0.005.
We have not done any PSAMS scan so we will do it next week.
I reduced the FC ASC threshold as shown in the attachment. I also reduced the fcWFS_qDip_lock_threshold in sqzparams from 0 to -50000 although I am not sure if this is useful.
The SQZ-CLF_REFL_LF_OUTPUT is 245uW now and was 5.7uW in O4a so the CLF power is 43 times more now.
Since the vent, we haven't recovered our squeeze in the region of that really improves our range: See Yellow BLRMS around 350Hz.
Checked SHG pump launch is ~20.5 - 21mW at both times and OPO green trans rejected is similar.
Trending our other signals, just see that OMC_TRANS_RF3 and CLF_REFL_RF6 and FC_WFS_A_ locking signal sare much larger, I think this is expected from increased CLF power. The NLG is simular 15.8 now, was 17.3. Plots of Jan 10th and March 9th.
Since we have a new OMC, we need to find the best optical gain spot on the new OMC.
To that end I closed the OMC ASC dither loops iwth a simple diagonal matrix (OM3-->OM3 and OM1-->OMC_SUS). It did converge with very low gain, but to a spot with not much headroom on the OMC_SUS (we are at 115000ct out of 131000cts on T2 and T3).
In that setting I reset the H1:ASC-OMC_[A/B]_[PIT/YAW]_OFFSET offsets, so right now we can lock to that spot with either dither or QPD.
Next: hunt for best optical gain around this spot.
Just as with the last OMC the optimal spot optical gain seems to be slightly different from the dither target. Did some manual optimisation to reach the attached QPD offsets.
Updated the dither input matrix H1:OMC-ASC_DACTMAT in SDF.
I'm having a hard time deciding if the ITMY violin mode 5/6 damping settings are decent. Stefan has been moving around the OMC alignment which seems to have some large effect on the monitor filters. However, the alignment has converged at some value and I have engaged a 0.01 gain with FMs 6, 7 and 10 and so far the monitors show both modes decreasing. The nominal gain is 0.02, so I think if we lose lock and relock that gain setting will be ok. We are stuck in the OMC_WHITENING state and this mode pair is the only problem- all other modes are low or are decreasing very well in their settings.
Edit: nominal low noise achieved. These damping settings are good.
The pressures: HAM7: ~1.9E-7 Torr HAM8: ~4.7E-7 Torr Corner: ~4.4E-8 Torr EX: ~4.9E-9 Torr Today's activities: - HAM8 Turbo was stopped, the cart was disconnected - Relay tube - HAM7 - HAM8 was valved in to the main volume - RV1; FCV2; FCV3; FCV4; FCV8 are now opened, so the system is back to normal As the vacuum works now ended, this was the last page of the vent vacuum diary. Congratulations to the vacuum team, and to all who helped in the vacuum tasks, it was a great effort, and it ended up being a success. If anyone is interested in the vacuum results and tasks more in-depth, here is a summary document: T2400085-v1
We've had a large crew in the control room today working on locking:
Naoki, Sheila, Vicky
While damping violins, we re-injected squeezing during OMC_WHITENING, ran SQZ-IFO ASC, and got 3dB of squeezing immediately. Up to almost 4.5dB with this 40x higher CLF power.
Opening the beam diverter, we immediately saw the squeezer in OMC transmission. The CLF_RF3 signal in OMC trans (SQZ-OMC_TRANS_RF3_DEMOD_RFMON) went from -25 (no sqz), to -8 (just opening bdiverter), to 0 (after running SQZ_AS42_ASC after resetting no-sqz offsets).
SQZ_MANAGER can successfully take the squeezer to FREQ_DEP_SQZ again. FC-IR handoff works, we adjusted gains according to FC_IR_OLTF to match old loop gain with higher CLF. Adjusted FC_ASC gain. SQZ_ANGLE_ADJUST guardian has the nominal state now as "DOWN" (set using flag=False in sqzparams.py). FC beam spot control left at False.
Louis, Vicki, Craig Today we revived the correlated noise budget code located at https://git.ligo.org/aligo_commissioning/correlated_noise, first made in June (alog 71333). This code is a standalone singular script which grabs the raw DCPD data, grabs the DARM calibration OLG and sensing function info, does some math from Kiwamu's DCC T1700131, and produces a correlated noisebudget. Formerly, I had used my ownnoise_recorder
white noise injections to get the DARM calibration information. But since I am gone, it would be better if we used a maintained piece of software to get the calibration. Today, Louis helped me to use apydarm
.npz file to get the DARM OLG and sensing functions. The code we developed today is in/ligo/gitcommon/correlated_noise/code/plot_cross_correlation_pydarm_npz_calibration.py
Attached are the correlated noisebudget results for GPS start 1387130434, over 600 seconds of data. I posit that we don't really need a ton of time to integrate down, both because the shot noise floor is not that far away from the correlated noise floor, and we can use logbinning averaging to achieve a higher effect number of averages in a shorter amount of time. Results I've used the Dec 18 noisebudget traces made by Camilla in/ligo/gitcommon/NoiseBudget/aligoNB/out/H1/lho_darm_noisebudget/lho_darm_noisebudget.hdf5
. Overall, the correlated noise results seem decently sensible, especially at high frequency. I note that the correlated noise limit we are hitting at 1 kHz seems to be laser frequency noise (third plot attached). At 500 Hz, we are running into our "thermal noise floor". Whether or not this is really thermal noise is anyone's guess, since it is above our official estimate, but the story for O4a remains the same as from O3. At 20 Hz, the correlated noise seems to overestimate what is actually in DARM, which cannot be correct. This is something Sheila has been concerned with in the past (alog 70978). This could be chalked up to a small change in the actual vspydarm
DARM OLG, unclear what else it could possibly be. It is worth noting that the DARM OLG cannot really affect the correlated noise results massively above 500 Hz, just because the magnitude of the DARM OLG is around 0.1 there and falling quickly. Future Work The next steps is for Vicki to import this code to the aligoNB, removing all calls to mynds2utils
library (avoiding a dependency there). Louis also wants to add some functionality toaligoNB
so that the noisebudget can callpydarm
at a GPS time and get the most recent calibration. (Craig loves this). Louis will clone thealigoNB
env to verify everything still works before making a "pull request" to the actualaligoNB
repo.
After some further conversation with Vicki and Gabriele, they asked me to put in some artificial 40% increase in the thermal noise to see if that could explain our correlated noise in December. It seems like potentially yes, pretty good agreement. Additionally, we realized that the Squeezed DARM should be below the Correlated Noise at 20 Hz. Because they are taken at different times, one with sqz and one with no sqz, then the filter cavity should be reducing the quantum radiation pressure noise. There is no discrepancy between the Correlated DARM and the Unsqueezed DARM, which can be seen from the .svg noisebudget here: https://lhocds.ligo-wa.caltech.edu/exports/craig.cahillane/gitcommon/correlated_noise/figures/20231220_180016_utc/correlated_darm_calibrated_zoomed_binwidth_0p1.svg Also attached as a PDF. I made the Unsqueezed DARM a different color and a thicker line so you can see it behind the Correlated DARM.
This log follows up some previous work that's been done to understand the LSC, in particular MICH, noise coupling that we have observed. The most recent work done on this front was by Dana, in alogs 74477 and 74787. Notably, the MICH coupling follows an interesting shape here, especially below 20 Hz. For MICH, we expect a flat coupling depending only on the finesse, Gm = pi/2*F. Evan Hall made some great measurements of this coupling years ago and you can see the results in Fig 2.17 of his thesis(link to thesis)- without any feedforward the magnitude of the coupling is flat in frequency down to 10 Hz. However, Dana's measurements clearly show a frequency dependent coupling below 20 Hz. Also, Dana mentions that the MICH coupling is about 40% too high than we expect based on finesse.
I'll add here a quick note that currently the UGF of MICH is about 8 Hz and the UGF of SRCL is about 11 Hz, so I think it's safe to assume that we are not seeing any significant closed loop effects from either of these loops down to about 12 Hz in these measurements.
Something to remember here is that when we measure the MICH coupling we drive the beamsplitter which does induce a change in the MICH length, but it also changes the SRCL and PRCL length. Therefore, we should expect to pick up SRCL coupling along with the MICH coupling when we measure. Evan's thesis also includes the form of the SRCL coupling in Eq 2.29: Gs = 0.012 [m/m] * Pa/750 [kW] * dL/10 [pm] * F/450 * (10 [Hz] / f)^2 (I am only including the first term that dominates at low frequency). The SRCL coupling results from radiation pressure in the SRC due to the DARM offset (dL), power in the arms (Pa), and finesse (F) and follows a 1/f^2 slope (again, I am ignoring the second term here that rises like f^2 at high frequency). We are operating at much higher power and double the DARM offset, Pa=370 kW and dL = 20 pm (and F = 440).
Regarding the 40% excess MICH coupling, if you divide Dana's result by an additional sqrt(2), it lines up exactly how you would expect. Is there a chance the MICH calibration is missing a rt2 factor related to the fact that we measure from the beamsplitter?
Assuming I'm correct about the sqrt(2) factor, and plotting the magnitude of the expected MICH and SRCL coupling along with Dana's calibrated measurement, our expected O4 SRCL coupling lines up almost exactly with the response at 20 Hz and below (see first attached plot).
I think this effect has always been there, but not easily observable because the SRCL coupling was much lower due to lower operating power and smaller DARM offset. Comparing Evan's MICH coupling measurement (Fig 2.17) with his SRCL coupling measurement (Fig 2.18), the SRCL coupling at 20 Hz was close to an order of magnitude lower than the MICH coupling.
I think this understanding of the coupling better explains why we need to put so much work into the LSC feedforward. Specifically, we measure the coupling for MICH and SRCL, and then usually tune MICH first and then SRCL. Then, to do our iterative tuning, we redo the MICH coupling. It's likely we could do a better job first just tuning SRCL and then measuring and tuning MICH, since we need to subtract the SRCL coupling well enough to get a "true" measure of the MICH coupling.
Furthermore, the SRCL coupling is dependent on our DARM offset. When we make changes to OM2, for example, we change the mode matching at the output. Since we servo to keep the amount of light on the DCPDs constant, we could be changing the required length to achieve this amount of light slightly. In principle, this should only effect the SRCL coupling, but since SRCL shows up in our MICH coupling measurement, it effects both.
Finally, it appears in Dana's measurement that there is a rising trend above 30 Hz, which I have no explanation for. I don't think that can be explained by the SRCL coupling. A look at that second term in the SRCL coupling equation: Gs = 3e-5 [m/m] * phi_s/10 [deg] * dL/10 [pm] * F/450 * (f / 100 [Hz])^2 (Evan's thesis Eq 2.29), I estimate that with a SRCL detuning of about 1 deg, around 30 Hz the SRCL coupling term with an f^2 slope is about 5.3e-7 m/m. This is both too small and the wrong slope to explain that feature.
I started poking around the CAL CS screens, and I noticed that the BS control path calibration screen has a "sqrt(1/2)" filter in M1 and M2 that is not engaged. Maybe that solves the rt2 mystery (screenshot attached).
Next, I took a look at the calibrated SRCL coupling. Thanks to Dana's fantastic documentation of the steps in 74477 I was able to generate the calibrated measurement of the DARM/SRCL transfer function (for the time of the SRCL excitation with no feedforward, use GPS time 1371490640). The DTT file is saved as "/ligo/home/elenna.capote/LSCFF/SRCL_DARM_cal.xml"
I exported the data and plotted it against my calculation of the SRCL coupling equation using both terms, Evan's thesis eq 2.29. For the high frequency term that is dependent on microscopic SRCL detuning, I used 0.5 deg (and darm offset 20 pm and finesse 440), which I got to by guessing and matching the trace. See the result in the second attachment.
Overall, the measurement magnitude is too low by a factor of 3. However, the slope matches up quite well. Given that we were apparently missing a rt2 in the MICH calibration, I am convinced that somewhere in the SRCL Cal screen, some filter magnitude is off by 3. Off the top of my head, I know that Gabriele updated the M1 offload filter for PRM and SRM, and that doesn't look like it has been updated in CAL CS. I'm not sure if other aspects are out of date as well. For those comparing the plots, the red SRCL trace in both LSC coupling plots is exactly the same.
Reading Matt's alog calculating the DARM offset (alog 76236), I realized made a pretty big error in these noise coupling calculations. I incorrectly assumed "double darm offset" meant 20 pm instead of 10 pm, but it actually means 40 mW instead of 20 mW. Therefore, I need to calculate what the DARM offset was around the time of these measurements. Dan took some contrast defect measurements at 60W using the O4a TCS settings before we powered up in April (see pdf attachment). I also trended back in time to confirm that this measurement was indeed taken in the 60W configuration.
Dan's measurement shows about 1 mW of contrast defect and b=0.648 mW/pm^2. Therefore, the DARM offset during O4a was likely around 7.7 pm, using 40 mW of DARM offset light (dL = sqrt((40-1)/0.648)). Recalculating the expected SRCL noise coupling value in m/m shows it lines up very well with the calibrated SRCL measurement (see plot). Therefore, my assumption in my previous comment that the difference in expected versus measured value was due to miscalibration seems less likely.
However, this corrected result now casts doubt on my assertion that the MICH coupling behavior at low frequency can be explained by SRCL coupling. Using the corrected DARM offset value shows that the SRCL coupling is less than the observed coupling at low frequency by about a factor of 3 (see plot).