Displaying reports 12961-12980 of 88171.Go to page Start 645 646 647 648 649 650 651 652 653 End
Reports until 10:22, Sunday 28 April 2024
H1 CDS
david.barker@LIGO.ORG - posted 10:22, Sunday 28 April 2024 - last comment - 15:40, Tuesday 30 April 2024(77473)
Restarted picket-fence, it has stopped 03:37:04 UTC Sun 28 April 2024

Another picket fence issue at 03:37 UTC, I think the third in the past few weeks. I restarted the process on nuc5.

Comments related to this report
david.barker@LIGO.ORG - 11:29, Monday 29 April 2024 (77485)
edgard.bonilla@LIGO.ORG - 15:40, Tuesday 30 April 2024 (77524)

Thank you for this summary. I will go dig in the code to see what is happening.

On first glance: the array of data should never be empty on an update, but somehow it is happening some times. I will add a failsafe (or an assert) so that the code can handle this exception and hopefully be more robust.
 

LHO VE
david.barker@LIGO.ORG - posted 10:15, Sunday 28 April 2024 (77472)
Sun CP1 Fill

Sun Apr 28 10:09:35 2024 INFO: Fill completed in 9min 31secs

Images attached to this report
H1 General (Lockloss)
ryan.short@LIGO.ORG - posted 10:09, Sunday 28 April 2024 - last comment - 11:23, Sunday 28 April 2024(77471)
Lockloss @ 16:50 UTC

Lockloss @ 16:50 UTC - link to online lockloss tool

Looks like ETMX had a glitch/saturation immediately before the lockloss (also seen by LSC-DARM), but otherwise I don't see an obvious cause.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 11:23, Sunday 28 April 2024 (77474)

H1 back to observing at 18:22 UTC.

LHO General
ryan.short@LIGO.ORG - posted 08:01, Sunday 28 April 2024 (77470)
Ops Day Shift Start

TITLE: 04/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 143Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY: One lockloss early this morning at 12:01; H1 was able to relock on its own. Now locked and observing for almost 2 hours. Planning for coordinated calibration sweeps with L1 at 18:30.

H1 General
anthony.sanchez@LIGO.ORG - posted 00:01, Sunday 28 April 2024 (77469)
Sat Eve Ops Shift End

TITLE: 04/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s
SHIFT SUMMARY:
Very quiet night.
The Wind is dieing down finally.
H1 Has been locked for 12 Hours and 12 minutes, and Observing.

H1 SEI
anthony.sanchez@LIGO.ORG - posted 23:46, Saturday 27 April 2024 (77468)
BRS Drift Trends--Monthly

BRS Drift Trends--Monthly Famis 26442

Trends go all the way back to Febuary which is when we let air into the vacuum chamber, so the ETMY Damp CTRL signal does make sense for that time frame in Febuary and early March.
BRSX has a few interesting spikes, April 2nd or 3rd Jim was adjusting the mass adjuster pico meter.
March 6th & 7th ish there was  some BRSX work & computer restart due to BRS not damping .

But Both BRS X & Y are within range!

Images attached to this report
H1 CAL
anthony.sanchez@LIGO.ORG - posted 22:29, Saturday 27 April 2024 (77467)
PCAL EX End Station Measurements & Lab Measurements April 23rd

A PCAL EndX Station Measurement was done on April, the PCAL team(    
 Dripta B. & Tony S.) went to EndX with Working Standard Hanford aka WSH(PS4) and took an End station measurements.
The EndX Station Measurement was carried out according to the procedure outlined in Document LIGO-T1500062-v15, Pcal End Station Power Sensor Responsivity Ratio Measurements: Procedures and Log.


Measurement Log
First thing they should have done was take a picture of the beam spot before anything is touched!


Martel:
Martel Voltage source applies voltage into the PCAL Chassis's Input 1 channel. We record the GPStimes that a -4.000V, -2.000V anhttps://alog.ligo-wa.caltech.edu/aLOG/uploads/77467_20240427213103_SPot.jpgd a 0.000V voltage was applied to the Channel. This can be seen in Martel_Voltage_Test.png . We also did a measurement of the Martel's voltages in the PCAL lab to calculate the ADC conversion factor, which is included on the above document.

Plots while the Working Standard(PS4) is in the Transmitter Module during Inner beam being blocked, then the outer beam being block, followed by the background measurment: WS_at_TX.png.

The Inner, outer, and background measurement while WS in the Receiver Module: WS_at_RX.png.

The Inner, outer, and background measurement while RX Sphere is in the RX enclosure, which is our nominal set up without the WS in the beam path at all.:  TX_RX.png.

The last picture is of the Beam spots after we had finished the measurement.


All of this data is then used to generate LHO_EndX_PD_ReportV2.pdf**** which is attached, and a work in progress in the form of a living document.


