Displaying reports 10441-10460 of 84772.Go to page Start 519 520 521 522 523 524 525 526 527 End
Reports until 16:12, Wednesday 20 March 2024
LHO General
corey.gray@LIGO.ORG - posted 16:12, Wednesday 20 March 2024 (76559)
Wed EVE Ops Transition

TITLE: 03/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 10mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:

Engineering Run #16 (ER16) started this morning and Oli handed over an H1 in NLN with Camilla doing a Squeezer measurement and there is a possibility we may try to "squeeze" in a few other measurements (i.e. no squeezing quiet time) before the 6pm target for Observing.

H1 General
oli.patane@LIGO.ORG - posted 16:00, Wednesday 20 March 2024 (76555)
Ops Day Shift End

TITLE: 03/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Commissioning all day with a few locklosses. Relocking took an average of 42ish minutes.
LOG:

15:00 Detector got to NOMINAL_LOW_NOISE
19:25 Lockloss

20:38 NOMINAL_LOW_NOISE
20:42 Lockloss in NOMINAL_LOW_NOISE from commissioners

21:31 NOMINAL_LOW_NOISE                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             

Start Time System Name Location Lazer_Haz Task Time End
15:13   Elenna Remote n A2L tests 16:13
17:35 FAC Karen WoodShop n Tech clean 18:20
17:51 FAC Kim H2 n Tech clean 18:13
17:58 EE Fil EY n Check hotspot 18:25
18:25 EE Fil EX n Getting other hotspot 18:47
18:34 SHG Julian Optics Lab y(local) Working on SHG 19:46
18:43 FAC Tyler Water tower n Turning on tractor but not driving it 19:13
19:47 WLK Ibrahim along EY n Taking a nice walk 20:31
H1 SQZ
camilla.compton@LIGO.ORG - posted 15:53, Wednesday 20 March 2024 - last comment - 08:23, Thursday 21 March 2024(76556)
SQZ_ANG_ADJUST servo turned back on

Naoki, Nutsinee, Camilla

We turned the SQZ_ANG_ADJUST servo back to it's O3a nominal ADJUST_SQZ_ANG_ADF.  Changed sqzparams.use_sqz_angle_adjust to True and reloaded SQZ_MANAGER and SQZ_ANG_ADJUST.

Set H1:SQZ-ADF_OMC_TRANS_PHASE as 133deg, new scan (as in 76434) running now to check what angle is best for total squeezing.

Comments related to this report
camilla.compton@LIGO.ORG - 16:16, Wednesday 20 March 2024 (76561)

Accepted at H1:SQZ-ADF_OMC_TRANS_PHASE = 120. This seems to give us the best range but not high frequency SQZ. Plot attached.

Images attached to this comment
nutsinee.kijbunchoo@LIGO.ORG - 17:46, Wednesday 20 March 2024 (76573)

We optimized the sqz angle after high CLF test and readjusted the AADF demod phase.

Images attached to this comment
camilla.compton@LIGO.ORG - 08:23, Thursday 21 March 2024 (76581)

We should check the ADF offset with a more themalized IFO as the SQZ angle servo seems to have pulled even the yellow BLRM to a worse location, see attached.

Images attached to this comment
H1 ISC (SQZ)
artem.basalaev@LIGO.ORG - posted 13:40, Wednesday 20 March 2024 - last comment - 12:31, Saturday 30 March 2024(76537)
Excess noise in DARM: relation to squeezing
Artem, Jennie W., Gabriele

Following up on alog 76516.

We compared DARM for following configurations:
* No squeezing O4a, 12/20/2023 18:10-18:20
* With squeezing O4a, 01/12/2024 01:35:15-01:45:15 
* No squeezing now, 03/17/2024 04:45:31-04:55:31
* With squeezing now, 03/17/2024 08:18:46-08:28:46

