Displaying reports 1601-1620 of 77270.Go to page Start 77 78 79 80 81 82 83 84 85 End
Reports until 09:52, Monday 20 May 2024
H1 SQZ
sheila.dwyer@LIGO.ORG - posted 09:52, Monday 20 May 2024 (77942)
FC2 spot centering

I've moved the offsets on the FS green QPD A to improve the spot centering on FC2, following 69276 and 73777.  The centering is better, as shown by the attached screenshot. This hasn't had much of an impact on the green build up in the filter cavity, and seems to have redcued the IR build up.   This didn't have much of an impact on the couple of months of downward trend on the FC build ups.

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 09:03, Monday 20 May 2024 - last comment - 11:47, Monday 20 May 2024(77940)
OPS Monday day shift update

We started comissioning at 16:00 UTC and will continue till 19:00 UTC, starting with some SQZ optimization.

Comments related to this report
ryan.crouch@LIGO.ORG - 11:47, Monday 20 May 2024 (77947)Lockloss

Lockloss at 18:45UTC during commissioning, likely from commissioning work, we were in PR2_SPOT_MOVE

H1 General
ryan.crouch@LIGO.ORG - posted 07:35, Monday 20 May 2024 (77939)
OPS Monday day shift start

TITLE: 05/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

H1 SQZ
oli.patane@LIGO.ORG - posted 07:17, Monday 20 May 2024 (77938)
SQZ OWL Intervention

I had to pop on to help the ifo because we had been taken out of Observing due to the SQZ OPO lockloss limit counter having reached its max. I followed 73053, skipping over the adjustment of the OPO temp, and the filter cavity eventually locked and we were able to get back into Observing.

H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 01:15, Monday 20 May 2024 (77937)
Sunday Ops Eve Shift End

TITLE: 05/20 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Unknown lockloss @ 5:50 UTC
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400219473

Relocking: happened automagically, and H1 was back to OBSERVING at 6:49 UTC
Survived a few more quakes tonight including a 5.1M

I have not seen any more deviations in the ISI HAM 3 BLRMS since the I power cycled them so hopefully they last until tomorrow morning.

H1 is now currently locked for 1 hour and a half.
 

LOG:
Tony went to the CER to reboot ISI interface Chassis around 3 UTC for 5 minutes.

Images attached to this report
H1 General (Lockloss, SEI)
anthony.sanchez@LIGO.ORG - posted 22:16, Sunday 19 May 2024 (77935)
Double lockloss & mid Eve shift update

TITLE: 05/20 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 14mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Unkown Lockloss
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400201888
I did go back to check if this lockloss was caused by the smaller ISI glitches that jim and I saw that did not trip the watchdog. This is not the case for this Lockloss It is still of unknown origin.


Relocking:
I had to slightly touch up the Beam Splitter and PRM  both in pitch to get DRMI locked but other than that it went well.
We are still saturating SUS in Power 10 & 25 Watts and in Move Spots.


HAM3 ISI tripped watchdog Lockloss
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400207843
Contacted Jim, took IMC_LOCK to Offline and went to the CER to power cycle the HAM3 ISI Chassis found in rack SEI-C2  - rack slots 30 & 31 . Once the ISI interface chassies came back on, Jim gave me a green light to start locking again.
He noted that there are some ndscopes I can use to watch for more glitches, which are identified by spikes above 20:
ndscope H1:ISI-HAM3_CPSINF_H{1,2,3}_BLRMS_65_100 H1:ISI-HAM3_CPSINF_V{1,2,3}_BLRMS_65_100  H1:ISI-HAM3_CPSINF_H{1,2,3}_BLRMS_130_200


Relocking 2:
I clicked on Nominal_Low_Noise and It went to it with out much fuss at all.

Observing reached at 4:13 UTC
Dropped to commissioning for some SQZ Scans to increase the range.

 PI 31 has been ringing up a fair amount this lock but every time it's been solved by the PI system.

