Displaying reports 65621-65640 of 83348.Go to page Start 3278 3279 3280 3281 3282 3283 3284 3285 3286 End
Reports until 12:30, Monday 04 May 2015
H1 PSL
patrick.thomas@LIGO.ORG - posted 12:30, Monday 04 May 2015 (18208)
Ops PSL check
Laser Status: 
SysStat is good
Front End power is 31.4W (should be around 30 W)
FRONTEND WATCH is RED
HPO WATCH is RED

PMC:
It has been locked 0 day, 23 hr 54 minutes (should be days/weeks)
Reflected power is 2.0 Watts and PowerSum = 24.3 Watts.
(Reflected Power should be <= 10% of PowerSum)

FSS:
It has been locked for 5 h and 4 min (should be days/weeks)
TPD[V] = ~1.1V (should be 1.3 - 1.6)

ISS:
The diffracted power is around 8.5% (should be around 7%)
Last saturation event was 22 h and 57 minutes ago (should be days/weeks)
H1 SEI
hugh.radkins@LIGO.ORG - posted 12:14, Monday 04 May 2015 (18207)
LHO SEI STS2-B Study Update

Attached are the series of plots: ASDs, Coherences, and TFs; for and between the three LVEA SEI STS2 instruments.

Last week I moved the STS2-B (ITMY) to concrete (References for it are the old unit on vinyl under the igloo.)

The current traces attached are from this morning at 0130pdt.  I had a problem with the calibration and units before, but getting that straight hasn't made answers to all the questions clear.

The three Z ASD are right on top of one another to below 20mHz.  The Y DOF ASDs are similar but they diverge below 40mHz.  For the X DOF, the HAM2 instrument seems the outlier diverting from the other ASDs as high as 90mHz whereas ITMY and HAM5 are hand in hand until 20mHz.

The Coherences look very good on Z, other DOFs are here and there.  Maybe as expect too, the Z TFs look great, and the other DOFs are 'it depends.'

I think we can say that the removed STS2 should go in for overhaul and the HAM2 machine should be huddle tested with one of the others.

Images attached to this report
H1 AOS
keita.kawabe@LIGO.ORG - posted 11:56, Monday 04 May 2015 - last comment - 21:32, Monday 04 May 2015(18205)
oplev receives the arm scatter

Apparently I haven't aloged it last week, but oplevs recive the IR scatter from the arm. It's not a big deal, I'm writing this just for the record.

Attached shows one 7W lock when ETMY OPLEV was not working (no light). As soon as IR resonates in the arm, ETMY oplev segments jump up  and the SUM goes to 560 counts (left and middle row). If the oplev laser was alive, this 560 counts would have been added on top of about 30k counts. Fortunately this is mostly common for all four segments, and the effect on the angle readout, when the oplev laser is alive, would have been about  0.03% of the full range, or about 0.03 urad.

The same thing happens to ETMX (right bottom) except that the oplev laser was alive and that the scatter increased the oplev SUM by only 360 counts.

For ITMs the SUM due to the arm scattering seems to be abount an order of magnitude smaller than ETMs, but the oplev power itself is also smaller (3000 to 4000 counts).

Images attached to this report
Comments related to this report
daniel.hoak@LIGO.ORG - 21:32, Monday 04 May 2015 (18221)

Along the same lines: quite a while ago during the DRMI locking, Jeff and I noticed that the BOSEMs of the HAM6 tip-tilts would pick up flashes from the DRMI lock acquisition that would generate spurious damping signals and shake the mirrors.  This isn't a problem because we don't need those optics to be quiet before DRMI locks, but we thought it was interesting.  I can't remember if the OMC SUS acquired some noise from the DRMI flashing.

After we noticed this, Jeff and I checked that it wasn't a problem for any of the corner-station mirrors that we don't actuate on to lock DRMI.  We saw no evidence that DRMI flashing generated noise in the ITMs, PR2-3, or SR2-3.  Of course it's impossible to tell if PR2, SR2, or BS OSEMs are affected by flashes since the LSC drive is banging on those optics when we're trying to acquire.

H1 ISC
keita.kawabe@LIGO.ORG - posted 11:24, Monday 04 May 2015 (18204)
TMSY IR QPD still clipped

