Displaying reports 51781-51800 of 83228.Go to page Start 2586 2587 2588 2589 2590 2591 2592 2593 2594 End
Reports until 16:42, Wednesday 07 December 2016
H1 General
travis.sadecki@LIGO.ORG - posted 16:42, Wednesday 07 December 2016 - last comment - 16:48, Wednesday 07 December 2016(32327)
Ops Eve Shift Transition

TITLE: 12/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68.7782Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.29 μm/s
QUICK SUMMARY:  Observing for 23 hours now.

0:10 Intent bit set to commissioning so Evan can turn off high frequency PCal line for HW inj.

0:11 Evan accepted the new SDF diff for PCal, so we went back to Observe.

0:17 Injection gain ramping dropped us out of Observe, Evan set this gain to 'Not Monitored', and we were back to Observe within the minute

0:34 PCal HF line turned back on, out of Observe.  I am running a2l since it looks like it is time, and Sheila is opportunistically working one of her work permits.
 

Comments related to this report
travis.sadecki@LIGO.ORG - 16:48, Wednesday 07 December 2016 (32331)

Back to Observing at 0:48 UTC.

H1 CAL (CAL)
evan.goetz@LIGO.ORG - posted 16:19, Wednesday 07 December 2016 - last comment - 16:35, Wednesday 07 December 2016(32323)
Long duration high frequency Pcal injection temporarily turned off for stochastic hardware injection
I turned off the 4301.3 Hz Pcal line at 00:10 Dec 8 2016 UTC for the planned stochastic injection. This dropped us from observing intent for a brief time. I updated the SDF and we returned to observing. I will turn the line back on once the stochastic injection has concluded.
Comments related to this report
evan.goetz@LIGO.ORG - 16:35, Wednesday 07 December 2016 (32326)
Pcal line turned back on at 00:35 Dec 8 2016 UTC.
H1 INJ (INJ)
adam.mullavey@LIGO.ORG - posted 16:11, Wednesday 07 December 2016 - last comment - 16:48, Wednesday 07 December 2016(32322)
Coherent Stochastic Hardware Injection

I've scheduled a coherent stochastic injection for 00:20 UTC (16:20 PT). It will take 13 mins. The update to the schedule file is:

1165191617 H1L1 INJECT_STOCHASTIC_ACTIVE 1 1.0 stoch/Waveform/SB_ER10_{ifo}.txt

Comments related to this report
evan.goetz@LIGO.ORG - 16:29, Wednesday 07 December 2016 (32324)
The PINJ_TRANSIENT_GAIN change from 0 to 1 for the stochastic injection knocked us out of observing intent before the start of the injection. We made this channel now unmonitored and went back to observing before the injection began.
adam.mullavey@LIGO.ORG - 16:48, Wednesday 07 December 2016 (32330)INJ

The stochastic waveform was successfully injected into both IFOs. The log file for H1 INJ_TRANS is attached.

Non-image files attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:04, Wednesday 07 December 2016 (32321)
Ops Day Shift Summary
Ops Shift Log: 12/06/2016, Day Shift 16:00 – 00:00 (08:00 - 16:00) Time -  UTC (PT)
State of H1: IFO locked in NOMINAL_LOW_NOISE for past 22 hours. Power at 29.1W. Range is 74.1MPc
Intent Bit: Observing
Support: N/A
Incoming Operator: Travis
Shift Summary: IFO has been locked in NOMINAL_LOW_NOISE and Observing mode for the entire shift. Things have been quite and stable. Took IFO to Commissioning for 2 minutes to restart the Guardian Scheduled Injections. In Stand-Down from 20:05 to 21:50 for two GRB Alerts.    
  
 
Activity Log: Time - UTC (PT)
16:00 (08:00) Take over from TJ
16:50 (08:50) Run A2L check – Coherence is good
17:08 (09:08) Chandra & Kyle – Going to Mid-Y to work on CP4
18:50 (10:50) Jeff K. – Drop out of Observing to restart Scheduled Injections
18:52 (10:52) Back into Observing
20:00 (12:00) Chandra & Kyle – Back from Mid-Y
20:05 (12:05) GRB Alert – On stand down until 21:05
20:50 (12:50) GRB Alert – On stand down until 21:50  
22:10 (14:27) Marc & Filiberto – Going down X-Arm (before Mid Station) transformer room
22:27 (14:27) Marc & Filiberto – Back from X-Arm
22:39 (14:39) Kyle – Going to Mid-Y
23:54 (15:54) Chandra – Going to Mid-X and Mid-Y
00:00 (16:00) Turn over to Travis
H1 ISC
terra.hardwick@LIGO.ORG - posted 16:03, Wednesday 07 December 2016 (32317)
PI mystery double mode quick look at df/f

