Displaying reports 62061-62080 of 85794.Go to page Start 3100 3101 3102 3103 3104 3105 3106 3107 3108 End
Reports until 18:20, Monday 21 December 2015
H1 PSL
thomas.shaffer@LIGO.ORG - posted 18:20, Monday 21 December 2015 (24371)
Mon PSL checklist

Laser Status:
SysStat is good
Front End power is 30.75W (should be around 30 W)
Frontend Watch is GREEN
HPO Watch is RED

PMC:
It has been locked 27.0 days, 8.0 hr 21.0 minutes (should be days/weeks)
Reflected power is 1.644Watts and PowerSum = 24.72Watts.

FSS:
It has been locked for 0.0 days 18.0 h and 48.0 min (should be days/weeks)
TPD[V] = 1.505V (min 0.9V)

ISS:
The diffracted power is around 8.035% (should be 5-9%)
Last saturation event was 0.0 days 18.0 hours and 20.0 minutes ago (should be days/weeks)

 

LHO VE
thomas.shaffer@LIGO.ORG - posted 17:47, Monday 21 December 2015 - last comment - 23:54, Monday 21 December 2015(24370)
Vacuum alarm at MY CP3

I received an alarm in the control room here at 00:50 UTC (16:50 PST) for the MY Cryo Pump 3. The fill percent jmped up to 120% and has since been very slowly trending down (currently at 117.6% at 17:42). Kyle, John, Bubba, and Gerardo have been notified and are monitoring the situation.

Trends below of CP3 and CP4 for the HVE-MY:CP{}_LIC and HVE-MY:CP{}_LT channel for the a few hours before the excursion.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 20:21, Monday 21 December 2015 (24372)

Update: The percent for CP3 seemed to have leveled off at around 113%.  Attached a 4 hours trend of its progress.

Images attached to this comment
thomas.shaffer@LIGO.ORG - 23:54, Monday 21 December 2015 (24375)

Newest trend. It has climbed back up to 117%. Gerardo is on site to investigate.

Images attached to this comment
LHO General
thomas.shaffer@LIGO.ORG - posted 16:05, Monday 21 December 2015 (24368)
Ops Eve Transition
H1 General
jim.warner@LIGO.ORG - posted 15:59, Monday 21 December 2015 (24367)
Shift Summary

TITLE:    Dec 21 Day Shift 08:00-16:00UTC

STATE Of H1: Observing, RF45 is acting up

SUPPORT: Typical control room crowd

SHIFT SUMMARY: I took over for Cheryl at 21:30, thing were quiet until RF45 started acting up at 23:30, still in observe, but data is obviously bad

ACTIVITY LOG:

21:20 JeffK Running pcal to darm tf, llo calls to say they are at dc readout, done 22:30

22:00 Bubba to Mid-Y, back 24:00

23:30 RF45 starts acting up, out of observe briefly while Evan went to LVEA to check some PSL rack equipment
 
 
21:20 JeffK Running pcal to darm tf, llo calls to say they are at dc readout, done 22:30
23:30 RF45 starts acting up, out of observe briefly while Evan went to LVEA to check some PSL rack equipment
22:00 Bubba to Mid-Y, back 24:00

 

 
H1 ISC (DetChar)
evan.hall@LIGO.ORG - posted 15:23, Monday 21 December 2015 - last comment - 16:36, Monday 21 December 2015(24365)
45 MHz glitching again

45 MHz stabilization started gitching circa 23:15:00 Z.

This was accompanied by a drop of a few percent in AS90.

Nothing is visible in the spare amplitude demod on the ISC rack (23567). Noise appears stationary with an rms of a few millivolts, meaning the RAN of this glitch at the ISC rack (not including the EOM driver chain) is less than a few parts in 105.

Comments related to this report
jim.warner@LIGO.ORG - 15:29, Monday 21 December 2015 (24366)

Things are continuing to degrade. We have dropped out of observing and Evan has gone out onto the LVEA floor to poke at some of the electronics.

evan.hall@LIGO.ORG - 16:36, Monday 21 December 2015 (24369)

Daniel, Jenne, Evan

The 45 MHz jump appeared in AS90 and ASC dc sum.

AS90Q increased in amplitude, while AS90I decreased in amplitude, indicating a phase shift of the 45 MHz. The drop in ASC dc sum means that there was also an amplitude shift.

Images attached to this comment
H1 CAL
jeffrey.kissel@LIGO.ORG - posted 14:33, Monday 21 December 2015 (24363)
New DARMOLGTF and PCALY to DARM Sweeps
J. Kissel

