Displaying reports 61881-61900 of 85905.Go to page Start 3091 3092 3093 3094 3095 3096 3097 3098 3099 End
Reports until 20:50, Sunday 03 January 2016
H1 PSL
betsy.weaver@LIGO.ORG - posted 20:50, Sunday 03 January 2016 - last comment - 09:16, Monday 04 January 2016(24665)
Wiggly ISS power

Just because...

While watching the IFO come back up, it was noticed that the live trend of ISS Diffracted Power was wiggling alot like the live trends of POP_A and IMC_TRANS.  Attached is a trend for the curious.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 21:42, Sunday 03 January 2016 (24666)DetChar, ISC, SYS
J. Kissel, B. Weaver

I'm the curious. I did a bunch more starring at these channels, trying to come up with a theory for all of this ETMX oscillation business. My best theory at this point: this wiggling is a mixing of tidal + length to angle coupling of the QUADs against power fluctuations arising from the ISS 2nd loop's feedback to the 1st loop, which is then fed back to the AOM's signal that we stare at for drift. Check out my attachment. All of the channels in the attachment, representing DHARD, Tidal, the IMC, the ISS... are all wiggling at roughly the same frequency.

Here're some things I've notice while staring:
(1) Notice that the Tidal Error signal (as shown by H1:IMC-F_OUT16 in DARK Green) is perfectly anti-correlated with the DHARD Pitch control signal (H1:ASC-DHARD_P_OUT16 in Purple). This is no surprise to me because I know that Tidal is fed to the UIM stages of both QUADs, which are known to have plenty of UIM-length-to-TST-angle imperfections. You could also claim some correlation between the DHARD yaw control signal (H1:ASC-DHARD_Y_OUT16) as well, but it's not so obvious, so I segregated it.

(2) Along the bottom are the DC component of 1st / Inner loop ISS PDs (H1:PSL-ISS_PD[A/B]_CALI_DC_OUT16), these lag just a smidge (5-10 [sec]), but perfectly behind the IMC TRANS PD (H1:IMC-TRANS_OUT16). This PD is watching the same light the 2nd ISS array is watching, whose control signal is fed back to the -- you guessed it -- the error point of 1st loop of the ISS, whose actuator -- you guessed it -- is the AOM. The same AOM who's diffracted power we monitor for drift (which is why Betsy had it up). When you actuate on the diffracted power, you're directly changing the input power into the IFO. Not so stable at low frequency, this intensity stabilization loop...

(3) The cavity powers (PRC and ARM, as measured by H1:LSC-POP_A_LF_OUTPUT and H1:LSC-TR_[X/Y]_NORM_INMON, respectively), also show the same "oscillation" as the ISS Inner Loop PDs, but they're look like a mix between the IMC TRANS / ISS Inner Loop PDs's fluctuations (i.e. input power fluctions into the PRC) and the Tidal / DHARD Pitch fluctuations (i.e. arm power fluctuations because of inadvertent pitch from tidal control). Some times they follow one, other times they follow the other. I suspect this is why the POP_LF trace (shown up on the front wall in bright yellow, so very obvious) seems to show slow oscillation, with and even slower envelope.

