Wednesday 12jun2019 - Sunday 16jun2019: No restarts
Monday 17jun2019
2019_06_17 19:00 h1alsey
2019_06_17 19:00 h1caley
2019_06_17 19:00 h1iopiscey
2019_06_17 19:00 h1iscey
2019_06_17 19:00 h1pemey
Kernel crash of h1iscey
Tuesday 18jun2019 - Monday 24jun2019: No retstarts
Tuesday 25jun2019:
2019_06_25 15:06 h1sysecatc1plc2sdf
2019_06_25 15:09 h1sysecatc1plc4sdf
2019_06_25 16:53 h1sysecatx1plc2sdf
2019_06_25 17:00 h1sysecatc1plc1sdf
2019_06_25 17:00 h1sysecatc1plc3sdf
2019_06_25 17:00 h1sysecatx1plc2sdf
2019_06_25 17:00 h1sysecaty1plc1sdf
2019_06_25 17:00 h1sysecaty1plc3sdf
2019_06_25 17:01 h1sysecatx1plc2sdf
Tuesday maintenance. Most Beckhoff systems were restarted, which in turn crashed some of their respective SDF systems.
TITLE: 06/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 7mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.04 μm/s
QUICK SUMMARY: 8 hour lock, EQ has subsided.
TITLE: 06/27 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
LOG:
There was even a second and third "uptick" in the ITMY Z-axis eq BLRMS AFTER Seismon reported the R3.5 waves had come and gone. X reached 1micron; Y reached 2; Z reached 3+ microns. Ride 'em Cowboy! We sure got them "8 seconds"!
12:13 UTC manually ended GRB Standown - INJ_TRANS to INJECT_SUCCESS
This one is a FERMI - Latency 7.06 - Trig Dur .512 . Extending Stand Down. EQ creeping in.
EQ effects starting to roll in hard. Going to maintain standown until we either lose lock or we survive, in which case I'll manually reset the INJ_TRANS node.
Swift alert - Trig duration is exactly 2.048
Initiated INJECT_KILL and Standing down for at least 15 minutes. EQ may get us. We'll see (uSeiesm is really low)
11:12 received 2 alerts. Sesmon says 6.6 and 6.4 magnitude.
09:31 Intention bit commissioning - squeezer must have re-locked itself while I was in the lbr.
09:34 Intention bit set back to Observing
Perhaps using the Automatic Operation mode may be useful in this capacity. I'm setting it now in the case the squeezer should becom unlocked again as it re-locks itself rather faithfully.
Edit to main post was to tag DetChar. Content was not changed.
TITLE: 06/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Calibration
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
First couple hours we were down for Calibration. Then we were down for another couple hours for a big wind storm + ALSx issue.
4th day of earthquake activity & it's getting a little painful. Tonight, the EARTHQUAKE state helped us ride through the EQ, but tonight we had Tidal Errors which drove multiple signals and prevented me on correcting matters by taking us back to the nominal WINDY state. Not sure what is different tonight, because this my first time seeing these signals rail in O3.
Crossing fingers for no EQs!!
LOG:
Screenshot of the MX PEM Wind channel...WOW
There were additional lightning strikes at 1:10:16, 1:11:34 - which produced the first roll of thunder Corey noted, and 1:14:01. In addition, the 1:18:04 lightning strike was followed by thunder at 1:18:24.
TITLE: 06/27 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY:
After the storm and ALSx issue, ran an alignment, went for locking & finally back to Observing.
NOTES:
Commissioners & Jason: Should We UNMONITOR these? (see 2nd attachment)
Went to Observing
There is usually a high-precision SDF difference immediately after the ISS RefSignal gets adjusted, then doesn't show up until the next necessary adjustment; I'm not sure why it's been popping up more often these last couple days. Despite that, the channel should definitely remain MONITORED, as changes to this channel change how much light is diffracted by the ISS AOM.
PSL ISS Diff: Keep ACCEPTING (per Jason's entry.)
ASC RF36 Offset Diffs: Keep ACCEPTING (per discussion with Keita tonight on 6/27).
After the storm was passing through, ALS x & y were obviously flashing all over the place. Unfortunately, within a few minutes the green spot for ALSx disappeared (and we had the error: "ReflPD A; Green input align").
1) Looking at ETMx, TMSx, & ITMx
Saw shifts for all of these guys, so I returned them to where they were during the lock, but no change for the spot on video.
2) ENDx Overview: No spot for Green WFS (& offcenter spots for Green QPDs)
3) PDH Locking screen:
Attached is a screenshot of the issue. Since the power is low I'm wondering if this is still an alignment issue & I just need to sweep optics to get something on the camera. But I don't really know where to start and where to go. This is something I can try next.
For the GREEN WFS, I'd prefer to not touch picomotors to get a spot on them, but I'm wondering if ETMX/ITMx/TMSx alignment sweeps could help this?
...........Oh Darn........
As I was going through the Troubleshooting wiki, there is mention of: If one has symptoms as above (i.e. no power for XARM Green ReflA), one should check the shutters. I just saw that the ISCTEX green shutter was CLOSED. I opened it and I atleast now see light (ugly light, but light). Why would this shutter close on me???
OK, now that I'm not blind, going to try and find the spot for Green X-arm!
5 Min Later:
Ugh. That did the trick. Unlocked ALSx & tweaked ETMx & (mostly) TMSx to get flashing from 0.1 up to 1.0. Now will move on...hopefully an alignment is not needed for the touching I did to the ITMx.
PRMI Flashes look like garbage (no flashing at all with PRM tweaks after BS tweaks from CHECK MICH FRINGES). Going for an alignment.
The ALSX shutter closing does not seem to be caused by the enabling of the picomotors, as seen with FRS 11354.
It was closed when the ALS_XARM node set H1:SYS-MOTION_X_SHUTTER_A_OPEN => 1 when it was starting to lock. I'm not sure why asking it to open actually closed it. Filed FRS 13154
2019-06-27_01:26:00.954991Z ALS_XARM executing state: LOCKING (-20)
2019-06-27_01:26:00.960283Z ALS_XARM [LOCKING.main] ezca: H1:SYS-MOTION_X_SHUTTER_A_OPEN => 1
2019-06-27_01:26:00.962242Z ALS_XARM [LOCKING.main] ezca: H1:ALS-C_LOCK_REQUESTX => End Locked
2019-06-27_01:26:00.963586Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_SWITCH => OFF
2019-06-27_01:26:00.964060Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_1_P_RSET => 2
2019-06-27_01:26:00.964461Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_2_P_RSET => 2
2019-06-27_01:26:00.964862Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_3_P_RSET => 2
2019-06-27_01:26:00.965275Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_1_Y_RSET => 2
2019-06-27_01:26:00.965644Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_2_Y_RSET => 2
2019-06-27_01:26:00.966066Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_3_Y_RSET => 2
(Changed tag to CDS, FRS)