Displaying reports 51641-51660 of 88221.Go to page Start 2579 2580 2581 2582 2583 2584 2585 2586 2587 End
Reports until 00:02, Thursday 20 July 2017
LHO General
corey.gray@LIGO.ORG - posted 00:02, Thursday 20 July 2017 - last comment - 01:01, Thursday 20 July 2017(37637)
EVE Operator Summary

TITLE: 07/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:

Two mysterious locklosses during the shift with no issues coming back up.
LOG:

Comments related to this report
corey.gray@LIGO.ORG - 01:01, Thursday 20 July 2017 (37643)

As I was leaving, noticed some star gazers parked in front of the LSB.  They were leavin' as I was leaving.

H1 AOS (DetChar)
robert.schofield@LIGO.ORG - posted 22:20, Wednesday 19 July 2017 - last comment - 13:19, Tuesday 25 July 2017(37630)
Why the GW channel detects thirsty black ravens along with colliding black holes

Pep Covas, DetChar, Anamaria Effler, Rick Savage, Robert Schofield

Summary: Ravens peck at the ice on the cryopump GN2 vent lines around the site, and the signal from simulated pecking at EY suggests that this pecking is the source of certain common DARM glitches identified by DetChar.  Evidence from PEM coupling functions, beam tube shaking, P-Cal periscope resonance measurements, and beam-spot perspecive photos, support a hypothesis that the raven pecks vibrate the GN2 vent tube, which is connected to and vibrates the vacuum enclosure and P-Cal periscope, thereby varying the optical path length of light that is scattered from the test mass and reflected back from the P-Cal viewport glass such that it recombines in varying phase with the main beam. The back-reflection of light from the viewport glass is made likely by the position and orientation of the P-Cal periscope mirrors, including the P-Cal beam relay mirrors. So we may still have some noise even if we remove the camera mirrors and baffle the periscope. We request more PEM injection time to study this possibility and for newly identified scattering at EY. The scattering problem might be solved (and we might be able to keep camera mirrors) if we can adjust the mirrors so that the image of the test mass beam spot is not perpendicular to the viewport glass.

DetChar has reported many first round Hvetos for Y-end microphones, such as the ones visible at about 94 Hz in Figure 1. Jordan played the microphone signal for me and I recognized the sound as similar to what I had heard when I found ravens on the outside cryopump/LN2 lines at EY. Last Friday we got some PEM injection time and Pep and I went out to study this coupling to DARM.

We took a closer look at the cryopump lines that I had seen the ravens on, and found many peck marks, consistent with the size of a ravens’s beak, in the ice that accumulates on the cryopump nitrogen gas vent line (see Figure 2). Figure 2 also shows a raven caught in the act of pecking ice, not at EY, but at the corner station. I guess we can’t blame them for desiring shave ice on a hot desert afternoon. Figure 2 also shows Pep chipping at the EY ice to see if such imitation pecking could account for the glitches in DARM.

Figure 3 is a comparison of spectrograms of an EY microphone and DARM for the imitation pecks and the time of the cluster of glitches just before 20:00 UTC in the Hveto plot of Figure 1. The signals on the microphone and the effect in DARM were similar for our chipping and the event from Hveto.

Light insulation on the vent line could allow the nitrogen to warm up slowly without ice accumulation, or, alternatively, a loose sheet metal shell could prevent pecking without icing up.  And there is ice at a different location below the LN2 dewar for desperate ravens.

We repeated one of the standard acoustic injections to compare acoustic coupling to the pre-run PEM injections and to see if measured coupling functions could account for the raven coupling. Figure 4 shows that coupling for acoustic injections has increased since the November measurement, especially at the ~94 Hz peak.

