Displaying reports 52281-52300 of 86276.Go to page Start 2611 2612 2613 2614 2615 2616 2617 2618 2619 End
Reports until 16:00, Tuesday 21 March 2017
LHO General
thomas.shaffer@LIGO.ORG - posted 16:00, Tuesday 21 March 2017 (34965)
Ops Day Shift Summary

 TITLE: 03/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC

STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Maintenance day. Tumbleweeds blocked the Xarm so that filtered out some work. I had some issues locking with ALS_DIFF not fining IR and causing a lock loss. 12 seconds after it would set the offset to 1380, the IMC would drop out and kill the lock. What eventually worked, although it did not identify the problem, was going through that step by hand and scanning through the offsets slowly. I'm not sure if it will happen again so future operators be wary.

LOG:

H1 SUS
thomas.shaffer@LIGO.ORG - posted 15:46, Tuesday 21 March 2017 - last comment - 15:19, Wednesday 22 March 2017(34982)
Charge Measurements Taken for EX EY but not processed

Ran the full script for EX but had to cut EY short after about 35min. I did not get the chance to process the data yet, but I can do it tomorrow.

Comments related to this report
thomas.shaffer@LIGO.ORG - 14:58, Wednesday 22 March 2017 (35006)

I had to tag Jeff on this one to run the long_trend.m because I had nds2 troubles. Jeff ran it with no problems...

