Just had a ~3min drop from OBSERVING due to SQZ, but it cameback automatically.
Did notice the SQZ_OPO_LR node has the familiar User Message:
"pump fiber rej power in ham7 high, nominal 35e-3, align fiber pol on sqzt0"
It's been trending up the last 5 days when it was last touched up on 3/26 (alog83570). Looks like it moved above 0.35 counts at 10am (local time) this morning. See attached.
It's been a few minutes and one can see H1's range took a step down about 6Mpc after this SQZ drop.
Camilla, Sheila.
The drop was because the OPO PZT ran out of range, see t-cursor on attached plot. It's a known issue that the SQZ angle (and alignment) changes with different PZT1 voltage.
It seems like that the sqz angle was set for 60-70V and was bad once we relocked at 100V. This would have been improved by taking SQZ_MANAGER to SCAN_SQZANG_FDS so it can find the best sqz angle again. If we were running the SQZ_ANG_ADJUST servo, this may have improved itself as you can see the ADF reported SQZ angle change at the time.
With the higher (19 vs 11) NLG 83665, the range and 350Hz SQZ (yellow BLRMS) does seem to be improved, but the high frequency SQZ did seem to be less stable as we thermalized.
[M. Todd, C. Compton]
Camilla and I made several knife edge measurements of the L5 CO2 laser in the optics lab after she got back from her trip to Access. The beamwidth estimates are consistent with tests done by Gabriele and Camilla
Measurements:
Fits to both the numerical derivative and cumulative yield similar estimates of the beamwidth (1/e^2 radius) : around 1.3mm at 16cm from the aperature is consistent with the beam profiles done in Gabriele and Camilla's test, which estimated the beam waist to be around 1.2mm.
Code for analyzing this data
Closes FAMIS 26036. Last checked in alog 83560.
Overall much quieter traces across all plots from last week's. Namely, the 7.6Hz to 9Hz elevated signals and peaks that Oli found seem to be gone. Plot attached.
TITLE: 03/31 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 19mph Gusts, 12mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY:
Ibrahim is handing over an H1 which has been at Nominal Low Noise for 2+hrs (and a nicer range just under 160Mpc---woo woo Sqz commissioning work this morning). Ibrahim also schooled me on when wind at EY can cause us grief if it hits EY at a pesky angle---like it was at 2000utc today).
Speaking of winds, it's continues to be generally below 25mph for the last 12hrs (but the forecast says it should drop after sunset. Secondary microseism had a small hump up between 10-22hrs ago and hovers just over the 50th percentile.
TITLE: 03/31 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
IFO is in NLN and OBSERVING as of 21:24 UTC
Overall calm final day of O4b with a successful comissioning session. Things of note:
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
15:17 | FAC | Nellie | MX | N | Technical Cleaning | 16:12 |
15:17 | FAC | Kim | MY | N | Technical Cleaning | 16:11 |
17:10 | FAC | Kim | H2 Building | N | Technical Cleaning | 17:18 |
17:43 | ISC | Mayank, Siva, Keita | OptLab | Yes | ISS Array work | 19:30 |
21:11 | ISC | Jennie, Mayank, Rahul, Keita, Sivananda | Optics Lab | Yes | ISS Array Work | 00:11 |
Sheila, Camilla, Jennie
This morning we changed SRCL offset from -191 to -306 and FC de-tuning from -34 to -28, as discussed in 83570. Took some SQZ data here as we were interested if we could get FIS SQZ lower than No SQZ ~100Hz and below, Sheila's models (e.g. 83572) suggest we should but it looks like there's a low frequeceny noise source (in FIS not FDS) in our data sets preventing us from getting down to the modeled level of SQZ.
Sheila turned OPO trans setpoint up from 80uW to 95uW to increase NLG from 11 to 19 (similar to what we had earlier in O4). Measured NLG with 76542. OPO gain left at -8. Turned off SQZ ASC.
opo_grTrans_ setpoint_uW | Amplified Max | Amplified Min | UnAmp | Dark | NLG (usual) | NLG (maxmin) | OPO Gain |
95 | 0.0176 | 0.000279 | 0.00002 | 0.00094 | 19.1 | 20.0 | -8 |
110 | 0.03315 | 0.000269 | 0.000879 | -0.00002 | 35 | -8 |
Type | Time (UTC) | Angle | Notes | DTT Ref |
No SQZ | 03/29 | N/A | ref 0 | |
FIS SQZ | 171 | Angle tuned for FDS (maybe thermalized since) | ref1 | |
FIS SQZ | 17:05:00 | 154 | Ang tuned for FIS | ref2 |
FIS Mid(ish) | 17:15:00 | 101 | Little better than no SQZ at 60Hz | ref3 |
FIS Mid(ish) | 92 | ref4 | ||
ASQZ FIS | 68 | ref5 | ||
ASQZ FIS -10deg | 17:24:00 | 58 | ref6 | |
ASQZ FIS +10deg | 78 | ref7 | ||
FIS Mid(ish) | 17:31:30 | 115 | ref8 | |
FIS Mid(ish) other side | 17:43:00 | 27 | ref9 | |
FIS Mid(ish) | 17:45:30 | 82 | Check data doesn't include a glitch | ref10 |
Type | Time (UTC) | Angle | Notes | DTT Ref |
FIS ASQZ +10deg | 17:53:00 | 82 | Plot seems similar with same ang, different SRCL offset | ref 11 |
FIS ASQZ | 17:56:00 | 72 | ref12 | |
FIS ASQZ -10deg | 62 | ref13 | ||
FIS Mid (ish) | 104 | Can see that rotation is a little different with SRCL de-tuning different but low freq noise level is the same. | ref14 |
Type | Time (UTC) | Angle | Notes | DTT Ref |
Mid SQZ | 112 | Interesting data here. Low freq noise higher than with NLG 19. | ref 15 | |
ASQZ | 18:20:00 | 70 | ref16 | |
MidSQZ | 18:22:30 | 100 | ref17 |
Sheila turned OPO trans back to 96uW so expect NLG to be 19 going into Observing, larger than normal but closer to the value uses before the last OPO crystal move. SQZ angle servo off and angle set back to 171. ADF left on.
I had a brief look at some of this data to put bounds on losses and arm power in 83953:
The first attachment shows a plot of more of this data against models, focusing on the unexplained low frequency noise that we don't see with the filter cavity . The measured NLG matches the NLG infered from anti-squeezing and squeezing for the NLG 19 measurements, but for the NLG 35 measurements the infered NLG is 27.3, so that is what I've used here. As Camilla wrote above, the NLG 35 measurements were made with a different SRC detuning than NLG19, so that is included in this model. Squeezing angles are fit to the band from 2100 Hz to 2300 Hz.
The first plot shows the measured data in solid lines, the quantum noise model in dashed lines, and the dotted lines show the non quantum noise from subtraction added to the quantum noise models. There is a discrepancy where many of the measurements seem to have extra noise from 20-50 Hz, I've tried to make an easier to read version in the second plot, and finally removed some traces to try to make it easier to see.
In the above alog we thought perhaps that this could be explained as an excess noise that was larger with higher nonlinear gain but consistent with squeezing angle, the last attachment shows the residuals between the model and measurement for the measurements that had clear discrepancies, they all seem to be different, so this excess seems to depend both on squeezing angle and nonlinear gain.
The script used to make these plots can be found at this repo
Today during commissioning we increased the SQZ NLG from 11 to 19, now the nominal OPO trans setpoint in sqzparams in 95uW. This was because before our last OPO crystal move 82134, the NLG was closer to 17-19.
We also turned the ADF (322Hz line) back on, it had been off since March 27th 83621, tagging DetChar.
Sheila, Camilla
The IFO was just relocking at the start of commissioning time today, so we set the ADF back on and the sqz angle servo on. This worked fine, with the phase shifter staying well within it's range (it stayed between 180 and 130 degrees, it's range is 0 -270 degrees).
In the attached screenshot the vertical cursors are both at 25 minutes into the lock. You can see that the SQZ BLRMS and the range behave differently with the servo on, but in both cases they start with a low range and move up slowly. We think that the set point of the squeezing angle servo wasn't set ideally for this time.
In the second screenshot you can see that I changed the SRCL offset and the servo responded to it, taking about 3 minutes to settle.
Rahul, Betsy, Camilla
Attached are some photos of the proposed location of the beamdump that will be placed behind the HAM1 RM3 / PM1 tip-tilt with new D2500101 attached to existing Tip-Tilt DSUB Bracket Holder D1101430. In reality the beamdump will be placed at the mirror image of the photos as the HAM1 beam will be coming the opposite incoming angle.
The Beamdump is made from:
Lockloss right after we got back to OBSERVING with good range.
First impression of cause is that it might be wind related since:
Relocking again now.
Mon Mar 31 10:09:31 2025 INFO: Fill completed in 9min 28secs
FAMIS 31079
The temperature increase noted last week seems to have come back to normal for the most part after a few days.
Jason's RefCav alignment tweak 3 days ago is clearly seen and level has stayed relatively stable since.
PMC Refl hasn't been rising, but perhaps has gotten noisier starting a few days ago.
Last week Corey changed the gains of POP18 because of difficulties locking DRMI. 83540 To avoid having the histories of these POP18 build ups being confusing, I've moved the gain of 2 into the trigger matrix, and in sdf set the locking gains back to 2. (These gains were changed from 1 to 2 when the 50/50 splitter was added to the POP path.)
I've edited line 238 in ISC_DRMI to set the trigger matrix element to 2.
Lockloss after 2 minute lock before reaching observing. No immediate apparent causes.
TITLE: 03/31 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 28mph Gusts, 23mph 3min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.21 μm/s
QUICK SUMMARY:
IFO is LOCKING in LASER_NOISE_SUPPRESSION
Today we have planned comissioning from 8:30 to 11:30 local time.
The last lockloss seems to have been caused by wind and elevated microseism, though neither seem high enough to have necessarily caused a lockloss.
Ibrahim, Oli, Camilla
We had two 30+ minute range drops last night, plot attached. Looks to be mainly under 60Hz from the OMC BLRMs, plot.
Doesn't appear to be sqz, EX ground motion 83233, or CO2 ISS channel 82728 related. Oli also checked this wasn't PI related 82944.
Confirmed not the PIs for either range drop (drop1, drop2). There was a small drop in range a few minutes before the second range drop around the same time as PI31 had a small ringup, but zooming in, the ringup happened multiple minutes before and so doesn't account for that quick drop either(ndscope3).
Sheila, Camilla
Reduced HAM7 rejected pump power and increased SHG launch, turned OPO trans setpoint up to 120uW and measured NLG with 76542 to be 58 (this was a little lower than with 120uW in 83370). OPO gain turned down from -8 to -12. ADF was on for all apart from "Mean SQZ w/o ADF".
Type | Time (UTC) | Angle | DTT Ref |
No SQZ | 16:01:00 - 16:15:00 | N/A | ref 0 |
SQZ | 16:56:30 - 16:59:30 | (CLF-) 174 | ref1 |
SQZ +10deg | 17:00:00 - 17:03:00 | (CLF-) 184 | ref2 |
SQZ -10deg | 17:03:30 - 17:06:30 | (CLF-) 164 | ref3 |
Mean SQZ w/o ADF | 17:07:30 - 17:10:30 | N/A | ref4 |
Mean SQZ w/ ADF | 17:11:00 - 17:14:00 | N/A | ref5 |
Mid SQZ + | 17:17:00 - 17:20:00 | (CLF-) 209 | ref6 |
Mid SQZ - | 17:21:30 - 17:24:30 | (CLF-) 152 | ref7 |
ASQZ | 17:27:30 - 17:30:30 | (CLF-) 80 | ref8 |
ASQZ +10deg | 17:31:30 - 17:34:30 | (CLF-) 90 | ref9 |
ASQZ -10deg | 17:35:00 -17:38:00 | (CLF-) 70 | ref10 |
Then went to FDS | |||
FDS SQZ, SRCL -191 | 17:46:00 - 17:49:00 | (CLF-) 174 | ref11 |
FDS SQZ +10deg, SRCL -191 | 17:49:30 - 17:51:30 (2mins) | (CLF-) 184 | ref12 |
FDS SQZ -10deg, SRCL -191 | 17:52:00 -17:54:00 (2mins) | (CLF-) 164 | ref13 |
FDS SQZ, SRCL -290 | 17:56:30 - 17:59:30 | (CLF-) 146 | ref14 |
FDS SQZ +10deg, SRCL -290 | 18:00:00 - 18:02:00 (2mins) | (CLF-) 156 | ref15 |
FDS SQZ -10deg, SRCL -290 | 18:02:30 - 18:04:30 (2mins) | (CLF-) 136 | ref16 |
Starting FC detuning -36Hz | |||
FDS SQZ, SRCL -290, FC detuning -40Hz | 18:08:30 - 18:11:30 | (CLF-) 146 | ref17 |
FDS SQZ, SRCL -290, FC detuning -32Hz | 18:12:00 - 18:15:00 | (CLF-) 146 | ref18 |
FDS SQZ, SRCL -290, FC detuning -32Hz | 18:18:00 - 18:21:00 | (CLF-) 149 | ref19 |
FDS SQZ, SRCL -290, FC detuning -28Hz* | 18:21:30 - 18:24:30 | (CLF-) 149 | ref20 |
FDS SQZ, SRCL -290, FC detuning -24Hz | 18:225:30 - 18:28:30 | (CLF-) 149 | ref21 |
OPO trans back to nominal 80uW, NLG 12 | |||
FDS SQZ, SRCL -290, FC detuning -28Hz | 18:46:30 - 18:49:00 (2m30) | (CLF-) 170 | ref22 |
FDS SQZ, SRCL -191, FC detuning -36Hz | 19:03:30 - 19:06:00 (2m30) | (CLF-) 171 | ref23 |
* For NLG of 58, SRCL -290, FC detuning -28Hz looked best.
Plots attached of FIS data showing SQZ, Mean SQZ, Mid SQZ and also SQZ and ASQZ, filename shown on screenshot.
Also did FDS SQZ, +/-10deg with nominal SRCL detuning (-191) and -290, plot attached. And adjusted the FC de-tuning with SRCL offset at -290, plot attached.
Finally we went back to the nominal NLG (NLG of 12 with 80uW OPO Trans setpoint) and checked FDS SQZ with the best found settings at high NLG: SRCL -290, FC de-tuning -28Hz and back to nominal settings, DARM plot attached. We didn't have time to fully tune the angle in both settings so could repeat this to check at which settings the range is best. Sheila ran a SQZ angle scan at these settings (SRCL -290, FC de-tuning -28Hz), see attached, it is less frequency dependent than than the scans taken the day before at SRCL -191 (nominal) and -190, FC de-tuning -36Hz (nominal), plot attached.
opo_grTrans_ setpoint_uW | Amplified Max | Amplified Min | UnAmp | Dark | NLG (usual) | NLG (maxmin) | OPO Gain |
120 | 0.0540944 | 0.00026378 | 0.000913452 | -0.0000233 | 57.75 | 58.68 | -12 |
80 | 0.010857 | 0.0002927 | 0.000904305 | -0.0000219 | 11.72 | 12.57 | -8 |
Here are some plots of Camilla's first dataset above, changing the SRC detuning while adjsuting the squeezing angle for high frequency squeezing, made with the same code used for 80318, which is available here
For the gwinc model, I've set the generated squeezing to 23 dB based on Camilla's measured NLG of 58. Based on the loss estimates from 83457, I've set the Injection loss to 0.178 (17.8% loss) and the PD efficiency (readout efficiency) to 0.815, and the phase noise to 0.
The third attachment shows the model where I've manually adjusted the SRC detuning to roughly match the subtracted squeezing, and the second shows a linear fit of SRCL offset to these detunings. This suggests that the SRCL offset should be at -306 counts to reduce the SRCL offset, and that we are currently running with a SRCL detuning of 0.013 radians.
This morning we put SRCL offset to -306, FC de-tuning -28Hz. I then ran SCAN_SQZANG which changed the angle form 171 to 161 and compare the before and after DARM, attached, SQZ looks alot better at higher frequencies, however the range, attached, is similar or a little worse, maybe the 300Hz (yellow BLRMs) squeezing is slightly worse.
Updated DTT legend as had typo.
Here are some preliminary plots from Camilla's data set of different squeezing angles taken at an NLG of 58 with the SRCL offset at it's nominal -191 counts setting, which we believe is about 13 mrad SRC detuning.
The first plot shows some assumptions that go into making this model, we start with an assumption about arm power, use the noise budget estimate of non quantum noise at 2kHz (which may be out of date now), and set the readout losses to fit the no squeezing data at 2.1-2.3kHz. Then subtract this quantum noise model without squeezing from the no squeezing data, and use that as an estimate of the non-quantum noise, which can be added to all of the quantum noise models for different squeezing angles to compare to the measurement. (second plot is a somewhat overwhelming plot of all this added for completeness).
I've set the phase noise to 0 based on 83457. Using the level of sqz and anti-squeeze at 2.1-2.3 kHz, we infer that the NLG was 63 and the total efficency was 66.5%. Camilla measured the NLG to be 58, for 120uW circulating power, but in 83370 she measured 61-63 for 120uW. The third plot here shows the data that Camilla took with the LO loop unlocked, so that the squeezing angle is averaging and rotating freely. Using this and knowledge of the NLG, we should be able to infer the total squeezing efficiency as a function of frequency. Doing the subtraction of non quantum noise increases the infered efficiency, (compare thick lines to thin), the two different values of NLG suggest rather different efficiencies. There is evidence that the efficiency frequency dependent, which could be caused by a number of effects. Below 200 Hz there is some excess noise in the mean sqz trace, as you can see here, which causes the efficiency infered to be above 1.
The next two plots show the model broken into more readable plots, with the only thing I've adjusted by hand being the SRC detuning. There is a discrepancy between the model + noise for the anti-squeezing and anti-squeezing +/-10 degrees traces without the filter cavity, which seems like it could be some excess noise that is similar for the different traces. This is similar to the discrepancy seen in the last plot in 82097, but it is larger in this higher NLG dataset.
I'm looking again at the OSEM estimator we want to try on PR3 - see https://dcc.ligo.org/LIGO-G2402303 for description of that idea.
We want to make a yaw estimator, because that should be the easiest one for which we have a hope of seeing some difference (vertical is probably easier, but you can't measure it). One thing which makes this hard is that the cross coupling from L drive to Y readout is large.
But - a quick comparison (first figure) shows that the L to Y coupling (yellow) does not match the Y to L coupling (purple). If this were a drive from the OSEMs, then this should match. This is actuatually a drive from the ISI, so it is not actually reciprocal - but the ideas are still relevant. For an OSEM drive - we know that mechanical systems are reciprocal, so, to the extent that yellow doesn't match purple, this coupling can not be in the mechanics.
Never-the-less, the similarity of the Length to Length and the Length to Yaw indicates that there is likely a great deal of cross-coupling in the OSEM sensors. We see that the Y response shows a bunch of the L resonances (L to L is the red TF); you drive L, and you see L in the Y signal. This smells of a coupling where the Y sensors see L motion. This is quite plausible if the two L OSEMs on the top mass are not calibrated correctly - because they are very close together, even a small scale-factor error will result in pretty big Y response to L motion.
Next - I did a quick fit (figure 2). I took the Y<-L TF (yellow, measured back in LHO alog 80863) and fit the L<-L TF to it (red), and then subtracted the L<-L component. The fit coefficient which gives the smallest response at the 1.59 Hz peak is about -0.85 rad/meter.
In figure 3, you can see the result in green, which is generally much better. The big peak at 1.59 Hz is much smaller, and the peak at 0.64 is reduced. There is more from the peak at 0.75 (this is related to pitch. Why should the Yaw osems see Pitch motion? maybe transverse motion of the little flags? I don't know, and it's going to be a headache).
The improved Y<-L (green) and the original L<-Y (purple) still don't match, even though they are much closer than the original yellow/purple pair. Hence there is more which could be gained by someone with more cleverness and time than I have right now.
figure 4 - I've plotted just the Y<-Y and Y<-L improved.
Note - The units are wrong - the drive units are all meters or radians not forces and torques, and we know, because of the d-offset in the mounting of the top wires from the suspoint to the top mass, that a L drive of the ISI has first order L and P forces and torques on the top mass. I still need to calculate how much pitch motion we expect to see in the yaw reponse for the mode at 0.75 Hz.
In the meantime - this argues that the yaw motion of PR3 could be reduced quite a bit with a simple update to the SUS large triple model, I suggest a matrix similar to the CPS align in the ISI. I happen to have the PR3 model open right now because I'm trying to add the OSEM estimator parts to it. Look for an ECR in a day or two...
This is run from the code {SUS_SVN}/HLTS/Common/MatlabTools/plotHLTS_ISI_dtttfs_M1_remove_xcouple'
-Brian
ah HA! There is already a SENSALIGN matrix in the model for the M1 OSEMs - this is a great place to implement corrections calculated in the Euler basis. No model changes are needed, thanks Jeff!
If this is a gain error in 1 of the L osems, how big is it? - about 15%.
Move the top mass, let osem #1 measure a distance m1, and osem #2 measure m2.
Give osem #2 a gain error, so it's response is really (1+e) of the true distance.
Translate the top mass by d1 with no rotation, and the two signals will be m1= d1 and m2=d1*(1+e)
L is (m1 + m2)/2 = d1/2 + d1*(1+e)/2 = d1*(1+e/2)
The angle will be (m1 - m2)/s where s is the separation between the osems.
I think that s=0.16 meters for top mass of HLTS (from make_sus_hlts_projections.m in the SUS SVN)
Angle measured is (d1 - d1(1+e))/s = -d1 * e /s
The angle/length for a length drive is
-(d1 * e /s)/ ( d1*(1+e/2)) = 1/s * (-e/(1+e/2)) = -0.85 in this measurement
if e is small, then e is approx = 0.85 * s = 0.85 rad/m * 0.16 m = 0.14
so a 14% gain difference between the rt and lf osems will give you about a 0.85 rad/ meter cross coupling. (actually closer to 15% -
0.15/ (1 + 0.075) = 0.1395, but the approx is pretty good.
15% seem like a lot to me, but that's what I'm seeing.
I'm adding another plot from the set to show vertical-roll coupling.
fig 1 - Here, you see that the vertical to roll cross-couping is large. This is consistent with a miscalibrated vertical sensor causing common-mode vertical motion to appear as roll. Spoiler-alert - Edgard just predicted this to be true, and he thinks that sensor T1 is off by about 15%. He also thinks the right sensor is 15% smaller than the left.
-update-
fig 2- I've also added the Vertical-Pitch plot. Here again we see significant response of the vertical motion in the Pitch DOF. We can compare this with what Edgard finds. This will be a smaller difference becasue the the pitch sensors (T2 and T3, I think) are very close together (9 cm total separation, see below).
Here are the spacings as documented i the SUS_SVN/HLTS/Common/MatlabTools/make_sushlts_projections.m
I was looking at the M1 ---> M1 transfer functions last week to see if I could do some OSEM gain calibration.
The details of the proposed sensor rejiggling is a bit involved, but the basic idea is that the part of the M1-to-M1 transfer function coming from the mechanical plant should be reciprocal (up to the impedances of the ISI). I tried to symmetrize the measured plant by changing the gains of the OSEMs, then later by including the possibility that the OSEMs might be seeing off-axis motion.
Three figures and three findings below:
0) Finding 1: The reciprocity only allows us to find the relative calibrations of the OSEMs, so all of the results below are scaled to the units where the scale of the T1 OSEM is 1. If we want absolute calibrations, we will have to use an independent measurement, like the ISI-->M1 transfer functions. This will be important when we analyze the results below.
1) Figure 1: shows the full 6x6 M1-->M1 transfer function matrix between all of the DOFs in the Euler basis of PR3. The rows represent the output DOF and the columns represent thr input DOF. The dashed lines represent the transpose of the transfer function in question for easier comparison. The transfer matrix is not reciprocal.
2) Finding 2: The diagonal correction (relative to T1) is given by:
I will post more analysis in the Euler basis later.
Here's a view of the Plant model for the HLTS - damping off, motion of M1. These are for reference as we look at which cross-coupling should exist. (spoiler - not many)
First plot is the TF from the ISI to the M1 osems.
L is coupled to P, T & R are coupled, but that's all the coupling we have in the HLTS model for ISI -> M1.
Second plot is the TF from the M1 drives to the M1 osems.
L & P are coupled, T & R are coupled, but that's all the coupling we have in the HLTS model for M1 -> M1.
These plots are Magnitude only, and I've fixed the axes.
For the OSEM to OSEM TFs, the level of the TFs in the blank panels is very small - likely numerical issues. The peaks are at the 1e-12 to 1e-14 level.
@Brian, Edgard -- I wonder if some of this ~10-20% mismatch in OSEM calibration is that we approximate the D0901284-v4 sat amp whitening stage with a compensating filter of z:p = (10:0.4) Hz? (I got on this idea thru modeling the *improvement* to the whitening stage that is already in play at LLO and will be incoming into LHO this summer; E2400330) If you math out the frequency response from the circuit diagram and component values, the response is defined by % Vo R180 % ---- = (-1) * -------------------------------- % Vi Z_{in}^{upper} || Z_{in}^{lower} % % R181 (1 + s * (R180 + R182) * C_total) % = (-1) * ---- * -------------------------------- % R182 (1 + s * (R180) * C_total) So for the D0901284-v4 values of R180 = 750; R182 = 20e3; C150 = 10e-6; C151 = 10e-6; R181 = 20e3; that creates a frequency response of f.zero = 1/(2*pi*(R180+R182)*C_total) = 0.3835 [Hz]; f.pole = 1/(2*pi*R180*C_total) = 10.6103 [Hz]; I attach a plot that shows the ratio of the this "circuit component value ideal" response to approximate response, and the response ratio hits 7.5% by 10 Hz and ~11% by 100 Hz. This is, of course for one OSEM channel's signal chain. I haven't modeled how this systematic error in compensation would stack up with linear combinations of slight variants of this response given component value precision/accuracy, but ... ... I also am quite confident that no one really wants to go through an measure and fit the zero and pole of every OSEM channel's sat amp frequency response, so maybe you're doing the right thing by "just" measuring it with this technique and compensating for it in the SENSALIGN matrix. Or at least measure one sat amp box's worth, and see how consistent the four channels are and whether they're closer to 0.4:10 Hz or 0.3835:10.6103 Hz. Anyways -- I thought it might be useful to be aware of the many steps along the way that we've been lazy about the details in calibrating the OSEMs, and this would be one way to "fix it in hardware."