Displaying reports 17321-17340 of 88572.Go to page Start 863 864 865 866 867 868 869 870 871 End
Reports until 14:52, Wednesday 11 October 2023
H1 ISC
camilla.compton@LIGO.ORG - posted 14:52, Wednesday 11 October 2023 - last comment - 16:21, Wednesday 11 October 2023(73393)
MICH and SRCL LSC FF Remeasured

Camilla, Jenne. Started in 73345. H1 had been locked ~5 hours.

Didn't exactly follow instructions in lsc/h1/scripts/feedforward/README.md, as took residual measurements with no FF and took FF measurements with actuation through ETMY PUM rather than ETMX. 

Non-image files attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 16:21, Wednesday 11 October 2023 (73398)

Gabriele helped fit the filters and we saved them to MICHFF and SRCLFF as 10-11-23-EY. 

H1 General
thomas.shaffer@LIGO.ORG - posted 14:25, Wednesday 11 October 2023 (73390)
Lock loss 2123 UTC

Lock loss was a control room user caused loss. Relocking now but we are also in the middle of a smaller earthquake.

H1 CAL
thomas.shaffer@LIGO.ORG - posted 14:08, Wednesday 11 October 2023 (73389)
Calibration Simulines ran

Tony followed the instructions on the wiki and ran a broadband and then simulines measurement. I'm getting the start time from when the PCAL signal started, end time is from the script.

Start: 1381086932

End: PDT: 2023-10-11 13:48:41.623282

UTC: 2023-10-11 20:48:41.623282

GPS: 1381092539.623282

 

2023-10-11 20:48:41,458 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20231011T202627Z.hdf5

2023-10-11 20:48:41,480 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20231011T202627Z.hdf5

2023-10-11 20:48:41,496 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20231011T202627Z.hdf5

2023-10-11 20:48:41,509 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20231011T202627Z.hdf5

2023-10-11 20:48:41,523 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20231011T202627Z.hdf5

H1 SQZ
naoki.aritomi@LIGO.ORG - posted 14:01, Wednesday 11 October 2023 (73388)
ZM6 output is close to saturation due to reset of SQZ ASC offset during homodyne work

Naoki, Vicky

Today we found that ZM6 output is close to saturation. We looked at ZM6 output and found three jumps in ZM6 output yesterday as shown in the attached figure. The first and third jumps are from the Set ZM HD and Set ZM IFO for homodyne work yesterday. The second huge jump (~10000) appeared in ZM5/6 and this would be the cause of the ZM6 saturation. This huge jump happened when the SQZ_MANAGER guardian moved from LOCK_CLF(30) to SQZ_READY_HD(40) at 12:30 PDT yesterday and this would be the cause of the strange seed alignment jump happened during homodyne work yesterday as reported in alog73365. We looked at SQZ_READY_HD state in SQZ_MANAGER guardian and found that there is a reset of SQZ ASC offset in the state. We commented out this offset reset. We need to offload ZM6 again as alog73171.

Images attached to this report
H1 ISC
camilla.compton@LIGO.ORG - posted 13:59, Wednesday 11 October 2023 (73384)
PRCL OLG Measurement Taken

As suggested by Elenna/Jenne, ran the /lsc/h1/templates/PRCL/PRCL/PRCL_OLG_NOISE_FULL_LOCK_NLN.xml PRCL open loop gain measurement.

This was with H1:LSC-PRCL1_GAIN at 10 and H1:LSC-PRCL2_GAIN at 1, after 4h35 at NLN. Cursor is on 22.5Hz, gain 1, phase 22.7 deg. Plot attached. This is fine and similar to last measurements (70692, 70664).

Images attached to this report
H1 ISC
jenne.driggers@LIGO.ORG - posted 13:05, Wednesday 11 October 2023 - last comment - 14:41, Wednesday 11 October 2023(73385)
NonSENS cleaning turned on during commissioning

While we're commissioning this afternoon, I've got NonSENS cleaning engaged.  I've also temporarily accepted the SDF diff that turns on the cleaning, so that we can see the range of the _CLEAN channel in real time (this is why our range is high on our control room screenshots right now). 

