Displaying reports 921-940 of 83227.Go to page Start 43 44 45 46 47 48 49 50 51 End
Reports until 10:06, Tuesday 03 June 2025
H1 AOS (SUS)
caroline.capuano@LIGO.ORG - posted 10:06, Tuesday 03 June 2025 (84743)
Plotting Displacement of Quadruple Pendulum Stages with Anti-Whitening Filters
Hello!

I have been working on eventually calculating how much force is being applied to three stages of the quadruple pendulum. The channels I am currently plotting in the figures attached are the DARM control signal (H1:CAL-CFTD_DELTAL_CTRL_DBL_DQ), the penultimate mass control signal (H1:CAL-CFTD_DELTAL_CTRL_PUM_DBL_DQ), the upper intermediate mass control signal (H1:CAL-CFTD_DELTAL_CTRL_UIM_DBL_DQ), the top test mass control signal (H1:CAL-CFTD_DELTAL_CTRL_TST_DBL_DQ), the external excitation signal (H1:CAL-CFTD_DELTAL_EXTERNAL_DQ) and Pcal y (H1:CAL-PCALY_RX_PD_OUT_DQ) - I should include Pcal X next time. By plotting these channels I can map out how much each stage of the quadruple pendulum is moving (or being actuated upon), the Pcal injections, and eventually compare the force needed to control each stage to keep our interferometer locked.

Right now I am plotting the meters per root Hz for each channel. I am also applying an anti-whitening filter so that I can convert the signals from counts back into the physical displacements. 

The path to the file to plot these figures is: /ligo/home/caroline.capuano/Force_on_ETMX_for_each_stage/phase_and_mag_of_h.py

All you need to do is run "python phase_and_mag_of_h.py" and it should produce both plots.

Currently I am taking data from LIGO Hanford at the GPS start time of 1425831025 for a duration of 1000 seconds.

There is a weird bump around 100 Hz for the external excitation signal, so Craig suggested I find another time of when we were locked and compare to see if the hump is still present.

To do next:
- figure out what filters to divide by so that I can calculate the force being applied to the three stages aka N/rtHz.
- maybe try quick_psd instead of welch's method and see if that makes a significant difference
Images attached to this report
H1 General (CDS, DetChar, ISC, OpsInfo)
thomas.shaffer@LIGO.ORG - posted 09:04, Tuesday 03 June 2025 (84741)
Changed the index number for Adjust_Power and Darm_Offset states

Two index number changes this morning:

  1. Adjust_Power was 1000, we have changed this to 521. This now fits it in linearly in the state graph and doesn't mess with other scripts, checks, and things that check for low noise conditions above 600.
  2. Darm_Offset was brought back to 427 from 432. A few days ago (alog84703) it was changed with the thought that the move would bring the state back into order, but we plan to move the state back to it's old place between DRMI_TO_POP and ENGAGE_RF_VIOLINS when we can. Sorry for the confusion.
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 07:36, Tuesday 03 June 2025 (84740)
OPS Day Shift Start

TITLE: 06/03 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.27 μm/s
QUICK SUMMARY:

IFO is in DOWN for PLANNED ENGINEERING

Today is a light maintenance day in with the plan being to continue locking H1 to NLN.

The highest state we are able to get to is: LOWNOISE_LENGTH_CONTROL.

H1 CDS
erik.vonreis@LIGO.ORG - posted 06:40, Tuesday 03 June 2025 - last comment - 07:29, Tuesday 03 June 2025(84738)
Workstations updated

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

Comments related to this report
david.barker@LIGO.ORG - 07:29, Tuesday 03 June 2025 (84739)

After opslogin0 was rebooted I started the two temporary EPICS IOCs to green up the EDC and restore the HAM1 gauge signal

digivideo_dummy_ioc: 1 windows (created Tue Jun  3 06:53:08 2025)
vac_ham1_pressure_converter_ioc: 1 windows (created Tue Jun  3 06:54:12 2025)
 

H1 General (OpsInfo, SUS)
oli.patane@LIGO.ORG - posted 21:32, Monday 02 June 2025 (84737)
Ops Eve Shift End

