Displaying reports 55721-55740 of 84557.Go to page Start 2783 2784 2785 2786 2787 2788 2789 2790 2791 End
Reports until 20:26, Monday 12 September 2016
H1 SYS (GRD)
jameson.rollins@LIGO.ORG - posted 20:26, Monday 12 September 2016 - last comment - 11:31, Tuesday 13 September 2016(29640)
Restarted DIAG_MAIN node to bypass broken PEM EY wind sensor

Apparently the PEM EY wind sensor EPICS IOC is malfunctioning causing the H1:PEM-EY_WIND_ROOF_WEATHER_MPH channel to be dead.  This channel is checked in one of the DIAG_MAIN PEM tests, so the dead channel was causing DIAG_MAIN to go into a connection error state, thereby not executing any of the diagnostic tests.

I temporarily bypassed the test with the faulty channel, replacing it with a notification that the sensor channel is dead.  This change should be reverted once the channel is restored.

 

While I was at it, I did a little maintenance on DIAG_MAIN:

Comments related to this report
thomas.shaffer@LIGO.ORG - 11:31, Tuesday 13 September 2016 (29656)GRD

Revomed the PEM_WIND test. After talking with Dave it doesnt seem too useful when we have other tools in the control room to show wind. Plus the connections to the weather stations seem to be unreliable and we dont want to stop the DIAG_MAIN from showing notificaitons just because of a connection error at a weather station, especially in an observing run.

H1 AOS
sheila.dwyer@LIGO.ORG - posted 20:16, Monday 12 September 2016 - last comment - 00:54, Tuesday 13 September 2016(29638)
CARM gain too high

Jenne, Evan, Sheila

Since Saturday (after RH settings were changed and we recovered from the power outage) we have been having sudden locklosses in the Analog CARM transition and the next few states.  We measured the CARM open loop this afternoon and saw that the gain was too high leaving us with too little phase margin (blue trace in screenshot).  We reduced the gain in the common mode summing junction by 8 dB (from 16dB to 8dB), green trace in the attachment.  Both measurements in the attachment were taken at DC readout. 

Evan's model of the CARM loop can be found at 22188

Images attached to this report
Non-image files attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 00:54, Tuesday 13 September 2016 (29647)

Since lowering this gain we haven't had any more of the locklosses shortly after switching to analog carm. 

H1 SEI (DetChar)
sheila.dwyer@LIGO.ORG - posted 19:53, Monday 12 September 2016 - last comment - 00:39, Tuesday 13 September 2016(29639)
BS ISI trip

We lost lock a few minutes ago with a BS ISI trip (COIL DRIVER chassis BIO)  We aren't sure what that is but everything looks fine on the CDS overview.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 21:00, Monday 12 September 2016 (29641)

This trip has just happened again.  But, this time we aren't able to fix it.  Sheila went to the CER to look, and all the lights on the coil driver chassis are green.  No overtemps are on, and fuse status is green.  We're calling Hugh right now, but if anyone sees this and knows how to fix it, please give the control room a call.

jameson.rollins@LIGO.ORG - 23:40, Monday 12 September 2016 (29642)

We tracked down the BS ISI trip to a single bit flip in the h1seib2 DIO_0 card, corresponding to the BS ISI ST1 V3 coil driver:

H1:ISI-BS_BIO_IN_CD_ST1_V3_STATUS

This bit being true was causing the ST1 watchdog to be permanentaly tripped.

We tried without success to clear the problem with the following:

  • power cycling the relevant BIO chassis
  • power cycling the relevant coil driver chassis
  • power cycling the entire h1seib2 IO chassis, which involved:
    • shutting down all h1seib2 models
    • taking h1seib2 FE out of Dolphin
    • power FE down
    • power IO down
    • power AI down (to protect again DAC high output on restart)
    • power IO up
    • power FE up
    • power AI up

None of that cleared the bad bit.  Eventually Sheila checked the binary output from the coil driver and determined that everything looked good.  This gets the coil driver off the hook, narrowing the problem down to the BIO chassis or the BIO card itself in the IO chassis.

Given that we determined there was no actual problem with the coil driver, we decided to just bypass the problem by using the H1:ISI-BS_BIO_IN_BIO_IN_TEST EPICS channel to add in a value to the BIO input that would flip the single bad bit back to the desired value.  This solves the problem for the time being

Once the BIO chassis/card is fixed, the H1:ISI-BS_BIO_IN_BIO_IN_TEST channel will need to be set back to zero (0).  See the "BIO" screen from the ISI BS overview screen.

