Displaying reports 53101-53120 of 86440.Go to page Start 2652 2653 2654 2655 2656 2657 2658 2659 2660 End
Reports until 11:46, Tuesday 21 February 2017
H1 CDS
patrick.thomas@LIGO.ORG - posted 11:46, Tuesday 21 February 2017 - last comment - 14:43, Tuesday 21 February 2017(34290)
Conlog frequently changing channels
Attached is a list of channels monitored by Conlog with the number of times each changed over the period of one hour this morning. Each of these channels changed more than 600 times in the hour. I will likely remove these from Conlog unless I hear a strong objection otherwise. These should be updated to be written as readonly in the autoBurt.req files. I understand that this would probably require changing the comments in the Beckhoff code that generates them.

The motivation for removing these is that Conlog has now used approximately 11% of its available disk space of 2 TB in about 2 weeks and 5 days.

A question: What are the guardian channels that end in _WORKER?
Non-image files attached to this report
Comments related to this report
jameson.rollins@LIGO.ORG - 12:01, Tuesday 21 February 2017 (34291)

guardian '_WORKER' channels provide status of the guardian worker subprocess.  They do not need to be tracked by conlog.

The guardian channels that should be tracked by conlog are:

  • _REQUEST
  • _STATE
  • _NOMINAL
  • _OP
  • _MODE
  • _MANAGER
patrick.thomas@LIGO.ORG - 14:43, Tuesday 21 February 2017 (34298)
I removed from Conlog the channels in the list.
H1 PSL
jason.oberling@LIGO.ORG - posted 11:05, Tuesday 21 February 2017 (34289)
PSL Power Watchdogs Reset (FAMIS 3638)

I reset both PSL power watchdogs at 19:00 UTC (11:00 PST).  This closes FAMIS task 3638.

