Displaying reports 61421-61440 of 85556.Go to page Start 3068 3069 3070 3071 3072 3073 3074 3075 3076 End
Reports until 16:05, Friday 08 January 2016
LHO General
corey.gray@LIGO.ORG - posted 16:05, Friday 08 January 2016 - last comment - 17:08, Friday 08 January 2016(24766)
DAY Ops Summary

TITLE:  1/8 DAY Shift:  16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC     

STATE of H1:  On the way to NLN

Incoming Operator:  Cheryl

Support:   Jenne, Evan, Kissel

Quick Summary:

Calibration work continues.  In the afternoon spent some time locking H1 & this was not trivial due to:

  1. 5.3 Mexico quake
  2. PRMI transition not working as desired
  3. Power not raised to 23 W (script was changed last night, but was not loaded)
  4. Also having issues with either the operator workstation and/or Guardian

Shift Activities:

Comments related to this report
corey.gray@LIGO.ORG - 17:08, Friday 08 January 2016 (24780)

Remember To Also LOAD Script

For the ISC_LOCK guardian, Jenne hit LOAD button this afternoon to allow Guardian to take H1 to 23W.

Last night for Sheila/Cheryl H1 troubleshooting work, the script was set to 10W, and Cheryl changed it back to 23W & saved it.  But H1 was in Observing, so she was not able to hit the LOAD button (is that allowable in Observing?).  Anyway, this afternoon Evan noticed H1's power was only taken to 10W.  After H1 dropped lock, Jenne hit the LOAD button.

If H1 is in a safe state, one should remember to also hit the LOAD button after making changes to scripts....or flag-the-alog/let-next-operator-know to LOAD during next opportunity.  

PRMI Transition Didn't Work

During locking this afternoon, DRMI took more than 15min, so I selected PRMI.  PRMI locked and alignment was optimized.  Requested DRMI LOCK, and H1 switched immediately from PRMI to DRMI, but unfortunately, the Guardian was stuck here.  Perhaps next time we can try re-requesting DRMI LOCK?

H1 General
corey.gray@LIGO.ORG - posted 15:51, Friday 08 January 2016 (24779)
Problems with operator0 and/or h1guardian0

This afternoon have noticed the Guardian screens going WHITE & have also had medm message windows saying:  "virtual disconnect" for h1guardian0.  Jim Batch checked this and mentioned that h1guardian0 has a scary amount of Network Connections (or something along those lines).  Attached is a snapshot when I lost guardian.

An additional symptom I'm seeing is with the actual work station (logged in as ops-->  ops@operator0).  The desktop has frozen up a few times.  I have rebooted this computer multiple times.  Will send an email to cdsadmin.

Images attached to this report
H1 SUS
betsy.weaver@LIGO.ORG - posted 14:53, Friday 08 January 2016 (24776)
Weekly ETM charge measurements

This afternoon, there was a window of opportunity to take ETMX and ETMY charge measurements.  Results are posted below.  Kissel is suggesting that I add another plot, but since it will take a while to work through I'm deferring to Monday, sad as he now is.  Charge is still accumulating and we need to think about flipping the bias soonish.

Images attached to this report
H1 SUS (SUS)
peter.king@LIGO.ORG - posted 13:28, Friday 08 January 2016 (24775)
18-bit DAC AI chassis S/N S1104370
This AI chassis was removed as mentioned in the following alog entry
  https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=21081

In seeking to find what was wrong with the chassis, I powered it up.
The following output channels were glitchy when their respective inputs
were terminated:
 Channels: 1, 3, 6, 8, 9, 10, 11, 14 and 16

Don't know why yet but the AA/AI boards (D070081-v6, S1103146, S1200704)
are a little warmer to the touch than usual (I think).  Channels [1-8]
are on S1103146, channels [9-16] are on S1200704.
H1 CAL (CAL)
darkhan.tuyenbayev@LIGO.ORG - posted 13:16, Friday 08 January 2016 - last comment - 15:33, Monday 11 January 2016(24774)
LHO Pcal EndX calibration measurements were taken