jameson.rollins@LIGO.ORG - 00:39, Tuesday 13 September 2016 (29646)

Unfortunately this bad bit is actually periodically flipping, and not staying flipped, so our test sum-in hack solution is not working.  We've had maybe two more locklosses caused by these bit flips.

LHO VE
kyle.ryan@LIGO.ORG - posted 17:16, Monday 12 September 2016 (29636)
Manually over-filled CP3
1720 -1735 -> To and from Y-mid 

LN2 @ exhaust after 32 seconds with LLCV bypass valve opened 1/2 turn -> Restored valve to as found state.  

Next CP3 overfill to be Wednesday, Sept. 14th.
H1 PSL
daniel.sigg@LIGO.ORG - posted 16:24, Monday 12 September 2016 - last comment - 13:11, Tuesday 13 September 2016(29635)
Outer Loop ISS Measurements

Keita Daniel

We were able to engage the new ISS with the most recent modifications, see alog 29570. The offset adjustment is very finicky. Trying to run with high ISS gain at low input power requires offset adjustments below the 0.1 count level as function of the gain value. We decided to leave the ISS gain fixed at 5 dB and set the offset through the 3rd loop filter module to 25.5 (or near there). This yields a unity gain frequency around 200 Hz. Ramping the power up to 50 W will then move the ugf up to about 4 kHz.

The first plot shows the transfer functions at 2.1 W (red), 50 W (blue) and 50 W with the boost engaged (green). The ISS gain was 5 dB for all measurements.

The second plot shows the PSD calibrated in RIN/√Hz. The red trace shows the error point which has not been corrected for the AC coupling, whereas the magenta trace shows the sixth PD (hooked up to channel 2). Both traces were taken at 50 W without boost. The black trace shows the error point at 2 W. The amber and dark blue traces show the RIN without the outer loop engaged. The dark blue trace is limited by ADC noise above 2 kHz. The ISS gain was again fixed at 5 dB.

Non-image files attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 13:11, Tuesday 13 September 2016 (29664)

Today, we locked the ISS at 2.1 W and measured the low end of the transfer function. Everything as expected.

Non-image files attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:07, Monday 12 September 2016 (29634)
Ops Day Shift Summary

Title:  09/12/2016, Day Shift 15:00 – 23:00 (08:00 –16:00) All times in UTC (PT)
State of H1: IFO is unlocked. Working on recovery after power outage.  
Commissioning: Daniel and Keita working ISS Second Loop
Outgoing Operator:  N/A
 
Activity Log: All Times in UTC (PT)

15:00 (08:00) Start of shift
15:27 (08:27) Filiberto – LVEA PSL rack and HAM2 installing ISS Second Loop chassis
15:51 (08:51) Karen – Going into the LVEA to do a walk through 
15:51 (08:51) Christina – Going to Mid-X for cleaning
15:56 (08:56) Filiberto – Finished in LVEA 
15:57 (08:57) Jason – Going into the LVEA to reset the Noise Eater
16:36 (09:37) Filiberto – Going into LVEA to work on ISS Second Loop chassis
16:49 (09:49) Filiberto – Out of the LVEA
17:00 (10:00) Jeff B. – Going to both End Stations to check dust monitors 
17:08 (10:08) Filiberto – Going into the LVEA to reinstall ISS Second Loop chassis
17:29 (10:29) Filiberto – Out of LVEA
18:00 (11:00 ) Jeff B. – Back from End Stations 
18:08 (11:08) TJ – Resetting Guardian nodes to correct problem apparently from power outage
20:44 (13:44) Filiberto – Going into LVEA to swap the ISS Second Loop chassis
21:05 (14:05) Filiberto – Out of LVEA


Title: 09/12/2016, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT)
Support: Sheila, Jenne, Dave, Richard, Carlos, TJ   
Incoming Operator: N/A

Shift Detail Summary:  Large dust storm in the area. Sorting out various problems after the power outage. Ran through an initial alignment. Commissioners working or relocking after the power outage.  

LHO FMCS
bubba.gateley@LIGO.ORG - posted 15:57, Monday 12 September 2016 (29631)
LVEA Heaters turned on
I have turned some of the heaters up in the LVEA. Heaters 1A, 1B, 4C, and 5C have all been increased by 1ma each.
H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 15:56, Monday 12 September 2016 - last comment - 15:59, Monday 12 September 2016(29632)
H1 PSL Status
PSL: 
SysStat: All Green, except VB program offline 
Frontend Output power: 34.9W  
Frontend Watch: Green
HPO Watch: Green

