Displaying reports 3981-4000 of 83106.Go to page Start 196 197 198 199 200 201 202 203 204 End
Reports until 09:10, Tuesday 26 November 2024
H1 PSL
ryan.short@LIGO.ORG - posted 09:10, Tuesday 26 November 2024 (81485)
PSL 10-Day Trends

FAMIS 31061

This week's trends capture how things compare pre- and post-NPRO swap towards the end of last week. Generally things are looking good and have been stable since the swap with probably the most notable change being the drop in PMC transmitted power by ~2W and rise in reflected power by ~5W. We suspect this to be due to slightly worse mode-matching into the PMC, which we plan to check in the coming weeks.

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 07:46, Tuesday 26 November 2024 (81483)
Ops Day Shift Start

TITLE: 11/26 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 3min avg
    Primary useism: 0.12 μm/s
    Secondary useism: 0.32 μm/s
QUICK SUMMARY: H1 lost lock this morning at 14:12 UTC due to a M6.1 quake out of Japan and has been down since (meaning magnetic and charge measurements were not run). Moving ISC_LOCK to 'IDLE' and SEI_ENV to 'MAINTENANCE' for maintenance day.

H1 CDS
erik.vonreis@LIGO.ORG - posted 06:49, Tuesday 26 November 2024 (81482)
Workstations updated

Workstations were updated and rebooted.  This was an OS packages update.  Conda packages were not updated.

LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 22:02, Monday 25 November 2024 (81481)
OPS Eve Shift Summary

TITLE: 11/26 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 04:24 UTC

Overall a pretty calm shift with one Lock Acquisition that required an initial alignment - all fully auto.

Of note:

LOG:

None

H1 ISC (Lockloss)
ibrahim.abouelfettouh@LIGO.ORG - posted 19:10, Monday 25 November 2024 (81479)
Lockloss 02:51 UTC

Unknown cause Lockloss (confirmed not PSL/IMC). While microseism is high, there weren't any EQs or other PEM events to cause an LL.

The Lockloss analysis tool is giving an OMC DCPD tag

LHO General
corey.gray@LIGO.ORG - posted 16:30, Monday 25 November 2024 - last comment - 20:13, Monday 25 November 2024(81457)
Mon DAY Ops Summary

TITLE: 11/25 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:

A bit of a busy morning with convoys of concrete trucks arriving onsite (for a pour for the new storage warehouse), discovering a ringing up violin mode, and then getting ready for Monday Morning Commissioning!  

Rahul has new violin settings for ETMy Mode1 and ITMy Mode5 (aka 05 & 06)--see alog81465 .  Operators will need to enter these settings by hand until Rahul accepts them.

Also:  If H1 drops out of Observing, be sure to LOAD the guardians she mentions in alog81474.

