H1 locked for 18hr 17min
16:49 restarted the Range Integrand DTT on Video0.
Not much else to report at this point.
LLO has been trying ground STS feed forward to HAM4 (Rana's alog ). I attach some spectra here suggesting we may want to try it as well. First plot is the coherence between the ground STS and SRCL_CTRL, red and blue are during a lock on Feb 14, green and brown are from a lock this afternoon. Even though our microseism is a factor of ~20 lower than it was during the lock in February, there is still some coherence between the Z STS and SRCL. The second plot shows the ITMY Z (in nm/s) and SRCL_CTRL (don't know the units here) spectra for both locks. The last plot shows the transfer functions from the STS to SRCL, red and blue are February, green and brown are today, looks like the coupling doesn't change much even with very different ground inputs.
Many thanks to everyone at LDAS for fixing the issue with CDS SSH access to the cluster.
K. Mogushi I witnessed glitches below 100Hz around 8:20UTC on Jul 20th in magnetometer x, y and z, but I do not know the cause of it. HAM 6 (OMC) x-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_72E7D4_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png LEVA x-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_20971E_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png EY x-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_1D4533_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png HAM 6 (OMC) y-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_62EF30_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png LEVA y-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_1E6840_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png EX y-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_AA5283_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png HAM 6 (OMC) z-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_29F575_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png LEVA z-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_14CF11_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png EX z-axis: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170720/plots/H1-ALL_60E63E_MEDIAN_RATIO_SPECTROGRAM-1184544018-86400.png
P. Marsh Jenne had asked to see if Delta L Ext noise in the 30-80 Hz band dropped while ETM and ITM beam spot positions were being moved this month; the short answer is no. In the attached document, the 1-100 Hz range is shown for various times during the spot moves, as compared against a reference spectrum on June 30th. The only obvious change is that some 20 Hz lines drop out between spot moves around 3:15 UTC and 3:45 UTC on June 15th but Jenne suggests that these were injected lines being shut off manually.
This is the PR3 and SR3 OSEM and Oplev plot referred to in alog 37553, under PR3+SR3 osem jumps:
PLOT 1:
PR3 PITCH:
PR3 YAW:
PLOT 2:
SR3 PITCH:
SR3 YAW:
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:
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.
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.
