Displaying reports 56821-56840 of 83294.Go to page Start 2838 2839 2840 2841 2842 2843 2844 2845 2846 End
Reports until 08:24, Monday 16 May 2016
H1 General
edmond.merilh@LIGO.ORG - posted 08:24, Monday 16 May 2016 (27206)
Shift Summary - Day Transition
TITLE: 05/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 0.0Mpc
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 1mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:
TITLE: 05/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 0.0Mpc
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 1mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:
 
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 07:10, Monday 16 May 2016 - last comment - 08:10, Monday 16 May 2016(27204)
laser status
The laser was off this morning.  The chiller indicated that there was a "Flow sensor 1" error.
Comments related to this report
peter.king@LIGO.ORG - 08:10, Monday 16 May 2016 (27205)
Looking at the data from the various flow sensors, maybe, just maybe, the problem is with the flow sensor attached
to the auxiliary circuit (which monitors flows to the power meters ...).  The attached plot seems to imply that the
flow to the power meters dropped before the crystal chiller flow declined.

    Would need to check that the power meters are really attached to this part of the cooling circuit because the
diode chiller was running this morning.

For reference the cooling system information is under
https://dcc.ligo.org/DocDB/0067/T1100373/002/LIGO-T1100373-v2%20Coolant%20system%20operating%20and%20maintenance%20manual.pdf
Images attached to this comment
H1 PSL
robert.schofield@LIGO.ORG - posted 16:59, Sunday 15 May 2016 (27203)
Shaker mounted on PSL table

While the laser was down I mounted a B&K voice coil shaker on the +X, +Y corner of the table to study the PSL jitter contribution to DARM noise in the 80-200 Hz region. I doubt it will affect alighnment but be aware since it is quite heavy.

H1 DetChar (DetChar, PEM)
brynley.pearlstone@LIGO.ORG - posted 15:21, Sunday 15 May 2016 - last comment - 08:57, Wednesday 18 May 2016(27202)
Possible new comb in H1, and persistent 0.5Hz comb

BP

Following Friday night's lock, I looked at the spectrum and saw some regular structure, looking like a 2Hz comb at odd frequencies.This looks like a new comb. [figs 1&2]

As followe up, I ran coherence with all of the EBAY magnetometers and saw strong coherence is some places with this 2Hz comb, as well as the persisting 0.5Hz comb (see plots below)

0.5Hz comb: https://ldas-jobs.ligo.caltech.edu/~brynley.pearlstone/comb_investigations/May_2016_comb/H1:PEM-EX_MAG_EBAY_SEIRACK_Z_DQ_25_40Hz.png

0.5Hz comb + 2Hz comb: https://ldas-jobs.ligo.caltech.edu/~brynley.pearlstone/comb_investigations/May_2016_comb/H1:PEM-EX_MAG_EBAY_SEIRACK_X_DQ_25_40Hz.png

Note: These two are the same magnetometer (MAG_EBAY_SEIRACK), looking at 2 different axes. Both combs were also seen in other magnetometers.

Full list of plots: https://ldas-jobs.ligo.caltech.edu/~brynley.pearlstone/comb_investigations/May_2016_comb/

Previous efforts to mitigate the 0.5Hz comb was focussed on powering the timing card independently in the CS EBAY LSC-C! I/O chassis which handles DARM. This has not worked to eliminate the comb. I can't report any reduction yet, as Friday's lock was not sensitive at low (<100Hz) frequencies.

This 2Hz comb on 1Hz offset is the transform of a 1Hz square wave. The 2Hz comb might have to do with the 0.5s and 1s structure seen it Keith's data folding studies here: https://alog.ligo-wa.caltech.edu/aLOG/index.php

Images attached to this report
Comments related to this report
brynley.pearlstone@LIGO.ORG - 08:57, Wednesday 18 May 2016 (27270)

Looking at the strain sensitivity of this lock vs a typical O1 lock there is no way to tell whether the combs are reduced in the strain. It is clear that these new 2Hz combs aren't going to be quiet.

Images attached to this comment
H1 ISC (ISC, PSL)
sheila.dwyer@LIGO.ORG - posted 21:38, Saturday 14 May 2016 - last comment - 13:49, Sunday 15 May 2016(27199)
30 Watts for 5 minutes

Evan, Sheila

Today we blended CHARD P, with the same blend filters Craig and I used last night for yaw. This went smoothly and the attached screenshot shows the settings, which are accepted in SDF and shouldn't need to be in the guardian since they don't need to change.  WE haven't made it to low noise to see what kind of improvement this gives us.

