edmond.merilh@LIGO.ORG - posted 09:07, Sunday 12 January 2020 - last comment - 09:10, Sunday 12 January 2020(54447)
H1 back to Observing 17:07UTC
After chatting with Ed this morning, just wanted to make a note about CHECK MICH FRINGES.
It's looked different for me my last two shifts. Instead of locking on a dark fringe and then tweaking the BS to minimize AS_AIR & make video spot symmetric, it is yielding a bright spot now. Is the new procedure to make the highs higher and lows lower for AS AIR?
TITLE: 01/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 26mph Gusts, 21mph 5min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.50 μm/s
QUICK SUMMARY:
TITLE: 01/12 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 118Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
Fairly decent night even with moderate winds.
Had (2) locklosses which appeared random (i.e. I'm saying not wind/microseism related....since we had higher winds and microseism during the rest of locks). Now both locklosses in a row have had an oscillating FSS which would not lock. So not sure this is a possible reason for locklosses, or a sign of something else causing FSS to oscillate.
Looks like we just missed a superevent candidate after this most recent lockloss.
LOG:
H1 had a 4hr lock and this was with sustained winds near 20mph, and then there was a random lockloss.
Once again, FSS would not lock and the PSL_FSS said it was due to "FSS Oscillating". (most recent alog of this I see is from June 2018)
I did the same thing I did earlier in the shift for this: toggled FSS autolocker, took ISC_LOCK to INIT/DOWN, took IMC_LOCK to INIT/LOCKING (& DOWN). Then I took PSL_FSS to INIT/DOWN (then FSS locked). This time it took 8min vs 20min after the last lock.
I marked this down time as CORRECTIVE MAINTENANCE since this isn't normal. (although Ed has just walked in, he mentioned addressing this before and Jason mentioned to him that there was a special way to "toggle" the FSS autolocker....so don't turn it off and wait a while. Just turn off and then on....but I'm pretty sure I tried that and other variants.)
Anyway, FSS during my shift wasn't happy. Am curious to know if this is a trend.
Not only do you have to toggle the autolocker off/on in rapid succession (click OFF then immediately click ON), when you perform the toggle is important as well. If it's having trouble relocking it will get to a point where it wants to grab, but for some reason can't (you'll see the 00 flashes on the PSL quad display, upper-left quadrant). You want to toggle the autolocker during this state, when it should be grabbing a 00 mode but isn't. If the autolocker is running through its temp search (seen by a triangular shape to the NPRO crystal temp graph on the FSS MEDM) then toggling the autolocker will do absolutely nothing.
There have been a few instances of the FSS RefCav having issues relocking in the last few days (a couple on Friday, and the two reported by Corey). This seems to be a growing trend, but oddly enough we very rarely have problems getting the RefCav to lock when we perform work on it. I suspect there may be issues with the archaic FSS RefCav autolocker code; it was written in one of the variants of C many years ago and hasn't been touched since. I'll formalize this in a Wiki page, but here are some pointers if the autolocker continues to have problems (in no particular order):
I also had the FFS not locking on Tuesday (alog 54329), the wind was very high at this time though I don't know if that could have any effect.
How would you suggest pausing the PSL_FFS code? Will taking it to INIT do this as it is Managed by ISC_LOCK.
Thanks for the notes about this, Jason---this helps alot! It was the middle of the night, and I totally did not want to phone you for something like this. I did think I tried different types of toggling of the Autolocker, but I definitely did not correlate toggling with looking at the RefCav flashing modes.
Camilla: (Correct me if I'm wrong Jason) One can PAUSE the PSL_FSS node (and any node) by going to the node's Main Screen & for the "OP" pull-down, click that and select PAUSE (other choices are STOP & EXEC). I imagine we can do that even if PSL_FSS is MANAGED?
H1's been locked 30+min & we are now in SEI_CONF = WINDY mode. Winds appear stable & microseism is below the 90th percentile.
10:07 H1 had a fairly random lockloss (the winds were not anything out of the ordinary, and microseism has been coming down below 90th percentile).
Only notable was that the FSS would not relock. Tried toggling FSS Autolocker a few times. Also tried INITs to ISC LOCK, IMC LOCK & LSR PWR to no avail. Randamly, FSS relocked on its own after 20min.
Now slowly working on locking (the Green Arms were misaligned, but ISC LOCK brought them back).
Since Microseism is lower, I transitioned us back to WINDY after the lockloss.
11:33 OBSERVING.
TITLE: 01/12 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
SEI_CONF state: USEISM_WINDY
Wind: 17mph Gusts, 15mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.54 μm/s
Winds look to be under 20mph. *knock on wood* Microseism is half of what it was when I ended my shift this morning (woo woo!), and we are at or might be a shade below the 90th percentile. **double knock on wood**
Noticed a 4.7 EQ which was up in the Arctic (82° North!).
QUICK SUMMARY:
H1's been locked 6.25+hrs. The range looks much less rattier than the lock earlier in the day, and the range looks to be close to a normal 119Mpc. There is glitches on H1, but not as bad as yesterday (microseismic shelving is at 20-34Hz vs up to ~50Hz for last lock.).
TITLE: 01/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Handed off in Initial Alignment, H1 made it to NLN in about 1.5 hours, despite wind and useism, and has remained locked
LOG:
Violin mode damping changes: IX mode 2 , EY modes 1 nd 6, plot attached
Winds have come down from 40mph, there was about 30 minutes of all wind indicators being below 20mph, currently all but EY under 20mph, and wind is increasing.
Range has been over 120Mpc once,and is currently 119Mpc.
Useism has signs of coming down, lower points on the trned are below 0.5 um/s.
Plot of about the last 6 huors, some H1 QPD signals, and Wind.
TITLE: 01/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
SEI_CONF state: USEISM_WINDY
Wind: 27mph Gusts, 21mph 5min avg
Primary useism: 0.08 μm/s
Secondary useism: 0.85 μm/s
QUICK SUMMARY: locking H1
TITLE: 01/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
Bumpy shift.
LOG:
Reason Unknown
TITLE: 01/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 89Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_CONF state: USEISM_WINDY
Wind: 15mph Gusts, 13mph 5min avg
Primary useism: 0.07 μm/s
Secondary useism: 1.16 μm/s
QUICK SUMMARY:
TITLE: 01/11 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
The tumbleweeds were a rollin' (& setting off the motion sensor lights all night!). In other words: LOTS OF WIND!! (Attached are photos of the X-arm...which is partially buried for a couple of sections!)
No real method to the madness, but for SEI_CONF I tried different states for on the order of an hour and then tried something else since I've been desperate.
Finally made it to OBSERVING during the last hour of the shift, but the microseism is high and the winds are sort of low...but have had some gusts.
H1 is fairly glitchy with DMT Omega showing lots of "shelf noise" from 20-50Hz. I'm wondering if changing SEI_CONF or SEI_DIFF could remove some of this noise...but I'm hesitant to touch anything since we are teetering on a very noisy Earth. I went up to NLN & am currently at these settings:
OVERALL, What made it possible to get to OBSERVING during the last hour was the winds finally starting to die down. Let's hope they stay manageable!!
LOG:
Additional Notes:
Just trying to think of a knob we can turn to make H1 less-glitchy and prevent it from losing lock (because locking is definitely tougher if we have any winds over 25mph AND high microseism. So we want to stay in the more stable NLN by any means possible.
H1's trying to get back to NLN.
Attached is a plot of winds for the last ~8hrs. (I'm blowing back at the computer screen as I see the Corner Station go over 30mph!!!)
As we are at LOWNOISE COILS, we get a gust of 39mph in the corner and the Control Room creaks!!
15:15 (7:15am) Finally back to OBSERVING after being down 8+hrs!
Wineds are finally under 20mph, and we just made it through another large Puerto Rico earthquake. Alignment looks decent (although CHECK MICH FRINGES didn't work for me....but that was OK since PRMI ended up locking anyway). Now trying to hurriedly step through ISC_LOCK with winds not howling!
But all is not rosy. Microseism continues to climb. And we are squarely at 1.0 um/s!
There was a very marginal SDF Diff in the FSS common gain which I accepted (see below). This is obviously some artifact of Corey's previous "tribulations".