Displaying reports 49401-49420 of 83210.Go to page Start 2467 2468 2469 2470 2471 2472 2473 2474 2475 End
Reports until 13:02, Monday 13 March 2017
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 13:02, Monday 13 March 2017 (34788)
CDS O2 restart report: Friday 10th - Sunday 12th March 2017

model restarts logged for Sat 11/Mar/2017* No restarts reported

model restarts logged for Sat 11/Mar/2017 No restarts reported

model restarts logged for Fri 10/Mar/2017 No restarts reported

Note that the reporting code mistakenly reported Sun as Sat in this morning's report. This is because LHO transitioned from PST to PDT at 02:00 Sunday. My code runs at 5 minutes past midnight, and goes back a period of 24 hours to get the previous day's date. When it ran at 00:05 PDT this morning, going back 24 hours ( convert to GPS, subtract 24*60*60 seconds) effectively goes back 25 hours to 23:05 Sat 11th. Other uses of relative time spanning this period may have similar surprises.

H1 DetChar (DetChar)
borja.sorazu@LIGO.ORG - posted 12:27, Monday 13 March 2017 (34787)
DQ Shift: Thursday 9th March 00:00 - Sunday 12st March 23:59 (UTC)

Summary of the DQ shift from Thursday 9th March to Sunday 12th March (inclusive), click here for full report:

* The DQ Shift started with a duty cycle of 76%, which increased to 86%, 95% and on Sundaw went back down to 60% due to extreme weather conditions of high Wind and microseism ground motion.

* Range sensitvity mainly around 65 Mpc, with the excepcion of Friday which most time around 60MPc due to strong Winds.
* Weather conditions has had an impact on range sensitivity and range during this DQ shift.
* Not many locklooses; some due to PI ringing up, other was preceded by soft. sat. of H1:LSC-X_ARM_CTRL, others high winds and micoseism ground motion.
* Script 'a2l' has been run quite a few times during this shift due to the common presence of low freq. noise (10-20Hz), which mostly had not impact on range sensitivity.
* A few Earthquakes which caused not much problem.
* IMPORTANT: Driving PI mode 23 (for instance when applying damping filters) caused glitchy narrow lines at (14.5, 64.0, 78.5 and 142.5 Hz), this dominated Omicron glitchgram with a 60-80Hz band of high SNR glitches. Commissioners have noticed this an put in place a practice of not damping this mode anymore unless required for lock acquisition.
* IMPORTANT: The Gold Star Omicron glitch for the whole of Friday was a blip glitch coincident with all quadrants of H1:SUS-ETMY_L2_NOISEMON, and the highest New SNR glitch for Sunday reported by PyCBC? live 'short' was of this type too. This relates to the alog entry by Miriam, Hunter, Andy where it was reported evidence that 'Some blip glitches may be due to ETMY L2 coil drive'.
* Observed high SNR glitches caused by scattering of SUS-SRM and SUS-PRM
* Increased limits of the X and Y arm LSC tidal HEPI off load for tidal control.
* PLS tripped with standard Flow-1 error, which was caused by the drop in flow rate in head 3. This was quickly solved.
* On Sunday high winds and microseism caused repeated tidal alarms "Tidal X/Y error" as the tidal arm servos were railing at their limits (solved by increasing their range), this had an impact in lock acquisition.
* On Sunday 'a2l' script did run with errors due to execution permissions, leaving the Gains to some random values worse than when the script started which increased low frequency noise. The permissions issue will be soon looked up and the script may be modified such that when errors occur the Gain values should be reverted to the ones at the start.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 12:15, Monday 13 March 2017 (34786)
Ops Day Mid-Shift Summary
   In Observing for past 12 hours. Environmental conditions are good. No issues or concerns at this time. 
LHO VE
logbook/robot/script0.cds.ligo-wa.caltech.edu@LIGO.ORG - posted 12:10, Monday 13 March 2017 - last comment - 14:39, Monday 13 March 2017(34784)
CP3, CP4 Autofill 2017_03_13
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 2192 seconds. TC B did not register fill. LLCV set back to 19.0% open.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 2276 seconds. TC A did not register fill. LLCV set back to 41.0% open.
Images attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 14:39, Monday 13 March 2017 (34792)

Increased each by 1%. CP3 now 20% open and CP4 42% open.

H1 AOS
jeffrey.bartlett@LIGO.ORG - posted 09:54, Monday 13 March 2017 (34783)
09:30 Meeting Minutes
   Reviewed the the work permits for Tuesday's maintenance window
    - The PSL will be down for most of the window
    - Expecting 2 Nitrogen deliveries on Tuesday
    - There will be tumbleweed baling On Monday & Tuesday

   Tumbleweed baling Monday along the Y Arm


