TITLE: 12/31 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 3mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.18 μm/s
QUICK SUMMARY: H1 lost lock at 14:43 UTC, ending this lock stretch at just over 29 hours. The online lockloss tool has not been updating since 12/26 at 20:14 UTC (5 days ago), so I don't know of a cause yet, but I plan to look into it. H1 is currently automatically relocking and up to RESONANCE.
TITLE: 12/31 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Currently Observing at 160 Mpc and have been Locked for over 20.5 hours. A few minutes ago we got another superevent candidate! Looking nice in H1! The evening has been quiet with nothing needing to be touched by me!
I did notice a notification on SQZ_OPO_LR that says "CMB EXC is on", and looking at the channel it checks, it looks like SQZ-OPO_SERVO_COMEXCEN went from 0 to 1 around 09:57 UTC on 12/30, which is a bit after we got locked last night and while we were having the SQZ issues. There are no excitations listed on the test point or CDS Overview screens, so I am wondering if this is some error? Tagging SQZ
LOG:
05:41 Superevent S241231bg
TITLE: 12/31 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 6mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.22 μm/s
QUICK SUMMARY: Forgot to put in my start of shift alog, so here it is as a midshift update. Currently Observing and have been locked for 17.5 hours. Quiet evening with nothing to report.
TITLE: 12/30 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 132Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
Locked entire shift (of a 15+hr lock) with (2) drops from Observing mostly for Squeezer (and also due to PI24). H1 was also mostly with No Squeezing since last night, and then Sheila and Daniel were able to get squeezing back around lunchtime (alog)---just in time for a superevent in the afternoon!
Environmentally we are looking good with lower microseism and low winds!
LOG:
We seem to be running into repeated problems where the green power is not sufficient to get to the nominal OPO green transmitted power.
Today the SHG output was particular low, so I adjusted the input pointing as well as lowered the temperature to 35.0C (from 35.5C). This gave us about 10% more green power, but still not enough! I then further increased the green power by adjusting the waveplate in front of the cube.
The rejected power (H1:SQZ-SHG_REJECTED_DC_POWERMON) is currently showing 1.8mW, down from around 4.7mW when I started. There is a little bit further to go, but we may have to realigning the green fiber coupler on the table. And if this doesn't work, we probably need to coonsider moving the OPO crystal.
Adding some plots related to Daniel's assesment above. The first time cursor (in the first attachment) is Oct 3 2024, the time of our most recent OPO crystal move 80451, you can see that the SHG launch power and OPO refl power have climbed back up as crystal losses have increased.
The second attachment shows that since Daniel's intervention described above (the time when SHG rejected power drops), the SHG power has been more stable, and the ISS control signal has been around 3V. I think that this means we can wait until Monday to move the crystal, so that we can do the temperature adjustments as we settle into our new crystal position during the workweek rather than over the weekend.
Link to Shift Summary
Mon Dec 30 10:16:30 2024 INFO: Fill completed in 16min 27secs
TCmins [-91C, -45C] OAT [+6C, 42F]. TC-A started positive, hence multiple decades in log plot.
1556utc H1 was taken out of observing due to PI24 ringing up (it was damped out within a minute), BUT....
Since we were out of Observing (and I had already gotten a workspace ready to work on the Squeezer), I wanted to try a "simple" Squeezer check (basically what Oli did with taking the Manager to DOWN and going back to FDS.
I thought I was close to FDS, because all of the sub-nodes went to NOMINAL states and then I believe the Manager would get to FDS, but then go to NO SQUEEZING.....Then I realized all their NOMINAL states were set for NO SQUEEZING!
So I worked on transitioning all 8-nodes Nominal states for SQUEEZING, to work on squeezing, but the issue I ran into was that the OPO_LR node had trouble getting to LOCKED_CLF_DUAL due to "USERMSG 0: No pump ISS means injecting bad squeezing. Going DOWN."
--->This sounds like yet another different SQZ issue. I did not have issues with the SQZ_FC as far as I could tell (also did not get to see the "leap second" issue RyanC noted last night).
At this point, I was stumped, but got a mattermost from Sheila saying she could help in a bit. So I switched all SQZ node Nominal states for NO Squeezing to get more Observing in the mean time.
SIDE NOTE: The buisiness for transitioning SQZ Nominal States is not quick or trivial (atleast for my slow self). While transitioning nodes for Observing WITH Squeezing, I ran into a LOADING error for the OPO_LR node. Eventually found that it was a typo in the wiki (for editing all the nodes I copied the state from the wiki into the node python files. I discovered the wiki had a typo [or the state had a slightly different name int he past]. For OPO_LR, the wiki said to make the Nominal -> "LOCK_CLF_DUAL". Eventually figured out from the log, that this name was wrong it is "LOCKED_CLS_DUAL". At any rate, I updated wiki. And now have more Nominal node experience...I think this is only my 2nd or 3rd time going through the buisiness of "editing nominal states" for observing.
Now realizing, I was looking at the "Old Instructions" wiki (hence the typo?).
NOTE: Is it useful having the old instructions in here? When you're under the time gun/clock, I tend to rush, and this time I gravitated to the old instructions (the first time I did this, I do remember looking at the NEW instructions and did an svn-commit of the edited python files.).
With that said, I did get there to Observing with NO Squeezing, AND I did not do anything with the SVN since I'm basically returning to Observing with NO Squeezing again (as RyanC did last night).
Additional Note: Also saw that right on the top of the wiki (under Quick Rundown), that RyanS made a script for the "WITH/WITHOUT Squeezing In Observing" transition, but I didn't get a chance to try it out before going back into Observing.
Good suggestion Corey, I've removed the old instructions from the wiki to avoid future confusion. They are still available in the wiki's history via the "info" button.
TITLE: 12/30 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 132Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 6mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.20 μm/s
QUICK SUMMARY:
H1's been locked for 6.25hrs (with no squeezing); we have triple coincidence now, but debating whether to drop out of Observing for Squeezer investigations---It feels like we've had a variety of squeezer issues for the last 36 hours through multiple differnt locks. Microseism continues it's downward trend with it down to touching the 50% percentile line. Winds have been at or under 10mph for most of the last 24hrs.
(Although Oli spotted the male elk while they left the site, he was not spotted this morning.)
SQZer not locked, SQZ_FC gave a notification about Leap data being expired in its log. I tried bringing FC1 and FC2 back to where they were the last time we locked the SQZer to to avail, following the wiki I tried to walk through the locking process but the ISS keeps losing lock and couldn't stay locked, I keep seeing the 10 locklosses notification. I wasn't able to get the ISS to lock, I ended up taking us to obs without SQZing, I had to accept a few SDFS.
10:31 UTC Observing
TITLE: 12/30 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Currently Observing at 155Mpc and have been Locked for 2.5 hours. One lockloss during my shift and relocking was entirely hands-off, but we had trouble getting into Observing because the squeezer wouldn't lock.
The FC would go to FC_ASC_ON, then less than a second later the OPO would drop from LOCKED_CLF_DUAL to LOCKED_CLF_DUAL_NO_ISS and then ENGAGE_PUMP_ISS, and either at the same time or immediately following this, the LO guardian would unlock from the OMC, and the filter cavity would go to DOWN a few seconds later. This happened over and over until I took SQZ_MANAGER to DOWN and then back to FDS, at which point we were able to get squeezing and go into Observing. I originally thought this issue was related to the problem Corey and Daniel worked on earlier, but the values for SQZ-SHG_FIBR_REJECTED_DC_POWERMON were still nice and low to where Daniel had adjusted them to, and I don't think there was an issue with the OPO temperature since we were able to lock with the ISS with the setpoint at 80uW?? Tagging SQZ
LOG:
00:30 Relocking and at MOVE_SPOTS
00:46 NOMINAL_LOW_NOISE
00:48 Observing
02:19 Lockloss
03:34 NOMINAL_LOW_NOISE
- SQZ was having issues locking
- Got it figured out by going to NO_SQUEEZING and then back to FDS
03:49 Observing
Lockloss @ 12/30 02:19 UTC
03:49 Observing
TITLE: 12/29 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
H1 was locked over 17hrs until it had a LockLoss (whose cause is unclear--LockLoss tool is down). Before the lockloss there was a drop from Observing due to the Squeezer.
Microseism continues it's downward trend of the last 24hrs (and winds were not an issue today).
LOG:
TITLE: 12/30 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.27 μm/s
QUICK SUMMARY:
Currently relocking and at ENGAGE_SOFT_LOOPS. Secondary microseism has gone way down over the last half a day and wind is low.
(CoreyG, DanielS)
At 1925utc, H1 dropped out of Observing due to the Squeezer. After a couple minutes, could see that the MANAGER & LO_LR nodes were cycling and not getting anywhere.
Wiki First
At this point, I opened the Troubleshooting SQZ wiki's "Can't Get To FREQ_DEP_SQZ" section. From this, I took MANAGER to NO SQUEEZING and then opened up all the SQZ Nodes.
At this point I notice the OPO_LR node which had been green is actually also cycling (but not as fast as the MANAGER & LO_LR. And OPO_LR was also showing a User Message, BUT it displayed too quick that I had to take a screenshot really quick to catch it. This node would hang out at the NOMINAL state (LOCKED CLF DUAL), drop out from this, display a message(s) for 1sec and then return to nominal state....all within a minute or so. There were actually 2 messages, they were to the best I could see (also attached):
At this point, I started diving into medms for anything related to the shy messages above. "pump fiber rej power" gave me the most info for where to look, but at this point, I also wanted to do an alog search.
Then Alog Search
I searched OPO_LR, where I focused on an alog from (1) RyanS which referenced a Tony alog and (2) RyanC. These three alogs narrowed my focus and had me looking at:
The Rejected power has been trending for the last month+ up to a max value around 3.0 (where it starts from about 0.03). I wasn't totally sure I had the scenario right, so at this point I reached out to Daniel (main contact for SQZ on the Call List).
Phoning Daniel For Help
After giving a summary the best I could, Daniel logged in and started looking. Some of the main points he mentioned:
With all that said,m he was able to get the LO_LR node to its nominal state, but he mentioned we could also fix the Fiber Rejected Power (atleast until the new year or about a week!). So he started to work on this. And this ended up being what was done by RyanS in his alog. See attached for image showing which waveplate/picomotor he adjusted on SQZT0 along with the HAM7 Fiber Rejected Power signal he watched & reduced. See attached for zoom in of the rejected power signal adjusment he made.
Daniel mentioned there will probably be a nead to make adjustments out on the table, but this change can get us through the holiday break.
Return to OBSERVING at 2056utc
nds1:
The /var file system on h1daqnds1 (the default NDS) became 100% full yesterday. This is discovered by the daily central syslogs for this machine increasing from roughly 3GB per day to 19GB yesterday.
For a short term fix, I first removed the syslog.3.gz and syslog.4.gz files to make enough room so I could compress syslog.1 and daemon.1 This reduced the disk down to 50% usage.
alarms:
To "green up" the alarms system which had been permanently RED since Thursday due to HAM6's gauge going offline I temporarily removed the PT110 channnels from the alarms system and restarted at 10:33 Sun 29dec2024.
As a place holder to remind me to return these channels back to alarms when the gauge is fixed, FRS32957 will remain open.
Channels removed:
H0:VAC-LX_Y0_PT110_MOD1_PRESS_TORR
H0:VAC-LX_Y0_PT110_MOD1_PRESS_TORR_ERROR
Sun Dec 29 10:16:20 2024 INFO: Fill completed in 16min 16secs
TITLE: 12/29 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 13mph Gusts, 7mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.42 μm/s
QUICK SUMMARY:
H1 has been locked for 10+hrs! Secondary microseism is mostly under the 95th percentile line, and winds are only around 10mph (with light rain on the drive in).
And for the first time since Christmas morning, SEISMIC has dropped from USEISM down to CALM!
H1 back to observing at 16:40 UTC. Fully automatic relock with an initial alignment.