TITLE: 06/03 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Just had another lockloss so I'm just putting the detector in IDLE for the night. I have a list of things from Elenna to check/try with relocking, but I won't be able to get to any of them before the end of my shift, so they can be checked tomorrow morning. This last lockloss was during OFFLOAD_DRMI_ASC while I was trying to adjust SRM, although I don't think I caused the lockloss? It took a while for DRMI to catch this time, so maybe running an initial alignment is warranted. The highest state we were able to get to today was LOWNOISE_LENGTH_CONTROL.

The list Elenna gave me is:

LOG:

23:00UTC Commissioning and sitting in POWER_10W
23:20 Started trying to increase power
01:49 Lockloss from LOWNOISE_LENGTH_CONTROL while sitting there running measurements
    - Started a manual initial alignment
        - Stopped at PRX_LOCKED, touched up PRM, then finished IA
    - Stopped at OFFLOAD_DRMI_ASC, touched up SRM, then continued
    - Lockloss in DRMI_TO_POP
        - Probably due to DRMI alignment not being the greatest
    - Stopped at OFFLOAD_DRMI_ASC, touched up SRM, SR2, and PRM, then continued
    - Lockloss in LOWNOISE_ESD_ETMX due to a CHARD P ringup that started in TRANSITION_FROM_ETMX
    - Lockloss from OFFLOAD_DRMI_ASC while I was trying to touch up alignment using SRM. Not sure if my fault?

H1 ISC
elenna.capote@LIGO.ORG - posted 19:46, Monday 02 June 2025 - last comment - 20:48, Monday 02 June 2025(84731)
Overall Summary of Afternoon/Early Evening locking progress

Writing this alog on behalf of most of the control room...

After we redid the input matrix for CHARD and INP1 10W, we checked the PRC2 and INP1 bandwidth. We were also concerned about the overall gain of CHARD P and Y since they seemed to be way too low

We decided to power up anyway, and saw that the pitch ADS was able to run fine, now that the CHARD pitch gain was nominal. However, yaw ADS still had problems during move spots.

Everything looked good, so I took us up in power from 25W to 60W, stopping frequently to check for instabilities. We made it, but again the ADS was unstable, so Georgia used the Camera servo guardian to move off the ADS to camera servos, and everything was fine.

I stepped through lownoise ASC by hand, skipping the lownoise steps of CHARD P and Y since those gains were not nominal.

Lots of the of the usual wobbly stuff in the ASC and buildups at high power, but the overall alignment and control looks good: PRG is still around 50 at full power.

We then ran through lownoise coil drivers and the ETMX ESD transition. We had one guardian error at the end of TRANSITION FROM ETMX due to divide by zero error since the convergence checker looks for something that is like [ADS error signal / ADS CLKGAIN] and the ADS CLKGAINs were zero. Georgia and I fooled the guardian by setting the CLKGAINs to 1 momentarily, and then undoing them once the state completed.

We ran all the way through LOWNOISE LENGTH CONTROL, although the LSC feedforward is no longer well-tuned, so I turned it off momentarily so we could check OLGs.

The LSC feedforward is currently so bad that we should go from-scratch when we retune it instead of the iterative method.

We had a fast unknown lockloss while sitting in this state- no one was doing anything and we don't see an obvious cause.

We think we have properly SDFed and guardianized all changes from today.

My only worry: we were not able to raise the CHARD Y gain until we reached maximum power, but obviously we are having ADS stability issues since this gain is too low. Currently I have set the guardian to have what I think is the "correct" CHARD Y gain (300 once all loops are closed), but if it's too high, drop it back to 3.

Recommended to do list:

Comments related to this report
elenna.capote@LIGO.ORG - 20:18, Monday 02 June 2025 (84732)

Oli and I are trying out relocking, and both sitting at 2W and sitting at 25 W (before move spots), I cannot raise the CHARD Y gain beyond 3 without causing some slow growing ~0.8 Hz oscillation in CHARD Y. We will try full power up again with low CHARD Y gain. Turns out the CHARD Y gain was not actually set to 300 at 2W (I only updated lscparams, not ISC_LOCK).

After MOVE SPOTS and reducing modulation depths (but before the rest of the power up), I tried again to raise the CHARD Y gain- same problems.

