Displaying reports 61081-61100 of 85942.Go to page Start 3051 3052 3053 3054 3055 3056 3057 3058 3059 End
Reports until 14:02, Saturday 13 February 2016
H1 CDS
david.barker@LIGO.ORG - posted 14:02, Saturday 13 February 2016 - last comment - 14:16, Saturday 13 February 2016(25532)
CDS web server down, we are restarting it

The CDS web service (cdswiki) has been down since at least 11:50 PST, Evan H has kindly agreed to  restart it to see if we can clear the error.

Comments related to this report
david.barker@LIGO.ORG - 14:16, Saturday 13 February 2016 (25533)

Machine came back after hard RESET using front panel button. Log files show no problems at the time of the freeze up, last log was 03:52 PST which could be close to the time the computer locked up due to the verbosity of the logging.

Thanks again to Evan for the reset.

H1 CDS
evan.hall@LIGO.ORG - posted 11:18, Saturday 13 February 2016 (25531)
ITMX ISI trip does not show up on ops overview

The ITMX ISI tripped after the most recent earthquake, but the corresponding box on the ops overview screen remained green.

The trip did show up as a diag main guardian notification, however.

Edit: nevermind, it seems that the ops overview screen on video2 is frozen.

H1 ISC (DetChar)
kiwamu.izumi@LIGO.ORG - posted 10:57, Saturday 13 February 2016 - last comment - 11:20, Saturday 13 February 2016(25528)
Fewer range killing saturations at ETMY

Related to: 25468, 25485

Last night, we seemed to have less number of the ETMY DAC saturation events presumably due to a combination of the new modification on the ESD driver electronics (25468, 25485) and moderate seismic and wind conditions. The DACs for driving the ESD now have more range above 152 Hz and therefore can tolerate some of the fast transients without hitting the DAC output range. As shown above, the BNS range plot from last night is cleaner than the typical O1 range plots. Looking at the undisturbed data from yesterday, we had only two saturation events (both of which occurred at the ESD stage of ETMY) out of the 9 hours lock stretch; one at the beginning and the other at roughly 10 minutes before the lockloss. See the attached trend.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 11:20, Saturday 13 February 2016 (25530)

A follow up:

I checked the number of saturations from a 14 hrs long stretch from this Wednesday's night as well. I found only two saturation events in the ETMY suspension (both of which happened in the ESD stage. One of them occurred at the ESD and L2 stages). See the attached trend.

The BNS range was already posted by Corey (25502) which showed two deep dips at t = 7 and 14 hours. These two correspond to the saturations at ETMY. I did not study the other small dips.

Images attached to this comment
H1 ISC
jenne.driggers@LIGO.ORG - posted 20:35, Friday 12 February 2016 - last comment - 11:09, Monday 15 February 2016(25525)
New ISS servo oscillates

The new ISS digital AC coupling caused the diffracted power to oscillate by ~1% with a period much less than 1Hz.  I tried turning the gain down on the servo, but we lost lock (we were in NomLowNoise).

Comments related to this report
kiwamu.izumi@LIGO.ORG - 00:55, Saturday 13 February 2016 (25526)

Later, I locked the interferometer to nominal low noise in order to check the behavior of the ISS. The 2nd loop was able to automatically engage the servo. I did not see a fault behavior with the ISS at least after twenty minutes in full lock.

Perhaps what Jenne saw is a type of oscillation that reported in alog 24665 ? Since the interferometer is locked, I am leaving it undistrubed. By the way OMC DCPDs are seemingly with low transimpedance. Noise in DARM below 50 Hz seems higher than the reference curve. I did not pay attention to the calibration at all.

kiwamu.izumi@LIGO.ORG - 09:45, Saturday 13 February 2016 (25527)

The attached show an overnight trend (for 12 hours) of the relevant channels. As Jenne pointed out, the diffraction power indeed fluctuated (below 1 Hz) by 1 % or so all the time, but this is a known behavior (alog 24665) -- the 2nd loop changes the operating point of the first loop since the 2nd loop still has some gain at low frequencies even though it is digitally AC-coupled. As Gabriele pointed out, we think this fluctuation is added by the angular motion of the input mode cleaner (alog 24677). If we want to improve fluctuations in the diffraction power, the next attacking point would be the input mode cleaner.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 11:09, Monday 15 February 2016 (25546)CDS, SEI
Tagging SEI and CDS in this. 

