H1 locked at NLN for 01:45
16:32 Switched ISI config to the new v2 state fter some trial and error. It seems that the WINDY_NO_BRSX is giving me the most stability.
16:47 GRB alert. not even close to being locked.
18:18 CP4 alarm - red then yellow
18:37 NLN! manually closed all Beam Diverters except for POP
18:38 Robert out to LVEA for PEM injections.
18:56 PI mode 28 ringing up changed from -30ø to -90ø
19:04 PI mode 27 ringing up changed from -10ø to +60ø
19:15 chasing PI mode 27 round a bit more and finally settling on +120ø and adjusted gain from 5000 to 6000.
19:45 Robert back out to LVEA for PEM injections.
20:16 PI mode 28 ringing up. I flipped from -90ø to +90ø
TITLE: 11/25 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Down due to earthquakes
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Anamaria left couple of suggestions of things that I can do to help improve the range. I was going to try for an hour but caused a lockloss in the process. Have been having trouble locking all my shift. There're only two ISI configurations I could try without using BRSX (which is still rung up). USEISM_NOBRSXY took me the furthest towards NLN (I was in NLN once with this configuration) but it seems unstable at ~37 mHz.
LOG:
9:22 Went to get food+cofee and came back to find PI mode 27 rung up pretty high. I was able to damp it.
14:53 Noticed an earthquake showing up on the FOM. USGS reported a 5.2M and 6.5M earthquake in Tajikistan. Terramon predicted the worst of it should arrive a little bit after 7am local time. I tried to switch ISI config to LARGE_EQ_NOBRSXY but lost lock in the process. Could switching the ISI state have caused the lockloss? The FOM reads about 0.8 um/s when I did the switch.
About 20 mins later a verbal alarm warned me about the earthquake. For it to be useful I propose that the threshold is set lower (probably half way lower than the current threshold) so people have time to react accordingly.
15:05 GRB alert. Bad timing, Universe.
15:09 Kyle arrived, going into LVEA.
15:34 Kyle out
~0710 - 0730 hrs. local -> Kyle in and out of the LVEA Survey of temperatures is as expected, 85C +/- 10C. Abiding by manufacturer's spec. of 80C at flange of gauge ( = 65C at PCB end of sensor tube). As such, have low expectations of efficacy of bake-out. At least the setup doesn't seem to intrude on the IFO folk's efforts so maybe they will forget about it and we can extend the bake period (if we can't go hotter, maybe we can go longer?). Also, I removed the access ladder that I had left leaning against BSC8's dome.
Staying down as 5.2M and 6.5M earthquakes in Tajikistan arrive at the site. I switched ISI config from WINDY_NO_BRSX_V2 to LARGE_EQ_NOBRSXY.
"Image acquisition failed error on Nov 23 2016 11:52:23 UTC." I killed the zombie process and reran the code.
TITLE: 11/25 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 69.4735Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT: Wind: 5mph Gusts, 3mph 5min avg Primary useism: 0.04 μm/s Secondary useism: 0.66 μm/s
QUICK SUMMARY: H1 was locked when I arrived. POPAIR dropped during the first half and hour into the shift but it seems stable now. So is the range.
TITLE: 11/25 EVE Shift: 0:00-08:00 UTC (16:00-0:00 PST), all times posted in UTC
STATE of H1: PEM Calibration
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY:
LOG:
Wanted to make/consolidate a few notes regarding operations as of late & for this weekend
PRC Gain & PR3_REFL_WFS
The last few shifts/weeks we have been waivering on the PR3 (POP vs REFL) WFS steps. As of this moment, we are bypassing BOTH of these steps in Guardian. Kiwamu said that if we had higher PRC Gain, we could try for the POP WFS, but the PRC Gain (PR_GAIN_OUT16 on front StripTool) must be 30 or more....it has been hovering at 29, so we are skipping this step.
Sheila tried to improve the PRC gain by tweaking on the PRC alignment over the last few weeks. This sounds like a work in progress. For the weekend, we will ignore these PR3 (POP/REFL) WFS steps.
Beam Diverters
Another step we have been skipping toward the end of the Guardian steps is the CLOSING BEAM DIVERTERS. We want to keep the POP Beam Diverter open, but perhaps for better performance and consistency for PEM Injections, we have been closing the REFL & AS_AIR Beam Diverters Manually (i.e. Sitemap/LSC/Beam Diverters). When you close the AS_AIR, it will give you a glitch in DARM, but it's not too scary.
POP90 & SRC1 pit/yaw Loop
There had been some issues with the SRC1 Loop. Basically it would push the alignment such that the POPAIR_B_RF90 (on the front StripTool) trace would increase (a bad thing). So, if you see this trace increase, you should:
Have not had issues with this for the (3) locks since Kiwamu left. (Knock on wood.)
Topped Crystal Chiller with 250mL. This Closes FAMIS 6498.
(The Sheet is full, & should be given to Jeff B.)
Fairly noisy seismically (useism has been holding at 0.7um/s for last 18hrs & winds are at a steady 9mph).
H1 has been also holding at a steady range of 70Mpc for the last 3hrs (even through some short injections by Robert); Noticeable
.......
Ugh!
4:02: LOCKLOSS: EY Went Crazy!
As I was typing this alog, H1 dropped out of lock. There were no noticeable issues (POP90 had been flat for hours, PI Modes were buried, seismic was noisy, but no changes). However, in addition to the usual HAM6ISI trip, EY's ISI, ETMy, & SUS all tripped.
I reset everyone's Watchdog, but when trying to run ALS, I was getting PDH Alerts (not enough light). Looked further and found that the ETMy DID NOT come back to a normal state:
So I opened ETMx, and then went through everything that looked different with ETMy. After a while, ETMy started to look fine. The ODC even came back green. At around this point, I talked with Betsy and I snapped a photo of ETMy with my phone to her & at this point it looked OK. We looked at the safe.snaps, and the Diffs for ETMy looked known & acceptable.
Additionally, ALS was locking in the Y-arm. So we are hesitantly going to say we are back, but I hope there isn't a switch, gain, filter, etc. which I could have missed.
OK, back at it.
SUS_ETMY Guardian Managmenet [Operator] Errors
As I was fixin' to get back to locking, I had a Guardian error saying SUS_ETMY was Managed by another User (this was me when I tried running an INIT on SUS_ETMY). I had taken it back to AUTO, but apparently, that isn't what I should have done.
With Travis & Betsy talking me through it, we tracked it down to the correct INIT (I had tried ISC_LOCK, with no luck). The error was coming from ALIGN_IFO, so eventually figured out that it needed the INIT to be run. Then we had SUS_ETMY being MANAGED properly.
Since H1 has been running suprisingly stable (no PIs rung up [speak of the devil---28 perked up as I typed] & SRC1 has been servoing fine), I went ahead and addressed DIFFERENCES on the SDF. Going a node at a time, below I list how many DIFFS each had, and also give a summary note about them as well. Attached you will also find a snapshots for all the DIFFs before I made them GREEN (well, except for SUSETMY...I forgot to snap one).
I reckon some of these will be RED again soon due to changes: PI's always change, Calibration may change, etc.
SUSIM: 1 Total Diffs
ACCEPTED: TRAMP for IM3 Pit
LSC: 6 Total Diffs
ACCEPTED all Gain changes.
ASC: 33 Total Diffs
ACCEPTED: PRC2_Y Filter difference, POP90 Gain, a few offsets, many matrix element changes, and many ODC channels.
REVERTED (2) TRamps
OMC: 3 Total Diffs
ACCEPTED: ODC channels
PSLISS: 1 Total Diffs
ACCEPTED: Ref_signal (has been moving around last few days)
ISIETMX: 9 Total Diffs
ACCEPTED all 9 filter changes (this is due to no BRSx for next few days)---For these Seismic SDFs, we probably want to update these when we are back to nominal environmental conditions and have BRSx back. Since the SEI Config could change a bit depending on weather & health of BRS's, will we NOT monitor these?
SUSETMX: 1 Total Diffs
ACCEPTED: GAIN for the L1 Lock Gain of ETMx (its nominal WAS 0.0)
SUSETMY: 2 Total Diffs (forgot to take snapshot!)
ACCEPTED: P2L & Y2L TRAMPS
ALSEX: 3 Total Diffs
ACCEPTED: These are all "EXTRA_AI" ??
ALSEY: 3 Total Diffs
ACCEPTED: These are all "EXTRA_AI" ??
SUSPROCPI: 4 Total Diffs
ACCEPTED gain & phase changes
CS ECAT PLC1: 8 Total Diffs
All related to "pico"
CALCS: 1 Total Diffs
Value for Pause
CALEX: 1 Total Diffs (forgot to take snapshot!)
Value for SINGAIN
"Slowly but surely..." I'll need BSC8 access in the morning and again tomorrow evening. Check out the attached image. This looks like a step response that couldn't be the result of a real pressure change. I would guess it has something to do with the shared 24 DC supply between PT180 and PT120B and that pulling the fuse for PT180 changed the supply's load - or something - but nothing related to heating the PT180 hardware.
TITLE: 11/25 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 22mph Gusts, 15mph 5min avg---> Hoping it doesn't get windier!
Primary useism: 0.06 μm/s
Secondary useism: 0.66 μm/s---> this is pretty high. Hope it stays flat or (obviously drops)
QUICK SUMMARY:
Ed, Kiwamu, Sheila (on phone)
The attached is the new AS36 I matrix which was able to stabilize the SRC1 loop, at least for 30 minutes. I changed only one element, SEG3 -> PIT element. It was -0.487 and now -0.6. Before this modfication, Ed and I closed the SRC1 loop with the old element. Seemingly issue was in pitch which ran away very slowly on a time scale of 5 minutes or so. We then opened the pitch loop and manually aligned SRM so that it maximizes the AS90/POP90 ratio. Then, looking at the error signal, we have determined the desired value for the element. No physics involved.
For OPS,
If the SRC1 loop is still unstable or slowly drifts (which should be visible as increased POP90 on the striptool), the first action should be to open the SRC1 loop by simply zeroing the loop gains.
17:10 Waiting at NOISE_TUNINGS. Losing recycling gain (AS90 over POP90) trace. Turned off SRC loops turned off as suggested by Nutsinee to try and hand align SR2.
17:15 ...never got to try aligning SR2 - LockLoss
21:10 aaaaand we're back. Initial alignment
21:15 Jim W on site.
21:25 Jim headed down to EX to deal with BRS
22:40 Jim headed back from EX. Begin locking.
00:00 Kiwamu has H1. Handing off to Corey
I came in today to see if I could resurrect BRSX, but I was unsuccessful. I re-enabled the damping at one point to see if it was still working and after a while the damper table seemed to just stop servoing. I also damped the BRS by hand a couple times, but it would ring back up, for no apparent reason. It's all very strange, I'm not sure whats going on. I am going to turn a couple of sensor correction taps off to keep operators from accidentally engaging the BRS, until I have a chance to talk to Krishna about how to fix BRSX.
For now, I have defined a couple of states for SEI_CONF to help keep the IFO running. There is a WINDY_NOBRSX_V2, that puts ETMX on 45 mhz blends, but keeps the other chambers on their 250mhz blends with low freq sensor correction. There is also a USEISM_MOD_WIND_NOBRSX, if the wind is low and microseism is too high.
IMC trends showed substantial movement in Pitch from the lock 12 hours ago. Clearing the WFS histories got it re-locked. ASC re-aligning.
MC1 - 7µrad
MC2 - 19µrad
MC3 - 3µrad
0.03-0.1 Hz FOM reached 10 um/s without any ISI tripping. Hooray!