Displaying reports 57501-57520 of 89077.Go to page Start 2872 2873 2874 2875 2876 2877 2878 2879 2880 End
Reports until 05:56, Monday 12 December 2016
H1 General
edmond.merilh@LIGO.ORG - posted 05:56, Monday 12 December 2016 - last comment - 07:38, Monday 12 December 2016(32466)
Shift Summary - Owl
TITLE: 12/12 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 70.8231Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
Very quiet shift. Drop in arnge from 5:00-5:45AM due to Hanford traffic. Reports from Karen, coming in from Kennewick near where I live, and from my wife this morning are prompting me to call it a night due to rather moderate snowfall. Heading out.
LOG:
Comments related to this report
edmond.merilh@LIGO.ORG - 07:38, Monday 12 December 2016 (32467)
7:30 made it home safely.
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 05:41, Monday 12 December 2016 (32465)
jump in on table temperature sensor output
In trending the PSL Enclosure temperatures for the past few days, I remembered about the AD590-based sensor on
the table near the exit of the reference cavity chamber.  There's a sudden jump in the temperature reading.  Not
sure why this would be the case.  The reference cavity was locked at the time.
Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 04:11, Monday 12 December 2016 (32464)
Mid-Shift Summary - Owl

H1 is locked and Observing for 19hours43min.

Range is vacillating between 63 and 73Mpc. (as per the range medm screen)

The 1009.5 vioin mode has neither rung down nor up.

Environmental conditions are nominally good

All seismic BLRMS show downward trending

H1 PEM
edmond.merilh@LIGO.ORG - posted 01:13, Monday 12 December 2016 (32463)
Dust Alarm data from alarms currently active

Below are trends from the past two days. I can see a definite correlation between wind speed and the .3u particle count in the PSL 101 dust monitor ~ two days ago. It's hard to tell about the most current one. The particle count is definitly high enough to set off the alarm but can wind speeds under 10mph be to blame?

I don't see any aLogs about VEA environmental changes at EY so I don't quite know what is going on with dust monitor 1. Again, I see wind speeds ≤ 10mph

Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 00:17, Monday 12 December 2016 - last comment - 00:27, Monday 12 December 2016(32461)
Shift Summary - Owl Transition
TITLE: 12/12 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 71.6633Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.34 μm/s 
QUICK SUMMARY:
H1 is locked and observing. Range:74Mpc. Keeping a eye on 2nd order violin harmonic that's peaking to 1e-15.
      
The range looks good so I'm not going to try and damp it just yet. LLO is also up and running.
Comments related to this report
edmond.merilh@LIGO.ORG - 00:27, Monday 12 December 2016 (32462)

Here's a plot of the a2l coherence at the beginning of my shift.

Images attached to this comment
LHO General
corey.gray@LIGO.ORG - posted 00:06, Monday 12 December 2016 (32460)
Eve Shift Summary

TITLE: 12/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 71.8Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

All shifts should be like this....weekend!  Cheryl handed off a locked H1 & it is approaching 16hrs of lock.  The range looks very good on this stretch:  flat, no glitch drops.  useism is just under the 90percentile and winds are low.

1st Harmonic of Violins (~1kHz) are high (1x^-15).  Perhaps we should address damping these guys down at some point when L1 is down?

Tonight Amber Henry was my copilot at the operator helm.  Walked her through some of the basics.

H1 SUS
cheryl.vorvick@LIGO.ORG - posted 15:59, Sunday 11 December 2016 - last comment - 19:20, Sunday 11 December 2016(32456)
PI mode 28 range up once and I changed the sign of the gain at 22:04:49UTC

Plot attached:

Images attached to this report
Comments related to this report
terra.hardwick@LIGO.ORG - 19:20, Sunday 11 December 2016 (32458)

Thanks. FYI we no longer need to log PI damping changes (unless of course something goes wrong/abnormal). 

H1 General
cheryl.vorvick@LIGO.ORG - posted 15:52, Sunday 11 December 2016 - last comment - 16:00, Sunday 11 December 2016(32455)
Ops Day Shift Summary: H1 locked for 7.5 hours, two drops from Observe

TITLE: 12/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 70.4106Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

Comments related to this report
cheryl.vorvick@LIGO.ORG - 16:00, Sunday 11 December 2016 (32457)
  • alog 32456 - PI mode 28 rang up
H1 General (DetChar)
cheryl.vorvick@LIGO.ORG - posted 15:34, Sunday 11 December 2016 - last comment - 21:26, Sunday 11 December 2016(32453)
H1 kicked out of Observe by EY ECAT PLC2 SDF
Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 21:26, Sunday 11 December 2016 (32459)

