TITLE: 04/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 28mph Gusts, 15mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.18 μm/s
QUICK SUMMARY:
Lockloss a 22:58 UTC with unkown cause right after SuperEvent S240428DR and during the Stand Down Time.
Screen Shots of the Lockloss tools NDSCOPEs attached.
---Relocking---
Started relocking immediately without an Initial Alignment.
Increase flashes ran on both arms.
Lockloss at ENGAGE_DRMI_ASC
Will try again with out IA, and if that fails then I will do an IA.
Also Robert Still has Cones up on the road along Y arm to protect his cable that he has run across the street. Please be aware of this cable and try not to drive down the Y arm with out addressing this cable going across the street.
TITLE: 04/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Two locklosses this shift (one as I type this), observing for the rest of the time. Since relocking this afternoon, DARM in high frequency didn't look as good and range was slightly lower.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
17:43 | PEM | Robert | LVEA | - | Grabbing guillotine, blocking camera | 17:49 |
18:17 | PEM | Robert | LVEA | - | Blocking different camera | 18:44 |
Another picket fence issue at 03:37 UTC, I think the third in the past few weeks. I restarted the process on nuc5.
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.
Sun Apr 28 10:09:35 2024 INFO: Fill completed in 9min 31secs
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.
H1 back to observing at 18:22 UTC.
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.
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.
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!
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.
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.
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 |
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.
H1 back to observing as of 18:29 UTC.
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.
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.
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.
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
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.
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
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.