He also mentioned that we may need to flip the bias soon on ETMX because (let's see if I understood this correctly) the angular actuation is off by ~8% in some quadrants, but the longitudinal is only off by ~3% (See summary screenshot).

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 15:19, Wednesday 22 March 2017 (35016)
Sorry abandoning TJ quickly on this one. Here's what I said in regards to these plots:

Last week, I'd threatened that we needed to flip the ESD bias sign on ETMY because the traditionally posted angular relative actuation strength plots continue to show changes at the level of 8-10% because appreciable effective bias voltage from charge (negative 20-30 V) is accumulating in some quadrants. Note that this is relative to zero effective bias voltage.

However, if I look at the summary pages, to show me the longitudinal relative actuation strength (the fifth plot that TJ posts) as measured by the PCAL and SUS calibration lines -- the actuation strength direction that actually matters for calibration -- it shows a level of 3-4%. Note that *this* is relative to the latest calibration reference model, created Jan 4th, when the effective bias voltage was already in the negative 10 V range.

In summary -- I don't think we're in dire need of a bias flip on ETMY any longer. But we remain dilligent!
H1 CAL (CAL)
sudarshan.karki@LIGO.ORG - posted 15:25, Tuesday 21 March 2017 - last comment - 12:11, Wednesday 05 April 2017(34980)
Pcal beam spot position

We were able to get images using the Pcal camera at ENDY today and these images will be used to determine the position of the Pcal beam. (Analysis to follow). We were not able to get down to ENDX because of tumbleweed infestation. We will probably try to get images from ENDX during Thursday's commissioning effort.

Images attached to this report
Comments related to this report
sudarshan.karki@LIGO.ORG - 12:11, Wednesday 05 April 2017 (35349)

Analysis can be found at: LHO alog #35347

H1 CDS
james.batch@LIGO.ORG - posted 15:13, Tuesday 21 March 2017 (34979)
Updated gds software
WP 6532

Updated GDS software Ubuntu 12, Ubuntu 14, and Debian 8 workstations.  This replaces foton with a new version that writes the gain coefficient in scientific notation with extended decimal places.  The issue is trying to find a format that will work for gain coefficient values of 479871010208.8750610351 and 1.827245000521226e-32, as an example.
H1 SUS
richard.mccarthy@LIGO.ORG - posted 14:50, Tuesday 21 March 2017 (34977)
WP 6530 Open Iris on ITM cameras
Not sure anything changed since we were not locked at the time but I used the lens controller to open the iris all the way on ITMx and ITMy.  Without a beam I just have to believe they are all the way open.  Perhaps next time we are out of observing and locked I will shut and open the iris to verify its function.
H1 TCS (TCS)
nutsinee.kijbunchoo@LIGO.ORG - posted 14:43, Tuesday 21 March 2017 - last comment - 15:09, Tuesday 21 March 2017(34976)
HWSY SLED is now OFF

To save its life span.

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 15:09, Tuesday 21 March 2017 (34978)
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 14:15, Tuesday 21 March 2017 (34974)
LVEA swept

Found a power cord plugged into the wall opposite to HAM4 (now unplugged). Probably had been plugged since last week we did the HWS table work.

H1 IOO (IOO)
cheryl.vorvick@LIGO.ORG - posted 13:37, Tuesday 21 March 2017 (34973)
IMC beam spot position measurements

I measured the beam spot positions on MC1, MC2, and MC3, using the procedure in alog 31402.

Non-image files attached to this report
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 13:20, Tuesday 21 March 2017 (34971)
PRMI carrier locking guardian code prepared

I have made a new guardian code called ISC_PRMICA which we will use on this coming Thursday to do a high power PRMI test. The code is based on ISC_DRMI with some modifications to load different set of locking parameters. The code is not tested yet. It lives at

/opt/rtcds/userapps/release/isc/h1/guardian/ISC_PRMICA.py

H1 CAL (CAL, ISC)
evan.goetz@LIGO.ORG - posted 11:23, Tuesday 21 March 2017 - last comment - 17:11, Tuesday 28 March 2017(34967)
Trends of H1 optical response parameters for ER10 and thus far in O2
Using MCMC fitting to the sensing function measurements made in ER10 and O2, we can establish an estimate on the variation of the optical response parameters. The table below gives the typical (simple mean), maximum, and minimum of the measured maximum a posteriori values from the MCMC fits.

Parameter             typical    maximum    minimum
---------------------------------------------------
Gain (ct/m)           1.143e6    1.166e6    1.085
Cavity pole (Hz)      347.1      358        341
Time delay (usec)     0.5        2.5        -1.3
Detuned spring (Hz)   7.3        8.8        4.9
Detuned spring 1/Q    0.04       0.08       1e-3
This covers measurement dates from Nov 07 2016 through Mar 06 2017. Attached are plots showing these trends for ER10 and O2. Note that I have added--where possible--the GDS calculated values for kappa_C and f_c (black crosses). Note that these values do not come with error bars because the uncertainty would need to be computed from the measurement uncertainty of what goes into the calculate of kappa_C and f_c. It would be useful to have calibration lines running during the measurements to see if there is any trend or drift during the measurements themselves.
Non-image files attached to this report
Comments related to this report
evan.goetz@LIGO.ORG - 17:11, Tuesday 28 March 2017 (35163)
Attached are trend plots for all ER10 and O2 measurements.

The plots are stored at:
${CALSVN}/aligocalibration/trunk/Runs/O2/H1/Results/SensingFunctionTFs

The script to produce plots is:
${CALSVN}/aligocalibration/trunk/Runs/O2/H1/Scripts/SensingFunctionTFs/runSensingAnalysis_H1_O2.m
Non-image files attached to this comment
H1 TCS (TCS)
nutsinee.kijbunchoo@LIGO.ORG - posted 10:46, Tuesday 21 March 2017 (34969)
HWS code restarted - accidently took new ref centroids

The HWS machine got rebooted so I restarted the code. I edited the code not to take new reference centroids but the tmux session didn't seem to recognize the change in the script so it ended up taking a new reference centroids anyway (to fix this issue I probably should have just exit the session and come back in). HWSX data starting from Tue, 21 Mar 2017 17:35:48 UTC now have new reference centroid taken during cold IFO (down time). All the optics were aligned.

H1 PSL
jason.oberling@LIGO.ORG - posted 10:29, Tuesday 21 March 2017 (34968)
PSL Power Watchdogs Reset (FAMIS 3642)

I reset both PSL power watchdogs at 17:24 UTC (10:24 PDT).  This closes FAMIS task 3642.

H1 CDS
james.batch@LIGO.ORG - posted 08:27, Tuesday 21 March 2017 (34966)
Update tconvert on Debian 8
WP 6489

The tconvert program was updated for Debian 8 workstations to a version that can correctly convert dates containing the month of October.  This version can also correctly obtain Bulletin C for leap second updates, using https.
LHO General
thomas.shaffer@LIGO.ORG - posted 08:06, Tuesday 21 March 2017 (34964)
Ops Day Shift Transition

TITLE: 03/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 9mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY: Starting maintenance day. Been locked since my shift yesterday.

LHO General
corey.gray@LIGO.ORG - posted 08:03, Tuesday 21 March 2017 (34962)
OWL Operator Summary

TITLE: 03/21 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

At 15:00 utc, took H1 PREVENTATIVE MAINTENANCE for Maintenance Day.  H1 was locked over 19 hrs.  Did NOT hit Load Coefficients for Sheila's filter change since we were locked entire shift.
LOG:

LHO General
corey.gray@LIGO.ORG - posted 03:55, Tuesday 21 March 2017 (34963)
Mid-shift Summary

Relatively quiet & smooth sailing.  L1 was knocked out by a 4.6 Guatemalan quake (we rode through it and it didn't show up on our seismic BLRMS signals).  Have been locked over 15hrs with a range  hovering around 69Mpc.

I'm taking a quick walk over to my office for about 10-15min.

LHO General
corey.gray@LIGO.ORG - posted 00:37, Tuesday 21 March 2017 (34961)
Transition To OWL

TITLE: 03/21 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 16mph Gusts, 13mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.15 μm/s  (really quiet & below 50%)
QUICK SUMMARY:

Approaching 12hrs of being locked. 

Jeff informed me of a To Do item for the next lockloss (Load Coeff for new filter files, as noted in Sheila's alog#34954); or it can be done during Maintenance Day.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:10, Tuesday 21 March 2017 (34960)
Ops Evening Shift Summary
Ops Shift Log: 03/20/2017, Evening Shift 23:00 – 07:00 (16:00 - 00:00) Time - UTC (PT)
State of H1: Locked at NLN for 11.25 hours at 29.7W and 68.4 Mpc.     
Intent Bit: Observing
Support: N/A
Incoming Operator: Corey

Shift Summary: Ran A2L DTT check – Pitch is rung up a bit, Yaw is OK. Ran the A2L DTT check at the end of the shift. Pitch is approaching 0.8, Yaw is still at or near the reference. PI Mode-23 rang up a couple of times, but self-damped almost immediately. No other issues arose during the shift.    

   Activity Log: Time - UTC (PT)
23:00 (16:00) Take over from TJ
23:20 (16:20) Ran A2L check script
07:00 (00:00) Turn over to Corey

 

H1 SEI
thomas.shaffer@LIGO.ORG - posted 08:39, Monday 20 March 2017 - last comment - 14:27, Tuesday 21 March 2017(34936)
HEPI Pump Pressure 45 Day Trends

EX had a dip in pressure around March 9th from 97.7 to 97.5, but other than that all looks good.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 08:41, Monday 20 March 2017 (34937)

I forgot to link to FAMIS4530

Closed

david.barker@LIGO.ORG - 17:23, Monday 20 March 2017 (34957)

Looking over the past week, the daily EY gliches are at 20:44 PDT (03:44 UTC). On Saturdays a second glitch occurs at 21:04 PDT (04:04 UTC). Attached plots show 03:25 to 04:10 UTC for 3/19 and 3/12 (two successive saturday evenings in local time).

Images attached to this comment
hugh.radkins@LIGO.ORG - 14:27, Tuesday 21 March 2017 (34975)

Here are data from End Y with most of the pressure channels and the controller output to the pump motor.

The attached plot gives support to this argument:

Something is happening with either the Pump motor or the VFD causing an increase in pressure out from the pump.  This is evident by the increasing delay in pressure response as we proceed down the Pump Station Manifold.  PRESS1 is the first after the Pump, the rest are after Laminar flow resistors and the filter.  BSCSUP_PRESS is way down the line at the Chamber.  The PRESS1 clearly leads the down stream pressures and it steps more sharply than the others.  So this is a real pressure change increasingly softened by the accumulators and resistors etc as the wave moves down the line.

The VOUT signal is the PID loop responding to the differential pressure (diff between BSCSUP and BSCRET[not shown].)  There is a big step down on this channel just before the pressure step up but that wouldn't cause an increase in pressure.  So, I don't believe the motor is being directed to drive harder.

I'll look over the VFD manual to see if it has any scheduled items that might cause this?  That just hardly makes sense...

Edit--Extra--If the output voltage of the PID controller could actually be manipulated without the VOUT data signal registering it, that too would be a possibility...Dave is looking closer at the computer.

Images attached to this comment
Displaying reports 52281-52300 of 86276.Go to page Start 2611 2612 2613 2614 2615 2616 2617 2618 2619 End