Displaying reports 64261-64280 of 85677.Go to page Start 3210 3211 3212 3213 3214 3215 3216 3217 3218 End
Reports until 20:10, Saturday 26 September 2015
LHO General
patrick.thomas@LIGO.ORG - posted 20:10, Saturday 26 September 2015 (21984)
Ops Eve Mid Shift Summary
23:12 UTC Tour in control room
before 23:36 UTC Tour out of control room
23:37 - 23:39:10 UTC Stepped out of control room
23:55 UTC Tour in control room
00:13 UTC Tour out of control room
00:30 - 00:39 UTC Stepped out of control room

7 SUS ETMY saturations. Range is starting to trend down over last hour, now at ~ 65 MPc. Winds have ranged up to 30 mph. Seismic in 0.03 - 0.1 Hz band at end X and end Y has come up to ~ .1 um/s. Corner station is at ~ .01 um/s. Have remained in observation mode since beginning of shift.
H1 DetChar (DetChar)
keith.riles@LIGO.ORG - posted 20:05, Saturday 26 September 2015 - last comment - 10:13, Monday 02 November 2015(21982)
Narrow lines in H1 DARM in O1 week 1
Executive summary: 
  • In regard to narrow lines, early O1 data resembles early ER8 data: a pervasive 16-Hz comb persists throughout the CW search band (below 2000 Hz); there is a notable 1-Hz comb below 100 Hz (0.5-Hz offset); and other sporadic combs persist.
  • On the other hand, there are distinct improvements: noise floor is cleaner nearly everywhere and substantially lower in the 10-70 Hz band; non-linear upconversion around quad violin modes and harmonics is much reduced; some combs and isolated lines have disappeared; and the OMC alignment dither frequencies have moved out of the CW search band (hurray!).
  • Oh the third hand, new artifacts have appeared or strengthened: a sporadic 8-Hz comb suspected before is confirmed; a 1-Hz comb (no offset) has emerged below 70 Hz; a broad bulge appears in the 1240-1270 Hz band.
Details: Using 104.5 hours of FScan-generated, Hann-windowed, 30-minute SFTs, I have gone through the first 2000 Hz of the DARM displacement spectrum (CW search band) to identify lines that could contaminate CW searches. This study is very similar to prior studies of ER7 data and ER8 data, but since this is my first O1 report, I will repeat below some earlier findings. Some sample displacement amplitude spectra are attached directly below, but more extensive sets of spectra are attached in zipped files. One set is for O1 sub-band spectra with labels (see code below), and one set is an overlay of early ER8 spectra (50 hours) and the early O1 spectra. As usual, the spectra look worse than they really are because single-bin lines (0.5 mHz wide) appear disproportionately wide in the graphics A flat-file line list is attached with the same alphabetic coding as in the figures. Findings:
  • A 16-Hz comb pervades the entire 0-2000 Hz band (and well beyond, based on daily FScans)
  • A typically much weaker and sporadic 8-Hz comb (odd harmonics) is also pervasive - previously suspected, now confirmed (all harmonics are labeled in figures, even when not visible)
  • A 1-Hz comb with a 0.5-Hz offset is visible from 15.5 Hz to 78.5 Hz (slightly wider span than before)
  • A new 1-Hz with zero offset is visible from 20.0 Hz to 68.0 Hz
  • A 99.9989-Hz comb is visible to its 8th harmonic (was previously visible to its 13th harmonic)
  • The 60-Hz power mains comb is visible to its 5th harmonic (was previously visible to its 9th harmonic)
  • There is a sporadic comb-on-comb with 0.088425-Hz fine spacing that appears with limited spans in three places near harmonics of 77, 154 and 231 Hz (ambiguity in precise fundamental frequency)
  • There is a 31.4149-Hz comb visible to its 2nd harmonic
  • The OMC alignment dithers have been moved to above 2000 Hz (thanks!)
  • Upconversion around the quad violin modes and their harmonics is much reduced, although the strengths of the higher harmonics themselves remain high. To be more specific, the fundamental and higher harmonics of the upconversion itself (integer harmonics) due to the fundamental violin harmonics are highly suppressed, while the higher harmonics of the violin modes themselves (not integer harmonics) remain high.
  • A number of previously seen combs are no longer apparent: 59.3155 Hz, 59.9392 Hz, 59.9954 Hz and 75.3 Hz
  • A variety of single lines have disappeared, and new ones have appeared (see attached line list)
  • Compared to early ER8 data, the noise floor is slightly lower in most of the band and significantly lower in the 10-70 Hz band, but there is a significant new bulge in the 1240-1270 Hz band