PMC:
Locked: 0 days, 3 hours, 9 minutes
Reflected power:   174.6W
Transmitted power: 119.1W 
Total Power:       293.6W 

ISS:
Diffracted power: 3.1%
Last saturation event: 0 days, 0 hours, 22 minutes 

FSS:
Locked: 0 days, 0 hours, 22 minutes
Trans PD: 4.401V
 
Comments related to this report
jeffrey.bartlett@LIGO.ORG - 15:59, Monday 12 September 2016 (29633)
This task is in the Ops checklist. Did not realize Patrick had already posted these data via a FAMIS task. 
H1 TCS
nutsinee.kijbunchoo@LIGO.ORG - posted 14:27, Monday 12 September 2016 (29630)
TCS chillers - new filters are in

Because the old filters are so dense that they let water though very slowly, I swapped them out for brand new ones. I ran clean chiller water though both filters couple of times before I put them in. Below I attached a picture comparing one of the old filters to a new one.

Images attached to this report
H1 CDS (DAQ, SUS)
david.barker@LIGO.ORG - posted 13:57, Monday 12 September 2016 (29629)
new h1susprocpi code installed, DAQ restart

WP6149 New h1susprocpi model installed followed by DAQ restart.

H1 PSL (PSL)
patrick.thomas@LIGO.ORG - posted 13:23, Monday 12 September 2016 - last comment - 13:33, Monday 12 September 2016(29626)
PSL Status Report - Weekly
Laser Status:
SysStat is good
Front End power is 34.9W (should be around 30 W)
Frontend Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 0.0 days, 0.0 hr 31.0 minutes (should be days/weeks)
Reflected power is 174.5Watts and PowerSum = 292.0Watts.

FSS:
It has been locked for 0.0 days 0.0 h and 17.0 min (should be days/weeks)
TPD[V] = 4.372V (min 0.9V)

ISS:
The diffracted power is around 3.448% (should be 5-9%)
Last saturation event was 0.0 days 0.0 hours and 17.0 minutes ago (should be days/weeks)

Possible Issues:
PMC has not been locked for very long
PMC reflected power is high
FSS has not been locked for very long
ISS diffracted power is Low
Comments related to this report
jason.oberling@LIGO.ORG - 13:33, Monday 12 September 2016 (29627)

Couple of notes:

  • Low diffracted power:
    • The new normal for the ISS diffracted power is 3%-4%.  The script should be updated to reflect this.
  • PMC reflcted power high:
    • After Saturday's power glitch the power meter that measures the PMC reflected power is misbehaving.  It is constantly reading 174+ watts, even though it's not seeing that much ligh; we're getting about 119W transmitted so at most we should be seeing ~31W reflected.  There's a couple things I'm going to try tomorrow, but if those fail the power meter will need replacing.  Until this gets resolved the Reflected Power and Power Sum for the PMC will be incorrect.
H1 ISC
sheila.dwyer@LIGO.ORG - posted 13:13, Monday 12 September 2016 (29625)
PR3 offset durring CARM offset reduction is back

Durring some of out unsucsesfull locking attempts last night we had the drift of PR3 durring the CARM offset reduction that we originally used the Ballmer offset to coutneract. (20055)

We had commented this out a few months ago because it was too large of a correction, but this morning I added it back and reduced it by a factor of 2 (the offset is now 0.25 in M1 P2P which causes about 0.02 urad of pitch).  

H1 PEM
jeffrey.bartlett@LIGO.ORG - posted 12:26, Monday 12 September 2016 (29623)
End-X High Particle Counts
   While investigating high particle counts at End-X, found the vacuum pump came up in reverse direction after the power outage.I reset the pump and adjusted the by-pass air. Ran Zero Count and Flow test, and all appears OK. 

   Checked End-Y. Found and fixed the same problem. Checked the CS as well. Since it is on a 3-phase circuit the pump did not restart in reverse. 

   Looking into making the power recovery of the vacuum pumps more robust.      
H1 DetChar (DetChar, ISC, SUS)
andrew.lundgren@LIGO.ORG - posted 11:07, Monday 12 September 2016 - last comment - 12:53, Monday 12 September 2016(29620)
Why does the OMC move so much during PSL power changes?
Josh, Andy

