Displaying reports 40481-40500 of 88906.Go to page Start 2021 2022 2023 2024 2025 2026 2027 2028 2029 End
Reports until 10:01, Friday 14 June 2019
H1 General (SEI)
travis.sadecki@LIGO.ORG - posted 10:01, Friday 14 June 2019 - last comment - 10:51, Monday 17 June 2019(49915)
Out of Observe for EQ transition

Transitioning to EARTHQUAKE mode for SEI.  This kicked us out of Observing due to H!ISIETMX SDF diffs (cleared themselves faster than I could get a screenshot).  Also, Sheila suggested also taking ISC_LOCK to EARTHQUAKE state, which also kicked us out of Observe since Guardian wants it in NLN to be in Observing.  I'll transition back soon as this was a smallish EQ, but we'll be out of Observing for a bit.

Comments related to this report
travis.sadecki@LIGO.ORG - 10:31, Friday 14 June 2019 (49916)SEI, SQZ

Back to Observing at 17:24 UTC.  ISI_CONFIG taken back to WINDY (I managed to get a screenshot of the transient SDF diffs this time, see attachement).  Also, SQZ was causing ZM2 to saturate.  Sheila took SQZ_MANAGER to SQZ_READY_IFO which cleared the saturations.  Upon returning to SQUEEZING, I got an SDF diff that the COMMBOOST was now 2.0 (which is the correct value according to Sheila) rather than 0.  Our range has returned to ~115 MPc, so we're thinking that SQZ got stuck in some strange state during the last relock.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 10:04, Monday 17 June 2019 (49980)DetChar, SEI
Tagging @DetChar and SEI for data in seismic's sensor correction configuration transition studies.
travis.sadecki@LIGO.ORG - 10:51, Monday 17 June 2019 (49996)
H1 General
patrick.thomas@LIGO.ORG - posted 09:34, Friday 14 June 2019 - last comment - 18:23, Friday 14 June 2019(49913)
Bruco started
Searches started for before and after lock loss last night
Started around 16:32 UTC

https://ldas-jobs.ligo.caltech.edu/~ldvw/bruco/patrick.thomas/H1-CAL-DELTAL_EXTERNAL_DQ_2019-06-13-18.30.53-600
https://ldas-jobs.ligo.caltech.edu/~ldvw/bruco/patrick.thomas/H1-CAL-DELTAL_EXTERNAL_DQ_2019-06-14-11.09.47-600
Comments related to this report
sheila.dwyer@LIGO.ORG - 18:23, Friday 14 June 2019 (49929)

In the second of these reports, the range was low because the squeezer LO servo had no boosts on due to a bug in the guardian code. There is was an extra peak in DARM around 272Hz, but the BRUCO report doesn't show anything very different there between the 2 locks. 

H1 General
travis.sadecki@LIGO.ORG - posted 08:21, Friday 14 June 2019 (49911)
Ops Day Shift Transition

TITLE: 06/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 110Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:  Lock is 10+ hours old, with the past 6 in Observing.

H1 AOS
cheryl.vorvick@LIGO.ORG - posted 08:19, Friday 14 June 2019 (49912)
changes between this lock and last

I ran my matlab code to look at two times, one during this lock, and one from the previous lock, to identify changes. Attached are results, in list form, from the excel file and in plots where the blue trace is from the previous lock and the red trace is from the current lock. 

channel   start end diff abs(diff)
H1:SUS-OMC_M1_DAMP_P_INMON p 1323.2684 1276.9399 -46.3284 46.3284
H1:SUS-PRM_M3_WIT_PMON p -1627.9656 -1581.6614 46.3043 46.3043
H1:SUS-SRM_M3_WIT_PMON p 2300.4584 2322.5835 22.1252 22.1252
H1:SUS-ZM1_M1_DAMP_P_INMON p -2407.8339 -2416.8431 -9.0092 9.0092
channel   start end diff abs(diff)
H1:SUS-SRM_M1_DAMP_Y_INMON y -1862.5385 -1887.4435 -24.9049 24.9049
H1:SUS-SRM_M3_WIT_YMON y -3533.2723 -3546.7958 -13.5235 13.5235
H1:SUS-SR2_M3_WIT_YMON y -219.2685 -225.0900 -5.8215 5.8215
Images attached to this report
Non-image files attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 08:07, Friday 14 June 2019 (49910)
OPS Owl Summary:

TITLE: 06/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 109Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY: winds are now under 10mph
LOG:

H1 General
cheryl.vorvick@LIGO.ORG - posted 05:15, Friday 14 June 2019 (49909)
OWL Mid-Shift Update

H1 has remained lock, past 2 hours have have a low glitch rate, range 106Mpc.

H1 General
cheryl.vorvick@LIGO.ORG - posted 00:09, Friday 14 June 2019 (49908)
OPS Owl Transition

