Displaying reports 41041-41060 of 88881.Go to page Start 2049 2050 2051 2052 2053 2054 2055 2056 2057 End
Reports until 13:20, Friday 17 May 2019
H1 SQZ (DetChar)
pep.covas@LIGO.ORG - posted 13:20, Friday 17 May 2019 (49310)
Line at 29.96944 Hz coherent with squeezer

A new line at 29.96944 Hz appeared the 5 May. I ran a bruco analysis and besides some other channels, it showed coherence with some squeezer channels like OPO_SERVO_SLOW_OUT_DQ.

After running some spectrograms around that time, I saw that this line also appeared in many other channels since a long time ago, but the time it went on in DARM was coincident with the time when it also appeared for the first time in that squeezer channel. That time seems to be coincident with some SDF changes reported here, which changed some settings in two squeezer channels.

The attached image shows a comparison of the spectra before this SDF changes and afterwards, where the new line can be clearly seen.

Images attached to this report
H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 11:40, Friday 17 May 2019 - last comment - 18:43, Friday 17 May 2019(49307)
Refcav Alignment Touch Up (Out Of OBSERVING for CORRECTIVE_MAINTENANCE at 18:28utc)

Summary:  18:28utc:  Out of OBSERVING (CORRECTIVE_MAINTENANCE) for PSL refcav alignment

Sheila checked on the high freq Intensity noise reported by Georgia last night, and has traced this down to PSL Ref Cav transmission (talked with Jason & heard him mention he has noticed this transmission dropping when humidity in the H1 PSL room rises).  Consulted with Keita & we decided to take H1 out of OBSERVING & mark this time as CORRECTIVE_MAINTEANCE (FRS forthcoming).  Keita contacting Brian & I notified other observatory operators via TeamSpeak.

RefCav alignment touch up is being done by Jason here in the control room via picomotors on the table.  This touch up caused a lockloss.  Once Jason is complete, I will take H1 to DC Readout and then we will take this opportunity to check H1's ability to acquire (I assume this will involve alignment stuff---i.e. ASC & Dither line systems).

Comments related to this report
jason.oberling@LIGO.ORG - 13:17, Friday 17 May 2019 (49308)

