a2l measurement shows YAW out up to .85. Livingston is down.
TITLE: 03/15 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 15mph Gusts, 13mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.24 μm/s
QUICK SUMMARY:
TITLE: 03/15 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
LOG:
Quiet shift. Nothing to report.
Flow rates for head 1-4 for ~a day after the sensor replacement. The signals look relatively clean. Head 3 looks a little ragged compared to the others. Power meter flow and front end flow rates look okay. The front end flow rate looks a little noisy in its maximum recorded value.
TITLE: 03/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 71Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
Recovery from Maintenance Day for the first 1-2hrs. And most of the shift we have had sustains winds around 10-20mph (with gusts above 40mph).
LOG:
Terra, Corey
PI Mode #27 was a bit touchy this evening. After two locklosses, talked with Terra. It's frequency was 14039.5Hz. The original filter being used was 14038.5Hz. We ended up switching to one a little closer: 14040Hz.
So for this current lock, we
Note For Operators After a lockloss due to a PI Mode:
OK, off to cook supper!
After Maintenance had a few SDF diffs and went through them with Kiwamu and Nutsinee. All of them were ACCEPTED (namely for ASC, OMCPI, PSLFSS, etc.).
After the last few locklosses, there have been some repeated TCS diffs (attached is a snapshot of the channel). Nutsinee said we can ACCEPT them (they are tiny changes 10^-15), and can probably NOT MONITOR them eventually...but we should wait for call from TCS person.
Terra & I also switched to a different filter for PI Mode#27, so this was also ACCEPTED.
After all the hub bub of a Maintenance Day, the site is somewhat quieter (no one here and the winds are finally mostly under 20mph).
Made a couple of lock attempts starting just before my shift. First two locks did not last long:
As noted earlier we ran the gamut of rung up modes (roll, some bounce, violin & now noticing PI modes). So I am going to stay at DC Readout for a while (Terra suggested ~15min) & then we'll go from there.
2:34 - 3:32: Observatory Mode was accidentally left in OBSERVING! It should have been taken to LOCK ACQUISITION after the lockloss.
Taking a screenshot for Hugh.....
From what I can see, the BRS STAT guardian is just complaining that BRSY is damping (either from the work earlier or the afternoon winds). From the other status lights, it looks like the sensor correction is probably turned on. If there are no SDF diffs on the ETMY ISI, then everything is probably okay. I can check remotely if it's needed.
I think we are good. While on the phone with Hugh, everything cleared up for BRS-y. Probably just dealing with a noisy/windy EY. Everything was fine with SDF for SEI.
TITLE: 03/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
Wind: 31mph Gusts, 25mph 5min avg
Primary useism: 0.19 μm/s
Secondary useism: 0.28 μm/s
It's become windy in the last few hours with gusts over 40mph (might be subsiding now).
QUICK SUMMARY:
Cheryl handed over an H1 which was in a LOCKING state. Kiwamu noticed that we had rung up Roll modes & so he addressed them a bit & then we went to for NOMINAL LOW NOISE.
Locked up but the range was down at a paltry 60Mpc. Now it was still windy. And we also have the BRSy in an odd state after Maintenance Day. (Ultimately lost lock after a pesky PI Mode 27.)
Jason, PeterK, Kiwamu (WP 6522)
We powered up the diagnostic bread board (DBB) this afternoon during the maintenance period and compared the pointing jitter signals against those from the bullseye sensor.
They show good agreement in their spectral magnitudes and showed high coherence. So pointing jitter noises seen by the bullseye are consistent with what the DBB sees.
* * * * * *
The attached are the plots showing the calibrated jitter noises and their coherence. As we know from the past measurements (e.g. 31631), the QPD2 spectra of the DBB show lower magnitudes than that of QPD1 by a factor of 5 or so across the entire frequency band. The calibrated bullseye jitters are found to be roughly at the identical magnitude to those seen by QPD1 of the DBB. Also, looking at the coherence, we found that the bullseye sensor seems to be almost at the same Gouy phase as QPD1.
After the measurement, we powered off the DBB by following the standard procedure (31717).
I also changed the input matrix for the pitch jitter mode of the bullseye in order to obtain zero offset when the beam is well centered. Now the input matrix is set such that (lower segment, upper right segment, upper left segment) = (-2, +1, +1) which had been (-1, +1, +1) since the week before the last week (34460). The calibration coefficient for it was then changed to reflect this change by a factor of 0.67. I updated the SDFs.
Head flow rates for heads 1-4 for the past 6 hours. The hiccups for the first 40 or so minutes are due to starting and restarting the crystal chiller as we checked for leaks. Also shown are the flow rates for the front end laser and the power meter circuit. These were previously disconnected when we were trying to debug what was causing the chiller to trip so often. Now that all four sensors in the heads have been replaced, they are not likely to be a cause of a trip unless there are still stray bubbles working their way through the system.
Light maintenance day for CDS.
HWS rsync data to LDAS
Dave
tested the autorun of the daily rsync of HWS data from h1hwsmsr to LDAS.
Corrected WAP unit name in lvea
Jim, Dave:
the LVEA wap was the spare unit (wap-spare), this was renamed wap-lvea. Output of wap_scan is now correct.
DIAG_MAIN guardian node restarted
Dave:
I restarted DIAG_MAIN to recoup on some memory.
Added h1iopasc0 to the periodic DIAG_RESET
Dave:
To get better statistics on the timing error of h1iopasc0, its latched STATE_WORD will now be cleared every minute (added this dcu to the script which clears the end station SUS errors)
WP 6511
In preparation for the installation of the new TCS HWS digital camera, 4 network cables were pulled in this morning. Cables run from the CER FAC-C1 rack to H1:SUS-R3 field rack (HAM4). The cables were landed as follows:
H1:FAC-C1 - GigE patch panel (U36, U35) on ports 53-56
H1:SUS-R3 - GigE patch panel (U42) on ports 5-8
Installed a patch panel with a RJ45 and 3W3 power connector on the east side of the TCS HSW enclosure.
TITLE: 03/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: maintenance most of the day, just relocking now, H1 is on it's way to NLN
LOG:
J. Kissel, B. Weaver I attach the the usual year's trend of effective bias voltage accumulated from charge, where the last few weeks are new data points. We expect and hope the trend of effective to be hovering between +/- 10 [V], which keeps the relative actuation strength change to under a few percent. We see that ETMX looks great in all quadrants. This is likely because our nominal low-noise (NLN) duty cycle is so high -- when in NLN, we turn OFF the ETMX ESD, so it does not have a ~400 [V] on to attract stray charge. Conversely, because the NLN duty cycle is so high, ETMY is starting to accumulate a significant amount of effective bias voltage. Although we've been flipping the sign of the bias voltage every time we're not using the ETMY ESD, that's "unfortunately" only 10-15% of the time these days with our awesome duty cycle. We should consider flipping sign of the bias voltage we use for ETMY in NLN soon. Perhaps the calibration group can take this opportunity to create a new calibration epoch, and reduce the reference time coupled cavity pole frequency...
16:29 H1 back to observing