FAMIS 9319
Late entry here, apparently I never posted this the other week.
BRS drift looks good, but ETMX Cbit doesn't look very stable.
FAMIS 10543
No water added to either chiller, both were full. Filters looked clean and clear.
TITLE: 01/09 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 120Mpc
OUTGOING OPERATOR: Camilla
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 3mph Gusts, 2mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.27 μm/s
QUICK SUMMARY: Locked for almost 5.5 hours. Calm environment. Tumbleweed clearing is ongoing on the Xarm.
TITLE: 01/09 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 119Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Locked 5h10. Big 6.3M EQ caused a lockloss but no WD trips and otherwise quiet night.
LOG:
When I arrived, Jim and I noticed that the intention bit and observatory mode was not set to observing, but were in a fine state for observing from probaly 05:14 UTC which is when the TMS offsets were reverted so SDF's cleared. Tagging DetChar.
after about 2 hours of trying to damp mode 3 with the filters that H1 has been using, with little to no effect, I talked to Jeff about changing the filters, since mode3 damping had always been mariginal.
Changes to IX mode3:
Attachment 1: IX mode3 from abandoning the old filters to damping at relocking H1
Changes to IX mode2:
Attachment 2: IX mode 2 from unsuccessful redamping to (mostly) successful damping at relock
Other modes, other optics, damped by Jim:
Attachment 3: IY mode 15
Attachment 4: IY modes 1 and 6
- Jeff, Cheryl, Jim
Lockloss details:
I don't know if this is by design, but I found that the violin damping continues for almost 2 seconds:
The mode2 switch must get switched in the DOWN script, because the mode2 output was re-enabled, and what doesn't make sense is that even with the mode2 gain at "0," mode2 output damps for about 5.5 seconds, and the output signal isn't small, it's +/-20000 counts!
Many plots that go with the timeline.
The cause was human error, the response of all the modes continuing to damp may be intentional, the response of mode2 may be understood, but was unexpected when I looked at the timeline of the signals.
Lockloss from a 6.3M EQ in Russia (not far from Alaska) knocked us out of lock fast from EQ mode. 0.03-0.1Hz band nearly touching 20μm/s. Waiting for the ground to calm a little before attempting relocking.
So it looks like Increase_Flashes has been restoring the TMS TEST bank offsets properly, but ISC_LOCK changes them in ENGAGE_SOFT_LOOPS and MOVE_SPOTS and does not restore the test bank offsets.
Attachment 1 - Showing Incr. Flashes restoring and turning off the TMS offsets in the last lock acquisition.
Attachment 2 - ISC_LOCK moving the TMS and not restoring the offsets.
I'll look next to see why this has changed.
TITLE: 01/09 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Camilla
SHIFT SUMMARY: Violins were a problem early on, quiet after locking
LOG:
When I came, TJ had the IFO sitting while he and Cheryl worked on violins.
5:00 We got to NLN and Jeff and Cheryl had to do the TMS offload again
From 5:00 on we were locked and the IFO was in an Observation ready state, but I thought I had heard Jeff set the Observation bit, somehow I never caught that never actually happened until Camilla came in. Don't know how that happened. So there are about 3 hours here where the IFO was in a good state, just nobody had pushed the button.
Flagging this for DetChar.
TITLE: 01/09 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 9mph Gusts, 7mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.27 μm/s
QUICK SUMMARY: Locked 3 hours. Wind is finally down, now below 10mph!
I have looked a little bit more at the data from moving the ETM reaction masses on Monday (alog 54314), and I think that the attached plots show that the candidate positions that I was using are better than the nominal positions.
On Monday, I did a chop / on-off test, going back and forth between the two positions, with 3 times in each position. Today I separated the data by which position it was in, and concatenated those times. In the attached plots I have a total of 26.6 minutes of data in the old nominal positions (0s on all 4 of the ETM R0 opticalign sliders) and 25.0 minutes of data in the candidate position (-200 on all 4 of the ETM R0 sliders).
In the first attachment, the scatter plots compare velocities of the ETMs versus the DARM BLRMS. The DARM BLRMS are a pretty good proxy for when glitches happen. The top row of all the plots is BLRMS #2, from 20 Hz - 34 Hz. The bottom row is BLRMS #3, from 38 Hz - 60 Hz. Each of the different figure windows is a different optic velocity (EX length, EX pitch, EX yaw, EY length, EY pitch, EY yaw). The blue markers are from times at the old nominal positions and the redish-orange markers are from times with the -200 urad slider values. The first take-away I have is that for most velocities, the new position has lower peak BLRMS than the nominal positions. The other take-away is that they seem pretty random for the most part, except for EX length which seems to have some interesting structure. The y-axis data is the same for all of these plots, so the fact that there seems to be some structure to the EX L plot suggests that that optic could be the most egregious in terms of generating the scatter.
Tomorrow I'll make some plots with also the wind and microseism incorporated in some way (I'm not yet sure how to best visualize those) to try to tease out whether this correlation is related to microseism levels at those times, or if it is more strongly related to optic velocity.
Something to note, I didn't think about the sign of the R0 offsets carefully enough on Monday, and I think that perhaps I did the pitch offsets in a good direction, but the yaw offsets in a not good direction. If we're having bad glitches again I may ask to try again soon. The R0 opticalign offsets should be of opposite sign from the M0 slider values to make the relative angle between the chains maximally large. For both end stations, the pitch sliders for the main chain are positive, and the yaw sliders are negative. Since I put negative slider values in for the R0s, I was increasing the pitch angle between the chains, but decreasing the relative yaw angle. So, overall I still was changing the angle between the optics and their reaction masses, but I could have gotten even more angular separation.
TITLE: 01/09 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Jim
SHIFT SUMMARY: In the process of trying to damp ITMX violin modes 2,3,4 that were rung up from some filter loading, before we can move further in the relocking process.
LOG:
Human caused. We dropped out of observing from a channel connection error when some background violin mode channels were changed. Surprised by this, while we were fixing the issue I allowed some other filters to be loaded, which killed the lock.
Cheryl made changes to the ITMX damping filters for a good reason, however we forgot to reduce the gain to zero before applying those filters. This resulted in an unfortunate lockloss due to a sharp (before we could react) increase in the ITMX violin mode amplitude.
ETMX ST2 has a bump around 13 HZ that's larger than the previous Weekly log post.
Some interesting behavior in the diode chiller flow (as reported by the Diode Chiller, shown on WeeklyChiller_01082020.png). In the last 10 days there have been 2 small drops in flow of ~0.1 lpm that lasts for ~13 hours before returning to normal. The drop is small enough that this isn't terribly concerning, but given our recent history with the diode chiller we'll keep an eye on this nonetheless. Everything else looks normal.
Plot attached shows that the violin peak at 998.828Hz, ITMY Mode 18, was damped overnight with a gain of +300. The nearby peak at 998.961Hz, ITMY Mode 17, was not rung up.
Attachments:
Wind has died back down to < 25mph. Locked and observing 14h30.
When I restarted the alarm handers at 08:12UTC the vacuum alarm didn't go off as normal so I wonder if the alarm handlers aren't connecting correctly (tagging CDS).
Gerardo fixed this yesterday. This is the new normal.
Yes, this is the new norm. The modifications done to the alarm system is as follows, removed all channels related to H2 and the instrument air for the outer buildings (they were in constant alarm), removed some repeated channels and added some ommited channels. Also updated the guidance that aplies to alarms related to vacuum channels.
Attached plot shows violin mode damping settings that are different than what guardian sets. All are damping well.
The guardian snapshot is not correct, not sure why, but it does not include IY mode18 who's gain in guardian is 0, and was set to 300 last night.
posting mostly because I've always wanted this. click on traces in the legend to remove. Good for removing all those LF traces to focus on the ones we care about. If it's too big you can resize your browser.
very cool!
Super sweet! I'm guessing this is LHO. From when is the O3 trace? Also -- d'you have one for LLO as well? Can you point us to the source code so we can reproduce this in the future once the budget changes?
Hey Jeff, you can make interactive python legends using a nds2utils function called make_interactive_svg(). It's located here you can pip install nds2utils.