H1 SEI
jeffrey.bartlett@LIGO.ORG - posted 09:49, Monday 13 March 2017 (34782)
Mag 5.3 Earthquake near Ovalle, Chile
Mag 5.3 Earthquake near Ovalle, Chile

    Seen on USGS, Seismon, and Terramon
    USGS - Mag 5.3 EQ at 15:05 UTC
    Terramon - Mag 5.1 EQ at 15:00 UTC, Predicted R-Wave of 0.822um/s arrival 15:52
    Rise in the BLRMS around 15:17 UTC; Primary microseism peak of 0.1um/s
    No apparent effect on H1
H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:22, Monday 13 March 2017 (34779)
Ops Day Shift Transition
 
Ops Shift Transition: 03/13/2017, Day Shift 15:00 – 23:00 (08:00 - 16:00) - UTC (PT)
State of H1: IFO locked at NLN, at 29.3W and 63.4 Mpc  
Intent Bit: Observing
Weather: Wind is up to a Gentle Breeze, Overcast, and Upper 40s  
Primary 0.03 – 0.1Hz: 0.01um/s 
Secondary 0.1 – 0.3Hz: At 0.2um/s
Quick Summary: In Observing for the past 8 hours. Observing conditions are good.   
Outgoing Operator: Jim
H1 General
jim.warner@LIGO.ORG - posted 07:59, Monday 13 March 2017 (34778)
Shift Summary

TITLE: 03/13 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Quiet shift
LOG:
Travis had it locked when I arrived, it's still locked as I leave. EY vacuum was alarming all night, otherwise nothing to report. 

LHO VE
kyle.ryan@LIGO.ORG - posted 00:00, Monday 13 March 2017 (34777)
CP7 dewar level alarm
CP7 dewar level alarm is due to the level being below 20% -> Accumulated tumbleweeds obstructing the Y-arm access road last Tuesday caused the cancellation of the originally scheduled LN2 delivery.  Rescheduled delivery is for this Tuesday.  No action is required by the CR operator.
H1 General
travis.sadecki@LIGO.ORG - posted 00:00, Monday 13 March 2017 (34776)
Ops Eve Shift Summary

TITLE: 03/13 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:  One lockloss due to PSL trip.  One unknown cause lockloss.  I did have a couple of Tidal X and Y error again tonight during relocking, but they stopped without intervention.  Otherwise a quiet night.  I did get a call from both Chandra and DaveB about CP7 alarms, although I did not receive any alarms in the control room.  Chandra advised to ignore these alarms until Tuesday since the dewar was not filled last Tuesday due to tumbleweed blockage, hence the low level.
LOG:  See previous aLogs.

H1 General
travis.sadecki@LIGO.ORG - posted 23:51, Sunday 12 March 2017 (34775)
Observing at 6:51 UTC

No issues coming back up. 

H1 General
travis.sadecki@LIGO.ORG - posted 22:52, Sunday 12 March 2017 (34774)
Lockloss 5:50 UTC

Cause unknown.  FOMs look good and environment is quiet.

H1 General
travis.sadecki@LIGO.ORG - posted 20:17, Sunday 12 March 2017 (34773)
GRB alert 3:06 UTC

Begin 1 hour standdown.

H1 General
travis.sadecki@LIGO.ORG - posted 19:36, Sunday 12 March 2017 (34772)
Observing at 2:36 UTC

No issues coming back up after PSL restart.

H1 General
travis.sadecki@LIGO.ORG - posted 17:43, Sunday 12 March 2017 - last comment - 19:08, Sunday 12 March 2017(34770)
Lockloss 0:40 UTC

PSL tripped. Calling Peter.

Comments related to this report
peter.king@LIGO.ORG - 19:08, Sunday 12 March 2017 (34771)PSL
Head 3 flow rate looks to be the cause.  Attached are two trend plots: one for the past 2 hours and one for the
past 12 hours.  The flow rate looked pretty clean for the past 12 hours before getting ragged.

    If there were any bubbles in the system because of yesterday's trip, this would be a good candidate for one.
Images attached to this comment
H1 General
travis.sadecki@LIGO.ORG - posted 16:30, Sunday 12 March 2017 (34769)
Ops Eve Shift Transition

TITLE: 03/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY:  No issues handed off.  Looks like a much better start to the night than last night.

 

H1 General
jeffrey.bartlett@LIGO.ORG - posted 15:59, Sunday 12 March 2017 (34768)
Ops Day Shift Summary
Ops Shift Log: 03/12/2017, Day Shift 15:00 – 23:00 (08:00 - 16:00) Time - UTC (PT)
State of H1: Locked at NLN for 13.5 hours at 30.2W and 64.3 Mpc.      
Intent Bit: Observing
Support: Keita, Jenne,
Incoming Operator: Travis

Shift Summary: Ran A2L DTT check – Pitch and Yaw are a bit elevated. As LLO is down, dropped out of Observing to run corrective script. A2L script finished with errors. Back to Observing. Spoke with Keita about the A2L Script. See aLOG #34763 for details. Successfully ran the script from a Controls terminal. Pitch and Yaw are now below the reference.