I have a feeling that when you add a gain peaky-very-low-frequency blend filter into the equation (ETMX, when in the 45 [mHz] blends), it exacerbates the whole problem. (Note, I attach the correct configuration of the BSC ISIs's blend filters)

Hurumph! It seems like the source of all of these symptoms appears to be the IMC -- both tidal control and PRC input power fluctuations. Maybe we should take a serious look at the low-frequency performance of the IMC? My deepest darkest fear is that it all comes from the HAM3 0.6 [Hz] problems, but I think that's too fast this issue.

Anyways as I've claimed all along, I think at least these sets of traces convince me that this is a particularly complex interaction of *many* plants and anima*ahem* control loops. I think we might be at the point in LIGO's life time that we can't keep getting away with just assuming that everything below 100 [mHz] won't interact with each other, and I expect this will only get worse with higher power.

Since we'll shortly have the oppurtunity to play again, I suggest we try a few things and see if it helps:
(1) Change / improve the isolation configuration on HAM2/HAM3 
(2) Try improving the UIM L to P 
(3) Change the UGF of the DHARD loops
(4) Rejigger the ISS loop (or at least characterize it better) such that the low-frequency loop shape is different.

P.S. The template for this StripTool lives in 
/ligo/home/jeffrey.kissel/2016-01-03/PowerFluctionations.stp

Betsy's pulling up DTT on this, check for coherence, but just by looking at the time-series, I'd have a tough time mathematically proving that this is a linear coherence. We'll post if we get any clues there.
Images attached to this comment
betsy.weaver@LIGO.ORG - 22:02, Sunday 03 January 2016 (24668)

Note the coherence of many things with the HAM3 0.6Hz...  (spectra taken from this lock stretch).

Images attached to this comment
betsy.weaver@LIGO.ORG - 22:08, Sunday 03 January 2016 (24669)DetChar

Dear DETCHAR - Since we can't seem to get the data from 10 days ago in our own controlroom, can you please look into coherence with IFO channels during that time when the 0.6Hz SEI HAM3 peak wasn't around?

Thanks-

Betsy, Kissel

jeffrey.kissel@LIGO.ORG - 09:13, Monday 04 January 2016 (24676)CDS, IOO, ISC, PSL, SEI
Sad that I have to tag SEI on this... Perhaps in the O1/O2 interim we need a concerted campaign of replacing electronics in HAM3.
gabriele.vajente@LIGO.ORG - 09:16, Monday 04 January 2016 (24677)

The low frequency gain of the ISS should be large enough: in the normal configuration there is a low frequency boost and an integrator. However, in the past it was clear that the low frequency (below ~20 Hz) error signal was spolied by some additional noise, most likely scatetred light. Indeed, when the beam on the external table was not properly dumped, we saw a lot of increased noise due to back scattering.

So, it's also possible that the ISS loop has enough gain at low frequency, but the error signal is polluted by some scattered light, which might be correlated with the motion of some suspended object.

H1 General
travis.sadecki@LIGO.ORG - posted 18:56, Sunday 03 January 2016 (24664)
Observing at 2:50 UTC

Once the EQ band calmed back to normal levels, I did an initial alignment and brought us back to Observing at 2:50 UTC.  I adjusted the ALS fiber polarization for both arms while we were waiting for the EQ to ring down.

LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 18:16, Sunday 03 January 2016 (24663)
CP3 Manual Overfill @ 01:36 UTC

After notifying the operator I drove past the CS @ 01:31 and arrived at Y-Mid station @ 01:35.
Started filling CP3 @ 01:36, opened the exhaust check valve bypass valve, then opened LLCV bypass valve 1/2 turn, started to notice flow 29 seconds later. however I closed the LLCV bypass valve after allowing flow for a total of 2 minutes.
6 minutes later I closed the exhaust check valve bypass valve.

Started driving back from Y-Mid @ 01:47, arrived at the CS @ 01:52.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:00, Sunday 03 January 2016 (24662)
Ops Day Shift Summary
Activity Log: All Times in UTC (PT)

00:00 (16:00) Take over from TJ
18:02 (10:02) High temp alarm on CS Zone 4 duct. Temperature hovering around 100F. Will monitor 
23:24 (15:24) Lockloss – Mag 6.8 EQ in India.
23:38 (15:38) Put IFO in DOWN until EQ ring up passes
23:47 (15:47) Reset timing error on H1SUSETMY
00:00 (16:00) Turn over to Travis
 

End of Shift Summary:

Title:  01/03/2015, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)

Support:  Vinny, TVo  
 
Incoming Operator: Travis

Shift Detail Summary:   Mag 6.8 EQ in India, R-Wave 9.6um/s, seismic a little over 2.0um/s. Put IFO in DOWN until seismic settles down. Otherwise, it was a good observing shift.  

H1 General
jeffrey.bartlett@LIGO.ORG - posted 15:47, Sunday 03 January 2016 - last comment - 15:51, Sunday 03 January 2016(24660)
Lockloss - Earthquake
  23:24 (15:24) Lockloss due to mag 6.8 EQ in India. Seismic rung up to over 2.0um/s. 
Comments related to this report
jeffrey.bartlett@LIGO.ORG - 15:51, Sunday 03 January 2016 (24661)
Reset H1SUSETMY timing error.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 12:09, Sunday 03 January 2016 - last comment - 12:25, Sunday 03 January 2016(24658)
Ops Day Mid-Shift Summary
   IFO locked and observing for past 9 hours. Seismic and microseism are flat and mostly within normal range bounds. Microseism is near the top of the range bounds. Winds are up to a light breeze (up to 7mph), outside temps are 18F for all reporting stations. There have been several ETM-Y saturations, however the remains around 80Mpc.      
