Displaying reports 9861-9880 of 88268.Go to page Start 490 491 492 493 494 495 496 497 498 End
Reports until 15:52, Friday 18 October 2024
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 SYS (GRD)
sheila.dwyer@LIGO.ORG - posted 15:21, Friday 18 October 2024 - last comment - 10:17, Saturday 19 October 2024(80749)
fast shutter guardian hanging getting data

When Ibrahim relocked the IFO, the fast shutter guardian was stuck in the state "Check Shutter" 

This was because it apparently got hung up getting the data using cdsutils getdata. 

The first two attachments show a time when the shutter triggered and shows up in the HAM6 GS13s, and the guardian passes.  The next time shows our most recent high power lockloss, where the shutter also triggered and shows up at a similar level in the GS13s, but the guardian doesn't move on. 

The guardian log screenshot shows both of these times, it seems that it was still waiting for data and so the test neither passed nor failed. 

To get around this and go to observing, we manualed to HIGH_ARM_POWER. 

Vicky points out that TJ has sovled this problem for other guardians using his timeout utils, this guardian may need that added.  

Another thing to do is make things so that we would notice that the test hasn't passed before we power up. 

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 10:17, Saturday 19 October 2024 (80758)

I looked at nds1's logs for this data request, the request appears to come it at the time it had timed out on h1guardian1.

From Shela's guardlog (paraphrasing somewhat):

2024-10-18_19:36:22Z timer

which is

2024-10-18T12:36:22 in "log PDT" format

NDS1 logs show (h1guardian1 is 10.101.0.249):

2024-10-18T12:36:27-07:00 h1daqnds1.cds.ligo-wa.caltech.edu daqd[1267959]: [Fri Oct 18 12:36:27 2024] connection on port 38943 from 10.101.0.249; fd=75
2024-10-18T12:36:27-07:00 h1daqnds1.cds.ligo-wa.caltech.edu daqd[1267959]: [Fri Oct 18 12:36:27 2024] ->42: version
2024-10-18T12:36:27-07:00 h1daqnds1.cds.ligo-wa.caltech.edu daqd[1267959]: [Fri Oct 18 12:36:27 2024] ->42: revision
2024-10-18T12:36:27-07:00 h1daqnds1.cds.ligo-wa.caltech.edu daqd[1267959]: [Fri Oct 18 12:36:27 2024] ->42: status channels 3 {"H1:ISI-HAM6_BLND_GS13Z_IN1_DQ"}
2024-10-18T12:36:27-07:00 h1daqnds1.cds.ligo-wa.caltech.edu daqd[1267959]: [Fri Oct 18 12:36:27 2024] ->42: status channels 3 {"H1:SYS-MOTION_C_SHUTTER_G_TRIGGER_VOLTS"}
 

So on first look it appears nds1 didn't get the request until after the 5 second timeout had expired.

Here is the request line (line 53) of isc/h1/guardian/LOCKLOSS_SHUTTER_CHECK.py

            gs13data = cdu.getdata(['H1:ISI-HAM6_BLND_GS13Z_IN1_DQ','H1:SYS-MOTION_C_SHUTTER_G_TRIGGER_VOLTS'],12,self.timenow-10)

This request is for 12 seconds of data with a start time 10 seconds in the past, meaning it cannot complete until +2 seconds have elapsed. Does this mean the 5 second timeout is effectively a 3 second timeout?

H1 ISC (Lockloss, PSL)
ibrahim.abouelfettouh@LIGO.ORG - posted 14:18, Friday 18 October 2024 (80748)
Lockloss 19:36 UTC

PSL caused Lockloss as ASC and IMC lost lock within 7ms of one another.

Images attached to this report
H1 AOS
sheila.dwyer@LIGO.ORG - posted 14:06, Friday 18 October 2024 (80746)
PSL NPRO current reduced

Sheila, Vicky, remote inputs from Jenne and Jason

We noticed that more of our low noise locklosses have been tagged with Camilla's IMC tag (which we think is related to the PSL glitches) since the laser current was raised (8 out of 15 locklosses were tagged 10/15-10/18), compared to the time since the IMC servo gain redistribution revert (10/10 to 10/15 1 lockloss out of 12 was tagged).  (Having this IMC tag made it very easy to do this check). 

After emailing with the PSL team, we decided to turn the current back down to 2.133A at the next lockloss. Vicky's screenshot shows us slowly lowering the current at 20:05 UTC.

 

Images attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:18, Friday 18 October 2024 (80744)
Fri CP1 Fill

Fri Oct 18 10:16:11 2024 INFO: Fill completed in 16min 6secs

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 09:14, Friday 18 October 2024 - last comment - 10:05, Saturday 19 October 2024(80742)
CNS-II reference GPS at EY, another -800nS glitch

