Not a straight forward relock. I couldn't get green to lock without having to move the TMSs so I went to do an initial alignment, but then the fiber polarization was >20% on the Y laser. After adjusting that and moving through IA, MICH would not dark lock. The alignment looked really good but it still would only lock bright. The dark offsets didn't look great so I ran the scripts for that hoping it might help. Then INPUT_ALIGN refused to lock. This is exactly what happened after the harmonic oscillator was replaced recently so I was getting worried, but bumping up the LSC XARM gain eventually worked. I couldnt bring the gain back down or it would kick the IMC and lose lock. After this the rest of IA went well, and locking was no problem.
Bounce is damping slowly but we are back to observing.
After 45hours and 22min it had enough. There was a small earthquake passing through (4.8 from Guatemala) but it didnt seem big enough to knock us out.
TITLE: 03/31 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.25 μm/s
QUICK SUMMARY: 42hrs long so far. wind is calm, seismic is calm, and range looks good.
b>TITLE: 03/31 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
H1 locked the entire shift at fairly good range for over 40hrs. We rode out 1 .4um/s shake. H1 could use a good shot of a2l. ETMY is .9 in YAW and ETMX is not far behind. uSeism is trending up a bit. Handing off to TJ.
LOG:
15:45 Richard to X arm vault and Fil to MX
15:47 Karen into Optics lab
19:18 Tour group in control room
19:57 Second tour group in the control room
20:00 Bubba reported that baers were a couple hundred meters from the corner station on Y arm
20:17 Richard out to the vault
20:49 Jim turning of BRSY temporarily
20:52 Jim done
As Krishna noted in aLog 35160, this machine does not have a lot of extra juice to run this. I should have closed out before but was watching the diagnostics. Jim turned off the sensor correction so in case the session closing glitched things, it would not glith the ISI/IFO. It did not and SC has been turned back on.
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 571 seconds. TC B did not register fill. LLCV set back to 17.0% open. Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 3188 seconds. TC A did not register fill. LLCV set back to 33.0% open.
Raised CP3 to 18% open (was 17%) and CP4 to 36% open (was 33%).
FYI we are losing our striptool scans for these fills. Robo-log will still be generated. Also the text alert will be generated at noon (rather than 10:45) reminding us to check that fill completed.
Added more insulation to the BRSY auxcillary table supporting the T240 seismometer, see 35147, on Tuesday. We saw improvement in the low frequency noise after insulating the supporting legs of the table, see 34869, so more on the table was warranted.
Attached are spectra before and after.
It is a little hard to see but I think the story is good. The upper plot shows the Y axis and the X axis traces are below. The reference traces are from 26 March 1000utc when the wind was very low. The current traces are from 31 March 1120utc, two days after the insulation was added to the table. Generally, comparing suggests the insulation has improved things below 60mHz. Maybe little improvement on Y below 10mHz.
15:42UTC
TITLE: 03/31 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 6mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.23 μm/s
QUICK SUMMARY:
Shift Summary: Run A2L check script; Yaw is up around 0.8, Pitch is below reference. Will run the repair script at first opportunity. Ran A2L script while LLO was down. Environmental and seismic conditions remain favorable. Other than 2 large glitches, there were no issues or problems worth noting during this shift.
Quiet first half of the shift. Dropped out of Observing for 8 minutes to run the A2L script while LLO was down. No other problems to report.
TITLE: 03/31 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Locked for almost 26hours, wind has calmed a bit.
LOG:
23hrs and counting ay 65Mpc.
The new red lines are a very nice touch, kudos to whomever did that. Everything seems to be in its normal operating range and the Sums may even be up a slight bit for a few of them.
FAMIS:4721
Added 50 ml.
Closed FAMIS#6516
WP6548 Remove MY compressed air channels from cell phone alarm system
Bubba, Chandra, Dave:
Following the stand-down of the MY air compressor this afternoon, its channels were removed from the cell phone alarm system and the code was restarted.
Eric Quintero, Rana
Summary:
Studying coherences between the ground and the LSC drives, we find that we can reduce the longitudinal forces to the mirrors in the 0.1-0.3 Hz band by a factor of ~2-5 in most cases, for both sites.
Details:
The recent success of the length to angle (L2A) feedforward at LLO led us to wonder about the source of so much low frequency motion. The SEI loop feedback and feedforward has been heavily tuned over the years to reduce much of the motion. By looking at the coherence and transfer function between the ground seismometers and the LSC*OUT signals (in a similar manner to what we did with the length to angle in May 2016), we are able to make an upper limit estimate on how much this can be reduced by implementing a global FF (just as we did in early 2010 for the S6 run using HEPI/PEPi).
We took 1 hour of data from 1000 UTC on March 12. The RMS of the ground motion in the 0.1-0.3 Hz band was 0.5 um/s, which is high, but only moderately high for the winter time. The summer time motion is more like 0.1 um/s.
The attached plots show:
upper plot: LSC control signal & LSC control signal after ideal subtraction
lower plot: top 5 signals used in the subtraction (in practice, using ~3 signals is enough to do the biggest part of the subtraction)
This subtraction is done on a bin-by-bin basis in the frequency domain, and as such, its a best case estimate. In reality, implementing a causal filter which avoids injecting too much noise at 3-20 Hz will degrade the subtraction performance somewhat. We are now working on making a frequency dependent weighting so as to make realizable filters.
In the attached channel list, you can see that all ground seismometers and tiltmeters were used.
The BRS's were being used at the time this data was taken, this is the nominal seismic configuration. The window you looked at was a relatively low wind time (~5 m/s according to the summary pages), so end station floor tilt probably wasn't a big effect. And based on a study RobertS did (alog 27170), we think tilt is only coherent over short distances, so the BRS probably wouldn't directly show up here. What we use the BRS for is doing tilt subtraction from the end station STS, and use that super-sensor for FF on the end station ISIs. We store that tilt subtracted ground signal in the science frames (since June 2016) as H1:ISI-GND_SENSCOR_ETMX/Y_SUPER_X/Y_OUT_DQ.
Was logged on checking health from the earlier invasive work. Everything was working fine so I closed (pushed X) on the remote desktop shell. The BRS output went to never never land and the ISI tripped. This of course did nothing useful for the the IFO or Observation mode.
When I logged back onto the BRSY, it was still running but giving some errors and the output was still very rung up. I am not sure which was causing which though. Following the BRS2 Manual (T1600103), restarted the TwinCat code, killed the old occurance and restarted the C#, and finally the EPICS. Exited the session the same way and this time it survived. Yikes!
The amplitude is still a bit large with the camera image swinging into the reference image on the edge. When that stays off the edge during its cycle, the BRS will be useful again.
The BRSY is now damping itself down and is no longer swinging out of range. But it is still getting itself under control. It is coming down quickly but may be some time. Operators should feel free to contact me if they aren't sure if it can be returned to service.
It is strongly advised to not login to the BRS machines when they are being used. This is because the spike in CPU-use disrupts the autocollimator fitting routine. This causes ~seconds long delays in the tilt output which affects the tilt-subtraction and so on.
I've attached about 10 hours of BRS-Y driftmon data around the time of this crash. It looks like this crash was caused by trying to use BRS-Y in a bad range. Even if the data looks temporarily smooth, BRS-Y should not be used if driftmon is below -15k counts.
The close time association with closing of the remote desktop terminal was likely just a coincidence. It is still advised to not login to the machine remotely when BRS-Y is being used for feedforward, unless really necessary.