TITLE: 06/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 108Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 14mph Gusts, 12mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:  locked in Observe

LHO General
thomas.shaffer@LIGO.ORG - posted 00:04, Friday 14 June 2019 - last comment - 10:12, Monday 17 June 2019(49896)
Ops Eve Shit Summary

TITLE: 06/14 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 107Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: After relocking from the earthquake and a end X Beckhoff crash, we are a bit down on range.
LOG:

Comments related to this report
jeffrey.kissel@LIGO.ORG - 10:12, Monday 17 June 2019 (49986)DetChar, SEI
Tagging @DetChar and SEI for data in seismic's sensor correction configuration transition studies.
H1 TCS
thomas.shaffer@LIGO.ORG - posted 23:45, Thursday 13 June 2019 (49907)
New Lock Point for TCSY CO2

The TCSY laser has lost lock a few times in the past few days (alog49888), so I tried to relock at a different lock point to potentially help. To do this, I let the Guardian node do most of the work, and watched to make sure that it was finding a good spot that was a bit further away than what it has been using. I manually brought the node to the find lock point state, and this state will continue to find new lock points if you keep it in this state (instead of moving on after finding the first suitable one).

I have noticed in that past that with larger temperature swings in the LVEA that we would sometimes lock lock, and since it has been the hottest days of this year the past two days I had thought that was the case again. After trending the temperature sensors near TCSY and the power set point offset, I'm not conviced. (see 2nd attached)

Hopefully this is a bit more stable at this further point.

Images attached to this report
H1 General
thomas.shaffer@LIGO.ORG - posted 22:02, Thursday 13 June 2019 - last comment - 22:10, Thursday 13 June 2019(49905)
Observing 0447 UTC

Earthquake recovery started with me trying to get the green arms to lock for longer than a few min while I waited for the ground motion to settle. At 0152 EX Beckhoff crashed. I called Patrick and he showed me how to restart it, but from the CDS overview PLC3's uptime was not counting up. This took a few different restarts and Patrick walking me through opening up the PLC3.pro and then logging in and running it. This seemed to solve the problem.

After I confirmed that beckhoff looked to be good again, I noticed that the EX ring heaters would not produce the correct power from the requested. Thinking that it was from teh Beckhoff boot, I tried to find the configuration parameters but they are not found from any medm (I put it on my todo list). I was able to figure out what was changed from SDF and this was fixed.

I began an initial alignment with the INIT_ALIGN guardian. After I touched up green, I could have left it to do teh entire initial alignment on its own except for one spot. When MICH Bright is requested the first time, it never seems to lock. But if you go to down and then request it again, it will lock right away. I've noticed this many times, but not sure why. Other than that it was a straight forward IA.

Once I had made it to DRMI locking, I received another incoming earthquake alarm. Though not as big as the one from Chile, it arrived right as we were powering up, bad timing. It was rough but we made it.

Attached: The reverted sysecatx1plc3 sdfs and the accepted LSC-MICHFF & SQZ-LO_SERVO_COMM_BOOST

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 22:10, Thursday 13 June 2019 (49906)CAL

Our range is only around 105Mpc, and I don't see anything glaring on the DARM spectrum as to why. Perhaps this is from one of the PCAL SDFs that I had reverted? They had changed at the same time as the Beckhoff restart, so I assumed the values in the snap files were correct.

H1 CDS
thomas.shaffer@LIGO.ORG - posted 19:22, Thursday 13 June 2019 - last comment - 13:25, Friday 14 June 2019(49903)
EX Beckhoff Crashed 0152 UTC

Currently talking to Patrick to get it going again.

Comments related to this report
thomas.shaffer@LIGO.ORG - 19:29, Thursday 13 June 2019 (49904)
Images attached to this comment
patrick.thomas@LIGO.ORG - 13:25, Friday 14 June 2019 (49921)
We restarted the computer twice, but each time PLC3 would not run. All the terminals were in OP and the IOC had started correctly both times. We ended up having to open PLC3, login and start it manually. When TJ did so he said that it reported that the program had changed and asked whether to download the new program. I had him say yes.
H1 General
thomas.shaffer@LIGO.ORG - posted 18:22, Thursday 13 June 2019 (49902)
Lock Loss 0119 UTC

The earthquake and wind finally got to us. We were all very impressed with how long we stayed locked considering though.

Images attached to this report
H1 General
thomas.shaffer@LIGO.ORG - posted 17:57, Thursday 13 June 2019 - last comment - 10:05, Monday 17 June 2019(49900)
Out of Observing 0025 UTC

Out to find a new lock point on the TCSY CO2.

As we started this work, we got a notification for an earthquake from Chile (6.4mag)

Comments related to this report
thomas.shaffer@LIGO.ORG - 18:16, Thursday 13 June 2019 (49901)