(Update: See Peter's alog.)

I looked at the lock stretch from last night and the IR QPDs on TMSY still show the sign of clipping though the saturation was fixed.

On the left column you have X QPD SUM(B)/SUM(A) data (top), which is basically just a solid flat line after the IR resonates in the arm over a large change in the IR alignment.

The top right plot for Y QPD SUM ratio has the same scale as the top left, it goes up and down in low power lock and then steps up when the power was increased. Even during the 10W lock, the ratio was not as stable as X.

It's not like Y beam is particularly moving larger than X.

Images attached to this report
H1 GRD (DetChar, ISC)
jeffrey.kissel@LIGO.ORG - posted 10:31, Monday 04 May 2015 (18203)
ISC_LOCK Guardian Nominal State Changed Back to 'LSC_FF'
J. Kissel

Now that the mini-run is complete, I've reverted the "nominal" ISC_LOCK guardian state back to LSC_FF (I'd changed it to the mini-run state of "LOWNOISE_ESD_ETMY" on Friday, see LHO aLOG 18145). I've reloaded the guardian code change, and confirmed that the "nominal" box is now surrounding the LSC_FF state; see attached.
Images attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 08:52, Monday 04 May 2015 (18202)
Morning meeting notes
SEI
nothing planned

SUS
nothing planned

CDS
continue preparations for chassis swap
possible RCG upgrade on Tuesday

FAC
starting repair of wall around patio area
wet paint all around building
expecting delivery from Sunbelt

PSL
trips appear to all be related to flow sensor

VAC
preparation for vent of end stations in June
need to run pump cart at Y end for 24 hours to bakeout RGA, possibly Tuesday
H1 PSL
edmond.merilh@LIGO.ORG - posted 08:23, Monday 04 May 2015 - last comment - 08:27, Monday 04 May 2015(18199)
PSL ISS AOM Diffracted power

This morning AOM diffracted power was up to ~ 13% with a refsignal setting of -2.00 . I've adjusted the Diff power to ~ 8.5% -> refsignal = -2.05

Comments related to this report
edmond.merilh@LIGO.ORG - 08:25, Monday 04 May 2015 (18200)

I've taken care of the changes noted by the SDF and accepted the new settings.

edmond.merilh@LIGO.ORG - 08:27, Monday 04 May 2015 (18201)

FSS resonance threshold had also changed from .6V to .55V. This was also noted and accepted in the SDF.

H1 ISC
evan.hall@LIGO.ORG - posted 00:40, Monday 04 May 2015 (18197)
AS_C bandwidth

Summary

Today I wanted to see if increasing the bandwidth of the SRC ASC loops could make the 90 Hz SRCL coupling into DARM go away or become more stationary. I cranked up the bandwidth of the AS_C loop, but saw no improvement. We should try cranking further, or else try cranking the bandwidth on the AS36I loop.

Details

I was able to bring the interferometer to dc readout at 10 W with a recycling gain of 39 W/W. To get there, I had to turn on the ITM oplev damping again to avoid 0.4 Hz instability during power-up (and sometimes during the last steps of the CARM reduction sequence). I was able to engage the MICH, SRCL, and dETM yaw boosts without issue.

Then I tried increasing the bandwidth of the AS_C pointing loops. I was able to increase the gain by a factor of 30 just fine (2 ct/ct to 60 ct/ct, pitch and yaw), which gave a ugf of about 250 mHz as measured by step response. This means that the original bandwidth was less than 10 mHz, since the loop is 1/f below the suspension resonances. Correspondingly, the low-frequency angular motion seen by AS_C is suppressed by a factor of 30 or so, and the rms angular motion seen by AS_C is reduced by a factor of 4 in pitch and some small factor in yaw. Based on the attached spectra, it seems like we would have to push the bandwidth up to several hertz in order to see any further improvement in the rms. Anyway, after doing this I did not see any improvement in the stationarity of the SRCL coupling aroung 90 Hz.