Line label codes in figures: b - Bounce mode (quad suspension) r - Roll mode (quad suspension) Q - Quad violin mode and harmonics B - Beam splitter violin mode and harmonics C - Calibration lines M - Power mains (60 HZ) s - 16-Hz comb e - 8-Hz comb (odd harmonics) O - 1-Hz comb (0.5-Hz offset) o - 1-Hz comb (zero offset) H - 99.9989-Hz comb J - 31.4149-Hz comb K - 0.088425-Hz comb x - single line Figure 1 - 0-2000 Hz (Early O1 data with line labels) Figure 2 - 20-100 Hz sub-band (shows complexity of combs below ~70 Hz Figure 3 - 1300-1400 Hz sub-band (shows how clean the noise floor is away from 8-Hz, 16-Hz lines at high frequencies Figure 4 - 0-2000 Hz (Early ER8 and O1 data comparison, no labels) Attachments: * Zip file with miscellaneous sub-band spectra for early O1 data (with line labels) * Zip file with sub-band spectra comparing early ER8 and early O1 data * Flat-file list of lines marked on figures
Images attached to this report
Non-image files attached to this report
Comments related to this report
keith.riles@LIGO.ORG - 12:53, Monday 28 September 2015 (22027)
A matlab file (37 MB) containing the averaged inverse-noise-weighted spectrum from the first week can be found here: 

https://ldas-jobs.ligo.caltech.edu/~keithr/spectra/O1/H1_O1_week1_0-2000_Hz.mat

Because of the way multiple epochs are handled, the matlab variable structure is non-obvious.
Here is how to plot the full spectrum after loading the file:  semilogy(freqcommon,amppsdwt{1,1})
nelson.christensen@LIGO.ORG - 07:39, Sunday 18 October 2015 (22614)
Keith has found:
"There is a sporadic comb-on-comb with 0.088425-Hz fine spacing that appears with limited spans in three places near harmonics of 77, 154 and 231 Hz (ambiguity in precise fundamental frequency)"

Using the coherence tool, we have seen coherence between h(t) and a number of auxiliary channels that shows this comb around 77 Hz. Seems to be around the input optics, in channels:
H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ  
H1_SUS-ITMY_L1_WIT_L_DQ
H1:SUS-BS_M1_DAMP_L_IN1_DQ      
H1_SUS-ITMY_L1_WIT_P_DQ
H1:SUS-BS_M1_DAMP_T_IN1_DQ          
H1_SUS-ITMY_L1_WIT_Y_DQ
H1:SUS-BS_M1_DAMP_V_IN1_DQ          
H1_SUS-ITMY_L2_WIT_L_DQ
H1:SUS-BS_M1_DAMP_Y_IN1_DQ         
H1_SUS-ITMY_L2_WIT_Y_DQ

See the attached figures.

Nelson, Soren Schlassa, Nathaniel Strauss, Michael Coughlin, Eric Coughlin, Pat Meyers
Images attached to this comment
soren.schlassa@LIGO.ORG - 11:09, Wednesday 21 October 2015 (22673)
The structure at 76.4Hz Nelson listed some channels for above shows up in at least 50 other channels. 

Greatest coherence is consistently at 76.766 Hz, second greatest is (mostly) consistently at 76.854Hz. 

Spacing between the two combs is about 0.0013Hz.

The epicenter seems to be the INPUTOPTICS/the SUS-BS and SUS-ITM* channels, like Nelson said (see below for fuller list).

The plots above are pretty typical, but I have plots for all channels listed and can post any more that are useful. Most or all channels showing the comb with max coherence greater than 0.1 are listed below. Max coherences over 0.2 are marked below as strong, and max coherences under 0.15 as weak. Those marked strongest are around 0.22. I haven't included anything of max coherence <0.1 but I'm sure there are many.

H1:ASC-AS_A_RF36_I_PIT_OUT_DQ (weak)
H1:ASC-AS_A_RF36_I_YAW_OUT_DQ
H1:ASC-AS_A_RF36_Q_PIT_OUT_DQ
H1:ASC-AS_A_RF36_Q_YAW_OUT_DQ (weak)
H1:ASC-AS_B_RF36_I_YAW_OUT_DQ
H1:ASC-AS_B_RF36_Q_YAW_OUT_DQ (strong)
H1:ISI-BS_ST2_BLND_RZ_GS13_CUR_IN1_DQ (strong)
H1:ISI-BS_ST2_BLND_Z_GS13_CUR_IN1_DQ (strong)
H1:ISI-HAM2_BLND_GS13RZ_IN1_DQ
H1:ISI-HAM2_BLND_GS13Z_IN1_DQ
H1:ISI-HAM3_BLND_GS13Z_IN1_DQ (strong)
H1:ISI-HAM5_BLND_GS13RZ_IN1_DQ
H1:ISI-HAM5_BLND_GS13Z_IN1_DQ
H1:ISI-HAM6_BLND_GS13RZ_IN1_DQ
H1:ISI-ITMX_ST2_BLND_RX_GS13_CUR_IN1_DQ (weak)
H1:ISI-ITMX_ST2_BLND_Z_GS13_CUR_IN1_DQ (strong)
H1:ISI-ITMY_ST1_BLND_RZ_T240_CUR_IN1_DQ (weak)
H1:ISI-ITMY_ST1_BLND_Y_T240_CUR_IN1_DQ (weak)
H1:ISI-ITMY_ST2_BLND_RZ_GS13_CUR_IN1_DQ (strong)
H1:ISI-ITMY_ST2_BLND_Z_GS13_CUR_IN1_DQ (strong)
H1:LSC-PRCL_IN1_DQ
H1:PEM-CS_LOWFMIC_LVEA_VERTEX_DQ (strong)
H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ (strongest)
H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ (strong)
H1:SUS-BS_M1_DAMP_L_IN1_DQ (strongest)
H1:SUS-BS_M1_DAMP_T_IN1_DQ (strong)
H1:SUS-BS_M1_DAMP_V_IN1_DQ (strong)
H1:SUS-BS_M1_DAMP_Y_IN1_DQ (strong)
H1:SUS-ITMX_M0_DAMP_R_IN1_DQ (strong)
H1:SUS-ITMX_M0_DAMP_V_IN1_DQ (strong)
H1:SUS-ITMY_L1_WIT_L_DQ (strong)
H1:SUS-ITMY_L1_WIT_P_DQ (strong)
H1:SUS-ITMY_L1_WIT_Y_DQ (strong)
H1:SUS-ITMY_L2_WIT_L_DQ (strong)
H1:SUS-ITMY_L2_WIT_P_DQ (strong)
H1:SUS-ITMY_L2_WIT_Y_DQ (strong)
H1:SUS-MC1_M3_WIT_L_DQ
H1:SUS-MC1_M3_WIT_P_DQ (weak)
H1:SUS-MC2_M1_DAMP_L_IN1_DQ
H1:SUS-MC2_M1_DAMP_T_IN1_DQ
H1:SUS-MC2_M1_DAMP_Y_IN1_DQ
H1:SUS-PR2_M1_DAMP_P_IN1_DQ
H1:SUS-PR2_M1_DAMP_R_IN1_DQ
H1:SUS-PR2_M1_DAMP_V_IN1_DQ
H1:SUS-PR2_M3_WIT_L_DQ
H1:SUS-PR2_M3_WIT_P_DQ (weak)
H1:SUS-PR2_M3_WIT_Y_DQ (weak)
H1:SUS-PR3_M1_DAMP_P_IN1_DQ
H1:SUS-PR3_M1_DAMP_V_IN1_DQ
H1:SUS-PRM_M1_DAMP_L_IN1_DQ (strongest)
H1:SUS-PRM_M1_DAMP_T_IN1_DQ
H1:SUS-PRM_M1_DAMP_Y_IN1_DQ (strong)
soren.schlassa@LIGO.ORG - 23:07, Sunday 25 October 2015 (22825)
The 99.9989Hz comb Keith found (designated H) appears in 109 channels (list is attached). Coherence is uniformly greatest at the ~500Hz harmonic, with many channels approaching .7 and greater, drops off sharply at the ~600Hz and ~700Hz, and is invisible after 700. (See spreadsheet titled "comb_H_sigcohs_wk1.xslx" for a list of cohering channels by line, with coherence value.) 

At all harmonics except the ~300Hz, the structure manifests in the signal and the coherences as two lines .001Hz apart, but if I recall correctly .001Hz is the resolution of the frequency series, so it's safer to say that this is a bulge with .001Hz < width < .002Hz. At ~300Hz, almost all the cohering channels with data in that range show a bulge of width about 0.5Hz (see attached "disjoint_plots" for a comparison of typical channels by harmonic). This bulge, and the fact that it appears in all the same channels associated with the rest of the comb, makes me think that the fundamental may be the bulge at ~300Hz and not the line at 99.9989Hz. An interesting feature of the bulge is that in many cases, it has a prominent upward or downward spike at 299.96Hz, which is just the place the line would be if it were there (see "bulge_w_spike.jpg").

More to come re: changes in week 4 data, patterns in cohering channels, and the spike.
Images attached to this comment
Non-image files attached to this comment
H1 PEM (DetChar)
dale.ingram@LIGO.ORG - posted 18:22, Saturday 26 September 2015 (21983)
Outreach activity report
LHO hosted a public event this afternoon.  Arrival time at LSB = 1:00 - 2:30 PM PM.  Departure time = 3:00 - 5:00 PM.  Group size = ~170 adults/children of all ages.  Vehicles at the LSB = ~50 passenger cars (very uncertain).  A series of three walking tours between 3:00 and 5:00 brought a total of ~120 people into the control room during this time span. 
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 16:49, Saturday 26 September 2015 (21981)
Day Shift Summary

TITLE: 09/26 [DAY Shift]: 15:00-23:00 UTC (08:00-16:00 PDT), all times posted in UTC

STATE Of H1: Observing at ~75 Mpc

SUPPORT: Mike

QUICK SUMMARY: Less 45MHz glitches during my shift. DHARD Y boost turned off (as MIke requested). Wind speed coming below 20 mph. Several small earthquakes throughout the shift.

INCOMING OPERATOR: Patrick

ACTIVITY LOG:

18:07 Jodi to high bay area looking for contamination control stuff. Still observing.

18:14 Jodi out

19:08 Switched the ifo to Commissioning to turn off the DHARD Y boost filter. 

19:09 Back to Observing

22:33 A big tour group starting to march in the control room. ~20 adults. There was also a 5.1M earthquake at Pacific-Antarctic Ridge arrving at about the same time so there were glitches in DARM during the time. Just in case anyone wants to look into outreach noise. 

22:46 Group leaving.

23:00 Handing off to Patrick.

LHO General
patrick.thomas@LIGO.ORG - posted 16:11, Saturday 26 September 2015 (21980)
Ops Eve Beginning Shift Summary
TITLE: 09/26 [EVE Shift]: 23:00-07:00 UTC (16:00-00:00 PDT), all times posted in UTC
STATE Of H1: Observing at ~71 MPc
OUTGOING OPERATOR: Nutsinee
QUICK SUMMARY: Lights appear off in the LVEA, PSL enclosure, end X, end Y and mid X. I can not tell from the camera if they are off at mid Y. Seismic in 0.03 - 0.1 Hz band is coming down from a small peak to ~.7 um/s. Seismic in 0.1 - 0.3 Hz band is around .09 um/s. Wind speeds are less than 20mph, may be coming down.
H1 General
peter.shawhan@LIGO.ORG - posted 16:05, Saturday 26 September 2015 (21979)
GWIstat has a new web location
The LIGO-Caltech systems folks have set up a dedicated account for GWIstat and the associated processes that Chad set up to feed it information about the LIGO detectors, running on the ldas-grid machine at Caltech.  The new URL for the GWIstat display is https://ldas-jobs.ligo.caltech.edu/~gwistat/, and it does not require ligo.org authentication any more.  The old URL now redirects to the new URL.  (At least I think so -- let me know if you run into any problems.)

Due to moving GWIstat to its new location, the durations of the current observing segments are not reported correctly.
H1 INJ (INJ)
cregg.yancey@LIGO.ORG - posted 13:43, Saturday 26 September 2015 (21978)
HWInjReport daily run 1127247535 - 1127333935

Parameters:

GPS Start Time = 1127247535 # Beginning of time span, in GPS seconds, to search for injections
GPS End Time = 1127333935 # Ending of time span, in GPS seconds, to search for injections
Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
IFO Coinc Time = 0.01 # Time window, in seconds, for coincidence between IFO injection events.
Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
Report Normal = True # Include normal (IFO-coincident, consistent, and scheduled for network injections and consistent and scheduled for IFO injections) injections in report
Report Anomalous = True # Include anomalous (non-IFO-coincident, inconsistent, or unscheduled) injections in report

All injections found were UNSCHEDULED CBC injections in H1. There were no injections found in L1. All injections were consistent.

Non-image files attached to this report
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 12:14, Saturday 26 September 2015 (21977)
Turned off DHARD yaw boost

Mike asked me to turn it off to maintain the configuration. So I went off observing for a bit to switch off the boost filter. I accepted the change in SDF and back to observing. All this took less than a minute.

H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 08:38, Saturday 26 September 2015 (21976)
Ops Day Shift Transition Summary

TITLE: 09/26 [DAY Shift]: 15:00-23:00 UTC (08:00-16:00 PDT), all times posted in UTC

STATE Of H1: Observing. The range fluctuates between ~70-40Mpc most likely due to RF45 glitches.

OUTGOING OPERATOR: Ed M.

QUICK SUMMARY: RF 45MHz has been glitching. Wind speed seems to be increasing (now ~30 mph). Seismic activity in earthquake band increasing coresponding to the wind speed. Last earthquake report from Terramon was about an hour ago.

H1 General
edmond.merilh@LIGO.ORG - posted 08:10, Saturday 26 September 2015 (21975)
Shift Summary - OWL

TITLE:  Sep 26 OWL Shift 23:00-07:00UTC (16:00-00:00 PDT), all times posted in UTC

STATE Of H1: Observing

LOCK DURATION: Entire Shift

SUPPORT: Mike Landry

INCOMING OPERATOR: Nutsinee

Activity log:

13:59 After tweaking, 45Mhz RFAM held stable for ~15 minutes. Still glitching but not as frequently.

14:05 looks like a quake is incoming. Engaging Sheila’s DHARD_Y boost.

14:25 Wind on the X arm is picking up to around 16 to 20mph.

14:28 accepted DHARD_Y boost change in SDF and going to go back to observing.

14:31 Intent bit set to Undisturbed


End-Shift Summary: Last half of my shift has been dominated by a continuing loss of range due to constant low frequency glitching in DARM. Mike visited me and we realized that it was the 45Mhz RFAM issue. We toggled the gain a bit as per Stefan’s aLog and then reverted it back. This seems to have lessened the occurrences although it will still happen sporadically. IFO was locked for the entire shift. ETMY glitched twice around 08:00UTC and didn't glitch again for about 4 hours. Then they came at the typical frequency. Mexican EQ showed on the graph so while we were out of Observing I switched on Sheila’s DHARD_Y boost and accepted the change to be able to return to Undisturbed. Neither Terramon nor the USGS site showed the quake before our graph did. nice. Handing off to Nustinee.

H1 INJ (INJ)
cregg.yancey@LIGO.ORG - posted 08:09, Saturday 26 September 2015 - last comment - 15:59, Tuesday 29 September 2015(21971)
HWInjReport daily run 1127163296 - 1127249696

Now that the multi-processing version of HWInjReport is operational and returning results (multi-processing code is an absolute bear!), this is the first of daily reports of analysis of output from HWInjReport. Currently, HWInjReport still has to be run manually and requires one to checkout the current schedule file from the SVN (currently at https://svn.ligo.caltech.edu/svn/dac/hwinj/Details/tinj/schedule; if this has changed, please let me know so I can modify the run script appropriately). Automatic execution of HWInjReport is soon to come.  I've attached copies of the output report file and the schedule file used.  NOTE: the report file is very wide due to the number and size of the columns in the network injections tables of the report.  To examine the report, you will need to either zoom out or change the font size in your browser/text editor to 10pt or less (I'm looking into compressing the columns in the network injections tables in future updates).

The daily run performed with the following parameters:

GPS Start Time = 1127163296    # Beginning of time span, in GPS seconds, to search for injections
GPS End Time = 1127249696    # Ending of time span, in GPS seconds, to search for injections
Check Hanford IFO = True    # Check for injections in the Hanford IFO frame files.
Check Livingston IFO = True    # Check for injections in the Livingston IFO frame files.
IFO Coinc Time = 0.01    # Time window, in seconds, for coincidence between IFO injection events.
Check ODC_HOFT = True    # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
Check ODC_RAW = True    # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
Check ODC_RDS = True    # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
Check GDS_HOFT = True    # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
Report Normal = True    # Include normal (coherent, consistent, and scheduled) injections in report
Report Anomalous = True    # Include anomalous (incoherent, inconsistent, or unscheduled) injections in report

 

NOTE: coherent -> coincident.  Missed changing that in the code where it outputs the report.

The schedule file only has injections spanning 1125280499 - 1126450499.  This is outside the range of times checked by HWInjReport, so there are no occurring or non-occurring scheduled injections reported.

No normal injections, as defined above for HWInjReport, were reported for the network injections.  All injections found were reported as UNSCHEDULED, and all injections occurring were reported as CBC injections.

Two H1-L1 coincident injections were found: CBC 1127175853.757(H1), 1127175853.764(L1) and CBC 1127179822.757(H1), 1127179822.764(L1).  Both injections were reported as UNSCHEDULED but, otherwise, had no other reported anomalies.

H1 had only 1 single-IFO injection, CBC 1127173426.757 (the report file shows 3, but only 1 is actually an H1-only injection.  There is apparently a bug due to the multi-processing code that is not propagating the association of the other 2 injections with their corresponding L1 injections. It's basically a problem of how memory works for a multi-processing environment.)

L1 had 5 single-IFO injections:

The first three injections have the anomaly that they occur in the ODC hoft and GDS hoft frames but not in the ODC raw or ODC rds frames. The remaining 2, other than being UNSCHEDULED, had no other anomalies reported.

 

ADDENDUM: I was able to successfully fix the data propagation bug.  I've attached a copy of the resulting "fixed" report that correctly shows the single-IFO injections for H1 and L1.

Non-image files attached to this report
Comments related to this report
cregg.yancey@LIGO.ORG - 14:33, Tuesday 29 September 2015 (22076)

Peter Shawhan and I examined the anomalies more closely and found they are not anomalies.  The missing injections in RAW and RDS for L1 do actually occur, but HWInjReport missed them.  My current working hypothesis is that the code missed these injections because of how it has to separate the list of files to pass to FrBitmaskTransitions into chunks of no more that 4090 files.  This is to prevent the number of arguments passed to FrBitmaskTransitions, one for each file, from exceeding the number of arguments supported by the OS (I actually ran into this issue at one point with the RAW frame files).  HWInjReport merges the output from the chunks into a single continguous internal list, however, it currently is not accounting for the occurrence doubled transitions (two "off" or "on" transitions consecutively placed) during the process of merging the transitions internally.  This may cause the code to become misaligned when finding the injections, based on the bit transitions, and so it completely misses it.

I am reasonably convinced this is the case because when I performed a run on a time-span around the anomalies, 1127162120 - 1127162970, the anomalies do not occur.  But, this is because the list of files is much smaller and only needs one chunk, instead of several, to be passed to FrBitmaskTransitions.

This also brings another point which is that I need to include all the output files, the report generated, the schedule used, and the log file when I upload files with my alog summaries of HWInjReport, because the log file has a lot of information regarding the internal activity to HWInjReport.  I built it that way because the code has some unexpectedly complex logic in places, which has made debugging a total bear, and it only got worse with the transition to multi-processing.

cregg.yancey@LIGO.ORG - 15:59, Tuesday 29 September 2015 (22084)

I just realized there is another bug in HWInjReport, though this one is somewhat benign.  While HWInjReport is specified to cover only a certain time-span, it actually ends up covering a larger time-span due to the fact that FrBitmaskTransitions processes entire frame files and HWInjReport is processing the resultant transitions into injection events.  This means that HWInjReport can receive from FrBitmaskTransitions a set of transitions that lie well outside the specified time-span and, consequently, generate injection events that lie outside the time-span.  It does not have this issue with the scheduled injections, because it trims those to the specified time-span before doing any further processing.  The fix, fortunately, is simple: just trim the transitions from FrBitmaskTransitions to within the specified time-span.  However, the bug does have the effect of potentially creating injections just outside the beginning or ending of the specified time-span that are flagged as UNSCHEDULED, because the scheduled injections to which they may correspond were trimmed.

H1 General
edmond.merilh@LIGO.ORG - posted 07:44, Saturday 26 September 2015 (21973)
Switched to Undisturbed

14:31UTC Intent bit set to Undisturbed

H1 General (DetChar)
edmond.merilh@LIGO.ORG - posted 07:27, Saturday 26 September 2015 (21972)
Intent bit to 'Commissioning'

Ed, Mike L

13:50UTC addressing RF45 AM issue that has been ongoing for about 4.5 hours. Mike L and I decided to try a reduction in the LSC-MOD_RF_45_AM gain by 1dB to as per Stefan's aLog https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=21716

H1 General
edmond.merilh@LIGO.ORG - posted 05:16, Saturday 26 September 2015 - last comment - 07:46, Saturday 26 September 2015(21970)
Mid-Shift Summary - OWL

Mid-Shift Summary: IFO Locked @ 64Mpc (lower than normal due to funny business visible in DARM). No obtrusive Seismic or wind activity. 2 ETMY glitches. Some increasing activity in the lower DARM frequencies are causing drops in range. It just keeps bouncing up and down (see screenshots) Is this a combination of bounce and roll modes ringing up? This was the same activity that I noted in my transition summary. Is it from anthropogenic noise?

Images attached to this report
Comments related to this report
edmond.merilh@LIGO.ORG - 07:46, Saturday 26 September 2015 (21974)

So this was due to the 45Mhz RFAM issue that H1 has been experiencing. With Mike L's help, I got an education on what it is and how to try and tame it in the days prior to it being rectified once and for all.

H1 General
edmond.merilh@LIGO.ORG - posted 00:11, Saturday 26 September 2015 (21968)
Shift Summary - OWL Transition

TITLE: Sep 26 OWL Shift 07:00-15:00UTC (00:00-08:00 PDT), all times posted in UTC

STATE Of H1: Observing

OUTGOING OPERATOR: Patrick

QUICK SUMMARY:. IFO Locked at 68Mpc/22.9W. No injections are running. All lights are off in LVEA, MID, END and PSL. Wind is <10mph. Microseism seems to be riding steady at ~.1um/s for the last few hours following an earthquake. EQ seismic took a little hop from ~ .2 um/s to .1um/s due to a small earthquake in the Portugal area. It appears that at 07:09UTC there was some raised level of noise activity in DARM from 25Hz and below. This only lasted about 1 minute.

H1 General
patrick.thomas@LIGO.ORG - posted 23:55, Friday 25 September 2015 - last comment - 23:58, Friday 25 September 2015(21966)
Ops Eve End Shift Summary
TITLE: 09/25 [EVE Shift]: 23:00-07:00 UTC (16:00-00:00 PDT), all times posted in UTC
STATE Of H1: Observing, ~67 MPc
SHIFT SUMMARY: Recovered from two lock losses. The cause of the first is unclear. The second was likely from a 6.2 magnitude earthquake in Chile. After recovering from the earthquake I put it into commissioning mode to allow Chris to do hardware injections while LLO was down. He is done and we are back to observing.
INCOMING OPERATOR: Ed
Comments related to this report
patrick.thomas@LIGO.ORG - 23:58, Friday 25 September 2015 (21967)
Terramon and GW Stat on nuc1 are down due to some kind of authentication issue.
H1 INJ (DetChar, INJ)
christopher.biwer@LIGO.ORG - posted 23:53, Friday 25 September 2015 - last comment - 07:38, Monday 28 September 2015(21965)
Hardware injection testing for lower frequency waveforms
We tested a set of waveforms to see if they would saturation the ETMY ESD.

Test the 15Hz waveform

Previously we have tested a waveform that began at 30Hz, see aLog 21838. It was requested we try it from 15Hz instead of 30Hz.

Here are the commands I ran for testing the 15Hz waveform:
ezcawrite H1:CAL-INJ_TINJ_TYPE 1
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 0.1 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 0.25 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 0.5 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 1.0 -d -d >> log3.txt 
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 1.0 -d -d >> log3.txt 
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 1.0 -d -d >> log3.txt

The start times of the injections from the log file (log3.txt):
SIStrOpen: Waveform starts at GPS=1127276638, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127276799, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127277026, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127277293, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127277517, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127277840, epoch=0, sample=0

I did not notice any ESD saturations.

John's waveforms

John V. has also provided 10 waveforms that I tested, see aLog 21964.

Cautiously testing the first waveform

Here are the command I entered as I slowly scaled up the first waveform's amplitude: 
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.2 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.5 -d -d >> log3.txt 
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.75 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.85 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 1.0 -d -d >> log3.txt

The start times for these injections:
SIStrOpen: Waveform starts at GPS=1127278105, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127278209, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127278748, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127279093, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127279520, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127279644, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127280123, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127280433, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127281232, epoch=0, sample=0

The injection that began at 1127280433 was near an ETMY alert from the robot voice. The ETMY alert happened a bit after the injection happened. SO I waited, I repeated the same injection, and there was no alert.

I did one of these injections with a padding of 10 minutes so if the search groups are going to followup one of these injections in more detail this would be a good choice:
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 1.0 -d -d >> log3.txt # gave this guy a bit of time

The start time of this injection is:
SIStrOpen: Waveform starts at GPS=1127281956, epoch=0, sample=0

Testing the other nine waveforms

Then I tested the remaining 9 waveforms by beginning with a scale factor of 0.3333 and incrementing to 1.0. I did these with little spacing between the injections so I do not think this set is worth the analysis groups following up. However, I think the injections with scale factor 1.0 should be looked at for ESD saturation (I believe Andy has a script for that):
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior1_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior1_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior1_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior2_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior2_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior2_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior3_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior3_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior3_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior4_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior4_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior4_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior5_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior5_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior5_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior6_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior6_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior6_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior7_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior7_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior7_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior8_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior8_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior8_1126259455.out 1.0 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior9_1126259455.out 0.3333 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior9_1126259455.out 0.6666 -d -d >> log3.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior9_1126259455.out 1.0 -d -d >> log3.txt

The start times of these injections:
SIStrOpen: Waveform starts at GPS=1127282013, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282066, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282120, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282173, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282226, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282278, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282326, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282377, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282422, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282476, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282517, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282577, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282631, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282681, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282727, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282770, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282819, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127282964, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283007, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283048, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283089, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283160, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283204, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283245, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283292, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283338, epoch=0, sample=0
SIStrOpen: Waveform starts at GPS=1127283440, epoch=0, sample=0

As I did these injections I had the SUS-ETMY_L3_ESDOUTF_LL_OUT channel open in dataviewer. I did not see any injection go above the 90000 counts. The highest was posterior0*.out which was near 80000 counts.
Non-image files attached to this report
Comments related to this report
john.veitch@LIGO.ORG - 02:28, Saturday 26 September 2015 (21969)

I am going to follow up the injections I passed to Chris. Assuming the "start time" is the time at the 1st sample of the injection file (and not the 1st non-zero sample) the end times of the increasing amplitude posterior0 injections should be around

[1127278112.46, 1127278216.46, 1127278755.46, 1127279100.46, 1127279527.46, 1127279651.46, 1127280130.46, 1127280440.46, 1127281239.46, 1127281963.46]
 
and for the scan through posterior injections 1-9 with increasing amplitude they are
[1127282020.46, 1127282073.46, 1127282127.46, 1127282180.46, 1127282233.46, 1127282285.46, 1127282333.46, 1127282384.46, 1127282429.46, 1127282483.46, 1127282524.46, 1127282584.46, 1127282638.46, 1127282688.46, 1127282734.46, 1127282777.46, 1127282826.46, 1127282971.46, 1127283014.46, 1127283055.46, 1127283096.46, 1127283167.46, 1127283211.46, 1127283252.46, 1127283299.46, 1127283345.46, 1127283447.46]
 
I'm going to just run all of these since they should be quite cheap to do. I'll post an update when the runs complete.
andrew.lundgren@LIGO.ORG - 07:38, Monday 28 September 2015 (22015)DetChar, INJ
The only ETMY overflows during the injection periods were:

1127278436.8
1127280154.9 (also overflowed ETMY L2 and OMC DCPD)
1127282847.5

None were related to the injections.
Displaying reports 64261-64280 of 85677.Go to page Start 3210 3211 3212 3213 3214 3215 3216 3217 3218 End