'Double modes' seen in some PI mode bands are not from test mass resonances, in agreement with model conclusions. Follow up on this .

I've looked at frequency shifting of the peaks seen in the 15060 - 15090 Hz range during 11 hours of the current lock.

Attached plots:

Images attached to this report
LHO VE
chandra.romel@LIGO.ORG - posted 15:50, Wednesday 07 December 2016 (32320)
CP3 overfill

3:48 pm local

Took 30 sec to overfill CP3 by raising LLCV from 18% to 50% open. I lowered back to 17% since there was some pressure at exhaust and fill time was so fast.

H1 PEM
jeffrey.bartlett@LIGO.ORG - posted 15:00, Wednesday 07 December 2016 (32319)
Reset Dust Monitor Alarms

   The dust monitor alarm levels have been set to their correct values. All future alarms should be treated as valid and should be investigated. Please open an aLOG and notify Jeff B.

LHO VE
john.worden@LIGO.ORG - posted 13:40, Wednesday 07 December 2016 - last comment - 14:50, Wednesday 07 December 2016(32315)
cp4 levels

CP4 appears to have joined with the disfunctioning CP3 and is now being investigated by Kyle and Chandra. Until further notice operators should expect false level indications at CP4.

Comments related to this report
chandra.romel@LIGO.ORG - 14:50, Wednesday 07 December 2016 (32318)