0032 UTC - Switched to the SEI_CONF EARTHQUAKE state, as this was the predicted state from the Seiplot.

0041 UTC - Changed ISC_LOCK state to EARHQUAKE to increase ADS line gains.

The wind has also picked up to mid 20s, not helpful.

jeffrey.kissel@LIGO.ORG - 10:05, Monday 17 June 2019 (49981)DetChar, SEI
Tagging @DetChar and SEI for data in seismic's sensor correction configuration transition studies.
LHO VE
chandra.romel@LIGO.ORG - posted 16:34, Thursday 13 June 2019 - last comment - 11:18, Thursday 20 June 2019(49897)
IP6 tripped

Around 4:17 pm local ion pump #6 in corner station tripped. I restarted the power supply and it seems to have recovered normally down to 162 micro-amps and falling.

 

Comments related to this report
rahul.kumar@LIGO.ORG - 11:18, Thursday 20 June 2019 (50086)

FRS ticket 13069, closed.

https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=13069

H1 ISC
jenne.driggers@LIGO.ORG - posted 15:40, Thursday 13 June 2019 - last comment - 17:29, Thursday 13 June 2019(49894)
New LSC feedforward, good for MICH, iffy for SRCL

[Laurence, Jenne]

We've recently imported V2 of Lee's IIRrational, and have been updating the feedforward fitting scripts to work with it (with lots of great support from Lee), and have applied it to feedforward measurements taken on Monday, after we'd thermalized at the new PSL power of 37W. 

Today we took a few minutes of pre-approved commissioning time to switch to the new MICH and SRCL feedforward filters.  The attached screenshot shows that the MICH filter is doing some good, however the SRCL filter is doing more harm than good.  I'd like to leave it on for a little while, but since we've got another pre-approved commissioning time once the Evening operator arrives to help the TCS CO2 laser, I'll likely revert the SRCL filter. 

In the attached plot, upper left shows LSC-DARM_OUT and the MICHFF and SRCLFF outputs that get sent to the ETMs to sum in with DARM.  References are all on the old 35W filters, current traces are the new filters.  You can see that there isn't much difference with the MICH output, but the SRCL output is much larger at low frequencies, and slightly larger at high frequencies. 

Upper right shows the difference in the calibrated Darm spectrum, that we've improved a bit between 10Hz - 15Hz, and above that any changes are quite subtle.  We've definitely degraded the spectrum below 9 Hz (the SRCL fit really, really wants to give a highish-Q peak there, to get the fit better above 10 Hz), which will contribute to upconversion around lines in the bucket.

Lower left shows the coherence between SRCL and DARM, and you can see that between 10-15 Hz, we've made an improvement, but both below and above that we have significantly hurt things, which is why I will revert the SRCL FF in 30 min or so.

Lower right, however, shows that the coherence between MICH and DARM is improved between 10-25 Hz, so that seems good. 

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 17:29, Thursday 13 June 2019 (49899)

The SRCL FF has been reverted for now.  We've lost that bit of improvement from 10-15Hz, but I think we don't want to be injecting as much noise as we were at lower freqs, so we'll keep working offline on a better version of the fit.

H1 ISC (ISC)
georgia.mansell@LIGO.ORG - posted 21:49, Wednesday 12 June 2019 - last comment - 16:38, Thursday 13 June 2019(49875)
Some output jitter investigation

Sheila, Georgia

Today while LLO was commissioning we took some time to look into output jitter. The end goal is to have a projection of OMC ASC to DARM for the noise budget, following similar methods to Koji or Carl

Today we only mostly ran excitations to the POS_Y loop, with various offsets and excitation levels. We also did a couple of excitations to the POS_X loop.

Other things to note:

Images attached to this report
Comments related to this report
georgia.mansell@LIGO.ORG - 16:38, Thursday 13 June 2019 (49898)

I had a look at DARM with and without the large offset in POS_Y, using the online time-dependent-correction-factor corrected channel (in the above alog the 3rd attachment is instead just using CAL-DELTAL_EXTERNAL).

The top plot of the attachment shows DARM with and without this offset, and with and without an excitation. The optical gain reduction with the alignment offset is obvious above 60 Hz, however I do not see any extra jitter coupling. I also plotted the coherence between one of the QPD channels and DARM (all the QPD channels looked very similar), and don't see anything there.

If I understand correctly: Adding the alignment offset increased our excitation coupling by a factor of 2, so given that we don't see extra jitter coupling with the offset our ambient noise is at least a factor of 2 below DARM.

Note: we were limited to offsets between -1 and 6 in the POS_Y degree of freedom: going outside these bounds saturated the OMC suspension.

Images attached to this comment
Displaying reports 40481-40500 of 88906.Go to page Start 2021 2022 2023 2024 2025 2026 2027 2028 2029 End