We also had a look at dithering SRM and demodulating DARM control to get an alignment signal for SRM.  The SNR was not good for a 4Hz or 9 Hz dither, but for a 15 Hz dither there is clearly a signal, although the lock point was not good. I've added filters we could try to supress the length coupling in MICH2, SRCL2, PRCL2 filter banks, but we didn't get a chance to try this again.

Evan noticed that there is an instability in CHARD P at 0.2Hz when we tried to power up past 20 Watts or so last night, so we redisgned the boost that comes on at 17Watts to be gentler and have higher frequency zeros, (the new filter is MSBoost2 and in FM1).  With this we seems to be stable at 30Watts, at least for 5 minutes (we broke lock by trying to go to 35W). 

We had a bit of trouble with the laser today, nothing that can't be fixed easily ( noise eater and ISS oscialltions, difficulty locking the FSS).  Evan changed the temp search ramp parameters for the FSS. 

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 13:49, Sunday 15 May 2016 (27201)

Also, we had to reduce the analog gain of the TMS QPDs even further in order to avoid saturation on some of the segments when going above 25 W. We used to set the gain to 9 dB once we achieved resonance; now we reduce it to 3 dB.

This is a problem that is better solved by picomotoring the TMS beams. The worst offender seems to be the Y-arm B diode; it has a factor of something like 40 in power between segments 2 and 4.

H1 AOS (SEI, SUS)
cheryl.vorvick@LIGO.ORG - posted 02:09, Saturday 14 May 2016 (27196)
Optical Lever 7 Day Trends

Attached are 7 day pitch, yaw, and sum trends for all active H1 optical levers.

Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 01:48, Saturday 14 May 2016 (27195)
Ops Eve Summary:

State of H1: locked in Low Noise, with 68.4Mpc

Activities:

H1 ISC
sheila.dwyer@LIGO.ORG - posted 23:37, Friday 13 May 2016 - last comment - 23:38, Friday 13 May 2016(27192)
back to almost low noise

Sheila, Craig, Cheryl

Tonight we are stable at 25 Watts, without the ISS 3rd loop on and no SRM control.  The range is just below 70 Mpc, and the spectrum seems non stationary with lots of loud glitches which aren't due to anything much that we have been doing.  

There is a broad peak around 60Hz, which is not something I've seen before, Craig found there is coherence with LSC signals there.  As expected we have a lot of noise from CHARD below 30 Hz.  We decided to try blending with the transmon QPDs.  We started with a simple blend, two poles at 4 Hz for the refl WFS and a complimentary filter for the QPDs.  This reduced the noise (and the coherence) but we still need to improve this a bit, probably with a .  We simply used the combination of TMS QPDs that is orthogonal to what we are using for the soft loops, so we might be able to find a combination that has better SNR for CHARD than what we are currently using.  Once the coherence with CHARD yaw was reduced we have more coherence with pit, so blending this will probably be one of our next jobs.  The current settings are in the screenshot.

The IFO has been basically undisturbed since 6:05 UTC, but we aren't easily able to hit the intent button, maybe because of old excitations...  

Images attached to this report
Comments related to this report
craig.cahillane@LIGO.ORG - 23:38, Friday 13 May 2016 (27193)ISC
S. Dwyer, C. Cahillane

We took a reference spectrum before turning on the blending of the CHARD Y error signal and after. (Plot 1)  You can see where we win at about 20 Hz.
Now that we have damped CHARD yaw noise at low frequency, we have CHARD pitch noise...  

Also, Plot 2 shows coherence between MICH, PRCL, and SRCL to DARM, particularly around 60 Hz.  
Images attached to this comment
H1 ISC (IOO, PSL)
kiwamu.izumi@LIGO.ORG - posted 20:40, Friday 13 May 2016 - last comment - 13:37, Sunday 15 May 2016(27190)
ISS third loop closed

Evan, Kiwamu,

In this afternoon, we closed the ISS third loop which are meant to damp the arm power fluctuation.

We confirmed that it suppressed the common arm power fluctuation at around 0.5 Hz by 10 dB nominally. We tested this loop at various PSL power from 2 to 25 W. Further sophistication of the loop shape can be done if necessary.

 


[nominal settings]

[injection point changed]

The original plan was to inject the third loop signal to either TRANSFER1 or 2 input. However it turned out that they have seem to have a factor of 10 attenuation, we ran into a range issue where the DAC output and SR560 (which is meant as a dewthitening filter) saturated before getting to the nominal servo gain. We instead moved the injection point to the one for the second loop by disconnecting the second loop and plugging the third loop cable.

Also, there is a low-pass-ish response somewhere in the second loop injection path which let us put a lead filter in FM3.