We noticed that the OMC is moving longitudinally by almost 100 microns between the 50 and 35 Watt locks overnight. It also moves after the other changes in power. The first plot shows the position as a function of power. We were curious whether there is a servo responsible for this, or if it's unintended, like a thermal effect. Is there a slow servo moving the OMC to maximize gain, that shifts the position as the IFO thermalizes?

The second plot zooms in on the time of the change down from 50 Watts. The OMC is stable during most of the lock, but then starts moving before the power is changed. Five minutes after the change, it starts moving in the opposite direction. Is it understood why it seems like it was starting to run away?
Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:55, Monday 12 September 2016 (29622)

This is a result of the alignment dither loop railing the OMC suspension actuators.  This should not be happening, especially after Sheila offloaded some of the alignment to the OMs (alog 29377).  We'll look into it. 

In the attached screenshot, note that the first lock at 50W does not rail the actuators, but we do pretty immediately for the second lock.  H1:FEC-46_DAC_OUTPUT_0_6 is the T3 actuator on the OMC suspension.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 12:53, Monday 12 September 2016 (29624)

We have angle to length feedforward for the OMC which was put in place to prevent scattering due to the angular dirves 19691.  In the second attachment to the alog Jenne linked you can see that the offloading helped us to not rail the suspensions, but most of the problem was due to the change as we power up not the miscentering when we first lock, so offloading with the pico motors could only help a litle bit.  I don't know why there seems to be a difference between the alignment of the carrier (which the OMC follows using the alignment dither loops) and the sidebands at the AS port, whoes alignment should be fixed by the AS_C and AS WFS centering servos.  

Durring the last few minutes of the 50W lock, the DC PDs were saturating due to PI, which could have confused the dither servo. 

If this continues to happen, we can try retuning the angular feedforward for the OMC.  It is possible both this and the confusing noise are related to the PIs being rung up.

H1 DetChar
sheila.dwyer@LIGO.ORG - posted 21:30, Sunday 11 September 2016 - last comment - 12:12, Monday 12 September 2016(29606)
Possible fringe wrapping

Evan, Sheila

Since the power reduction from 50W to 35W at about 2:25 UTC Sept 11, we have been sitting with the IFO mostly undistured other than changes to PI damping.  We have not been in low noise (no ISS second loop, we are still on the high noise ESD driver), but we have seen some hugh noise in DARM that looks like a fringe wrapping shelf.  We reduced the power again at 3:46 UTC, and the noise got better and went away after 10s of mintes.  

We don't see anything in our LSC loops or main ASC loops that had a similar shape, do the detchar fringe wrapping/scattering tools offer any clues? Especially at the beinging of this time window, there is a lot of noise in DARM (a high frequency comb) which is due to a rung up PI mode. 

Images attached to this report
Comments related to this report
andrew.lundgren@LIGO.ORG - 12:12, Monday 12 September 2016 (29621)DetChar, ISC
Andy, Josh

This doesn't seem like fringe wrapping. We're looking mostly at the time from 2:50 to 3:30 UTC (actually Sep 12 in UTC day), after the IFO has settled a little from the transition from 50 down to 35 Watts, and before the power changes again. We find no optics moving enough longitudinally to make a scattering shelf, though it could be something moving in angle. But also, this doesn't really seem to have the time structure of a scattering shelf.

The first attachment has spectra starting at 2:50 and stepping every 10 minutes. It's very confusing, and things are moving in different directions. But focusing on the feature between 20 and 40 Hz, it's hard to get a sense of what it actually is. The next two attachments are 15-minute spectrograms that show a wide band of noise slowly walking down in frequency. But an Omega scan shows bursts of noise - they don't look like scattering. They also don't look big enough to account for all of this noise, so maybe there's a glitchy bit and a background of Gaussian noise.

The next two plots are coherences with MICH/PRC/SRC at the beginning and end of the period. The coherence is significant with all, and it goes up at the low frequencies toward the end (when the excess noise has moved down in frequency). So maybe it's just because of changing coupling to some auxiliary degrees of freedom.

I'll quickly mention that there's a lot of other things going on. The last attachment is a spectrogram showing a huge moving comb around 300 Hz. We also saw clear RF beatnote whistles. We'll look into all of these more.
Images attached to this comment
H1 ISC (ISC, TCS)
kiwamu.izumi@LIGO.ORG - posted 19:35, Sunday 11 September 2016 - last comment - 21:26, Wednesday 14 September 2016(29604)
continued work on high power locking with the latest ring heater setting

Evan H., Jenne, Matt, Kiwamu,