I attempted to repeat this exercise with the AS36I loops, since Gabriele had previously found that the pitch loop was the dominant signal modulating the SRCL/DARM coupling once dETM yaw was adequately suppressed. However, I could not increase the loop gains by more than a factor of 4 before they went unstable (this was the case even when I engaged the same HSTS compensation filter as used for the AS_C loops). This factor of 4 was not enough to give a noticeable improvement in the spectra of AS36I pitch and yaw, since these loops are also slow (<100 mHz, just based on watching the loops' responses to transients).

Non-image files attached to this report
H1 PSL
evan.hall@LIGO.ORG - posted 12:15, Sunday 03 May 2015 (18194)
PSL untripped

I came in and found the PSL had tripped about 6 hours ago. It is again correlated with some flipping of the diode chiller flow monitor bit. After the trip, the bit flips for about 40 s before returning to the OK (1) state.

When I went to reset it, both chillers were on. The diode chiller has been holding steady at 20.5 lpm or so for the past hour (not sure about further back in time).

Images attached to this report
H1 DetChar (DetChar, PEM)
andrew.lundgren@LIGO.ORG - posted 06:31, Sunday 03 May 2015 - last comment - 15:36, Sunday 03 May 2015(18193)
Range-wind correlation for some locks during mini-run
To answer Jeff's question about the wind, I looked at the ten hour lock, and the three hour lock starting about 23:30 UTC (ignoring the stochastic injection). I wrote a custom script to make the plots, since I couldn't get sensemon range from NDS. I've done a 3-minute median filter on the wind and range minute trends to smooth them out a bit.

The first plot shows the wind and range for the first lock. Around 12:30 UTC, the spectrogram (second plot) shows a big increase in the noise, and there's a corresponding decrease in the range. I think this is unrelated to the wind, and will be investigated elsewhere, so I've cut this lock off about 320 minutes in (third plot). The fourth plot is the scatter of the wind versus the range. A simple fit gives a value of 8.4 Mpc at zero with an 0.03 Mpc decrease per MPH of wind. The fifth and sixth plots are this repeated for the other lock, starting after the stochastic injection ends. The fit is 9.0 Mpc at zero with an 0.01 Mpc decrease per Mpc of wind.

I've attched the script I used. It needs a cache file for data of type H-SenseMonitor_CAL_H1_M called snsw.lcf. There's some values hard-coded, but it should be obvious what to change.
Images attached to this report
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 15:36, Sunday 03 May 2015 (18196)DetChar, ISC, PEM, SEI
Sweet set of plots, thanks! Can you (and/or @DetChar, collectively) make a similar assessment of wind vs. omicron glitchiness?
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 00:42, Sunday 03 May 2015 (18192)
Mini run Saturday evening shift Summary

16:24 Jim left the interferometer locked. Intent bit switched to Undisturbed.

19:48 Lock loss. PSL tripped ("Epics Alarm" went red). The guardian didn't switch off the undistrubed intent bit. I switched it off few minutes later.

20:40 PSL recovered (Thank you Peter K!) but IMC wasn't. I waited at least 5 minutes but it doesn't seem to lock itself. I trended and adjusted the MC1, MC2, and MC3 pitch back to where it was before it lost lock.

21:22 IMC locked. Redid initial alignment for the first time today.

22:18 Locked at LOWNOISE_ESD_ETMY (~11Mpc)

22:28 Intent bit switched to Undisturbed

22:50 Undistrubed intent bit turned off. Attempted to damp the violine modes.

22:55 Intent bit switched to Undistrubed. Jeff Kissel suggested I leave the violin modes alone.

23:01 Lock loss. PSL tripped AGAIN ("Interlock OK" went red).

23:09 PSL recovered

23:47 I realigned IMC again. It seems to me that IMC optics read off the bad alingment from somewhere and didn't go back to where it was when the ifo was locked. I was able to bring the IMC reflected light down to 52 counts (It was 53 during the previous lock). The alignment is saved. AS Air flashing at none 0,0 mode. Redid the initial alignment (didn't take too long. The ALS was already good).

           ALIGN_IFO stays on MICH_DARK_LOCKED for a very long time even though AS AIR was ~0. I moved on to SRC ALIGN before the panel was green.

00:17 Lock loss at ANALOG_CARM. IMC locked itself this time.

00:34 Locking again at LOWNOISE_ESD_ETMY (~10 Mpc). Intent bit switched to Undisturbed. Leaving the interferometer at this state. Wind slowly picking up speed.

 

A few notes before I leave the chair:

- As Jeff K. has requested, it would be nice if a Detcharian out there could plot the BNS inspiral range vs. wind speed during lock segments. I'm unable to do ligo-proxy-init from the control room computer and don't know of other way to get the BNS range data.

- Guardian does not switch off the Undisturbed intent bit when lock lost.

- IMC lock does not recover on its own after both PSL trips, but recovered just fine after a lock loss that doesn't cause by a PSL trips.

- We have a total lock time of ~20 hours during this 40-hour mini run (started Friday 8AM, ended Sunday at midnight - locking 50% of the time). 

 

I guess that is it for the Mini run. Enjoy the data!

Images attached to this report
H1 General (DetChar)
nutsinee.kijbunchoo@LIGO.ORG - posted 19:50, Saturday 02 May 2015 - last comment - 23:05, Saturday 02 May 2015(18187)
Lock Loss 19:48

Since the initial alignment hasn't been done since last night. I'm redoing the initial alignment. Wind speed looks good so hopefully I can get it back up again soon.

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 19:52, Saturday 02 May 2015 (18188)

Okay maybe not too soon. PSL just tripped....