Currentlt H1 has been locked and in Observing for over 1 hour.

 

Images attached to this report
H1 General
anthony.sanchez@LIGO.ORG - posted 16:44, Sunday 19 May 2024 - last comment - 17:58, Sunday 19 May 2024(77932)
Sunday Ops Eve Shift Start

TITLE: 05/19 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 4mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

IFO is now at Laser Noise Suppression and going up! Ryan was able to get H1 the IFO past PRMI.
If we lose lock and get back into PRMI, 2 OLG measurements to take :
/opt/rtcds/userapps/release/lsc/h1/templates/PRCL/PRCL/PRCL_OLG_PRMI.xml
&
/opt/rtcds/userapps/release/lsc/h1/templates/MICH/MICH/MICH_OLG_PRMI.xml

and for DRMI :
/opt/rtcds/userapps/release/lsc/h1/templates/PRCL/PRCL/PRCL_OLG_DRMI.xml
&
/opt/rtcds/userapps/release/lsc/h1/templates/MICH/MICH/MICH_OLG_DRMI.xml

Hopefully we wont have to relock at all.

Ryans Changed made to the Gains in lcsparams.py  and Timers in ISC_DRMI.py have Not been Reverted.
 

SDF diff that had to be accepted to get into OBSERVING:
H1:SYS-MOTION_C_PICO_A_CURRENT_ENABLE

Images attached to this report
Comments related to this report
anthony.sanchez@LIGO.ORG - 17:21, Sunday 19 May 2024 (77933)

This SDF Diff was reverted: H1:SYS-MOTION_C_PICO_A_CURRENT_ENABLE

I will be watching H1:LSC-POP_A_LF_NORM_MON to see if we thermalize a little closer to what we saw a week about 10 days ago , note the Y cursur at 515.119 counts.

H1:LSC-POP_A_LF_NORM_MON as of right now with the same cursur location from 10 days prior.

 

Images attached to this comment
anthony.sanchez@LIGO.ORG - 17:58, Sunday 19 May 2024 (77934)SQZ
Images attached to this comment
H1 General
ryan.crouch@LIGO.ORG - posted 16:34, Sunday 19 May 2024 (77930)
OPS Sunday DAY shift summary

TITLE: 05/19 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: More progress than yesterday in terms of the PRMI oscillation as I seem to have solved it for now by adjusting loop gains and ramps and can hold it locked, then I was back to DRMI not being able to lock but after Sheila restored PR3 to a previous spot we were able to lock DRMI no problem. Currently a few minutes away from NLN

15:00 UTC Initial Alignment as there weren't really any flashes on PRMI

After some more fiddling with gains/ramp times and talking to Sheila I was able to stop the PRMI 20ish Hz buzz by reducing PRMI-MICH to 2.2 from 2.8 and increasing PRMI_PRCL to 8 from 6 and set the ramp time sof both to 5 alog77928

20:25 UTC - No matter how much adjusting I did with the sliders (BS, PRM, SRM) I couldn't get AS AIR looking good enough so I thought there must be an alignment issue somewhere after a few mores tries I dropped to do another Initial Alignment, after this I still had DRMI issues.

I further decreased the gain of PRMI-MICH to 2.0 after Sheila looked at my OLG measurement, PRMI locked pretty easily after this. We're not sure why my PRCL OLG measurement looked the way it did alog77929

22:35 UTC Sheila adjusted PR3 to where it used to be, after which I did another Initial Alignment so we could try locking PRMI. I may need to revert my PRMI loop changes? I have not reverted them as of now

After finishing IA we locked DRMI immediately

There were a lot of IFO_OUT saturations during POWER_25W and MOVE_STOPS

H1 AOS
sheila.dwyer@LIGO.ORG - posted 15:52, Sunday 19 May 2024 (77931)
PRMI troubleshooting remotely

