TITLE: 08/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Frustrating work getting back, but hopefully it will stay this time. See alog38279 for my relocking struggles.
LOG:
Summary: I forgot that AS90 is now unreliable because of some test that is going on that I can't seem to find any record of, random connection errors, odd camera image for MICH dark locked, and SRY not locking. Brought back to NLN for 14min before it lost lock again.
Long version:
After the lock loss I tried to relock and had some issues with DRMI. I played around with the alignment a bit and eventually got to lock on what I thought was a PRMI because the POP18 (pink signal on the striptool) and POP90 (light green) were both up, but there was no AS90 (purple). Confused, I tried to figure out where in the SRC cavity the misalignment was, and couldn't find anything but noticed that the spot looked odd for a PRMI. I decided to do an initial alignment and couldn't get Xarm to lock in IR in INPUT_ALIGN. The usual gain trick didn't work at first, but on the third try or so, it finally did. PRC was no issue, but then I couldn't get MICH to lock dark. I would let everything swing and look at the alignment via the camera, and I made it look impeccably symmetric. But when I went to lock it, there was still more light than usual and nothing I did really seemed to change it. I thought that the camera exposure may have been changed or something but looking back at the Guardian it hasn't been changed in a while, and even when I played with the exposure by hand I couldn't get it to look any more familiar. I eventually moved on and then couldn't get SRY to lock at all. I adjusted the spot on the AS_C PD numerous times, I tried adjusting via the camera as well, and nothing seemed to work.
Running out of options I tried restoring all of the optics and then going back to try yet another initial alignment. It was the exact same situation as last time. I eventually got SRY locked, but not because I did anything different. It just felt like working. Okay, then I get back to trying to lock DRMI and again, it seems to lock on a funny PRMI. After banging my head against a wall for a bit I eventually vaugely remember a background conversation while I was doing some other work about someone mentioning that there was going to be some tests with AS90 and the purple trace would not behave normally. So I tried to move on and then Guardian started complaining about connection errors. The channel seemed fine and re-requesting the state solvled the issue. This hapeed a few more times though, no idea what was going on.
After all that there was very little issues and it came right up. BUT as I was writing this it just lock lost. Lovely.
No obvious cause.
TITLE: 08/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
Wind: 15mph Gusts, 13mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY: All seems good and calm, 38hr lock.
TITLE: 08/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Nice quiet shift with H1 locked for 38+hrs. Worth note are random visitors to the site who are in the area due to the #Eclipse2017 mania. :)
LOG:
Noticed Diag_Main message for "Seismon system not updating" at around 16:47. (Opening up the DIAG_MAIN node's Log, this message came out at 15:36utc (or 36min after Jim's shift ended).
Jim mentioned that we do not have an action to restart Seismon (he needs to get with Dave B. for troubleshooting).
Now on the Seismon medm, the Keep Alive is still flashing, and I don't see any notes on it about NO Updating.
TITLE: 08/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 16mph Gusts, 9mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.08 μm/s
Winds picking up a little in last hour, but otherwise quiet morning.
QUICK SUMMARY:
H1 locked for 30.5hrs. w/ range a little low at 50Mpc (low for the post-MT-EQ-epoch).
Made quick OSB walkabout w/ nothing to report.
TITLE: 08/19 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 49Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Quiet Shift
LOG:
Locked all shift. Not much too report.
TITLE: 08/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 49Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Wind is still at a consistent 20mph, but on a 22hr lock.
Looks like we just rode through 6.4M Fiji ~500km deep.
19hr lock.
TITLE: 08/18 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
Wind: 16mph Gusts, 10mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY: 14hr lock at a lower 50Mpc.
TITLE: 08/18 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 49Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
LOG:
TITLE: 08/18 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 5mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: after EQ, drop in range from 24 hours ago
TITLE: 08/18 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
LOG:
Recovery from earthquake was rough. Jeff was waiting for violins to settle when I arrived, we got to Low Noise ESD ETMY and ISC_DRMI guardian said somethin about the ETMY ESD not being on. Didn't know what to do, so I pushed the "On" button on the ETMY SUS overview, which broke the lock. After that, I couldn't get past Locking ALS. Not knowing what else to do, I did an initial alignment. When I got to Mich alignment, I couldn't get locked on the dark fringe, at all. I eventually just put the alignment guardian in down and aligned the AS spot by eye, finished SRC and went back to locking. A few attempts at locking PRMI/DRMI and I was able to move on. Violins were a bit high after, but they damped down on their own. Ran A2L, which seemed to take an unusual amount of time to complete.
Back to observing at 9:20.
At mid shift all is well. We are at triple coincident observing. With the wind dropping a little, environmental conditions are good.
J. Kissel I've checked the last suspensions for any sign of rubbing. Preliminary results look like "Nope." The data has been committed to SUS repo here: /ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM1/SAGM1/Data/ 2017-08-08_1629_H1SUSIM1_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1629_H1SUSIM1_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1629_H1SUSIM1_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM2/SAGM1/Data/ 2017-08-08_1714_H1SUSIM2_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1714_H1SUSIM2_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1714_H1SUSIM2_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM3/SAGM1/Data/ 2017-08-08_1719_H1SUSIM3_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1719_H1SUSIM3_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1719_H1SUSIM3_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM4/SAGM1/Data/ 2017-08-08_1741_H1SUSIM4_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1741_H1SUSIM4_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1741_H1SUSIM4_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM1/SAGM1/Data/ 2017-08-08_1544_H1SUSOM1_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1544_H1SUSOM1_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1544_H1SUSOM1_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM2/SAGM1/Data/ 2017-08-08_1546_H1SUSOM2_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1546_H1SUSOM2_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1546_H1SUSOM2_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM3/SAGM1/Data/ 2017-08-08_1625_H1SUSOM3_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1625_H1SUSOM3_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1625_H1SUSOM3_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/RM1/SAGM1/Data/ 2017-08-08_1516_H1SUSRM1_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1516_H1SUSRM1_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1516_H1SUSRM1_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/RM2/SAGM1/Data/ 2017-08-08_1520_H1SUSRM2_M1_WhiteNoise_L_0p01to50Hz.xml 2017-08-08_1520_H1SUSRM2_M1_WhiteNoise_P_0p01to50Hz.xml 2017-08-08_1520_H1SUSRM2_M1_WhiteNoise_Y_0p01to50Hz.xml Will post results in due time, but my measurement processing / analysis / aLOGging queue is severely backed up.
J. Kissel Process the IM1, IM2, and IM3 data from above. Unfortunately, it looks like I didn't actually save an IM4 Yaw transfer function, so I don't have plots for that suspension. I can confirm that IM1, IM2, and IM3 do not look abnormal from their past measurements other than a scale factor gain. Recall that the IMs had their coil driver range reduced in Nov 2013 (see LHO aLOG 8758), but otherwise I can't explain the electronics gain drift, other than to suspect OSEM LED current decay, as has been seen to a much smaller degree in other larger suspension types. Will try to get the last DOF of IM4 soon.
All HTTSs are clear of rubbing. Attached are - the individual measurements to show OSEM basis transfer function results, - each suspensions transfer functions as a function of time - all suspensions (plus an L1 RM) latest TFs just to show how they're all nicely the same (now) Strangely, and positively, though RM2 has always shown an extra resonance in YAW (the last measurement was in 2014 after the HAM1 vent work described in LHO aLOG 9211), that extra resonance has now disappeared, and looks like every other HTTS. Weird, but at least a good weird!
J. Kissel Still playing catch up -- I was finally able to retake IM4 Y. Processed data is attached. Still confused about scale factors, but the SUS is definitely not rubbing, and its frequency dependence looks exactly as it did 3 years ago.
Not sure when it went away, but No longer have the "Seismon system not updating" message, and it looks like we've had a few earthquakes post since having the message earlier this morning. ("Keep Alive" continues to flash.)
There are a several ways Seismon can die, the keep alive only tells you about one of them. The diag_main test looks at the system time (what gps time the front thinks it is ( I think)). This clock stops under different conditions than the keep alive, but is also subject to temporary freezes, not sure of the cause. The diag main test looks for the seismon system time to be a minute or more out of sync with another front end ( I think LSC). There is also a light on the "compact" seismon screen that comes on if the difference is greater than 5 seconds, this should have been on when Corey looked, if he was looking at the compact screen.