I've posted a note in the DCC with some information about our duty cycle durring ER7, and some of the causes of downtime. 

https://dcc.ligo.org/DocDB/0120/T1500368/001/ER7DutyCycleNote.pdf

  I will possibly update this with more information about DRMI locking durring high winds and when it is and is not necessary to wait for bounce and roll modes to ring down in the coming days. 

Sheila, Elli

I moved the ITMs to improve the recycling gain, as well as the PRM.  To get from a recylcing gain of just under 36 to 39 I mostly moved ITMY in yaw.  This may be a different alignment than what we were using durring ER7, but it seems to be an improvement over the alingments we had yesterday, so we have updated references for now.  The green alignment in the X arm did not change, but Elli and I redid the green QPD offsets and camera position for the Y arm.  We lost lock and relocked allowing the ASC to engage with the guardian using these new IR QPD offsets, which was fine and brought us to a recycling gain of 39 again.  For now the many people who want to do things incompatible with full locking have taken over the IFO.  

Old offsets:

  sheila.dwyer@opsws3:~/StripTools$ caget H1:ASC-Y_TR_A_PIT_OFFSET H1:ASC-Y_TR_A_YAW_OFFSET H1:ASC-Y_TR_B_PIT_OFFSET H1:ASC-Y_TR_A_PIT_OFFSET

Elli, Hannah

To create a reference of the ITMX Green for locking.

