Displaying reports 59021-59040 of 83069.Go to page Start 2948 2949 2950 2951 2952 2953 2954 2955 2956 End
Reports until 15:14, Monday 04 January 2016
H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 15:14, Monday 04 January 2016 (24689)
PSL Weekly Status
PSL Status: 
SysStat: All Green, except VB program offline & LRA out of range 
Output power: 30.4w  
Frontend Watch: Green
HPO Watch: Red

PMC:
Locked: 2 days, 22 hours, 52 minutes
Reflected power:    1.6w
Transmitted power: 22.9w 
Total Power:       24.5w 

ISS:
Diffracted power: 8.32%
Last saturation event: 0 days, 1 hours, 11 minutes 

FSS:
Locked: 0 days, 1 hours, 56 minutes
Trans PD: 1.317v
H1 DetChar (DetChar)
beverly.berger@LIGO.ORG - posted 14:57, Monday 04 January 2016 (24688)
DQ Shift for 31 December 2015 - 3 January 2016

Complete results from this DQ shift may be found here.

 

 

 

 

 

 


H1 General
jeffrey.bartlett@LIGO.ORG - posted 14:29, Monday 04 January 2016 - last comment - 16:15, Monday 04 January 2016(24687)
Lockloss - Due to POP_A_LF Drop
   Lost lock at 20:50 (12:50) due to the drop in power in POP_A_LF. Did an initial alignment and was able to relock the IFO on the first try. Back in Observing with 21.7W and 78Mpc. 

   The POP_A_LF signal is still a bit ragged and is just above the IMC-MC2_TRANS signal. 
Comments related to this report
vincent.roma@LIGO.ORG - 16:15, Monday 04 January 2016 (24693)

I'm not sure what the significance of this is, or if there is any, but I looked at the pitch and yaw signals for the various optics for today's locklosses, it seems like the ITMY optical lever pitch has behaved similarly to the H1:LSC-POP_A_LF_OUT signal, which is believed to be responsible for our recent locklosses.  I've attached two images, one for each lock today.  There are many plots shown for the various pitch and yaw signals.  The plots in the top right and bottom right are the ones I was interested in.

Images attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 12:15, Monday 04 January 2016 (24686)
Ops Day Mid-Shift Summary
   The IFO remains up and in Observing. Environmental and seismic conditions are favorable. The POP_A_LF_Output continues to be an issue. There was an attempt to tweak PR2 to bring this back up. Some gain on the problem was made but that has faded away. Range continues to suffer (mid 70s to high 60Mpc). Will hope the lock holds.   
H1 General
jeffrey.bartlett@LIGO.ORG - posted 11:04, Monday 04 January 2016 (24685)
Out of Observing for POP_A_LF
   17:55 (09:55) took the IFO to Commissioning mode so Sheila & Jenne could try to improve the power decline apparent in the LSC-POP_A_LF_Output signal. After tweaking PR2 pitch & Yaw, POP_A_LF looks a little better but is still a concern. The investigation into the problem continues. 

   18:52 (10:52) - Put the IFO back into Observing mode. 
H1 CAL (CDS, ISC)
jeffrey.kissel@LIGO.ORG - posted 09:52, Monday 04 January 2016 (24683)
Schedule of Activity for CAL Week at LHO
J. Kissel, for the CAL Team

I attach a picture of the whiteboard which shows the strawman schedule of activity during calibration week (Jan 5 to Jan 12). This list contains everything mentioned on the End-Of-Run measurement page of the JRPC Wiki that is relevant for LHO, but just organized into a rough schedule. Wish us luck!

P.S. These measurements are covered by WP 5674.
Images attached to this report
H1 PSL
jason.oberling@LIGO.ORG - posted 09:41, Monday 04 January 2016 (24682)
FSS RevCav TPD Since Adjustment