But once MAX POWER gets us to 60W, I can raise the gain no problem!

I edited MAX POWER to change the CHARD Y gain right at the end of the state (I think).

elenna.capote@LIGO.ORG - 20:30, Monday 02 June 2025 (84734)

In terms of setting the time on the ASC convergence in MOVE SPOTS, YAW3 (ITMX spot feedback to PRM) is the culprit that is taking forever.

Oli just took a look back- we usually spend about 5 minutes in move spots, and tonight it is taking more than 10 minutes.

elenna.capote@LIGO.ORG - 20:44, Monday 02 June 2025 (84735)

We were able to run through LOWNOISE ASC guardian state fine, so the edits described above work!

elenna.capote@LIGO.ORG - 20:48, Monday 02 June 2025 (84736)

We lost lock from a 1 Hz DHARD P ring up that began during the "TRANSITION FROM ETMX" state.

When we went through this state previously and successfully, we were running camera servos instead of ADS. I wonder if that's related to this lockloss.

H1 ISC
matthewrichard.todd@LIGO.ORG - posted 18:56, Monday 02 June 2025 - last comment - 18:59, Monday 02 June 2025(84729)
LSC MICH1 OLG Measurement

M. Todd, E. Capote, C. Cahillane


We ran an OLG measurement for LSC-MICH1 loop, once we were in LOWNOISE_LENGTH_CONTROL.

At first we saw that the guardian had not turned off some strange notch filters we did not expect to see.

Craig spotted these as BounceRoll filters, which we turned off and reran the measurement.

Soon after the measurement was done, we lost lock so we are wondering if these notches were responsible or if we need to watch out in other LSC loops.

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 18:59, Monday 02 June 2025 (84730)

Here is a measurement of SRCL as well. Everything looks good. We lost lock before we could measure PRCL.

So far indications are that the BR notches had nothing to do with the lockloss, so we can probably keep them off if we want.

Images attached to this comment
H1 PSL (ISC, PSL)
craig.cahillane@LIGO.ORG - posted 18:39, Monday 02 June 2025 (84728)
ISS array in need of pointing fix
Now that we're at 60 W of input power, I double checked the ISS secondloop array pointing after the vent.
We're missing slightly, seemingly pitched off the ISS QPD.

The ndscope has Y1 dashed white lines at where the ISS PD values are now.
The ISS secondloop PD values from March 12 are the actual traces.

We're still locking, and so I leave ISS picoing undone for now.  
We'll have to leave the ISS secondloop open and pico back onto the array at some point. 

Based on the attached PSD, this could be responsible for our huge peak at 29 Hz in DARM. 
Non-image files attached to this report
LHO General
corey.gray@LIGO.ORG - posted 16:31, Monday 02 June 2025 (84709)
Mon DAY Ops Summary

TITLE: 06/02 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Much of today was work in ASC land with H1 locked most of the day at 10W (but started powering up at the end of the shift) and also had the arrival of even more members of the Syracuse LSC Team!  But there was also work on the Squeezer toward the end of the day.  The plan for tomorrow's Maintenance Day is to continue with Vent Recovery locking work.

Rahul addressed rung up violin modes from this morning and he requested the Oli (EVE operator) to apply these settings new settings (noted in alog 84720).