All of this data and Analysis has been commited to the SVN :
https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Projects/PhotonCalibrator/measurements/LHO_EndX/


PCAL Lab Responsivity Ratio Measurement:
A WSH/GSHL (PS4/PS5)FrontBack Responsivity Ratio Measurement was ran, analyzed, and pushed to the SVN.
The analysis of this measurement produces 4 PDF files which we use to vet the data for problems.
raw_voltages.pdf
avg_voltages.pdf
raw_ratios.pdf
avg_ratios.pdf

 

Obligitory BackFront PS4/PS5 Responsivity Ratio:
PCAL Lab Responsivity Ratio Measurement:
A WSH/GSHL (PS4/PS5)BF Responsivity Ratio measurement was ran, analyzed, and pushed to the SVN.
The analysis of this measurement produces 4 PDF files which we use to vet the data for problems.
AlphaTrends
raw_voltages2.pdf
avg_voltages2.pdf
raw_ratios2.pdf
avg_ratios2.pdf

This adventure has been brought to you by Dripta B. & Francisco L.

 

 

Images attached to this report
Non-image files attached to this report
H1 General (OpsInfo, PEM)
anthony.sanchez@LIGO.ORG - posted 16:12, Saturday 27 April 2024 (77466)
Sat Eve Ops Shift Start

TITLE: 04/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 23mph Gusts, 14mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:
Wind speeds are elevated, but H1 has been Locked and Observing for over 4 hours.
Robert has an accelerometer line going through the Hallway, out the door and across the road. Please dont drive down Y arm until after the cable has been removed sometime tomorrow.

 

LHO General
ryan.short@LIGO.ORG - posted 16:00, Saturday 27 April 2024 (77465)
Ops Day Shift Summary

TITLE: 04/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: One lockloss and an earthquake this shift, but otherwise a quiet one. Since neither H1 nor L1 were locked for the scheduled 18:30 UTC coordinated calibration sweeps, we have postponed them until tomorrow at the same time.

H1 has now been locked for 4 hours.

LOG:

Start Time System Name Location Lazer_Haz Task Time End
17:19 PEM Robert EX - Picking up cables 17:37
H1 General (Lockloss)
ryan.short@LIGO.ORG - posted 10:36, Saturday 27 April 2024 - last comment - 11:59, Saturday 27 April 2024(77463)
Lockloss @ 17:18 UTC

Lockloss @ 17:18 UTC - link to online lockloss tool

There was a M6.1 quake from Indonesia incoming at the time, although I don't immediately see evidence that ground motion caused this lockloss.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 11:59, Saturday 27 April 2024 (77464)

H1 back to observing as of 18:29 UTC.

LHO VE
david.barker@LIGO.ORG - posted 10:26, Saturday 27 April 2024 (77462)
Fri and Sat CP1 Fill

Sat Apr 27 10:10:32 2024 INFO: Fill completed in 10min 28secs

Fri Apr 26 10:10:46 2024 INFO: Fill completed in 10min 42secs

Jordan confirmed a good Friday fill curbside.

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 08:06, Saturday 27 April 2024 (77461)
Ops Day Shift Start

TITLE: 04/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY: Looks like H1 lost lock around 6 hours ago from a M6.5 EQ from Japan and Oli was able to help it back up. H1 has been locked and observing for 3 hours.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 07:34, Saturday 27 April 2024 - last comment - 15:38, Tuesday 30 April 2024(77460)
Step in Clean range around 5:20 this morning

There was a drop in clean range around 5:20 this monrning, which doesn't seem to be a reapeat of the output arm shift we had earlier this week. 

Attached is a trend of the DARM blrms (based on DARM error, no calibration corrections or cleaning) and comparison of the cleaned and corrected range against the CAL-DELTAL range, only the cleaned channel sees the drop.  This made me concerned that we had a drop in optical gain, but the trend of the time dependent calibration correction factors doesn't show anything happening at this time. 

I don't know what would cause a sudden change in the clean range, since I don't think that the jitter subtraction would cause a sudden change like this.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 15:38, Tuesday 30 April 2024 (77523)CAL

I'm still not at all sure why this drop happened, particularly if Sheila notes that there were no changes in the calibration TDCFs.  However, the drop is seen in all of the GDS-CALIB_STRAIN channels, not just a drop in the _CLEAN channel.  This indicates that the range drop comes from earlier in the process than the line subtraction or the cleaning. 

The crosshair in the attached plot is the same time as the crosshair in Sheila's plot, just to make it a little easier to orient and compare the plots.

Blue: Range from CAL-DELTAL_EXTERNAL

Green: Range from GDS-CALIB_STRAIN

Red: Range from GDS-CALIB_STRAIN_NOLINES

Orange: Range from GDS-CALIB_STRAIN_CLEAN