The new coupling function for the –Y mic (6.2e-17m of DARM per Pa of sound pressure at about 94 Hz) underestimates the effect of the bird pecks in DARM, by nearly a factor of ten, while the new coupling function from the BSC10 ACCX (about 2e-8 m/m), for the same acoustic injection, gives a much closer estimate of 1.4 times the actual peak height in DARM (data shown in Figure 5). Thus, the VEA sound level from the pecking doesn’t seem loud enough to account for the effect in DARM, and the coupling route is likely through the direct mechanical connection of the pecked GN2 vent tube to the vacuum enclosure.

We ran the shaker that was set up on the beam tube to excite the P-cal periscope and found a stronger response at ~94 Hz than we had in the past. A look at the resonances measured for the P-Cal periscope at LLO show a strong 93 Hz resonance that was damped with a SUS damping cube (https://alog.ligo-la.caltech.edu/aLOG/uploads/33697_20170512084726_2017-05-11_Phase3a_L1_BSC5_PCAL_Periscope_Vert.pdf ). Because the 94 Hz feature excited by the birds in DARM is excited by somewhat localized shaking in the region of the periscope, a known scattering site, and because of the similar resonance measured for the LLO periscope, it is likely that the peck coupling is produced by scattering associated with the periscope.

A detailed understanding of the scattering may help us ensure that it is corrected for O3. The inability to mitigate the scattering (including the ~94 Hz peak) with black glass in the viewports (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31261) suggests that the problem is not scattering from outside the ports, but from the periscope structure or the viewport glass.   The viewport glass can reflect the light scattered from the test mass directly back to the test mass if the camera and P-Cal beam relay mirrors place the image of the beam spot directly in front of the viewports so that the scattered light path is perpendicular to the viewport. One of my photos from the point of view of the test mass beam spot showed such a retroreflection (https://alog.ligo-wa.caltech.edu/aLOG/uploads/8281_20131027132038_Figure1-ViewFromETMXBeamspot.jpg). Based on the linked and other beam spot perspective photos, I think that the view port glass may be the dominant problem. The relay mirrors place the beam spot image nearly perpendicular to the glass in all 3 paths, including the P-Cal beam, so removing 2 paths, the camera relay mirrors, may not be enough to completely mitigate the retroreflections (not to mention that we would like to keep the camera mirrors). It might be possible to angle the mirrors slightly so that the scattered light hits the viewport at a larger angle. If not, we may need to move the mirrors or add more.

We need more PEM injection time to shake the P-Cal beam viewports in order to see if they are reflecting scattered light.  Also, Pep and I found that exciting the cryopump produced scattering shelves for some resonance that is at a lower frequency than the P-call baffle resonances and we need time to study this.

Non-image files attached to this report
Comments related to this report
andrew.lundgren@LIGO.ORG - 05:43, Thursday 20 July 2017 (37646)
Very nice investigation.

Once upon a desert scorching, ignorant of scientists working,
Over a quaint and curious site of shining machinery did I soar—
   There I landed, gently tapping, disturbing not the machine’s clacking,
   On the chill pipe softly rapping, lapping the ice’s cold succor.
“A cool treat,” I fluttered, “and then away I’ll soar—
           Only this and nothing more.”

Ah, be thou not so craven to name me a common raven;
And dismiss these pecks I’ve graven upon your precious noise floor
   Eagerly I read your logbook, hoping that this humble rook
   Might one day not be overlook’d -- overlook’d in LIGO’s lore-
This this somber, clever avian might find a place in LIGO’s lore-
           Part of science for evermore.
jameson.rollins@LIGO.ORG - 08:28, Thursday 20 July 2017 (37649)

Brilliant!  Both Robert and Andy!

chandra.romel@LIGO.ORG - 13:19, Tuesday 25 July 2017 (37767)

A company came out today to take measurements for an estimate to insulate the GN2 exhaust line to prevent ice build up at both end stations and corner station.

H1 General
corey.gray@LIGO.ORG - posted 21:59, Wednesday 19 July 2017 (37641)
Back To OBSERVING, Missed GRB, REFL Gain Servo Diff

4:11  Had a random lockloss.  It's windy out, but not too bad. 

As were were seconds from getting to NLN, we had a GRB (Swift) & this was confirmed with Will at LLO. 

Also had another H1SYSECATC1PLC2SDF diff similar to yesterday.  It is related to the Refl Servo Gain, and this time we were at 6dB (vs 7dB which was ACCEPTED by me yesterday).  This matches what Thomas wanted from his alog yesterday.  So, perhaps Guardian now accounts for this & we should be good for future locks.

4:51 OBSERVING.

LHO General
corey.gray@LIGO.ORG - posted 20:11, Wednesday 19 July 2017 (37639)
Mid Shift Status

Have some nice triple coincidence going with GEO (& Virgo is locked, but not in OBSERVING).  

Rode through a 5.8 EQ in Japan.  Sustained winds at about 10mph for last 10hrs.

LHO General
corey.gray@LIGO.ORG - posted 16:22, Wednesday 19 July 2017 (37636)
Transition To EVE

TITLE: 07/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 14mph Gusts, 11mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.06 μm/s

Low useism & slight winds.
QUICK SUMMARY:

Ed just finished up an A2L and took us back to OBSERVING while he was handing off to me.

Jenne just finished walking a tour through the Control Room a few minutes ago.

H1 General
edmond.merilh@LIGO.ORG - posted 16:00, Wednesday 19 July 2017 (37634)
Running a2l

22:51 New lock is 1 hr old and LF DARM is looking "off". Livingston was informed.

22:58 Intention Bit back to Undisturbed

 

H1 SUS (CAL, DetChar, ISC, SUS)
jeffrey.kissel@LIGO.ORG - posted 15:28, Wednesday 19 July 2017 (37628)
Charge Measurement Update; Some H1SUSETMY Quadrants Now Have ~50-100 [V] Effective Bias Voltage
J. Kissel

I've measured the effective bias voltages for each quadrant of the ETM ESD systems, as per the usual optical lever angular response method. 

Unfortunately, it looks like several of the quadrants of the ETMY ESD have accumulated an effective bias voltage of (negative) ~50-100 [V] -- a change of about 30-40 [V] since the last measurement on Jun 27 2017 -- namely UL in Pitch, LL in yaw, UR in pitch, and LR in yaw. This corresponds to a 15-20% decrease in angular actuation strength (relative to no effective bias voltage; a 10% change since last measured on Jun 27th). 
See attached 1-year trends of the effective bias voltage and angular actuation strength.

This seems to have not drastically affected the longitudinal actuation strength, as measured by the calibration lines in DARM, which reports only a ~5% increase in actuation strength with respect to when we last updated the actuation strength in the calibration model in January. 
Looking back through the summary pages, one can see a ~1-2% decrease in actuation strength (which corresponds to an increase of the necessary correction factor, kappa_{tst}) between July 6th (when we were hit by the 5.8 Mag Montana Earthquake) and July 9th once we were able to recover the IFO enough to measure with calibration lines. It usually takes a month or two for charge to accumulate a ~1-2% change "naturally." 
I attach four reports from the summary pages, 
     2017-06-28 -- Just after the last charge measurement
     2017-07-06 -- Just before the 5.8 Mag Montana earthquake
     2017-07-09 -- just after the 5.8 Mag Montana earthquake
     2017-07-19 -- today.
The overall h(t) calibration is OK, since we correct for this changing actuation strength.
Note that on Jun 27th, the calibration team switched the GDS pipeline's actuation strength reference from H1 PCALY's RX PD to its TX PD, due to known problems with the RX PD clipping. This was *not* done in the front-end calculation. So the red trace should be trusted, and the gray should be ignored.

So, if you asked me "do you think this drastic effective bias voltage change is from the Montana Earthquake?" 
I would say "The data isn't as dense as we'd like for a definitive statement, but signs point to yes."

This leaves a few questions open:
(1) Can we ascertain the geometric location of a charge source that would impact the actuation strengths as above?
    - Yes, but it'll need a little thinking, and I want to get this data up. Stay tuned.

(2) Is it plausible that that geometric arrangement would cause so little change in longitudinal actuation strength?
    - Yes, but contingent upon answer to (1).

(3) Even with glass tips on all EQ stops, is it still possible that charge can accumulate from a violent earthquake?
    - I don't know enough about the mechanism to say... 

(4) Is there a potential for this effective bias voltage configuration / amount to cause the recent mystery noise (see LHO aLOGs 37616, 37599 and 37590)?
    - Plausible; one might imagine if there's enough effective bias voltage, that coupling to ambient electric fields is larger...
    Remember there are three potential ways that the ESD system is vulnerable to stray charge changing its canonical actuation strength (alpha),
        (a) Charge accumulated in between the test mass and reaction mass, (beta)
        (b) Charge accumulated on areas outside of the gap, on the test mass (beta_2)
        (c) Charge on the surrounding cage (gamma)
    and these angular actuation measurements cannot distinguish between these, as 
        V_eff = (beta - beta_2) / [2 (alpha - gamma)]
    See discussion in T1500467.

(5) Is it worth spinning up the TMDS band-wagon?
    - My vote is no, but this decision should be made with a much more broad audience of input.

For the record, ETMX looks OK (all quadrants' effective bias voltage is below +/-40 [V]), but the data is to sparse to make conclusive statements about whether there was (a) a similar ~30-40 [V] jump, or (b) it was suddenly relative to the Montana quake. The majority of quadrants look to be continuing on the same trend as before; only UL in yaw and LR in pitch are suspicious.
Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 15:21, Wednesday 19 July 2017 - last comment - 15:58, Wednesday 19 July 2017(37627)
SVN Committals du jour

the following were committed by me to the SVN:

 

Comments related to this report
edmond.merilh@LIGO.ORG - 15:30, Wednesday 19 July 2017 (37632)

Some more for the list:

  • /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSITMX.txt      hugh.radkins Jul 10 14:19
  • /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSETMY.txt      jim.warner Jul 10 14:17
  • /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSETMX.txt      jim.warner Jul 10 14:06
jeffrey.kissel@LIGO.ORG - 15:58, Wednesday 19 July 2017 (37635)CDS, SUS
J. Kissel, J. Warner, H. Radkins, Operators

All of the suspension filter changes are from the past few weeks worth of work on violin mode damping. Thanks for cleaning up after us!
H1 General
edmond.merilh@LIGO.ORG - posted 15:15, Wednesday 19 July 2017 - last comment - 16:54, Wednesday 19 July 2017(37626)
Lockloss and Recovery - H1 back to Observing

19:39 H1 lost lock to no obvious cause. Jeff K seized the opportunity to take charge measurements he wasn't able to yesterday. the LLO operator was informed of this activity. They, too, will do some opportunistic work in the interim.

20:57 I needed to re-align the green arms.

21:11 Begin main locking sequence.

22:00 chasing dow PI modes 28 and 26

22:06 Intention bit - Undisturbed 52Mpc

 

Comments related to this report
hugh.radkins@LIGO.ORG - 16:54, Wednesday 19 July 2017 (37638)Lockloss, PEM, SEI

Interestingly, the lockloss is very proximal to the EndY Chiller fault but I can't say they are related.

I trended numerous PEM and ISI channels (some attached) and the CY_STATUS dropped from 1 to 0 at 19:38:37utc, the IFO dropped lock 19:39:29, and PUMPSTAT alarmed at 19:39:40.  There is a large MAINMON glitch when the CY_STATUS changed but no ground seismometer response at the time of lock loss.  I'm not sure about the CY_STATUS relation to the PUMPSTAT.  I stepped through the spectra of the floor STS but see nothing in the broad stroke at which to dig deeper.

Images attached to this comment
LHO FMCS
bubba.gateley@LIGO.ORG - posted 15:01, Wednesday 19 July 2017 - last comment - 15:33, Wednesday 19 July 2017(37629)
E Y Chilled Water Pump Trip
At about 12:45 P M local time the END Y chilled water pump tripped, reason unknown. It was reset at ~ 2:30 P M. The temperature in the VEA rose ~ 1.75 degrees F. during that time.
Comments related to this report
jeffrey.kissel@LIGO.ORG - 15:33, Wednesday 19 July 2017 (37633)CAL, CDS, DetChar, ISC
Tagging relevant parties.
See attached 5-day temperature report to show the change relative to how well we've been doing.
Images attached to this comment
H1 SEI
edmond.merilh@LIGO.ORG - posted 12:40, Wednesday 19 July 2017 (37617)
EQ Report

Terramon is reporting .586um/s from the Tonga region and oddly enough, BLRMS are showing exactly that. Seismon hasn't updated since an Alaskan area quake that happened yesterday.

H1 rode through like a champ.

Images attached to this report
H1 ISC
jenne.driggers@LIGO.ORG - posted 11:06, Wednesday 19 July 2017 - last comment - 13:19, Wednesday 19 July 2017(37616)
Mainsmon coherent enough to subtract low freq noise?!

Looking at the subtraction for today, I noticed that the PEM mainsmon (PEM-EY_MAINSMON_EBAY_1_DQ) was coherent enough to subtract noise at frequencies other than the power lines.  This is pretty unusual, so we're trying to think up things to check, like whether the ETM is much more charged than it used to be.  TVo and Sheila are looking at BruCo to see if anything else looks suspicious.

I'll take a quick look to see if other mainsmon channels are also highly coherent, but this may be an interesting avenue to look at for why we have this extra noise now. 

Of note is that I didn't see this mainsmon subtraction for data from July 15th (alog 37590).

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:39, Wednesday 19 July 2017 (37618)DetChar, PEM

The mainsmon channels also seem more noisy than in the past.  Is this something that we've seen before?

The attached spectra show that the mainsmons are noisier now than they were a few days ago.  Spot checking, the noise was there on July18th, but not July17th.  It's not clear from the time series trends that there is anything different going on.

EDIT: Spot checking more spectra, it looks like the noise may have started on 17July2017, between 20:00 and 21:00 UTC.

Images attached to this comment
thomas.massinger@LIGO.ORG - 12:08, Wednesday 19 July 2017 (37619)DetChar

Josh, TJ

Can you explain how you're finding the broadband coherence between the MAINSMON and h(t)?

The bruco run from today doesn't show anything other than 60 Hz + harmonics: 

https://ldas-jobs.ligo.caltech.edu/~thomas.massinger/bruco_H1_July19_10UTC/PEM-EY_MAINSMON_EBAY_1_DQ.png

We did some spot checking and don't see significant broadband coherence throughout the day, it looks consistent with other days from the last few weeks: 

https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=172856


Blue: 2017-07-19 03:30:00
Yellow: 2017-07-19 01:30:00
Green: 2017-06-30 14:30:00
Red: 2017-07-04 14:30:00

jeffrey.kissel@LIGO.ORG - 12:12, Wednesday 19 July 2017 (37620)
For the record, the analog CDS team reverted the ESD power supplies on July 11th -- see LHO aLOG 37455.
jenne.driggers@LIGO.ORG - 12:52, Wednesday 19 July 2017 (37621)

Hmmm.  Looking at coherence on DTT, I'm also not seeing much.  I was inferring that there would be coherence based on the subtractability of the noise.  As Kiwamu pointed out, perhaps it's a series of glitches or something, where the coupling is constant but the noise isn't, so when you look at coherence averaged over long times, it doesn't show up?

EDIT: It looks like Kiwamu was right, that there was a glitch, probably in the power lines.  I re-did the subtraction in sections of 256 seconds rather than a full 1024, and the first sets were fine and normal (no broad subtraction with mainsmon), and the last set is pretty significant.  So, maybe this is just a regular thing that happens, and I just caught it by accident.  The attached is a spectrum during the time of the glitch.  I assume that the glitch must be on the power lines, since I get such good subtraction using them as my witness.

Images attached to this comment
thomas.vo@LIGO.ORG - 13:13, Wednesday 19 July 2017 (37623)

Sheila and I ran BruCo:

https://ldas-jobs.ligo-wa.caltech.edu/~thomas.vo/bruco_July19/

During this GPS time (1184486418) around 25-35 Hz range, there is a lot of coherence between H1:ASC-OMC_A_PIT(YAW) to DARM.  But spot checking the few hours after with DTT, this seems to go away so maybe there's some transient stuff going on during this time.

Non-image files attached to this comment
thomas.massinger@LIGO.ORG - 13:19, Wednesday 19 July 2017 (37625)DetChar

Looking at a spectrogram of the MAINSMON channel, there are two broadband glitches near the end of the 1024 second stretch from your original plot:

https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=172923

 

H1 CDS
david.barker@LIGO.ORG - posted 10:23, Wednesday 19 July 2017 - last comment - 12:39, Wednesday 19 July 2017(37611)
Virgo alerts are not currently working

Starting at 04:25 PDT this morning (11:25 UTC) the virgo alert system stopped working.

The log file reports a bad request error:

Traceback (most recent call last):
  File "/opt/rtcds/userapps/release/cal/common/scripts/vir_alert.py", line 498, in <module>
    far=args.far, test=args.test))
  File "/opt/rtcds/userapps/release/cal/common/scripts/vir_alert.py", line 136, in query_gracedb
    'label: %sOPS %d .. %d' % (ifo, start, end))
  File "/opt/rtcds/userapps/release/cal/common/scripts/vir_alert.py", line 162, in log_query
    return list(connection.events(query))
  File "/usr/lib/python2.7/dist-packages/ligo/gracedb/rest.py", line 618, in events
    response = self.get(uri).json()
  File "/usr/lib/python2.7/dist-packages/ligo/gracedb/rest.py", line 374, in get
    return self.request("GET", url, headers=headers)
  File "/usr/lib/python2.7/dist-packages/ligo/gracedb/rest.py", line 488, in request
    return GsiRest.request(self, method, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/ligo/gracedb/rest.py", line 356, in request
    return self.adjustResponse(response)
  File "/usr/lib/python2.7/dist-packages/ligo/gracedb/rest.py", line 369, in adjustResponse
    raise HTTPError(response.status, response.reason, response_content)
ligo.gracedb.rest.HTTPError: (400, 'BAD REQUEST / {"error":"Invalid query"}')

 

Comments related to this report
david.barker@LIGO.ORG - 12:39, Wednesday 19 July 2017 (37622)

After discussion with Keita, we will stop monit trying to run vir_alert on h1fescript0 for now. I believe the plan is that these alerts will be added to the standard gracedb database prior to the next V1 engineering run. I have sent emails bringing sysadmins attention to a potential issue with gracedb-test in case other users are being impacted.

H1 General
corey.gray@LIGO.ORG - posted 18:47, Tuesday 18 July 2017 - last comment - 21:55, Wednesday 19 July 2017(37602)
Back to OBSERVING

Took H1 back to OBSERVING at 1:22utc (6:22pm).  Had an SDF Diff, but it was related to the REFL Servo Gain noted by Thomas & Pep.

Running with a range of ~54Mpc.

Comments related to this report
corey.gray@LIGO.ORG - 21:55, Wednesday 19 July 2017 (37640)

Attached is what the SDF Diff was when I ACCEPTED it (but this doesn't match what Thomas notes in his alog).

Here the gain was at 7dB (usually it was 6dB), but Thomas says he changed it vice versa.

Images attached to this comment
Displaying reports 51641-51660 of 88221.Go to page Start 2579 2580 2581 2582 2583 2584 2585 2586 2587 End