Another collection of our bi-monthly(-ish) assessment of the calibration and DARMOLGTF. Details will be processed later including analysis of time-dependence. The front-end, CAL-CS, DELTAL_EXTERNAL calibration (and therefore the low-latency GDS pipeline output) is still within the desired precision. I attach screenshots of the measurements for posterity. Note, this time, I've updated the reference to be the most recent sweep, taken Dec 01 2015, (see LHO aLOG 23883, also yet to be processed.)

DARM OLGTF Template:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/2015-12-21_H1_DARM_OLGTF_7to1200Hz.xml

Corresponding Exports: 
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_coh.txt
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_tf.txt
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_coh.txt
2015-12-21_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_tf.txt

PCAL2DARM TFs:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/PCAL/2015-12-21_PCALY2DARMTF_7to1200Hz.xml

Coresponding Exports:
2015-12-21_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_coh.txt
2015-12-21_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_tf.txt
Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 11:27, Monday 21 December 2015 - last comment - 13:15, Monday 21 December 2015(24360)
Ops mid-day update: 19:27UTC

Title: Ops Day Shift, 16:00-23:59UTC, 08:00-16:00PT

State of H1: in Oberve for almost 12 hours, range is 74.3Mpc

Details: some site activites, useism is around 0.7um.s, winds 5-15mph

Comments related to this report
cheryl.vorvick@LIGO.ORG - 13:15, Monday 21 December 2015 (24362)

Site activities: Bubba driving

  • 10:28AM - arrives at MX
  • 10:43AM - leaves MX headed to MY
  • 10:51AM - arrives at MY
  • 11:39AM - leaves MY
LHO General
cheryl.vorvick@LIGO.ORG - posted 11:22, Monday 21 December 2015 (24359)
21 dec 2015 - morning commissioning meeting

work today:

- follow up on glitch and range drop around 14:00UTC

- CDS - Richard tomorrow/today, audio signal

- Bubba at MY and MX

 

work tomorrow Maintenance:

- Hugh rezero TS2's at end stations

- Richard, audio signal

- Bubba, forklift work, clean room curtains at EY, switch fans at EY, pick up welder at EX

- Jason, BS and SR3 oplevs

- Sudarshan/Darkhan, possible pcal calibration at Y end

- Jeff, forklift PSL chiller

H1 AOS (ISC, SEI, SUS)
jason.oberling@LIGO.ORG - posted 08:58, Monday 21 December 2015 - last comment - 14:55, Monday 21 December 2015(24356)
Optical Lever 7 Day Trends

Attached are 7 day pitch, yaw, and sum trends of all active H1 optical levers.

Images attached to this report
Comments related to this report
jason.oberling@LIGO.ORG - 14:55, Monday 21 December 2015 (24364)AOS, ISC, SEI, SUS

After having some time to analyse these, I conclude the following:

  • Centering
    • Need to keep an eye on SR3 and HAM2 pitch, these are starting to approach their linear limits (~25-30 µrad).  Nothing to worry about for now, but will need a re-zeroing in the near future.
    • All other active oplevs are good.
  • Glitching
    • Can't really tell glitching from the attached trends, so I use the spectrograms posted to the DetChar summary pages (SUS Oplev overview linked, find individual oplevs under the SUS dropdown menu.  HAM oplevs not on DetChar pages, only used for alignment purposes so glitching is not a critical issue for them).
    • The highest rate of glitches can be found on BS, SR3, and ITMy:
      • BS: I am still adjusting the power to find the glitch-free zone I set on this new laser in the lab; planning another adjustment tomorrow (see LHO WP5667).  This is the highest priority as BS oplev damping is still used during DRMI acquisition.
      • SR3: Glitching first reported by Nutsinee and Jenne here.  Not a high priority as this oplev is not used for any damping, but since I will be adjusting the BS tomorrow I will adjust SR3 as well (see above linked WP).
      • ITMy: This oplev is still using an unstablized laser on the old style oplev power supply and no thermal stabilization.  At this glitch rate this is my next target for laser replacement (to fulfill ECR E1500224), especially as pitch oplev damping is still used for this optic.  I have seen no reports of the glitches causing issues with IFO operation.
    • ETMx has the next highest rate of glitching.
      • Low priority as the oplev is not used for any damping.
    • ITMx and ETMy show very occaisional glitches.
      • ITMx: Like ITMy, this oplev is still using an unstabilized laser on the old style power supply an no thermal stabilization.  Barring other lasers requiring swaps due to glitches (i.e. can't fix with a simple power adjustment) this is my next target for laser replacement after ITMy (to fulfill the above linked ECR).
      • ETMy: As ETMx, low priority as no oplev damping is used here.
    • PR3 oplev is showing no issues.
H1 General (DetChar)
cheryl.vorvick@LIGO.ORG - posted 08:49, Monday 21 December 2015 (24355)
GRB alert arrived 16:34:45UTC

State if H1: in Observe

H1 ISC
daniel.sigg@LIGO.ORG - posted 08:43, Monday 21 December 2015 - last comment - 09:41, Monday 21 December 2015(24354)
RF AM 45.5MHz

Plot 1 shows the RF AM stabilization out-of-loop sensor and the control signal. Over the past 30 days there were 5 clearly visible glitches in the control signal. These are reflected in the out-of-loop sensor. However, there are two non-stationary episodes in the sensor signal which have only a negligible counterpart in the control signal.

Plot 2 shows the same traces over the past 120 days. Overall, the glitches seem to have reduced in size and frequency for no apparent reason.

Non-image files attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 09:41, Monday 21 December 2015 (24358)

Two glitches in the AC channel line up with PSL table temperature swings associated with entry into the PSL laser room.

Images attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 07:58, Monday 21 December 2015 (24353)
Ops Owl Shift Summary
Activity Log: All Times in UTC (PT)

08:00 (00:00) Take over from Ed
11:15 (03:15) High heat alarm for CS Zone 4 duct temperature, (101.16F). Will monitor.
13:08 (05:08) Four ETM-Y saturations (18:08:33, 37, 40, 44), with a marked drop in range to ~ 63Mpc
16:00 (08:00) Turn over to Cheryl    


End of Shift Summary:

Title: 12/21/2015, Owl Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT)