From 07:32 - 07:37 Fri 18oct2024 PDT we had another glitch on the EY CNS-II GPS 1PPS as read by the timing system's EY comparator. This had happened twice recently, 05:50-06:40 Mon 30sep2024 (50mins) and a pair the next day 07:14 (3mins) 07:42 (8mins) Tue 01oct2024.

attached are details of today's glitch, and a month trend showing all three.

On a related note, the EX CNS-II broke on the 8th Oct with a bad power supply (a wall wart). It might be prudent to schedule a replacement of EY's power supply next Tuesday.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 10:16, Friday 18 October 2024 (80743)

It started again at 10:02. This time it is switching between -2200ns and -800ns

Images attached to this comment
david.barker@LIGO.ORG - 10:05, Saturday 19 October 2024 (80757)

Follow up: EY CNS-II started glitching again around 10am Friday, it continued to do this for about an hour, then went good again. No further glitches since then over the past 23 hours.

H1 ISC (Lockloss, PSL)
ibrahim.abouelfettouh@LIGO.ORG - posted 08:07, Friday 18 October 2024 (80741)
Lockloss 14:48 UTC

PSL Caused Lockloss only 15 minutes into Observing.

ASC and IMC lost lock within 18ms of one another (attached plot).

Images attached to this report
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 07:34, Friday 18 October 2024 (80740)
OPS Day Shift Start

TITLE: 10/18 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:

IFO is at NLN and OBSERVING as of 14:33 UTC

Walked in and IFO was at OMC_WHITENING. Sat down and IFO was at NLN.

LHO General
corey.gray@LIGO.ORG - posted 22:00, Thursday 17 October 2024 (80734)
Thurs EVE Ops Summary

TITLE: 10/17 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

Not a great night for H1.  There were winds, but we used to be able to ride through these.  Tonight locks were short and several had the IMC flagged for their locklosses.  And there was one stint where it took the IMC a while to lock.

There was also a M5 EQ offshore from Coos Bay, OR.
LOG:

H1 PEM (PEM)
corey.gray@LIGO.ORG - posted 21:06, Thursday 17 October 2024 (80739)
HVAC Fan Vibrometers FAMIS Check (FAMIS 26335)

For FAMIS #26335:  All looks well for the last week for all site HVAC fans (see attached trends).

Images attached to this report
LHO General (PEM)
corey.gray@LIGO.ORG - posted 18:27, Thursday 17 October 2024 - last comment - 19:08, Thursday 17 October 2024(80737)
M5.0 Earthquake Off Oregon Coast (~80miles from Coos Bay) Takes H1 Down

Earthquake at 558pm local time and H1 went down at 0600.  Took USGS about 25min to post the earthquake online.  H1 currently turning on ASC for DRMI.

Comments related to this report
corey.gray@LIGO.ORG - 19:08, Thursday 17 October 2024 (80738)

Back to Observing in 58min.

H1 AOS
joshua.freed@LIGO.ORG - posted 17:02, Thursday 17 October 2024 (80732)
PR2 damping contributions to DARM

J. Freed

 

Today we did damping loop injections on all 6 BOSEMs on the PR2 M1. This is a continuation of the work done previously for ITMX and ITMY

The gain on this instance was 750

The plots, code, and flagged frequencies are located at /ligo/home/joshua.freed/20241017/Scrpts. While the diaggui files are at /ligo/home/joshua.freed/20241017/Data

For PR2 all sensors had flags in the 8-12Hz range. Which implies couplings in that range

pr2_t3_20241017.png Shows an image of T3 during the time of injection vs the background which shows a clear picture of the possible coupling in the 8-12 Hz range
 
PR2HistogramofCouplings(allsensorsonM1).png  Shows a histogram of all instances at which the estimated maximum ambiant noise before injections was below the estimated ambiant noise during the injections of the different sensors and their freqeuncies (A.K.A. flagged frequencies). All sensors are included.  The most instances are in the 8-13Hz range with some in the 26Hz-28Hz and 46-47Hz range 
 
GPS Start Times for Injections (end ~150 sec after start)
Background time:1413227145
T1 time:    1413227579
T2 time:    1413227855
T3 time:    1413228082
LF time:    1413228385
RT time:    1413228590
SD time:    1413228845

 

 

Images attached to this report
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 16:43, Thursday 17 October 2024 (80735)
Thursday OPS Day Shift End

TITLE: 10/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

Lockloss from SQZrs PSAM activity.  
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1413215714

Relocking notes:
I had IMC Locking issues before entering into Initial_Alignment.