Images attached to this comment
H1 General
oli.patane@LIGO.ORG - posted 04:47, Saturday 27 April 2024 (77459)
04/27 OWL Intervention

H1 Manager called because it couldn't get ALSY to lock in initial alignment. The flashes were barely below being able to catch. I paused INIT_ALIGN and touched ALSY in yaw and we were able to lock green and are on our way back up.

H1 General
anthony.sanchez@LIGO.ORG - posted 00:02, Saturday 27 April 2024 (77458)
Friday night Eve Shift End

TITLE: 04/27 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: Oli
SHIFT SUMMARY:
H1 is locked and Observing for 4 Hour now.
Relatively quiet night.
 

LOG:
No log

LHO FMCS
anthony.sanchez@LIGO.ORG - posted 22:57, Friday 26 April 2024 (77457)
Vibration Sensors HVAC Fans Health

FAMIS 26297

H0:VAC-MX_FAN1_370_2_ACC_INCHSEC has a very Strange looking reoccuring ingrease in its noise.
It looks like this fan wasn't being used until about 100 days ago. 100 days ago it seemed to be fairly noisy as well, but this is strange looking and very different.
it seems like the fan is noisy for 12-16 ish hour and quiet for 8-16 hours. Maybe this particular fan isnt on for 8 hours,
It's likely it turns on at 1Pm and turns Off at 9-10 pm.

I think this is a new noticable development since the last time I checked on the Vibrometers.

Images attached to this report
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 20:39, Friday 26 April 2024 (77456)
Lockloss & Fri Mid Eve shift update

TITLE: 04/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

00:52 UTC Intentional Drop from Observing to adjust squeeze angle.

Requested SQZ_MANGER to go to SCAN_SQZANG saw the phase slider move around a bit and it created https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/SQZANG_SCAN/SQZANG_SCAN_240426175458.png

00:56 UTC Back to Observing

2:04 UTC  Lockloss  https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1398218686

Unknown cause but ETMY L2 Master out starts to change behaivor about a second before the lockloss.


---Relocking--
Increase flashes ran for YARM
Happened automatically without any input from me.
Nominal_Low_Noise reached at 3:01 UTC
Observing reached at 3:04 UTC

 

Images attached to this report
X1 SUS (SUS)
oli.patane@LIGO.ORG - posted 20:05, Friday 26 April 2024 (77455)
Searching for the perfect position for the secondary prism on the BBSS

Ibrahim A, Oli P, Mark B, Betsy W

Context:

M3 on the beam splitter has secondary prisms that are placed along the barrel below the primary prisms. These secondary prisms are placed at a location below the primary prism, and if placed in the correct spot, act as a clamp, damping the oscillations moving down the wire loop into the optic. We've been working on finding the optimal secondary prism position for the BBSS.

Experiment:

The experiment for determining this position was developed for the BSFM in 2011(T1100086), and we used a similar setup for our three (successful) runs for the BBSS. This is basically how the experiment is set up to work:

  1. A biased solenoid is placed a few millimeters away from one of the M2-M3 loop wires. The solenoid is driven at the wire’s predetermined resonance frequency using a waveform generator.
  2. The wire goes from M2 down through M3’s fixed primary prism and (the reason for this experiment) moveable secondary prism.
  3. Phonograph needle is rested on wire below the secondary prism and the other end is connected to a spectrum analyzer. Five FFT averages are taken to give us an attenuated peak at the resonant frequency. This is a reading. We took 4/5 measurements for each location, where each measurement consisted of five 8-second averages.
  4. We move the prism down by a millimeter or two and take more readings.
  5. From the results, we determine the lowest amplitude peak/highest attenuation and note the prism position.
  6. This becomes the new BBSS secondary (glued on) prism position.

Results + Commentary:

Note: Mark has an upcoming alog about the run of data and issues that we took when he was here, but in LESS IMPORTANT Auxiliary Investigations we will be focusing on the data from the second and third runs, but here in the results will still be showing the data we got with him.

The plot attached shows the attenuation measured versus the position (positive distance relative to the mass’ centerline) of the secondary prism. Each color is a separate run, and the more negative the attenuation, the quieter the reading was, so we are looking for a location with the lowest values where the secondary prism would do the most damping.

We found that there is a region between ~29.00mm and ~31.5mm below the horizontal center of the mass where the amplitude is minimized. There are approximately three anomalous data points in between, with one confirmed being due to cross-coupling of above wire. As of now, we’re still working on understanding this data and have spoken to Mark B and Jeff K about how we can go about accurately interpreting the raw data (including essential questions about the calibration and setup. See below.)

LESS IMPORTANT Auxiliary Investigations - Details, Details, Details

    Read for Clues/Hints (things we noticed, changed etc.):

Images attached to this report
Displaying reports 12961-12980 of 88171.Go to page Start 645 646 647 648 649 650 651 652 653 End