If this problem (this aLOG and LHO aLOG 24665) has moved into the "we keep re-discovering it" category, perhaps the ISC team should request that CDS to work with SEI to push fixing HAM3's 0.6 [Hz] oscillation problems, and allow some non-Teusday time to do so.
H1 ISC
sheila.dwyer@LIGO.ORG - posted 19:30, Friday 12 February 2016 (25523)
re-occurence of ALS glitches

We had another incident of ALS glitches today, this time in the X arm. We sat for a while just with the green arms locked, and the glitches became more frequent and worse and then things got better.  The glitches were bad for about an hour and a half, but you can see that something is still noisier than it was this morning. 

We have had this problem several times before: 22184

Images attached to this report
H1 ISC
jenne.driggers@LIGO.ORG - posted 19:12, Friday 12 February 2016 (25522)
ISS causing lockloss

[Jenne, Kiwamu, Sheila, Nutsinee]

We were trying to lock the IFO at lower power, so that we can see how / if that changes the DARM spectrum at low frequencies, but we have (re-)discovered the fact that the ISS loop is unstable at powers other than 20W.  So, shortly after engaging the ISS second loop we lost lock twice (once at 2W and once at 10W). 

For now, we're going to skip over the engage ISS second loop state, since we need to think more before we decide to make a change. 

H1 SUS (ISC, SUS)
jenne.driggers@LIGO.ORG - posted 18:45, Friday 12 February 2016 (25520)
SR3 cage servo setpoint modified

[Jenne, Sheila, Nutsinee, TJ]

We struggled for much of the afternoon trying to get the DRMI ASC to behave.  In the end, it seems that the SR3 OSEM values have changed now that we have a new satellite amplifier installed (see alog 25516 by Fil).  Sheila pointed out that we should trend both the WIT channels and the oplev channels for SR3, and then trust the oplev since nothing about it was changed today. 

In the attached plot, you can see that since we didn't move SR3 in yaw, the oplev value is constant but the WIT value is different.  Since the cage servo forces the WIT_P value to go to a constant pre-set value, it is the oplev that appears to move in pitch.  I have reset the SR3 cage servo setpoint to be 927, which is where it needs to be if we move SR3 so that we're back to the old oplev value.  This seems to have fixed things, and we were able to move on.

The OSEM inputs changed by about 20 counts each.

Images attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 16:37, Friday 12 February 2016 - last comment - 10:56, Saturday 13 February 2016(25519)
Used garbage bag to measure exhaust flow of CP3
Kyle, Gerardo 

We want to know if we can use the measured exhaust flow of CP3 to distinguish between relatively low LN2 pump levels versus relatively high LN2 levels and then exploit this as part of a makeshift control loop and/or justify increasing the time interval between manual over-fills.  CP3 was last manually over-filled this past Wednesday afternoon.  So this morning, at the ~42 hour mark, we used a plastic garbage bag to capture the exhaust until the bag was taught full (see image).  We did this twice and got the following results: 

220L/90sec = 145L/min, 220L/100sec = 130L/min.  

6 hours later we manually over-filled CP3 at its normal 48 hour scheduled interval and then let the system settle down for 10 minutes or so before repeating the "bag" experiment.  This time we got the following results:  

220L/115 sec = 115 L/min.  

CONCLUSION:  

