Displaying reports 4621-4640 of 83188.Go to page Start 228 229 230 231 232 233 234 235 236 End
Reports until 10:38, Tuesday 29 October 2024
LHO VE
david.barker@LIGO.ORG - posted 10:38, Tuesday 29 October 2024 (80915)
Tue CP1 fill

Tue Oct 29 10:08:04 2024 INFO: Fill completed in 8min 0secs

Gerardo confirmed a good fill curbside.

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 08:48, Tuesday 29 October 2024 - last comment - 10:37, Tuesday 29 October 2024(80913)
Fire pump running, test alarms and reporting

Eric is running the fire pumps this morning for maintenance. This is a good opportunity to test CDS reporting and alarms. Attached MEDM shows CDS Overview with a red fire pumps button, it opens the FMCS overview (also shown). I let the first three cell phone alarm texts to proceed and then bypassed this alarm for the remainder of this morning.

Bypass will expire:
Tue Oct 29 08:41:08 PM PDT 2024
For channel(s):
    H0:FMC-CS_FIRE_PUMP_1
    H0:FMC-CS_FIRE_PUMP_2
 

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 10:37, Tuesday 29 October 2024 (80914)

Bypass has been removed

H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 08:21, Tuesday 29 October 2024 (80912)
H1 ISI CPS Noise Spectra Check - Weekly (Famis 26015)

FAMIS Link:  26015

Only CPS channels which look higher at high frequencies (see attached) would be the following (which have been like this on the order of weeks):

  1. ITMx St1 V1
  2. ITMy St1 V2
  3. ETMy St1 H2
Non-image files attached to this report
H1 SUS
oli.patane@LIGO.ORG - posted 08:10, Tuesday 29 October 2024 (80911)
TMTS TF check to verify corrected Coil Driver Strength

In 80171, we noted that the incorrect coil driver strength had been in use for getting the calibration in plotTMTS_dtttfs.m. We corrected this value and last week I was able to take transfer function measurements of the TMTs, which we wanted to take just so we could verify that the updated calibration was more accurate to the models, and also just because it had been four and two years since taking measurements for TMSX and TMSY, respectively.

I've attached the pdfs for their individual analyses (TMSX, TMSY), as well as comparisons between the most recent and previous measurements (TMSX, TMSY). The corrected coil driver strengths do shift the measurement traces up closer to the model traces.

Non-image files attached to this report
H1 General
oli.patane@LIGO.ORG - posted 07:38, Tuesday 29 October 2024 (80910)
Ops Day Shift Start

TITLE: 10/29 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.25 μm/s
QUICK SUMMARY:

Maintenance day today

H1 CDS
erik.vonreis@LIGO.ORG - posted 06:57, Tuesday 29 October 2024 (80909)
Workstations updated

Workstations were updated and rebooted.  This was an OS packages update.  No conda packages were updated.

LHO General
thomas.shaffer@LIGO.ORG - posted 18:41, Monday 28 October 2024 (80905)
Ops Shift End

STATE of H1: Corrective Maintenance
SHIFT SUMMARY: PSL team made major progress and was able to get the second amplifier to output 140W! They will continue work tomorrow to wrap it up.
LOG:                                                                                                                                                                                                                                                                                       

Start Time System Name Location Lazer_Haz Task Time End
16:34 SAF LVEA LVEA Y LVEA is LASER HAZRD 23:50
14:57 TCS Camilla Mech room N Chillers check 15:01
15:02 FAC Karen Optics lab, vac prep N Tech clean 15:33
15:51 FAC Karen Garb room/LVEA Y Tech clean 16:24
16:14 FAC Kim MidX N Tech clean, back 16:55 17:27
16:29 FAC Karen EndY N Tech clean 17:27
16:47 EE Marc, Fernando PSL racks / CER N Investigate racks 17:00
16:50 PSL Jason, RyanS PSL room Y NPRO swap, AMP1 20:11
21:31 PSL Jason, Ryan PSL encl. local NPRO swap, AMP2 00:06
21:34 CDS Fernando, Marc CER Y Powering 35Mhz back up 21:40
22:49 SQZ Camilla, Vicky LVEA YES SQZT0  table work 23:22
H1 PSL
jason.oberling@LIGO.ORG - posted 17:58, Monday 28 October 2024 (80908)
PSL NPRO Swap: It Lives! (WP 12155)

R. Short, J. Oberling

Continuing from the weekend.

First thing this morning Marc and Fernando turned off the 35.5MHz RF so we could swap the in-service EOM for the spare, as we had observed no beam distortions with the spare and having RF shouldn't change that.  We installed and aligned the spare and then moved on with recovering Amp1.  With the amp not being pumped we had 1.7W incident and 1.43W in transmission; after tweaking the alignment there was 1.55W in transmission (91.3% throughput, well above our 65% requirement).  We also preemptively turned the HWP on the High Power Attenuator (HPA) assembly after Amp1 to pass a minimum amount of power, so it was ready for Amp2 alignment checks.  We slowly increased the pump diode currents in 1A steps, keeping both diodes the same on the way up, and tweaked beam alignment into the amplifier at each step.  The power output by the amplifier was monitored with our roving 300W-capable water-cooled power meter.  The results:

Injection Current (A) Initial Power (W) Final Power (W)
1.0 1.7 1.7
2.0 1.9 2.0
3.0 3.4 9.1
4.0 17.8 18.2
5.0 28.4 28.7
6.0 39.0 39.2
7.0 49.2 49.3
8.0 58.9 58.9
9.0 68.3 68.3