Attached are 2 trends of the FSS RefCav TPD.  The first is a 14 day trend showing the last decay up until the 1-1-2016 lockloss and the subsequent RefCav adjustment.  The second is a 3 day trend detailing what the RefCav TPD has done since we adjusted it on 1-1-2016.  Since the adjustment the TPD has fallen by ~0.2 V to 1.31 V, but has appeared to level out there over the last 24 hours.  As it stands now no adjustment is necessary; 1.31 V on the TPD indicates that there is plenty of light for the ALS system to function correctly (danger zone is ~0.9 V on the TPD).  I will continue to monitor as this could change (but hopefully won't).

Images attached to this report
H1 AOS (ISC, SEI, SUS)
jason.oberling@LIGO.ORG - posted 09:29, Monday 04 January 2016 - last comment - 15:20, Thursday 07 January 2016(24680)
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
Comments related to this report
jason.oberling@LIGO.ORG - 10:16, Monday 04 January 2016 (24684)

Centering:

  • SR3 Pitch and ITMy Pitch & Yaw are both near their respective linear limits so they need to be recentered.  This will be done during the 1-5-2016 maintenance period.
  • All other oplevs OK.

Glitching (via DetChar summary pages):

  • No real change from my last alog on this for all oplevs except BS and SR3.  Priority remains getting stabilized lasers into the ITMx and ITMy oplevs, then addressing glitching lasers that aren't used in damping loops.
    • BS: Has cleared up since the last power adjustment.  Will keep an eye on it, but for now I'm calling this one good to go.
    • SR3: Still glitching, with the occaisional bad glitch.  Looks like this laser might need to be replaced; will leave it for now and return once ITMx and ITMy are complete.
jason.oberling@LIGO.ORG - 15:20, Thursday 07 January 2016 (24751)ISC, SUS

Update on the BS oplev.  Appears the cessation of glitching was only temporary, as the last couple of days have seen the laser go wild.  Will attempt a power adjustment during the next maintenance period (as discussed here).  If that is unsuccessful then I will swap back in the now re-stabilized laser SN 130-1 (that I just recently removed from this oplev and found to be functioning normally, just in need a slight tweak to it's TEC setpoint).

H1 SEI
hugh.radkins@LIGO.ORG - posted 09:23, Monday 04 January 2016 (24678)
LHO SEI Sensor Correction Seismometers--All need Centering

This may be a rehash but WP review reminded me.  Re WP 5618

The attached 30 day trends of the three Ground STS2's Mass position shows that they are all out of spec.  The values for these should be something smaller than 5000 counts or 1.5 or 2 volts.  If it can be managed during Tuesday Maintenance without interfering with calibration or other work, I'd like to again try recentering these.  Much easier now given the remote capability.

Images attached to this report
H1 General
jeffrey.bartlett@LIGO.ORG - posted 09:21, Monday 04 January 2016 (24679)
08:30 Meeting Minutes
   No reports from the various groups as all are getting back up to speed after the year end holiday break. 

Planned Tuesday Maintenance: 
(1). Jeff B. - Run dust monitor vacuum plumbing at End-X
(2). Jeff K. - Run End-X calibration
(3). Jeff K. - End-X UIM electronics investigation
(4). Richard - Survey of on site cameras

   Starting after the 01/05/16 Tuesday maintenance, the remaining day shifts (08:00 16:00) during the week will be given to the calibration group. These calibration activities may go beyond 16:00. 

   Starting Thursday 01/07/16 there will commence a regular 08:30 meeting in the control room to review FRS tickets and to plan for the various activities around the site. This will be similar to the Monday meeting but will concentrate on FRS items not work permits.         
H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:24, Monday 04 January 2016 (24675)
Ops Day Shift Transition
  Transition Summary:
Title:  01/4/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 3 hours. Range is 74Mpc and power is at 21.8W. Environmental conditions are good. As Jim reported, the slow degradation of power via POP_A_LF may foretell of a lock loss. Will keep an eye on it. 
 
Outgoing Operator: Jim
H1 General
jim.warner@LIGO.ORG - posted 07:50, Monday 04 January 2016 (24674)
Shift Summary

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

State of H1: Observing

Shift Summary:  Started the shift with an unlocked IFO due to EQ.  After EQ ringdown, aligned and locked IFO.  Since going to Observing, we have been watching the slow degradation of power via POP_A_LF, much like last EVE.  At one point we attempted to reverse the trend by adjusting ETMy pitch, but were thwarted by WFS control loops.

Activity log:

11:30 Lockloss probably from whatever is causing POP to drift down

13:15 Back to observing, shortly thereafte I notice that POP is once again drifting down. No clear cause, environment is quiet, RF45 seems to be behaving, ASC foms etc all look nominal.

14:45 Bubba starts clearing the parking lot. This has a noticeable effect on the IFO.

H1 General (DetChar)
jim.warner@LIGO.ORG - posted 07:18, Monday 04 January 2016 (24673)
Parking lot plowing has an effect on IFO

Starting at about 14:30, Bubba started cleaning the parking lot. He started with shoveling, which had no effect. He's now running the tractor near the OSB and it's having some effect on the IFO. The range has gotten pretty ratty and POP (which is still trending down after re-locking 2 hours ago) is occasionally getting knocked around. Think we'll survive, but analysis people should be aware when looking at this mornings data.

H1 General
jim.warner@LIGO.ORG - posted 03:50, Monday 04 January 2016 (24672)
Mid Shift Summary

Can't say I'm suprised, but we just lost lock. The hours long decline in POP had looked like it was stabilizing. Apparently not. Time to see how re-locking goes.

H1 General
travis.sadecki@LIGO.ORG - posted 00:00, Monday 04 January 2016 (24671)
OPS Eve Shift Summary

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

State of H1: Observing

Shift Summary:  Started the shift with an unlocked IFO due to EQ.  After EQ ringdown, aligned and locked IFO.  Since going to Observing, we have been watching the slow degradation of power via POP_A_LF, much like last EVE.  At one point we attempted to reverse the trend by adjusting ETMy pitch, but were thwarted by WFS control loops.

Incoming operator: Jim

Activity log:

0:33 Vinny +1 to LVEA and Betsy to Optics Lab

1:08 Vinny +1 out

1:22 Adjusted ALS fiber polarization for both X and Y

1:27 Switched ETMx ISI X blend to 90 to stop an oscillation and began initial alignment

1:29 Gerardo to CP3

1:30 Betsy out

1:46 Betsy to LVEA for cables

1:56 Gerardo done

2:00 Betsy out

2:50 Observing

6:28 Commissioning mode to adjust ETMy pitch in attempt to save lock

6:40 Back to Observe

7:16 H1:FMC-CS_LVEA_REHEAT_4_DEGF alarm

H1 General
travis.sadecki@LIGO.ORG - posted 23:00, Sunday 03 January 2016 (24670)
Briefly out of Observing 6:28-6:40 UTC

We are once again experiencing the slow degradation of power as we saw during my shift yesterday.  At Kissel and Betsy's suggestion, we briefly went out of Observing in order to attempt to save the lock as we are approaching the "point-of-no-return".  I adjusted ETMy in pitch since Betsy found a correlation between ETMy drifting down in pitch and the POP power dropping.  This worked temporarily, until the WFS caught wind of my treason and fought back.  We decided to surrender and let it play out. 

H1 SUS
betsy.weaver@LIGO.ORG - posted 21:59, Sunday 03 January 2016 - last comment - 09:33, Monday 04 January 2016(24667)
SUS ETMy Vertical drift

The ETMy has been slowly sagging over the last few months.  Recently, the sag rate has increased.  While the temperature control at EY appears to be noisier during this December's cold spell, the overall temp has not changed by a large (greater than a deg C) amount, so I doubt that is the full cause of the drift.  However, there have been a few pressure changes that the ETMy chamber has witnessed, according to the VE pressure channels I picked off and plotted (attached).  I can't correlate all of the vertical motion humps exactly to these pressure steps, but the direction is correct: lower pressure means a a lower QUAD - that said, the sag usually happens much faster than weeks when the pressure or temp is changed, so wt-heck?.  The most recent step in pressure shown on the plot was Dec 11th when the VE crew was doing some work on an IP bakeout at Y2-8.  I'll poke them to see what the nature of the pressure step is.  I worry a bit that there is something wrong with the channel after the step feature since it goes very quiet past that point.

The corresponding ETMy pitch motion change is much more subtle, which is good from an alignment standpoint.  The BOSEMs still have plenty of signal, so we shouldn't have any issues with drive due to this drift.

 

Another day, another mystery.  Keep H1 weird.

Images attached to this report
Comments related to this report
brett.shapiro@LIGO.ORG - 09:33, Monday 04 January 2016 (24681)

This pressure change is too small to account for the vetical drift. In log 15887, ETMY is measured to sag by 120 microns during pumpdown, a pressure change of 760 torr. For a pressure change on the order of 1e-8 torr, as seen here, you would therefore expect a vertical change of 

 

(1e-8 / 760) * 120 microns = 1.6e-9 mincrons or 1.6e-15 meters. This is well into the noise of the OSEMs.

 

I think it is more likely the in-vacuum temperature is different from the VEA temperature sensor. Are the any in-chamber temperature sensors on the ISI table?

A consistency check you can do is see if it is just the suspension, or really a change in the whole chamber is to see if the ISI is sagging as well; or rather trying to sag since it has active position control. So, if the vertical ISI actuators are pushing up harder proportional to how much the quad is sagging, then there is at least some consistency throughout the chamber.

Since the suspension pitch isn't changing (which is great) that suggests that either the suspension is super well balanced, or it is just the top springs at the ISI table that are sagging. The temperature of these springs likely follows the temperature of the ISI much more closely than the ones lower down.

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.

Displaying reports 59021-59040 of 83069.Go to page Start 2948 2949 2950 2951 2952 2953 2954 2955 2956 End