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.
Title: 1/11 Owl Shift 8:00-16:00 UTC (0:00-8:00 PST). All times in UTC.
State of H1: Observing
Shift Summary: Locked in Observing for my entire shift and ~23 hours total. No issues to report.
Incoming operator: Nutsinee
Activity log:
15:15 Out of Observing, likely due to Richard restarting OMC Trans camera
15:16 Back to Observing
Locked in Observing since before my shift started. A few ETMy saturations not related to RF45. CDS overview shows TPs for H1SUSPR2, H1SUSSR2, and H1LSC in addition to CRC for H1ISIHAM3 and TIM for H1IOPASC0.
TITLE: Jan 10 DAY Shift 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC
STATE Of H1: Observing
SUPPORT: Jeff K
INCOMING OPERATOR: Travis
SHIFT SUMMARY: Nothing new to report. Nice, quiet shift
ACTIVITY LOG:
01:43 started to experience RF45 noise for the first time in the 8+hr lock
06:02 Intention bit switched due to freq change for PCal
06:18 Intention Bit set back to Observe
J. Kissel, R. Savage, E. Merilh Having completed the planned suite of high frequency lines (see LHO aLOG 24843), we've moved the PCALX line up to 5 [kHz] in order to completely cover the 1 to 5 [kHz] band. This enables us to quantify the uncertainty in this region as required by the burst group (see T1300950). First attachment shows that the 5 [kHz] frequency region has only one narrow feature, and PCALX's 5001.3 [Hz] line steers clear of it. Second attachment shows the newly accepted SDF diff. In addition, we've installed two new lines in the PUM and UIM stage of ETMY. This will allow a very precise estimation of each of these stage's strength w.r.t. PCAL, and to confirm they do not evolve with time. The new excitations are piped in to the signal path by re-purposing the pre-existing Pitch and Yaw lockin oscillators; sending their output to every coil on each stage with the same sign in the LKIN2OSEM matrices to create a longitudinal excitation (see attached screenshots). The parameters of these lines are Stage Freq (Hz) CLKGAIN (ct) Oscillator EY L3* 35.9 0.11 H1:SUS-ETMY_L3_CAL_LINE EY L2 35.3 15.0 H1:SUS-ETMY_LKIN_P_OSC EY L1 34.7 45.0 H1:SUS-ETMY_LKIN_Y_OSC * This line already exists, and is part of the normal ~35 [Hz] cluster of lines. Third attachment shows the DARM ASD around the now-5-line cluster, the fourth shows the SDF diffs, and fifth shows the screens in which the parameters exist. I've chosen the frequencies of the UIM and PUM excitations to match LLO's normal cluster of calibration lines, so as to minimize the impact on Pulsar analysis, which I assume is already excluding these frequencies (and they've already satisfies all other criteria as well). For those who will be concerned, I've confirmed that these extra lines have a negligible effect on the inspiral range (< 1 [Mpc]). These lines are also less than 1% of the typical RMS out of each stage, so there should be no danger of (more) DAC saturation (see 6th attachment). We will leave these lines on either as long as LLO still needs to get it's high-frequency "sweep" or until tomorrow morning when we solidify any further plan for the low-frequency region.
J. Kissel, R. Savage, LHO Operators Tallying up the progress so far on the schedule of PCALX excitations at high frequency (see plan in LHO aLOG 24802): Achieved Planned Frequency Amplitude Start Time Stop Time Duration Duration Success? (Hz) (ct) (mm-dd UTC) (mm-dd UTC) (hh:mm) (hh:mm) (Yes / No, reason if no) ------------------------------------------------------------------------------------------------------------------------------ 1001.3 35k 01-09 22:45 01-10 00:05 01:20 01:00 Yes 1501.3 35k 01-09 21:12 01-09 22:42 01:30 01:00 Yes 2001.3 35k 01-09 18:38 01-09 21:03 02:25 02:00 Yes 2501.3 40k 01-09 12:13 01-09 18:31 06:18 02:00 Yes 3001.3 35k 01-10 00:09 01-10 04:38 04:29 04:00 Yes 3501.3 35k 01-10 04:41 01-10 12:07 05:26 06:00 Good Enough! 4001.3 40k 01-09 04:11 01-09 12:04 07:55 08:00 Good Enough! 4501.3 40k 01-10 17:38 01-11 06:02 12:24 12:00 Yes 5001.3 40k 01-11 06:18 on-going (as long as we can get) Thanks to all of the operators who have been dilligently caring for these lines while we sleep! For the record, while these PCALX calibration lines are on, the majority (if not all) of the range is consumed, so we cannot perform PCALX hardware injections.
I used the high frequency calibration lines injected above to estimate the sensing function at those frequencies. For this analysis, SLM Tool was used to obtain the line amplitude and phase of these calibration lines at different relevant channels.
Sensing Function = DARM_ERR[ct] / PCAL_TXPD[m]
The DARM_ERR signal is dewhitened and the PCAL_TXPD is corrected to get metres using the scheme described in G1501518.
Furthermore, ratio of GDS/Pcal is calculated and is included in the attached plot.
A data quality flag has been created to capture times when these extra PCAL lines were in the data. It is H1:DCH-EXTRA_PCAL_LINES:1 and a description of this flag can be found on the detchar wiki.
Over the last few days there have been strange glitch patterns that appear to be harmonics of some sort showing up on the summary pages. I've included a few plots showing this from today and yesterday. It's not particularly easy to read off the glitch frequencies sometimes from these plots so I analyzed spectra to try and find the actual frequencies of these glitches. The numbers below came from looking at peaks in a Strain ASD plot. These are estimates, and for a few of them it's hard to tell exactly which peak corresponds to the glitches.
Frequencies [Hz]:
46.1 56.8 70.1 80 113.75 144 (170.5 or 176) 208 256 (302.2 or 303.2)
I'd asked Vinny to check this out, and am to blame for calling them "harmonics." However, based on the frequencies he's quoted, they're not so harmonic. Attached is a plot of the frequencies and their frequency difference. No two omicron glitch "lines" are exactly harmonic as Vinny suggests. The first few are only roughly 10 [Hz] apart, the next few are 30 [Hz] apart, etc. My hope was that, if they were harmonic, it would point us to a fundamental frequency which might correspond to a known feature (e.g. the ~10 [Hz] QUAD highest vertical modes) that was modulating other noise at low frequency. Looks like no cigar. However, we've been having these "harmonic"-like omicron triggers for the past several days as Vinny shows, and they can reach several hundreds of Hertz. I'll caution folks to just dump this in the "RF45 noise" bucket: while we have seen the EOM driver's control servo show coherence with DARM during / surrounding / between when harmonic-like omicron triggers are happening (such episodes usually correspond with a much more gruesome, pattern-free, omicron glitchgram, and a noticeable decay in sensitivity / sensemon range), we've also seen the harmonic-like omicron triggers when there is no coherence between the EOM driver control servo and DARM. Since this (and the EOM RF frequency control servo) appear to come and go entirely randomly -- has anyone made a comparison with something equally random and unexpected, like ... the space weather?
at 00:39UTC i noticed that OMC REFL and TRANS cameras are producing NO images. Also, Refl centroid is at 0:0 and Trans is off scale -1 : -1.
an FRS has been filed.
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.