After Ryan was able to lock PRMI by adjusting both the MICH and PRCL gains (77926) , he mentioned to me that the build ups didn't look good.  Indeed, POP18 was around 26 counts after PRMI ASC ran, before our PR3 moves this week it would be around 50 counts in PRMI.  I looked back and it hasn't been 50 since I put PR3 back on Friday.  I was able to walk PR2, PRM and BS to improve the build up a little, but decided to move PR3.  We did this at LOCKING_ARM_GREEN, and saw that putting PR3 back according to the slider values (rather than top mass osems), did improve the COMM beatnote from around -10 to around 0dBm. 

Ryan is going to run an initial alignment skipping the green arms, and try to relock PRMI.  Then we will see if this PR3 move solves the low POP18 power, if the PRMI gain changes can be reverted. 

Also note that Ryan posted a PRCL UGF measurement that seems very strange. 

H1 General
ryan.crouch@LIGO.ORG - posted 10:45, Sunday 19 May 2024 - last comment - 12:14, Sunday 19 May 2024(77926)
OPS Sunday day shift update

I spent a bit trying to align everything by hand with ISC_LOCK paused in DRMI, misaligning PRM and SRM to adjust the BS then aligning PRM to adjust it then SRM. Still the same behaviour on PRMI as yesterday even with turning down the MICH and PRCL gains, and despite good flashes on DRMI it wasn't able to lock after my adjustments, I had to move SRM a lot. The wind is also picking up which is not helping ALS.

Images attached to this report
Comments related to this report
ryan.crouch@LIGO.ORG - 11:30, Sunday 19 May 2024 (77927)

I talked with Sheila who had some more suggestions, gain lowering/raising and a template to run if I'm able to get PRMI locked, She's on her way back into town and might be able to help more in an hour or two.

ryan.crouch@LIGO.ORG - 11:52, Sunday 19 May 2024 (77928)

Increasing the ramp times of MICH and PRCL and reducing the gain even more of MICH (2.8 to 2.5) and raising the gain of PRCL (6 to 8) has allowed us to survive longer. After this we keep losing lock at different points in the ISC_DRMI  PRMI code, the furthest I've made it was PRMI_WFS_CENTERING.

ryan.crouch@LIGO.ORG - 12:14, Sunday 19 May 2024 (77929)

I was able to lock PRMI finally and go through ASC by increasing the ramp times of both MICH and PRCL from 2 to 5, further decreasing the gain of MICH from 2.5 to 2.2 with als and 2.8 to 2.6 without arms and with PRCLs als gain being raised from 6 to 8. DRMI still wasn't able to catch after 1 round of PRMI, I'm holding in PRMI_ASC to take a quick OLG measurement of PRCL and MICH.

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 10:31, Sunday 19 May 2024 (77925)
Sun CP1 Fill

Sun May 19 10:09:59 2024 INFO: Fill completed in 9min 56secs

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 07:38, Sunday 19 May 2024 - last comment - 08:22, Sunday 19 May 2024(77921)
OPS Sunday day shift start

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

Comments related to this report
ryan.crouch@LIGO.ORG - 07:57, Sunday 19 May 2024 (77923)

I'm not getting any flashes on DRMI or even PRMI so I'm going to do an initial alignment

ryan.crouch@LIGO.ORG - 08:22, Sunday 19 May 2024 (77924)

I have reached out to everyone (Jenne and Sheila) on the call list that are not on travel or otherwise listed as unavailable, Jenne is helping over text.

H1 General
oli.patane@LIGO.ORG - posted 04:16, Sunday 19 May 2024 - last comment - 07:43, Sunday 19 May 2024(77919)
Ops OWL Assistance Status

Tony and I have been troubleshooting the relocking issues since 08:00UTC, and have had no luck. We have been stuck not able to get past ACQUIRE_PRMI due to the ~10-30Hz wiggle that starts a few seconds into PRMI catching. So far:

08:05 Got on to Tony trying to lock the ifo but having trouble getting past PRMI