To end we had power supply 1 @ 9.2A and power supply 2 @ 9.0A, to have most of our pump diodes monitors back at 100%; monitor for pump diode 3 (which is actually pump diode 1, the software is flipped; 3 and 4 are actually 1 and 2, with 1 and 2 actually being 3 and 4) is right below 90% while the rest are right below 100%, indicating pump diode 1 has seen the most degradation since install.  With these pumping currents we had 68.9W out of Amp1, so we aligned the beam onto the Amp1 power monitor PD and recalibrated it; we also recalibrated the NPRO power monitor PD as it turned out our original calibration was done with WP14 not fully optimized.  We then checked beam alignment up to Amp2, which all looked good.  We installed a temporary PBSC after M07 to check the polarization of the light incident on Amp2.  We turned the power in the Amp2 path up to ~3.55W (>5% of Amp1 output, to avoid the HPA causing any polarization weirdness).  PBSC transmission was measured at 0.47mW, and tweaking WP04 only got this down to 0.45mW, so polarization looked good.  We turned the power to ~1.71W in prep for Amp2 recovery, and measured the power transmitted through Amp2 with no pump light; this measured at 1.4W, a throughput of 81.9%.  At this point we broke for lunch.

After lunch we started recovering Amp2.  We didn't do any pre-alignment work, as our throughput was already higher than the 65% requirement so we started powering up Amp2 in the same way we did Amp1 (we stopped at 9.0A as that was where Amp2 was running before the NPRO swap).  The roving power meter was placed directly after L18, on the other side of the external shutter; we removed L18 on the off chance the laser power ablated any material from the power meter head.  We also pre-set the HPA after Amp2 to pass a minimum power in prep for alignment checks from Amp2 to the PMC.  Results of Amp2 recovery:

Injection Current (A) Initial Power (W) Final Power (W)
1.0 1.5 1.5
2.0 2.9 2.9
3.0 8.9 9.2
4.0 18.1 18.3
5.0 28.1 28.3
6.0 38.2 38.3
7.0 47.8 47.8
8.0 56.7 56.8
9.0 64.2 64.2

With Amp2 now mostly recovered (still had to increase the seed beam power, it was still at ~1.7W) we checked alignment between Amp2 and the PMC while we had low power in that path (L18 was reinstalled for this).  Everything here looked really good still.  We installed the cover onto the ISS AOM and the beam was nice and centered.  We then removed L18 again and reinstalled our roving power mete to increase the seed power into Amp2.  Ryan slowly increased the seed using the HPA after Amp1 while I watched all of the optical elements in the path with an IR viewer for any signs of early burn spots.  Everything went smoothly and at max Amp2 seed we have 141.3W out of Amp2.  We realigned the beam onto the Amp2 power monitor PD and recalibrated it in the Beckhoff software.  To finish for the day we closed the external shutter and turned on the power and PD watchdogs, as well as the NPRO noise eater.  The amplifiers are running overnight with the enclosure in Science Mode for more data gathering for glitches.  Tomorrow we will begin recovering the PSL stabilization systems.

H1 PSL
sheila.dwyer@LIGO.ORG - posted 11:22, Monday 28 October 2024 - last comment - 11:20, Thursday 31 October 2024(80902)
comarison of new and old PSL glitches

Continuing on from Jenne's observation that there are still glitches in the new NPRO, I've tried to make a plot we can use to compare the glitch rate in the new and old NPROs, using the NPRO_PWR channel instead of the FSS channel which isn't available for the new NPRO. 

I've used a 3 hour stretch of observing time for the old NPRO, and a three hour stretch before the time when Jenne made a plot in 80837.  The ISS is not on for the new NPRO time, which is probably why the intensity is flcutuating and making it harder to see the small steps in power that are the glitches we are looking for.  In the second panel, I've plotted the data high passed with a 0.05 Hz butterworth, this helps to show the glitches, although not perfectly (in either case).  Based on this, the glitches look to be happening at a roughly similar rate, although somewhat less with the new NPRO.

This script in in sheila.dwyer/DutyCycle)4/dutycycleplots/PSL_glitches.py

Images attached to this report
Comments related to this report
brian.lantz@LIGO.ORG - 16:04, Monday 28 October 2024 (80906)
sheila.dwyer@LIGO.ORG - 11:42, Monday 28 October 2024 (80903)

Attaching another plot, showing that comparing our old NPRO to LLO during an observing stretch that started at midnight UTC time on Oct7th, LLO has no similar glitches.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 14:26, Tuesday 29 October 2024 (80921)

Here's the same plot, but using a time from last night when the PSL environmental controls were off.  There are still gltiches, but fewer.

Images attached to this comment
victoriaa.xu@LIGO.ORG - 14:23, Wednesday 30 October 2024 (80947)

These plot tiles show runs of Sheila's code looking for PSL power glitches on several days before / after the suspect date around Sept 12.

There's not a clear correlation between the glitches and locklosses. While maybe there's more glitches after Sept 12 (bottom row), the glitches don't consistently correlate with locklosses? Sept 14 is a good example of this: lots of glitches, the IFO stays locked through many of them.

2nd plot here shows overnight again with the swapped new laser. There are still glitches (though potentially less). 