H1 PEM
jeffrey.bartlett@LIGO.ORG - posted 10:45, Tuesday 21 February 2017 (34288)
Monthly Dust Monitor Vacuum Pump Check (FAMIS #7510)

Checked the dust monitor vacuum pumps in the CS and both ends. Adjusted pressures as necessary. All temperatures within normal range.

H1 General (PEM)
cheryl.vorvick@LIGO.ORG - posted 09:50, Tuesday 21 February 2017 (34287)
H1 remains locked during Norco delivery at CP1 (South side of LVEA) - truck injects noise

H1 remained locked while the Norco truck drove to CP1.

This injection of noise into H1 was very similar to the flatbed truck that picked up the frontloader, alog 34102.

H1 General (FRS)
richard.mccarthy@LIGO.ORG - posted 09:40, Tuesday 21 February 2017 (34286)
End Y Entrance Phone Fixed
The phone at EY Ext 239 has been down.  The problem was the Analog driver in the corner station was not supplying enough voltage to the end station.  We have moved the number to different outputs on the unit and moved the wiring at the end station.  The entrance phone and VEA phone are working now.  
LHO VE
chandra.romel@LIGO.ORG - posted 09:02, Tuesday 21 February 2017 (34285)
CP3 LLCV

Lowered CP3 LLCV from 16 to 15% open.

H1 General
travis.sadecki@LIGO.ORG - posted 08:11, Tuesday 21 February 2017 (34284)
Ops Day Shift Transition

TITLE: 02/21 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventitive Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 5mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:  Corey handed off a recently relocked H1.  At 16:03 UTC, I transitioned ISI_CONFIG to VERY_WINDY_NOBRSXY and set OPS_OBSERVATORY_MODE to Preventative Maintenance in preparation for Maintenance Day activities. 

 

LHO General
corey.gray@LIGO.ORG - posted 07:59, Tuesday 21 February 2017 (34274)
OWL Operator Summary

TITLE: 02/21 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY:

Other than a big South American EQ which took H1 & L1 down, had a nice shift.
LOG:

 

Images attached to this report
H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 06:44, Tuesday 21 February 2017 (34283)
Earthquake Report: 6.5 Bolivia, H1/L1 Locklosses
H1 General (SEI)
corey.gray@LIGO.ORG - posted 06:36, Tuesday 21 February 2017 (34282)
14:32 Lockloss due to 6.5 Bolivian EQ

Pretty abrupt lockloss if it was due to the EQ (no heads up on the Tidal striptool).  L1 also lost lock.

Going to LARGE_EQ_NOBRSXY to ride it out for a bit (since the ISI_CONFIG window told me to)....but it looks like this quake is not that bad...may transition sooner rather than later.

H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 04:22, Tuesday 21 February 2017 - last comment - 07:23, Tuesday 21 February 2017(34279)
Earthquake Report: 5.1 Indian Ocean
Comments related to this report
corey.gray@LIGO.ORG - 07:23, Tuesday 21 February 2017 (34280)

OR....

This could be a 4.9 from Mexico which was registered at 11;56utc (and not posted until 12:47utc.  This is probably more reasonable?

LHO General
corey.gray@LIGO.ORG - posted 04:08, Tuesday 21 February 2017 (34278)
Mid-shift Summary

H1 Locked for 8hrs.  Decent range. 

See a 5.1 EQ in Indian Ocean off of eastern Africa.  We'll see if that gives us any grief.

H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 03:39, Tuesday 21 February 2017 (34277)
Earthquake Report: 4.9 or 4.7 EQ?? H1 NOT Affected

 

LHO General
corey.gray@LIGO.ORG - posted 00:25, Tuesday 21 February 2017 (34275)
Transition To OWL

TITLE: 02/21 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 70.1Mpc
OUTGOING OPERATOR: Nutsinee
CURRENT ENVIRONMENT:
    Wind: 4mph
    Primary useism: 0.02 μm/s
    Secondary useism: 0.20 μm/s

Light rain on drive in (most of the snow is finally melted [we've had snow on the ground since early January!]).  useism has been trending down for the last 18hrs.
QUICK SUMMARY:

Nothing noteworthy for hand-off.  L1 had been down but are now making us doubly coincident.  Just a comparison to last night, the fundamental violin mode is an order of magnitude higher than last night (is 2e-18 tonight vs. 2e-19 last night)

H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 00:01, Tuesday 21 February 2017 (34273)
Ops Eve Shift Summary

TITLE: 02/21 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC

STATE of H1: Observing at 69Mpc

INCOMING OPERATOR: Corey

SHIFT SUMMARY: Quiet. One lockloss. No issue coming back up.

 

H1 AOS
sheila.dwyer@LIGO.ORG - posted 22:42, Monday 20 February 2017 (34223)
First look at bullseye QPD, some noise subtraction

Keita, Sheila, Vaishali

Bullseye

On Friday we had a first look at some data from the new bullseye PD we installed this week. The point of installing this detector was to investigate the broad lump of noise which shows up at some interferometer alingments. 

The first attachment shows the RIN measured on the QPD (NSUM) and the HPL diode, the bullseye signal which is labeled here as PIT and roughly calibrated into beam radii, and a yaw signal which is not correctly normalized or calibrated. The second attachment shows coherences.  The bullseye signals is very coherent with intensity noise, and all the signals have small coherence with DARM both at low frequencies and up to nearly a kHz where the broad lump of noise was. (This was measured in our normal observing configuration where we don't see the broad lump of noise.)  The third attachment shows the DAMR spectrum, with predictions for the level of noise based on the coherences with the bullseye detector (DARM ASD *sqrt(coherence))  Since there is a lot of coherence between the bullseye detector and intensity noise, I have also shown the intensity noise projection from the noise budget based on injections into the ISS second loop.

Other noise subtraction

Using the same long coherence data that we got for the bullseye coherences, I did a subtraction very similar to what Keita did in 33650.  I used IMC WFS A+ B DC PIT and YAW, SRCL, PRCL, MICH, all 3 bullseye sensors, and ASC HARD control signals.  At each frequency I used ony the channel that had the highest coherence, and estimated the noise in DARM attributed to that channel as DARM asd*sqrt(coherence). The fourth attached plot shows the estimations for some individual channels and the combined one which is the estimate for the most  coherent signal at each frequency. 

The last attachment shows the DARM spectrum with this signal subtracted (labeled subtraction residual) which looks very similar to Keita's result with only jitter channels subtracted, as well as this subtracted DARM with shot noise also subtracted (shown in green).

 

 

 

 

Images attached to this report
H1 AOS (DetChar, PSL)
miriam.cabero@LIGO.ORG - posted 09:19, Friday 20 January 2017 - last comment - 07:23, Monday 06 March 2017(33446)
Sub-set of blip glitches might originate from PSL

Tom Dent, Miriam Cabero

We have identified a sub-set of blip glitches that might originate from PSL glitches. A glitch with the same morphology as a blip glitch shows up in the PSL-ISS_PDA_REL_OUT_DQ channel at the same time as a blip glitch is seen in the GDS-CALIB_STRAIN channel.

We have started identifying times of these glitches using omicron triggers from the PSL-ISS_PDA_REL_OUT_DQ channel with 30 < SNR < 150 and central frequencies between ~90 Hz and a few hundreds of Hz. A preliminary list of these times (on-going, only period Nov 30 - Dec 6 so far) can be found in the file

https://www.atlas.aei.uni-hannover.de/~miriam.cabero/LSC/blips/O2_PSLblips.txt

or, with omega scans of both channels (and with a few quieter glitches), in the wiki page

https://www.lsc-group.phys.uwm.edu/ligovirgo/cbcnote/PyCBC/O2SearchSchedule/O2Analysis2LoudTriggers/PSLblips

Only two of those times have full omega scans for now:

https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/day/20161204/1164844817-1164931217/scans/1164876856.97/

https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/day/20161204/1164844817-1164931217/scans/1164882018.54/

 

The whitened time-series of the PSL channel looks like a typical loud blip glitch, which could be helpful to identify/find times of this sub-set of blip glitches by other methods more efficient than the omicron triggers:

https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/day/20161204/1164844817-1164931217/scans/1164876856.97/1164876856.97_H1:PSL-ISS_PDA_REL_OUT_DQ_1.00_timeseries_whitened.png

Comments related to this report
thomas.dent@LIGO.ORG - 09:05, Friday 20 January 2017 (33450)
marco.cavaglia@LIGO.ORG - 14:48, Sunday 22 January 2017 (33513)DetChar
I ran PCAT on H1:GDS-CALIB_STRAIN and H1:PSL-ISS_PDA_REL_OUT_DQ from November 30, 2016 to December 31, 2016 with a relatively high threshold (results here: https://ldas-jobs.ligo-wa.caltech.edu/~cavaglia/pcat-multi/PSL_2016-11-30_2016-12-31.html). Then I looked at the coincidence between the two channels. The list of coincident triggers is:

-----------------------------------------------------
List of triggers common to PSL Type 1 and GDS Type 1:
#1:	1164908667.377000

List of triggers common to PSL Type 1 and GDS Type 10:
#1:	1164895965.198000
#2:	1164908666.479000

List of triggers common to PSL Type 1 and GDS Type 2:
#1:	1164882018.545000

List of triggers common to PSL Type 1 and GDS Type 4:
#1:	1164895924.827000
#2:	1164895925.031000
#3:	1164895925.133000
#4:	1164895931.640000
#5:	1164895931.718000
#6:	1164895958.491000
#7:	1164895958.593000
#8:	1164895965.097000
#9:	1164908667.193000
#10:	1164908667.295000
#11:	1164908673.289000
#12:	1164908721.587000
#13:	1164908722.198000
#14:	1164908722.300000
#15:	1164908722.435000

List of triggers common to PSL Type 1 and GDS Type 7:
#1:	1166374569.625000
#2:	1166374569.993000

List of triggers common to PSL Type 1 and GDS Type 8:
#1:	1166483271.312000

-----------------------------------------------------

I followed-up with omega scans and among the triggers above, only 1164882018.545000 is a blip glitch. The others are ~ 1 sec broadband glitches with frequency between 512 and 1024. A few scans are attached to the report.
Images attached to this comment
thomas.dent@LIGO.ORG - 07:08, Monday 23 January 2017 (33531)

Hi Marco,

your 'List of triggers common to PSL Type 1 and GDS Type 4' (15 times in two groups) are all during the known times of telephone audio disturbance on Dec 4 - see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32503 and https://www.lsc-group.phys.uwm.edu/ligovirgo/cbcnote/PyCBC/O2SearchSchedule/O2Analysis2LoudTriggers/PSLGlitches

I think these don't require looking into any further, the other classes may tell us more.

miriam.cabero@LIGO.ORG - 05:22, Tuesday 24 January 2017 (33566)

The GDS glitches that look like blips in the time series seem to be type 2, 7, and 8. You did indeed find that the group of common glitches PSL - GDS type 2 is a blip glitch. However, the PSL glitches in the groups with GDS type 7 and 8 do not look like blips in the omega scan. The subset we identified clearly shows blip glitch morphology in the omega scan for the PSL channel, so it is not surprising that those two groups turned out not to be blips in GDS.

It is though surprising that you only found one time with a coincident blip in both channels, when we identified several more times in just one week of data from the omicron triggers. What was the "relatively high threshold" you used?

marco.cavaglia@LIGO.ORG - 15:29, Friday 10 February 2017 (34050)DetChar
Hi. Sorry for taking so long with this. I rerun PCAT on the PSL and GDS channels between 2016-11-30 and 2016-12-31 with a lower threshold for glitch identification (glitches with amplitude > 4 sigma the noise floor) and with a larger coincidence window (coincident glitches within 0.1 seconds). The list of found coincident glitches is attached to the report. Four glitches in Miriam's list [https://www.atlas.aei.uni-hannover.de/~miriam.cabero/LSC/blips/O2_PSLblips.txt] show up in the list: 1164532915.0 (type 1 PSL/type 3 GDS), 1164741925.6 (type 1 PSL/type 1 GDS), 1164876857.0 (type 8 PSL/type 1 GDS), 1164882018.5 (type 1 PSL/type 8 GDS). I looked at other glitches in these types and found only one additional blip at 1166374567.1 (type 1 PSL/type 1 GDS) out of 9 additional coincident glitches. The typical waveforms of the GDS glitches show that the blip type(s) in GDS are type 1 and/or type 8. There are 1998 (type 1) and 830 (type 8) glitches in these classes. I looked at a few examples in cat 8 and indeed found several blip glitches which are not coincident with any glitch in the PSL channel. I would conclude that PCAT does not produce much evidence for a strong correlation of blip glitches in GDS and PSL. If there is, PSL-coincident glitches must be a small subset of blip glitches in h(t). However, some blips *are* coincident with glitches in the PSL, so looking more into this may be a good idea.
Non-image files attached to this comment
miriam.cabero@LIGO.ORG - 02:13, Wednesday 15 February 2017 (34164)

Hi,

thanks Marco for looking into this. We already expected that it was a small sub-set of blip glitches, because we only found very few of them and we knew the total number of blip glitches was much higher. However, I believe that not all blip glitches have the same origin and that it is important to identify sub-sets, even if small, to possibly fix whatever could be fixed.

I have extended the wiki page https://www.lsc-group.phys.uwm.edu/ligovirgo/cbcnote/PyCBC/O2SearchSchedule/O2Analysis2LoudTriggers/PSLblips and the list of times https://www.atlas.aei.uni-hannover.de/~miriam.cabero/LSC/blips/O2_PSLblips.txt up to yesterday. It is interesting to see that I did not identify any PSL blips in, e.g., Jan 20 to Jan 30, but that they come back more often after Feb 9. Unfortunately, it is not easy to automatically identify the PSL blips: the criteria I used for the omicron triggers (SNR > 30, central frequency ~few hundred Hz) do not always yield to blips but also to things like https://ldvw.ligo.caltech.edu/ldvw/view?act=getImg&imgId=156436, which also affects CALIB_STRAIN but not in the form of blip glitches.

None of the times I added up to December appear in your list of coincident glitches, but that could be because their SNR in PSL is not very high and they only leave a very small imprint in CALIB_STRAIN compared with the ones from November. In January and February there are several louder ones with bigger effect on CALIB_STRAIN though.

thomas.dent@LIGO.ORG - 11:59, Monday 20 February 2017 (34266)

The most recent iteration of PSL-ISS flag generation showed three relatively loud glitch times:
https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/day/20170210/latest/scans/1170732596.35/

https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/day/20170210/latest/scans/1170745979.41/

https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/day/20170212/latest/scans/1170950466.83/

The first 2 are both on Feb 10, in fact a PSL-ISS channel was picked by Hveto on that day (https://ldas-jobs.ligo-wa.caltech.edu/~detchar/hveto/day/20170210/latest/#hveto-round-8) though not very high significance.
PSL not yet glitch-free?

miriam.cabero@LIGO.ORG - 03:28, Tuesday 21 February 2017 (34276)

Indeed PSL is not yet glitch free, as I already pointed out in my comment from last week.

florent.robinet@LIGO.ORG - 06:21, Tuesday 21 February 2017 (34281)

Imene Belahcene, Florent Robinet

At LHO, a simple command line works well at printing PSL blip glitches:

source ~detchar/opt/virgosoft/environment.sh
omicron-print channel=H1:PSL-ISS_PDA_REL_OUT_DQ gps-start=1164500000 gps-end=1167500000 snr-min=30 freq-max=500 print-q=1 print-duration=1 print-bandwidth=1 | awk '$5==5.08&&$2<2{print}' 

GPS times must be adjusted to your needs.

This command line returns a few GPS times not contained in Miriam's blip list: must check that they are actual blips.

miriam.cabero@LIGO.ORG - 06:07, Wednesday 22 February 2017 (34312)

The PSL has different types of glitches that match those requirements. When I look at the Omicron triggers, I do indeed check that they are blip glitches before adding the times to my list. Therefore it is perfectly consistent that you find GPS times with those characteristics that are not in my list. However, feel free to check again if you want/have time. Of course I am not error-free :)

florent.robinet@LIGO.ORG - 00:42, Thursday 23 February 2017 (34339)

I believe the command I posted above is an almost-perfect way to retrieve a pure sample of PSL blip glitches. The key is to only print low-Q Omicron triggers.

For example, GPS=1165434378.2129 is a PSL blip glitch and it is not in Miriam's list.

There is nothing special about what you call a blip glitch: any broadband and short-duration (hence low-Q) glitch will produce the rain-drop shape in a time-frequency map. This is due to the intrinsic tiling structure of Omicron/Omega.

miriam.cabero@LIGO.ORG - 07:23, Monday 06 March 2017 (34606)

Next time I update the list (probably some time this week) I will check the GPS times given by the command line you suggest (it would be nice if it does indeed work perfectly at finding only these glitches, then we'd have an automated PSL blips finder!)

Displaying reports 53101-53120 of 86440.Go to page Start 2652 2653 2654 2655 2656 2657 2658 2659 2660 End