SudarshanK, DarkhanT, EvanG

Pcal PD Calibrationat at ENDY was completed today. The results are within the variation seen in the past. A more detail report coming soon.

• TITLE: 12/22 Eve Shift: 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC"

• STATE Of H1:Observing at 78Mpc for ~1 hours

• OUTGOING OPERATOR: Cheryl

• QUICK SUMMARY: Seems to have been a quick recovery form maintenance day! Wind is <15mph, useis 0.5um/s, PSL 21.9, CW inj running.

Kyle, Bubba 

Today we decoupled both ends of the external 3/8 tubing used to sense the liquid pressure sampled at the bottom of CP3's inner LN2 vessel -> We then blew through it with bottled UHP N2 to verify that it wasn't the source of obstruction -> Next, we reconnected the end at the vacuum interface and pressurized the tubing to 15-20 psi in an attempt to "blow" the obstruction back into the liquid vessel.  We also tried "pumping" the line to rough vacuum -> A second attempt at pressurizing it, this time to 30 psi, did not dislodge the obstruction

1500 hrs. local -> Manually overfilled CP3 via the LLCV bypass circuit (liquid exiting exhaust line) 

We will manually top off pump periodically until issue is resolved -> The LLCV is in manual mode at a constant 15% open (recent average prior to problem was ~19% open) 

State of H1: Low Noise, A2L measurements finished, now in Observe

JeffK and I talked to LLO, and they are working on a measurement, and expect to be back in Observe soon.

Help with Mantenance and Relocking: Kiwamu, JimW, Ed, JeffK, Jenne

Relocking Details/Issues:

1. MICH DARK did not lock.  It WAS well aligned, but would not catch.  MICH DARK is needed for end of O1 calibraitons, so some effort to lock and or diagnose the issue was made, and not successful.
2. H1 broke lock at ENGAGE_ASC twice, and JimW offered that sitting in each part, part 1, part 2, and part 3, and waiting for ASC signals to settle each time, has helped get H1 through those steps.  This issue and the necessary work around are new in the last two weeks.
3. H1 then stalled at engaging the ISS 2nd Loop, which had to be engaged manually.

Currently: H1 in Observe at 23:24:36UTC, and as of this alog, range is 80Mpc.

A few weeks ago, Hugh switched the end station BSC Z blends to 45 mhz. We've done a bit of looking at this, and it seems okay, so this morning I switched the CS BSCs to 45s on Z as well. First attached plot shows the improvement in the Z direction on ITMX, the BS and ITMY were very similar so I'm not posting them. The green lines are the ST1 T240 ASD (solid) and RMS (dashed) with the Quite_90 blend, brown is the T240 ASD (solid) and RMS (dashed) with the 45 mhz blends. Purple is the ground from when the 90mhz blends were engage, black is the ground with 45mhz. We were getting a factor of 3 to 5 suppression of the microseism, with the 45 mhz blends we get a factor of ~40. There is some increased motion in the 20-80 mhz region, but the RMS of the ISI is still lower.

One possible problem with running the 45 mhz blends in Z is increased coupling to St1 RZ. I've looked at the local ISI sensors, and this doesn't seem to be affecting us yet. In fact, the T240s (which are suspect because of Z/RZ coupling) and the CPSs both show less motion at the microseism with the 45mhz blends, second plot, red and green are CPS and T240 RZ with 90mhz blends, blue and brown are CPS and T240 RZ with 45mhz blends. Additionally, The RZ drive doesn't seem to be significantly different, implying that we aren't contaminating RZ with increased Z drive (third plot, pink is with the 90mhz blends, light blue is with the 45mhz blends). After we relock today, I'll try to do a comparison with the ASC controls from last night.

The volume for the alarms were so very quiet this morning I couldn't hear them, and the volume for the verbal alarms was reasonable, and of course, when I tried to raise the alarm volume, the verbal alarms were too loud.

JimB discovered that the sound settings on the computer are seperated into "alarms" and "computer" volume sliders, and the alarm volume was set very low.

I discovered that to have the alarm volume about the same as the verbal alarm volume, the volume on the alarms needs to be at max. and the verbal alarms need to be at about 1/2 of the total possible volume.  

Picture attached.

J. Kissel, H. Radkins, J. Warner [+ J. Driggers and E. Hall for code assistance]

