TITLE: 07/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Travis
SHIFT SUMMARY:  Locking at 50 W for commissioning work.  Evan and Koji replaced ASAIR PD.  No issues.
LOG:
 

23:39 Nutsinee and Betsy to LVEA HWS table

0:07 Nutsinee and Betsy out

Evan and Koji replacing ASAIR PD after lockloss

6:44 EQ/Wind took us down, nobody except Terra is here, calling it a night

Just a quick note becuase this investigation isn't quite complete yet, but I can improve the recycling gain by moving the SOFT offsets in pitch after moving the PRC1 pitch offset.  I have not yet tried adding yaw offsets to this.  With pitch only, I can get up to 30 at 50W (previous record was 28 at 50W). 

What we'd like to do after finding a semi-good spot is to move the beam spot on some of the PRC mirrors (see Stefan's recent alogs for scripts that do this), which will hopefully let us move the spot on POPA back closer to the center.  I wants to be at least 0.65, which is getting uncomfortably close to the edge.

Koji, Evan

We removed the unmodified BBPD S1200242 from ISCT6, and replaced it with S1200236, which has the modifications described in G1500595.

(As Jenne requested) To avoid the confusion, the control room OBSERVE banner on Ops Overview will no longer show if the intent bit is not set. The banner will show only when both "Ops Observatory Mode (Observing)" and "Undisturbed" buttons are engaged.

Betsy, Nutsinee

LLO recently found their HWS mirrors to be contaminated (LLOalog27041). So we went to the table to take a look at our mirrors and took some pictures.

The mirrors are dusty overall and periscope mirrors show sign of coating degradation (I assume that the watermark-looking patterns are coating defects) Betsy later explained to me those marks are leftover marks from First Contact. See below:

HWSX bottom periscope mirror

HWSX top periscope mittor (sorry I wasn't able to get a good shot)

HWSX STEER M7 and STEER M8

HWSX STEER M6 with flash light shined through the back.

HWSY bottom periscope mirror

HWSY top periscope mirror

HWSY periscope mirror with flash light shined through the back

HWSX return beam (without Hartmann plate)

HWSY return beam

HWSX has been giving us data that makes sense. HWSY data however makes no sense. I forgot to stop the code when I took the Hartmann plate out and in and somehow that caused the scripts to think that there were only few hundred peak counts when everything was closed out. I re-initialized the reference images for both HWSX and HWSY. Every necessary optics were aligned and CO2 heating power was set for 2 W PSL input.

Following the same idea as elog 28442, here is a script for moving the beam spot position on PRM (prmspotmove.py).

It monitors IM3 slides, and moves IM4, PRM and PR2 sliders in such a way the the beam spot positions on PR2 and PR3 don't change.

The script was tuned in INPUT_ALIGN (for IM4 and PR2 matrix elements) and PRM_ALIGN (for PRM matrix elements).

Matrix  elements (in rad /rad IM3)

pitIM3toPR2=+0.0022;
yawIM3toPR2=+0.0055;
pitIM3toIM4=-1.3;
yawIM3toIM4=+0.92;
pitIM3toPRM=-0.009;
yawIM3toPRM=+0.031;
 

Also attached is the python script used for finding the matrix element, getMx.py.

Decreased CP3 LLCV from 24 to 21% open

TITLE: 07/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Travis
SHIFT SUMMARY:  After performing initial alignment this morning, locking was difficult. And earthquakes. And Stefan.

17 seconds to overfill CP3 with LLCV bypass valve half turn open

NOTE: as soon as I opened the bypass exhaust valve vapor and liquid poured out, even before opening LLCV bypass valve

We will most likely need to reduce the LLCV % open tomorrow when CP3 Dewar gets filled.

On the run up to ER10 and O2, I am regularly reviewing code which is locally modifed and not committed to the SVN repository. I have cleared out most of the outstanding mods for: front end source code, filter module files and guardian code. Items which are scheduled for install tomorrow have been kept locally modified for now.

I noticed that not all matlab mdl source files have been generated with matlab version 2012b (v 8.0). Here are the ones which are different:

2010a /opt/rtcds/userapps/release/isi/common/models/Offset_DOF.mdl
2015b /opt/rtcds/userapps/release/isc/h1/models/h1oaf.mdl
2015b /opt/rtcds/userapps/release/isi/h1/models/h1isietmx.mdl
2015b /opt/rtcds/userapps/release/isi/h1/models/h1isietmy.mdl
 

The version can be found by running my script which_matlab_version.py

ITMX tripped 26 June on Stage1 Actuators at 1209 utc. A 6.4EQ in Kyrgystan at 1117 is a good candidate.

Attachment 1 shows 5 seconds of the MASTER_dof_DRIVE--the output from the model; and, the three horizontal inputs to the model control loops.  Note the H2 drive going fuzzy just after T=29sec.  Any output from the model pushing H2 would also drive H1 and H3 which don't see any drive.  The bottom plot shows the RZ and X motion increasing at the same time while Y motion is unaffected.  A drive only on H2 alone would produce little if any Y motion (on this platform.)

On attachment 2, the horizontal coil monitor currents and voltages are plotted on the middle and lower graphs.  Different time scale with 30 seconds here but T=0 is the same.  Note at T=20 the H2 current does an ugly reverse and hump for a few seconds and then goes back to looking normal.  The H2 Drive and the plant response does not see any of this so it would seem this does not actually get to the Actuator.  The monitors do appear pretty normal until just before T=30 when it goes flat.  This when the H2 DRIVE has shot to narnia.  Note the WD does not trip until almost T=32 after the 8192 model cycles.

While the coil driver monitors show a different behavior here compared to the 13 July EQ trip discussed in 28567, the same arguements hold: 1) no model output only drives H2.  2) H2 only actuation would be sensed most by RZ and X; and, mostly not sensed by Y.  3) The H2 current monitor behavior several seconds before the badness must be suspect.  The voltage trend of H2 is trending higher at the time the extreme RZ and X response starts but it isn't a crazy number especially when compared to H1 voltage at the same time.  The 13 July event sees the H2 current ramping to high levels as the RZ and X sensors  respond.