The NonSENS cleaning was on starting a few tens of seconds before 20:00:00 UTC today, and I intend to leave it as-is for at least an hour.  Robert is doing work at this time, but it's quite minimally invasive, so this time should still be useful for PE verification software injections that are a part of the review of the cleaning.

Comments related to this report
jenne.driggers@LIGO.ORG - 13:12, Wednesday 11 October 2023 (73386)

Here is a plot showing the effect of the cleaning that is currently ongoing.  Since Robert was able to significantly mitigate the 120 Hz peak yesterday, there is not much difference between the strain channel and the cleaned channel there anymore.  But, our LSC FF needs tuning (measurements to be taken later this commissioning period), so there's lots of effect down there.

Both the Jitter and LSC noises were retrained on data from our most recent lock.  The high frequency laser noise I havne't retrained in several weeks, and it's still doing quite nicely.

Images attached to this comment
jenne.driggers@LIGO.ORG - 13:24, Wednesday 11 October 2023 (73387)

This quiet period ended at 20:22 UTC (for calibration measurements).

jenne.driggers@LIGO.ORG - 14:41, Wednesday 11 October 2023 (73392)

Attached is the range plot from the control room wall, where we can see the improvement due to the cleaning being engaged.

Since we have lost lock, I re-accepted in the h1oaf Observe.snap file the correct value of 0 gain for H1:OAF-NOISE_WHITENING_GAIN, so NonSENS will be off (without any SDF diffs) when we get relocked.

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 10:38, Wednesday 11 October 2023 (73382)
Wed CP1 Fill

Wed Oct 11 10:11:20 2023 Fill completed in 11min 16secs

Jordan confirmed a good fill curbside.
 

Images attached to this report
H1 PEM (DetChar)
oli.patane@LIGO.ORG - posted 10:12, Wednesday 11 October 2023 - last comment - 15:18, Wednesday 11 October 2023(73320)
EX Chiller Versus Range Investigation

Tyler "has recently changed the chiller pumps to not be on at all times and come on when needed. He gave me some data for when the EX chiller has been turning on and off over the last 2.5 weeks" (TJ, 2023). I took this data and plotted it against our range as well as the average internal temperature at EX to see if we would lose range when the chiller at EX turned on(attachment1).

Over this date range, the longest amount of time that the chiller was on consistently was for just over two hours. With both these longer segments and the more regular shorter segments of 'on' time (sometimes just 10 minutes on), there is no noticeable change in the range when the chiller turns on or off. There are multiple times where the range trends downward after the chiller starts turning on for longer stretches of time (red attachment2), but it is not consistent - yellow(attachment3) and green(attachment4) rectangles show the range rising with chiller 'on' times. Therefore I am inclined to attribute the lowering of the range during these times as being due to changes in indoor/outdoor temperatures and wind and not the chiller.

Images attached to this report
Non-image files attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 11:32, Wednesday 11 October 2023 (73383)FMP

Tagging Facilities as well.

Thank you for getting these out Oli, this is great! I agree with you that it doesn't seem like this chiller pump has any direct impact on our range, though perhaps we might want to consider looking further into a possible correlation of VEA temps and our range.

tyler.guidry@LIGO.ORG - 15:18, Wednesday 11 October 2023 (73394)
Clarification: It is not the chiller "pump" that was reconfigured to run only when demanded. It was the chiller themselves. It's also not clear that this was the status quo for all chillers across site. It was only recently discovered on one chiller in particular. 

The chiller "pump" has always and will continue to run regardless of the state of the chiller itself as glycol needs to be continually cycled through the AHU cooling coils at all times.
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 08:13, Wednesday 11 October 2023 (73381)
Wednesday Ops Eve Shift Start

TITLE: 10/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 13mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.62 μm/s
QUICK SUMMARY:

Locked for 5 hours when I arrived.
Everything Seemed to look great,
15:02 UTC a seemingly random lockloss occured.
Richard informed me that the Dust monitors in the PSL were alarming again , likely due to the elevated wind speeds.
 

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 00:01, Wednesday 11 October 2023 (73380)
Ops Eve Shift Summary

TITLE: 10/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:

LOG:

No log for this shift.