[Instability at 25 W]

With a 25 W PSL, we see an instability that occured at 0.24 Hz. Similarly to the usual arm power instability at 0.4 - 0.5 Hz, it modulated the arm power, but the frequency seems to be a bit low and it coupled to the HARD mode. This instability seems to happen regardless of whether the third loop is closed or not. A possible source might be an unstable ASC loop. Currently  under investigation.

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 13:37, Sunday 15 May 2016 (27200)

The third loop signal now goes through an SR560 with an inversion, so the gain should now be +0.04 in the filter module.

H1 FMP
bubba.gateley@LIGO.ORG - posted 18:18, Friday 13 May 2016 - last comment - 19:30, Friday 13 May 2016(27187)
Chilled water pump at End Y tripped
I just received a call from Cheryl in the control room saying the chilled water pump at EY was in alarm. I looked at the screen and chilled water pump #1 had tripped. I started pump 2.
Comments related to this report
bubba.gateley@LIGO.ORG - 19:17, Friday 13 May 2016 (27188)
Chilled water pump 2 did not appear to allow the chiller to start so I cleared the fault on pump 1 and restarted pump 1. The water temperature is now falling. I will continue to monitor.
cheryl.vorvick@LIGO.ORG - 19:30, Friday 13 May 2016 (27189)

00:51:52UTC - pump 1 shuts off, temperatures climb

01:13:24UTC - pump 2 turned on, temperatures take a small dip, but continue to climb

02:03:32UTC - pump 1 turned on again, temperatures for chilled water start to fall

02:15:35UTC - EY VEA temperature starts to fall, after reaching a peak of 69.5F, from an average of 68F

02:27:15UTC - EY VEA temperature reaches 68.1F, and chilled water supply/return have leveled out at 43F/48FF

LHO VE
chandra.romel@LIGO.ORG - posted 14:20, Friday 13 May 2016 - last comment - 17:49, Friday 13 May 2016(27182)
CP 5 & 6 PIDs
Richard changed PID settings on CP 5 & 6 today. Current settings:

CP5
Gain: 7
Integral: 460
Set Pt: 90

CP6
Gain: 6
Integral: 360
Set Pt: 88

Set points are set lower than nominal 92% so PID experiments can continue Monday.
Comments related to this report
chandra.romel@LIGO.ORG - 17:49, Friday 13 May 2016 (27186)
Liquid levels of CP 5 & 6 have settled to the set points.
Images attached to this comment
LHO VE
chandra.romel@LIGO.ORG - posted 14:15, Friday 13 May 2016 - last comment - 09:22, Monday 16 May 2016(27181)
CP3 overfill
1:30pm local

1/2 turn open on LLCV bypass --> took 33:17 min. to overfill CP3. 

Raised LLCV from 20% to 21%.
Comments related to this report
chandra.romel@LIGO.ORG - 09:22, Monday 16 May 2016 (27211)
Temp induced
Images attached to this comment
chandra.romel@LIGO.ORG - 08:05, Saturday 14 May 2016 (27197)
CP3 Dewar is being filled this Tuesday so LLCV may need to be lowered again.
H1 SUS
sheila.dwyer@LIGO.ORG - posted 00:16, Friday 13 May 2016 - last comment - 15:45, Monday 16 May 2016(27158)
coil driver switching causing locklosses

It looks like we need to do something about the triple coil drivers that we switch in lock, especially PRM M3.  We have lost lock a good fraction of the times that we have tried to switch in the last month or so.  Screenshot is attached, I also filed an FRS ticket hoping that someone might make an attempt to tune the delays while people are in the PSL tomorrow morning.  FRS ticket #5489 

Images attached to this report
Comments related to this report
rana.adhikari@LIGO.ORG - 12:17, Friday 13 May 2016 (27178)ISC, Lockloss

Is the DAC spectrum post-switch using up a large fraction of the range? If the noise in the PRC loop has change a little bit it could make this transition less risky.

sheila.dwyer@LIGO.ORG - 12:25, Saturday 14 May 2016 (27198)

Here's the PRM drive from last night's lock, in which we just skipped the PRM M3 BIO switching leaving the low pass off (BIO state 1). It seems like we should have plenty of room to turn the low pass on without saturating the DAQ.  

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 15:45, Monday 16 May 2016 (27226)
FRS Ticket #5489 closed in favor of a long-term fix Integration Issue #5506 (which is now also in the FRS system) and for an eventual ECR. Work permit #5880 indicates we'll install the fix tomorrow. See LHO aLOG 27223.
H1 CAL (CAL)
craig.cahillane@LIGO.ORG - posted 18:47, Thursday 12 May 2016 - last comment - 16:49, Friday 13 May 2016(27154)
Calibration Kappa Covariance Triangle Plots
C. Cahillane