H1 is currently at 13.5hrs for this current lock (and that's even after a low fly-by from a chinook helicopter!).
LOG:

Comments related to this report
david.barker@LIGO.ORG - 16:57, Monday 25 November 2024 (81478)

The helicopter can be clearly heard in the LVEA on H1:PEM-CS_MIC_LVEA_BS_DQ

Non-image files attached to this comment
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 15:57, Monday 25 November 2024 (81477)
OPS Eve Shift Start

TITLE: 11/25 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.55 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 19:35 UTC (13 hr lock)

Everything seems quiet, especially violins, which have been a recent issue.

H1 ISC (SUS)
ibrahim.abouelfettouh@LIGO.ORG - posted 15:56, Monday 25 November 2024 (81476)
Investigating SRM M3 WD Trips During Initial Alignment

Ibrahim, TJ

Beginning after the first NPRO Swap recovery on 10/30, there have been 7 or so instances of SRM M3 tripping during PREP_FOR_SRY in initial alignment, predominantly due to Y saturation. TJ and I are investigating.

So far, we know that SRM sees elevated noise while in PREP_FOR_SRY, particularly after SRM re-alignment. We've also found that AS_C SUM is too low to be considered locked at this state, but that ALIGN_IFO guardian continues with SR initial alignment, leading to the WD trip. The current hypothesis is that SRM is catching onto a wrong mode, but tricking the automation into continuing alignment.

The first screenshot shows the incidence of the WD tripping during initial alignment happening frequently after 10/30. There is one instance of it happening 10/16 but nothing in the near past before that.

The second shows one recent instance of this trip, leading to the WD trip.

Images attached to this report
H1 OpsInfo (OpsInfo, PEM, SUS, TCS)
camilla.compton@LIGO.ORG - posted 14:38, Monday 25 November 2024 (81474)
PEM and SUS In-lock charge Injections to start early at 7am and 7:25am tomorrow

I edited the sys/h1/guardian/injparams.py and  sus/h1/guardian/SUS_CHARGE.py code to move the magnetic injections and in-lock charge measurements 20 minutes earlier tomorrow, usual start times are 7:20am and 7:45am. Moved to 7 am and 7:25am, should be over by 7:40am. If we drop out of observing, can an operator please reload PEM_MAG_INJ and SUS_CHARGE guardians.

Aim to turn CO2 laser off  at 7:40am tomorrow, before the lockloss to see if we see similar SQZ alignment changes related to CO2 lasers as LLO does: 72244.

H1 AOS (DetChar, PEM)
adrian.helmling-cornell@LIGO.ORG - posted 14:20, Monday 25 November 2024 (81473)
HAM 2 Accelerometer Transients - Electronics Problem?

Adrian, Robert S.

We examined hours-long stretches of data from the H1:PEM-CS_ACC_HAM2_PRM_Y_DQ accelerometer because it featured a few short-duration, broadband transients every hour (figure 1). These transients are not seen in other chamber accelerometers or GS13s (figure 2), so we suspect the cable or signal conditioning box for the accelerometer is failing. It sounds like Lance has some time to check this tomorrow during the maintenance period.

Non-image files attached to this report
H1 SUS (SUS)
ryan.crouch@LIGO.ORG - posted 12:38, Monday 25 November 2024 (81469)
OPLEV charge measurements, ETMX, ETMY

On 11/12/24 Rahul ran the OPLEV charge measurements, I processed them this afternoon...

ETMY's charge seems to be slightly trending up in UL and LL but looks stagnant in UR. The charge is >= 50 V in LL_{P,Y} and UL_Y.

ETMX's charge looks to have a small upwards trend and is >= 50 V in all DOFs and quadrantss. The charge looks to have risen ~5-10 V in a little over a month over the DOFs and quadrants. The error in the measurement for EX is also larger than we usually see, the secondary microseism was elevated during these measurements.

Images attached to this report
H1 ISC
elenna.capote@LIGO.ORG - posted 12:08, Monday 25 November 2024 - last comment - 12:26, Thursday 12 December 2024(81468)
High Frequency OMC DCPD data taken during no sqz time

Today we ran a correlated noise measurement for 1 hour starting at 1416594379, meaning that the detector was locked, thermalized, and with no squeezing engaged for this period of time. We left calibration lines on during the measurement. The measurement was preceeded by a calibration measurement as well, see alog 81461.

During the measurement I ran a script that I edited from Sander Vermeulen that collects the full 524kHz OMC DCPD channels (H1:OMC-DCPD_{A,B}0_IN1) (see Jeff Kissel's comment in alog 69398 which gives a good description of how these channels are created). The data from these two channels was saved in in hdf5 files as 1 second frames. Those files can be found in /ligo/home/elenna.capote/OMC_DCPD/242511-102557/, and on the DCC at this file card: T2400394.

Sheila noted one large glitch at UTC 18:35, so this data may need to be gated around that time.

Edit: the resulting zip file is 9GB so the DCC cannot host it. I am thinking of other ways to share this data with others....

Editedit: added box link to DCC for data access.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:26, Thursday 12 December 2024 (81798)
This data has been posted to the DCC here: T2400394.
H1 ISC
sheila.dwyer@LIGO.ORG - posted 11:21, Monday 25 November 2024 - last comment - 13:10, Monday 25 November 2024(81464)
sensitivity comparison, running A2L decoupling

Over the weekend, we've had greatly improved stability because of the PSL swap.  The IFO range has been mostly below 160Mpc, with short times near 165Mpc in the first hour of each lock.

The first attachment shows a comparison of the cleaned GDS strain sensitivity at the 165 Mpc time to later in the lock, along with coherences from the lower range time.  The sensitivity earlier in the lock was broadly better from 18-55 Hz, there are coherences with both ASC and LSC that are contributing to the noise from 18-27 Hz so we spent some time trying to address those.  The worse sensitivty from 27-55 Hz is not explained by these coherences, and the usual squeezing adjustments (81463 81458) don't seem to be able to help.  We might think about checking both the SRC detuning and the filter cavity detuning to see if they make an impact in this region.  We do seem to have slightly less high frequency squeezing than in the past.

To address the ASC coherences, I ran the A2L script that TJ put in userapps/isc/h1/scripts/a2l/a2l_min_multi.py  with the command python a2l_min_multi.py --all  The second attachment shows this script running, using an ndscope template that is in sheila.dwyer/ndscope/ASC/A2L_script_ADS.yaml  The first time through the pitch a2l gains for ETMY, ITMY and ITMX were all set to the maximum that the script checks, so we ran it again.   The third attachment shows the coherences (with no squeezing) after this A2L adjustment and Camilla's adjustment of the PRCL feedforward.   In the past we've seen that after running this a2l script we can do slightly better by dong a manual adjustment based on injections into CHARD or DHARD, (79921  80250) we haven't taken the time to check that today, but the script does seem to have helped in the frequency region where it's measuring.  It has made the CHARD Y coherence worse below 15 Hz, which we've seen consistently when the decoupling is good around 20-30 Hz. 

The last attachment shows a comparison of the DARM sensitivty in the high range early part of the lock, the lower later sensitivity, and currently after these retunings but without squeezing.  This suggests that our adjustments did a good job below 27 Hz where we the squeezing does have an impact in this frequency band where we haven't yet recovered the sensitivity.

Old A2L settings:

        'FINAL':{
            'P2L':{'ITMX':-1.0,
                   'ITMY':-0.39,
                   'ETMX':2.98,
                   'ETMY':4.72},
            'Y2L':{'ITMX':3.05,
                   'ITMY':-2.43, #+1.0,
                   'ETMX':4.9,
                   'ETMY':1.42 }

New A2L settings:

        'FINAL':{
            'P2L':{'ITMX':-0.66,
                   'ITMY':-0.05,
                   'ETMX':3.12,
                   'ETMY':5.03},
            'Y2L':{'ITMX':2.980,
                   'ITMY':-2.52, #+1.0,
                   'ETMX':4.99,
                   'ETMY':1.34 },

 

 

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 12:27, Monday 25 November 2024 (81470)

Attached updated plot. It seems that these commissioning changes made the range better 10-30Hz, maybe look 50-90Hz. No SQZ is slightly better right at 20Hz.

Also attache is range BLRMs, showing main change is 20-29Hz region.

Images attached to this comment
ryan.crouch@LIGO.ORG - 13:10, Monday 25 November 2024 (81471)

Running the range comparison script comparing the time of the best range early this morning (11:30UTC) to a time a few hours later (16:15 UTC) and currently (20:30 UTC) using 15 minutes of data. It looks like SQZer differences and violins, since its seen in broadband high and low frequency, and I can see the ~500Hz line rising from ETMY 1 and ITMY 5/6 for the first time span. That line is reduced in the following check, after new damping settings are put in. A line at 300Hz also looks to have grown slightly.

The blue traces are the reference good range time from the beginning of the lock.

Non-image files attached to this comment
H1 ISC
camilla.compton@LIGO.ORG - posted 11:01, Monday 25 November 2024 (81467)
PRCL FF Gain Tuned

After Sheila adjusted the A2L gains we checked on MICH and PRCL coherence suing the injections inlsc/h1/scripts/feedforward/{DOF}_excitation.xml.

MICH looked fine (attached).

Did not check SRCL, as originally there looked to be no SRCL/DARM coherence (e.g. 81451). After the other changes, there is now some SRCL coherence (shown in Sheila's alog). We could we tuning this gain in a future commissioning time.

PRCL looked bad, the "no FF" trace as considerably changed too (blue to green), unless the old reference was with a different injection. This could be because we unclipped LSC POP 81329. We reduced the PRCLFF gain until it started to get worse again, leaving the gain at 0.6. Plot attached: changed from purple to black which is an improvement < 60Hz and maybe worse 60-70Hz.
Accepted in safe and observe sdf's and edited lscparams.py, ISC_LOCK reloaded. Maybe worth remeasuring and fitting this PRCLFF.
Images attached to this report
H1 SUS (SUS)
rahul.kumar@LIGO.ORG - posted 10:38, Monday 25 November 2024 - last comment - 15:53, Monday 25 November 2024(81465)
Violin modes - new settings for ETMY 01 and ITMY05/06

I have found new damping settings for ETMY mode01 and ITMY mode05/06, which are given below,

ETMY01

Nominal - FM1+FM6+FM10, Gain = +0.1 (+30deg phase)

New - FM1+FM8+FM10, Gain = +0.1 (+60deg phase)

 

ITMY 05/06

Nominal - FM5+FM6+FM7+FM10, Gain = +0.02 (-30deg phase)

New - FM5+FM6+FM8+FM10, Gain = +0.01 (+30deg phase)

I have not made any changes in the lscparam file, will check these new settings for a few lock stretches (also let microseism to settle down) before making them final.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 15:53, Monday 25 November 2024 (81475)OpsInfo, SUS

Tagging OpsInfo

So once Rahul is happy with the new Violin Mode settings for ETMy 01 & ITMy 05/06, Operators will need to enter his NEW settings by hand (this can be done any time after the DAMP_VIOLINS_FULL_POWER [566] state.  For clarity, also attaching screenshots with the filter banks in question circled in light blue:

  • ETMy 01 = ETMy MODE1
  • ITMy 05/06 = ITMy MODE5
Images attached to this comment
H1 PSL
jason.oberling@LIGO.ORG - posted 19:16, Friday 22 November 2024 - last comment - 10:55, Monday 25 November 2024(81426)
PSL NPRO Swap: It's Done, Again (WP 12210)

V. Xu, R. Short, J. Oberling

Short short version: The PSL NPRO swap is done and IFO recovery has begun.  I'll get a more detailed alog in tomorrow, right now I'm exhausted.

Comments related to this report
jason.oberling@LIGO.ORG - 10:55, Monday 25 November 2024 (81462)

Promised details from the final day of the NPRO swap.

Summary

  • Measured mode matching lens positions to update PSL table as-built drawing
  • Recovered both amplifiers without issue, final total output power of ~140.2 W
  • Locked PMC, adjusted alignment, returned amplifier pump diode currents to previous operating levels; Amp1 out now ~68 W, Amp2 out now ~139 W, PMC Trans ~104 W, PMC Refl ~24 W
    • Have some PMC mode matching work to do, will do in future maintenance periods
  • Locked ISS, had weird issue with PD values in MEDM (see details below), found it was due to NPRO noise eater needing a reset
  • Locked FSS, had ~0.84 V TPD with no IMC
  • Scanned NPRO temperatures for mode hopping, settled on NPRO crystal temperature of 23.96 °C
  • Measured stabilization system TFs and set gains; all gains unchanged except FSS Common gain changed from 15 dB to 14 dB

Mode Matching Lens Positions

We first measured the new positions of mode matching lenses L02 and L21, I'll update the As-Built table layout with the new values.  The new positions:

  • L02: 1251.5 mm
  • L21: 1137.5 mm

Amplifier Recovery

With the previous day's work resulting in the NPRO being ready for amplifier recovery, this is where we started our recovery work.  Amplifier recovery was straightfoward.  As a reminder, we first measure the power into the amp and the unpumped power out, to assess our intial alignment.  Then we raise the amp pump diode operating current in 1A intervals until we get to the locking point, adjusting beam alignment into the amplifier at each step in current (so alignment follows the formation of the thermal lenses in the amplifier crystals).  For Amp1 we had 1.612 W input and an unpumped output of 1.252 W.  This is 77.6% throughput, which is above our requirement of 65% throughput before starting to pump the amplifier, so we proceeded with recovery of Amp1 (see Amp1 columns in below table).  We finished Amp1 recovery with ~70.2 W output, so we calibrated the Amp1 power monitor PD to this value (was off by a couple Watts).  We then lowered the light level in the Amp1/Amp2 path (using the High Power Attenuator (HPA) after Amp1) and checked alignment, all looked good.  We increased the Amp2 seed with the HPA to ~1.8 W and checked the unpumped output from Amp2.  This measured at ~1.5 W, which is ~83% throughput and above our 65% threshold, so we proceeded with recovery of Amp2.  This also went very well, see the Amp2 column in the below table; we had ~64.0 W output from Amp2 with an ~1.8 W initial seed power (the power was bouncing between 63.9 W and 64.0 W).  With Amp2 fully powered we then used the HPA to increase the Amp2 seed to max, which resulted in ~140.2 W output from Amp2.

Current (A) Amp1 Output Power (W) Amp2 Output Power (W)
Initial Pout Final Pout Initial Pout Final Pout
1 1.25 1.25 1.6 1.6
2 1.46 2.37 3.0 3.0
3 6.11 8.43 9.1 9.3
4 16.6 18.1 18.2 18.4
5 28.6 28.6 28.1 28.4
6 39.6 39.6 38.0 38.2
7 50.3 50.4 47.4 47.5
8 60.7 60.7 55.8 56.8
9 70.2 70.2 63.7 64.0

Stabilization System Recovery

PMC:  After lunch we began recovering the PSL stabilization systems in order: PMC, ISS, FSS.  We began by using the HPA after Amp2 to lower the power to ~100 mW to check our beam alignment up to the PMC.  All looked good here so we increased the power to max and measured the power incident on the PMC at ~129.4 W.  We then toggled the PMC autolock to ON and it locked without issue.  We needed to use the picomotor-equipped mirrors (M11 and M12 on the layout) to tweak the beam alignment into the PMC, but were only able to get ~102.0 W in transmission with ~27.0 W in reflection.  This is 9 W more than we had after our last NPRO swap, indicating that we really need to take a look at PMC mode matching; since we still had more than enough power to deliver to the IFO we decided to defer the mode matching work to a later Tuesday and continue with PSL recovery.  The PMC Trans and Refl monitor PDs were calibrated to the newly measured values; they were pretty close to begin with, but were still 1-2 W different than our power meter was measuring.  We then returned the amplifer pump diode currents to their previous operating values (9.0 A and 8.8 A for Amp1, 9.1 A and 9.1 A for Amp2), which lowered Amp1 output power from ~70 W to ~68 W and Amp2 output power from ~140 W to ~139 W; this also changed PMC Refl to ~24 W and PMC Trans to ~104 W, indicating our beam is better matched to our current mode matching solution at these pump diode currents.

ISS:  Moving on to the ISS, we first measured the amount of power in our 1st order diffracted beam (the "power bank" for the ISS).  With the loop off and the AOM diffracting a default of 4% we expect ~5.7 W in this beam, and this is what we measured.  AOM alignment was good, so moved on to the ISS PDs in the ISS box.  A voltmeter get plugged into the DC Out ports on the ISS box and a HWP inside the box is adjusted until PD voltages read ~10.0 V.  We did this, but noticed the DC voltage reading on the ISS MEDM screen was much higher, ~12.5 V for PDA and ~13 V for PDB.  We tried to lock the loop and, as expected with PD voltages that high, the loop thought it needed to removed more power from the beam and ran the diffracted power up really high.  We immediately unlocked the ISS and began looking into what could be the problem, as the MEDM reading on the ISS PDs generally matches the voltmeter reading (I say "generally matches" because, for reasons unknown to me, the ISS does not use the DC out from its PDs, it uses a Filter out and "derives" the DC and AC PD voltages from that).  The PDs appeared to be working correctly, and we found no large dark voltages that would indicate a PD failure/malfunction.  When we unplugged the Filter output the PD reading in MEDM began to slowly climb, but when we blocked the light onto the PDs the MEDM reading went to zero.  Looking back at trends we saw the PDs behaving as expected before this most recent NPRO swap, only reading these higher values in MEDM with the relock of the PMC an hour or so prior.  I had never seen this behavior in the past, so wasn't quite sure where the problem could be.  Thinking maybe something had gone wrong in either the ISS inner loop servo box or maybe something in the CER, we called Fil and asked if he could take a look at the CER electronics for the ISS while we moved on to FSS recovery.  It was at this point we found the problem.  When the FSS MEDM screen was opened the first thing we saw was one NPRO noise eater (NE) light green, and the other red.  The green light was our NE enable monitor, indicating that the NE toggle was switched ON in the PSL software; the red light was our NE monitor, which reads the Check output from our NPRO monitor PD that indicates whether or not the NPRO's relaxation oscillation was being supressed.  So we had the NE toggled ON but it was clearly not working, so we toggled it off and on again.  The NE monitor went green and the channel monitoring the relaxation oscillation indicated it was working properly, and the ISS PD values on the ISS MEDM screen now read the correct values.  So I learned that we have another measure of if the NE is working or not, the ISS PD readings on the MEDM screen go higher.  Trending back, the NE stopped working at ~16:58 PST on Thursday, right before Ryan and I left the enclosure for the day.  We'll keep an eye on this, as right now it's not clear why the NE turned off.  At this point everything looked good for the ISS so we moved on to the FSS.

FSS:  For the FSS, we first tried to see if the RefCav would lock with the autolocker; it would not.  We had to manually tune the NPRO temperature to find a RefCav resonance, one was found with a slider value of ~ +0.06.  The temperature search ranges were adjsuted to this new value and we tried the autolocker again.  While we could see clear flashes the autolocker would not grab lock for some reason.  The FSS guardian was paused so it would stop yanking the gains around upon lock acquisition, but this did not help, the autolocker refused to hold lock for some reason.  So I did it manually (from the FSS manual screen, manually change NPRO temperature until a resonance flashed through, then really quickly move the mouse up to turn the loop on; if the loop grabs go back to the FSS MEDM screen and turn on the Temperature loop, if not then turn the loop off and try again), which worked.  With a locked RefCav we measured a RefCav TPD voltage of ~ 0.84 V.  The RefCav Refl spot looked pretty centered so we did not do any alignment tuning.  This completed our work in the enclosure so we cleaned up, turned the computers and monitors off, left the enclosure, and put it into Science mode.  Outside, we scaned the NPRO for mode hop regions and measured TFs of the stabilization loops.

NPRO Temperature Scan

Now outside the enclosure we set up to scan the NPRO temperatures to check for mode hopping.  We took the HV Monitor output from the PMC fieldbox to trigger an oscillscope on the PZT ramp and used the PMC Trans PD to monitor the peaks.  We set the PMC's alignment ramp to +/- 7.0 V and a 1 Hz scan rate, and monitored the peaks as we tuned the NPRO crystal temperature.  We used the slider on the FSS Manual MEDM screen, which gives us a total range of approximately +/- 0.8 °C (0.01 on the slider changes the NPRO crystal temperature by roughly 0.01 °C and the slider goes from -0.8 to +0.8).  Since we were close to zero on slider, sitting at ~ +0.07, we started by moving lower (which reduces the NPRO crystal temperature); our starting crystal temperature, as read at the NPRO power supply front panel, was 24.22 °C.  We got all the way to the negative end of the slider, which gave a crystal temperature of 23.38 °C, and did not see any evidence of mode hopping on the way down.  Heading back up we finally started to see early evidence of mode hopping near the top end of the slider; we could clearly see a new forest of peaks show up in the PMC PZT scan and one of them started to grow noticebly as the temperature was further increased.  This mode hop region began at a crystal temperature of 24.76 °C, and the slider maxed out at 24.91 °C.  At this point we still had not fully transitioned through the mode hop region, but we did have a peak starting to grow very large indicating that we were almost there.  Since we saw no evidence of mode hopping by making the temperature colder, we went back to our starting place of 24.22 °C and then reduced the temperature further to the next RefCav resonance below that; this resulted in a crystal temperature of 23.96 °C at a slider value around -0.17.  Again I had to lock the RefCav manually, as the autolocker did not want to grab and hold lock.  With all of the stabilization systems locked we moved on to TF measurements.

Transfer Functions and Gains

We started with the PMC.  With the current settings we have a UGF of ~1.6 kHz and 60° of phase margin, see first attachment.  Everything looked good so we left the PMC alone.

For the ISS, we have a UGF of ~45 kHz and a phase margin of 37.5°, see second attachment.  Again, everything look normal here so we left the ISS alone.

For the FSS, we started with a Common gain of 15 dB.  Everything looked OK, but since we had seen some potential zero crossings that like to hide in the longer range scans we did a "zoomed in" scan from 100 kHz to 1 MHz.  Sure enough, there were a couple peaks in the 500 kHz to 600 kHz range that were pretty close to a zero crossing.  We lowered the Common gain to 14 dB to move them away from the potential crossing; the third attachment shows this zoomed in area with the Common gain at 14 dB, and the peaks in question are clearly visible.  With this Common gain we have a UGF of ~378 kHz with ~60° of phase margin, see fourth attachment; we took this TF out to 10MHz to check for any weirdness at higher frequency and did not see anything immediately concerning.  To finish we took a look at the PZT/EOM crossover (around 20 kHz) to set the Fast gain.  The final attachment shows this measurement (a spectrum of IN1) at a Fast gain of 5 dB; this looks OK so we left the Fast gain as is.

At this point the NPRO swap was complete, the PSL was fully recovered, and we handed things over to the commissioning team for IFO recovery.  We still need to look at PMC mode matching, and will do so during future Tuesday maintenance periods.  This closes WP 12210.

Images attached to this comment
H1 PEM (DetChar, PEM, TCS)
robert.schofield@LIGO.ORG - posted 18:06, Thursday 14 November 2024 - last comment - 10:19, Thursday 19 December 2024(81246)
TCS-Y chiller is likely hurting Crab sensitivity

Ansel reported that a peak in DARM that interfered with the sensitivity of the Crab pulsar followed a similar time frequency path as a peak in the beam splitter microphone signal. I found that this was also the case on a shorter time scale and took advantage of the long down times last weekend to use  a movable microphone to find the source of the peak. Microphone signals don’t usually show coherence with DARM even when they are causing noise, probably because the coherence length of the sound is smaller than the spacing between the coupling sites and the microphones, hence the importance of precise time-frequency paths.

Figure 1 shows DARM and the problematic peak in microphone signals. The second page of Figure 1 shows the portable microphone signal at a location by the staging building and a location near the TCS chillers. I used accelerometers to confirm the microphone identification of the TCS chillers, and to distinguish between the two chillers (Figure 2).

I was surprised that the acoustic signal was so strong that I could see it at the staging building - when I found the signal outside, I assumed it was coming from some external HVAC component and spent quite a bit of time searching outside. I think that this may be because the suspended mezzanine (see photos on second page of Figure 2) acts as a sort of soundboard, helping couple the chiller vibrations to the air. 

Any direct vibrational coupling can be solved by vibrationally isolating the chillers. This may even help with acoustic coupling if the soundboard theory is correct. We might try this first. However, the safest solution is to either try to change the load to move the peaks to a different frequency, or put the chillers on vibration isolation in the hallway of the cinder-block HVAC housing so that the stiff room blocks the low-frequency sound. 

Reducing the coupling is another mitigation route. Vibrational coupling has apparently increased, so I think we should check jitter coupling at the DCPDs in case recent damage has made them more sensitive to beam spot position.

For next generation detectors, it might be a good idea to make the mechanical room of cinder blocks or equivalent to reduce acoustic coupling of the low frequency sources.

Non-image files attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 14:12, Monday 25 November 2024 (81472)DetChar, TCS

This afternoon TJ and I placed pieces of damping and elastic foam under the wheels of both CO2X and CO2Y TCS chillers. We placed thicker foam under CO2Y but this did make the chiller wobbly so we placed thinner foam under CO2X.

Images attached to this comment
keith.riles@LIGO.ORG - 08:10, Thursday 28 November 2024 (81525)DetChar
Unfortunately, I'm not seeing any improvement of the Crab contamination in the strain spectra this week, following the foam insertion.

Attached are ASD zoom-ins (daily and cumulative) from Nov 24, 25, 26 and 27.
Images attached to this comment
camilla.compton@LIGO.ORG - 15:02, Tuesday 03 December 2024 (81598)DetChar, TCS

This morning at 17:00UTC we turned the CO2X and CO2Y TCS chiller off and then on again, hoping this might change the frequency they are injecting into DARM. We do not expect it to effect it much we had the chillers off for a ling period 25th October 80882 when we flushed the chiller line and the issue was seen before this date.

Opened FRS 32812.

There were no expilcit changes to the TCS chillers bettween O4a and O4b although we swapped a chiller for a spare chiller in October 2023 73704

camilla.compton@LIGO.ORG - 11:27, Thursday 05 December 2024 (81634)TCS

Between 19:11 and 19:21 UTC, Robert and I swapped the foam from under CO2Y chiller (it was flattened and not providing any damping now) to new, thicker foam and 4 layers of rubber. Photo's attached. 

Images attached to this comment
keith.riles@LIGO.ORG - 06:04, Saturday 07 December 2024 (81663)
Thanks for the interventions, but I'm still not seeing improvement in the Crab region. Attached are daily snapshots from UTC Monday to Friday (Dec 2-6).
Images attached to this comment
thomas.shaffer@LIGO.ORG - 15:53, Tuesday 10 December 2024 (81745)TCS

I changed the flow of the TCSY chiller from 4.0gpm to 3.7gpm.

These Thermoflex1400 chillers have their flow rate adjusted by opening or closing a 3 way valve at the back of the chiller. for both X and Y chillers, these have been in the full open position, with the lever pointed straight up. The Y chiller has been running with 4.0gpm, so our only change was a lower flow rate. The X chiller has been at 3.7gpm already, and the manual states that these chillers shouldn't be ran below 3.8gpm. Though this was a small note in the manual and could be easily missed. Since the flow couldn't be increased via the 3 way valve on back, I didn't want to lower it further and left it as is.

Two questions came from this:

  1. Why are we running so close to the 3.8gpm minimum?
  2. Why is the flow rate for the X chiller so low?

The flow rate has been consistent for the last year+, so I don't suspect that the pumps are getting worn out. As far back as I can trend they have been around 4.0 and 3.7, with some brief periods above or below.

Images attached to this comment
keith.riles@LIGO.ORG - 07:52, Friday 13 December 2024 (81806)
Thanks for the latest intervention. It does appear to have shifted the frequency up just enough to clear the Crab band. Can it be nudged any farther, to reduce spectral leakage into the Crab? 

Attached are sample spectra from before the intervention (Dec 7 and 10) and afterward (Dec 11 and 12). Spectra from Dec 8-9 are too noisy to be helpful here.



Images attached to this comment
camilla.compton@LIGO.ORG - 11:34, Tuesday 17 December 2024 (81866)TCS

TJ touched the CO2 flow on Dec 12th around 19:45UTC 81791 so the flowrate further reduced to 3.55 GPM. Plot attached.

Images attached to this comment
thomas.shaffer@LIGO.ORG - 14:16, Tuesday 17 December 2024 (81875)

The flow of the TCSY chiller was further reduced to 3.3gpm. This should push the chiller peak lower in frequency and further away from the crab nebula.

keith.riles@LIGO.ORG - 10:19, Thursday 19 December 2024 (81902)
The further reduced flow rate seems to have given the Crab band more isolation from nearby peaks, although I'm not sure I understand the improvement in detail. Attached is a spectrum from yesterday's data in the usual form. Since the zoomed-in plots suggest (unexpectedly) that lowering flow rate moves an offending peak up in frequency, I tried broadening the band and looking at data from December 7 (before 1st flow reduction), December 16 (before most recent flow reduction) and December 18 (after most recent flow reduction). If I look at one of the accelerometer channels Robert highlighted, I do see a large peak indeed move to lower frequencies, as expected.

Attachments:
1) Usual daily h(t) spectral zoom near Crab band - December 18
2) Zoom-out for December 7, 16 and 18 overlain
3) Zoom-out for December 7, 16 and 18 overlain but with vertical offsets
4) Accelerometer spectrum for December 7 (sample starting at 18:00 UTC)
5) Accelerometer spectrum for December 16
6) Accelerometer spectrum for December 18 
Images attached to this comment
Displaying reports 3981-4000 of 83106.Go to page Start 196 197 198 199 200 201 202 203 204 End