Specifically, following ASDs were calculated: sqrt(abs(no_sqeezing_now^2 - no_squeezing_o4a^2)), and sqrt(abs(squeezing_now^2 - squeezing_o4a^2)). These are shown as blue and red traces on the attached plot. The original DARM traces are shown in gray.

Our preliminary conclusion from this is that it appears that excess noise is ~same with and without squeezing.

We'll make this plot with longer time series and do some more tests.

Jupyter notebook is available here.
Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 09:35, Friday 22 March 2024 (76621)

Here is my plot which is just binning calibrated CAL-DELTAL_EXTERNAL_DQ and then excluding all the ASD values where the noise now is better than the noise in 04a (these are at low frequency and this is where our noise has improved due to ASC control noise improvements and new DARM configuration).

Then I use the same maths as Artaem to get:

excess noise with no squeezing = sqrt( (ASD with no squeezing now)^2 + (ASD with no squeezing in 04a)^2)

excess noise with no squeezing = sqrt( (ASD with squeezing now)^2 + (ASD with squeezing in 04a)^2)

These also seem to be the same in my plot, which implies that the excess noise is indeed due to some correlated noise (i.e. non-quantum).

Images attached to this comment
gabriele.vajente@LIGO.ORG - 12:31, Saturday 30 March 2024 (76817)

See evolution and reduction with ZM alignment: 76757

H1 GRD
sheila.dwyer@LIGO.ORG - posted 13:31, Wednesday 20 March 2024 (76550)
ADS will be off during DARM transitions

We have lost lock a few time duing the DARM transitions: 1394979344 1394954887

Both the lockloss tool and Elenna flagged that there's a big glitch in ADS durign the transition, so I've edited the guardian so it will be off.  It was already turned off for the coil driver switching, I've just moved the lines that turn it back on to after the DARM transitions.

H1 ISC
gabriele.vajente@LIGO.ORG - posted 13:18, Wednesday 20 March 2024 - last comment - 14:51, Wednesday 20 March 2024(76548)
OMC locking demodulation phase

I was trying to figure out which things are in the intersection of 1) could give a flat noise in DARM and 2) has been changed during the vent. One suihc thing is OMC lenght noise. This got me down the rabbit hole of understanding the OMC lock.

OMC dither lenght control

The 4.1 kHz we inject on PZT1 for the lock shows an amplitude modulation: this is normal since 4.1 kHz is high enough in frequency and close to 16384 Hz, so that the line produced by the DAC is a bit undersampled.

The OMC length locking error signal H1:OMC-LSC_I_OUT shows now a large 4 Hz bump that was not there in O4a: we think this is due to the fact that the I/Q demodulation phase of the OMC dither line is mistuned: we are coupling line amplitude modulation into I. So hopefully tuning the demodulation phase will help with this problem.

We retuned the OMC lenght demodulation phase while at 2W in PREP_DC_READOUT. The old value was 35 degrees, and gave us almost equal amplitude in I and Q of a 11 Hz PZT line I injected. The optimal phase that moves this line all in I and none in Q is 56 degrees. Decoupling is better than a factor 100. We'll see when we lock to NLN if this improved the 4 Hz bump in the OMC lock and DCPD, and if this mistuning has any effect on the OMC locking point.

I don't know where this phase is set (probably SDF), so we need to check that and update this parameter where it is set

Still to do: measure OMC lock open-loop gain and check the UGF. Lock loss at 13:42 LT caused by the OMC UGF template, the excitation was probably too large
 

Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 14:51, Wednesday 20 March 2024 (76554)

The new phase works well in NLN (injected line at 11 Hz shows up only in I and not in Q). But the 4 Hz bump is still there. And there is also a 4 Hz line in the PZT1 signal (the one used for the 4.1 kHz dither). So it's more complicated that simply amplitude modulation of the 4.1 kHz line.

Images attached to this comment
H1 SQZ
sheila.dwyer@LIGO.ORG - posted 12:35, Wednesday 20 March 2024 - last comment - 08:23, Thursday 28 March 2024(76540)
SQZ data set