nutsinee.kijbunchoo@LIGO.ORG - 20:50, Saturday 02 May 2015 (18189)

20:40 PSL untripped but having trouble locking IMC. I cleared all the IMC WFS history but that didn't help. Still working on it.

nutsinee.kijbunchoo@LIGO.ORG - 22:20, Saturday 02 May 2015 (18190)

22:18 Locking again on LOWNOISE_ESD_ETMY at ~11 Mpc. I had to tweak all the IMC optics to get IMC to lock again after PSL tripped. Intent bit switched to Undisturbed at 22:28.

nutsinee.kijbunchoo@LIGO.ORG - 23:05, Saturday 02 May 2015 (18191)

23:01 Lock loss. PSL tripped AGAIN.

H1 ISC (ISC, SEI)
sheila.dwyer@LIGO.ORG - posted 07:05, Friday 24 April 2015 - last comment - 13:59, Sunday 03 May 2015(18035)
Recycling gain

Evan, Sheila

We have been able to lock the IFO at 10 Watts with a recycling gain of 37.  We also think that we can probably improve our inital alingment scheme by adding a servo from POP A to PR3 durring the INput align step.  We've closed loops around ITMX from the TRX QPDs, these were stable for almost an hour before we dropped the lock for other reasons, and helped keep the X arm build up stable as we increased the power.  

Variation on Inital Alingment 

At the beginning of the evening, our alignment resulted in a rather low recycling gain (15 or something) which resulted in difficulty locking.  This was probably because the ITM camera references would have moved 18033.  We have now gone through an initial alignment with some extra steps which brought us back to a decent recycling gain (35 before any manual adjustment or full lock ASC).  

 

  PIT (urad) Yaw
PD1 169.2 -311.4
PD4 134.5 -278.9
mean 151.85 -295.15

 This resulted in a recycling gain of about 35, so it seems like this was a sucsesful approach at least once.  If there is time for some day time commissioning tomorrow, it would probably be helpful to add to the INPUT align state a loop which actuates on PR3 to center the beam on POP A.  Commissioning the dither Align script for the BS to ETMY baffle PDs might also be helpful, but this is a lower priority because we aren't sure that step is necessary.  

Since we have seen this week that many things (CARM offset reduction, violin and roll mode damping, and ASC error signals, possible radiation pressure instability on the ITMs) change when we go from a bad recycling gain to a good one, it seems like we will want to improve our initial alignment scheme enough to consistently bring us to a high enough recycling gain that we can use consistent settings for lock acquisition.  

Avoiding oscillations durring power up

We ran into the oscillation in ITM pitch which we think is due to mis centering and radiation pressure on the ITMs several times tonight.  It seems like we are more stable when the recycling gain is high, we have also slowed down the final CARM offset reduction and the power increase.  

Closing ITM loops

We were able to close loops around ITMX from the QPD error signals we found last night. Here are settings:

DSOFT P (ITMX P) error signal 1.71 TRX A -1 TRX B FM offset 0.08, FM2,3,4 gain -700,000, top mass offloading on

DSOFT Y (ITMX Y) error signal 1.84 TRX A -1 TRX B FM offset -0.1, FM2,3,4,6 gain 600,000, top mass offloading on

both of these loops respond in a 2-3 seconds.  

DARM OLG

Evan made a measurement of the DARM OLG, this was when we still on ETMX, DC readout with low frequency boost, and a recycling gain of 35.  11 Watts input power. 

Now a large earthquake has tripped most of the seismic platforms.  

Non-image files attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 09:57, Friday 24 April 2015 (18048)

While in  full RF lock with a good recycling gain, turn off the green QPD servo and align the Y green beam to the arm manually (or using green WFS feeding back to PZT mirrors), then and set the QPD offsets.

Hopefully this will fix the ETMY green beam position, and makes Y arm initial alignment less convoluted.

evan.hall@LIGO.ORG - 13:59, Sunday 03 May 2015 (18195)

The BS alignment slider values for PD1 and PD4 are switched in this entry. I redid the BS→EY baffle pointing today and found

  P (µrad) Y (µrad)
PD1 134.3 −280.0
PD4 169.5 −314.0
Mean 151.9 −297.0

Also, PD4 has a large dark offset (19.7 µW) compared to PD1 (−0.5 µW). The net power reported by PD4 with the PSL beam pointing onto it is 4.2 µW, and the for PD1 it is 5.2 µW. The settings for both are 0 dB gain, 0.5 A/W responsivity, and 20 kΩ transimpedance.

Displaying reports 65621-65640 of 83348.Go to page Start 3278 3279 3280 3281 3282 3283 3284 3285 3286 End