After Hugh had gone down to the end-stations to check the centering of the STS-2s (aLOG pending), we looked back at Brian's LHO aLOG 22985 that reminds us that we digitally store the mass centering information. There were a few mysteries still associated with those channels, however, namely whether they were the X/Y/Z mass positions or U/V/W mass positions. As such, we went out the CER / SEI racks with a DVM and toggled some switches. We learned several things:
(1) The output of the X/U, Y/V, and Z/W BNC spigots are proportional to each of the stored IOP ADC EPICs channels 
(2) To match them up, one must account not only for the 40/2^16 [Vpp/ct] ADC gain, but the gain difference of 2.0 [V_adc/V_spigot] between the spigot and the ADC channel because of the single-ended-to-differential driver in the STS interface chassis (see D040019, pg 5 specifically). Thus, to turn the ADC channel back into the volts which the STS-2 manual recommends for being less that 1.5 [V], one must multiply by (1/2) * (40/2^16) = (20/2^16) = 3.0518e-04 [V/ct].
(3) All of the corner station STS chassis had their XYX / UVW switches toggled to XYZ.
(4) The spigots are marked as "X/U", "Y/V", and "Z/W," the output of which (either X/Y/Z or U/V/W) should be controllable by the rocker switch to the right of the spigots (see attached image). However, Hugh and I toggled this switch on all three STS2 chassis in the corner station, and when toggled to U/V/W, the spigot output went to 0.0 [V] (maybe occassionally we'd see a ~1 [mV] offset) and the ADC readout went to ADC-noise-level zero. So either we're missing something, or the U/V/W readout functionality is busted on these chassis. Hopefully, it's busted in the "it never worked" sense, and the X/Y/Z readout *is* actually the U/V/W readout, and we're constantly monitoring it. 

Hurumph.

Anyways, as a by-product of this investigation, I (with the help of Jenn and Evan) wrote a python script called /opt/rtcds/userapps/release/isi/common/scripts/check_sts_centering.py that takes a 10 second average of these IOP channels (ifo is an input argument, but otherwise hard-coded to be the IOP channels mentioned in Brian's aLOG), calibrates them into "STS Volts," compares them against the 2 [V] threshold, and spits out whether an STS on site ios out-of-spec. Here's today's results, to show how the script works: 
/opt/rtcds/userapps/release/isi/common/scripts$ ./check_sts_centering.py H1
Averaging Mass Centering channels for 10 [sec] ...


There are 3 STS proof masses out of range ( > 2.0 [V] )!
STS B DOF X/U = -4.446 [V]
STS EX DOF Y/V = 7.656 [V]
STS EY DOF Z/W = -2.429 [V]


All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = 0.367 [V]
STS A DOF Y/V = -1.019 [V]
STS A DOF Z/W = -0.359 [V]
STS B DOF Y/V = 0.751 [V]
STS B DOF Z/W = -0.422 [V]
STS C DOF X/U = 0.88 [V]
STS C DOF Y/V = -0.508 [V]
STS C DOF Z/W = -1.313 [V]
STS EX DOF X/U = -1.112 [V]
STS EX DOF Z/W = 1.111 [V]
STS EY DOF X/U = 1.025 [V]
STS EY DOF Y/V = 0.828 [V]


Assessment complete.
/opt/rtcds/userapps/release/isi/common/scripts$


We intend to, for now and now that it's so easy, check the STS centering every maintanence day. As Jenne suggests, we could take the script up another 10 levels and code it up as a guardian monitoring node for the SYS_DIAG to watch that'll then notify the operator only when it has surpassed the threshold, that way we don't have to remember to check. But we'll leave that for another scripter for another day. Script has been committed for use at both sites.

The /gds-h1 filesystem has been replicated and was remounted this morning on h1dmtqfs0 and the corresponding DCS QFS readers (gateway, lhoarchive, qfs-nfs1, qfs-nfs2, and qfs-nfs4).  The new filesystem resides on what had previously been a spare CDS SATAboy.  The old filesystem has been renamed xgds-h1 and is no longer is use.

Maintenance:

- 16:02UTC, Christina at EY cleaning

- 16:02UTC, Chris, EY activities

- 16:05UTC, Richard, audio signal work, CR, CER

- 16:09UTC, closed shutter on OMC, ending the lock

- 16:10UTC, JeffK, charge measurements started on ETMY and ETMX 16:11UTC

- 16:13UTC, Bubba to EX

- 16:15UTC, JoeD, escorting Sprague around the site

- 16:17UTC, Ryan finished with alog maintenance

- 16:32UTC, Christina, leaving EY

- 16:40UTC, Sudarshan, ..., EvanG, pcal work at EY

- 16:40UTC, Richard to EY to take pictures

- 16:58UTC, Christina leaving EX

- 17:01:15UTC, GRB test, successful

- 17:03UTC, Jason done with oplevs and reset of PSL chiller watchdogs

- 17:09UTC, JeffK, done with charge measurements on EY

- 17:10UTC, Christina to LVEA

- 17:12UTC, JeffK, done with charge measurements on EX

- 17:20UTC, Hugh at EY, re-zeroing STS, and will turn off sensor correction on ISI

- 17:24UTC, JeffB done with forklift work

- 17:24UTC, Richard back from EY

- 17:26UTC, EY HEPI/ISI/SUS tripped with work on STS re-zeroing

- 17:31UTC, Norco truck 1 arrived with liquid nitrogen delivery, heading down X arm

- 17:40UTC, Norco truck 2 arrived with liquid nitrogen delivery, didn't see which arm/CS

- 17:45UTC, Bubba in LVEA to check on long-term storage

- 17:45UTC, Sprague checking traps along the arms, and will check out when done

- 17:49UTC, Joe to LVEA

- 18:49UTC, JeffK and Hugh to CER, HEPI/ISI electronics, not ones controlling the IFO

- 19:01UTC, Joe in LVEA

- 19:02UTC, JeffK and Hugh, out of CER

- 19:10UTC, Hugh to CER

- 19:15UTC, Richard to CER

- 19:20UTC, Richard to CER

- 19:26UTC, DaveB to CER

- 19:27UTC, Hugh out of LVEA/CER

- 19:27UTC, Cheryl out of LVEA - lights are out, sweep is done

- 19:37UTC, Norco truck leaves the site

- 19:46UTC, Cheryl, PSL IOO rotation stage search for home

- 19:47UTC, Sudarshan and company out of EY EVA

- 19:48UTC, Cheryl, offload IMC WFS

- 20:05UTC, Cheryl, start of relocking H1

The Verbal Alarms announced a GRB at 17:01:15UTC, which was actually a SNEWS allert test.

The website tracking alerts has the SNEWS allert listed as a GRB under the "search" field, so this is likely why the Verbal Alarms read it as a GRB.

J. Kissel

This is your weekly ETM charge measurement update! While charge continues to slowly accumulate on both test masses, I think we can begin to say that the rate of charge accumulation (as measured by effective bias voltage and L, P, and Y actuation strength) is slow enough on H1 SUS ETMY that we can get through the remainder of the run without flipping the ESD bias voltage sign, and retain low enough systematic error in the calibration model to stay within the desired 10%. However, one of the first things we should consider doing once the run is complete (after the calibration run is complete) is reducing the bias voltage by half to continue to slow the rate of charge. Oh, and H1 SUS ETMX continues to slow its accumulation rate thanks to our high duty cycle and turning of the bias when its not needed.

See attached images for depictions of the trends both in effective bias voltage and actuation strength in Pitch and Yaw (+ Longitundinal for H1 SUS ETMY).

I increased the power on the BS and SR3 oplev lasers this morning by ~5%.  I used the voltage read out of the "Current Monitor" port on the back of the laser (this port monitors the laser diode current, outputs a voltage).  The old and new values are listed below, as well as the new SUM counts.  Since I had to open the coolers the lasers are housed in they will need ~4-6 hours to return to thermal equilibium; at that point I can assess whether or not the glitching has improved.

• BS OpLev
  • Old voltage:  0.987 V
  • New voltage:  1.036 V
  • New SUM:  ~33500 counts
• SR3 OpLev
  • Old voltage:  0.889 V
  • New voltage:  0.933 V
  • New SUM:  ~40900 counts

I reset the 35W FE laser watchdog at 17:01 UTC (9:01 PST).

Activity Log: All Times in UTC (PT)

08:00 (00:00) Take over from TJ
08:10 (00:10) GRB Alert. IFO in Observing mode. Spoke to LLO
10:01 (02:01) Gerardo – Back from Mid-Y 
10:15 (02:15) Gerardo – Going back to Mid-Y
10:16 (02:16) Kyle – Called to check on problem with CP-3
10:17 (02:17) John – On site with Gerardo at Mid-Y
12:45 (04:45) John & Gerardo – Back from Mid-Y – leaving site
14:00 (06:00) Restart CS weather station code
15:30 (07:30) CP-4 is dropping N2. Percent down to 83%. Sent E-Mail and V-Mail to Gerardo 
16:00 (08:00) Turn over to Cheryl

End of Shift Summary:

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

Support:  Gerardo, John
 
Incoming Operator: Cheryl

Shift Detail Summary: Locked in Observing mode for entire shift. Take down IFO for start of maintenance window. 

There were problems with CP-3 (aLOG #24370, 24379) which Gerardo and John worked on. After Gerardo left CP-4 started to show dropping N2 levels as well. Down to 83%. Sent E-Mail and V-Mail to Gerardo. 

John, Kyle and Gerardo

One of the lines for CP3 pressure transducer appears to be plugged.
A first attempt to unplug it was not successful, for now we will continue to fill the pump manually and we'll continue to monitor CP3 level.  Alarms will continue for now.