Comments related to this report
jeffrey.bartlett@LIGO.ORG - 12:25, Sunday 03 January 2016 (24659)
   It is currently snowing at the site, a dry light snow with about .25" accumulation. The roads and parking lot do not appear to be slippery. However visibility is somewhat limited. 
H1 CDS
david.barker@LIGO.ORG - posted 10:09, Sunday 03 January 2016 (24657)
backup machine cdsfs1 crashed again, was remotely rebooted via IPMI power cycle

Our cdsfs1 backup machine once again crashed, was not accessible via the network. I was able to remotely power cycle it via IPMI.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 09:48, Sunday 03 January 2016 (24656)
CDS model and DAQ restart report Saturday 2nd January 2016

O1 day 107

model restarts logged for Sat 02/Jan/2016 No restarts reported

H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:12, Sunday 03 January 2016 (24653)
Ops Day Shift Transition
  Transition Summary:
Title:  01/3/2016, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)
	
State of H1: 16:00 (08:00), The IOF has been in Observing mode for last 5.5 hours. Range and power are normal. Environmental conditions are good. There have been several saturations during the last shift. Will clear the timing error on H1SUSETMY (CPU max at 63uS) at the next out of Observing opportunity.  
 
Outgoing Operator: TJ

LHO General
thomas.shaffer@LIGO.ORG - posted 08:03, Sunday 03 January 2016 (24652)
Ops Owl Shift Summary
LHO General
thomas.shaffer@LIGO.ORG - posted 06:00, Sunday 03 January 2016 (24651)
Ops 3/4 Shift Report

Observing at 77Mpc for 3hrs.

Environment is calm, CW inj running, Timing error on H1SUSETMY

LHO General
thomas.shaffer@LIGO.ORG - posted 02:46, Sunday 03 January 2016 (24650)
Observing 10:41 UTC

I had to fiddle with ALS for a bit, run through an initial alignment, change the PZT sweep starting voltage in omcparams.py again to -30 (see alog24609 for the last time),and then lost it at DC_READOUT. But it came right back up after and we are back to observing!

LHO General (Lockloss)
thomas.shaffer@LIGO.ORG - posted 00:34, Sunday 03 January 2016 (24649)
Lockloss 8:16 UTC

When I arrived the IFO wasn't looking good, H1:LSC-POP_A_LF_OUTMON had been dropping in power since ~5UTC and the control signals were all over the place. The DARM spectrum wasnt looking good below 70Hz or so. EX ISI had a large amount of movement in it, but the dropping POP power and lack of useism doesn't explain our usual blends ringing up.  I decided to try changing the blends anyway, mainly because it was the only idea I had. This calmed the ASC slightly but a few minutes later AS90 started to dive and then lockloss.

This seemed to have happened a month ago (alog23941).

Images attached to this report
H1 AOS
betsy.weaver@LIGO.ORG - posted 00:19, Sunday 03 January 2016 (24648)
Reset the PMC SDF REF Voltage from yesterday finally

Now out of lock, we resumed the SDF monitoring of the PMC REF V channel, restored the original 1.34615V setting as per Jason, and accepted it in SDF.

H1 General
travis.sadecki@LIGO.ORG - posted 00:00, Sunday 03 January 2016 (24647)
OPS Eve Shift Summary