Images attached to this comment
Non-image files attached to this comment
sheila.dwyer@LIGO.ORG - 15:21, Wednesday 30 October 2024 (80948)

The PSL-PWR_NPRO_OUT_DQ channel seems to not be connected at LLO, which explains why the comparison plot a few comments above makes it look like L1 PSL is so much quieter than H1.

victoriaa.xu@LIGO.ORG - 11:20, Thursday 31 October 2024 (80973)

Adding screenshot of the NPRO power glitches over the past day. There are still glitches with the new laser -- not all glitches correspond to locklosses, but some do.

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 10:16, Monday 28 October 2024 (80901)
Mon CP1 Fill

Mon Oct 28 10:11:10 2024 INFO: Fill completed in 11min 6secs

Travis confirmed a good fill curbside. TC-B slightly off.

Images attached to this report
H1 PSL (PSL)
marc.pirello@LIGO.ORG - posted 10:06, Monday 28 October 2024 (80900)
Powered Down 35.5MHz Amplifier in CER for PSL EOM work (WP12169)

Working with Jason and with advice from Daniel, we powered down the 35.5MHz RF Amplifer in the CER at 10am PST.  We will power it back up when the EOM work is complete.

 F. Mera, J. Oberling, R. Short, M. Pirello

LHO General
tyler.guidry@LIGO.ORG - posted 08:01, Monday 28 October 2024 (80897)
DGR Storage Building Progress
Last week a bulk of the mobilization and earthwork began on the new storage building nearest the Staging Building. Footings are dug, and layout has begun. Beginning this week, the DGR team will shift from a 4-10 schedule to 5-8's as they start to build forms. They expect a forklift to be delivered sometime this morning and rebar to follow shortly after. The construction is presently ahead of schedule and the hope at this time is to begin pouring concrete as early as the end of next week.

T. Guidry 
Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 07:43, Monday 28 October 2024 (80896)
OPS Monday day shift start

TITLE: 10/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.52 μm/s
QUICK SUMMARY:

H1 TCS
thomas.shaffer@LIGO.ORG - posted 15:45, Friday 25 October 2024 - last comment - 08:11, Monday 28 October 2024(80882)
TCS X&Y Chiller Flush

Camilla C, Brice W, TJ S

Following the procedure written out by Alastair - T1600050 - today we did a full flush of both chiller lines with ~13gal each.

The last time a full flush was done, and not just refills from line leaks or chiller swaps, was back in 2016 (alog30017). This is notably, much longer than the 6mo service interval the manufacturer recommends. Just like back then, after turning off the lasers, power supplies, and AA chassis, we disconnected all electrical and tried to drain the chillers to start. We struggled to get much out of the chiller via the drain pipe, but a trickle would come out of the process input if the ball valve on the back of the chiller is set to a 45deg angle. After the chillers were mostly drained, we tried to wipe the reservoirs to get out any junk that was in there. We then set up a hose with a quick connect and connected it to the process input line and ran it to a bucket below the mezzanine to avoid carrying large quantities of water down those stairs (see attachment 1). The process output was hooked up to the chiller, then with two people on the mezzanine and one below to watch the bucket and hose, we turned on a chiller and filled the reservoir as the level dropped. We put about 13 gal through the system for each before turning off the chiller, which should be more than each system contains (alog30638).

Seperately, I noticed while we were swapping the TCSY laser that some of the 1/4" tubing connected to the RF driver felt softer than others also connected to it. Turns out, 2 of the 8 connected to it are a different type - Tygon 2001 (softer) vs Tygon2475. According to a data sheet I found, the 2001 has a max working pressure of  30psi compared to the 2475 max at 50psi. We should really think about replaing all of these lines post O4, but I'll need to look into how much pressue these lines actually have.

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 08:11, Monday 28 October 2024 (80898)

Checked on the chillers this morning, no extra water was needed, this means we didn't let much air into the system while flushing. Updated T2200289.

H1 SQZ
victoriaa.xu@LIGO.ORG - posted 09:58, Thursday 24 October 2024 - last comment - 11:18, Monday 28 October 2024(80830)
Initial beam profiling after GAOM1 (used for squeezer pump ISS)

Sheila, Daniel, Vicky

On Tuesday, Sheila and I took some beam profiles of the squeezer pump beam after the pump AOM used for ISS (GAOM1). This is trying to understand and fix the squeezer pump ISS issues that result from GAOM1 becoming misaligned on SQZT0.

Summary and proposed plan: the vertical beam profile we measured looks reasonable, the horizontal profile looks off (potentially related to measuring after the AOM). We could move GAOM1 closer to SHG by 1-2 holes to get closer to the beam waist of ~100um that is about 1.3m after SHG. While GAOM1 is out, we could re-measure the horizontal beam profile to make sure it is OK.

Here are plots of the pitch beam profiles we took before, and the very quick a la mode plot code that adapts Sheila's and Georgia's previous codes. I think the vertical beam profiles we took line up with Georgia's previous measurements and D1201210, which both say there should be a waist like 1.25m - 1.3m after SHG. In real life, we measured from z=0 at the EOM mount edge closest to GAOM1, to the face of the beam profiler (may need to take into account beam profile distance..).

So it seems possible that GAOM1 is like 0.02-0.05 meters (~2 inches?) downstream of the waist. From photos and SQZT0 layout D1201210, there is room to try moving GAOM1 closer to L15 (closer to SHG) by 1-2 holes.

Useful DCC references:

Images attached to this report
Non-image files attached to this report
Comments related to this report
victoriaa.xu@LIGO.ORG - 11:18, Monday 28 October 2024 (80899)

On Friday, Sheila and I measured some beam profiles of the SHG output path without the pump AOM and EOM, then moved GAOM1 ~1" closer to SHG than before (as we wanted to try: photo), and finally re-aligned through GAOM1 and the pump fiber. Overall, the squeezer pump ISS is working and ready.

With GAOM1 an inch closer to SHG, maybe GAOM1 alignment got smoother than before. We have an alignment that can optimize both 0-th order throughput and diffraction efficiency, which seemed problematic in recent realignments (eg 80266, 79993, 78519). With 43mW into GAOM1, we transmitted 40mW at 0V (so 40/43 = 93% throughput), while being able to diffract ~15mW at 5V (28.5 dBm), so ~35% diffraction efficiency. Seems ok-good compared to recent re-alignments.

On Friday, with 20 mW launched into the fiber, we had about  2 (BS50:50) * (2.2mW (opo_refl unlocked) + 1mW (opo_refl_rejected)) = 6.4mW through the fiber, so 6.4/20 ~ 32% throughput even with ~0.1mW mis-polarized light.

Given the questionable yaw beam quality when no parts are installed on the SHG output path, and the dependence of yaw beam profile on SHG temperature, it might require work on SHG to totally solve the beam quality issues. Unclear that further mode-matching adjustments will fix it.

  • First attchment here plots all the beam profile measurements from this round (friday and tuesday). Same as Tuesday. Pitch looks good. Yaw does not look consistent with pitch, and not quite gaussian either. 
  • See photos of the beam profiles in the second attachment here: the yaw profile degrades as we go further from SHG, while the pitch profiles look consistently good. Yaw profile looked bad even with no EOM or AOM installed, so it is a bigger issue. Could be related to SHG problems, since the yaw profile depends so much on SHG temperature. After adjusting the EOM alignment, the yaw beam looked more single-peaked after the EOM, but was still not a great gaussian (see photos), and it got worse as the beam propagated farther from SHG.
     

Update from Monday: Camilla and I went to SQZT0 and touched up pump fiber coupling. Also touched the alignment on pump GAOM1 to check.

  • GAOM1: with 47mW into the AOM, measured 40mW after the AOM (0V, ~85% throughput), with 5V diffracting 14.4mW into the 1st order mode (~35% diffraction). Slightly worse than Friday, but touching alignment didn't improve it (original alignment today was already the best).
  • Pump fiber: improved OPO_REFL from 1.7mW to 1.95mW.
Images attached to this comment
Non-image files attached to this comment
H1 SQZ
sheila.dwyer@LIGO.ORG - posted 15:52, Friday 18 October 2024 - last comment - 10:12, Friday 03 January 2025(80747)
homodyne angle sign, initial look at Camilla's data set

Vicky, Sheila

Summary:  Today we learned that frequency independent anti-squeezing is a very good way to determine which sign the homodyne angle is. 

Background: I've been working on using code from Vicky's repo and the noise budget repo to do some checks of a quantum noise model, this is in a new repo here

Details about how this model is made:

