TITLE: 07/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
Wind: 3mph Gusts, 2mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY:
TITLE: 07/21 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Locked all night
TITLE: 07/21 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 0Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
Other than the earthquake, fairly uneventful shift...which is nice.
LOG:
Beginning of shift coincided with an big EQ. Unfortunately, I didn't manage to switch the Operator Observatory Mode to "EARTHQUAKE", so just wanted to note this:
So from 22:56-2:05, we were out for the earthquake (SUS transfer functions were run during this time).
We have been back to OBSERVING for the last hour or so (worked on damping Bounce/Roll modes at the beginning because they were rung up).
Keita, TVo
In Keita's previous alog-33547 , he checked the free swinging ITMs for rubbing by comparing the angular response to the SUS M0_TEST drives during initial alignment by the operators. Looking at the shifts from the norm of the responses as a function of time could signal rubbing as was shown in his aLOG.
In trying to investigate the 10-80Hz noise, we tried to run this script again from June 27th 00:00:00 to July 14th 00:00:00. Picture 1 shows the results:
1) The first plot is the range, operators only run initial alignment out-of-observing.
2) The second plot is the response of the individual optics, you can see that even after the earthquake, they don't change much as a function of time.
3) The third plot shows the ITMY vertical position and a guess at what the rubbing threshold could be based off of Keita's alog above.
4) The fourth plot shows ITMX vertical position.
I tried editing the script to run a similar measurement for ETMs, but the results are much more scattered and will require more investigation. It is possible that the ETM responses are different because they undergo different actuation during initial alignment than the ITMs.
Here is a similar plot for ETMs except using the Oplev/M0_test in order to compare the responses before and after the earthquake. There doesn't seem to be much of a difference in response except at about Day 14.4 in EY Yaw but then it goes back to what it was before.
J. Kissel Took some earthquake time to measure as much SUS as I could. 4 Chains x 6 DOFs in 1.5 hours? Not bad! The ITMs are clear of rubbing. I'll post more detailed plots and compare against old data and model tomorrow. I attach a few choice DTT screenshots of the current measurement (where the reference is some random reference that shouldn't be treated as cannon, but in most cases is indicative of goodness) to whet your appetite. Data files live here: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Data/ 2017-07-20_2320_H1SUSITMX_M0_WhiteNoise_L_0p01to50Hz.xml 2017-07-20_2320_H1SUSITMX_M0_WhiteNoise_P_0p01to50Hz.xml 2017-07-20_2320_H1SUSITMX_M0_WhiteNoise_R_0p01to50Hz.xml 2017-07-20_2320_H1SUSITMX_M0_WhiteNoise_T_0p01to50Hz.xml 2017-07-20_2320_H1SUSITMX_M0_WhiteNoise_V_0p01to50Hz.xml 2017-07-20_2320_H1SUSITMX_M0_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data/ 2017-07-21_0016_H1SUSITMX_R0_WhiteNoise_L_0p01to50Hz.xml 2017-07-21_0016_H1SUSITMX_R0_WhiteNoise_P_0p01to50Hz.xml 2017-07-21_0016_H1SUSITMX_R0_WhiteNoise_R_0p01to50Hz.xml 2017-07-21_0016_H1SUSITMX_R0_WhiteNoise_T_0p01to50Hz.xml 2017-07-21_0016_H1SUSITMX_R0_WhiteNoise_V_0p01to50Hz.xml 2017-07-21_0016_H1SUSITMX_R0_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/ 2017-07-20_2320_H1SUSITMY_M0_Mono_WhiteNoise_L_0p02to50Hz.xml 2017-07-20_2320_H1SUSITMY_M0_Mono_WhiteNoise_P_0p02to50Hz.xml 2017-07-20_2320_H1SUSITMY_M0_Mono_WhiteNoise_R_0p02to50Hz.xml 2017-07-20_2320_H1SUSITMY_M0_Mono_WhiteNoise_T_0p02to50Hz.xml 2017-07-20_2320_H1SUSITMY_M0_Mono_WhiteNoise_V_0p02to50Hz.xml 2017-07-20_2320_H1SUSITMY_M0_Mono_WhiteNoise_Y_0p02to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/ 2017-07-20_2358_H1SUSITMY_R0_L_WhiteNoise_0p01to50Hz.xml 2017-07-20_2358_H1SUSITMY_R0_P_WhiteNoise_0p01to50Hz.xml 2017-07-20_2358_H1SUSITMY_R0_R_WhiteNoise_0p01to50Hz.xml 2017-07-20_2358_H1SUSITMY_R0_T_WhiteNoise_0p01to50Hz.xml 2017-07-20_2358_H1SUSITMY_R0_V_WhiteNoise_0p01to50Hz.xml 2017-07-20_2358_H1SUSITMY_R0_Y_WhiteNoise_0p01to50Hz.xml Notes: Measurements were run with all nominal offsets on. Made sure to remove TEST bank P and Y gains (i.e. set them to 1). Made sure to switch coil driver state to 1 (high range). Ran damping loops for a minute between each DOF. ITMY M0 was measured with 0.02 Hz BW. Want to do 0.01 Hz BW to resolve resonances, but didn't notice until too late (in order to process with matlab scripts, all DOFs need to be the same BW and Freq Range). Don't think it negates results, but a bummer. ITMX R0 R P and Y have less than 5 averages, but it was obvious from first few averages that nothing was wrong.
I'm checking the coil driver switching while we wait for the earthquake to ring down, to ensure that the analog switches are actually switching. Here's a rough note of my method:
* Set BIO state request to negative of the value that you want (i.e. -2 for state 2, -3 for state 3). This gives you control of the coil out filter banks (ex. H1:SUS-ITMX_L2_COILOUTF_UL). Do this for all 4 quadrants.
* Turn off all filters, so you have a flat digital TF from the excitation point to the driver. Do this for all 4 quadrants.
* For BS (only one with oplev damping), disable oplev damping.
* Take TF from coil output filter bank excitation to fastimon channel (ex. H1:SUS-ITMX_L2_COILOUTF_UL_EXC to H1:SUS-ITMX_L2_FASTIMON_UL_OUT).
* Switch analog coil driver state, retake TF, confirm that it changed as expected.
* Put state request back to positive number that it started at; this resets the digital filters appropriately.
All switching seems fine for PRM M3, SRM M3, ITMX L2, ITMY L2, ETMX L2 and ETMY L2, which is all suspensions and stages that we switch coil driver states for, except for BS M2. BS M2's UR coil is different from the other coils on BS M2.
I'm attaching a screenshot of the BS measurements, showing that the shape of the UR analog driver is slightly different in each state, and the overall gain is different by about 8dB.
I ask that the BS M2 coil driver be looked at first thing in the morning.
Looks like BS M2 UR has been like this at least since January. That doesn't mean it shouldn't be fixed, but it does mean that it probably won't help the new noise. I checked a time in January and another in early June. The noisemon and fastimon have always been lower in amplitude than the others, and have some extra forests of lines. The lines are coherent between the noisemon and fastimon, so I think they are showing real junk somewhere in the drive path. The plots show a comparison of UR with another quadrant recently, then a similar plot from January. Last, the coherence shows that the lines in the notch at 300 Hz are coherent between noisemon and fastimon, and there's no drop in coherence near the forests of lines.
Corresponds to FRS Ticket 8594 Ticket has been marked for closure given that the coil driver has been swapped LHO aLOG 37694 and the problem his disappeared.
This earthquake occurred during the shift change this evening.
The attached are comparison of the OMC length and oplev spectra before (4/7/2017 12:30 UTC) and after (today; 20/7/2017 21:00 UTC) the Montana earthquake.
The attached are the spectra of the BS, PR3 and SR3 oplevs, comparing before and after the earthquake. Again I don't see any suspicious changes except that the BS PIT noise floor improved by a few dB for some reason after the earthquake.
TITLE: 07/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 0Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 14mph Gusts, 12mph 5min avg
Primary useism: 0.97 μm/s
Secondary useism: 0.47 μm/s
6.7 Turkey EQ took H1 down as I was walking in.
QUICK SUMMARY:
For Earthquake, ISI_CONFIG was taken to BIG_EARTHQUAKE_NOBRSXY.
While waiting, for earth to calm down, Jeff is going to perform Test Mass transfer functions (to look for any possible rubbing) until the earthquake band (0.03-0.1Hz) drops/quiets down to 0.1um/s.
Attached are plots (Pictures 1&2) of MICH, PRCL, SRCL, and DARM spectra (one plot is zoomed into 10-100 Hz):
References are before the earthquake (06/23/17 03:00:00)
Non-References are after the earthquake (07/20/17 03:00:00)
Seems like no real differences except for MICH so I made a TF between it and DARM just to make sure (Picture 3)
it doesn't look like these DoFs are the root of our problem.
Evan G., Pep C. Summary: We investigated when and why extra lines appear in the DARM spectrum near 1500-1520 Hz after the recent Montana earthquake. These lines appear associated with increased amplitude of the violin resonances, but coupling behavior is not firmly established. We would like the violin modes to come down in amplitude (better damping?) to verify that these lines could be mitigated. Details: Looking back over various spectra computed by the CW group (see here, for example), we find that the lines seem to have an amplitude behavior that changes in time. We wonder if they could be associated with changes in the violin resonances in time. In the attached image, we plot three different times, June 19, July 19, and July 20, 2017. The 1500-1520 Hz band (upper left) shows the increased amplitude of the new lines; at the same time, we plot the violin resonances for the 500 Hz, 1000 Hz, and 1500 Hz bands. Note that the June 19 trace is quiet and we do not see evidence for additional lines. Also, there are no broad shoulders associated with this time. We speculate that the increased amplitude of the violin resonances is causing some strange mixing problem that creates additional lines in DARM. After the Montana earthquake, the lines are much more stationary than we have ever observed lines in this band in the past. We had previously found that lines would be transient in this band. For example: Present March 29 Gone April 4 Present June 28 Gone June 29 When looking for these lines, we caution that not all lines are always present and the amplitude of the lines is quite variable. We also checked that the low frequency noise in DARM is not substantially different, so it's not clear that the broad shoulders are caused by up-conversion. However, since the fundamental violins are sometimes 2 orders of magnitude higher, it might be due to this. Again, better damping of the violins might help here. ;)
TITLE: 07/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
LOG:
Some log was lost due to not saving to draft:
15:30 Apollo on site. Welding outside of MX.
16:49 Lockloss. Unknown
17:00 Richard to LVEA to take a picture while I'm doing alignment.
17:13 re-locking
17:23 Christina to MX to clean.
19:09 Apollo guys done at MX and heading to MY
22:18 UTC
Vacuum pressure gauge PT-345 tripped for some reason so it was reactivated.
LHO Fellow: Jian Liu
See https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20170717 for the complete details.
The summary pages for the X,Y, and Z PEM magnetic noise channels show a change in magnetic noise at EY between 14 July 2017 (Firg. 1) and 15 July 2017 (Fig. 2) characterized by a peak at about 30 Hz and higher broadband noise below the peak. Five minute spectra with start times spaced 10 minutes apart are shown in Fig, 3, again for the Z direction. The starting time is 15 July 2017 00:00:00 UTC (red) with subsequent times 00:10:00 (gold), 00:20:00 (green), 00:30:00 (purple), and 00:40:00 (blue). From Fig. 4, the peak at about 30 Hz starts to appear around 00:20 UTC on 15 July (about 17:20 PDT on 14 July). The full transition is shown for X,Y, and Z several hours apart in Fig. 4 where the elevated broadband noise increase is also seen. In Fig. 4, the two times shown are 14 July 10:00:00 UTC (red, green, blue) and 15 July 20:00:00 UTC (purple, gray, gold).
The time of this transition appears to correspond with PEM injections at EY carried out by Robert Schofield and Pep Covas to identify noise produced by thirsty ravens (see alog 37630). Alog 37523 indicates that the injections began on 14 July at 22:37 UTC and continued for about 2 hours.
Recent Bruco scans (see, e.g., the one on 19 July in alog 37614 do not show any indication that this excess noise correlates with h(t).
19:13UTC have ben trying differetnphases on ETMX Mode4 which causes SDF to take the intention bit to commissioning. CHanging gains while Observing doesn't affect the bit but changing phase does. Should we consider unmonitoring the filter banks to avoid interrupting the data flag or should we not be damping violins while observing. I was of the understanding that it was ok.
WP7080 Reduce FMCS chilled water alarm levels
Bubba, Dave:
The cell phone alarm system was reconfigured and restarted at 10:32PDT. The chilled water supply temperature HIGH alarms were reduced from 55F to 49F. The wait time before sending cell phone texts was reduced from 15min to 5min.
16:50 Lockloss. Reason, unknown.
16:55 doing initial alignment. Found the COMM Beatnote to be low (~ 3.5). It was out a tiny bit in PIT but mostly YAW.
17:13 Begin re-locking sequence.
17:33 manually damping some ETMX Mode 4 at DC Readout.
17:49 Observing @ 55Mpc
In the instance that Livingston should lose lock,
I will break H1 lock for investigation of BS Coil driver and possibly ESD power supply swaps.we will take the opportunity to do investigative work on BS coil driver ad swapping ESD power supplies.