Displaying reports 49721-49740 of 83190.Go to page Start 2483 2484 2485 2486 2487 2488 2489 2490 2491 End
Reports until 09:50, Monday 27 February 2017
H1 PSL
edmond.merilh@LIGO.ORG - posted 09:50, Monday 27 February 2017 - last comment - 10:12, Monday 27 February 2017(34431)
PSL Weekly 10 Day Trends - FAMIS #6137

Everything looks nominal and normal. There is a noticeable increase in PMC Trans power. This is due to increase in diode current power resulting from the most recent trip.  Alignment of the beam into the PMC and temperature tuning still needs to be done.

Images attached to this report
Comments related to this report
jason.oberling@LIGO.ORG - 10:12, Monday 27 February 2017 (34433)

Concur with Ed, everything looks normal.

H1 General
edmond.merilh@LIGO.ORG - posted 08:11, Monday 27 February 2017 (34429)
Shift Transition - Day

TITLE: 02/27 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 16mph Gusts, 13mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.35 μm/s 
QUICK SUMMARY:

H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:00, Monday 27 February 2017 (34428)
Ops Owl Shift Summary
Ops Shift Log: 02/26/2017, Owl Shift 08:00 – 16:00 (00:00 - 08:00) Time - UTC (PT)
State of H1: Locked at NLN, with 62.7 Mpc of range.  
Intent Bit: Observing
Support: N/A
Incoming Operator: Ed

Shift Summary: A2L DTT script shows Yaw is slightly elevated. No bad enough to warrant running the correction script. After several hours, the A2L Yaw has increased quite a bit and Pitch is elevated, as well. Should run the A2L script at first opportunity.

Other than the A2L, there were problems or issues this morning.  

Activity Log: Time - UTC (PT)
08:00 (00:00) Take over from Cheryl
15:05 (07:05) Apollo A/C contractor on site to see Bubba
15:55 (07:55) Bubba – Escorting Apollo to Mid-X for controls upgrade
16:00 (08:00) Turn over to Ed

 

 

H1 General
jeffrey.bartlett@LIGO.ORG - posted 04:10, Monday 27 February 2017 (34427)
Ops Owl Mid-Shift Summary
  Observing for 21:45 hours. A2L Yaw is a bit elevated, but no other concerns noted. Good shift for data taking. 
H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:34, Monday 27 February 2017 (34426)
Ops Owl Shift Transition
Ops Shift Transition: 02/26/2017, Owl Shift 00:08 – 16:00 (00:00 - 08:00) - UTC (PT)
State of H1: IFO locked at NLN, at 31.3W and 64.1 Mpc  
Intent Bit: Observing
Weather: Wind is a Gentle Breeze, overcast, upper 30s  
Primary 0.03 – 0.1Hz: Currently at 0.08um/s
Secondary 0.1 – 0.3Hz: Currently at 0.95um/s 
Quick Summary: Observing for the past 17.5 hours. All appears normal.   
Outgoing Operator: Cheryl
H1 General
cheryl.vorvick@LIGO.ORG - posted 00:03, Monday 27 February 2017 (34425)
Ops Eve Summary:

TITLE: 02/27 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:

 

H1 SUS (SUS)
cheryl.vorvick@LIGO.ORG - posted 18:02, Sunday 26 February 2017 (34423)
Bounce Mode - test of increased gain suggests it would do good with no ill effects

I've used higher gains for Bounce Mode to address an increase after a disturbance like an earthquake.  Recently I increase the gain on relocking, where there was no increase in the Bounce Mode, and results are here:

One attachment with 4 plots:  in all plots red = current gain of 0.1, blue = increased gain of 0.3

In all cases I included Roll Mode, and none were adversely effected during this short test.

Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 17:23, Sunday 26 February 2017 (34422)
Ops Eve Transition

TITLE: 02/27 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY:

 

H1 AOS
edmond.merilh@LIGO.ORG - posted 15:56, Sunday 26 February 2017 (34421)
Shift Summary - Day

TITLE: 02/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:

Quiet shift. Observing 09Hr35min
LOG:

17:56UTC Reset timing error in H1IOPASC0

 

H1 AOS (DetChar)
robert.schofield@LIGO.ORG - posted 14:42, Sunday 26 February 2017 (34420)
Investigation of a scattering shelf that reached 800 Hz