08:29 Took us to DOWN to revert to previous alignment values that Ryan C used earlier (1400036418 aka 05/18/24 03:00 UTC)

08:30 Started an Initial Alignment

08:55 Initial Alignment finished
    - lscparams:
        - PRMI_MICH W_ALS changed 3.2 -> 2.6 and NO_ARMS changed 2.8 -> 2.6 (didn't help)
        - PRMI_PRCL W_ALS changed 6 -> 2 (didn't help)
    - ISC_LOCK and ISC_DRMI reloaded, starting relocking
- Couldn't get DRMI, went straight down to MICH instead of trying PRMI first
- Couldn't get PRMI to lock for more than ~3 seconds, then we get the wiggle between 10 and 30 Hz and lose it

09:47 Earthquake mode activated due to incoming earthquake from Alaska
10:33 Ground mostly settled after earthquake

The oscillations seem to start a couple of seconds after getting PRMI, right before ISC_DRMI's PRMI_LOCKED gets into .run. We wanted to see if it was related to the ramp times and/or value changes happening at the same time, so we have increased the gain ramp times for lines 518 (LSC_MICH1) and 519 (LSC_PRCL1) in ISC_DRMI from 2 to 4 seconds for each, and if that doesn't work I'll be adding in timers between these lines and around the other value changes and gain ramps between those lines and the end of PRMI_LOCKED .main in ISC_DRMI.

Comments related to this report
oli.patane@LIGO.ORG - 05:13, Sunday 19 May 2024 (77920)

11:18 Lines 518 and 519 in ISC_DRMI gain ramp time was increased from 2 to 4 seconds, reloaded, relocking
    - didn't work, still lost lock at same place

I added 5 second sleep timers after each line where a filter value or ramp time was changed between ACQUIRE_PRMI LSC_MICH1 gain ramp time (line 518) to the end of .main in PRMI_LOCKED, and the oscillations started 3 seconds after LSC_MICH1 (this is still with ramp time set to 4s instead of 2s).

Then I changed LSC_MICH1 ramp time back to 2
- Not sure what happened this time - didn't seem to oscillate, just a short lock

Putting the detector in DOWN for the next hour until I can wake people up

oli.patane@LIGO.ORG - 07:43, Sunday 19 May 2024 (77922)

Ryan C has come in for his shift this morning, so right before he came in I reverted all changes made to lscparams and the ISC_DRMI script during our troubleshooting this past night and reloaded both ISC_DRMI and ISC_LOCK. This means that the PRMI_MICH and PRMI_PRCL gains in lscparams are back to where they were at the beginning of my shift (and I believe should also match what they were at the beginning of Tony's shift, since he said he also reverted everything back to how it was originally?).

H1 TCS
camilla.compton@LIGO.ORG - posted 16:31, Thursday 29 February 2024 - last comment - 00:34, Monday 20 May 2024(76056)
Measured Distance between ALS table and Viewport

At LLO, Aidan and Karla found the ISCTEX/Y tables (ALS/HWS) tables were further from the BSC viewport than designed which would change Aidan's T1000717  mode-matching calculations. Ours are also different, EY more than EX. 

Distances are from the ISC table horizontally to the viewport outside edge, as in D0902168 and D0902163.
Measured to the back edge of VP closest to chamber and removed 2" for VP flange thickness, in photos the tape measure distance is 3". 
 
  Design Measured (+/-0.5") Difference 
ISCTEX to BSC10 right VP 16.5" D0902168  19.5" photo 3" = 75mm
ISCTEY to BSC9 left VP 16.5" D0902163 24.5"  photo 8" = 200mm
Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 00:34, Monday 20 May 2024 (77936)

Madison Simmonds, Camilla Compton

G1100873-v4 shows this center of VP to table distance is 18.6" which is closer to what was measured but not what was used in the HWS calculations.

Displaying reports 1601-1620 of 77270.Go to page Start 77 78 79 80 81 82 83 84 85 End