The highest I could get the RefCav TPD voltage was ~2.56V; this is in contrast to our usual max of ~4.2V.  I'm not sure the reason for this difference, but it could be temperature/humidity related.  I took a quick look at temperature and humidity in the laser enclosure over the last few days, see attachment.  The swings in temp and %RH seen in the first half of the plot represent an incursion into the PSL enclosure this last Tuesday, 5/14/2019.  The table north temperature sensor has seen an increase since we left the enclosure, from ~74 °F to ~74.5 °F, while the table south temperature sensor has seen no change.  The humidity in the laser room has seen a large increase since the last incursion, it's currently sitting at ~42% (this makes sense as we've had some spring rain move into the area the latter half of this week).

Images attached to this comment
georgia.mansell@LIGO.ORG - 18:39, Friday 17 May 2019 (49322)

Once we got to NLN the high frequency noise in DARM was still bad.

Keita adjusted the FSS common gain (H1:PSL-FSS_COMMON_GAIN) from 20 dB to 24.5 dB 23 dB, which got rid of the noise. We tried to find a place in the guardian where this gain is set but it looks like it isn't hard coded anywhere, and it will just go back to its original value.

 

If we lose lock and re-acquire and this gain is somehow reverted to 20dB, operators could try stepping it back (eg by running the command z step H1:PSL-FSS_COMMON_GAIN +0.1 until it reaches 23).

keita.kawabe@LIGO.ORG - 18:43, Friday 17 May 2019 (49323)

The change was quite drastic, a difference of 1dB or so suddenly quenched terrible high frequency stuff.

24.5dB was based on the fact that the last time FSS common gain was set to 20dB was when the refcav transmission was 4.2, now it is 2.5, so it was the reduction of 4.5dB.

However, after doing that we noticed that H1:PSL-FSS_FAST_MON became quite glitchy, so I reduced it to 23dB, which looks OK.

LHO General
corey.gray@LIGO.ORG - posted 08:16, Friday 17 May 2019 (49304)
Transition to DAY Log

TITLE: 05/17 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 111Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

Got the rundown of everything Niko dealt with for his fairly busy shift.  Sitting here and looking around only items to note at this moment:

H1 General
yannick.lecoeuche@LIGO.ORG - posted 08:04, Friday 17 May 2019 (49303)
Shift Summary - Owl

TITLE: 05/17 Owl Shift 07:00 – 15:00 (00:00-08:00), all times posted in UTC

STATE of H1: Observing

INCOMING OPERATOR: Corey

SHIFT SUMMARY: Began the shift locked (thanks to Georgia’s ADS rephasing), but started experiencing issues about two hours in. We were taken out of Observing several times by the SQZ laser locking and unlocking. Rather than mess with the SQZ system, I un-monitored the relevant channels and we were able to keep 110 Mpc lock. I also had to re-phase PIT3 on the ADS overview from 90 to 110 to suppress ASC yaw oscillations. After those changes, things quieted down. We’ve been locked for 9 hours, Observing for 4 hours.

LOG:

07:00 (00:00) Start of shift

08:44 (01:44) Something took us out of Observing, but it was immediately ready to go back in

09:14 (02:14) DIAG_SDF showing ‘sysecatc1plc4: 2’ every few minutes, taking us out of Observing. Putting IFO into AUTOMATIC OPERATION so that it’s back to Observing faster.

09:26 (02:26) Going out of Observing, re-phasing ADS PIT3 to try and suppress oscillations

09:59 (02:59) Un-monitoring three sdf channels (will post alog), bringing us back to Observing

10:21 (03:21) Out of Observing, taking SQZ GUARDIAN to DOWN to check if we’re losing range from the SHG railing.

10:37 (03:27) Back to Observing, with squeezing

15:00 (08:00) End of shift

H1 SQZ
yannick.lecoeuche@LIGO.ORG - posted 03:38, Friday 17 May 2019 - last comment - 14:50, Friday 17 May 2019(49301)
Re-phasing ADS PIT3, un-monitoring SQZ channels

After being locked for ~1.5 hours, ASC yaw oscillations started to build up. I re-phased PIT3 in the ADS overview to 110 via Georgia's original re-phasing alog (49298). This is reducing the oscillations, so I am accepting sdf changes for this phase setting.

Additionally, before this we were getting taken out of Observing sporadically with changes to H1:SQZ-FIBR_SERVO_COMGAIN, H1:SQZ-FIBR_SERVO_FASTGAIN, and H1:SQZ-FIBR_LOCK_TEMPERATURECONTROLS_ON. On the SQZ medm screen it looks like the SHG Power is to blame, as it is railing to -9000. There is an alog about this that Nutsinee posted (48760), but I don't think I can recreate what she did to mitigate the problem. We still get an extra 15 Mpc with squeezing on, so I'm un-monitoring these channels for now and going back to Observing.

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 05:16, Friday 17 May 2019 (49302)

This doesn't look like it is caused by the power stabilization servo (even so it is railed). This is related to the TTFSS. More likely a laser related readback is close to its limit and trips the laser auto-locker. Look at the error flags of the squeezer laser auto-locker to determine which sensor might be responsible.

Was alog 49181 ever un done?

corey.gray@LIGO.ORG - 09:26, Friday 17 May 2019 (49306)SQZ

Looking at the Laser Auto Locker medm, I see the autolocker is OFF, and we have the following error:

"Fiber trans PD Error" (screenshot attached).

In an alog search, I see that there were waveplate adjustments on Maintenance by Sheila (alog 49237).

Ops Note:  Will we want to re-monitor the squeezer channels Niko notes above at some point?

Images attached to this comment
corey.gray@LIGO.ORG - 14:50, Friday 17 May 2019 (49313)SQZ

OK, after chatting with commissioners and emails from Daniel, wanted to give an update.

Issue appears to have fixed itself after the RefCav touch up by Jason.  So undid what has been done for this last night & alog 49181 on Daniel's request:

  1. High Power Limit returned to 0.03 (Sheila already did this.  see attached)
  2. Re-enabled HiLo (see attached)
  3. Monitored 3-channels Niko unmonitored on CS_ECAT_PLC4:  H1:SQZ-FIBR_SERVO_COMGAIN, H1:SQZ-FIBR_SERVO_FASTGAIN, and H1:SQZ-FIBR_LOCK_TEMPERATURECONTROLS_ON.
Images attached to this comment
H1 General
yannick.lecoeuche@LIGO.ORG - posted 02:10, Friday 17 May 2019 (49300)
SDF diffs taking us out of Observing

We've dropped out of Observing several times with DIAG_SDF reporting:

USERMSG 0: DIFFS: sysecatc1plc4: 2

There are no changes to accept, however, and this seems to happen every few minutes. The only thing I know of that is different from before is that ASC yaw oscillations have been steadily increasing for the past hour.

H1 General
yannick.lecoeuche@LIGO.ORG - posted 00:25, Friday 17 May 2019 (49299)
Ops OWL Shift Transition

Ops Shift Transition: 05/17/2019, Owl Shift 07:00 – 15:00 (00:00-08:00) - UTC (PT)

State of H1: Locked

Intent Bit: Observing

Weather: No wind, raining

Primary 0.03 – 0.1Hz: 0.01 um/s

Secondary 0.1 – 0.3Hz: 0.1 um/s

Outgoing Operator:     Ed

Quick Summary: Locked for a little over an hour after Georgia did some ADS re-phasing (see alog 49298). DARM looks noisy but we’re holding lock at 109 Mpc.

H1 ISC
georgia.mansell@LIGO.ORG - posted 00:24, Friday 17 May 2019 (49298)
Locking tonight

Ed, Georgia

Tonight we encountered the same problem as last night - a 0.5Hz instability that rang up in the INCREASE_POWER state. We tried various iterations of gains and notches in INP1 and the DC centering loops, including what was suggested by Sheila and Keita, but still had trouble.

What we did that allowed us to power up (this time)

For now both of these changes are in the guardian/accepted in SDF.

 

The power up whole story

I added stricter convergence checkers in INCREASE_POWER but they weren't strict enough and we lost lock again. I've left these in the guardian anyway.

I noticed that when we engage the soft loops the POP RF18 buildups get worse (though the recycling gain gets better). I tried adding an offset to the PRC2_P loop (still at 2W input power), saw RF18 and the power recycling gain increasing and the 0.5 Hz instability ringing up in pitch and INP1 Yaw, strange.

I opened the PIT3 ADS loop (pointing of PRM) and aligned it by hand for better buildups.

We tried powering up again, with 60s waits at each 5 W power step, and survived just fine. At this point (sitting at 20W) I tried closing the PIT3 loop again, and as it, and the rest of the ASC, converged we saw the 0.5 Hz ring up and we lost lock. I very roughly re-phased the PIT3 loop so that the error signal was zero for the better alignment.

The next time we survived the power up.

This PIT3 phasing does not look good full power: there is a clear line in DARM at the dither frequency (19.653 Hz), and there is some lumpiness at low frequency that looks like bad A2L. I think we haven't actually solved the problem, but since we had a superevent (just locked in time, whew!) I don't want to take us out of observing to play with the phasing.

 

Intensity noise coupling

This lock has a terrible breathing noise above 2 kHz. This is intensity noise (see attached plot and coherence between DARM and the ISS second loop PDs) and is surprising since it should be squashed by the ISS second loop. Maybe we need to take a look at the open loop transfer function and adjust the gain?

Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 23:59, Thursday 16 May 2019 (49297)
Shift Summary - Eve

TITLE: 05/17 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: Niko
SHIFT SUMMARY:

After much trial and error Georgia got the kinks worked out and we were able to get H1 back up and Observing. Everything leading up to that is in my previous aLog.
LOG:

 

H1 General
edmond.merilh@LIGO.ORG - posted 22:49, Thursday 16 May 2019 (49296)
H1 Back to Observing 5:46UTC
H1 SEI
edmond.merilh@LIGO.ORG - posted 20:24, Thursday 16 May 2019 (49295)
H1 ISI CPS Sensor Noise Spectra Check - Weekly FAMIS #12847

Everything seems to be in order.

Images attached to this report
H1 PSL
edmond.merilh@LIGO.ORG - posted 20:08, Thursday 16 May 2019 (49294)
PSL Weekly Report - 10 Day Trends FAMIS #10609

Everything looks to be nominal. Diode powers seem to have been intentionally increased.

Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 19:58, Thursday 16 May 2019 - last comment - 20:00, Thursday 16 May 2019(49292)
Mid Shift Summary - Evening

The evening started out with a summary of actions to be taken during lock acquisition according to the aLog posted by Sheila and the special operator's note.

then......

22:52 5.2 EQ in the Central E Pacific rise caused a lockloss with no alerts of incoming.

23:44 I realized that the Observatory mode was still in Observing since 23:19 (Verbal Alarms were working for everything else)

00:14 Initial Alignment after 2 failed DRMI attempts

00:39 Re-Locking

01:45-present sitting at Increase Power to wait for SRC Soft Loops to converge.

2:58 Temp MX alarm

P.S.

        I also noted that during initial alignment, SRC align Guardian gave the green light to Offload before the Pitch Control signals had actually converged. One should watch this in the future.

Comments related to this report
edmond.merilh@LIGO.ORG - 20:00, Thursday 16 May 2019 (49293)

.5Hz issue continues to haunt

Images attached to this comment
LHO General
corey.gray@LIGO.ORG - posted 16:16, Thursday 16 May 2019 - last comment - 10:14, Monday 17 June 2019(49277)
DAY Operator Summary

TITLE: 05/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

Troubleshooting was the focus in the morning (Betsy on IMC & Sheila on ASC).  Since thinking about any hardware changes since Maintenance Day, Sheila & Marc went to check baluns (no issue there).  Ultimately, Sheila (& Keita later joining her) was able to get h1 back to NLN by focusing on ASC.  We've been locked for all of the second part of the shift.

NOTE:  See Sheila's alog about how to handle H1 if you have trouble after a lockloss.


LOG:

Comments related to this report
jeffrey.kissel@LIGO.ORG - 10:14, Monday 17 June 2019 (49988)DetChar, SEI
Tagging @DetChar and SEI for data in seismic's sensor correction configuration transition studies.
H1 ISC (OpsInfo)
sheila.dwyer@LIGO.ORG - posted 15:49, Thursday 16 May 2019 - last comment - 16:06, Thursday 16 May 2019(49286)
ASC change this morning allows us to lock, summary of the last couple of days of locking problems, operator note for relocking

Sheila, Keita

We have been able to get back to observing after struggling with ASC problems since Tuesday maintence.  We will need to wait for a few lock acquisitions to see if our changes have solved the problem consistently or not.

ASC work this morning:

This Keita and I picked up where Georgia and Cheryl left off last night, 49273.  We looked at 4 locklosses where there was a large 0.5 Hz oscillation in INP1 Y, DSOFT P, PRC2 P+Y, SRC2P and DC2 (REFL) P when the circulating power reached about 90kW in each arm. Screenshots of each of these locklosses are attached in chronological order, in each case INP1 Y seems to be the largest and earliest thing to run away.  Georgia changed the configuration in each power up attempt, as she wrote in the alog.

4:41 UTC:  REFL centering loops have notches for pitch, but not yaw.  New AS72 phases from yesterday earlier in the evening, and INP1 P gain increased by 20dB from it's normal gain.

5:07 UTC:  REFL centering loops have notches for pitch, but not yaw.  New AS72 phases from yesterday earlier in the evening, and INP1 P gain at its nominal gain.

6:51 UTC:  REFL centering loops have 0.5 Hz notches for pitch, and yaw notches added.  New AS72 phases from yesterday earlier in the evening, and INP1 P gain increased by 20dB from it's normal gain.

7:15 UTC:  REFL centering loops have 0.5 Hz notches for pitch, and yaw notches added.  New AS72 phases reverted to old settings, and INP1 P gain increased by 20dB from it's normal gain.

This morning Corey locked the IFO, and rode out an earthquake that peaked at around 0.2 um/second in earthquake mode.  After the earthquake passed I checked that the AS72 phases were really giving us an alignment that minimized the POP90 build ups once the arm dither loops were on (we tuned the phases last night before engaging the arm dithers).  I then tried to revert to the configuration that we were able to power up with a few times yesterday, INP1 gain low, notches on in pit refl centering loops but not yaw.  When I tried to revert the AS72 phases, the POP90 build up got worse and we lost lock suddenly (similar to the locklosses that were making it difficult to get to DC readout yesterday.).  

In the next lock we turned off all the 0.5Hz notches in REFL centering loops, and manually reduced the gain of INP1 P back to its nominal after the ASC was engaged, keeping the new AS72 phasing.  We saw no oscillations at all with that configuration, and that is how we are currently locked.  We looked at the measurements of the refl centering loops taken last week when we were having 2 minute yaw oscillations 49160.  While we had the slow oscillations the REFL centering loops weren't suppressing their error signals in yaw well, so after we turned off the notches we also added a boost.  The loop is probably only marginally stable with both the boost and the notch on, although it should be stable with either one alone on.  We are leaving the boost on and the notch off for now.

Summary of difficulties since Tuesday:

On Tuesday we started to have difficulty with locklosses when engaging the ASC after we came back from maintenance, clearly something had changed since turning the loops on was decreasing our build ups, although turning the dither loops on helped bring them back.  We thought that this could be an issue with our initial alignment references, in part because of the move of TMSY M3.  Since we haven't reset the green references since before moving the spot positions at the end of the ER, we decided to reset the green references  49245  We had lots of trouble acquiring lock with the spot positions set to be close to their full lock positions, loosing lock in the CARM transitions and transitioning DRMI to POP.  It may be that we cannot have our spots as far off center before we engage the ASC as we have them in full lock now.  This took us a few hours, after we reverted the references we were again able to lock, but continued to have difficulty engaging the ASC.  

We were in this state were we were able to survive the ASC engagement maybe in every 3rd attempt from late Tuesday until yesterday evening, which has cost us a lot of time.  We lost lock once on Tuesday because of a 0.5Hz pitch instability as we attempted to increase power, the next time we were able to attempt that the oscillation started and we engaged the pitch REFL centering loops 0.5Hz notches, which we had removed uneventfully  last Thursday 49160.  Since engaging them made the oscillation stop and allowed us to power up, we left them on.  That lock was the one that gave us a few hours of observing time late Tuesday and early Wed.

Early Wed morning Cheryl had a lockloss caused by the glitch problems of the MC1 or MC3 osems, 49280.  This also caused us one more lockloss on Wed, because of the existing alignment problems it took us a lot of time to recover from these on Wed.  We made three attempts to increase the laser power on Wed, the first we lost lock because of an osem glitch, and the next two we lost lock because of a problem with the ASC that seems to start when we reduce the 9MHz modulation depth at 40W input power.  

Yesterday afternoon we restored the TMS M3 pico according to it's counter (because we thought that a change in initial alignment references could be responsible for our difficulties) , but this didn't make much of a difference in the alignment problems, so we concluded that the issue probably wasn't related to the green references. We then watched which loops were slow to bring their error signals to zero as the ASC gets engaged, and saw INP1, SRC2P and SRC1P were all very slow.  We speed up INP1 +SRC2P, but still had locklosses engaging the soft loops.  After that Georgia and I phased AS72 WFS.  I think that a combination of the changes we made yesterday afternoon are now allowing us to get to DC readout and be stable there better than we were yesterday, I don't see as many locklosses engaging ASC after the time when we made these changes.  

However, after this we had the 0.5Hz instability problems when power up.  The guardian is now set up to relock with the INP1 P gain increased, we think this should be good because the INP1P loop was incredibly slow (taking ~10 minutes to converge) without it.  The notches in REFL centering are off, and will stay off unless someone manually turn them on. 

A note for the next operators to lock H1:

We are leaving the guardian set up to relock H1 in a state that is slightly different from the one that worked for this lock, because we think that should work better than what we did this time.  If all goes well, you will have no problems locking and an SDF DIFF in the ASC OBSERVE file next time H1 is relocked, which is that ASC-INP1_P FM4 is off.  

If you do have trouble with an ASC instability (especially a 0.5Hz instability) while increasing the power, it may be that we need to reduce the gain of INP1 P by engaging this filter (H1:ASC-INP1_P FM4) while we power up.  You can find the filter by SITEMAP -> ASC- > central_servo_overview, INP1P is in the upper left corner.  Once you reach DC readout, you can turn on FM4 which is named -20dB to reduce the gain. It is OK to do this manually until someone has a chance to add it to the guardian if necessary. 

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 16:06, Thursday 16 May 2019 (49290)

Also, for now H1:PSL-ISS_SECONDLOOP_REFERENCE_PN_MTRX_1_4 is 110 and it is accepted in SDF, but it should be nominally 125.

Next time it locks it's changed back to 125 by the guardian, so make sure to accept that.

H1 SUS
betsy.weaver@LIGO.ORG - posted 11:54, Thursday 16 May 2019 - last comment - 16:20, Thursday 16 May 2019(49280)
MC1 and MC3 glitches

This morning I spent some time looking for more MC1 and MC3 glitches, reported by Cheryl, Jenne, Sheila yesterday https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=49257

The summary from Tuesday forward is that - 

It's not obvious that these glitches are continuing.  We scanned back a week and did not see any such glitches prior to their start at 5am local Wed. 

Also, they do not appear on PR2 (PRM and MC2 are hard to see due to all of the actuation on them which causes the signal to jump around.)

(Betsy, Fil, Marc)

 

 

Images attached to this report
Comments related to this report
rahul.kumar@LIGO.ORG - 16:20, Thursday 16 May 2019 (49291)

Its now been more than 4 hrs of IFO lock and I have been keeping an eye on the MC1 and MC3 for any glitches: none so far.

Displaying reports 41041-41060 of 88881.Go to page Start 2049 2050 2051 2052 2053 2054 2055 2056 2057 End