H1 PEM
robert.schofield@LIGO.ORG - posted 18:55, Tuesday 10 October 2023 (73378)
120 Hz peak mitigation: periscope resonances tuned and fan SF2 turned off

During maintenance today I adjusted weights on the PSL periscope to try to reduce the DARM peak in the 120 Hz region. I reduced the highest part of the peak where the HVAC-produced seismic peak overlaps with a periscope peak,  by about 3/5.  Also, with the consent of Tyler, I shut off SF2, which is mainly responsible for the new HVAC peak, reducing the total LVEA flow from 31k CFM to about 27k CFM. Before the pandemic we ran with two fans pushing about 10k CFM each for a total of about 20k CFM, so I dont think it will be too much of an issue. I have been monitoring LVEA temperature and it looks like the excursions are getting smaller.

The improvement at 120 Hz is looking pretty good, more details later.

H1 General (Lockloss, SEI)
ryan.short@LIGO.ORG - posted 18:52, Tuesday 10 October 2023 - last comment - 21:16, Tuesday 10 October 2023(73377)
Lockloss @ 01:43 UTC - EQ

Lockloss @ 01:43 UTC from several earthquakes in Afghanistan (M6.3 followed by aftershocks of M5.0 and M4.1). Earthquake mode first activated at 00:59 UTC when the initial S-wave hit.

Holding H1 in DOWN until ground motion calms down.

Comments related to this report
ryan.short@LIGO.ORG - 21:16, Tuesday 10 October 2023 (73379)

H1 is back to observing as of 04:14 UTC

LHO General
ryan.short@LIGO.ORG - posted 16:07, Tuesday 10 October 2023 (73375)
Ops Eve Shift Start

TITLE: 10/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 12mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY: H1 has been locked and observing for 2 hours.

H1 General
anthony.sanchez@LIGO.ORG - posted 16:00, Tuesday 10 October 2023 (73374)
Tuesday Ops Day Shift END


TITLE: 10/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
Tuesday maintenance day recovery went well.
There was a H1:PSL-ENV_LASERRM_ASC_TEMP_DEGF  Channel That isstill getting back to nominal temps in the PSL
The PSL Dust mon has been going off since the wind has started to pick up.
H1 has been locked for 2 Hours and 12 Minutes.
LOG:
                                                                                                                

Start Time System Name Location Lazer_Haz Task Time End
15:05 TCS Camilla CtrlRm n Blasting CO2 EX 15:50
15:08 FAC Randy EX,EY N Taking Trailer to EY & EX 17:08
15:09 VAC Janos FTCE N Counting Particles 15:21
15:10 FAC Cindy HAM Shaq N Technical Cleaning and recycling Cardboard 17:10
15:11 FAC Kim EX N Technical Cleaning 16:30
15:12 FAC Karen EY N Technical Cleaning 16:30
15:22 VAC Janos Travis Mid X and EX N Vacuum Work 17:22
15:23 EE FIL CER N ITMX Coil driver work needs SUS and HEPI SAFE 15:42
15:30 CDS Dave B. Remote N Picket Fence work 17:30
15:31 VAC Jordan Gerardo FTCE N Ion Pump install 18:31
15:32 Tour Matt H & Co FTCE & LVEA N RAL Tour 16:52
15:35 PSL Jason CtrlRm N PSL Refcav tuning 15:39
15:36 PEM Robert PSL YES Tuning Periscope Resonate Freq 17:36
15:45 EE Fil & Marc LVEA N PEM Inventory 17:17
15:52 FAC Tyler & Mc Miller EY N Chiller Maintenance. 18:02
16:01 SQZ Shelia & Vicky SQZt0&7 LOCAL Homodyne Alignment 19:17
16:22 SQZ Jeff, Regina & Doortea LVEA LOCAL Crashing the RAL Party and Joinin SQZrs 16:49
16:41 PEM Fil MIDX N Looking for part numbers 17:01
16:47 OMC Keita HAM6 N Plugging in Beckhoff cable to OM2 16:50
16:59 RAL Matt H &Co Roof N RAL Tour to Roof 17:17
17:01 SQZ Camilla & Doortea LVEA SQZt0 LOCAL Helping Sheila & Vicki with SQZ work 19:26
17:04 FAC Kim & Karen LVEA N Technical Cleaning 18:48
17:48 Hartman Camilla LVEA YES LASER HAZARD TRANSITION 19:33
18:03 VAC Travis & janos LVEA Yes VAC Work with Laser Haz Goggles. 18:04
18:24 EE Marc & Fil ISCT1 Yes Documenting Cabling at ISCT1 18:47
18:26 OM2 keita HAM6 yes Undoing the  Beckhoff and OM2 Changes this morning 18:27
18:56 VAC Jordan BSC3 YES Opening FIlter Cav Gate valve 19:11
19:53 VAC Travis Mid Y N Vacuum work 21:23
19:56 PEM Robert PSL AntiRoom No Checking PSL AC For proper Functionality 20:12
19:57 SQZ Sheila & Camilla SQZt7 Local Touching up SQZ settings 20:27
20:29 FAC Mitchel Mechanical Room N Checking HEPI Pumps and Dust Monitors 20:59

 

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 14:03, Tuesday 10 October 2023 - last comment - 18:31, Tuesday 17 October 2023(73365)
homodyne measurements today

