TITLE: 12/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68.7782Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 10mph Gusts, 8mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.29 μm/s
QUICK SUMMARY: Observing for 23 hours now.
0:10 Intent bit set to commissioning so Evan can turn off high frequency PCal line for HW inj.
0:11 Evan accepted the new SDF diff for PCal, so we went back to Observe.
0:17 Injection gain ramping dropped us out of Observe, Evan set this gain to 'Not Monitored', and we were back to Observe within the minute
0:34 PCal HF line turned back on, out of Observe. I am running a2l since it looks like it is time, and Sheila is opportunistically working one of her work permits.
I turned off the 4301.3 Hz Pcal line at 00:10 Dec 8 2016 UTC for the planned stochastic injection. This dropped us from observing intent for a brief time. I updated the SDF and we returned to observing. I will turn the line back on once the stochastic injection has concluded.
Pcal line turned back on at 00:35 Dec 8 2016 UTC.
I've scheduled a coherent stochastic injection for 00:20 UTC (16:20 PT). It will take 13 mins. The update to the schedule file is:
1165191617 H1L1 INJECT_STOCHASTIC_ACTIVE 1 1.0 stoch/Waveform/SB_ER10_{ifo}.txt
The PINJ_TRANSIENT_GAIN change from 0 to 1 for the stochastic injection knocked us out of observing intent before the start of the injection. We made this channel now unmonitored and went back to observing before the injection began.
The stochastic waveform was successfully injected into both IFOs. The log file for H1 INJ_TRANS is attached.
'Double modes' seen in some PI mode bands are not from test mass resonances, in agreement with model conclusions. Follow up on this .
I've looked at frequency shifting of the peaks seen in the 15060 - 15090 Hz range during 11 hours of the current lock.
Attached plots:
3:48 pm local
Took 30 sec to overfill CP3 by raising LLCV from 18% to 50% open. I lowered back to 17% since there was some pressure at exhaust and fill time was so fast.
The dust monitor alarm levels have been set to their correct values. All future alarms should be treated as valid and should be investigated. Please open an aLOG and notify Jeff B.
CP4 appears to have joined with the disfunctioning CP3 and is now being investigated by Kyle and Chandra. Until further notice operators should expect false level indications at CP4.
CP4 bottom sensing line plugged up this morning after alarming all night. Kyle and I applied up to 180 psig of N2 to the sensing line in an effort to clear the blockage but so far no luck (we've left sensing line under pressure for several hours while watching exhaust pressure).
We performed a manual overfill at 11am by turning LLCV bypass valve 1/2 turn open. Overfill took 1 hour.
I started to install thermocouples at the exhaust line similar to CP3 so we can monitor and fill from control room as we do CP3.
Attached is a trend of the corner EtherCAT Device0 channels while there was a broken module on 11/26, see alog 31854. The error can be seen in the ERROR_FLAG, SLAVE_COUNTERROR and the FRAMEWORKINGCNTs. The SLAVECOUNTACTUAL dropped from 345 to below 50—indicating a broken link or module.
On Nov 1 chassis 3 was pulled for some repairs, see alog 31081. The Device0 channels showed similar behavior.
On Nov 15 the power supply was changed for the baffled PD controllers, see alog 31509. This temporarily removed 4 modules from the EtherCAT chain. Again, we can see this clearly in the Device0 channels.
The last plot shows frame rates. Most frames seem to be lost during the above repairs and modifications.
No errors were detected in the end stations.
Reveived a second GRB Alert at 20:50 (12:50PT). Both sites in Observing mode. Will extend the hold until 21:50 (13:50PT)
Received GRB alert at 20:05 (12:05PT) - LLO received same. Both IFOs in Observing mode. Will observe hold until 21:50.
Hold will last until 21:05 - Not 21:50
Dropped out of Observing from 18:50 (10:50PT) to 18:52 (10:52PT) while Jeff K. reenabled scheduled injections.
J. Kissel for S. Karki WP #6368 I've moved the PCALX roaming line, its long duration sweep, from 4001.3 Hz to 4301.3 Hz. See schedule status below. Since it looks like we'll have the duty cycle to just finish the schedule within a week, I'm just going to continue to re-gathering the highest frequency data. As such, Sudarshan has something consistent and straightforward with which to work instead of data with a bunch details or qualifications. Frequency Planned Amplitude Planned Duration Actual Amplitude Start Time Stop Time Achieved Duration (Hz) (ct) (hh:mm) (ct) (UTC) (UTC) (hh:mm) --------------------------------------------------------------------------------------------------------------------------------------------------------- 1001.3 35k 02:00 39322.0 Nov 28 2016 17:20:44 UTC Nov 30 2016 17:16:00 UTC days @ 30 W 1501.3 35k 02:00 39322.0 Nov 30 2016 17:27:00 UTC Nov 30 2016 19:36:00 UTC 02:09 @ 30 W 2001.3 35k 02:00 39322.0 Nov 30 2016 19:36:00 UTC Nov 30 2016 22:07:00 UTC 02:31 @ 30 W 2501.3 35k 05:00 39322.0 Nov 30 2016 22:08:00 UTC Dec 02 2016 20:16:00 UTC days @ 30 W 3001.3 35k 05:00 39322.0 Dec 02 2016 20:17:00 UTC Dec 05 2016 16:58:57 UTC days @ 30 W 3501.3 35k 05:00 39322.0 Dec 05 2016 16:58:57 UTC Dec 06 2016 21:09:56 UTC ~15:00 @ 30 W 4001.3 40k 10:00 39322.0 Dec 06 2016 21:09:56 UTC Dec 07 2016 18:50:09 UTC ~20:00 @ 30 W 4301.3 40k 10:00 39322.0 Dec 07 2016 18:50:09 UTC 4501.3 40k 10:00 39322.0 4801.3 40k 10:00 39222.0 5001.3 40k 10:00 39222.0 Frequency Planned Amplitude Planned Duration Actual Amplitude Start Time Stop Time Achieved Duration (Hz) (ct) (hh:mm) (ct) (UTC) (UTC) (hh:mm) --------------------------------------------------------------------------------------------------------------------------------------------------------- 1001.3 35k 02:00 39322.0 Nov 11 2016 21:37:50 UTC Nov 12 2016 03:28:21 UTC ~several hours @ 25 W 1501.3 35k 02:00 39322.0 Oct 24 2016 15:26:57 UTC Oct 31 2016 15:44:29 UTC ~week @ 25 W 2001.3 35k 02:00 39322.0 Oct 17 2016 21:22:03 UTC Oct 24 2016 15:26:57 UTC several days (at both 50W and 25 W) 2501.3 35k 05:00 39322.0 Oct 12 2016 03:20:41 UTC Oct 17 2016 21:22:03 UTC days @ 50 W 3001.3 35k 05:00 39322.0 Oct 06 2016 18:39:26 UTC Oct 12 2016 03:20:41 UTC days @ 50 W 3501.3 35k 05:00 39322.0 Jul 06 2016 18:56:13 UTC Oct 06 2016 18:39:26 UTC months @ 50 W 4001.3 40k 10:00 39322.0 Nov 12 2016 03:28:21 UTC Nov 16 2016 22:17:29 UTC days @ 30 W (see LHO aLOG 31546 for caveats) 4301.3 40k 10:00 39322.0 Nov 16 2016 22:17:29 UTC Nov 18 2016 17:08:49 UTC days @ 30 W 4501.3 40k 10:00 39322.0 Nov 18 2016 17:08:49 UTC Nov 20 2016 16:54:32 UTC days @ 30 W (see LHO aLOG 31610 for caveats) 4801.3 40k 10:00 39222.0 Nov 20 2016 16:54:32 UTC Nov 22 2016 23:56:06 UTC days @ 30 W 5001.3 40k 10:00 39222.0 Nov 22 2016 23:56:06 UTC Nov 28 2016 17:20:44 UTC days @ 30 W (line was OFF and ON for Hardware INJ)
Note, PCALX was briefly turned OFF during this 4301.3 Hz stretch. See LHO aLOG 32323.
The Pcal to DARM ratio for these individual lines were calculated using SLM Tool and the result is tabulated below. The Cavity pole and the optical gain on the last column are eyeballed measurement from the CalMon Tool . These time dependent corrections havenot been applied to the sensing function analysis yet.
Freq Start Time End Time FFT Real Complex Coh CC Pole (O. Gain)
---------------------------------------------------------------------------------------------------------------------
1001.3 30-Nov-2016 09:16:44 30-Nov-2016 13:47:04 10 0.022149 -0.358814 0.999589 346.05(0.9863)
---------------------------------------------------------------------------------------------------------------------
1501.3 30-Nov-2016 17:28:11 30-Nov-2016 19:36:18 10 -0.017951 -0.109817 0.999943 346.05(0.9863)
---------------------------------------------------------------------------------------------------------------------
2001.3 30-Nov-2016 19:36:53 30-Nov-2016 21:01:35 10 -0.015679 -0.044511 0.999391 346.05(0.9863)
---------------------------------------------------------------------------------------------------------------------
2501.3 02-Dec-2016 07:52:51 02-Dec-2016 20:16:47 30 -0.011385 -0.020594 0.998321 347.69(0.9703)
---------------------------------------------------------------------------------------------------------------------
3001.3 04-Dec-2016 02:27:58 05-Dec-2016 00:00:17 30 -0.007719 -0.010563 0.999057 347.06(0.9614)
---------------------------------------------------------------------------------------------------------------------
3501.3 06-Dec-2016 02:27:26 06-Dec-2016 06:10:11 30 -0.005708 -0.005431 0.988492 350.70(0.9793)
3501.3 06-Dec-2016 10:36:18 06-Dec-2016 15:03:35 30 350.70(0.9793)
---------------------------------------------------------------------------------------------------------------------
4001.3 12-Nov-2016 17:20:18 12-Nov-2016 20:49:17 60 -0.004374 -0.003211 0.996350 350.00(0.9966)
4001.3 12-Nov-2016 09:48:25 12-Nov-2016 16:40:53 60 350.00(0.9966)
---------------------------------------------------------------------------------------------------------------------
4301.3 18-Nov-2016 05:20:00 18-Nov-2016 12:44:49 60 -0.003607 -0.002212 0.985922 345.04(0.9748)
4301.3 17-Nov-2016 14:26:40 17-Nov-2016 17:20:13 60 347.00(0.9730)
4301.3 17-Nov-2016 08:56:40 17-Nov-2016 11:07:35 60 347.00(0.9730)
---------------------------------------------------------------------------------------------------------------------
4501.3 20-Nov-2016 05:00:00 20-Nov-2016 13:24:30 60 -0.003366 -0.002162 0.990728 350.76(0.9985)
4501.3 19-Nov-2016 15:40:00 19-Nov-2016 23:48:16 60 350.21(1.0017)
---------------------------------------------------------------------------------------------------------------------
4801.3 22-Nov-2016 07:43:20 22-Nov-2016 16:01:44 60 -0.002883 -0.001369 0.959987 346.89(0.9890)
4801.3 21-Nov-2016 15:20:00 21-Nov-2016 18:22:20 60 346.71(0.9979)
4801.3 21-Nov-2016 04:36:40 21-Nov-2016 09:28:48 60 346.71(0.9979)
---------------------------------------------------------------------------------------------------------------------
5001.3 25-Nov-2016 07:43:17 25-Nov-2016 14:52:54 60 -0.002634 -0.000904 0.973928 348.94(0.9625)
5001.3 27-Nov-2016 11:44:40 27-Nov-2016 18:04:12 60 345.48(0.9724)
---------------------------------------------------------------------------------------------------------------------
More detailed Analysis.
With the ASC IMC model now running at 16384 Hz we look at the coherence of jitter as measured by the IMC WFS and other channels up to 7.4 kHz. Not sure we can conclude anything except that pointing errros contaminate everything.
We can compare this with an older 900-Hz bandwidth measurement from alog 31631 which was taken before the piezo peak fix (alog 31974).
Note that 1084Hz thing doesn't have coherence with IMC WFS.
Can you check the DC sum channels for the IMC WFS as well? They are the ones that hVeto keeps finding as related to the 1080 Hz noise, and they see a modulation in the noise rather than a steady spectrum.
Done, again nothing for the bump in question though there are coherence bumps for f>1100Hz and f<800Hz.
TITLE: 12/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 70.7388Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Pretty smooth shift as far as locking goes. Some excitement regarding CP4 (see aLog 32283). Also, set some arbitrarily high thresholds for most dust monitors to stop alarms. JeffB will reset them tomorrow. Locked for over 6 hours now.
LOG:
3:35 CP4 alarm
5:24 GRB alert, contacted LLO who verified that they received the alert, begin standdown
6:24 GRB standdown end
7:10 PI mode 27 ringing up, changed phase from 20 to 120. Did not go out of Observe. Are we supposed to go out of Observing to make PI mode changes??
As of now, you do not need to drop out to change either PI phase or gain. We unmonitored these so they wont drop you out anyway. If PI ever gets so high that it takes more than a phase flip, gain flip, or couple thousand gain increase, you're seeing it in DARM, and you're worried about losing lock, you 'd want to drop out.
As a benchmark against which to compare upcoming O2 data, I have compiled a list of narrow lines seen in the H1 DARM spectrum up to 2000 Hz, using 107 hours of ER10 FScan 30-minute SFTs. There are no big surprises relative to the lines and combs Ansel and I have reported on previously from ER9 and later data, but below are some observations. Attached figures show selected band spectra, and a zipped attachment contains a much larger set of bands. Also attached for reference is a plaintext list of combs, isolated lines, PEM-associated lines. etc. In the attached spectra, the red curve is the ER10 data, and the black curve is the full-O1 data. The label annotations are keyed to the height of the red curve, but in some cases, those labels refer to lines in the O1 data that are not (yet) visible in accumulated current data. For the most part, lines seen in O1 that don't show up in ER10 nonetheless remain for now in the lines list and still have labels on the graphs that end up in the red fuzz. If they fail to emerge in O2 data, they will be deleted from future line lists. Observations:
Here is a plot of the violin mode harmonics around 1kHz, comparing the amplitudes today to the amplitudes right after the damping efforts of Nov 30th.
We don't actively damp these by default, only when someone manually engages damping do they get damped. Durring the first part of ER10 ISI trips caused by tidal problems were ringing them up, but that problem is fixed now and most modes are ringing down. ETMX modes (between 1003 and 1006Hz) have increased in amplitude since the 30th.
The largest peak here is the pair on ETMY that Keith points out, we have settings that work to damp both of these modes using the mode9 filter bank on ETMY, and it would not be difficult to turn this damping on automatically in the guardian.
Our question for Keith and detchar is is this (the current spectrum) good enough? Or should we continue to try to add automatic damping for some of these modes?
Automatically damping the violin modes would reduce up-conversion contamination at the starts of lock stretches, making more data usable for CW searches. Even small excess powers in narrow bins leads to unnecessary outliers in analysis that waste computing and manpower. Unless there is a downside to such damping, it seems warranted. thanks, Keith
Back to Observing at 0:48 UTC.