Summary: 1-10 Hz ground motion was increased by a factor of about 10 by a truck and this resulted in a scattering shelf that reached about 800 Hz. The motion frequency that produced the shelf was about 1.05 Hz, near angular resonances for the output Faraday isolator. A possible mechanism for producing such a high frequency shelf is angular motion of an un-dumped beam on distant surface relief.


When the front loader was picked up, the loaded truck made scattering noise in DARM. The spectrum, during part of this period, Figure 1, shows two interesting features, first, that a scattering shelf reached up to at least 700 Hz, very high, and, second, that there was only a single shelf, not a series of stepped shelves, as would be expected from multiple reflections, which is one potential mechanism for producing shelves that reach such high frequencies (see examples from our recent injections: https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=31898 ).

Figure 2 shows spectrograms of the seismic spectrum and the scattering in DARM during this period. The seismic spectrum increased mainly in the 1-10 Hz region. Figure 2 shows that the scattering arches actually reached higher than 800 Hz and that their spacing was close to 2.1 arches per second. Since there are two velocity maxima in every cycle, the frequency of motion producing them was about 1.05 Hz. I looked for correlated motion at 1.05 Hz in all of our monitored optics and did not find it. However, the unmonitored output Faraday isolator has pitch and yaw resonances at about 1.05 Hz (https://dcc.ligo.org/DocDB/0124/E1600080/001/E1600080_OFI_Test_Report_LLO.pdf)  and is thus a possible culprit. Figure 1, along with PRCL and SRCL spectra support the Faraday isolator possibility because there was very little difference at 1 Hz in these spectra, suggesting that the 1Hz motion did not affect these cavities.

The fringe crossing frequency reached over 800 Hz, and, for a 1 Hz motion, this requires an optical path length variation of about 65 um, huge compared to expectations of any of our 1 Hz motions. While the Faraday isolator is unmonitored, the HAM5 table motion during this period was less than a nm in the 1 Hz band, so it is unlikely that the Faraday isolator would be moving 65um at 1 Hz and it is unlikely that we would have any reflectors in our system that would move this much at 1 Hz. Thus it is likely that the scattering path length variation is somehow amplified. One way is by multiple reflections. But for multiple reflections, I would expect a series of shelves with the higher frequency shelves lower in amplitude than the lower frequency ones, both because the losses in the scattering beam should be greater for more reflections, and also because the power is spread out over a greater frequency band. For example, there should also be a shelf at 400 Hz if the 800 Hz shelf was produced by two passes (and the 400 Hz shelf would be larger by the square root of the inverse of the reflection ratio and by the sqrt(2) for the smaller bandwidth).

A second possibility is that the optical path length variation was dominated by motion of the scattered beam across the reflecting surface. One mechanism to convert motion across a reflector into path length variation would be if the reflector were tilted relative to the beam (and it was not specular). Another mechanism could be surface relief. If the scattering noise were produced by, for example, an un-dumped beam from the Faraday isolator, then for an angular motion of the isolator of 100 nR, the scattered beam would move 10 um at 100 m. If the scattering surface were at 45 degrees to the beam, the reflection at one extreme of the angular beam motion would be 10 um further away than at the other extreme.  

The “filled in” nature of the scattering arches suggests a range of optical path length variations below some maximum. This seems consistent with the scanning hypothesis. This would involve path length variation associated with the reflecting surface, rather than path length variation associated with distance from the rotation axis of the scattering optic, which is proposed as a mechanism for “filled in” arches in angular injections here:

https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=31898 .

I think it would be worth making angular injections at LHO HAM5 to study this more (Anamaria and I tried this Friday at LLO but didn’t find scattering - link just above). The potential scattering from the output Faraday isolator may possibly be a problem normally, because the ground motion didn’t increase by much more than a factor of 10 and so the normal shelf may reach 70 Hz or so.

 

Non-image files attached to this report
H1 PSL (PSL)
edmond.merilh@LIGO.ORG - posted 08:37, Sunday 26 February 2017 - last comment - 10:28, Sunday 26 February 2017(34415)
PSL Diode Chiller and Frontend Alarm

16:15UTC I noticed that the Diode Chiller alarm was intermittently flashing RED. When I went into the Diode room I didn't see the light on the unit blinking at all less the frequency at which medm was reporting it. I'm going to add water to it and check the status again. THe frontend warning light is also intermittently flashing. Are the two related? Below is a plot from the last 7 days. I looked back 20 days but saw nothing else.

Images attached to this report
Comments related to this report
edmond.merilh@LIGO.ORG - 08:54, Sunday 26 February 2017 (34416)

16:40 Added 500mL of water to Diode Chiller. Chiller alarm has ceased. Frontend alarm still flashing, frequently, for a couple of minutes following the drink but seems to have ceased as well. Perhaps the two were related after all.

peter.king@LIGO.ORG - 10:28, Sunday 26 February 2017 (34417)
I think you'll find that if the front end laser power dips below 34 W, then the MEDM status
button will flash.
H1 General
edmond.merilh@LIGO.ORG - posted 08:08, Sunday 26 February 2017 (34414)
Shift Transition - Day

TITLE: 02/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.24 μm/s 
QUICK SUMMARY:

 

H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:06, Sunday 26 February 2017 - last comment - 12:30, Sunday 26 February 2017(34413)
Ops Owl Shift Summary
Ops Shift Log: 02/25/2017, Owl Shift 08:00 – 16:00 (00:00 - 08:00) Time - UTC (PT)
State of H1: Locked at NLN, with 62.7 Mpc of range.  
Intent Bit: Observing
Support: N/A
Incoming Operator: Ed
 
Shift Summary: A2L DTT script shows yaw is elevated. Will run the A2L script if LLO drops out of lock. Ran the A2L script while LLO was recovering from a Lockloss.  
   PI Mode 23 rang up and one minute later lost lock. At the time of the lockloss the End-X seismic (3-10 and 10-30 Hz) spiked off the top of the chart. Relocked with no problems. Damped PI Mode 27.  
   After relocking, the remainder of the shift was uninterrupted Observing.
 
Activity Log: Time - UTC (PT)
08:00 (00:00) Take over from Cheryl
09:08 (01:08) Drop out of Observing to run A2L script
09:16 (01:16) Back in Observing
13:59 (05:59) PI Mode 23 ringing up
14:00 (06:00) Lockloss –
14:22 (06:22) Relocked at NLN
14:25 (06:25) Damped PI Mode 27
16:00 (08:00) Turn over to Ed
Comments related to this report
krishna.venkateswara@LIGO.ORG - 12:30, Sunday 26 February 2017 (34419)DetChar, SEI

The lockloss at ~14:00 UTC was likely caused or related to this 3.5 M earthquake: http://earthquake.usgs.gov/earthquakes/eventpage/uw61252706#executive

This was an unusual event: short but strong high-frequency seismic waves. It should be an interesting case to analyze.

H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 00:42, Saturday 25 February 2017 - last comment - 09:47, Monday 27 February 2017(34395)
PSL Down!

Just as I submitted the Shift Transition Summary, the PSL Went Down (Flow Sensor #1 for Crystal Chiller; with the cap popping off & water geyser-ing out).

I have put us in the CORRECTIVE MAINTENANCE Observatory Mode State.

I left a voicemail with Jason at 12:38am local time.  This requires a PSL Expert for recovery.  Once we have a PSL Expert available to assist, it should take us ~30-60min to get the PSL back and then another 30-60min to get H1 back to NLN.  

I've also appraised the LLO Operator of our status.  

Comments related to this report
corey.gray@LIGO.ORG - 03:50, Saturday 25 February 2017 (34397)OpsInfo, PSL

Lockloss at 8:38utc.

Got a hold of Jason.  On phone with Jason from 2:35-3:10am to restore the PSL.  Some Notes:

  • He had trouble ssh-ing into the usual opsws1 & 2 computers.  Able to ssh into opsws12 (even though it had an odd message)
  • "Head 1 Flow Error" (again)
  • Topped Off Crystal Chiller with 400mL of water
  • Jason needed to bump up pump diode currents for pump diode boxes (something he planned to do on next maintenance day).
  • Out for CORRECTIVE MAINTENANCE from lockloss to NLN for about 3hrs.
  • New FRS created:  #7499
  • 11:08utc (3:08am)Back to locking
    • One oddity:  Had an HAM6 ISI WD Trip during the DRMI_ASC_OFFLOAD step!
  • ACCEPTED SDF difs for:
    • ISS RefSignal:  was -1.03, now -1.14.
    • CS ECAT PLC2:  H1:IMC-REFL_SERVO_IN1GAIN  was -7, now -8.  Can we ignore this channel?  It's been changing by 1.0 every lock lately.

Back to OBSERVING at 11:44utc (3:44amPST)

david.barker@LIGO.ORG - 11:02, Saturday 25 February 2017 (34402)

opsws1 and opsws2 have been replaced by zotac machines with new names. Best to use opslogin when logging in remotely.

david.barker@LIGO.ORG - 11:07, Saturday 25 February 2017 (34403)

I could not reproduce the problem with opsws12

vernon.sandberg@LIGO.ORG - 08:31, Monday 27 February 2017 (34430)

FRS ticket is: Ticket 7499 - PSL Tripped Due To Head 1 Flow Error

https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=7499

 

jason.oberling@LIGO.ORG - 09:47, Monday 27 February 2017 (34432)

This trip appears to have been caused by the flow reading from the Laser Head 3 flow sensor dropping below the trip point and therefore tripping the "Laser Head 1-4 Flow" interlock.  This is in contrast with the previous trips from 2-20-2017, which were caused by the flow reading from the Laser Head 2 flow sensor dropping below the trip point.  The first attachment shows all of the active laser head flow sensors as well as the "Laser Head 1-4 Flow" interlock that caused the trip.  It is obvious that the flow read by the Laser Head 2 flow sensor was the cause of the interlock trip.  The second attachment is a slightly zoomed in view of the Laser Head 3 flow sensor signal and the "Laser Head 1-4 Flow" interlock.

In addition, while restarting the laser I had difficulty injection locking the PSL; it took 3 attempts to injection lock the PSL.  I believe this was due to drop in laser power due to the natural decay of the output power of the pump diodes.  To alleviate this I increased the HPO pump diode currents by 0.5A each.  I had planned to do this during the 2-28-2017 maintenance window, but it was necessary at this time to maintain stability of the injection locking.  In the interest of returning to OBSERVING ASAP, I did not temperature tune the pump diodes; this will be done during the 2-28-2017 maintenance window.

Images attached to this comment
H1 ISC (IOO, ISC, PSL)
kiwamu.izumi@LIGO.ORG - posted 17:01, Friday 24 February 2017 - last comment - 11:26, Monday 27 February 2017(34389)
Beam size jitter coupling as a function of PR3 spot position

[Vaishali, Kiwamu, Sheila(remotely)]

WP 6497

Sheila suggested us doing an interesting test today during the commissioning time window. The measurement we did is a coherence measurement between the bullseye sensor and DARM while changing the PR3 spot position.

The result suggests that a part of the broadband lump in 200 Hz-1 kHz is due to beam size jitter with a caveat that we couldn't fully reproduce the broadband lump.


[Background]

Back in pre-O2 commissioning, we had unidentified broadband noise in 200 Hz - 1 kHz (e.g. alog 30752) which was found to be a function of the PR3 spot position. One hypothesis was beam size jitter somehow coupling to OMC DCPDs.

[The measurements and results]

We tested three different PR3 spot positions, all of which is characterized by POP_A QPD readouts as follows.

Our intention was to reproduce what Sheila observed in this past November (31628) with a hope to reproduce the broadband lump. However, we didn't get drastic increase in the frequency band -- we only obtained a 18% increase at around 400 Hz. See the second attachment for the increased DARM noise. Despite different alignment, configurations (B) and (C) gave almost identical DARM noise. Increased noise below 30 Hz is presumably due to mistuned A2L couplings, as we have moved the spot position.

The first attached figure shows the coherence between the bullseye sensor (sorry for any confusion, but PIT = beam size jitter, YAW = horizontal pointing jitter). The dashed lines are the ones from configuration (A). Notice that they are almost at the same level as the previous measurement (31628). The solid lines are the ones from configuration (B). Those from configuration (C) are not shown as they are almost identical to configuration (B). As we have moved the PR3 spot position, the coupling of beam size jitter increased while the horizontal jitter coupling reduced. The coherence for beam size jitter became 0.05-ish above 300 Hz corresponding to a fractional contribution of 22 % to the DARM amplitude spectral density. Also, at the same time, the power recycling gain improved which is consistent with what Sheila observed.

These results indicate that broadband noise is more or less reproducible, and also, a part of broadband noise is due to beam size jitter.

Later, we tried further exploring the parameter space of the PR3 spot position to see if we can further elevate noise in 200 Hz - 1 kHz. This lead to a lockloss presumably due to too much misalignment on PRM when we were at (POP_A_PIT, POP_A_YAW) = (-0.3, +0.6). We couldn't find a location where the broadband lump becomes more prominent.

[A minor change in bullseye signals]

Besides, we made minor modifications on the bullseye settings.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 07:04, Saturday 25 February 2017 (34398)IOO, ISC, PSL

Another caveat:

Later, Keita pointed out that we shouldn't have put a low pass in the sum channel because it spoils the dynamic cancelation of intensity noise. However, if this theory holds, the implementation of the low pass shouldn't decrease the coherence between PIT and SUM as it allows for intensity noise to contaminate both channels in a same way. But we saw a significant decrease in the coherence by a factor of 100 or so. We will get back to this point in the next week and assess what is going on.

daniel.sigg@LIGO.ORG - 11:07, Sunday 26 February 2017 (34418)

With single precision floating point representation and two poles at 30 mHz anything above ~30 Hz is probably bit noise.

kiwamu.izumi@LIGO.ORG - 11:26, Monday 27 February 2017 (34435)

A follow up on the beam size jitter measurement.

So far the data seems still consistent with the hypothesis that excess noise in 200 - 1000 Hz is due to beam size jitter which happens to be coherent with intensity noise at the output of the high power oscillator (HPO).


The first attachment is a screenshot of plots showing the coherence of DARM with some relevant intensity noise channels. The data is from configuration (C), see the above entry for details. The below is a list of remarks on the plots.

  • Intensity fluctuation at the output of the high power oscillator (PSL-PWR_HPL_DC) is also coherent with DARM with a coherence of 0.04 which is as coherent as the bullseye sensor output.
  • The second loop ISS sensors didn't see a high coherence, indicating that the actual DARM contamination is not via a simple intensity noise coupling.
  • As pointed out by Sheila et al (34223), beam size jitter has been showing a high coherence with intensity fluctuation even when there was no low pass in the normalization.
    • This likely means that beam size jitter is coherent with intensity fluctuation.
  • These observations suggest that it can be beam size jitter which contaminated DARM.

 

Images attached to this comment
H1 SEI (PEM)
hugh.radkins@LIGO.ORG - posted 10:44, Friday 24 February 2017 - last comment - 10:55, Monday 27 February 2017(34380)
EndY PEM T240 Mass Center checked--Okay, not centered

Checked the mass centering on the T240 Deployed Wednesday, but I did not center them.

Day                U       V       W

Wednesday 0.12  0.09  0.02V

Friday          -.11   -.22   -.32

So the warm up of the springs is evident on the mass positions but it is still within comfortable range.

It will need re-centering when we put the T240 into the BRS enclosure (Tuesday.)

Comments related to this report
hugh.radkins@LIGO.ORG - 11:12, Friday 24 February 2017 (34381)

Here is spectra for the T240 (current ADC_0_ traces) compared to the ISI gnd STS (insulated) and from the PEM STS inside the BRS enclosure (Reference ADC channels.)  I'll attribute the difference at low frequency to the un-insulated state of the T240 and when inside the BRS (maybe it will get some extra insulation then) it will compare better at lower frequencies.

Images attached to this comment
krishna.venkateswara@LIGO.ORG - 16:50, Friday 24 February 2017 (34390)

I'm a bit surprised they don't agree more at the microseism but there may be a scale factor mismatch between the two seismometers. It would be good to look at the coherence between the two.

But the T240 does look better at low frequencies and is more promising. One thing I thought was interesting was the difference at high frequencies between the on-floor seismometers and the BRS-platform seismometer. The BRS-platform has three swivel-feet with ~3 mm rubber shims under them, resulting in increased motion between 10-50 Hz and maybe reduced motion at higher frequencies. Perhaps the feet could be redesigned to reduce this motion.

hugh.radkins@LIGO.ORG - 10:55, Monday 27 February 2017 (34434)

Here is this morning's look at the PEM T240 located on the floor next to the BRS (opposite side of the BRS to the ISI_GND_STS.

The PEM ADC is a bit unknown to me so like before when I made the PEM STS equal to the ISI GND STS by using a gain proportional to the ratio of the ISI STS/PEM STS amplitude at the useism, I now multiplied that scale factor by 5/4 (the ratio of the STS/T240 sensitivity.)  If you compare this ASD with that in aLog 34381, one might argue the traces are more similar at the useism.  Edit--added Coherence.

Tomorrow, this T240 will be moved into the BRSY enclosure replacing the STS that has been giving me troubles for the past few weeks.

Images attached to this comment
Displaying reports 49721-49740 of 83190.Go to page Start 2483 2484 2485 2486 2487 2488 2489 2490 2491 End