Received GRB alert at 08:23 (00:23) - LHO in Observing for only 19 minutes before alert. LLO still recovering from earlier lockloss. Ignored alert.
Title: 11/20/2015, Evening Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT) State of H1: 08:04 (16:00), The IFO locked at NOMINAL_LOW_NOISE, 22.2w, 77Mpc. Outgoing Operator: Ed Quick Summary: IFO has been in Observing mode for 4 minutes. Ed has just recovered from an earthquake related lockloss. Environmental conditions are good – wind is a light breeze (4-7mph), seismic activity is below 0.1 um/s, and microseism is centered around 0.3 um/s.
TITLE: Nov 18 DAY Shift 00:00-08:00UTC (04:00-00:00 PDT), all times posted in UTC
STATE Of H1: SUPPORT:
LOCK DURATION: ≈ 4.75
INCOMING OPERATOR: Jeff B
END-OF-SHIFT SUMMARY: Lockloss; 5.5Mag - Japanese bounce mode. First attempt at re-locking made it to DARM_WFS. Second attempt required manual DIFF VCO adjustment. Stopped at CARM_ON_TR to wait for ASC to converge - ETMX Saturations. Third attempt: All three times got good DRMI lock. I’m gonna let this one cook for a bit. EQ band still not really below .1µm/s yet. Dropped slightly below .1µm so proceeded….no luck. Small aftershock is coming. SUCCESS! Handing off to Jeff.
ACTIVITY LOG:
03:15 Tour group into the control room
05:00 Playing with cdsutils audio just to hear some sounds I got some Verbal Alarms:
TRANS Injection running (Nov 20 05:05:00 UTC)
TRANS Injection inactive (Nov 20 05:05:25 UTC)
TRANS Injection running (Nov 20 05:08:00 UTC)
TRANS Injection inactive (Nov 20 05:08:24 UTC)
Hmmmm…
06:10 Lockloss - Earthquake; EQ bands rise to 1µm/s. No significant movement in µSeism
07:44 Jeff B on site. Still no lock and small aftershock is inbound.
08:04 Intention Bit set to Undisturbed
08:04UTC!
06:10UTC
| ifo | P-phase Arrival Time | S-phase Arrival Time | R-wave Arrival Time | R-Wave Velocity (micro m/s) | EQ Distance (km) | GPS P-phase Arrival Time | GPS S-phase Arrival Time | GPS R-wave Arrival Time |
|---|---|---|---|---|---|---|---|---|
| H1 | 21:43:39 PST | 21:52:58 PST | 22:12:12 PST | 0.979172 | 8475.152 | 1132033436.5 | 1132033995.0 | 1132035149.8 |
| L1 | 23:45:52 CST | 23:53:45 CST | 00:26:46 CST | 0.605742 | 11533.17 | 1132033569.5 | 1132034042.5 | 1132036023.5 |
| G1 | 06:44:57 CET | 06:53:23 CET | 07:20:16 CET | 0.741625 | 10168.32 | 1132033514.3 | 1132034020.2 | 1132035633.5 |
| V1 | 06:45:25 CET | 06:53:34 CET | 07:23:32 CET | 0.668707 | 10852.45 | 1132033542.3 | 1132034031.2 |
1132035829.0 |
Guardian is notifying me that AS beam shutter isn't closed.Is it supposed to be?
MID-SHIFT SUMMARY: IFO has been locked and observing for 4hrs40min @ 80.7Mpc. Winds are calm. EQ bands haven’t changed. µSei is just touching .5µm/s. There was a tour groub of Cub Scouts in the control room at 03:15UTC. Other than a couple of big ETMY saturations, everything has been running smoothly.
This entry is to document a wandering line that is sometimes present between ~600hz to ~670hz in H1. This line is annoying for some burst searches (I know it shows up in the GRB-triggered X-pipeline search, and I understand it may show up in other burst searches as well). For two-detector searches, triggers caused by this line are generally caught by coherence vetos. Also, the folks running the pipeline are able to manually cut triggers from these frequencies in post-processing. So, while this is not extremely urgent, my hope is that someone will see this and have an idea of how to easily get rid of this line.
The easiest place to see this line is in the FScan plots on the detchar summary page. For example, the following is an FScan spectogram from Nov 10, you can see this line trending from 670 Hz down to 655 Hz over the course of ~14 hours (the x-axes on these plots are quite annoying): https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H1_DUAL_ARM/H1_DUAL_ARM_HANN/H1_DUAL_ARM_HANN/fscans_2015_11_10_06_00_01_PST_Tue/H1_GDS-CALIB_STRAIN/spec_620.00_720.00_H1_1131112818_1131199218.png
The 2nd harmonic shows up as well: https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H1_DUAL_ARM/H1_DUAL_ARM_HANN/H1_DUAL_ARM_HANN/fscans_2015_11_10_06_00_01_PST_Tue/H1_GDS-CALIB_STRAIN/spec_1320.00_1420.00_H1_1131112818_1131199218.png
Usually it varies more erratically: https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H1_DUAL_ARM/H1_DUAL_ARM_HANN/H1_DUAL_ARM_HANN/fscans_2015_11_08_06_00_01_PST_Sun/H1_GDS-CALIB_STRAIN/spec_620.00_720.00_H1_1130940019_1131026418.png
Sometimes, it goes away entirely: https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H1_DUAL_ARM/H1_DUAL_ARM_HANN/H1_DUAL_ARM_HANN/fscans_2015_11_16_06_00_02_PST_Mon/H1_GDS-CALIB_STRAIN/spec_620.00_720.00_H1_1131631219_1131717619.png
This line shows up in the other ifo degrees of freedom (perhaps unsurprisingly):
I had an idea to check some PSL vibration and PWR channels. There was a moment when I thought the PSL microphone was seeing the line (compare these times: STRAIN vs MIC), but I think it was a coincidence as the line in MIC stays constant even as the wandering line wanders. Nothing in the following channels:
As a follow-up to Hartmut's question about the DARM rms, here are spectra of the in- and out-of-loop DARM sensors before and after transitioning to DC readout (at 2 W input power). The spectra are calibrated into RIN.
The left-hand plots show the sensors when DARM is controlled via AS45Q. Above 10 Hz or so, we see the sensing noise of AS45Q impressed onto the DARM loop. From 2 Hz to 8 Hz or so, and below 0.5 Hz, both sensors appear to see some DARM displacement noise. Between 0.5 Hz and 2 Hz, the sensors are not seeing the same signal. If the AS45Q signal in this region is indeed DARM displacement noise (rather than some kind of loop-suppressed sensing noise), this would seem to indicate that the sensing noise of the DC readout chain is higher than the intrinsic DARM displacement noise by a factor of a few in this region.
The right-hand plots show the sensors when DARM is controlled via DCPD sum. During the transition, an additional boost is engaged (two complex poles at 2 Hz, two complex zeros at 8 Hz), so this makes it tricky to directly compare these plots with the left-hand plots. Probably it is best to try to get an equivalent set of plots for the intermediate case (DARM controlled by AS45Q, boost engaged).
Attached is the same plot as before, but this time both configurations have the same OLTF (boost on).
Times:
After finding that the new lines and a broad peak at around 1020Hz are correlated with the RF AM monitor channels and RF45 out of loop sensors but not in-loop (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=23552), I went to the floor and started to move the Tenma power supply from the wall AC outlet to the power strip in the PSL rack, and move the +-17V from the ISC rack to the PSL rack.
We powered off the RF AM monitor by first disabling the +-30V output of Tenma, then disconnecting the +-17V connector from the ISC rack, then disconnecting the AC power cable of Tenma from the AC outlet. One of these actions kicked the IFO out of lock.
When the IFO locked again, the lines and the peak were still there. At this point, RF AM monitor was still connected to the EOM, but the +-17V cable was disconnected from the supply, and the +-30V supply AC power cable was disconnected. In the first attachment, the red trace ("RFAM monitor power disconnected outside of the PSL room") corresponds to this state. The second attachemnt shows the connection cartoon.
The blue trace is from this morning when RFAM monitor was connected and working (third attachment for the cartoon). Black is from a week ago, i.e. no RFAM monitor unit.
Then we totally isolated RF AM monitor from everything else by terminating the coupled output of the couplers, and disconnecting the DAQ cable from the AA chassis. Green trace ("RF AM monitor totally disconnected") corresponds to this state as well as the fourth attachment. The lines and the 1020Hz peak definitely got smaller but they're still there.
At this point, we could remove the couplers and pull everything out to completely revert back to the old configuration to see if the noise goes away.
However, doing so means breaking the lock again, and considering the relocking difficulty we experienced today, I talked with Michael Landry and we agreed to run the IFO as is till tomorrow.
As of now, LSC-MOD_RF9 channels are not measuring anything.
TITLE: 11/19 [DAY Shift]: 16:00-24:00 UTC (08:00-16:00 PDT), all times posted in UTC STATE Of H1: Observing at ~ 77 MPc. SHIFT SUMMARY: Most of the shift was devoted to troubleshooting RF 45 AM monitor noise. Back to observing at 00:13 UTC. ITMX, ITMY and BS ISI blends are on 45mHz. EMTX X and ETMY Y ISI blends are on 45mHz. ETMX Y and ETMY X ISI blends are on Quite_90. Accepted SDF differences for these (see attached). Ran a2l. Winds are around 10 mph. Earthquake seismic band is between ~ 0.01 and 0.05 um/s. Microseism is between 0.1 and 0.4 um/s. From the cameras the lights are off in the LVEA, PSL enclosure, end X, end Y and mid X. I can not tell if they are off at mid Y. INCOMING OPERATOR: Ed ACTIVITY LOG: 17:10 Out of observing for Keita to test grounding configurations for RF AM monitor. Not going into PSL enclosure. (WP 5616) 17:39 Kyle to X28 17:48 Lock loss likely from powering down of RF AM monitor 19:08 Evan and Keita to PSL enclosure to disconnect RF AM monitor 19:25 Lock loss likely from Evan and Keita in PSL enclosure 19:37 Evan and Keita done 20:07 Kyle back from X28 for lunch 20:15 Evan to LVEA (WP 5617) 20:40 Evan done 21:26 Kyle to mid Y then X28 23:46 Evan and Keita to LVEA to disconnect RF AM monitor DAQ cable 00:08 Kyle back
TITLE: Nov 19 EVE Shift 00:00-08:00UTC (08:00-04:00 PDT), all times posted in UTC
STATE Of H1: Locking
OUTGOING OPERATOR: Patrick
QUICK SUMMARY: IFO is locked at NLN but ongoing 45MHzRFAM work has us not Observing yet. µSei is ≈.3µm/s. EQ bands ≈.03µm/s. Winds are below 20MPH.
1005-1205 and 1400-1545 hrs local -> Kyle back and forth between CS and BT port X2-8 Ran diesel generator at BT port X2-8 between 1030-1540 hrs local
The ALS Comm and Diff "shuttered" states are now GoTo states, since we've had two or more locklosses today when shuttering ALS. This is somewhat similar to what we saw back in August (aLog 20286) where if the ALS can't get to the shuttered state, it goes to lockloss, going through the ALS Down state, which clears things like the DARM gain. This isn't good, since at this point we're not using ALS for DARM anymore, so it doesn't matter if the green laser loses lock. Today, the green Xarm was losing lock before we asked for the shuttered state, which was causing the guardian to take ALS_DIFF through its down state. Anyhow, "shuttered" is now a GoTo state so that even if the greens lose lock, we don't lose the whole IFO needlessly.
I restarted it. Screenshot of error attached.
Keita, Evan
We installed a mixer-based 45 MHz RFAM monitor using two spare 45 MHz spigots on the distribution amplifier on the ISC rack. This provides an unobtrusive way to look for 45 MHz amplitude glitches on the ISC rack (i.e., it does not require inserting anything into the main 45 MHz drive that goes to the EOM driver and the EOM). On the other hand, if the glitches are only on the main 45 MHz drive, this monitor will not tell us anything.
Set-up is as follows:
I have calibrated LSC-EXTRA_AI_1_OUT so that it is in volts. This channel is not dequeued, but if we have another hours-long episode of glitching we can watch the test points in real time.
Took me a while to figure out that "not dequeued" is really "not DQ-ed", which means that the channel is not in the permanent DAQ channel list (where it has the prefix _DQ).
Likely Keita and Evan disconnecting the RF AM monitor in the PSL enclosure.
We would like to know the range of counts we have available for doing hardware injections with PCAL. Hardware injections are filtered with an inverse actuation filter to get from strain to counts, this is the CAL-PINJX_HARDWARE filterbank. Here I've filtered waveforms with the CAL-PINJX_HARDWARE filterbank and see how many counts they require. I've attached plots of the time series in counts. Last Thursday a filter was added to compensate for the upsampling that is done in the analog electronics. This seems to have a significant effect on the counts. I did a test with the coherentbbh0 waveform (used in hardware injections tests before) and saw that it increased its counts by a factor of ~3. I've attached plots for before and after adding this filter. Here I report the max number of counts from the waveforms: * CW injections: ~1500 counts * 1.4-1.4 non-spinning SEOBNRv2 waveform (target SNR is ~15): 7e7 counts * 25-25 non-spinning SEOBNRv2 waveform (target SNR is ~15): ~10000 counts * coherentbbh0 waveform from hardware injections tests (recovered SNR is ~18-23): ~20000 counts Note these SNRs are approximates and can change depending on sky location. It was quoted that perhaps the CW injections could change by a factor of 2. There is also a higher-frequency line that gets injected in PCALX and we need to take this into consideration as well.
I filtered the 1.4-1.4 non-spinning BNS template with and without the inverse anti-imaging filter that was added last week. The first plot is the h(t) time series for the waveform. It is near the time of the merger where the maximum number of counts occurs. The second plot is the filtered time series in counts without the inverse anti-imaging filter. The maximum is 5e6 counts. The third plot is the filtered time series in counts with the inverse anti-imaging filter. The maximum is 7e7 counts.