Support:  None
 
Incoming Operator: Cheryl

Shift Detail Summary: Locked in Observing mode for past 8 hours. Power at 21.8w, range 79Mpc. Wind is light to gentle breeze (4-12mph). Seismic is improving with a downward trend for the past 6 hours. Microseism is also decreasing, but at a much slower rate than seismic. 

Other than 4 ETM-Y saturations (within 11 seconds), which took the range down to a low of 63Mpc, there were no problems or issues during the shift.  

H1 General
jeffrey.bartlett@LIGO.ORG - posted 04:05, Monday 21 December 2015 (24351)
Ops OWl Mid-Shift Summary
    All quiet on the western front. IFO is in Observing mode, with 21.8W, and 81.5Mpc of range. The wind, seismic, and microseism have remained constant over the first 4 hours of the shift. For the most part generally good data collecting conditions prevail. 
H1 INJ (DetChar, INJ)
christopher.biwer@LIGO.ORG - posted 09:39, Saturday 19 December 2015 - last comment - 07:52, Monday 21 December 2015(24327)
summary of burst hardware injection tests
Max, Chris

Summary:

We tested scheduling the burst injections. The purpose of this test was to test the burst pipeline hardware injection recovery as outlined in the O1 plan.

The initial aLog is here: aLog entry

Waveform:

The waveform parameters are here: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/config/Burst/Waveform/WNB_burst_1134573920_1.info

The waveform file for H1 and L1 are: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/config/Burst/Waveform/WNB_burst_1134573920_1_H1.txt https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/config/Burst/Waveform/WNB_burst_1134573920_1_L1.txt

First Test:

The first test was scheduled for 1134577813. The schedule file was given:
1134577813 2 1.0 WNB_burst_1134573920_1_

This injection failed.

It failed because the waveform files ended in .dat instead of .txt. tinj was updated but the documentation for performing hardware injections document was not!

Max and I checked the PINJX_TRANSIENT EXCMON channel to confirm that a signal did not go into the inteferometers.

Second Test:

The second test was scheduled for 1134581196. We renamed the waveform ASCII files and the schedule file was given:
1134581196 2 1.0 WNB_burst_1134573920_1_

This injection was successful.

cWB already picked up the injection. See gracedb link: gracedb entry

Action Items

  * The documentation for burst injections needs to be updated with the correct filename.
Comments related to this report
christopher.biwer@LIGO.ORG - 09:46, Saturday 19 December 2015 (24328)
I checked the segment database to make sure the injection was logged correctly. It was. Querying ODC-INJECTION_BURST:2 in both IFOs from 1134577800 I get a segment for [1134581196,1134581198).
christopher.biwer@LIGO.ORG - 07:52, Monday 21 December 2015 (24352)
The documentation (DCC link) has been updated to correctly say to use .txt extension for burst injection waveform files.
Displaying reports 62061-62080 of 85794.Go to page Start 3100 3101 3102 3103 3104 3105 3106 3107 3108 End