(Gray, Kawabe, Vorvick)

Wanted to close the loop here (mainly wanted to confirm there were no other channels we had to worry about).

Today Cheryl took care of UNMONITORING the channel (H1:ALS-Y_FIBR_LOCK_TEMPERATURECONTROLS_ON) we observed knocking us out of OBSERVING the last two days.

I went ahead & followed Keita's instructions for checking ALL the channels for this frontend (h1sysecaty1plc2), which Cheryl posted (here), to make sure there were no other channels in h1sysecaty1plc2 we might be missing.  The [15] channel list files are at:  /ligo/home/keita.kawabe/LockLoss/SDFERRORS/h1sysecaty1plc2 & I ran a lockloss script on all of these files for both OBSERVING drops which happened during Cheryl's shifts (GPS time:  1165432802 & 1165531183) & for both of these times, the channel noted above is the only one which makes an obvious change (see attachment #1 & #2 for both times).

So we should now be good (unless a new channel makes a change on us).

Images attached to this comment
H1 General
cheryl.vorvick@LIGO.ORG - posted 13:35, Sunday 11 December 2016 (32450)
Site Update: roads conditions at the site are questionable - 21:25UTC (1:26PM PT)

Terra called in to check on H1.  I hadn't looked outside, so wasn't aware that we'd had sleet this morning after I got here, and she's telling me that road conditions in town are not good.  She and I talked about H1 and it's running well, so she did not come to the site.  She emailed Keita, so he's aware.

H1 AOS
cheryl.vorvick@LIGO.ORG - posted 13:19, Sunday 11 December 2016 (32449)
Dust - plot of 1 day and 6 hours, so 7AM Saturday to 1PM Sunday (local time)

Local time translates into 15:00UTC yesterday to 21:00 today.

Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 11:26, Sunday 11 December 2016 - last comment - 13:17, Sunday 11 December 2016(32443)
out of Observe to run a2l

After reading Keita's alog 32025, I used the template to passively look at coherance over this lock, and pitch is at 0.9 and has been and this was not in the previous lock, interestingly enough, though yaw was worse at the end of the last lock.

Going out of Observe now to reduce the coherance made sense in light of the long lock we just had.

Comments related to this report
cheryl.vorvick@LIGO.ORG - 11:36, Sunday 11 December 2016 (32444)

paasive a2l checks:

  • first file: 18:59:54UTC - before running a2l
    • pitch coh = 0.9, which is significantly higher than the referances
    • yaw coh is below the referances in the 15-21Hz range
  • second file: 19:23:25UTC - after running a2l
    • pitch coh is now at or below referances
    • yaw coh is now higher than the first measurement (first file), and is at, above, and below the referances in the 15-21Hz range
Images attached to this comment
cheryl.vorvick@LIGO.ORG - 12:41, Sunday 11 December 2016 (32445)

Here's what's odd - pitch and yaw coherances are better an hour after running a2l, but the entire region 10Hz to 40Hz is elevated, and the range has gone down.

Plot start time is 20:32:06UTC.

Images attached to this comment
cheryl.vorvick@LIGO.ORG - 12:55, Sunday 11 December 2016 (32446)

New plot - start time 20:43:21 - coherence is higher but 10-40Hz is not elevated.

Images attached to this comment
keita.kawabe@LIGO.ORG - 13:17, Sunday 11 December 2016 (32448)

Smaller coherence with larger DARM noise at 20Hz means that the excess noise is not due to a2l coupling. When something other than a2l coupling dominates the noise at 20Hz, running or not running a2l is irrelevant, so please don't run it.

Again I'll say this, it's a perfect project for a fellow to write a script to plot the coherence and DARM BRMS for 15-25Hz or so VS time. With such a script it would be easy for operators to determine (and show to others) if running a2l would be beneficial or not.

Anyway, going out of OBSERVE to run a2l script is OK when all of below are satisfied.

  • Measurements show that coherence has been constantly large for hours (not just one or two) in a single lock stretch.
  • L1 is out of OBSERVE.
  • We're not chopping up otherwise good science segment into shorter than 2 hours chunks (2 hours is just my preference).

Do it sparingly, single IFO data is still valuable for CW.

(Added later at 13:30 local time: If the coherence is super bad like Cheryl's "before" plot for PIT, there's not much point in waiting hours to run a2l, but make sure that the alignment itself is not suspect.)

Displaying reports 57501-57520 of 89077.Go to page Start 2872 2873 2874 2875 2876 2877 2878 2879 2880 End