Remained lock for the entire shift. No issues or problems to report.

   Activity Log: Time - UTC (PT)
15:00 (08:00) Take over from Nutsinee
15:20 (08:20) Ran A2L check script
15:27 (08:27) Drop out of Observing to run A2L Script
15:32 (08:32) Back to Observing after A2L Script finished
15:40 (08:40) Bubba - Going down both Arms to check for tumbleweed accumulation
16:05 (09:05) Bubba – Back from Arm inspection   
17:03 (10:03) Drop out of Observing to run A2L Script – aLOG #34763
17:12 (10:12) Back to Observing after A2L Script ran successfully on a Controls terminal
23:00 (16:00) Turn over to Travis
H1 DetChar (DetChar, ISC, SUS)
andrew.lundgren@LIGO.ORG - posted 07:05, Thursday 09 March 2017 - last comment - 16:36, Monday 13 March 2017(34694)
Some blip glitches may be due to ETMY L2 coil drive
Miriam, Hunter, Andy

A subset of blip glitches appear to be due to a glitch in the ETMY L2 coil driver chain.

We measured the transfer function from the ETMY L2 MASTER channel to the NOISEMON channel (specifically, for the LR quadrant). We used this to subtract the drive signal out of the noisemon, so what remains would be any glitches in the coil drive chain itself (and not just feedback from DARM). The subtraction works very well as seen in plot 1, with the noise floor a factor of 100 below the signal from about 4 to 800 Hz.

We identified some blip glitches from Feb 11 and 12 as well as Mar 6 and 7. Some of the Omega scans of the raw noisemon signals look suspicious, so we performed the subtraction. The noisemons seem to have an analog saturation limit at +/- 22,000 counts, so we looked for cases where the noisemon signal is clearly below this. In some cases, there was nothing seen in the noisemon after subtraction, or what remained was small and seemed like it might be due to a soft saturation or nonlinearity in the noisemon.

However we have identified at least three times where there is a strong residual. These are the second through fourth plots. We now plan to automate this process to look at many more blip and check all test mass L2 coils in all quadrants.
Images attached to this report
Comments related to this report
miriam.cabero@LIGO.ORG - 09:28, Thursday 09 March 2017 (34698)

In case someone wants to know, the times we report here are:

1170833873.5
1170934017
1170975288.38

borja.sorazu@LIGO.ORG - 08:24, Sunday 12 March 2017 (34761)DetChar, SUS

I have noticed similarly caused glitches on the 10th March, in particular for the highest SNR Omicron glitch for the day:

 

Looking at the OmegaScan of this glitch in H(t) and then the highest SNR coincident channels which are all the quadrants of H1:SUS-ETMY_L2_NOISEMON:

 

Images attached to this comment
miriam.cabero@LIGO.ORG - 09:14, Monday 13 March 2017 (34781)

Hi Borja,

could you point us to the link to those omega scans? I would like to see the time series plots to check if the noisemon channels are saturating (we saw that sometimes they look like that in the spectrogram when it saturates).

I am also going to look into the blip glitches I got for March 10 to see if I find more of those (although I won't have glitches with such a high SNR like the one you posted).

Thanks!

borja.sorazu@LIGO.ORG - 12:13, Monday 13 March 2017 (34785)

Hi Miriam,

The above OmegaScan can be found here

Also I noticed that yesterday the highest New SNR glitch for the whole day reported by PyCBC live 'Short' is of this type as well. The OmegaScan for this one can be found here.

Hope if helps!

paul.altin@LIGO.ORG - 15:09, Monday 13 March 2017 (34793)

Hi Miriam, Borja,

While following up on a GraceDB trigger, I looked at several glitches from March 1 which seem to match those that Borja posted. The omegascans are here, in case these are also of interest to you.

miriam.cabero@LIGO.ORG - 16:36, Monday 13 March 2017 (34796)

Hi,

Borja, in the first omega scan you sent, the noisemon channels are indeed saturated. In that case it is difficult to tell apart if that is the reason for the spectrogram looking like that or if indeed it might be a glitch in the coil drive. Once Andy has a more final version of his code, we can check on that. In the second omega scan, the noisemon channels look just like the blip glitch looks in the calib_strain channel, which means the blip was probably already in the DARM loop before and the noisemon channels are just hearing it. Notice also that, besides the PyCBC_Live 'short', we have a version of PyCBC_Live that is dedicated specifically to find blip glitches (see aLog 34257), so at some point we will be looking into times coming from there (I will keep in mind to look into the March 10 list).

Paul, those omega scans do not quite look like what we are looking for. We did look into some blip glitches where the noisemon channels looked like what you sent and we did not find any evidence for glitches in the coil drive. But thanks for your omega scans, I will be checking those times when Andy has a final version of the subtraction code.

 

Displaying reports 49401-49420 of 83210.Go to page Start 2467 2468 2469 2470 2471 2472 2473 2474 2475 End