HWS code stopped during the weekend because the disk ran out of space. I deleted some of the old data and the scripts are running again. I'm working on a script that will delete old data automatically.

Status / Work Permit review

SEI - nothing to report. Tues plans to examine the IMTY coild driver

SUS - No report

CDS - (for Tues)ITMY SEI coil driver investigation/ITM cameras. May restart baffle PD boxes

PSL - ongoing chiller flow sensor errors causing laser trips. 

VAC - BSC Ion pump repcaement scheduled for Tues

FAC - Divers on site to inspect fire water tank.

Software - revisions to be made to GDS programs. Additional framewriter to be added to collect data from concentrator.

A TV crew froim Hong Kong will be on site tomorrow

According to T1500556, current settings for test mass oplevs are:

ITMY oplev PIT noise is close to the DAQ noise floor at about 3Hz, and the DAQ noise dominates the RMS down to 0.7Hz or so. ITMX is OK for RMS due to double 1:10 whitening, but not much better at 3Hz. Not good for oplev damping.

Also it seems totally fine to use two stages of whitening filters for ETMX.

We can set things up like this (changes in bold font):

The filter gains for the high power oscillator monitoring diodes were switched back from 1 to their
old values that were recorded under
20599




Jason/Peter

The IOC for h1cam18 was not running properly, an old image was being displayed and centroid values were frozen.  Tried restarting the IOC, it didn't clear the problem.  Tried rebooting h1digivideo1, it came back OK, but the IOC for h1cam18 wouldn't run.  Tried deleting all of camera 18's log files and restarting, still wouldn't run.  Logged on to network switch to power cycle the h1cam18, then restarted the IOC and it appears to be behaving OK now.

Multiple LASER trips are evident in the trends. Also, apparently, H1:PSL-OSC_DB3_CUR is reporting 100A. This is inconsistent and virtually impossible. Something wrong with the channel. FRS# 5955 filed.

I have been taking spectra from the SR785 (WP6005) whenever I get a chance over the last week to see if there is any evidence of three mode interactions in the 60kHz to 70kHz region that we will not be sensitive to with the aliased OMC DCPD HF channels that we normally analyze.
There is a consistent peak at 62935Hz, this peak is present with no optical power in the arm cavities.
There are several other more transient peaks, one of the times several had large amplitudes is shown in the first figure.
The largest peak is at 63776Hz  The maximum amplitude seen was 5E-6  This is about the same as the 18040Hz mode when it is 2 orders of magnitude above thermal noise and 2 orders of magnitude under unlocking the cavity.
The second largest is at 70160Hz and the third largest at 62336.

There is no evidence of peaks in DARM at this time at the expected aliased frequencies 1760Hz,  3200Hz or 4624Hz and the peaks that appear in the HF channels that do not appear in the normal DCPD channels do not coincide in frequency, see the second image.

Executive summary: 