Title: 1/2 Eve Shift 0:00-8:00 UTC (16:00-24:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: Locked in Observing for my entire shift.  However, we have witnessed a brief drop in range and ringing up of ASC loops and tidal signals (see earlier aLog 24645) in the middle of the shift.  Towards the end of the shift, we have seen a drop in transmitted power via H1:LSC-POP_A_LF_OUTPUT (see attached screenshot) that is very reminiscent of a situation for which I was also the on-duty operator.  Perhaps is it coincidental, but this earlier instance of these issues occurred EXACTLY one month earlier (see aLog 23921 for related evidence of the tidal relation amd aLog 23941 for the analysis and comparative plot).  If Jenne's conclusion still holds true, sorry TJ!

Incoming operator: TJ

Activity log:

0:17 Betsy to optics lab

1:38 Betsy out

3:46 Ringing up of ASC loops is noticed and DIAG notification of tidal approaching its limit, range degrades ~15 MPc

4:04 ASC loops ring down and range returns to normal

Images attached to this report
H1 General (SEI)
travis.sadecki@LIGO.ORG - posted 20:20, Saturday 02 January 2016 - last comment - 20:25, Saturday 02 January 2016(24645)
Temporary drop in range related to tidal limits

We noticed that the range had dropped and the ASC loops had rung up.  Guardian DIAG was also notifying us that the tidal control was nearing its limits at both ETMx and ETMy.  While digging through the aLog for solutions (and finding only speculative fixes involving switching of ISI blends), things seemed to have calmed down and returned to normal.  However, plotting the TIDAL_CTRL signals for both X and Y shows that the control signal is much larger than we have seen in quite some time.  The first plot is a 2 day plot of the TIDAL_CTRL signal for both arms, and the second is a 30 day plot.

Images attached to this report
Comments related to this report
travis.sadecki@LIGO.ORG - 20:25, Saturday 02 January 2016 (24646)

We are not sure we understand why Guardian DIAG is throwing the 'within 10% of its limit' notification.  The control signal for both arms is ~300 while the limit for both arms is set to 700. 

H1 General (DetChar, PEM)
vincent.roma@LIGO.ORG - posted 14:38, Saturday 02 January 2016 - last comment - 09:06, Sunday 03 January 2016(24642)
Low Frequency Noise

Looking at the spectrograms and glitchgrams on the summary pages for January 2nd there seems to be some interesting behaviour from about 10 - 35 Hz at LHO.  The noise drops in this band over the course of the day and glitches in this band become less frequent as well.  It does not seem to correlate to wind speed or ground motion, at least not in an obvious way.  Looking at the ground motion BLRMS page of the summary pages, there do seem to be some spikes between 4 - 6 UTC, in multiple bands.  However these spikes are relatively short-lived and the noise in the spectrograms starts before that.  I've attached a few images showing noise and glitches from the band of interest..  The plots are also visible on the summary pages.

Images attached to this report
Comments related to this report
beverly.berger@LIGO.ORG - 09:06, Sunday 03 January 2016 (24655)DetChar, PSL

The last lock loss on 1 Jan was due to PSL issues (see alog). The low frequency noise reported here seems to be correlated with unusual noise in PSL ISS and also shows up in IMC frequency noise. The attached pdf shows apparently normal behavior on 1 Jan for PSL ISS, IMC frequency noise, and strain followed by excess noise in all three on 2 Jan. While things appear to have calmed down on 3 Jan (so far), there appears to be a PSL glitch that shows up in the strain channel.

Non-image files attached to this comment
H1 AOS (DetChar, ISC)
joshua.smith@LIGO.ORG - posted 12:11, Friday 01 January 2016 - last comment - 08:39, Sunday 03 January 2016(24611)
RF Beats / Whistles seen at H1 on December 31

Happy New Year all!

H1 has historically not has as bad of RF beat / whistle problems as L1 has. In fact, the last alog report is for data on October 30th. But dec 31st shows a high density of glitches above 100Hz and densest above 500Hz, which have the signature shape of RF beats we've seen before and are correlated with PRCL and SRCL, similar to one of the manifestations of whistles seen at LLO

Note 1: we produce auto omega scans for the loudest glitches that hveto finds, and these whistles are all very quiet. If anyone wants to follow these up in more detail, you can get GPS times for the high-frequency low-snr triggers for Dec 31 correlations with PRCL and SRCL at those links. 

Note 2: Dec 31 looks like the worst day, but there might have been some weak whistles occuring on other days too, but we'd have to follow up some low SNR triggers on those days (e.g. today Jan 1 and the past few days).

Images attached to this report
Comments related to this report
joshua.smith@LIGO.ORG - 08:39, Sunday 03 January 2016 (24654)DetChar, ISC

Quick update: RF beat / whistles are still happening today, Jan 3. The hveto page shows whistles in rounds 4 and 8 coincident this time with H1:ASC-REFL_B_RF45_Q_PIT_OUT_DQ (and not PRCL and SRCL as above, so a different line/VCO freq must be at play). They are still low SNR, but lightly visible in omega scans. Some example omega scans are attached and linked here. Text files of glitches coincident with ASC REFL B RF45 are here for round 4 and round 8

https://ldas-jobs.ligo-wa.caltech.edu/~hveto/daily/201601/20160103/H1-omicron_BOTH-1135814417-28800-DARM/wscans_rd8/
 
​[8:34] 
note, not showing in PRCL or SRCL
Images attached to this comment
Displaying reports 61881-61900 of 85905.Go to page Start 3091 3092 3093 3094 3095 3096 3097 3098 3099 End