Vicky, Sheila, Camilla, Dorotea, Naoki

We went to SQZT7 this morning with the new homodyne (73241).  In the end we wer able to see decently flat shot noise and decent visibility.  On the way, we ran into some difficulties that caused some confusion:

In the end we have flat shot noise, and a visibility of 98.5% measured on PDA (3.07% loss) and visibility of 97.8% (4.44% loss) measured on PDB.  The nonlinear gain of 11 measured with seed max/ no pump. A comment to this alog will contain the measured sqz/asqz/mean sqz.

Comments related to this report
victoriaa.xu@LIGO.ORG - 13:47, Wednesday 11 October 2023 (73376)

Screenshot summarizing homodyne measurements today. With measured carrier NLG=11 (for generated squeezing ~14.7-14.8 dB), we observe

  • squeezing           = - 6 dB
  • anti-squeezing    = +13.5 dB
  • mean-squeezing = +10.5 dB

Comparing sqz/anti-sqz to generated sqz: ~7% unexplained homodyne losses. This is consistent with our last estimate of excess HD losses (8/29/2023, LHO:72802, ~7% mystery loss). Since then, we swapped the HD detector and improved readout losses (visibility). We now measure more homodyne squeezing at 6 dB, consistent with expected loss reductions. That is compared to 8/29 (LHO:72802), we have less total loss, less budgeted hd loss && more squeezing, but the same unexplained hd losses as before.

Comparing mean-squeezing to generated sqz: could be consistent with sqz/asqz losses. I think there is a mis-estimate of the generated squeezing level from non-linear gain. If we ignore our NLG11 measurement, and instead use the generated squeezing level to match observed 13.5 dB of anti-squeezing, then we allow losses to determine the measured 6 dB squeezing level, we would have an NLG=10 (not 11) for a generated squeezing level of 14.5 dB. This would suggest 7% unexplained losses, same as the sqz/asqz measurements.

For ~7% mystery losses, this is compared to total HD losses of 21%, of which we budget 15% losses. From the sqz wiki, the budgeted losses are:

  • opo escape 98.5% 
  • in-chamber ham7 95.3%
  • beam diverter 99%
  • SQZT7 on-table optics losses 2% (72604)
  • HD PD QE 97.7%  (73241)
  • visibility 95.6%  (from 97.8% fringe visibility on PD B) 

If we include phase+dark noise that degrades squeezing but is not loss, then 21% total loss can explain the 6dB measured squeezing, see e.g. from the gsheet calculator (edited to include ranges for NLG=10 and NLG=11):

    SQZ   ASQZ
NLG                    10 - 11
x  (0.68, 0.70)  (0.68, 0.70)
gen sqz (dB)  (-14.5, -15.01)   (14.5, 15.01) 
with throughput eta =                       0.79
meas sqz (dB)  (-6.24, -6.29)  (13.54, 14.03) 
with phase noise (mrad) =                      20.00
meas sqz (dB)  (-6.08, -6.11)  (13.54, 14.03)
with dB(Vtech/Vshot) =                    -22.00
var(v_tech/v_shot)   0.0063   0.0063
meas sqz (dB)   (-5.97, -6.00)    (13.54, 14.03) 