CP4 bottom sensing line plugged up this morning after alarming all night. Kyle and I applied up to 180 psig of N2 to the sensing line in an effort to clear the blockage but so far no luck (we've left sensing line under pressure for several hours while watching exhaust pressure).

We performed a manual overfill at 11am by turning LLCV bypass valve 1/2 turn open. Overfill took 1 hour.

I started to install thermocouples at the exhaust line similar to CP3 so we can monitor and fill from control room as we do CP3.

Images attached to this comment
H1 SYS
daniel.sigg@LIGO.ORG - posted 13:22, Wednesday 07 December 2016 (32313)
EtherCAT Error Reporting

Attached is a trend of the corner EtherCAT Device0 channels while there was a broken module on 11/26, see alog 31854. The error can be seen in the ERROR_FLAG, SLAVE_COUNTERROR and the FRAMEWORKINGCNTs. The SLAVECOUNTACTUAL dropped from 345 to below 50—indicating a broken link or module.

On Nov 1 chassis 3 was pulled for some repairs, see alog 31081. The Device0 channels showed similar behavior.

On Nov 15 the power supply was changed for the baffled PD controllers, see alog 31509. This temporarily removed 4 modules from the EtherCAT chain. Again, we can see this clearly in the Device0 channels.

The last plot shows frame rates. Most frames seem to be lost during the above repairs and modifications.

No errors were detected in the end stations.

Non-image files attached to this report
H1 DetChar
jeffrey.bartlett@LIGO.ORG - posted 13:00, Wednesday 07 December 2016 (32314)
GRB Alert

Reveived a second GRB Alert at 20:50 (12:50PT). Both sites in Observing mode. Will extend the hold until 21:50 (13:50PT)

H1 General
jeffrey.bartlett@LIGO.ORG - posted 12:19, Wednesday 07 December 2016 - last comment - 12:23, Wednesday 07 December 2016(32309)
GRB Alert

 Received GRB alert at 20:05 (12:05PT) - LLO received same. Both IFOs in Observing mode. Will observe hold until 21:50.  

Comments related to this report
jeffrey.bartlett@LIGO.ORG - 12:23, Wednesday 07 December 2016 (32310)

Hold will last until 21:05 - Not 21:50

H1 DetChar
jeffrey.bartlett@LIGO.ORG - posted 11:10, Wednesday 07 December 2016 (32308)
Drop Out of Observing

   Dropped out of Observing from 18:50 (10:50PT) to 18:52 (10:52PT) while Jeff K. reenabled scheduled injections.

H1 CAL (DetChar, OpsInfo)
jeffrey.kissel@LIGO.ORG - posted 11:02, Wednesday 07 December 2016 - last comment - 09:14, Thursday 22 December 2016(32307)
PCALX Roaming Calibration Line Frequency Changed to 4001.3 to 4301.3 Hz
J. Kissel for S. Karki
WP #6368

I've moved the PCALX roaming line, its long duration sweep, from 4001.3 Hz to 4301.3 Hz. See schedule status below.

Since it looks like we'll have the duty cycle to just finish the schedule within a week, I'm just going to continue to re-gathering the highest frequency data. As such, Sudarshan has something consistent and straightforward with which to work instead of data with a bunch details or qualifications. 


Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 28 2016 17:20:44 UTC  Nov 30 2016 17:16:00 UTC         days    @ 30 W  
1501.3       35k                      02:00                   39322.0           Nov 30 2016 17:27:00 UTC  Nov 30 2016 19:36:00 UTC         02:09   @ 30 W         
2001.3       35k                      02:00                   39322.0           Nov 30 2016 19:36:00 UTC  Nov 30 2016 22:07:00 UTC         02:31   @ 30 W
2501.3       35k                      05:00                   39322.0           Nov 30 2016 22:08:00 UTC  Dec 02 2016 20:16:00 UTC         days    @ 30 W
3001.3       35k                      05:00                   39322.0           Dec 02 2016 20:17:00 UTC  Dec 05 2016 16:58:57 UTC         days    @ 30 W
3501.3       35k                      05:00                   39322.0           Dec 05 2016 16:58:57 UTC  Dec 06 2016 21:09:56 UTC         ~15:00  @ 30 W
4001.3       40k                      10:00                   39322.0           Dec 06 2016 21:09:56 UTC  Dec 07 2016 18:50:09 UTC         ~20:00  @ 30 W
4301.3       40k                      10:00                   39322.0           Dec 07 2016 18:50:09 UTC
4501.3       40k                      10:00                   39322.0           
4801.3       40k                      10:00                   39222.0           
5001.3       40k                      10:00                   39222.0         

Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W (see LHO aLOG 31546 for caveats)
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC    Nov 18 2016 17:08:49 UTC      days     @ 30 W          
4501.3       40k                      10:00                   39322.0           Nov 18 2016 17:08:49 UTC    Nov 20 2016 16:54:32 UTC      days     @ 30 W (see LHO aLOG 31610 for caveats)   
4801.3       40k                      10:00                   39222.0           Nov 20 2016 16:54:32 UTC    Nov 22 2016 23:56:06 UTC      days     @ 30 W
5001.3       40k                      10:00                   39222.0           Nov 22 2016 23:56:06 UTC    Nov 28 2016 17:20:44 UTC      days     @ 30 W (line was OFF and ON for Hardware INJ)  
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:05, Thursday 08 December 2016 (32360)
Note, PCALX was briefly turned OFF during this 4301.3 Hz stretch. See LHO aLOG 32323.
sudarshan.karki@LIGO.ORG - 10:25, Tuesday 13 December 2016 (32512)

Progress on Analysis:

The Pcal to DARM ratio for these individual lines were calculated using SLM Tool and the result is tabulated below. The Cavity pole and the optical gain on the last column are eyeballed measurement from the CalMon Tool . These time dependent corrections havenot been applied to the sensing function analysis yet.

Freq      Start Time               End Time            FFT       Real       Complex       Coh       CC Pole (O. Gain)

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

1001.3  30-Nov-2016 09:16:44    30-Nov-2016 13:47:04    10       0.022149   -0.358814   0.999589    346.05(0.9863)

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

1501.3  30-Nov-2016 17:28:11    30-Nov-2016 19:36:18    10      -0.017951   -0.109817   0.999943    346.05(0.9863)

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

2001.3  30-Nov-2016 19:36:53    30-Nov-2016 21:01:35    10      -0.015679   -0.044511   0.999391    346.05(0.9863)

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

2501.3  02-Dec-2016 07:52:51    02-Dec-2016 20:16:47    30      -0.011385   -0.020594   0.998321    347.69(0.9703)

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

3001.3  04-Dec-2016 02:27:58    05-Dec-2016 00:00:17    30      -0.007719   -0.010563   0.999057    347.06(0.9614)

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

3501.3  06-Dec-2016 02:27:26    06-Dec-2016 06:10:11    30      -0.005708   -0.005431   0.988492    350.70(0.9793)

3501.3  06-Dec-2016 10:36:18    06-Dec-2016 15:03:35    30                                          350.70(0.9793)

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

4001.3  12-Nov-2016 17:20:18    12-Nov-2016 20:49:17    60      -0.004374   -0.003211   0.996350    350.00(0.9966)

4001.3  12-Nov-2016 09:48:25    12-Nov-2016 16:40:53    60                                          350.00(0.9966)

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

4301.3  18-Nov-2016 05:20:00    18-Nov-2016 12:44:49    60      -0.003607   -0.002212   0.985922    345.04(0.9748)

4301.3  17-Nov-2016 14:26:40    17-Nov-2016 17:20:13    60                                          347.00(0.9730)

4301.3  17-Nov-2016 08:56:40    17-Nov-2016 11:07:35    60                                          347.00(0.9730)

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

4501.3  20-Nov-2016 05:00:00    20-Nov-2016 13:24:30    60      -0.003366   -0.002162   0.990728    350.76(0.9985)

4501.3  19-Nov-2016 15:40:00    19-Nov-2016 23:48:16    60                                          350.21(1.0017)

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

4801.3  22-Nov-2016 07:43:20    22-Nov-2016 16:01:44    60      -0.002883   -0.001369   0.959987    346.89(0.9890)

4801.3  21-Nov-2016 15:20:00    21-Nov-2016 18:22:20    60                                          346.71(0.9979)

4801.3  21-Nov-2016 04:36:40    21-Nov-2016 09:28:48    60                                          346.71(0.9979)

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

5001.3  25-Nov-2016 07:43:17    25-Nov-2016 14:52:54    60      -0.002634   -0.000904   0.973928    348.94(0.9625)

5001.3  27-Nov-2016 11:44:40    27-Nov-2016 18:04:12    60                                          345.48(0.9724)

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

 
Data Files:
aligocalibration/trunk/Runs/ER10/H1/Measurements/DARMOLGTFs/HF_2016-11-12_H1_DARM_OLGTF_A_DARMIN2_B_DARMIN1_coh.txt
aligocalibration/trunk/Runs/ER10/H1/Measurements/DARMOLGTFs/HF_2016-11-12_H1_DARM_OLGTF_A_DARMIN2_B_DARMIN1_tf.txt
aligocalibration/trunk/Runs/ER10/H1/Measurements/PCAL/HF_2016-11-12_H1_PCAL2DARMTF_A_PCALYRX_B_DARMIN1_tf.txt
aligocalibration/trunk/Runs/ER10/H1/Measurements/PCAL/HF_2016-11-12_H1_PCAL2DARMTF_A_PCALYRX_B_DARMIN1_coh.txt
 
Parameter Files:
aligocalibration/trunk/Runs/ER10/H1/params/HF_2016-11-12/
 
Script:
aligocalibration/trunk/Runs/ER10/H1/Scripts/SensingFunction/compareSensingHF.m
Non-image files attached to this comment
sudarshan.karki@LIGO.ORG - 09:14, Thursday 22 December 2016 (32833)

More detailed Analysis.

Non-image files attached to this comment
H1 ISC
daniel.sigg@LIGO.ORG - posted 10:07, Wednesday 07 December 2016 - last comment - 15:30, Monday 12 December 2016(32306)
Jitter Coherence

With the ASC IMC model now running at 16384 Hz we look at the coherence of jitter as measured by the IMC WFS and other channels up to 7.4 kHz. Not sure we can conclude anything except that pointing errros contaminate everything.

We can compare this with an older 900-Hz bandwidth measurement from alog 31631 which was taken before the piezo peak fix (alog 31974).

Non-image files attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 13:45, Wednesday 07 December 2016 (32316)

Note that 1084Hz thing doesn't have coherence with IMC WFS.

Images attached to this comment
andrew.lundgren@LIGO.ORG - 04:42, Sunday 11 December 2016 (32436)
Can you check the DC sum channels for the IMC WFS as well? They are the ones that hVeto keeps finding as related to the 1080 Hz noise, and they see a modulation in the noise rather than a steady spectrum.
keita.kawabe@LIGO.ORG - 15:30, Monday 12 December 2016 (32486)

Done, again nothing for the bump in question though there are coherence bumps for f>1100Hz and f<800Hz.

Images attached to this comment
H1 General
travis.sadecki@LIGO.ORG - posted 00:00, Wednesday 07 December 2016 - last comment - 16:30, Wednesday 07 December 2016(32293)
OPS Eve Shift Summary

TITLE: 12/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 70.7388Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  Pretty smooth shift as far as locking goes.  Some excitement regarding CP4 (see aLog 32283).  Also, set some arbitrarily high thresholds for most dust monitors to stop alarms.  JeffB will reset them tomorrow.  Locked for over 6 hours now.
LOG:

3:35 CP4 alarm

5:24 GRB alert, contacted LLO who verified that they received the alert, begin standdown

6:24 GRB standdown end

7:10 PI mode 27 ringing up, changed phase from 20 to 120.  Did not go out of Observe.  Are we supposed to go out of Observing to make PI mode changes??
 

Comments related to this report
terra.hardwick@LIGO.ORG - 16:30, Wednesday 07 December 2016 (32325)

As of now, you do not need to drop out to change either PI phase or gain. We unmonitored these so they wont drop you out anyway. If PI ever gets so high that it takes more than a phase flip, gain flip, or couple thousand gain increase, you're seeing it in DARM, and you're worried about losing lock, you 'd want to drop out.

H1 ISC (DetChar)
keith.riles@LIGO.ORG - posted 21:28, Tuesday 06 December 2016 - last comment - 05:48, Thursday 08 December 2016(32289)
Narrow lines in H1 ER10 data
As a benchmark against which to compare upcoming O2 data, I have compiled a list
of narrow lines seen in the H1 DARM spectrum up to 2000 Hz, using 107 hours of
ER10 FScan 30-minute SFTs. There are no big surprises relative to the lines and combs
Ansel and I have reported on previously from ER9 and later data, but below are some
observations. 

Attached figures show  selected band spectra, and a zipped attachment
contains a much larger set of bands. Also attached for reference is a plaintext list of combs, 
isolated lines, PEM-associated lines. etc. In the attached spectra, the red curve is the
ER10 data, and the black curve is the full-O1 data. The label annotations are keyed to
the height of the red curve, but in some cases, those labels refer to lines in the O1 data
that are not (yet) visible in accumulated current data. For the most part, lines seen in 
O1 that don't show up in ER10 nonetheless remain for now in the lines list and still
have labels on the graphs that end up in the red fuzz. If they fail to emerge in O2
data, they will be deleted from future line lists.

Observations:
  • As noted previously, the 8-Hz / 16-Hz combs seen in O1 are blessedly gone
  • Thanks to interventions to upgrade timing electronics firmware, the previously dominant low-frequency comb with 1-Hz spacing and 0.5-Hz offset is greatly reduced (but not eliminated)
  • Compared to O1, the non-linear upconversion around quad violin modes and harmonics is much worse in ER10, and it appears that at least some violin mode excitations are affecting the low frequency band in that one sees there a multitude of sparsely distributed doublets, triples and quadruplets of lines with a spacing of about 0.0468 Hz. Andy Lundgren pointed out that this spacing coincides closely with a beat between two 2nd-harmonic violin modes he reported on last week. If I measure / eyeball those frequencies as seen in the ER10 data set, I get 1009.4414 and 1009.4881 Hz, giving a beat of 0.0467 Hz (but with an uncertainty of a few tenths of a mHz), consistent with the explanation. Further credence comes from the proliferation of such doublets / triplets / quadruplets seen in the wings of the quad harmonics (fundamental and higher).
  • There are so many upconverted lines around the quad harmonics that I didn't bother cataloguing them in those regions on the assumption that they will go away in O2 with improved damping (but cataloguing can be revisited later, if needed).
  • With the exception of the violin mode regions, the higher frequency spectrum is generally free of narrow lines (unlike the region below 100 Hz), but one disturbing feature is the presence of non-Gaussian broad disturbances that were not visible in O1. The infamous region around 1083 Hz is one example, as is the 100-200 Hz band.
Figures: [ER10 in red and O1 in black; labels are attached to peaks in the ER10 data] Fig 1 - 0-1000 Hz Fig 2 - 1000-2000 Hz Fig 3 - 2-20 Hz Fig 4 - 20-50 Hz Fig 5 - 50-100 Hz Fig 6 - 100-200 Hz Fig 7 - 490-535 Hz Fig 8 - 1000-1000 Hz Fig 9 - 1800-1900 Hz Other attachments: * zipped file with full set of sub-band spectra * Lines list with label definitions
Images attached to this report
Non-image files attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 12:39, Wednesday 07 December 2016 (32311)DetChar

Here is a plot of the violin mode harmonics around 1kHz, comparing the amplitudes today to the amplitudes right after the damping efforts of Nov 30th. 

We don't actively damp these by default, only when someone manually engages damping do they get damped.   Durring the first part of ER10 ISI trips caused by tidal problems were ringing them up, but that problem is fixed now and most modes are ringing down.  ETMX modes (between 1003 and 1006Hz) have increased in amplitude since the 30th.  

The largest peak here is the pair on ETMY that Keith points out, we have settings that work to damp both of these modes using the mode9 filter bank on ETMY, and it would not be difficult to turn this damping on automatically in the guardian.  

Our question for Keith and detchar is is this (the current spectrum) good enough?  Or should we continue to try to add automatic damping for some of these modes?  

Images attached to this comment
keith.riles@LIGO.ORG - 05:48, Thursday 08 December 2016 (32355)
Automatically damping the violin modes would reduce up-conversion contamination at the starts of
lock stretches, making more data usable for CW searches. Even small excess powers in narrow bins
leads to unnecessary outliers in analysis that waste computing and manpower. Unless there is a 
downside to such damping, it seems warranted.

thanks,
Keith
Displaying reports 51781-51800 of 83228.Go to page Start 2586 2587 2588 2589 2590 2591 2592 2593 2594 End