Shift Summary: Was Observing unitl an earthquake in Philippines knocked us out.
Incoming operator: Ed
Activity log:
17:03 Lockloss due to an earthquake. See alog24858.
17:12 Rick shutdown 5 kHz Pcal line at X-end.
18:59 Bubba going to mid-Y to work on the pipe under the beam tube.
20:00 Hand over the ifo to Ed.
Monday Morning Meeting Notes
- Jeff gave update on the calibraiton world (sorry I didn't really catch the content. I heard something about high frequency line and data quality flag). Tomorrow is the end of calibration period.
- PEM injection period after O1 ends.
- After tomorrow -- don't call people at night (except for Mike and Richard).
- IFO should be ready to be handed over to the comissioners by Friday.
The temporary PUM and UIM calibration lines slipped passed Rick when he was turning off the last of temporarty calibrations fromt last night. We noticed only after Chris had begun his first injection, so we waited for enough data then briefly went out of observe and turned off the lines -- out of observe at 22:01:27 and back in at 22:02:23 UTC.
FRS 4201 The OMC trans camera (h1cam20) software needed to be manually killed and restarted. Monit would not restart until the pid file had been deleted. Also restarted h1cam14 and h1cam17 since they were in the same state.
11:21UTC @ 76Mpc - Sidenote: I had to manually tweak TMSY to maximize Recycling Power.
I will be conducting some hardware injection tests at H1 and L1. This aLog will be updated as hardware injections are scheduled.
My first attempt to examine my alignment resulted in a perfect transition from PRMI to DRMI. It seems talking about it causes it! She's a very sensitive IFO.
TITLE: Jan 11 DAY Shift 20:00-00:00UTC (12:00-16:00 PDT), all times posted in UTC
STATE Of H1: Locking
OUTGOING OPERATOR: Nutsinee
QUICK SUMMARY: IFO locking. EQ bands have rung down but still not exactly nominal. The "mean" µSei seems to be right above the 90%ile with the Z-axis peaking up to 1µm/s. Winds are calm. Thank you Nutsinee for covering the morning!
Performed a run spanning the time period from 1136160017 (Jan 07 2016 00:00:00 UTC) to 1136571715 (Jan 11 2016 18:21:38 UTC)
The following parameters were used for this run:
No injections were scheduled to occur in this time period.
No injections were found within the channels and frames checked by HWInjReport during this time period.
No anomalies to discuss.
Performed a run spanning the time period from 1136149303 (Jan 06 2016 21:01:26 UTC) to 1136235703 (Jan 07 2016 21:01:26 UTC)
The following parameters were used for this run:
There were no injections scheduled to occur within this time period.
No injections were found to occur within the channels and frames checked by HWInjReport during this time period.
No anomalies to discuss.
Due to several WD trips and 20+ hours lock prior to the lockloss I decided to do an initial alignment.
At about 17:15:00 UTC, I stopped the Xend Pcal line at 5001.3 Hz by setting the amplitude to zero (from 40,000 cts).
A 6.4M earthquake in Philippines knocked us out. Requsted the IFO to Down. If Terramon is right about 4.6 um/s peak we are probably going to be down for another while.
Another 6.1M in Japan reported at 17:08 UTC.
Attached is a summary plot of the laser's performance since New Year's Day.
- the decline in pre-modecleaner transmission appears to match the decline in laser power
(~1.6% versus ~1.6%) quite well
- the decline in NPRO power is ~0.7%
Everything else looks okay.
TITLE: Jan 11 DAY Shift 16:00-00:00UTC (08:00-16:00 PDT), all times posted in UTC
STATE Of H1: Observing
OUTGOING OPERATOR: Travis
QUICK SUMMARY: H1IOPASCO Timing error visible on CDS overview. I'm reluctant to hit the reset button simply because I don't know what IOPASCO is. Otherwise everything looks great. Traffic has been picking up. Wind below 5mph. Useism is on the rise towards 90th percentile.
Jeff K. suggested I hit the reset button. So I did and cleared the error without problem.
During the last lock segment, we had the Tidal Error messages (X& Y COMM CTRL within 10% of limit). Additionally, noticed on the Striptool on nuc1 that IMC-F_OUT16 was diverging & drifting off-screen (see attached). Ultimately there was a lockloss (could it be related?).
Talked to Hugh while we were locked, and he pointed me to the End Station HEPIs & also to the ISC signals they get. He mentioned they have a limit of 700,000counts. ETMy was moving below -36,000 (this was OK). EX was flatlined at 14,660 (this was ODD). But since both of these were well away from 700,000, we ruled out this being a tidal issue and figured it was something upstream (ISC? PSL?). We'll see how the next lock looks.
The attachment shows how the integrated ALS offsets remain as error point offsets for the IMC-F → UIM offloading.
We should bleed these ALS offsets away once we have transitioned off ALS, and preferrably before increasing the laser power (as this will load CARM by a few microns).
I thought that with EX tidal flatlined, the IMC frequency changes to try and keep H1 locked, but then runs out of range causing lock loss?
Wouldn't that mean the EX flatlined is the issue, IMC_F is just responding?
It seems that during this lock acquisition, there were large offsets remaining on the ALS → UIM offloading filter modules, and correspondingly large offsets on the IMC-F → UIM offloading filter modules (which are used during full lock).
The IMC-F → UIM offloading hit the limit around 15:50:00 Z, causing the tidal offloading to halt. As Cheryl said, this means IMC-F starts accumulating a dc offset to keep the laser on resonance.
Performed a run spanning the time period from 1132963217 (Dec 01 2015 00:00:00 UTC) to 1136155727 (Jan 06 2016 22:48:30 UTC)
The following parameters were used for this run:
During this time period, 12 scheduled injections were found to have occurred
Only 1 injection was found to not occur:
Of the occurring scheduled injections, only two occurred as single-IFO injections:
All other scheduled injections occurred as H1-L1 coincident injections. The only UNSCHEDULED injections were 5 CALRESETs at L1 and 1 CALRESET at H1.
The CALRESET injections have the same pattern of occurring with only certain paired combinations of the frame flags indicated by HWInjReport, as seen previously. However, all of the occurring scheduled injections have the anomaly of not occurring in the CAL-INJ channel and not having the TRANSIENT bit set to “off” to indicate the presence of a transient injection. They do occur, consistently, in the ODC-MASTER channel for HOFT, RAW, and RDS frames and the GDS-CALIB channel for HOFT frames.
Minor correction made to report. There were, in fact, 2 single-IFO injections that occurred, both in L1. I missed the second one due to an eyeball error.
As reported by Chris B. in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=24282, the two single-IFO injections were the result of H1 losing lock.
The absence of occurrence of the injections in the CAL-INJ channel turns out to not be an anomaly but the result of a deliberate change to using the new CAL-PINJX_ODC_CHANNEL_OUT_DQ channel to record the information that was originally in CAL-INJ_ODC_CHANNEL_OUT_DQ. Currently, HWInjReport does not check the CAL-PINJX channel, however, it should not be difficult to add checking on this channel.