This result is surprising and not as expected.  We may instead need to have Dave B. setup the exhaust PRESSURE signal (the not-blocked sensing line) so that we can trend it (I don't think we can currently for some reason).  We already know that the exhaust pressure does vary >50% with slow over-filling so we might make a course control loop that fills CP3 based upon a preset time interval and then shuts off based upon when an exhaust pressure threshold is exceeded. 
Non-image files attached to this report
Comments related to this report
david.barker@LIGO.ORG - 10:56, Saturday 13 February 2016 (25529)

The discharge line pressure EPICS channel is HVE-MY:CP3_PT201 and it is indeed not in the DAQ at the moment, we'll add it during Tuesday maintenance.

In the mean time it is recorded every hour by the hourly autoburt backup system. Here are the commands to grep for this channel from yesterday for example (the space after the name is important)

david.barker@sysadmin0: cd /ligo/cds/lho/h0/burt/2016/02/12

david.barker@sysadmin0: grep "HVE-MY:CP3_PT201 " */h0vemy.snap

00:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

01:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

02:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

03:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 8.241758241758241e-01

04:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 7.020757020757020e-01

05:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

06:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 7.020757020757020e-01

07:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 6.715506715506715e-01

08:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 6.715506715506715e-01

09:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 7.936507936507936e-01

10:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 6.715506715506715e-01

11:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 6.715506715506715e-01

12:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.494505494505494e-01

13:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.494505494505494e-01

14:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.494505494505494e-01

15:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.494505494505494e-01

16:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 7.020757020757020e-01

17:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

18:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

19:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

20:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

21:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

22:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01

23:00/h0vemy.snap:RO HVE-MY:CP3_PT201 1 5.799755799755799e-01


 
I wrote a quick python script to plot out this channel for the month of Feb up to midnight this morning, plot is attached. I'll extend this script to plot any channel from the hourly autoburts.
Images attached to this comment
LHO General
thomas.shaffer@LIGO.ORG - posted 16:00, Friday 12 February 2016 (25512)
Ops Day Shift Summary
H1 SEI
hugh.radkins@LIGO.ORG - posted 15:27, Friday 12 February 2016 (25518)
Attempt to center ETMY X=+30 (outside) STS2 Masses--not yet

Two of the three channels still seem to be stuck on the rail.  I did two centering pushes today.  I'll continue next week, hopefully it will stabilize by then.

H1 SUS
filiberto.clara@LIGO.ORG - posted 13:37, Friday 12 February 2016 - last comment - 19:47, Friday 12 February 2016(25516)
OMC and SR3 Sat Amp Units Modified
While investigating the high frequency oscillations seen on SR3, we decided to modified the satellite amp units for OMC and SR3 (Bottom). Two decoupling capacitors were placed on the input of the negative regulator (U503), as implemented at LLO. 

C602 0.1uf
C601 10uf

The OMC units modified are S1100129 and S1100127. For the SR3 unit, we removed unit S1000287 and replaced with a modified unit S1100074. High frequency oscillations 1.7KHz and 1.9KHz seem to have cleared. Work to continue next week, as some channels still show some noise on the spectrum.
Comments related to this report
keita.kawabe@LIGO.ORG - 19:30, Friday 12 February 2016 (25521)

SR3 should be back (but we cannot prove that until we see that the cage servo doesn't act up with pre-disaster gain.)

In the first attachment, we can see that the SR3 M3 WIT_PMON and YMON seem to have gone back to the old peak-to-peak.

In the second attachment, top right shows the comparison of now (red) and before (blue, green) of SR3 M3 LL OSEM.  After the modification (red), 1.7kHz and 1.9kHz lines obvious in blue and green are gone. I'm sure that the SR3 is fully back..

Top left shows the four SR3 M3 OSEMs as of now. None of them show kHz oscillation lines. LL is the noisiest, LR is the most quiet. There are some ugly 60Hz harmonics, and there are also a bunch of peaks that are not the power line harmonics (e.g. 142Hz). I cannot prove it but I suspect that these peaks were there before.

The bottom left shows OSEM outputs of OMC, PR3 and SRM. SRM and OMC don't have ugly power line and whatnot peaks, but PR3 look similar to SR3.

Images attached to this comment
keita.kawabe@LIGO.ORG - 19:47, Friday 12 February 2016 (25524)

Even though SR3 seems to be back to its old self,  fast OSEM is still copied to EPICS without decimation and pollutes cage servo when the oscillation comes back (and the OSEM RMS is anyway dominated by high frequency junk even when it's not oscillating).

Since these are only used for cage servo and as slow references, I put 60Hz 3rd order Butterworth LPF to all of the SR3 M3 OSEMINF (attached). This is a mild one and should not interfere with the cage servo, but reduces the high frequency junk leaking into WIT_PMON that is used by the cage servo.

Images attached to this comment
H1 PSL
kiwamu.izumi@LIGO.ORG - posted 12:09, Friday 12 February 2016 (25515)
ISS 2nd loop fully automated

The automation of the 2nd loop engagement has been updated to use the front end funcionts (alog 25473) and confirmed to be functional.

We do not have to do the manual engagement any more. Yay.

 

[some more words]

I have tested the automation once as part of the full locking sequence in this Wednesday. The test in full lock exposed some minor issues with my implementation (e.g. some settings were not properly initialized and etc). Today I fixed the IMC_LOCK code so that the automation startd from the proper initial settings. I tested the new implementation with the input mode cleaner multiple times and confirmed that it was functional as intended. The automation is fully implemented.

H1 SEI
hugh.radkins@LIGO.ORG - posted 11:20, Friday 12 February 2016 (25514)
STS2-C moved from HAM5 area to near STS2-B in Bier Garten for Huddle testing

WP--5683; ECR-- E1500455

I've center the masses now and they seem pretty good after 4 or 5 attempts.  We'll see how things have thermally stabilized after the weekend.

H1 ISC
evan.hall@LIGO.ORG - posted 23:40, Monday 08 February 2016 - last comment - 16:58, Friday 12 February 2016(25451)
Oscillator amplitude noise coupling TFs into DARM

Related: 20559, 19911

Summary

I remeasured the RFAM-to-DARM TFs for the 9 MHz and 45 MHz sidebands.

The 45 MHz measurement agrees with the previous result of ~0.1 mA/RAN. However, the 9 MHz measurement is also ~0.1 mA/RAN, which is a factor of 10 higher than what was measured previously. Note that the previous "9 MHz" RFAM measurement was really a simultaneous measurement of 9 MHz and 45 MHz RFAM, since we had no 45 MHz RFAM stabilization in place.

Details

For the 45 MHz measurement, I injected into the error point of the 45 MHz RFAM stabilization servo and measured the TF from the OOL RFAM stabilization detector (which is already calibrated into RAN) to the DCPD sum.

For the 9 MHz measurement, I temporarily replaced the OXCO with an IFR running at 9.1 MHz and +10 dBm. Then I used the spare DAC channel to inject into the IFR modulation port, which was set to 10 % deviation, dc-coupled (which means a RAN of 0.071 for 1 V of input, though I did not measure this directly). The signal from the spare DAC is buffered by an SR560 and sent back into one of the spare ADC channels. Then I measured the TF from the spare ADC channel to the DCPD sum. This measurement relies on the 45 MHz RFAM servo suppressing the resulting fluctuations in the 45 MHz sidebands before they are applied to the EOM; looking at the OOL readback, this seems to be satisfied below 1 kHz. Above 1 kHz, there is a RAN increase of <2 compared to no 9 MHz injection.

Templates live in my folder under Public/Templates/Osc/(45|9)_RFAM_2016-02-08.xml.

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 16:58, Friday 12 February 2016 (25517)

In addition, I took noise measurements of the 9 and 45 MHz RFAM spectra.

The 45 MHz measurement is straightforward, since we already have a calibrated, dequeued RFAM monitoring channel. (Actually I used the faster, undequeued IOP channel, calibrated it, and undid the AA filter.) the noise between 50 Hz and 1 kHz is a few parts in 109 / Hz1/2.

We don't have a similar readback channel for the 9 MHz RFAM close to the EOM, so I made a mixer-based measurement by taking an output from the ISC 9 MHz distribution amp, splitting it, and driving both sides of a level-7 mixer. I had 9 dBm into the LO and −3 dBm into the RF, so the LO was being driven hard and the RF was below the mixer's compression point. The mixer IF was terminated and then bandpassed with a 1.9 MHz filter. The IF dc was −135 mV or so.

To read out the noise, I took one of Rai's low-noise preamps (measured to have <2 nV/Hz1/2 input-referred noise) and ac-coupled the input with a 20 µF capacitor (giving a high-pass pole at <0.1 Hz). Then I read out the noise with an SR785. I have not yet verified that the signal is above the noise floor of the mixer measurement.

Finally, I also include the RFAM-to-DARM coupling TFs with the DARM loop undone.

Images attached to this comment
Non-image files attached to this comment
Displaying reports 61081-61100 of 85942.Go to page Start 3051 3052 3053 3054 3055 3056 3057 3058 3059 End