We locked the interferometer at 50 W with the latest ring heater setting (RHX = 0.5 W, RHY = 2.5 W, 29588). So far the interferometer has been locked at 50 W for roughly 1 hour.

P.S. we have now having difficulty damping a PI mode (mode2, 15520 ITMX) and decreased the PSL power back to 30 W.

 

[DRMI lock on POP sensors]

As reported yesterday (29601), we had a difficulty in switcing the sensors from the 3fs to 1fs earlier today (29603). In the end, I manually executed the sensor switch process one by one and for some reasons this was successful. I then measured the open loop transfer functions of the DRMI LSC degrees of freedom, but they looked OK. See the first attachjment. This may be due to that we did not wait for long enough time to let the new CO2 setting settle (29603) for lock acquisition ([CO2X, CO2Y] = [500 mW, 1000 mW]). Not sure.

Also, in lock acquisition, I manually kept aligning PR3 when the interferometer was at ANALOG_CARM in order to maintain the lock.

[CO2 tuning at 50 W]

This is not well tuned, but the below is an OK CO2 tuning for 50 W which gave us a 30% imbalance at the AS port OSA.

[CO2X, CO2Y ] = [300 -400 mW, 0W]

This time I did not spend time for tuning the dCO2 at 20 W or 40 W. Maybe I should have done that to collect more data points.

[PIs]

MODEs 17 and 27 needed a sign flip. Mode 27 seems tricky -- every time when it rang up we needed to flip the control sign.

Images attached to this report
Comments related to this report
matthew.evans@LIGO.ORG - 21:46, Sunday 11 September 2016 (29607)

The PI difficulties are probably my fault. The phases may not have been set properly after the power glitch.

sheila.dwyer@LIGO.ORG - 00:41, Monday 12 September 2016 (29609)

After damping PIs (Terra is writing about this) we tried to take the IFO back to 50 W, but lost lock within a few minutes.  I'm not sure why we lost lock, it didn't seem to be PI or the usual sidebands tanking problem, there was a glitch in CHARD and DHARD a second before lockloss (1st attachment). 

We spent some time relocking and found that we had some problems durring the latter CARM offset reduction steps which were similar to what we had last night.  We measured the DARM loop at RF DARM and at the state CARM 15 pm, it seems fine (2nd attachment).  

It is possible that our relocking difficulties were due to bad alignment, or the new TCS.  As we were about to try to relock the 3rd time, we got hit by an EQ so we stopped for tonight. 

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 18:52, Monday 12 September 2016 (29637)TCS

Here is some analysis of the sideband imbalance.

Synopsis -- Overall, adjustment of the CO2 lasers I did at 50 W improved the sideband imbalance at the AS port

However, the resulting CO2 setting does not match what we expected from the previous test (29585). We expected the final CO2 settings to be [CO2X, CO2Y] = [100 mW , 0 mW], but we ended up with [400 mW, 0 mW].

The 45 MHz seems to prefer a high CO2 contrast of roughly 400 mW (CO2X minus CO2Y) regardless of the ring heater settings so far, and this prevents us from further reducing the common lens.

 

[The sideband evolution as seen by the OSA]

The below shows a plot of the OSA raw output. I plotted several scans from different times, each of them is separated almost by 10 minutes in time.

Also, here is a rough time line of what I have done in this lock.

  • 17:36 The interferometer reached 50 W
    • CO2X and CO2Y were simultaneously reduced to 100 mW and 0 W respectively.
  • 18:00 I started increasing CO2X because the sideband imbalance was becoming worse.
  • 18:53 I kept increasing CO2X and eventually set CO2X to 400 mW
  • 19:24 PSL power was decreased to low power to combat the PIs.

Here is another plot showing how the sideband amplitude evolved as a function of time.

It is evident that increasing CO2X helped reducing the imbalance. Before I started changing CO2X, there was a slow trend in which the imbalance kept decreasing.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 00:12, Tuesday 13 September 2016 (29643)

Here is another trend plot.

The carrier recycling gain stayed at 29 at 50 W. The sideband build up or ASAIR90 seemed to have reached some kind of equilibrium after approximately 1 hour or so. Also, looking at ASAIR RF 45 Q, I don't see any change in the DARM offset point -- hopefully this is an indication of a stable optical gain. The Pcal line at 331.9 Hz was too small that it was burried below intensity noise. So I could not directly check the DARM optical gain.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 00:22, Tuesday 13 September 2016 (29644)

The intensity noise coupling changed as a function of time at 50 W. Here is a plot showing several coupling transfer functions from different time.