The first attached plot illustrates how these models and plots are made.  It starts with a no squeezing time, and an esitmate of non quantum noises from the noise budget, (dark gray, this one is from Elenna's recent run of the noise budget: 80603  ) and an estimate of the arm circulating power along with other parameters set in a quantum parameters file in the same format that is used by the noise budget.  It fits the readout losses by adding a gwinc model of quantum noise with the noise budget estimate of other noises, and adjusting the readout losses of the gwinc model, this is done from 1.5-1.8kHz in this case.

Based on this readoutlosses we get a model of quantum noise without squeezing, and subtract that from the no squeezing trace to get an estimate of the non-quantum noise.  This is enough different from the noise budget one that I've used that as the estimate of the non-quantum noise for the rest of the traces. 

By subtracting this subtraction estimate of the non-quantum noise, it estimates squeezing in dB, and finds a median level of dB from 1.5-1.8kHz for anti-squeezing and squeezing. This should be the same with and without the filter cavity, but in this data set there is slightly more anti-squeezing in the time without the filter cavity, so I've used FIS and FIAS to estimate the nonlinear gain and total efficiency for squeezing.  The nonlinear gain is translated into generated squeezing for gwinc, and the injection losses for squeezing are set so that the injection efficiency* readout efficiency = total squeezing efficieny. 

With this information we can generate models for anti-squeezing and squeezing traces, but fitting the squeezing angle to minimize or maximize quantum noise.  Then for the mid angle traces, the squeezing angle is fit to minimize the residual between the data and the quadrature sum of the subtraction estimate of non quantum noise and the model. We can then look at these plots and try manually changing parameter in the quantum parameter file.

Homodyne angle:

We've been stumped for a while about the excess noise we see with low frequency anti-squeezing, in 79775  I went through old alogs and see that we've had this mismatch of model with our data for a long time.  Today we tried flipping the sign of the homodyne angle and see that low frequency anti-squeezing is much closer to fit both with and without the filter cavity. Compare the 2nd and 3rd attachments to see this.

We still have more work to do on this model, including adding in the additional traces near squeezing and near anti-squeezing that Camilla took, and checking if it can give us any information about arm power (it doesn't seem very useful for that), or the mode mismatches. 

 

 

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 12:06, Monday 21 October 2024 (80797)

I neglected to mention that this is based on the nice data set that Camilla collected here: 80664, and that three is more work to be done with this, checking SRC detuning, mode mismatch, and including the +/- 10 deg data.

 

victoriaa.xu@LIGO.ORG - 12:04, Thursday 24 October 2024 (80820)SQZ

Sumary: seems the current (+) side of DARM is better for FDS, although it is opposite of our previous quantum noise models. But given the current sign is actually better for DARM, the model error doesn't really matter, and it's not really worth changing signs.

The wrong HD angle sign seems to be why none of our quantum noise models, despite fitting all other SQZ angles well, have ever fit FIAS properly. We will update our quantum noise models for the noise budget. Attached are some quantum noise models and DARM plots for Camilla's recent SQZ dataset lho80664.
 

Plots with optimal FDS (optimal fc detuning) for both signs of the homodyne angle: showing 1st just the quantum noise models without adding back non-quantum noise (NQN), and 2nd showing QN models + NQN.

  • Current sign of DARM (+) has solid lines. "Other" sign (-) has dashed lines.
     
  • Homodyne angle is only really obvious for FIAS (freq-indep anti-squeezing, turqoise traces).  It's almost indistinguishable for FIS otherwise (green, yellow, light blue). Marginally noticeable for FDS (but more sensitive to FC optimization).
    • Sheila made a super important observation that FIAS has never fit quantum noise models properly. 
    • Quantum noise models with the "other" (-) sign expect FIAS < No SQZ between 15-100 Hz, and FIAS < FIS between 15-50 Hz. This is not what we have observed with FIAS, despite QN models fitting all other SQZ angles fine.
    • Only flipping the HD angle sign was able to match the QN models to data, suggesting that previous quantum noise models used the wrong sign of the homodyne angle.
    • It turns out this doesn't really matter in real life, but we will update the noise budget models.
       
  • Confusingly, the current (+) side is better with FDS, but the "other" (-) side is better for unsqueezed DARM. See the grey (+) vs. black (-) traces for unsqueezed DARM at +/- 10 deg homodyne angles.
    • Not sure where the notion of a "good side of DARM" comes from
    • Pre-O4a, there was a quick test to lock on the other side of DARM, lho68080...  But maybe this test just shows some technical noises change with the HD angle?
      • In the test, see the plot of how unsqueezed DARM (purple vs. red) is very different below 100 Hz for the two signs, but not in the pway predicted by quantum noise models (grey + black traces).
      • So, seems like this test suggests the +/- sign measured DARM noise differences are more likely technical (non-quantum) noises that change with homodyne angle.

Third attachment (3rd) shows a wider range of homodyne angles, from +15 deg to -10 deg. So far the code for these plots is living here.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Altogether this is making progress on the quantum noise models for the noise budget!

Summarizing updates and what we're learning:

  • As Sheila said, low freq frequency-independent anti-squeezing (FIAS) ---> homodyne angle (which sign it is + approx how many degrees): see light blue FIAS traces in 2nd plot.
  • As in lho80318 79951, can use the frequency-independent squeezing (+mid-sqz) bronchosaurus (FIS) ---> SRCL detuning. 
  • Subtracted FDS data still WIP as the low frequency quantum noise estimate seems not totally right.
    • Maybe could fit the FC detuning at each SQZ angle (as SQZ angle can affect the RLF-CLF offset for such low (sub-linewidth) FC detunings), but haven't thought about this FDS data much yet.
  • Important model degeneracies remain from having 4 model unknowns: [[ IFO arm power + readout loss, and SQZ NLG + injection loss ]] with which to fit 3 DARM measurements [[ unsqueezed shot noise + anti-squeezing (kHz level) + squeezing (kHz level) ]].
  • Still need to factor in mode-matchings.
Images attached to this comment
sheila.dwyer@LIGO.ORG - 22:41, Monday 28 October 2024 (80877)

Vicky, Sheila

Based on the fit of total squeezing efficiency and nonlinear gain (which is based on subtracted SQZ and ASQZ from 1.5-1.8kHz), and known losses from loss google sheet, we can infer some possible maximum and minimum arm powers using the no squeezing data. 

The first attachment shows the same plot as above, but with the latest jitter noise measured by Elenna in 80808 We noticed this afternoon that there is a problem with the way these jitter noises are being added in quadrature by the noise budget, but we haven't fixed that yet.  In this data set, we have 15.1dB of anti-squeezing and 5.1dB of squeezing from 1.5-1.8kHz, we can use the Aoki equations to solve for nonlinear gain of 14.6 and total efficiency eta for squeezing of 73%.  Since the known readoutlosses are 7.3% and the known squeezer injection losses are 8.8%, this gives us a minimum readout efficency of (eta/(1-known injection loss) = 79% and a maximum of 1-known readout loss = 91.2%.  Using the level of noise between 1.5-1.8kHz with no squeezing (and an estimate of the non quantum noise) we can use these max and min readout efficencies to find min and max circulating powers in the arms. 

These arm power limits will be impacted by our estimate of the non-quantum noise, the homodyne angle, and the SRC detuning.  With 0 SRC detuning, and a homodyne angle of 7 degrees, this resutls in a range of arm powers of 324-375kW.  the estimate of non-quantum noise is the most important of these factors, while SRC detunings large engouh to change these estimates significantly seem outside the range that is allowed by other squeezing mesurements.

  • If I reduce the technical noise estimate from the noise budget by 10% in the ASD, the arm power range is 330-383kW, raising the non quantum estimate by 10% gives a range of 328-375kW.
  • Using a homodyne angle of 10.6 degrees instead of 7 gives an arm power range of 331-383kW. 
  • using an SRC detuning of 0.48 degrees (which is clearly too large based on the mid frequency squeezing) results in a range of powers of 321-372kW. 

I've run the comparison of the model to different squeezing configurations for the low and high range and the nominal parameters (0 SRC, 7 degrees homodyne angle). Frequency independent squeezing and both types of mid squeezing are sensitive to the arm power from 50-100Hz, this comparison shows that the low end of the arm power range seems to have slightly too little arm power and the high range slightly too much.  However these frequencies are also sensitive to homodyne angle and SRC detuning. 

Images attached to this comment
H1 SEI (CSWG, ISC, SEI, SUS, SYS)
jeffrey.kissel@LIGO.ORG - posted 13:04, Tuesday 15 October 2024 - last comment - 16:07, Monday 28 October 2024(80683)
Measurements of HAM2ISI to/from SUS PR3 Sus Point and M1 Stages Successful, But Incomplete
J. Kissel
WP 12140

I've completed 6 SUS + 4 ISI = 10 of 12 total DOF excitations that I wanted to drive before I ran out of time this morning. Each drive was "successful" in that I was able to get plenty of coherence between the 4 DOFs of ISI drive and SUS response, and some coherence between 6 SUS drive DOFs and ISI response. As expected, the bulk of the time was spent tuning the ISI excitations. I might have time to "finish" the data set and get the last two missing DOFs, but I was at least able to get both directions of LPY to LPY transfer functions, which are definitely juicy enough to get the analysis team started.

Measurement environmental/configuration differences of the HAM2 ISI from how they are nominally in observing:
    - PR3 M1 DAMP local damping loop gains are at -0.2, where they are nominally at -1.0. (The point of the test.)
    - CPS DIFF is OFF. (needed to do so for maintenance day)
    - Coil Driver z:p = 1:10 Hz analog low-pass (and digital compensation for it) is OFF. (need to do so to get good SNR on SUS M1 drive without saturating the SUS DACs)

Interesting things to call out that are the same as observing:
    - The PR3 alignment sliders were ON. P = -122 [urad]; Y = 100 [urad]. (Don't *expect* dynamics to change with ON vs. OFF, but we have seen diagonal response change if close an EQ stop. Haven't ever looked, but I wouldn't be surprised of off-diagonal responses change. Also DAC range gets consumed by DC alignment request, which is important for driving transfer functions.)
    - Corner station sensor correction, informed by the Bier Garten "ITMY" T240 on the ground. (the h1oaf0 computer got booted this morning, so we had to re-request the SEI_CS configuration guardian to be in WINDY. The SEI_ENV guardian had been set to LIGHT_MAINTENANCE.)
    - PR3 is NOT under any type of ISC global control; neither L, P, or Y. (global ISC feedback for the PRC's LPY DOFs goes to PRM and PR2.)

There are too many interesting transfer functions to attach, or even to export in the limited amount of time I have. 
So -- I leave it to the LSC team that inspired this test to look at the data, and use as needed.

The data have been committed to the SVN here:
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/SAGM1/Data/
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_L_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_T_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_V_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_R_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_P_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_Y_0p02to50Hz.xml

    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/Common/Data
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_L_0p02to50Hz.xml
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_T_0p02to50Hz.xml
            [ran out of time for V]
            [ran out of time for R]
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_P_0p02to50Hz.xml
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_Y_0p02to50Hz.xml


For the SUS drives templates, I gathered:
     Typical:
     - The top mass, M1, OSEM sensors, in the LTVRPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M1_DAMP_?_IN1_DQ             [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The top mass, M1, OSEM sensors, in the T1T2T3LFRTSDD OSEM Sensor/Coil Basis, calibrated into microns, [um].
         H1:SUS-PR3_M1_OSEMINF_??_OUT_DQ         [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The top mass, M1, OSEM coils' requested drive, in the T1T2T3LFRTSD OSEM Sensor/Coil Basis, in raw (18 bit) DAC counts, [ct_M1SUS18bitDAC].
         H1:SUS-PR3_M1_MASTER_OUT_??_DQ          [Filtered with the 32x filter, then downsampled to to fs = 512 Hz]

     For this set of templates:
     - The bottom mass i.e. optic, M3, OSEM sensors, in the LPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M3_WIT_?_DQ                  [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The bottom mass i.e. optic, M3, optical lever, in PIT YAW Euler Basis, calibrated into mircoradians, [urad].
         H1:SUS-PR3_M3_OPLEV_???_OUT_DQ          [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The ISI's Stage 1 GS13 inertial sensors, projected to the PR3 suspension point LTVRPY Euler basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_SUSPOINT_PR3_EUL_?_DQ       [Filtered with the 4x filter, then downsampled to to fs = 1024 Hz]
     - The ISI's Stage 1 super sensors, in the ISI's Cartesian XYZRXRYRZ basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_ISO_*_IN1_DQ                [Filtered with the 2x filter, then downsampled to to fs = 2048 Hz]

Note: The six M1 OSEM sensors in the Euler Basis are set to be the "A" channels, such that you can reconstruct the transfer function between the M1 Euler Basis to all the other response channels in the physical units stated above. As usual the excitation channel for the given drive DOF (in each template, that's H1:SUS-MC3_M1_TEST_?_EXC) is automatically stored, but these channels are in goofy "Euler Basis (18-bit) DAC counts," so tough to turn into physical units.

For the brand new ISI drive templates, I gathered:
     - The ISI's Stage 1 super sensors, in the ISI's Cartesian XYZRXRYRZ basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_ISO_*_IN1_DQ                [Filtered with the 2x filter, then downsampled to to fs = 2048 Hz]
     - The ISI's Stage 1 GS13 inertial sensors, projected to the PR3 suspension point LTVRPY Euler basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_SUSPOINT_PR3_EUL_?_DQ       [Filtered with the 4x filter, then downsampled to to fs = 1024 Hz]

     - The top mass, M1, OSEM sensors, in the LTVRPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M1_DAMP_?_IN1_DQ             [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The bottom mass i.e. optic, M3, OSEM sensors, in the LPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M3_WIT_?_DQ                  [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The bottom mass i.e. optic, M3, optical lever, in PIT YAW Euler Basis, calibrated into mircoradians, [urad].
         H1:SUS-PR3_M3_OPLEV_???_OUT_DQ          [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The ISI's Stage 1 actuators' requested drive, in the H1H2H3V1V2V3 ISI actuator basis, in raw (16-bit) DAC counts, [ct_ISIST116bitDAC].
         H1:ISI-HAM2_OUTF_??_OUT                 [Didn't realize in time that there are DQ channels H1:ISI-HAM2_MASTER_??_DRIVE_DQ stored at fs = 2048 Hz, or I would have used those.]

Note: Here, I set the number of "A" channels to twelve, such that both the ISI's Cartesian basis and the PR3 Suspoint basis versions of the GS13s can be used as the transfer function reference channel. 
Comments related to this report
jeffrey.kissel@LIGO.ORG - 13:50, Tuesday 15 October 2024 (80688)
OK ok ok. I couldn't resist and it didn't take that long. 

I attach the unit-full transfer functions between the ISI Sus. Point Drive DOFs (L, P, Y, and T) and the Top Mass SUS M1 OSEMs response in L, P, Y.

It's.... a complicated collection of TFs; and this isn't all of them that are relevant!

Just to make the point that Dan DeBra taught Brian Lantz, who taught me, and we're passing down to Edgard Bonilla: *every* DOF matters; the one you ignore is the one that will bite you.
The transverse, T, DOF drive data set demonstrates this point. None of these transverse to LPY couplings nominally exist if we just consider first principles equations of rigid-body motion of an ideal suspension. But alas, the on-resonance coupling from T to L, P, Y ranges from 0.1 ... to 50 [m/m] or [rad/m]. 

I may need to drive the ISI with an entirely different color of excitation to resolve these transfer functions above 5 Hz, where it's perhaps most interesting for DARM, but this is a good start.

The ISI drive templates have been re-committed to the repo with the calibrations of each channel in place. (It was really easy: just multiplying each channel by the appropriate 1e-9 [m/nm] or 1e-6 [m/um] in translation, and similar 1e-9 [rad/nrad] or 1e-6 [rad/urad].)
Images attached to this comment
brian.lantz@LIGO.ORG - 09:50, Wednesday 16 October 2024 (80709)

Thank Jeff!

You were right - this looks much more interesting than I had hoped. We'll run the scripts for the SUS to SUS TFs and put them up here, too.

Transverse to Pitch at 50 rad/m on resonance. Maybe "only" 10 when you turn up the damping to nominal? Ug.

brian.lantz@LIGO.ORG - 16:07, Monday 28 October 2024 (80907)

I've also taken a look at how much the ISI moves when Jeff drives the BOSEMs on the top stage of PR3. The answer is "not very much". I've attached two plots, one for the top mass Yaw drive and the other for the top mass length drive. note - The ISI reponses need to be divided by 1000 - they are showing nm or nrad/drive, while the SUS is showing microns or microradians/drive.

So - the back reaction of the osem drives can be safely ignored for PR3, and probably all the triples, as expected. (maybe not for the TMs, not that it matters right now).

It raises 2 questions

1. How do I divide a line by 1000 in a dtt plot? (I feel so old)
2. Why does the green line (SUSPoint) look so much noiser that the cart-basis blend signals? I would expect these to look nearly identical above about 1/2 Hz, because the blend signal is mostly GS-13. The calibrations look right, so why does the TF to the GS-13 signal look so much worse than the TF to the blend output?

These plots are at {SUS_SVN}/HLTS/H1/PR3/SAGM1/Results/

2024-10-15_length_to_length_plot.pdf
2024-10-15_yaw_to_yaw_plot.pdf

Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 10:17, Wednesday 23 October 2024 (80835)
I grabbed the remaining ISI drive degrees of freedom this morning, V and R. The color and strength of the excitation was the same as it was on Oct 15th, where I used the L drive excitation params for V, and the P drive excitation params for R.

PR3 damping loops gains were at -0.2 again,
Sensor correction is ON,
CPS DIFF is OFF.
PR3 alignment offsets are ON.

For these two data sets, the PR3 top mass coil driver low pass was still ON (unlike the Oct 15th data), but with the damping loop gains at -0.2, there's no danger of saturation at all, and the low pass filter's response is well compensated, so it has no impact on any of the ISI excitation transfer functions to SUS-PR3_M1_DAMP_?_IN1_DQ response channels. It's only really important to have the LP filter OFF when driving the SUS.

There was the remnants of an earthquake happening, but the excitations were loud enough that we still got coherence above at least 0.05 Hz.

Just for consistency's sake of having a complete data set, I saved the files with virtually the same file name:
     /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/Common/Data/
         2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_L_0p02to50Hz.xml
         2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_T_0p02to50Hz.xml
         2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_V_0p02to50Hz.xml   # New as of Oct 23
         2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_R_0p02to50Hz.xml   # New as of Oct 23
         2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_P_0p02to50Hz.xml
         2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_Y_0p02to50Hz.xml
Images attached to this comment
jeffrey.kissel@LIGO.ORG - 12:56, Wednesday 23 October 2024 (80847)
Today I also gathered another round of all six DOFs of ISI excitation, but this time changing the color of the excitation to get more coherence between 1 to 20 Hz -- since this is where the OSEM noise matters the most for the IFO. In the end, the future fitter may have to end up combining the two data sets to get the best estimate of the plant.

In the same folder, you'll find 
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/Common/Data
        2024-10-23_1739_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_L_0p02to50Hz.xml
        2024-10-23_1739_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_P_0p02to50Hz.xml
        2024-10-23_1739_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_R_0p02to50Hz.xml
        2024-10-23_1739_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_T_0p02to50Hz.xml
        2024-10-23_1739_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_V_0p02to50Hz.xml
        2024-10-23_1739_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_Y_0p02to50Hz.xml

Happy fitting!
brian.lantz@LIGO.ORG - 16:00, Thursday 24 October 2024 (80863)

Here is the set of plots generated by {SUSsvn}/Common/MatlabTools/plotHLTS_dtttfs_M1 for the data Jeff collected on Oct 15.
(see above, the data set is in 6 text file with names like 2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_L_0p02to50Hz_tf.txt (L, P, Y, etc)

These are funny looking because the damping loops are only running at 1/5 of the normal gain. This gives higher-Q peaks and less OSEM noise coupling. This is done as part of an exercise to run the detector with a combination of real OSEM signals (ie the ones here) PLUS model-based OSEM estimators. I've set the script to show all the cross terms, and these are clearly present. It remains to be seen how much the various cross terms will matter. This is the data we will use to help answer that question.

I've also attached a slimmed-down version of the cross-coupling plots which just shows the coupling to yaw. These are the same plots as above with some of the lines removed so that I can see what is happening to yaw more easily. In each plot the red is the measured cross-coupling from dof-drive to Yaw-response. For reference, these also include the light-blue yaw-to-yaw and the grey dof-to-dof measurements.

These plots and the .mat file are in the SUS SVN at {SUS_SVN}/HLTS/H1/PR3/SAGM1/Results/

2024-10-15_1627_H1SUSPR3_M1.mat
2024-10-15_1627_H1SUSPR3_TFs_lightdamping_yawonly.pdf
2024-10-15_1627_H1SUSPR4_M1_ALL_TFs_lightdamping.pdf

Non-image files attached to this comment
brian.lantz@LIGO.ORG - 20:40, Thursday 24 October 2024 (80870)

On a side note, the ISI to ISI TFs are not unity between 0.1 and 1 Hz. I think they should be. This is a drive from the blended input of the control loop (well, several, because it's in the EUL basis) to the signal seen on the GS-13, in the same EUL basis, converted to displacement (so it will roll off below 30 mHz, because the the realtime calibration of the GS-13s in displacement rolls off, and it has a bump at 30 Hz because this is really the complementary sensitivity, and that has a bump because of the servo bump)

But it should be really close to 1 from 0.1 to 3 Hz. The rotational DOFs (right side, red line) look pretty good, but the translations (L, V, T) all show a similar non-unity response. Jim and Brian should discuss. They look similar to each other, so maybe it's a blend which isn't quite complementary?

Non-image files attached to this comment
brian.lantz@LIGO.ORG - 16:56, Saturday 26 October 2024 (80890)

I've plotted the TFs from the SUSpoint drive to the M1 EUL basis TFs. Note that in the plots, I've adjusted the on-diagonal model plots to be -1 + model. The model is the INERTIAL motion of the top stage, the measured TFs all show the RELATIVE motion between the ISI and top stage. So you want to model Top/ISI - ISI/ISI or -1 + model. This is only true for the on-diagonal TFs.

The code to do this lives in {SUSsvn}/HLTS/Common/MatlabTools/plotHLTS_ISI_dtttfs_M1.m

I've attached a big set of pdfs. The cross couplings look not-so-great. See the last 5 plots for the cross-couplings of dof->Yaw. in particular, L->Y is about the same as Y->Y. (pg 22)

The pdfs and the .mat file have been committed to the SVN at

{SUSsvn}/HLTS/H1/PR3/SAGM1/Results/
  2024-10-15_1627_H1SUSPR3_M1_SUSpointDrive.mat
  2024-10-15_1627_H1SUSPR3_M1_ALL_TFs_lightdamping_SUSpointDrive.pdf

(Also, see in the previous comments, there was a file which I named ...PR4...  this is now corrected to ...PR3... )

Non-image files attached to this comment
Displaying reports 4621-4640 of 83188.Go to page Start 228 229 230 231 232 233 234 235 236 End