I have generated corner plots of the time-dependent kappas to check their covariance.

There are six kappa values: 
1) Kappa_tst Mag
2) Kappa_tst Phase [Rads]
3) Kappa_pu Mag
4) Kappa_pu Phase [Rads]
5) Kappa_C
6) Cavity Pole F_CC

We do get some values of covariance that are comparable with variance... However, all values, including variance, are sub-percent.  
I anticipate that if propagated into the uncertainty budget, all covariant terms would be negligible.  We cannot be sure, however, without doing the work.

For the LLO Kappa Triangle Plots, please see LLO aLOG 26134
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 16:49, Friday 13 May 2016 (27184)
J. Kissel, C. Cahillane

A couple of notes from a discussion between Craig and I about these results:
(1) The "Var" and "Covar" results reported on the plots are actually the square root of the respective element in the covariance matrix, multiplied by the sign of the element. Thus the reported "Var" and "Covar" value is directly comparable to the uncertainty typically reported, but the off-diagonal elements retain the sign information of the covariance.

(2) Lest ye be confused -- the (co)variances (which are actually uncertainty values) are report at the *top* of each sub-plot, and the upper most variance value (for |k_TST|) is cut off. The value is 0.00234.

(3) In order to compute the statistical uncertainty of these time-dependent systematic errors for the C02 uncertainty, Craig computed a running median (where the width of the median range was 50, once-a-minute data points; +/- 25 points surrounding the given time's data point) over the entire O1 time series, subtracted that median from every given data point, and took the standard deviation of residual time-series assuming that what remains is representative of the Guassian noise on the measurement. See original results in LHO aLOG 26580, though that log reports a range of 100 (+/- 50) once-a-minute points which has since been changed to the above-mentioned +/- 25 points for a more physical time-scale (but only changes the results at the 5% of the reported already ~0.3-0.5% uncertainty, i.e. the reported relative uncertainty of 0.002 change by 0.00005).

For these plots, where he went a step further and computed the full covariance matrix on all time-dependent factors in order to address the question "is there any covariance between the statistical uncertainties, given that they're computed using -- in some cases -- the same calibration line?"). In doing so, he'd first taken the exact same median-removed time-series for each time-dependent factor, but found that the data set (i.e. the 2D and 1D histograms) was artificially biased around zero. We know now this was because, often, the median *was* the given time's value and residual was zero. Thus, instead, he recomputed the running median, disallowing the given time's value to be used in the median calculation. Graphically,

    x   x x     x         x           x  x 
      x    x x    x   x      x x  x    x   x
         x     x x      x  x     x  x      x x 
        [------------\_/-------------]
  x   Raw data      
 \_/  Given time's central value to which a median will be assigned and subtracted.  
[---] Median Window

As one can see in his attached plots, that successfully de-biases the histogram.


(4) The following time-dependent systematic error uncertainties *are* indeed covariant:
    (a) kappa_TST with kappa_PU (in magnitude and phase) -- the actuation strength of the PUM and TST mass stages.
    (b) kappa_C with f_cc -- the IFO optical gain and cavity pole frequency

    We know and expect (b), as has been shown in Evan's note T1500533. What's more is that it's *negatively covariant, so what estimation of the uncertainty we have thus far been making -- ignoring the covariant terms -- is actually an over estimate, and all is "OK."

    We also expect (a), because of how the two terms are calculated (see T1500377) and because they're also calculated from the same pair of lines. Sadly, we see that sqrt(covariance) is *positive* and of comparable amplitude to the sqrt(variance). But -- said at little more strongly than Craig suggests -- for these terms that have positive covariance comparable to the variance, the absolute value of both variance and covariance corresponds to an uncertainty (i.e. sqrt(variance)) on the 0.3-0.5% level, which is much smaller than other dominant terms in the uncertainty, as can be seen for example in pgs 3 and 4 of the attachment "05-Jan-2016_LHO_Strain_Uncertainty_C03_All_Plots.pdf" in LHO aLOG 24709. 

As such, we deem it sufficient to continue to ignore all covariant terms in the statistical uncertainty of these time-dependent parameters because they're either negative or, where positive, contribute a negligible amount to the overall statistical uncertainty budget compared with other, static statistical uncertainty terms.


     
Displaying reports 56821-56840 of 83294.Go to page Start 2838 2839 2840 2841 2842 2843 2844 2845 2846 End