DTT homodyne template saved at $userapps/sqz/h1/Templates/dtt/HD_SQZ/HD_SQZ_101023.xml .

Edited to include some history of homodyne measurements:

  • 6 dB SQZ -  10/10/23 LHO:73365 = 21% total loss, 15% known loss, 7% mystery (this time)
  • 5.2dB SQZ - 8/31/23, LHO:72802 = 27% total loss, 21% known loss, 7% mystery (bad PD-B QE, lower visibility?)
  • 5.5dB SQZ -   2/3/23, LHO:67219 = 25% total loss, 15% known losses, < 10% mystery (tech noise -10dB), NLG was varied.

It could still be interesting to vary NLG to see if we can obseve any more squeezing, or if an additional technical noise floor (aside from dark noise) is needed to explain the NLG sweeps.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 17:02, Wednesday 11 October 2023 (73395)

We revised the sqz loss wiki table again today, and are including it to explain what we think our current understanding of losses is. 

It seems likely that the 7% extra losses we see on homodyne measurements are in HAM7, so we've nominally added that to the loss budget. 

In addition to this, there would be an additional 8% loss on the sqz beam if we didn't correct it's linear polarization with a half wave plate.  72604  At the time of the chamber close out, (65110) we measured throughput from HAM7 to HAM5 that would implies that two passes through the OFI were giving us 97.6% transmission, so this is not compatible with the polarization being wrong by this much.  We haven't included this as a loss in the loss budget because it seems incompatible with our measurement in chamber. 

The wiki currently lists the OMC transmission as 92%, and the PD QE as 98%.  The PD QE may be worse than this (see 61568), but measurements of the product of QE and OMC transmission for 00 mode seem to indicate that is in the range 90-92%, so this is close. 

With the infered losses of from the measured sqz/anti-sqz in the IFO, the plausible range of losses is 30-35%, we are using 32%.  With only known losses (including the values for OMC trans and PD QE), we have 14% unexplained loss. If we include the 7% apparent HAM7 losses, we have 9% unexplained losses in the IFO.  This does seem similar to the 8% polarization problem, but it would also include SQZ-OMC mode matching.  

Possible future scenarios:  We may be able to reduce the 7% HAM7 losses, and we may be able to swap the OMC to reduce those losses from 92% to 97%.  

  total efficiency resulting sqz measured without subtraction (technical noise -12dB below shot, 20mrad phase noise) if technical noise is 20dB below unsqueezed shot noise
fix HAM7 losses 0.73 4.4dB 5dB
swap OMC (92%-> 97%) 0.71 4.14dB 4.8dB
swap OMC and fix HAM7 losses 0.77 4.85dB 5.6dB
swap OMC, fix HAM7 losses, and fix 8% from polarization issue (if that is real) 0.84 5.83dB 6.8dB

These numbers come from the aoki equations that Vicky added to the google sheet here: gsheet

 

Images attached to this comment
victoriaa.xu@LIGO.ORG - 18:31, Tuesday 17 October 2023 (73537)

Don G. and Sheila have very likely resolved the homodyne polarization issue as being due to the SQZT7 periscope. So, the mis-polarization is likely not an issue for squeezing in the interferometer.

The sqz beam leaves HAM7 via reflection off the sqz beam diverter. From the latest CAD layout from Don, the outgoing reflected beam (blue) is ~75.58 degrees from global +X. The periscope re-directs the beam to travel along SQZT7, approximately along +Y. The CAD layout thus suggests that the SQZT7 periscope re-directs the beam in yaw (counter-clockwise) by an estimated 90 - 75.58 = 14.4 degrees

From recent homodyne measurements LHO:72604, of the sqz light leaving HAM7 and arriving on SQZT7, ~8% of the power was in the wrong polarization, this calculates to a ~16.5 degrees polarization misrotation. Compared to this 16.5 degree misrotatation we were searching for, the 14.4 degrees polarization rotation induced by the periscope image rotation can plausibly explain the misrotation.

Images attached to this comment
Displaying reports 17321-17340 of 88572.Go to page Start 863 864 865 866 867 868 869 870 871 End