Ran through a painless IA after the lockloss. Accepted an SDF diff for ETMy violin mode 10 filter to get to Observing. Screenshot attached.
Unknown cause, nothing apparent on FOMs.
TITLE: 01/28 Day Shift: 16:00-00: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.04 μm/s
Secondary useism: 0.64 μm/s
QUICK SUMMARY: Locked in Observing for ~26 hours. No issues to report.
Shift Summary: Ran the A2L DTT script a few times during the shift. The signal remains at or below the reference line. There have no ring up of either the 4735 Hz violin mode or the PI Modes. H1 locked in Observing for the entire shift.
Activity Log: Time - UTC (PT)
The IFO locked in Observing mode for the past 21 hours. Environmental conditions are good. The A2L is at or below the reference line. The PI modes have been well behaved, as has the 4735 Hz violin mode.
Ops Shift Transition: 01/28/2017, Owl Shift 08:00 – 16:00 (00:00 - 08:00) - UTC (PT)
TITLE: 01/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Locked my whole shift with lots of coincident time. A few GRBs coincident as well. No issues to report.
LOG:
14Hour lock cruising at 67Mpc. Two GRB alerts, but other than that it has been uneventful so far.
FAMIS#4712
ETMY P has past -10
BS sum has slowly increased, maybe due to Betsy's findings with the BS bouncing back up with tempurature.
TITLE: 01/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 3mph Gusts, 1mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.50 μm/s
QUICK SUMMARY: Going on 9+ hours, 4.7khz was damped earlier.
ALL TIMES IN UTC
15:02 King Soft on site to take water samples.
15:58 ran a2l while Livingston is still getting re-situated
18:18 just spotted the first wave of tour children headed this way!
18:46 first wave out
19:00 Out of Observing to tend to 4735
19:06 Back to Observing
19:14 second wave of tour kids making their way over.
19:30 second wave out. There was another group from the same school. I can't remember the time they were in here follwing.
19:42 Karen driving her car to the warehouse
21:18 Alfredo and Elizabeth driving to MY and then to H2 building
22:40 Kim B in with a small tour group from Cle Elum.
Scanned 60 days on these 117 signals. All are within a few percent of nominal level and trends tend to inversely follow the temperature.
Working on a better less-painful way to monitor these so it can be FAMIS'd but not there yet.
Meanwhile, I'll attach them here but just for history/reference. The HAM5 L4C P3 has a 25 unit step up in late May that remained until mid-December. Can't explain this but it steps right back to where it was so I suspect it is not real pressure.
I'd say not much reason to look at them until some future trend looks concerning.
at about 20:18 ETMY IOP/SUS CDS Overview was showing some timing and ADC errors (only to name the ones that I could quickly identify) that lasted for only a few seconds and then reverted back to 'Green" status. I will notify Dave Barker and I'm flagging Detchar as we are in Observing mode. This did not upset the Intent bit and there were no other alerts other than the visual one that I happened to notice.
This is another occurance of the ongoing end-station-sus adc and timing overruns we see on these faster computers. The glitch rate is low, and are cleared on the following minute, so most go un-noticed. I just did a recheck on the rates, and they are at around 10 per day for both ETMX and ETMY, occuring randomly in time.
If you want to trend these occurances, I have some scripts which do this. The data is in the STATE_WORD channel, which also includes higher order bits which tend to dominate the signal. So I have a script to just look at the TIMING and ADC bits.
in /ligo/home/david.barker/daq/ there are the scripts
get_iopsusey_stateword_mintrends.bsh, get_iopsusex_stateword_mintrends.bsh and mask_out_stateword_tim_adc_bit.py
Running the first two will get 3 days of minute trends for these channels and write them to a data file, running the python script (with the data file as an argument) lists the local times of each event.
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 47 seconds. 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 116 seconds. LLCV set back to 37.0% open.
19:03UTC
At Keita's request I've taken H1 out of Observing and set the mode to corrective maintenance. THe notch filter for the 4735 has been on but DARM still shows a spike in that frequency range. Keita will make some further adjustments to try and mitigate this. Update: while i'm making this log he has damped it. We will watch it for a short while to make sure it holds.
4.7k violin has been better than before since a bandstop was turned on in DARM chain (alog 33585) but it's not completely gone.
Typical behavior is that it dies down quickly after relocking, looks OK for two hours or so, then starts to ring up very slowly (first attachment).
We took H1 out of ofservation while L1 was down, changed the phase of violin damping setting (second attachment), confirmed that this damps down the violin (you can see this at the very end of the first attachment), accepted the change in SDF and went back to observation. We used 7 minutes.
I assume that the damping loop was tuned without the bandstop in DARM, and when the bandstop was inserted the damping needed retuning.
Grabbing the opportunity to dither-up while Livingston is still in the process of re-joining the search.
H1 back into Observe
Attached script checks any jumps for ITM M0 TEST outputs (e.g. when operators run initial alignment) and L2 witness monitors (or oplev) starting 09/Jan/2017 UTC for 14 days. It calculates DC "response" in urad/urad, as in angle measured by witness (or oplev) per angle offset of M0.
In the attached, just look at middle two panels. Second panel from the top shows the DC "response" for both ITMX and ITMY, and you can clearly see that ITMY startted to act erratically after Jan 15 2017 10:30:00 UTC or so, and it was fixed as soon as the vertical offset was applied to push the optic up (third panel from the top).
Seems like V=-65.7um is the threshold for ITMY to rub something. Interestingly, when ITMY rubs, YAW is constrained but PIT moves more in DC. Also, since the vertical offset was applied, ITMY has slowly drifted back up by about 30um, probably due to temperature change.
Unfortunately this doesn't show anything about CPX because the M0 offset only acts on ITMX chain, not CPX.
Borja fixed a bug which potentially makes the script skip a few last TEST OFFSET jumps. In this particular analysis the result was the same. Fixed script is attached.
Thanks Borja!