The day started out with the drama of a fire out beyond End-Y (Fire Dept phoned the Control Room notifying us that they were fighting a fire on SR240 (see attached photo from the roof of the Corner Station).
LOG:

Images attached to this report
H1 ISC
camilla.compton@LIGO.ORG - posted 16:23, Monday 02 June 2025 (84711)
Notes on Today's Relocking so far

Control Room (Corey, Sheila, Elenna, Oli, Georgia, Craig, Julia, Matt, Keita, Ryan S, Camilla

Notes of what's been done so far today, we've spent the majority of the day locked at POWER_10W, adjusting the ASC sensing matrix and gains:

Images attached to this report
H1 ISC
georgia.mansell@LIGO.ORG - posted 15:42, Monday 02 June 2025 - last comment - 16:18, Monday 02 June 2025(84724)
INP1, CHARD, PRC2 offset tests for input matrix design at 10 W

Julia, Georgia, Sheila, Camilla, Elenna

This might be out of date already as some ASC input matrices have already been updated.

On Sunday we had some locklosses as we powered up from a 0.02Hz oscillation. One known issue is we have taken out some gain out of our CHARD loops. We wanted to check our sensing (input) matrices CHARD, INP1 (which both use the refl wfs) and PRC2 (which uses new in vac pop_x).

We sat at 10W, with the input matrix Sheila found last week:

DOF REFL_A_RF9_I REFL_A_RF45_I REFL_B_RF9_I REFL_B_RF45_I POP_X_I
INP1_P 1   1    
CHARD_P   -1   -0.5  
PRC2_P         -1
INP1_Y 1   1    
CHARD_Y   -1   1  
PRC2_Y         -1

While Elenna measured the phasing using an 8 Hz line, Julia and I added offsets into the loops and looked at the responses in the different sensors.

Some of this is a bit different to what Sheila saw last week, but our ifo alignment has changed. We want to find intrixes that are sensitive to each DOF and ideally are insensitive to the other DOFs.

While writing this another input matrix for INP and CHARD has been put in - https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=84711 - and seems to be working so stay tuned.

We plan to work on our gain heirarchy and hopefully power up further soon!

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 16:18, Monday 02 June 2025 (84726)

These are my radar plots for my 8 Hz dither sensing matrix.

Non-image files attached to this comment
H1 SUS (SUS)
rahul.kumar@LIGO.ORG - posted 13:38, Monday 02 June 2025 - last comment - 20:21, Monday 02 June 2025(84720)
Violin damping settings which worked for 2W and 10W input power

This morning while Corey and the commissioning team were trying to lock and power up the interferometer, the violin modes were pretty rung up. For most of the modes, I was able to damp them down using nominal settings except three of them which are listed below along with the settings which seems to be working for now. 

Comments related to this report
oli.patane@LIGO.ORG - 20:21, Monday 02 June 2025 (84733)

Made those changes for 2W damping, and will hopefully be able to confirm whether they also work for 60W. For ITMX 03 and ITMY 05, I added new 2W settings for IX3 and IY5. These changes were saved in lsc_params and the violin damping guardian has been reloaded.

H1 TCS (ISC)
camilla.compton@LIGO.ORG - posted 10:48, Monday 02 June 2025 - last comment - 16:57, Monday 02 June 2025(84716)
No new Point Absorbsers since the Vent

TJ, Camilla, Checking as Sheila was concerned about this as Georgia/Craig need to move the ITMX SPOT GAIN "CENTER" 84702.

Attached are the HWS Live plots comparing when we get to 10W and 120s later for ITMX and ITMY now. And also for ITMX and ITMY at our last 10W power up before the vent (note that then we don't pause at 10W and continue increasing power during the 120s). 

Can see no obvious new point absorbers, ITMY looks perfect and ITMX has the same point absorbers as before, it;s possible there's a new point absorber on the right of the optics (orange arrow in attached) but it doesn't look scary. We will continue to check this but it's possible that our alignment has just changed (has since 66198) so that we can now see this point.

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 16:57, Monday 02 June 2025 (84727)ISC

Sheila and Elenna turned the CO2s on as we were powering up from 10W to 25W. Attached is the 2 minutes after CO2s were turned on while we were sat at 15W for 4 minutes.

Can see the CO2 patterns of ITMX and ITMY.   IY CO2 looks good but IX CO2 it looks off in YAW, we should check how this compares to the IFO spot at full power. It would be worth doing some dither tests to see if this needs adjusting.

Images attached to this comment
H1 DetChar (DetChar)
craig.cahillane@LIGO.ORG - posted 14:35, Sunday 01 June 2025 - last comment - 09:05, Tuesday 03 June 2025(84703)
DARM_OFFSET state number changed from 427 to 432
Changed the DARM_OFFSET ISC_LOCK state number to be in order, after ENGAGE_ASC_FOR_FULL_IFO
Comments related to this report
thomas.shaffer@LIGO.ORG - 09:05, Tuesday 03 June 2025 (84742)

This change was reverted - alog84741

Displaying reports 921-940 of 83227.Go to page Start 43 44 45 46 47 48 49 50 51 End