The measurement time were set to identical to the ones showed in above or 29637. Here is a plot of the transfer coefficient at 400 Hz as a function of time.

As you can see, the coupling became worse at the beginning for about 20 minutes or so. Then it came back to a value as small as the very begining. Although high frequency above 100 Hz seems to have settled to a small coupling, the low frequency part looked worse at the end. See the first attachment.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 01:34, Tuesday 13 September 2016 (29648)

As for the HWS signals, while the HWSX signal seems reasonable, the HWSY reports a twice large self heating.

Here are some conclusions from comparison of the predicted ITM lensing (outputs from TCS-SIM) and HWS outputs.

  • HWSX
    • It looks that we are overestimating the defocus by the self heating in the ITM substrate by 15% or so. This could be due to an inaccurate calibration of the arm power in the TCS simulator.
    • The CO2 actuator coefficient needs to be updated to 25 uD/W (28799). Because we use a high value for the CO2 actuation coefficient, the simulator overestimates the effect by 24 %.
  • HWSY
    • The below assumes an accurate readout of the HWSY.
    • The predicted self heat seems to be too low by almost a factor of two.
    • The predicted CO2 defocus is too high by 24% or so. This means the actuation coefficient should be 47 uD/W in the TCS simulator.
    • However, a 47 uD/W is not consistent with what we have measured (28799) -- the past measurement suggested that it should be about 25 uD/W.
  • Questions
    • Why does the CO2 X now have a smaller actuator coefficient? In the past it was 62.3 uD/W (T1400685).
    • Why is the CO2 Y coefficient different from a calibration measurement (28799)? The measurement suggested it was 25 uD/W and now it seems more like 47 uD/W.
    • Why the ITMY self heating increased by a factor of two?

 

The below shows a comparison between the single-pass defocus measured by HWSX and that predicted by simulator (with some coefficient fitting similarly to 27330):

I added a constant offset to the simulated defocus in order to plot it on top of the measured defocus. I removed the ring heater component that was unfortunately in the middle of settling to the equilibrium in the simulator due to the unscheduled model restart (29592).

The below is a same plot, but for the ITMY substrate defocus.

As noted in the legend, the component from the self heat needed to be increased by a factor of two.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 09:27, Wednesday 14 September 2016 (29692)

The stability of AS90 was apparently better with the combination of the new ring heater setting and dynamically-decreased CO2s.

The below plot shows a comparison of this lock stretch (Sep. 12) and two lock stretches (Sep. 09) from a day before we started changing the ring heater setting.

The two lock stretches from Sep. 09 both showed AS90 decreasing monotonically as a function of time. This was something we have been suffering from (29486) and has been an issue since the begining of this month (29457) at which we considerably changed the interferometer alignment.

In contrast, AS90 settled to a value pf 600 counts on a time scale of 30 minutes or so in the new lock stretch. This lock was stable until PI modes started ringing up. The carrier recycling gain was slightly lower than the previous two stretches. I don't know if this due to misalignment or new ring heater setting.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 21:26, Wednesday 14 September 2016 (29712)

Here are the evolution of the wavefront gradient as a function of time as seen by the Hartman sensors.

The starting time is set to Sep 12 2016 00:30:30 UTC at which the interferometer was in the middle of powering up to 50 W. The gradients are initilized such that the gradients are zero at dt = 0.

Images attached to this comment
H1 PSL
peter.king@LIGO.ORG - posted 13:26, Saturday 10 September 2016 - last comment - 13:41, Monday 12 September 2016(29594)
PSL tripped
Came in to find the laser had tripped, presumably because of the site-wide power glitch.
Brought laser back.  Everything seems to be okay.  However both the reflected power and
the power sum measurement reported by the MEDM screen are out of whack.  It might be that
the power glitch fried the reflected power power meter similar to what happened the last
time power to the site went out - it took out the power meter in the external shutter.
The power sum might be a problem with the photodiode.

    Both might require restoration of the calibration factors from the snap files.
Comments related to this report
peter.king@LIGO.ORG - 14:07, Saturday 10 September 2016 (29595)
The output filters for both the reflected power and power sum report what look like the correct
values.  For the reflected power signal, the ADC seems fine so it must be the power meter.
jason.oberling@LIGO.ORG - 13:41, Monday 12 September 2016 (29628)

Filed FRS #6194 for the apparent power meter failure.

Displaying reports 55721-55740 of 84557.Go to page Start 2783 2784 2785 2786 2787 2788 2789 2790 2791 End