EvanG, Travis, Darkhan,

Today we repeated Pcal end-station measurements at EX, the procedure is described in T1500063. Rough readings from dataviewer and GPS times are given in the attached notes.

The outer beam still show a significan drop in power between Transmitter and Receiver modules, earlier we thought that the beam was not well centered at the input port of the RxPD integrating sphere, but by looking at an outer beam spot with IR viewing card it does not look to be the case (see attached picture).

Earlier this week we took a similar set of measurements, but we suspected that WS/TX when WS is inside of received module were not taken properly and today's measurements were taken as a double-check (LHO alog 24726).

We will post a full report and some conclusions soon.

Images attached to this report
Comments related to this report
darkhan.tuyenbayev@LIGO.ORG - 15:42, Friday 08 January 2016 (24778)CAL

A generated report (comparison with previous measurements) was uploaded to DCC T1500129-v4.

This report gives us more confidence that our measurements taken on 2016-01-05 (LHO alog 24726) were not made properly, because
on 2016-01-05 the value of RX/WS (not optical efficiency corrected one) changed by ~ 2 %, but
on 2016-01-08 this ratio was back to it's value measured earlier in O1.

The data point for 2016-01-15 will need to be removed from future end-station measurement reports.

darkhan.tuyenbayev@LIGO.ORG - 15:33, Monday 11 January 2016 (24876)CAL

During Pcal end-station TxPD and RxPD measurements the ETM must be aligned.

This conlog is made to confirm that ETMX was aligned during measurement process.

Images attached to this comment
H1 ISC
jenne.driggers@LIGO.ORG - posted 12:53, Friday 08 January 2016 - last comment - 18:22, Friday 08 January 2016(24773)
Spot positions through December

We've continued measuring the beam spot positions once a week as part of Tuesday maintenence. 

The 2 pdfs below are different views of the same data set.  The first set of plots is the data on x-y grids, so you can really see how little our spots are moving.  The second set of plots is the data as a function of time.  Some of the pitch values are changing more now than they were back in October, but the maximal excursions are still only about 2mm away from the means.

Non-image files attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 18:22, Friday 08 January 2016 (24782)

Here's the same data, but with more features in the presentation.

The color indicates the time between lock acquisition and the measurement.  Darkest blue is 0 minutes, and brightest pink is 30+ minutes, with a gradient in between.