Camilla, Nutsinee, Sheila

Screenshot of different sqz angles attached.  Nutsinee's final attachment compares sqz with two different CLF servo signs.

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 12:40, Wednesday 20 March 2024 (76547)

We offloaded IFO ASC and used "Save ZMs IFO" script to save the ZM settings that we found.

camilla.compton@LIGO.ORG - 14:51, Wednesday 20 March 2024 (76553)
Naoki and I just saw 5.4dB @ 2kHz and 5.2dB @1kHz with the IFO just locked (<10 minutes at NLN) with this new ZM5/6 alignment.
This might be our best ever SQZ, but we often have better SQZ at the start of a lock before the IFO has thermalized.

We moved the ADF back to 1.3kHZ as think the 322Hz ADF we used eariler is impacting the range.

Images attached to this comment
victoriaa.xu@LIGO.ORG - 08:23, Thursday 28 March 2024 (76734)ISC, SQZ

Attachment 1 - looking for freq-dep SQZ loss/rotations. Here we fit a common model of frequency-dependent losses and rotations to all squeeze angle spectra simultaneously. FIS data would probably clean this up at low-frequencies, maybe removing the ~20 Hz anti-sqz bump.

  • Top plot - SQZ dBs after subtraction of non-quantum noise. Note: after subtraction, we see worse squeezing now at 100 Hz vs. kHz, unlike before in O4a/O3.
  • Middle plot  - fitted frequency-dependent losses (1 - \eta(\Omega)). Note: now estimating ~10-15% more loss at 100 Hz than kHz; only few% loss difference between 1-3 kHz. This was the opposite in O3 e.g. Fig. 3 mid-right plot of the quantum response paper (P2100050shows ~20% less loss at 100 Hz.
  • Bottom plot - fitted sqz angle rotation (\theta(\Omega)), in addition to the sqz angle used for each trace (\phi_0). That is, each frequency bin corresponds to a sqz angle at \phi_0 + \theta(\Omega).

Dots + thick lines = subtracted sqz data, with a moving average for clarity. Thin line = common fit model. Equations in the plot title. For each frequency bin \Omega, we fit the loss(\Omega) and the sqz angle offset theta(\Omega) given the \phi_0 for the dataset. The fit to all sqz angle spectra is done independently for each frequency bin.

This dataset suggest higher freq-dep losses at low frequencies in-band, but before we typically we had lower freq-dep losses below darm pole, e.g. Fig. 3 of the O3 quantum response paper (P2100050). I'm not really sure yet how to interpret this, and don't think there's a clear expectation for one way or another. As a basic sanity check, I compared another time with anti-sqz from March 17 LHO:76434 (which had different PSAMS settings) - there, evidence for frequency-dependent losses at lower frequencies is weaker, but there is still some evidence for it.

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

Attachment 2 - squeezing-related DARM comparison, O4a vs. pre-O4b. Blue/yellow = O4a. Purple/pink = pre-O4b. Interesting things (from a sqz perspective):

  • Above the DARM pole, SQZ is mostly loss-limited, notice purple better than blue -- DARM is slightly better now than O4a. For NO SQZ, optical gain looks slightly higher now. For SQZ, there's now more high freq SQZ, aka reduced SQZ losses.

    For reference, in O4a we saw up to [-4.5, -4.8] dB with/without subtracting non-quantum noise. Now pre-O4b, we've seen up to -5.4 dB without subtraction at the starts of locks when technical noise is lower, and can see 4.5 dB thermalized. Tracking losses in the gsheet

    From the OMC replacement plan G2302156 - the old OMC003 was estimated ~90% throughput, the new OMC001 was estimated ~96% prior to install.
    (O4a OMC loss inferences in e.g. 73873 and 74022 suggested 89-91% omc003 tem00 efficiency. See T1500060 for OMC specs.)
     
    • pre-O4b: Inferring losses from 15.8 dB anti-sqz && -5.4 dB sqz w/o subtraction {NLG = 17.3, 25mrad phase noise, in this thread 76553}
      --> pre-O4b: inferred losses ~ 22-25%, of which we expect ~16% (if new OMC001 ~3.6% loss), leaving ~12-13% excess loss. Mode-matching status unknown.
       
    • O4a: NLG sweep on DARM after crystal move, Oct 2023, see LHO:74318. This is consistent with O4a SQZ angle datasets: 74935 - Dec 2023 - cold OM2, and 73621 - Oct 2023 - hot OM2.
      --> O4a: inferred losses ~30-32%, of which we expected ~22% (if old OMC003 was 10% loss), leaving ~12-14% excess loss. Mode-matching attempted, railed PSAMS actuators, ran out of range to continue.
       
    • The higher squeezing pre-O4b (-5.4 dB vs. -4.5 dB) seems consistent with a 5-6% reduction of SQZ losses. This improvement is plausibly consistent with the expected OMC loss reduction.
       
    • On the other hand - while we see some squeezing improvement consistent with expected loss reductions, this actually suggests that the 10-13% excess sqz losses from O4a remain untouched. In O4a, based on 8dB homodyne SQZ (73562), these 10% excess losses were not "injection losses" i.e. they were after HAM7. 
       
    • May be worth considering more closely the conversion from NLG to generated squeezing level, since that factors into these loss estimates. These loss estimates are based on a model for a linear OPO. Dhruva's ADF paper P2200041 does some more math on the conversion from NLG to generated squeezing level for a bowtie OPO, like as the observatories have. I believe the same NLG corresponds to a slightly lower generated squeezing level than expected for a linear OPO.
    • Mode-matching gains from the break TBD. The sqz alignment scripts will be helpful to fully explore PSAMS optimizations. Naoki has started this in LHO:76757, bringing in Masayuki's work from e.g. LLO:64903LLO:64458.
       
  • Below the DARM pole, notice blue better than purple -- it's interesting that both no-sqz and sqz are worse, especially considering the above evidence for higher freq-dep losses below the darm pole. Attachment 1 top plot - we see worse squeezing now at 100 Hz than we used to in O4a, even after subtracting non-quantum noises.

A comment regarding the excess noise - it seems clear that the excess mid-band DARM noise is not caused by / related to squeezing, because it's there even without squeezing injected. That said, squeezing seems to be having its own issues at these lower frequencies, below the DARM pole. Not clear how the worse low-frequency squeezing (after subtraction) could be a consequence of whatever causes the excess noise without squeezing. Likely different issues / things to be optimized happening at the same time/frequencies.

After PSAMS optimization with alignment scripts, it could be interesting to try a similar SQZ dataset with FIS.

Images attached to this comment
H1 SUS
oli.patane@LIGO.ORG - posted 11:47, Wednesday 20 March 2024 - last comment - 09:43, Monday 25 March 2024(76545)
Model updates for USER DACKILL w/ better Watchdogs con't: ITMs and BS

Oli P, Jeff K

As a continuation of the SUS model updates (76269), yesterday I updated the models, medms, and watchdog filter banks for the ITMs and BS. Everything looks to be functioning as intended. Changes made are basically the same as what was done for the ETMs and TMSs, with the exception of the pi model for the ITMs(attachment1). I will list the model files that have changed:
SUS
- QUAD_ITM_MASTER.mdl
- h1susitmx.mdl
- h1susitmy.mdl
- h1susitmpi.mdl
- BSFM_MASTER.mdl
- h1susbs.mdl
ISI
- h1isiitmx.mdl
- h1isiitmy.mdl
- h1isibs.mdl
The OVERVIEW and WD medm files have been updated for each suspension, there has been the addition of a new filter bank within the WD screen to accomodate for the addition of the RMSLP put into the WD models, and these filters, along with the BANDLIM filter banks, have been updated with the correct filters. SDFs have been accepted for safe(attachment2) and OBSERVE(attachment3). All changes are in svn.

SUS Type Updated?
QUAD ETM 76269
QUAD ITM this alog
BSFM this alog
HLTS  
HSTS  
TMTS 76269
OMCS  
HSDS  
HPDS  
HDDS  
HTDS  
OFIS  
OPOS  
HAUX  
HTTS  
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:43, Monday 25 March 2024 (76676)
J. Kissel, O. Patane

Oli and I reviewed their work on this upgrade and it looks great. We did see a few oversights that we corrected this morning:
    (1) Set the H1 SUS M1 and M2 thresholds to (still arbitrary) 100 and 200 [um_RMS], respectively, in the 0.1 to 10 Hz region (see 1st attachment)
    (2) Turned on the H1 SUS M2 stage calibration, which had been installed, but just not turned on. (see 2nd Attachment)

We've accepted these changes in the SDF system.
Images attached to this comment
H1 SEI (ISC)
jim.warner@LIGO.ORG - posted 11:16, Wednesday 20 March 2024 - last comment - 09:06, Thursday 21 March 2024(76544)
NLN locklosses sending big kicks to ETMX HEPI

The commissioners are aware of this now and some people are looking into it, but it seems that the new DARM offloading scheme has been sending big kicks (a few 10s to 200 microns) to the ETMX HEPI at almost every lockloss from NLN. This doesn't seem to be happening with ETMY. On attached trends, top blue trace is the ISC tidal signal sent to ETMX HEPI, yellow is the ISI watchdog state, bottom is the ISC LOCK state number. The ISI doesn't trip every time, but it's happend 5 times just over the last week. This isn't normal behavior, but it seems like we've just been ignoring this for a while. I recall having this happen a bit before the end of O4a, and we added a filter to the input to the HEPI model, but that just seems to slow the kick a bit. 

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 12:35, Wednesday 20 March 2024 (76546)ISC

Louis and I modified the aL1L3 filter (FM6) in ETMX_L1_LOCK_L by replacing the single pole at 50 Hz with a complex pair at 30 Hz, so that this offloading filter rolls off like 1/f above 30 Hz. Since the output of L1_LOCK_L is offloaded to HEPI, we suspect that this is what was causing the kick at EX. No DARM control is directly applied to EY, so that would explain why EY does not trip. The most recent lockloss did not trip anything.

Images attached to this comment
jim.warner@LIGO.ORG - 13:04, Wednesday 20 March 2024 (76549)

It didn't trip the ISI, but we still are spiked up to about a third of the actuators drive range on the last lockloss. I'm less worried about tripping the ISI than I am about damaging something on the suspension or HEPI. attached trend shows the ISC signal to ETMX HEPI and the drives on the horizontal actuators at the last lockloss. 

Images attached to this comment
camilla.compton@LIGO.ORG - 14:04, Wednesday 20 March 2024 (76552)

Evan added a 0.1Hz low pass filter into FM3 of H1:LSC-X_ERR_TIDAL_ERR, and for symmetry into H1:LSC-Y_ERR_TIDAL_ERR. Turned on filters and sdfs.  We expect this to stop the kicks and not effect the slower tidal offloading: titdal to UIM is ~0.03Hz, to HEPI would be even slower  68749.

camilla.compton@LIGO.ORG - 09:06, Thursday 21 March 2024 (76583)

Since the 0.1Hz LP has been added, the two locklosses have not kicked the HEPI. See attached zoomed out and zoomed in plots. 

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 10:19, Wednesday 20 March 2024 (76543)
Wed CP1 Fill

Wed Mar 20 10:11:21 2024 INFO: Fill completed in 11min 18secs

Travis confirmed a good fill curbside.

TCs started around -60C, I reduced trip temps to -120C. Note TCmins today are close to the -200C limit.

Images attached to this report
H1 ISC
elenna.capote@LIGO.ORG - posted 09:33, Wednesday 20 March 2024 (76541)
Updated ITMY Y2L gain

With the updated AS A WFS yaw offset, the most significant ASC coherence to DARM comes from CHARD Y, see Gabriele's bruco.

To try to improve this, I revisited the ITMY Y2L gain. I chose to inject broadband noise from CHARD Y from 10-40 Hz and adjust the Y2L gain to reduce the coupling. I was able to acheive a 20 dB reduction of the CHARD_Y/DARM transfer function at 20 Hz, and a 10 dB improvement in the DHARD_Y/DARM at 30 Hz. The CHARD Y coupling to DARM may be a few dB worse from 10-15 Hz.

The good news is that it appears that with the new WFS offset, the CHARD and DHARD Y coupling improve together over the same frequency band. The bad news is that there doesn't seem to be much appreciable change in the noise, suggesting that despite the high CHARD Y coherence with DARM, we are likely limited by other noise there.

Here is a summary of the steps I took and the notes:

Y2L gain Notes
-1.65 Nominal gain, DHARD Y and CHARD Y references measured
-1.5 CHARD Y coupling worse than -1.65
-1.4 CHARD Y coupling worse than -1.5
-1.7 No significant change of CHARD Y coupling relative to -1.65
-1.8 Improvement of CHARD Y relative to -1.65, some loss of coherence in the injection
-1.9 Improvement of CHARD Y relative to -1.8, had to increase injection strength 60%
-2.0 CHARD Y coupling worse relative to -1.9, sign flip

Once I determined that a gain of -1.9 was better than nominal, I remeasured the DHARD Y coupling and saw that it was also better, although not the the same degree as the CHARD Y coupling.

First picture shows the transfer function measurement of CHARD_Y_OUT/DARM with different Y2L gains, second picture shows DHARD_Y_OUT/DARM with the initial and final Y2L gains.

I then measured DARM with no calibration lines to check if there was any improvement. I observed no significant change in the noise up to 100 Hz.

Since this Y2L gain appears better, I updated lscparams.py to change the gain from -1.65 to -1.9 (and loaded the guardian, but I did not do any svn commit). I also took SDF to safe and updated. I could not see any SDF diff in observe for the ITMY Y2L gain.

Although the DHARD/CHARD P coherence to DARM is less significant than the Y coherence, it is probably worth checking the P2L gains again to see if we can do any better.

Images attached to this report
H1 ISC
gabriele.vajente@LIGO.ORG - posted 22:27, Tuesday 19 March 2024 - last comment - 10:35, Thursday 21 March 2024(76534)
Moved the input beam

[Jennie, Evan, Gabriele]

We tried again to move the input beam pointing in-lock, similarly to what was done in 76359.

First we moved IM1 and IM3 in pitch, looking at IM4_TRANS and POP_LF. We could increase the power in IM4, and we moved until we reached a maximum in POP_LF. Half way during the test we switched back to ADS from cameras, but it turns out that the PRM ADS was moving in the wrong direction. We went back to camera servos (restoring the original, correct offsets) and helped PRM along to speed up the camera servo convergence.

When we reached this maximum of POP_LF by moving pitch IM1 and IM3, we checked DARM: there was more noise in DARM at low frequency and around 100 Hz, the range was lower, but coherence with jitter was unchanged. Evan tried to improve things by tuning the SQZ, without luck.

We then moved to yaw, and we could improve IM4 and POP_LF further. Unfortunately we lost lock during the test. We don't believe we caused the lock loss.

The change in input beam alignment had a good effect on the optical gain, KAPPA_C increased by 2% (yaw being the most effective direction). For comparison IM4_TRANS improved by 6.6%, POP_LF improved by 2.8%

Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 08:51, Wednesday 20 March 2024 (76539)

The arm power also increased proportionally to LSC-POP and ASC-POP. I think this means that moving the input pointing we were fixing some clipping in the PRC. It's worth repeating the test: we could go back to the pitch position we found (by moving IM1, IM3 with a long ramp, and also moving PRM to the new value, and maybe also IM4?). From there we can restart the yaw motion, which seemed promising.

Images attached to this comment
jennifer.wright@LIGO.ORG - 23:12, Tuesday 19 March 2024 (76535)

I reverted the alignment changes to IM1, IM3 and PRM. See attched images of the SDFs for SUSPRM and SUSIM models.

Images attached to this comment
gabriele.vajente@LIGO.ORG - 10:35, Thursday 21 March 2024 (76590)

For future reference, here are the moves we did (in SUS offset sliders) or loops did for us (in M1 DAMP IN units, should be the same as sliders)

Optic (pitch) Initial value Final value Change
IM1 (us moving) 7794 2900 -4894
IM3 (us moving) -7576 -5376 +2200
IM4 (loop) -2862 -2731 +131
PRM (loop helped by us) -1314 -1132 +182
PR2 (loop) -484 -516 -32
PR3     none
BS     none

 

H1 SQZ (SQZ)
nutsinee.kijbunchoo@LIGO.ORG - posted 23:52, Monday 18 March 2024 - last comment - 15:18, Wednesday 20 March 2024(76511)
Back to 5 dB of squeezing!

Naoki, Camilla, Evan, Sheila, Julian, Nutsinee

Many things happened with the squeezer this afternoon. A quick summary is we are back to 5 dB at kHz and we should be able to do this repeatedly. No PSAMs adjustment required at this time.

- When the IFO relocked this afternoon we adjusted ZM5 alignment to optimize ADF trans signal. By doing so we improved both the RF3 and the 42. However this made squeezing worse.

- We adjusted the SQZ angle. We couldn't make it better so we went the other way. This made squeezing worse and ADS TRANS went up with it. Note that this is the IQSUM channel. We didn't think that was a sensible behavior but we've seen it before.

- Sheila and Julian then optimized the crystal tempeature. The NLG for today was 17.3.

- Naoki measured the SQZ IFO sensing matrix. We found a big cross coupling between ZM5 P to AS42 B Y. Other than then everything else was sensible. A new improved sensing matrix has been implemented. 

- We lost hours tracking down why the filter cavity failed to lock on green. A reminder to check SDF next time we run into mysterious problems.

- After everything went back to normal we recovered 5 dB of squeezing. DARM plot said so. BLRMS seemed slightly off. We tried turning the ASC loop off and optimizing the ZM alignment by hand to see if we could do any better than the loop. We couldn't. SQZ IFO ASC loop now works as it should.

- We also optimized the filter cavity offset. Mostly to double checked that we were sitting at a good place. An offset of -28 (where we started) gave the best squeezing at low frequency.

 

We haven't got to increase CLF power today. 

After a new CLF VCO installed we should revert the CLF sign to make sure everything was the same as before. In theory this shouldn't do anything. 

 

 

Images attached to this report
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 00:35, Tuesday 19 March 2024 (76513)

Naoki Nutsinee

We changed "fcgs_trans_lock_threshold" to 120 today so FC wouldn't lock on higher order mode. The filter cavity was having trouble getting pass GR VCO lock so we have now reduced this power back to 80.

camilla.compton@LIGO.ORG - 15:18, Wednesday 20 March 2024 (76557)

Accepted the new ASC_INMATRIX settings in sdf, see attached. Aslo accepted ASC_POS_Y's new minus sign and AS_A_RF42_YAW_OFFSET.

Accpeted the SQZ_ASC WFS as OFF. As decided, we will start the ER with SQZ ASC IFO off.

Images attached to this comment
Displaying reports 10441-10460 of 84772.Go to page Start 519 520 521 522 523 524 525 526 527 End