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).
Data attached with filename shown on screenshot.
Type | Time (UTC) | SRCL | Angle | DTT Ref |
No SQZ | 16:01:00 - 16:15:00 | N/A | N/A | ref 0 |
FIS | 16:20:30 - 16:23:30 | -191 | (CLF-) 174 | ref1 |
FIS | 16:27:30 - 16:30:30 | -90 | (CLF-) 218 | ref2 |
FIS | 16:35:00 - 16:38:00 | 0 | (CLF+) 107 | ref3 |
FIS | 16:42:00 - 16:45:00 | -290 | (CLF-) 146 | ref4 |
FIS | 16:48:00 - 16:51:00 | -390 | (CLF-) 129 | ref5 |
Note that I left the OPO servo gain at -8, but we have previously used -12dB for 120uW OPO trans (83370)
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 | -8 |
The squeezer unlocked, then relocked from 1521-1526UTC. The SQZ_OPO_LR node now has the message "pump fiber rej power in ham7 high, nominal 35e-3, align fiber pol on sqzt0".
Today Francisco and I went down to the End station to make an End X measurement using PS4.
He took some time to do a Beam Spot move, and then we got started on the ES measurement following the instructions in the T1500062 Procedures and Log .
I did happen to look inside the RX sphere when swapping spheres and saw a small black dot on the spectralon on the inside of the shpere. It actually looks like it may be some tiny pitting in the spectralon shell.
(pcal_env) tony@LHOGC000360:~/Documents/PCAL/git/pcal/O4/ES/scripts/pcalEndstationPy$ python generate_measurement_data.py --WS "PS4" --date "2025-03-24"
Reading in config file from python file in scripts
../../../Common/O4PSparams.yaml
PS4 rho, kappa, u_rel on 2025-03-24 corrected to ES temperature 299.4 K :
-4.701550919294612 -0.0002694340454223 4.0632996079052654e-05
Copying the scripts into tD directory...
Connected to nds.ligo-wa.caltech.edu
martel run
reading data at start_time: 1426956240
reading data at start_time: 1426956650
reading data at start_time: 1426956970
reading data at start_time: 1426957350
reading data at start_time: 1426957720
reading data at start_time: 1426958030
reading data at start_time: 1426958180
reading data at start_time: 1426958960
reading data at start_time: 1426959280
Ratios: -0.46129682487781465 -0.4660359949229844
writing nds2 data to files
finishing writing
Background Values:
bg1 = 8.837346; Background of TX when WS is at TX
bg2 = 5.591501; Background of WS when WS is at TX
bg3 = 8.780952; Background of TX when WS is at RX
bg4 = 5.680601; Background of WS when WS is at RX
bg5 = 8.772249; Background of TX
bg6 = 0.562586; Background of RX
The uncertainty reported below are Relative Standard Deviation in percent
Intermediate Ratios
RatioWS_TX_it = -0.461297;
RatioWS_TX_ot = -0.466036;
RatioWS_TX_ir = -0.455766;
RatioWS_TX_or = -0.460962;
RatioWS_TX_it_unc = 0.088015;
RatioWS_TX_ot_unc = 0.088093;
RatioWS_TX_ir_unc = 0.093864;
RatioWS_TX_or_unc = 0.092606;
Optical Efficiency
OE_Inner_beam = 0.988107;
OE_Outer_beam = 0.989162;
Weighted_Optical_Efficiency = 0.988635;
OE_Inner_beam_unc = 0.059352;
OE_Outer_beam_unc = 0.059902;
Weighted_Optical_Efficiency_unc = 0.084326;
Martel Voltage fit:
Gradient = 1636.730463;
Intercept = 0.022399;
Power Imbalance = 0.989831;
Endstation Power sensors to WS ratios::
Ratio_WS_TX = -1.078361;
Ratio_WS_RX = -1.391797;
Ratio_WS_TX_unc = 0.053544;
Ratio_WS_RX_unc = 0.043735;
=============================================================
============= Values for Force Coefficients =================
=============================================================
Key Pcal Values :
GS = -5.135100; Gold Standard Value in (V/W)
WS = -4.701551; Working Standard Value
costheta = 0.988362; Angle of incidence
c = 299792458.000000; Speed of Light
End Station Values :
TXWS = -1.078361; Tx to WS Rel responsivity (V/V)
sigma_TXWS = 0.000577; Uncertainity of Tx to WS Rel responsivity (V/V)
RXWS = -1.391797; Rx to WS Rel responsivity (V/V)
sigma_RXWS = 0.000609; Uncertainity of Rx to WS Rel responsivity (V/V)
e = 0.988635; Optical Efficiency
sigma_e = 0.000834; Uncertainity in Optical Efficiency
Martel Voltage fit :
Martel_gradient = 1636.730463; Martel to output channel (C/V)
Martel_intercept = 0.022399; Intercept of fit of Martel to output (C/V)
Power Loss Apportion :
beta = 0.998895; Ratio between input and output (Beta)
E_T = 0.993751; TX Optical efficiency
sigma_E_T = 0.000419; Uncertainity in TX Optical efficiency
E_R = 0.994851; RX Optical Efficiency
sigma_E_R = 0.000419; Uncertainity in RX Optical efficiencyForce Coefficients :
FC_TxPD = 7.896238e-13; TxPD Force Coefficient
FC_RxPD = 6.188319e-13; RxPD Force Coefficient
sigma_FC_TxPD = 5.403288e-16; TxPD Force Coefficient
sigma_FC_RxPD = 3.778561e-16; RxPD Force Coefficient
data written to ../../measurements/LHO_EndX/tD20250325/
Martel Voltage Tests
WS_at_RX.png
WS_at_RX_BOTH_BEAMS.png
WS_at_TX.png
LHO_EndX_PD_ReportV5.pdf
This adventure has been brought to you by Matt Todd, Francisco L. & Tony Sanchez.
TITLE: 03/26 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.22 μm/s
QUICK SUMMARY: Locked for 3 hours, calm environment, no alarms. The violins are still slowly coming down, at 5e-16 in DARM atm. The usual ITMY modes 5&6 are the culprits. There is some planned extra commissioning time today coordinated with LLO.
TITLE: 03/26 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Lost lock a few minutes ago unfortunately. Reason still unknown. We had just gotten back up to Observing less than 30 minutes ago after an earlier unknown lockloss at 02:21 UTC (Here is the sunset from the overpass at the time of that lockloss - Photo credit to Francisco)
LOG:
23:30UTC In OMC_WHITENING damping violins
23:35 NOMINAL_LOW_NOISE
23:37 Observing
01:54 Superevent S250326y
02:21 Lockloss (Lockloss Desert View - P.C. Francisco)
- Lost lock at RESONANCE, decided to run an initial alignment since PRMI/DRMI had trouble right before
04:33 NOMINAL_LOW_NOISE
04:35 Observing
04:57 Lockloss
04:33 Back Observing
Closes FAMIS#26035, last checked 83269
Script reports that noise is elevated for:
ETMY_ST2_CPSINF_V2
Overall, elevated noise in the corner station seen between 7.6 and 9 Hz in various sensors.
I also noticed that the noise between 0.1 and 1 Hz falls off slightly faster this week as compared to last week, getting down to 1.5e-9 before 1 Hz, versus last week the sensors were still reading 5e-9 at 1 Hz.
HAM2
- The peak in V2 and V3 at 10.5 Hz is a bit larger
HAM2/HAM3/HAM4/HAM5/HAM6
- H3/V3 have peaks between 7.6 to 9 Hz that are up to half an order of magnitude higher than those frequencies were last week
ITMX ST1
- Increased noise between 7.6 to 9 Hz in all (I think) sensors
ITMX ST2
- Increased noise at 7.6 Hz in H3
ITMY ST1
- Slightly elevated noise between 7.6 to 9 Hz in H1/H3/V1/V3
ITMY ST2
- Slightly elevated noise between 7.6 to 9 Hz in all (I think) sensors
BS ST1
- Slightly elevated noise between 7.6 to 9 Hz in V1/V2/V3
BS ST2
- Slightly elevated noise between 7.6 to 9 Hz in all (I think) sensors
Back to observing after finishing maintenance and then damping violins for over 2 hours. Accepted a few SDFs related to ALS and that's it.
TITLE: 03/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Busy maintenance day mostly focused on preparing cabling for HAM1 ISI installation. After that wrapped up, ran an initial alignment with some code testing, then H1 was able to lock without issue and fully automatically. Had to wait in OMC_WHITENING to damp violins (likely my fault for breaking lock during powerup this morning).
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
14:38 | FAC | Kim | EX | N | Technical cleaning | 16:04 |
14:49 | FAC | Chris | X-arm | N | Tumbleweed clearing | 19:58 |
14:58 | CAL | Tony, Francisco | PCalLab | Local | Prep for measurements | 15:28 |
15:00 | FAC | Tyler | Staging | N | Moving ISI container; shop -> staging | 15:43 |
15:11 | CDS | Erik | CR | N | Rebooting FOMs | 15:11 |
14:38 | FAC | Nellie | EY | N | Technical cleaning | 15:17 |
15:27 | IAS | Jason, RyanC | LVEA | N | FARO surveying | 19:14 |
15:29 | CAL | Tony, Matt, Francisco | EX | YES | PCal measurements | 17:58 |
15:34 | AOS | Camilla | LVEA/OptLab | N | Putting away parts | 15:59 |
15:36 | CDS | Fil, Marc | LVEA/CER | N | HAM1 field cabling | 19:25 |
15:43 | VAC | Travis, Janos | EX | N | Compressor work | 18:25 |
15:44 | FAC | Tyler | CS/MX/MY | N | 3IFO and capital inventory | 19:44 |
15:46 | VAC | Richard | LVEA | N | Turn on roughing pump panel | 17:07 |
15:59 | VAC | Jordan, Janos | LVEA | N | Bringing parts in via FC door | 17:07 |
15:59 | FAC | Tyler, Contractor | H2 Building | N | HVAC work | 19:59 |
16:02 | FAC | Mitchell | LVEA | N | Clearing off SEI racks | 17:12 |
16:05 | FAC | Kim | LVEA | N | Technical cleaning | 18:54 |
16:08 | AOS | Betsy | LVEA | N | Checking on progress | 16:25 |
16:14 | SEI | Jim | LVEA | N | Checking on progress | 17:12 |
16:19 | TCS | Camilla | OptLab | N | Grabbing parts | 16:23 |
16:21 | ISC | Mayank, Jennie | OptLab | Local | ISS array work | 20:52 |
18:12 | SEI | Jim | LVEA | N | Testing loadcell readers | 18:27 |
19:15 | CDS | Richard | LVEA | N | Talking to Fil and Marc | 19:21 |
19:17 | AOS | Jason | OptLab | - | Inventory | 19:28 |
19:30 | OPS | Camilla | LVEA | N | Sweep | 19:45 |
20:36 | CDS | Marc | CER | N | Listening for power supplies | 21:07 |
20:54 | ISC | Keita, Mayank | OptLab | Local | ISS array work | 22:45 |
21:22 | TCS | Camilla, Matt | OptLab | Local | CO2 laser work | 22:30 |
TITLE: 03/25 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: SEISMON_ALERT
Wind: 3mph Gusts, 1mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.25 μm/s
QUICK SUMMARY:
Waiting in OMC_WHITENING still while damping violins. We're pretty close so hopefully will be getting into NLN soon.
J. Kissel, O. Patane, B. Lantz After seeing my post of the current (2025-03-19) performance of the H1ISIBS in LHO:83470, Brian -- in his LHO:83473 comment -- rightly cautioned Oli to beware the difference between (1) a "statistical" or "incoherent" model of the CART2EUL projection to the suspension point, where . one takes the ASDs of the CART DOFs (which are inherently only containing amplitude information, no phase relation between channels), . multiplies them by the CART2EUL coefficients, and . takes the quadrature sum to form an ASD model of the euler basis motion, vs. (2) a "linear combination" or "coherent" model of the CART2EUL project to the suspension point, where . the time-series of each CART DOF are multiplied by the CART2EUL coefficients, . the time-series are then coherently summed (where "coherently" summed just means the amplitude AND phase relationship between the channels has been preserved), and . then an ASD is taken of that to form an ASD model of the euler basis motion. He states - "if the DOFs are independent (which maybe they are, and maybe they are not), then using the quadruture sum of the ASDs, (1), is a reasonable thing to do." and - "I think this difference [between (1) and (2)] not going to impact any of your calculations" I'd not seen a comparison of these two models either at all or in a long time, every chamber + SUS combination is different, and I had the data, so I made the comparison. I'll discuss the 6 Euler Basis plots in reverse-traditional order, because they're easiest to understand progressively that way. YAW This plot is uninteresting, because the BS projection matrix from CART to EUL has only one unity element, mapping RZ directly to Yaw. However, it lets me introduce what I'll be plotting. In the upper panel, this shows the both models of ASDs and the underlying Cartesian components multiplied by the CART2EUL matrix element. As expected here, the thick black dashed ASD -- the coherent sum (2) model -- is identical to that think magenta dashed ASD -- the incoherent sum model (2). The lower panel is the ASD ratio of the linear sum (2) divided by the incoherent sum (1). Of course, for this DOF, the two models are identical, so this ASD ratio is identically 1.0 across the whole frequency band. With me so far? Good. :-P PITCH Here, because the Beam Splitter suspension is mounted in the center of the ISI BS optical table, yaw'd 45 degrees, RX and RY map to PITCH via sqrt(2) with the same sign. But the RX and RY performance of the ISI BS is slightly different, so the ratio between (2) and (1) is interesting. Most notably around the HEPI cross-beam foot resonance (traditionally called the "HEPI Pier resonance" prior to 2014; see LHO:13505) -- the broad feature at ~7 Hz -- where the ASD ratio shows that the incoherent sum model (1) under predicts Sus. Point displacement by a factor of ~1.35x w.r.t. the coherent sum model (2). And then at some other feature at ~17 Hz, the incoherent sum model (1) is over predicting the Sus. Point displacement by ~(1/0.8) = 1.25x. ROLL OK, now flip the sign of the contribution of RY, and watch the coherent sum drop -- fascinating! The contribution of that same ~7 Hz feature is now dramatically over-predicted by the incoherent sum, by a factor of ~(1/0.4) = 2.5x. Are these two the inverse of each other? No! I don't show it explicitly, but comparing (2)/(1) for roll (the inverse of what's plotted) and (1)/(2) for pitch, the 7 Hz number is 0.74x and 0.52x respectively, so markedly different! VERTICAL Now we're getting really interesting -- for vertical, Z is mapped one-to-one, but RX and RY are contributing in opposite sign, and with only *roughly* the same magnitude [m/rad] CART2EUL coefficient. The incoherent sum (1) is overestimating the vertical displacement by as much as a factor of ~(1/0.2) = 5x where the vertical motion is limited by RX and RY between 0.5 and 3 Hz. Wow! I won't look type thru the rest of the plot, because the plot describes it best, but boy is it more interesting than I thought it would be. TRANSVERSE With transverse, even though this degree of freedom "doesn't matter" for the beam splitter, now we're cooking with 5 contributing Cartesian degrees of freedom and except for RZ they're all contributing at interesting levels. Again, you reading the plot is more useful than me describing it here, but it's quite interesting that the linear sum (2) predicts more motion between 0.6 Hz and 3.5 Hz and the incoherent sum (1) predicts more motion overestimates the motion between 3.5 to 15 Hz. LONGITUDINAL Finally, the DOF we work the hardest on, shows contribution from all 5 Cartesian degrees of freedom. A lucky-coincidence perhaps, but it looks like the models are about the same for most of the frequency region, and the incoherent sum (1) is over-predicting the displacement between 3.5 to 15 Hz, which is re-enforcing Brian's comment. WHAT DOES IT ALL MEAN? Brian is, again, definitely right to call out that the linear sum (1) model is a better model of the displacement of the Sus. Point than the incoherent sum. But, both I (and perhaps even he) definitely wasn't expecting factors of 2x discrepancy, let alone factors of 5x. So, I think I might make Brian's conclusion from LHO:83473 a little stronger -- the difference between models will impact the calculations of the Bigger Beam Splitter Suspension (BBSS) performance, so for the update to the seismic input motion, I'll *not* just update the performance from the ~2005 seisBSC.m estimate to the current 2025 real *cartesian* performance incoherently projected to the Sus Point, but instead update it to the current 2025 real *euler* Sus. Point performance computed in the front-end.
Brian says: "huh. I'm not happy about being right here. Something is wrong with that ISI. This means there is very strong coupling between Z and RX/RY on that table, something I've been worried about for a while, but not able to improve. This was just supposed to be a 'thing to keep in mind when checking your work'." This forced me to look at my own plots again with a different lens, that I think is worth sharing: "Mmm -- maybe you're thinking too fast here -- the RX/RY coupling to Sus Point Vertical is entirely via geometry, not anything funky with the cross-coupling within the ISI DOFs. Sure, improving RX/RY would help by whatever way you want, but this doesn't point fingers at any internal, ISI, RX/RY to Z (or vice verse) coupling. But also -- the good news is that we "improve" the Sus. Point vertical motion for the BS by a factor of 5x at 0.5 Hz just by showing the better math'ed projection! And actually -- now that I stare at the V plot more closely, the *coherent* V motion (the black-dashed trace) is not limited by RX or RY *anywhere*: - Where the RY/RX component motion is comparable to Z component (say, between 0.5 Hz and 3 Hz), apparently, the *differential* RX / RY motion is smaller than the component, and - Where the RX/RY component motion is clearly different from each other (between 5 and 30 Hz), the Z motion is far larger anyways." But, back to Brian's worry about this ISI's performance -- remember to head to LHO:83530 for discussion :: yes, this is one of the worst performing ISIs and we don't know why.
The Kepco Power Supply for SUS-C4 started chirping at the end of maintenance today. By 2pm the chirping is more regular. The draw on the supply is 7A, typical failing fans last a few days once they get to this stage. We should replace this one before the weekend, as a target of opportunity. Down time will be 30 mins start to finish.
M. Pirello, F. Clara
Due to earthquake we took a window of opportunity to replace the SUS-C4 Kepco Power Supply which controls HAM1 and HAM2 suspensions. These suspensions were placed into safe and the supply replaced. We replaced only the -18V supply, the +18V matching supply was replaced in December 2022 so we left it in place.
M. Pirello, F. Clara
FranciscoL, TonyS, MattT, RickS
On Tuesday, March 25, we reverted the PCALX lower beam to its nominal center. We expect to see a change of 4 HOPs in \chi_XY -- returning to the value it was two week ago.
Target was placed with a 33 degree offset as seen on the first attachment (TARGET_ON -- featuring a responsible scientist, wearing laser goggles). Each individual beam voltage values, as found, were very similar to the values recorded at the end of the move done last week.
The following table shows the voltage values as read by the Keithley voltmeter we use during the procedure
Step | Comment | Readout [V] |
---|---|---|
1 | Both beams - target off | 3.379 |
2 | Both beams - target on (as found) (BEFORE_MOVE) | 2.937 |
3 | Lower beam after actuation | 1.395 |
4 | Both beams - target on (AFTER_MOVE) | 2.903 |
5 | Both beams - target off | 3.394 |
The IFO has not regain lock at the time of writing this alog which limits further observations from this move.
WP 12393
The FE and IO chassis for h1seih16 were powered down for in-rack cabling of the ISI electronics. All cables are now routed and dressed. The long field cables were left disconnected, will wait until they are in connected at the flange.
The AI chassis on U38 was removed. AA chassis from U39 was moved down. This matches LLO's rack configuration, alog 75328.
CDS Team
RyanC, TJ
I wrote a new decorator in ISC_library (@ISC_library.bring_unlocked_imc_2w_decorator(nodes)) for the specific scenario of the IMC losing lock while we're at 10Ws which would give it trouble relocking - alog82436. The decorator looks for the IMC being unlocked with a power above 2Ws and if the rotation stage is stationary it requests the LASER_PWR GRD to 2Ws.
We sprinkled the decorator into ALIGN_IFO, INIT_ALIGN, into the MICH, SRC and AS_CENTERING states, I also added it to CHECK_MICH_FRINGES and MICH_OFFLOADED in ISC_LOCK. We successfully tested it today during an initial alignment by breaking the IMC lock during these states.
TITLE: 03/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.25 μm/s
QUICK SUMMARY: H1 is currently relocking up to MOVE_SPOTS. Looks like H1 was able to lock twice last night and most recently lost lock about an hour ago. Maintenance day today, but I'll let H1 continue until those activities begin.
Halted locking for the start of maintenance day. ISC_LOCK to 'IDLE' and seismic environment to 'MAINTENANCE' at 14:40 UTC.
Power cycling the dust monitor did not help, later in the day I restarted the IOC using telnet which was successful.
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."