The marker shape now (per JimW's request) indicates the ISI blend state, as a check to see if changing the blends changes the alignment.  Circles indicate both x and y axes of the ISI are on the Quite_90 blends, diamonds indicate both axes on the 45mHz blends, and square markers indicate that the beamline axis is on the 45mHz and the orthogonal axis is on the 90mHz blend.  I conclude that the ISI state has no noticeable effect on the beam spots.

Non-image files attached to this comment
LHO FMCS
bubba.gateley@LIGO.ORG - posted 12:44, Friday 08 January 2016 (24772)
Welding turbo header piping at M Y
I started welding the turbo header piping under the beam tube at Mid Y back together today. The first weld was started at approximately 10:17 PT and lasted for ~45 seconds. The next welds were at ~10:36 and 10:46: PT and each lasted for ~ 90 seconds. There will be more welding next week.
H1 INJ (CDS)
james.batch@LIGO.ORG - posted 12:04, Friday 08 January 2016 (24771)
Backup of h1hwinj1 started
FRS #3896

The ~hinj account on h1hwinj1 is now being backed up to the daqsvn.ligo-la.caltech.edu computer every hour.  This should close out FRS ticket.
LHO General
richard.oram@LIGO.ORG - posted 10:44, Friday 08 January 2016 (24769)
LLO Observing Time Loss due to HW/SW faults recorded in FRS for 10/1/2015- 1/08/2016

Sharing learning laterally across the Observing Sites

The Detector Engineers and Operators review together the faults in the FRS that caused observing time loss.

The circumstance surrounding each fault  is reviewed and a discussion of whether the response in each case was appropriate and what is now in place to mitigate repeat occurrence.

 

See LLO log entry 24196

https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=24196

H1 CAL
jeffrey.kissel@LIGO.ORG - posted 10:33, Friday 08 January 2016 - last comment - 19:13, Tuesday 12 January 2016(24768)
Sensing Function Characterization Measurements Done(ish)
J. Kissel

In order to begin exploring the systematic discrepancy between model and measurement below ~30 [Hz] in the IFO's sensing function (see, e.g. LHO aLOG 24709), we've taken PCAL2DARM and DARMOLGTF transfer functions at the normal amplitude and at half amplitude. Sadly, the IFO lost lock during the last few (low frequency) data points of the last half amplitude DARMOLGTF, but I think we have enough data to make a comparison. 

Premiliminary message: there's no obvious, unexpected difference between normal and half amplitude. Coherence is less, so the data points are a little more scattered, but no surprise there.

One thing of note, while watching the DARM ASD during the measurement, there are no signs of higher harmonics in the PCAL excitation, but once the DARM OLGTF (as driven by the ESD and subsequent upper stages) reaches ~20 Hz, one can clearly see a second harmonic in the ASD meaching along right behind the fundamental excitation frequency. To give a feel, during the normal amplitude drive, once the excitation hit ~15 [Hz], the second harmonic's amplitude was roughly 3.5 orders of mangitude below the fundamental (but still clearly visible thanks to the discrepancy between the 10 and 30 [Hz] sensitivity). Recall that the linearization for ETMY is *not* on in the IFO's lowest noise state. The EY bias voltage remains -380 [V] (with an effective bias voltage from charge of ~ -20 [V]; see LHO aLOG 24547).

We leave the IFO down for the PCAL team to explore PCALX problems (see LHO aLOG 24726), and so Betsy can grab this week's charge measurements on ETMY.

Analysis of the data to come later, but the files live here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/DARMOLGTFs/
2016-01-08_H1_DARM_OLGTF_7to1200Hz.xml
2016-01-08_H1_DARM_OLGTF_7to1200Hz_halfamp.xml

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/PCAL
2016-01-08_PCALY2DARMTF_7to1200Hz.xml
2016-01-08_PCALY2DARMTF_7to1200Hz_halfamp.xml
Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 19:13, Tuesday 12 January 2016 (24909)

Later, I have processed the transfer functions that Jeff took and I have made a comparison. I do not see any systematic change between the measurements with the nominal amplitudes and the ones with half amplitudes. See the attached pdf for more details. Note that we are seeking a systematic as large as 20 % at 10 Hz. There are seemingly statistical error in the measurement but they don't look systematic.

The analysis code lives in the SVN at: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Scripts/DARMOLGTFs/HalfAmp_20160112.m

The resultant plot can be found at: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Results/DARMOLGTFs/2016-01-08_HalfAmp.pdf

Non-image files attached to this comment
H1 DAQ (CDS)
james.batch@LIGO.ORG - posted 08:33, Friday 08 January 2016 - last comment - 10:52, Friday 08 January 2016(24765)
Restarted h1nds0
Found h1nds0 to be dead with a kernel panic, rebooted.  Did not cycle power, just reboot.
Comments related to this report
james.batch@LIGO.ORG - 09:12, Friday 08 January 2016 (24767)
The h1nds0 computer died January 7, 22:39:00 UTC which was 14:39 PST. Monit did not tell us about it because the computer was locked up, so we were dependent on an observant operator or administrator to notice it.  Apparently we need a better system to alert people to faults of this nature.
keith.thorne@LIGO.ORG - 10:52, Friday 08 January 2016 (24770)
LLO CDS uses regular SSH queries of all machines via Nagios to keep ahead of these things.  Contact Michael Thomas for details
LHO General
corey.gray@LIGO.ORG - posted 08:16, Friday 08 January 2016 (24764)
Transition to DAY Shift Update

TITLE:  1/8 DAY Shift:  16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC     

STATE of H1:   OBSERVING (but taken out at 8am for calib)

Outgoing Operator:  Patrick

Quick Summary:

Nice H1 hand-off from Patrick (H1 has been locked since Cheryl locked it last night and it is going on 10+hrs).  Range has been hovering at a flat & quiet 80mpc.  useism looks like it's been dropping over last 12hrs & LVEA is currently at 0.55um/s in LVEA.  Winds are under 4mph.  

Patrick mentioned nds0 being down (symptoms:  (1) nds0 white boxed  & (2) edcu red-boxed on overview) & that David has been notified.

Jeff took H1 promptly at 16:00utc for Calibration.  

LHO General
patrick.thomas@LIGO.ORG - posted 07:58, Friday 08 January 2016 (24763)
Ops Owl End Shift Summary
TITLE: 01/08 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC

STATE Of H1: Observing @ ~ 79 MPc.
SHIFT SUMMARY: Remained in observing entire shift. 3 SUS ETMY saturations. Left a message with Dave that nds0 is down. H1:LSC-POP_A_LF_OUTPUT has been stable.
INCOMING OPERATOR: Corey
LHO General
patrick.thomas@LIGO.ORG - posted 03:57, Friday 08 January 2016 (24762)
Ops Owl Mid Shift Summary
Have remained in observing at ~ 79 MPc. 3 SUS ETMY saturations. H1:LSC-POP_A_LF_OUTPUT stable.

nds0 is still down. I have left a message for Dave.
H1 General
cheryl.vorvick@LIGO.ORG - posted 02:33, Friday 08 January 2016 (24761)
Ops Eve Summary:

Ops Eve Summary: 00-08:00UTC, 16:00-23:59PT

State of H1: Observe, range 79Mpc, POP_A_LF stable

Fellow: Darkhan

Shfit Summary:

Calibration measurements until about an hour into my shift

Locking went well, and made it past DRMI

Calibrations needed H1 in not-DRMI, so I broke the lock

Calibrations continued, then back to locking

Even after having been out of lock most of the day, H1 locked and went back to Low Noise

Relocking Issues:

Changes: 

I restored the gaudian to requestion 23W instead of 10W. JeffK had suggested it, and I emailed Sheila, and she said to go ahead.

H1 CAL (CAL)
darkhan.tuyenbayev@LIGO.ORG - posted 11:59, Wednesday 06 January 2016 - last comment - 15:23, Friday 08 January 2016(24726)
LHO Pcal EndX calibration measurements were taken

RickS, Darkhan,

Yesterday, Jan 5, 2016, we took Pcal end-station calibration measurements at EX using WS1 calibration standard. The measurement procedure is described in T1500063.

Rough numbers from dataviewer and GPS times were noted in the attached scan (blank form is taken from T1500062).

A generated report (comparison with previous measurements) was uploaded to DCC T1500129-v3.

At first when we started the measurements we found out that laser power in PcalX is modulated through Pcal hardware injection channels H1:CAL-PINJX_*, we had to restart the measurements after tuning off these excitations.

Non-image files attached to this report
Comments related to this report
darkhan.tuyenbayev@LIGO.ORG - 12:20, Wednesday 06 January 2016 (24727)

At first we used CAL_INJ_CONTROL medm screen to turn off injections.

When we found out that some injections are still going into PCALX, we looked into H1:CAL-PINJX_* filters using auto-generated medm screens in

/opt/rtcds/lho/h1/medm/h1calex/H1CALEX_PINJX_*.adl

We switched off outputs from these filters before taking our measurements and put them back on afterwards.

darkhan.tuyenbayev@LIGO.ORG - 15:23, Friday 08 January 2016 (24777)

Jeff pointed out that going to /opt/rtcds/lho/h1/medm/h1calex/H1CALEX_PINJX_*.adl  is not necessary, there's a MEDM screen under Sitemap -> CAL -> PINJX that gives an access to Pcal hardware injection switches.

Displaying reports 61421-61440 of 85556.Go to page Start 3068 3069 3070 3071 3072 3073 3074 3075 3076 End