And then I had IMC Locking Issues in SR2 Alignment as well making Initial_Alignment incredibly difficult to Get into and Complete.
Sheila asked me to just take the IMC to Offline and wait until the PSL glitches.   

Reached Nominal Low Noise at 18:51 UTC

Commissioning activities started with:


 


More Issues with IMC Locking and Staying Locked.

 

LOG:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    

Start Time System Name Location Lazer_Haz Task Time End
16:36 SAFE HAZARD LVEA YES !!!!!LVEA IS LASER HAZARD!!!! 03:16
15:20 FAC Kim Mid X N Technical Cleaning 16:43
16:36 EE Ferando CER N Getting a USB Back up to a Beckhoff machine 17:02
17:24 SQZ Vicki CtrlRm N Removing typo from SQZ_MAN 17:54
19:48 PSL Jason Optics lab Yes Working on new NPRO Laser 23:41
20:53 Health Camilla & Jeff Yarm N Jogging Y arm 21:23
21:55 Health Landry & Rick Y-arm N Walk down the Arms. 22:25


 

LHO General
corey.gray@LIGO.ORG - posted 16:38, Thursday 17 October 2024 (80733)
Thurs EVE Ops Transition

TITLE: 10/17 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 7mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

Tony was addressing remaining items to allow H1 to get to OBSERVING at the beginning of my shift.  Environmentally, it's been windy the last 7hrs and has been slowly getting less windy; microseism is between the 50th & 95th percentile.  Jason is working on the spare NPRO in the Optics Lab.

Violin modes are about 2-orders of magnitude quieter than yesterday.

H1 ISC
elenna.capote@LIGO.ORG - posted 15:58, Thursday 17 October 2024 (80730)
PRCL coupling through other DOFs

Sheila and I have been investigating the source of the PRCL/DARM coupling that we observe. As a part of this investigation, Sheila has already run two sets of projections that investigate the PRCL coupling to DARM through the other LSC degrees of freedom, and through CHARD P and Y. Those can be found here: alog 80212 and alog 78969.

Today, I took the frequency noise injection from the noise budget, and added that projection to the total. To the point: PRCL coupling to DARM through frequency noise is smaller than PRCL coupling through the other LSC degrees of freedom, therefore it is not a significant source of coupling of PRCL to DARM. Figure 1 shows the projection of PRCL noise to DARM directly, as well as the projection through other degrees of freedom. Figure 2 shows all DOFs projected to DARM.

Some details:

The PRCL and frequency noise injections were rerun as a part of noise budget injections in 80596. The PRCL injection was run while CARM was only on REFL B, to better estimate the PRCL coupling through frequency noise.

The frequency noise injection is run by using REFL A as an out-of-loop sensor with CARM only on REFL B, therefore the frequency noise projection on one sensor will be higher by sqrt(2) in regions where CARM is limited by shot noise. In the past, we've estimated this to be below 4kHz, although we haven't checked recently. The frequency noise projection to DARM in these plots is divided by sqrt(2).

The notebook used to make these plots is located in /ligo/gitcommon/NoiseBudget/simplepyNB/PRCL_frequency_projections.ipynb

Images attached to this report
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 12:42, Thursday 17 October 2024 (80729)
Mid Shift update Comissioning plan & Lockloss.

TITLE: 10/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 13mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:


Lockloss from SQZrs PSAM activity.  
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1413215714

Relocking notes:
I had IMC Locking issues before entering into Initial_Alignment.

And then I had IMC Locking Issues in SR2 Alignment as well making Initial_Alignment incredibly difficult to Get into and Complete.
Sheila asked me to just take the IMC to Offline and wait until the PSL glitches stopped so we waited abotu 20 minutes. 
Took ISC_LOCK back to down and started a Manual Initial_Alignment @ SR2 Align.  


Reached Nominal Low Noise at 18:51 UTC

Commissioning activities started with:

Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 14:45, Tuesday 15 October 2024 - last comment - 10:25, Friday 18 October 2024(80687)
PSL NPRO Controller Swap

R. Short, J. Oberling

After the NPRO control box was swapped last week and glitches persisted (see alog80566), we decided it would be best to switch back to the original so that signal readbacks for the NPRO would be accurate. I started by bringing down the PSL in a controlled manner (ISS, FSS, PMC, AMPs, NPRO), then went out to the LVEA PSL racks and swapped control box S/N S2200008 for S2200009. Since this is the control box that had previously been in service with this NPRO laser head, no adjustments were needed to set the temperature and current to be correct. I returned to the control room and brought the whole system back up without issue.