Using singleImage_checkSaturation.m (/ligo/home/eleanor.king/scattering/singleImage_checkSaturation.m) we took images of the ITMX/Y Green cameras from ER7 ( /ligo/data/camera/archive/2015/06/05 "H1 ITMY Green (h1cam24)_2015-06-05-16-30-58.tiff" and "H1 ITMX Green (h1cam22)_2015-06-05-15-16-43.tiff)

Compared them with pictures taken today. (/ligo/data/camera "ITMY_green_illuminator_H1 ITMY Green (h1cam24)_2015-07-09-16-03-52.tff" and "IMTX_green_illuminator_H1 ITMX Green (h1cam22)_2015-07-09-16-03-43.tiff")

The cameras appear stable. We determined this by looking at the relative position of prominant features of the scattering.

FYI:

The lock-out on the L1 PSL is now released.

All conditions in the original memo have been met. 

The release memo is here: https://dcc.ligo.org/M1500231

Kiwamu, Stefan

We noticed that in full lock (before power up) we again have questionable WFS. Indeed it seems to again be SRCL1 YAW that runs away - slowly at low power, but rapidly at high power. This is all a deja-vu, see elogs 18442, 18923, 18931.

More investigation suggested that it is actually the QPD loops that pull us into a regime where the other loops are not stable. So for now we changed the QPD loop offsets at low power to just keep us at the same location:
  New values: H1:ASC-X_TR_A_PIT_OFFSET H1:ASC-X_TR_B_PIT_OFFSET H1:ASC-X_TR_A_YAW_OFFSET H1:ASC-X_TR_B_YAW_OFFSET
   -0.084
   -0.212
   -0.023
    0.006
  Old values: H1:ASC-X_TR_A_PIT_OFFSET H1:ASC-X_TR_B_PIT_OFFSET H1:ASC-X_TR_A_YAW_OFFSET H1:ASC-X_TR_B_YAW_OFFSET
   -0.029
   -0.158
   -0.007
    0.105

However we still lost it on POWER UP. More work needed here.


We also reverted the changes from earlier today (alog 19511): ETMX ISCINF gain back to 1, and the L1 gain back to 0.28. This now gave us a lower peak-peak ESD drive and - unlike earlier today - ALS DIFF engaged just fine... (no idea why it acted up earlier...)

Evan, Nic, Stefan, Elli, Sheila

After spending some time to recover alignment, fiber polarization, turn TCS back on, ect, we have started to attempt locking. 

The first problem we ran into was that ALS DIFF was not locking, the first problem we found was that the linearization was off.  In addition, it seems that the ESD gain has been reduced by a factor of 2 after the vent and discharging.  The attached screenshots show the OLG and crossover measurements with a factor of 2 added in drivealign, they match the references well this way.  The green reference in the OLG measurement shows the gain when we managed to lock with the nominal settings from before the vent.  

We have edited the guardian to add a factor of 2 gain in ETMX ISCINF, and reduced the L1 gain from 0.28 to 0.14 to keep the crossover around 1 Hz.  The drives with DIFF locked are attached.  

We were able to lock on DC readout, but Evan found that the DARM gain was 4dB too high, so he reduced the gain in the DARM filter bank to 900 from 1200.  We made it to DC readout and lost lock durring the power up.  

More charge measurements on ETMs. Plots are attached.
Still no charges.

Earlier today, I wrote a couple out of loop feedforward filters to the BS ISI foton file using Foton. When I hit the load coefficients button (while the ISI was isolated, the ff paths were off, so it shouldn't have done anything), the ISI tripped, hard. It rang up the T240's pretty bad and I couldn't isolate the ISI for several minutes after. Worried I had inadvertantly written some other filter I ran a diff on the most recent archived file and the file created yesterday when Jeff restarted the models. This showed a whole bunch of filter coefficient differences, which shouldn't have been there (as reported by a diff of the two archive files, I don't know exactly what changed, see attached). Talking to Jim, Dave and Jeff, it sounds like the glitch was probably caused by my having used Quack recently (June 22nd) to load some blend filters. Jeff's model restart (and even a prior model restart on June 30) simply inherited that quack-written file. Today was the first time the BS's foton file was opened and saved in Foton. Quack can apparently load coefficients with higher precision than Foton will accept, so when you open and save a "too high" precision filter with Foton, it rounds the coefficients off. Sudden change in precision of SOS coefficients in the blend filters = bad for isolation loops = bad trip.

We've seen this Foton vs. Quack Rounding problem before -- see e.g. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=3553 -- and it's still biting us.

This sounds like a relatively easy thing to control for, I can think of two ways:

- getting Quack to check and do the rounding on it's own before writing to the Foton file.

- have the post-build script run a "foton -c" on all filter files before the model gets restarted.

Is there someone in the CDS group who can fix this? Maybe it has been? There are several versions of Quack running around, June was my first attempt with it, maybe I used the wrong one.

I used /ligo/svncommon/SeiSVN/seismic/Common/MatlabTools/autoquack.m

 https://svn.ligo.caltech.edu/svn/seismic/Common/MatlabTools/autoquack.m

Last Changed Author: brian.lantz@LIGO.ORG
Last Changed Rev: 7939
Last Changed Date: 2014-02-14 15:38:15 -0800 (Fri, 14 Feb 2014)
Text Last Updated: 2014-02-14 15:48:16 -0800 (Fri, 14 Feb 2014)

0712 - Joe Gleason to EY

0715 - J Gleason out

0858 - Jim W finished with BSC measurements

0859 - Leonid starting charge measurements EX/EY

0900 - Fil to EX for ALS fiber conduit install

0923 - Richard to EX to help Fil

0924 - Jordan, Vincent to EX for PEM cabling

0934 - Gerardo to EX prep for gate opening

0953 - Richard back

1000 - Kyle to EX

1114 - Nutsinee to EY for PCal measurments

1115 - Vincent to CER

1121 - Vincent out but then to LVEA for PEM cables

1125 - Bubba at EX (according to card reader)

1127 - Kyle, Gerardo back from EX and goin intot the LVEA to HAM6

1138 - Ed to EX to adjust OpLev

1139 - Nutsinee back

1155 - Kyle, Gerardo out

1232 - Fil to MY

1323 - Gerardo, John, Bubba at EX

1408 - HEPI alarm. Pump pressure was "Not Okay" Hugh was contacted(see alog)

1410 - Hugh to EY to investigate

1445 - Kyle to EY

1506 - Kyle back

1550 - Elli, Sheila to LVEA to turn ON CO2X laser

1558 - Elli, Shelia out of LVEA and now going to the Ends to turn ON the ring heaters

This morning when Jim B. restarted H1IOPSEIH23, I forgot to set the IMC_LOCK Guardian to OFFLINE. The IMC kept its lock but the WFS ran away with the HEPI misalignment. To avoid this in the future Jeff, Sheila, and I decided to have IMC_LOCK check that the SEI managers for HAM2/3 are ISOLATED. I added a new decorator to the IMC_LOCK  Guardian (@sei_state_checker) that will make sure HAM2 and HAM3 SEI managers are in the ISOLATED state. If they are not, it will return the MOVE_TO_OFFLINE state. OFFLINE is now a protected state(redirect = False) and has a run condition that will not allow the Guardian to move on unless the SEI managers are ISOLATED (Thank you, Jamie). The idea behind this is to allow the the node to "wait" in OFFLINE until the SEI managers are where they should nominally be.

I reloaded the Guardian with the new code and committed it to the SVN.

**EDITED Wed July 8, 2015  15:36 PST**

We are sliding backwards in our efforts to quiet the pressures at EndX.  EE's latest test in the grounding has increased the noise on the pressure signals.  As a result, I've opened up the no-alarm region of the differential pressure to +-6 psi.  Remember, a momentary pressure glitch is pretty harmless and meaningless; but, an alarm that is sustained must be addressed asap.

~1500 hrs. local -> Adjusted boil-off pressure regulator 1 full turn clockwise

My script which reads the digital video ITM green image's X,Y,SUM and writes them as EPICS values to the ALS end station model (as YAW,PIT,SUM) has been extended to run on the X-arm as well as the Y-arm.

I have created an MEDM screen (H1CDS_CAMERA_COPY.adl, see attachment) which is accessible from the SITEMAP via the CDS pull down (last item on list).

The script runs within a screen environment on h1fescript0 as user controls

The last time the OverVoltage while running at SetPoint occurred was 14 July 2014.  Restarted normally per procedure in WIKI.  The system was down for about 40 minutes.  FRS 3289.

Following up this earlier report on pre-ER7 narrow lines in H1 DARM, attached is a corresponding
list of early ER7 lines and some spectra for 30.5 hours of data from May 31 through June 4 at 13:00 UTC, based
on FScans SFTs generated as of Thursday morning. 

Figure 1 shows the 0-2000 Hz spectrum for the early ER7 data with line labels according to the same scheme as before.

Figure 2 shows the mid-May and early ER7 spectra overlain without line label clutter.

Attachment 1 is the early ER7 line list (nearly identical in line frequencies but not strengths to that of mid-May)

Attachment 2 is a zipped tar file of 27 sub-band spectra for early ER7 with lines labeled.

Attachment 3 is a zipped tar file of 27 sub-band spectra comparing mid-May to early ER7 without labels.

I haven't yet digested all of the changes from mid-May to the early ER7A data (what I call ER7A here), but here are things that are immediately apparent::

 Bounce and roll modes are greatly reduced in this ER7 sample
 Quad violin modes are less excited in this ER7 sample 
 The previous comb with a fundamental of 36.9733 Hz (54 harmonics visible) has shifted slightly to a fundamental of 36.9725 Hz (50 harmonics visible). 
 The broad structures seen in the 280-440 Hz band are worse in early ER7 than in mid-May (due to PSL jitter, if I understood Robert correctly)  
 The nefarious OMC alignment dithers and their upconversion have reappeared in what the CW group considers to be an astrophysically interesting band (anything below 2 kHz) at frequencies of 1675.1, 1700.1, 1725.1 and 1750.1 Hz
 Whatever dithers there were previously at 81.0000 and 310.0000 Hz have disappeared.

Attached is a pre-ER7 list of narrow lines seen above 5 Hz in recent H1 DARM data, along with spectra containing labels for the lines.

The spectra used for line-hunting are from 18 hours of DC-readout conditions on May 17. Most of the lines were also seen
in the early-May mini-run data, but are more exposed in the more sensitive May 17 data (see figure 1)

Notable combs / lines:

 Exact integers: 16.0000 Hz, 64.0000 Hz (distinctly louder than other 16-Hz lines), 81.0000 Hz, 1150.0000 Hz, 1672.0000 Hz, 1704.0000 Hz, 1880.0000 Hz, 1896.0000 Hz
 Nearly exact-integer combs: 

 3.9994 Hz (offset by ~2 Hz from zero, first visible harmonic at 13.9977 Hz -- these seem to correlate with a near 4-Hz comb starting at 2 Hz in EX magnetometers (and to a lesser degree in EY magnetometers), where the contamination in DARM at 10 Hz and below is presumably too faint to be seen in the rapidly rising DARM noise. A strong comb is apparent in PEM FScans.
 99.9989 Hz (correlated with magnetometers in EX - see NoEMi and PEM FScans)

 Quad suspension violin modes with fundamentals near 500 Hz are not quite truly harmonic, but some of their upconversion is (see figure 2)
 Especially pervasive combs: 3.9994 Hz (34 harmonics), 16.0000 Hz (124 harmonics), 60.0 Hz (9 harmonics), 64.0000 Hz (31 harmonics), 36.9733 (54 harmonics), 59.9954 (6 harmonics), 99.9989 (13 harmonics)
 There are tentative identifications here of lines near 300 Hz and their harmonics as due to beam splitter violin modes, but their frequencies shifted by several mHz between the mini-run and the May 17 lock stretches, unlike the quad suspension violin modes which hardly moved at all (attributable to temperature?)
 Designated calibration line frequencies are shown on the spectra even when there is no apparent line (some not yet enabled?)

Notes:

 Because the binning in the spectra is 0.5 mHz (based on 30-minute FScan Hann-windowed SFTs), but the line widths in the plots are much larger, the spectra shown here look awful (but aren't). Dewhitening applies five poles at 1 Hz and five zeroes at 100 Hz.
 I didn't bother labeling the forest of bounce/roll-mode sidebands on the quad suspensions and their harmonics
 Although the 1150-Hz line seems well centered on the integer value, its energy is spread over several tenths of a Hz, unlike other integer-Hz lines
 Many line frequencies are give to four digits after the decimal point, but their statistical uncertainties are typically no better than a few tenths of a mHz, and based on changes between early and mid May, some lines have systematic drifts of O(mHz).
 With one exception, the quad violin mode fundamental frequencies were determined from the mini-run data, where they were more excited than on May 17. Those frequencies agree (independently) to within 2 mHz (in most cases, to better than 1 mHz) with the frequencies measured for individual test masses here. The one exception was that I had originally marked 504.1492 Hz as a mode in the mini-run, while the earlier study had found a mode instead at 501.254 Hz. Since the earlier measurements are guided by test-stand data, I am deferring to them and tagging 501.2544 Hz here, since I do see a line there in the mini-run data, albeit weaker than other modes.


Key to spectra labels:

b = Bounce modes
r = Roll modes
C = Calibration lines
L = Lock-in oscillator
M = Power Mains comb
N = Near to power mains comb
S = 64 Hz comb
s = 16 Hz comb
F = Near to 4 Hz (3.9994 Hz) comb
H = Near to 100 Hz (99.9989 Hz) comb
D =  59.3155 Hz comb
E = 36.9733 Hz comb
G = 75.23 Hz comb
Q = Quad violin modes
B = Beam splitter violin modes
x = Miscellaneous singlets

Figures:
1 - Superposition of 0-2000 Hz spectra for minirun (29.5 hours) and May 17 data (18 hours)
2 - Quad violin mode regions for first three harmonics (actual modes are non-harmonic, but some upconversion of fundamental is propagation harmonically)
3 - May 17 spectrum with labeled lines

Other attachments:
1 - Ascii list of narrow lines / combs found in 0-2000 Hz
2 - zipped tar file of 27 sub-band spectra (mostly 100-Hz wide)