TITLE: 04/16 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.12 μm/s
QUICK SUMMARY:
TITLE: 04/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 62Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: locked all shift, no issues other than some wind causing some noise, web page stat was yellow is now green
I have just restarted the primary and redundant pipelines at LHO at GPS time 1176395700. Due to an issue with the computed kappas being out of the expected range, h(t) was marked bad by the calib_state_vector. This is due to a bug in the most recent release of the calibration code, gstlal-calibration-1.1.5-v1. For more information on this bug and the proposed fix, see https://bugs.ligo.org/redmine/issues/5494
TITLE: 04/16 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: Cheryl
SHIFT SUMMARY:
LOG:
Quiet night again. Apparently, something happened with h(t) last night at 3:11 local (?), got a call from UWM about it. Sounds like they are looking into it.
TITLE: 04/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
One lockloss through the night (~30min down).
Had a couple of SDF diffs:
Oh, and forgot to mention Jim & I encountered a porcupine at the OSB entrance last night at around 12:30am! It was right near the 3-wheel bike. It slowly walked away when it heard us, but just be careful!
Going on 23.5hrs of lock. Range is bobbing around 65Mpc. Laser power is ~26W.
L1 was down for about 30min and contemplated jumping out of OBSERVING to run an A2L, and damp out the 4.7kHz resonance, but didn't get the chance.
TITLE: 04/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
Wind: 3mph Gusts, 2mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.12 μm/s
Quiet seismically.
QUICK SUMMARY:
TITLE: 04/15 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: locked entire shift
LOG: tours around noon, about 4 sets of high school students
TITLE: 04/15 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: Cheryl
SHIFT SUMMARY:
LOG:
Quiet shift.
TITLE: 04/14 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
A couple of odd locklosses (posted earlier). Current lock started out decently, but the range has slowly trended down.
Laser power has been drifting down (see earlier alog), and currently are at 25.9W.
3:41: Lockloss
PSL Issues: (I marked some CORRECTIVE MAINTENANCE time, but not sure this is FRS-worthy):
Corresponding with this lockloss, had the following PSL Guardian Messages:
For ISS Diff Power (it was oscillating between 3-14), I turned OFF the Autolocker, clicked Manual & I thought I turned it OFF---so I could tweak the Ref Signal, but I didn't have luck here. I tried restoring everything.
Since Noise Eater was RED/Off, I went out to the LVEA to toggle the switch. This made the Guardian Messages go away, and I went about locking.
SDF Diffs & Servo Gain Changes
Upon reaching NLN, had a few diffs (attached).
PSL Power Drifting Down, Servo Gains, & ACCEPTING Diffs Until Alignment Can Be Tweaked Up
Ended up calling Keita about these Servo Gains before attempting to go to OBSERVING.
Looks like the PSL power has been dropping over the last month (see attached IMC trends) and we finally took a jump down to where the REFL servo gains were increased & noticed by SDF (see attached trends of ISS diff power, PSL Power, & IMC/LSC REFL SERVO IN1GAINS).
We also looked at the DARM (H1:CAL-DELTAL_EXTERNAL_DQ) spectra & compared tonight (blue) to March 19 (red). Since the high freq isn't getting increasingly noisy with higher frequency, we are OK with the SERVO gain values.
So, if we have more of these DIFFs over the weekend, we should ACCEPT them in SDF. Hopefully we can last until Peter/Jason can touch up the alignment for us next week.
5:20 Back to OBSERVING
This ended a 31hr8min lock. Had a few issues for ALSx, but it seems to be fine now. Working on getting it back.
Not sure of lockloss. Looks pretty quiet seismically and nothing looked amiss before the lockloss.
Notes:
TITLE: 04/14 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 14mph Gusts, 11mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.13 μm/s
A little breezy, but has been coming down over last 5hrs. useism is also very quiet as well.
QUICK SUMMARY:
Shift Summary: Run A2L check script. Pitch is at or below the reference; Yaw is up to 0.6. Took the opportunity in the afternoon to run the A2L repair script, while LLO was addressing rung up violin modes.
Overall a good day of Observing. No significant problems or issues to report.
Drop out of Observing at 21:20 (14:20) to run A2L repair script. LLO is out of Observing while they damp their violin modes. LHO is back in Observing as of 20:26 (14:26).
J. Kissel I'd collected charge measurement data this past Tuesday (4/11); here's the processed data. Conclusions: - ETMX continues to hover around an un-impactful 10-20 [V], because we have a relative high observing duty cycle. (see attachments 1 & 2) We shut off the ETMX ESD's bias voltage during observation, which means stray charge in the vacuum system is only attracted by the ~10-20 [V] instead of the ~400 [V] in place when we're down or acquiring lock. As long as we continue doing so, we should be fine for the foreseeable future. - ETMY continues to accumulate charge. (see attachments 1, 2, & 3) While we flip the sign of ~400 [V] bias of the ETMY ESD while down and during acquisition, the high observation duty-cycle means it's essentially always one sign. That means we're accumulating charge at a relatively fast rate of 5 [V/month] -- as reported by the *angular* effective bias voltage (see 3rd and 4th attachment). What *really* matters is the relative longitudinal actuation strength -- relative to when we last reset the clock (in this case January) -- and with this we're still in the greener side of the yellow zone (see 5th attachment). As such, my recommendations from last week (LHO aLOG 35366) are now solidified: Just before we vent on May 8th, during last minute preparations as we bring the IFO down, let's - Turn OFF the ETMX ESD bias completely, and leave it OFF - Leave the ETMY bias ON at 400 [V], with the opposite sign as in observation (Negative in NLN, switch to Positive for vent) for the duration of the vent (i.e. until we open back up to the arms)
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 72 seconds. LLCV set back to 20.0% open. Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 1984 seconds. TC A did not register fill. LLCV set back to 37.0% open.
Raised CP4 to 38% open.
Is this something Operators should worry about, or is it handled by others offsite? Jim & Cheryl both alogged status and that Aaron was working on/fixed it. Just wondering if this rises to the state of needing an alarm because it affects H1 data, or does it just mean one of our tools is having an issue (i.e. GWI.stat being yellow and the Daily Summary Pages reporting an on BNS range).
Should we be checking the GWI.stat through the shift (I can put it in our Shift Check Sheet), or is this something we leave to off-site staff? For GWI.stat's Help Page it says we should report bugs to Peter Shawhan. I'm not sure of who we report Summary Page bugs to.