* Good news - as expected, the 16-Hz comb due to the OMC length dither is gone (at least at this sensitivity level)
* Bad news - low-frequency 1-Hz combs remain, and some new low-frequency combs & lines have appeared 

Some details:

 I initially looked at 15 hours of 30-minute FScan DELTAL_EXTERNAL SFTs (30 SFTs) generated during ER9 and was aghast at how bad the low-frequency spectrum looked, with a pervasive 0.485308-Hz comb ranging up to its 446th harmonic at 216.4 Hz, but when I exclude the three hours of SFTs when the 2-second ALS- glitches were present, things don't look quite so bad (see figure 1 for a sample without removal and figure 4 with removal). I dewhiten according to the new 6-pole / 6-zero, 0.3 / 30 Hz algorithm.
 The infamous 16-Hz comb due to the OMC length dither tracked down and killed here is gone (at least at this sensitivity level and these SFT statistics). As a result the high-frequency band (up to 2 kHz) is remarkably smooth with only violin modes and sporadic isolated artifacts.
 The 1-Hz comb with 0.5-Hz offset remains pervasive, but other prior 1-Hz or near-1-Hz combs with different offsets (e.g., 0.25 Hz) are not strong.
 On the other hand, there is a new near-1-Hz comb (0.996798-Hz spacing) visible to its 204th harmonic at ~203.3 Hz.
 There is also a new near-2-Hz comb (1.999951-Hz spacing) visible on approximate odd-integer-Hz frequencies, starting from ~9 Hz and visible up to ~175 Hz. This is likely the same 2-Hz comb reported in May by Bryn Pearlstone (which Ansel Neunzert kindly reminded me about today). 
 There is a "new" 56.8406-Hz comb visible to its 11th harmonic at ~625.25 Hz, which in hindsight I can see was buried in the O1 spectrum (I overlooked the pattern and indicated the teeth as isolated lines). This time the pattern was strong enough to jump out at me and to jog my memory that this comb was seen in  H2 1-arm data in 2012 in both the arm feedback channel and a quiet sensor-noise-dominated OSEM channel. This seemed to indicate a DAQ system problem at the time. I can see from O1 NoEMi line lists that this comb is pervasive in ISI, SUS and PEM channels at the corner station and both end stations.
 The old "K" comb-on-comb (0.088425-Hz fine comb attached to teeth of a coarse 76.3235-Hz comb) has more 11 more fine teeth visible on the lowest-frequency coarse-tooth comb.
 The old calibration line at 35.9 Hz has been moved to 35.3 Hz. The new excitation lines at 33.7 and 34.7 Hz are easily visible, but not as strong as the primary calibration lines. I found these changes documented here.
 There are sporadic new isolated lines here and there (indicated in line list - see below)
 There is a "crab-killer" broad bump centered at about 58.6 Hz which degrades sensitivity in the Crab Pulsar band of interest (~59.3 Hz). On the other hand, the whole noise floor is elevated w.r.t. O1, anyway. So it may be premature to worry about the bump.


Figure 1 - spectrum for 50-100 Hz when the 3-hour 2-second-glitches stretch is included (~0.5 Hz lines marked with 'h' for 'half')
Figure 2 - 0-2000 Hz (removing 3-hour bad stretch from here on)
Figure 3 - 20-50 Hz sub-band 
Figure 4 - 50-100 Hz sub-band 
Figure 5 - 100-200 Hz sub-band
Figure 6 - 1300-1400 Hz sub-band (illustration of how clean the high-frequency band is)

Also attached are a larger set of zipped sub-band spectra and a lines list (excluding the bad 3-hour stretch). Note that because the statistics here are two orders of magnitude smaller than used for the full O1 run report, I am not yet removing lines seen then that may yet re-emerge with more accumulated post-O1 data. So many of the line labels in these figures are buried in the noise fuzz for now.

Line label codes in figures:

b - Bounce mode (quad suspension)
r - Roll mode (quad suspension)
Q - Quad violin mode and harmonics
B - Beam splitter violin mode and harmonics
C - Calibration lines
M - Power mains (60 HZ)
O - 1-Hz comb (0.5-Hz offset)
o - weaker 1-Hz and near-1-Hz combs (various offsets, including zero)
H - 99.9989-Hz comb
J - 31.4127 and 31.4149-Hz combs
K - 0.088425-Hz comb-on-comb
t - 1.999951-Hz, 2.07412-Hz and 2.07423-Hz combs
D - 56.8406-Hz comb
x - single line (not all singlets in the vicinity of quad violin modes are marked, given the known upconversion)