Once it was time to lock the FSS, similar to what was needed with the last control box swap, I manually moved the NPRO temperature down about 0.4K (from 0.19 to -0.23) and locked the RefCav so that the SQZ laser would be happy. I then updated the FSS search parameters and accepted them in SDF (see screenshot).

As I noted in the 10-day trends yesterday (see alog80665), PMC REFL has risen over the past week, so I attempted a remote alignment tweak using the picomotors before the PMC. In the end, I wasn't able to make much of any improvement to the PMC alignment. I also attempted a remote alignment tweak for the RefCav, and here I was able to get a slight improvement from 0.80V to 0.81V on the TPD.

Looking for more things to try to impact the laser glitching and hopefully bring down the amount of PMC reflected power, Jason and I returned to the PSL racks to try adjusting the NPRO pump current. We ultimately raised the current from 2.12A to 2.19A, increasing the NPRO output power from 1.82W to 1.91W according to the PD in front of the laser, but not having much of an impact on the PMC. We also tried slightly altering pump diode currents in the amplifiers, but we didn't see any improvement, so these remain as they were.

I concluded our PSL activities today with a rotation stage calibration following the steps in alog79596. The measurement file, new calibration fit, and screenshot of accepting SDFs are attached.

  W (Max power in) D B (Min power angle) C (Min power in)
Old Values 94.642 1.990 -24.794 0.000
New Values 91.236 1.990 -24.797 0.000
Images attached to this report
Non-image files attached to this report
Comments related to this report
jason.oberling@LIGO.ORG - 10:25, Friday 18 October 2024 (80745)

Original NPRO injection current was 2.133 A, and the new injection current is 2.193 A.

H1 CAL
francisco.llamas@LIGO.ORG - posted 17:06, Monday 25 March 2024 - last comment - 17:32, Thursday 17 October 2024(76699)
Changed SDF values for Pcal Yend

DriptaB, LouisD, TonyS, FranciscoL

We noticed a 0.4% change from the value at the end of O4a for the X/Y ratio. We found alog 76562 where the Pcal EY EPICS values were changed. We have now changed them back to O4a values. See screenshot of SDF screen to find values. We will follow up with an updated value of X/Y to see if anything went wrong.

For future reference: steps to update SDF

  1. 'caput' the channels to be changed
  2. sitemap --> CAL EX(Y) --> GDS --> SDF TABLE --> ACCEPT (under select all, only afer triple checking numbers) --> CONFIRM.
  3. SDF RESTORE SCREEN --> ! SELECT REQUEST FILE --> open "safe.snap" --> LOAD TABLE. Look for differences and confirm changes if needed (was not needed for EY).
  4. Load OBSERVE.snap by following step (3).
  5. Open FORCE COEFF CALCULATION and check that changes were applied.
Images attached to this report
Comments related to this report
anthony.sanchez@LIGO.ORG - 17:32, Thursday 17 October 2024 (80736)

UPDATED Instructions!!!
For future reference: steps to update SDF

  1. 'caput' the channels to be changed
     
  2. Open OBSERVE.snap by following these steps:
    sitemap --> CAL EX(Y) --> GDS --> SDF TABLE 
     
  3. Save the new EPICS value to OBSERVE.snap:
    Find the channel that you have changed the EPICS variable for and click the ACCEPT button on the far right.  (under select all, only afer triple checking numbers).  then Please make sure you click the big green CONFIRM button.
    Open FORCE COEFF CALCULATION and check that changes were applied.
    Congratulations you just saved EPICS values to OBSERVE.snap!
     
  4. Load safe.snap by following these steps:
    SDF RESTORE SCREEN --> ! SELECT REQUEST FILE --> open "safe.snap" --> LOAD TABLE. Look for differences and confirm changes if needed.
     
  5. Save the new Epics values into the Safe.snap by following step 3 again from here.
     
  6. To confirm that your values were correctly saved into the safe.snap file please use the following terminal commands:
    Check Xarm values:
    cat /opt/rtcds/lho/h1/target/h1calex/h1calexepics/burt/safe.snap | grep FORCE_COEFF && cat /opt/rtcds/lho/h1/target/h1calex/h1calexepics/burt/safe.snap | grep XY_COMPARE_CORR_FACT

    Check Yarm Values:
    cat /opt/rtcds/lho/h1/target/h1caley/h1caleyepics/burt/safe.snap | grep FORCE_COEFF && cat /opt/rtcds/lho/h1/target/h1caley/h1caleyepics/burt/safe.snap | grep XY_COMPARE_CORR_FACT

    If that didn't work..... please request expert assistance for more guidance.
Displaying reports 9861-9880 of 88268.Go to page Start 490 491 492 493 494 495 496 497 498 End