In response to Keita's alog (here) I changed the whitening gain and number of active filters on the ITMx, ITMy, and ETMx optical levers. They are now set as outlined in the 2nd table in Keita's alog. I also enabled the corresponding de-whitening filters in the oplev filter medm screens (ITMy and ETMx only, as these were the only ones that had additional whitening filters enabled) and accepted the changes in SDF.
I took spectra of each segement of the QPD for each TM oplev, both before and after the de-whitening filters (channels labeled IN1 are before de-whitening, channels labeled OUT are after de-whitening) as well as spectra of the pitch and yaw signals of each oplev.. To my knowledge, ETMx and ETMy look as they are supposed to. On the other had, the ITMx and ITMy QPD spectra do not look right to me. When I took the spectra there were ongoing investigations into ITMx ISI coil driver issues and ITM charge measurements (ie, the optics were moving); also, the oplev lasers for both ITMx and ITMy oplevs are unstabilized lasers, sitting on the LVEA floor. All of these could be causing issues with the measurements; they should be re-taken once things have quieted down and see if there are differences. If there are no differences, I fear we may have made things worse for the ITMs. There also appears to be a comb in all of the ITMy spectra. I think this is caused by the laser glitching; as soon as I have a stabilized laser ready for install this laser is getting replaced.
This completes WP #6020.
ITMX looks good to me. All quadrants look similar to each other and the PIT plot looks better than before (e.g. https://alog.ligo-wa.caltech.edu/aLOG/uploads/28615_20160725101947_Screenshotfrom2016-07-2510%3A01%3A12.png).
ITMY looks OK-ish to me except at high kHz for segment 1 and 3, which need to be investigated further. But the thing is that ITMY used to be without any whitening gain and filter that there was no way this kind of oddness could have been revealed before. See the attached plot of the current ITMY oplev signals with the pink line showing the old noise floor, and compare with the above mentioned old plot.
Had bagged entire RGA assembly previously -> Removed 1.5" O-ring valve (redundant valve in series with 1.5" UHV valve) and installed turbo in its place. Backed turbo with leak detector. Opened 1.5" UHV valve to combine detector with RGA volume. Helium line penetrated bag at top while O2 sensor (with internal pump) penetrated bag at bottom. No flow meter on helium but set to "significant" flow rate. O2% fell from 20% to 1.6% over 10 minutes. No leaks detected with helium baseline holding @ 1.2 x 10-9 torr*l/sec or so throughout the helium application -> Once convinced that no leaks were present, I closed the 1.5" UHV valve and "cracked" the isolation valve of the external calibrated helium leak and observed the expected response; thus demonstrating that the mass spec. was sampling the test port during testing. Installed 5 of 6 heat tapes on RGA assembly in preparation of baking it out at the next available opportunity. Note to self: The isolation valves for the Nitrogen and Krypton calibration gases were closed during this testing so the two "factory" double-sided mini-conflat joints did not get tested. Also, I noticed after shutting down and decoupling the leak detector etc. that the factory 2.75" CFF joint between the RGA analyzer and its protective nipple showed a crescent shaped gap. All of the joints tested in this excercise (12 or 13?) where ones that I bolted and are "metal-to-metal" and won't change with with baking. This sole gappy joint could leak following a thermo cycle so I will "cinch" it up and leak check it along with the two double sided joints that I missed before baking.
J. Kissel We're still struggling to get past the Parametric Instability Phoenix (e.g. LHO aLOG 28600), so we haven't had much IFO time / patience to debug ESD bias sign flipping. As such, the charge, effective bias voltage, and actuation strength continue to change slowly. Again (see last week's report in LHO aLOG 28523), ETMX is charging about twice as fast as it has between the prior two flips, so its accumulated charge will begin to get excessive sooner than ETMY. I'll keep pushing for a debug of the bias flipping, but we've got higher priorities with the IFO stability at the moment, and the change from charge is not out of control or ridiculous. Yet.
J. Kissel, J. Betzwieser, B. Storr WP #6023 Joe and Bria have discovered a small bug in the future monitoring of the IFO response parameter time-dependence regarding the use of the sub-function atan2 (see LLO aLOG 27214). As such I've svn up'd the affected library part, /opt/rtcds/userapps/release/cal/common/models/CAL_LINE_MONITOR_MASTER.mdl and recompiled, restarted, and restored the model to the OBSERVE SDF file (which I'd reconciled before restarting).
The flow sensor in the crystal chiller was replaced. The water filters in the chiller room were also replaced as per work permit ... 6008 Power cycled both the diode and crystal chillers. Rebooted the Beckhoff computer. Right away an increase in the flow rate of the crystal chiller was observed. The error message also disappeared. A plot of the before/after flow rates is attached. The exception delay in the crystal chiller was set back to 000 s. JeffB/Jason/Peter
I also happened to notice that the pump current for head 3 is now correctly reporting 50.2 A on the MEDM screen as opposed to 100+ A yesterday (and possibly a number of days before).
The sensor replacement does not appear to have fixed the problem.
Richard told me the crystal chiller was alarming this morning, in addition to the message about the flow sensor error. Nothing a top up of its water level didn't solve. Added about 100 millilitres.
The LVEA has transitioned to LASER SAFE. On the walk around, the left hand side door of TCS-X was found closed but unlocked. Please check your enclosure doors when your table work is completed, thank you.
TITLE: 07/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Travis
SHIFT SUMMARY: Locking at 50 W for commissioning work. Evan and Koji replaced ASAIR PD. No issues.
LOG:
23:39 Nutsinee and Betsy to LVEA HWS table
0:07 Nutsinee and Betsy out
Evan and Koji replacing ASAIR PD after lockloss
6:44 EQ/Wind took us down, nobody except Terra is here, calling it a night
Just a quick note becuase this investigation isn't quite complete yet, but I can improve the recycling gain by moving the SOFT offsets in pitch after moving the PRC1 pitch offset. I have not yet tried adding yaw offsets to this. With pitch only, I can get up to 30 at 50W (previous record was 28 at 50W).
What we'd like to do after finding a semi-good spot is to move the beam spot on some of the PRC mirrors (see Stefan's recent alogs for scripts that do this), which will hopefully let us move the spot on POPA back closer to the center. I wants to be at least 0.65, which is getting uncomfortably close to the edge.
Koji, Evan
We removed the unmodified BBPD S1200242 from ISCT6, and replaced it with S1200236, which has the modifications described in G1500595.
Evan already compensated 12dB (x4). This is indeed consistent with the transimpedance difference betwen the old (1800Ohm@90MHz) and new (450Ohm) BBPD.
The attached plot shows the difference of the normalized RF90 before and after the swap. The gain is matched within 3%.
(As Jenne requested) To avoid the confusion, the control room OBSERVE banner on Ops Overview will no longer show if the intent bit is not set. The banner will show only when both "Ops Observatory Mode (Observing)" and "Undisturbed" buttons are engaged.
Betsy, Nutsinee
LLO recently found their HWS mirrors to be contaminated (LLOalog27041). So we went to the table to take a look at our mirrors and took some pictures.
The mirrors are dusty overall and periscope mirrors show sign of coating degradation (I assume that the watermark-looking patterns are coating defects) Betsy later explained to me those marks are leftover marks from First Contact. See below:
HWSX bottom periscope mirror
HWSX top periscope mittor (sorry I wasn't able to get a good shot)
HWSX STEER M7 and STEER M8
HWSX STEER M6 with flash light shined through the back.
HWSY bottom periscope mirror
HWSY top periscope mirror
HWSY periscope mirror with flash light shined through the back
HWSX return beam (without Hartmann plate)
HWSY return beam
HWSX has been giving us data that makes sense. HWSY data however makes no sense. I forgot to stop the code when I took the Hartmann plate out and in and somehow that caused the scripts to think that there were only few hundred peak counts when everything was closed out. I re-initialized the reference images for both HWSX and HWSY. Every necessary optics were aligned and CO2 heating power was set for 2 W PSL input.
Following the same idea as elog 28442, here is a script for moving the beam spot position on PRM (prmspotmove.py).
It monitors IM3 slides, and moves IM4, PRM and PR2 sliders in such a way the the beam spot positions on PR2 and PR3 don't change.
The script was tuned in INPUT_ALIGN (for IM4 and PR2 matrix elements) and PRM_ALIGN (for PRM matrix elements).
Matrix elements (in rad /rad IM3)
pitIM3toPR2=+0.0022;
yawIM3toPR2=+0.0055;
pitIM3toIM4=-1.3;
yawIM3toIM4=+0.92;
pitIM3toPRM=-0.009;
yawIM3toPRM=+0.031;
Also attached is the python script used for finding the matrix element, getMx.py.
Here is the theoretical matrix for this move (note that signs will vary for pitch and yaw):
IM4/IM3=-1.022385686091801*tim3;
PR2/IM3=0.069871106113604*tim3;
PRM/IM3=-0.350788523435222*tim3;
This was calculated with the following data (in meters):
RPRM=-11;
RPR2=-4.555;
RPR3=36.0;
RITM=1939;
LPRM=16.6128;
LPR2=16.1551;
LPR3=24.88797;
LARM=3994.5;
LIM4=0.413;
LIM3=1.17;
n=1.45;
f=-RITM/(n-1); # thin lens approximation
fm=-RPRM/(n-1); # thin lens approximation
Decreased CP3 LLCV from 24 to 21% open
I have been taking spectra from the SR785 (WP6005) whenever I get a chance over the last week to see if there is any evidence of three mode interactions in the 60kHz to 70kHz region that we will not be sensitive to with the aliased OMC DCPD HF channels that we normally analyze.
There is a consistent peak at 62935Hz, this peak is present with no optical power in the arm cavities.
There are several other more transient peaks, one of the times several had large amplitudes is shown in the first figure.
The largest peak is at 63776Hz The maximum amplitude seen was 5E-6 This is about the same as the 18040Hz mode when it is 2 orders of magnitude above thermal noise and 2 orders of magnitude under unlocking the cavity.
The second largest is at 70160Hz and the third largest at 62336.
There is no evidence of peaks in DARM at this time at the expected aliased frequencies 1760Hz, 3200Hz or 4624Hz and the peaks that appear in the HF channels that do not appear in the normal DCPD channels do not coincide in frequency, see the second image.
We disconnected this SR785 around 11am local time today. This closed work permit #6005.
J. Kissel, T. Hardwick We've taken the liberty of rifling through Carl's home directory in hopes to find the raw data from this entry to re-plot for clarity. We found it! The newly attached plot now highlights the PI modes that Carl mentions in his aLOG, and also shows the anticipated ADC noise. Thus, any modes below 6.3e-6 [V/rtHz] should not be resolved by the ADC, and therefore will show up aliased into digitized signals in the detection band. Terra notes that the mode Carl mentions at 70160 Hz is the largest of several peaks at 69.84, 69.95, and 70.03 kHz (not highlighted), which is likely a mode cluster. Other details: The raw data lives here (determined by Terra knowing that Carl keep his GPIB data in his home folder, then lining up the data on the figure with the filename): /ligo/home/carl.blair/gpib/netgpibdata/dataSPSR785_24-07-2016_212424.txt This data (as described in the referenced work permit 6005), is the raw analog output of the TMSY's red QPD's whitening chassis. This data also happens to cover the frequency region surrounding the 65536 [Hz] native sampling frequency of the General Standards ADC, and the corresponding notch in all Anit-Aliasing (AA) chassis. One can see, delightfully, that there is very little noise or lines in this frequency band on this channel that might also otherwise be aliased down to low frequency. We should perform a similar spectral analysis of the OMC DCPD whitening chassis output voltage to check if their AA chassis is also sufficiently notched so as to not contribute noise in to the DARM sensitivity.
[Matt, Carl]
The phase lock loop is now installed as an optional tool in the PI armory. I have used the settings and method Matt demonstrated to me on the test stand to lock onto OMC PI signals in the last 50W lock. I tried locking onto QPD signals but was unable to at quiescent amplitudes. The phase locked loop in the locked state is shown in the first image. It is tracking a 15521Hz ITMX mode (sorry for the poor labeling in the figure, there's still a few bugs in medm screens).
The settings used were:
Filter I - 100Hz LP Gain 1
Filter Q - 100Hz LP Gain 1
Freq Filter 1 - gain 1
Freq Filter 2 – gain 0.02, 20mHz integrator + low pass see below
FC Count - 10mHz low pass (this was not low enough as the frequency estimate was still fluctuating by 20Hz
Ampl Filt er - 1Hz low pass gain 1
Lock Filter - 1Hz low pass gain 1
Lock was acquired by setting a set frequency close to the mode frequency observed in a spectrum of the OMC HF channels. The loop was engaged with a 100Hz low-pass in Freq Filter 2 then put in a narrow band mode by engaging a 1Hz low-pass in Freq Filter 2, the loop lost lock when I tried to further reduce its bandwidth by either reducing the gain of decreasing the frequency of the low-pass. The figure is in the high bandwidth mode. The PLL and iwave can be accessed from the mode block for any mode and a matrix is used to select a control signal, see the second image.
I think the best way to transition from PLL "aquisition mode" (high-gain and wide-band) is:
This should keep the output of FF2 (which contains an integrator) fairly constant, and thus keep the PLL locked during the transition.
Well, step 1 was supposed to read:
start with gain of 1 in FREQ_FILT1 and FREQ_FILT2 (FF1 and FF2), no filtering in FF1, and Int20mHz + LP10 in FF2
Executive summary: * Good news - as expected, the 16-Hz comb due to the OMC length dither is gone (at least at this sensitivity level) * Bad news - low-frequency 1-Hz combs remain, and some new low-frequency combs & lines have appeared Some details:
I analyzed the 56.8406Hz comb with coherence tool and here are the results. The same structure is found to be significant in 35 channels in ER9, distributed in ISI, SUS, PEM and LSC subsystems. Among all the 35 channels, 22 of them does not have a range up to its 11th harmonic, 625.25 Hz.
Keith indicated in his slog entry that a DAQ malfunction is suspected to be the ultimate source of this, and these findings suggest it's in an EX electronics crate.
Here are a few interesting observations:
The 9th harmonic at 511.56Hz is the weakest in most channels, sometimes buried in noises.
In some PEM channels, there are missing lines at low frequency (< 200 Hz) and high frequency (> 500 Hz).
In PEM and ISI channels, there seems to be another comb structure with a frequency slightly larger than 56.8406Hz coexists. That one is usually most significant at its third harmonics.
Generally, the structure is more clearly seen in LSC, SUS and ISI channels
Sample plots from each subsystem:
Figure 1: We can see the 56.8406Hz comb structure exists with its 9th harmonic weakest in ISI.
Figure 2: PEM channels have more noises and, as in ISI channels, the other comb structure coexists.
Figure 3: SUS channels do not have enough range up its 11th harmonic but we can see its first and second harmonic here.
Figure 4: There is only one channel from LSC but the structure is very clear.
All plots and a list of channels are attached in the zip file.
Just to be clear. Here are the channels that the coherence tool is finding the comb. This is what is supporting Keith's assumption that the problems could be in an EX electronics crate. Channels List: H1:ISI-ETMX_ST2_BLND_RX_GS13_CUR_IN1_DQ_data H1:ISI-ETMX_ST2_BLND_RY_GS13_CUR_IN1_DQ_data H1:ISI-ETMX_ST2_BLND_RZ_GS13_CUR_IN1_DQ_data H1:ISI-ETMX_ST2_BLND_X_GS13_CUR_IN1_DQ_data H1:ISI-ETMX_ST2_BLND_Y_GS13_CUR_IN1_DQ_data H1:ISI-ETMX_ST2_BLND_Z_GS13_CUR_IN1_DQ_data H1:LSC-X_TR_A_LF_OUT_DQ_data H1:PEM-EX_ACC_BSC9_ETMX_Y_DQ_data H1:PEM-EX_ACC_BSC9_ETMX_Z_DQ_data H1:PEM-EX_ACC_ISCTEX_TRANS_X_DQ_data H1:PEM-EX_ACC_VEA_FLOOR_Z_DQ_data H1:PEM-EX_MIC_VEA_MINUSX_DQ_data H1:PEM-EX_MIC_VEA_PLUSX_DQ_data H1:ISI-ETMX_ST1_BLND_Y_T240_CUR_IN1_DQ_data H1:ISI-ETMX_ST1_BLND_Z_T240_CUR_IN1_DQ_data H1:ISI-GND_STS_ETMX_X_DQ_data H1:ISI-GND_STS_ETMX_Y_DQ_data H1:PEM-EX_MAINSMON_EBAY_1_DQ_data H1:PEM-EX_MAINSMON_EBAY_2_DQ_data H1:PEM-EX_MAINSMON_EBAY_3_DQ_data H1:PEM-EX_SEIS_VEA_FLOOR_X_DQ_data H1:PEM-EX_SEIS_VEA_FLOOR_Y_DQ_data H1:SUS-ETMX_L1_WIT_Y_DQ_data H1:SUS-ETMX_L2_WIT_L_DQ_data H1:SUS-ETMX_L2_WIT_P_DQ_data H1:SUS-ETMX_L2_WIT_Y_DQ_data H1:SUS-ETMX_M0_DAMP_L_IN1_DQ_data H1:SUS-ETMX_M0_DAMP_P_IN1_DQ_data H1:SUS-ETMX_M0_DAMP_T_IN1_DQ_data H1:SUS-ETMX_M0_DAMP_V_IN1_DQ_data H1:SUS-ETMX_M0_DAMP_Y_IN1_DQ_data
I chased Comb 23 (type K) in Keith’s post, shown in Keith's original post as
This comb has an offset of 153.3545 Hz and a fundamental frequency of 0.0884Hz. It starts at 153.3545 Hz and goes up to its 11th harmonic, 154.3272 Hz. As is listed in Keith's txt file:
Comb 23 (type K, offset=153.354500): Frequency (offset + harmonic x fund freq) Ampl (m/rtHz) Bar (logarithmic) K 153.3545 ( 0 X 0.0884) 1.844961e-19 **** K 153.4429 ( 1 X 0.0884) 1.949756e-19 **** K 153.5314 ( 2 X 0.0884) 2.165192e-19 ***** K 153.6198 ( 3 X 0.0884) 2.181833e-19 ***** K 153.7082 ( 4 X 0.0884) 2.457840e-19 ***** K 153.7966 ( 5 X 0.0884) 2.243089e-19 ***** K 153.8851 ( 6 X 0.0884) 2.709562e-19 ***** K 153.9735 ( 7 X 0.0884) 2.499596e-19 ***** K 154.0619 ( 8 X 0.0884) 2.562208e-19 ***** K 154.1503 ( 9 X 0.0884) 1.945817e-19 **** K 154.2388 ( 10 X 0.0884) 1.951777e-19 **** K 154.3272 ( 11 X 0.0884) 1.703353e-19 ****
I found the comb structure in two channels of ISI subsystem.
Figure 1 shows the plot of channel H1:ISI-HAM6_BLND_GS13RZ_IN1_DQ. Descriptions of this channel can be found here:
https://cis.ligo.org/channel/314371
Figure 2 shows the plot of channel H1:ISI-HAM6_BLND_GS13Z_IN1_DQ. Descriptions of this channel can be found here:
https://cis.ligo.org/channel/314374
In the plots of both channels, we can see a comb structure stands out at the positions of harmonics. We are wondering about the reason for this:
Why these seismic isolation channels?
This post is supplementary to the first post about coherence analysis result for the 56.8406Hz Comb at
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28619
The first post is addressing the 56.8406Hz comb found in Keith's original post (marked as D comb):
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28364
Information about this comb from the txt file in Keith's post:
Comb 35 (type D, offset=0.000000): Frequency (offset + harmonic x fund freq) Ampl (m/rtHz) Bar (logarithmic) D 56.8406 ( 1 X 56.8406) 3.968800e-17 *********** D 113.6811 ( 2 X 56.8406) 1.773964e-17 ********** D 170.5217 ( 3 X 56.8406) 7.121580e-18 ********* D 227.3622 ( 4 X 56.8406) 3.232935e-18 ******** D 284.2028 ( 5 X 56.8406) 1.166094e-18 ******* D 341.0433 ( 6 X 56.8406) 1.007273e-18 ******* D 397.8839 ( 7 X 56.8406) 5.962059e-19 ****** D 454.7245 ( 8 X 56.8406) 3.752194e-19 ***** D 511.5650 ( 9 X 56.8406) 2.577108e-19 ***** D 568.4056 ( 10 X 56.8406) 1.964393e-19 **** D 625.2461 ( 11 X 56.8406) 1.891774e-19 **** --------------------------------------------------------------
Besides the 35 channels found in the original post, 7 more channels are found to be relevant to the 56.8406Hz Comb. Two new subsystems, ASC and HPI are involved.
These new channels are:
H1:ASC-X_TR_A_NSUM_OUT_DQ
H1:ASC-X_TR_B_NSUM_OUT_DQ
H1:HPI-ETMX_BLND_L4C_Y_IN1_DQ
H1:HPI-ETMX_BLND_L4C_Z_IN1_DQ
H1:PEM-EX_ACC_BSC9_ETMX_X_DQ
H1:SUS-ETMX_L1_WIT_L_DQ
H1:SUS-ETMX_L1_WIT_P_DQ
So updated channel list is (42 channels in total):
H1:ASC-X_TR_A_NSUM_OUT_DQ
H1:ASC-X_TR_B_NSUM_OUT_DQ
H1:HPI-ETMX_BLND_L4C_Y_IN1_DQ
H1:HPI-ETMX_BLND_L4C_Z_IN1_DQ
H1:ISI-ETMX_ST1_BLND_RX_T240_CUR_IN1_DQ
H1:ISI-ETMX_ST1_BLND_RY_T240_CUR_IN1_DQ
H1:ISI-ETMX_ST1_BLND_RZ_T240_CUR_IN1_DQ
H1:ISI-ETMX_ST1_BLND_X_T240_CUR_IN1_DQ
H1:ISI-ETMX_ST1_BLND_Y_T240_CUR_IN1_DQ
H1:ISI-ETMX_ST1_BLND_Z_T240_CUR_IN1_DQ
H1:ISI-ETMX_ST2_BLND_RX_GS13_CUR_IN1_DQ
H1:ISI-ETMX_ST2_BLND_RY_GS13_CUR_IN1_DQ
H1:ISI-ETMX_ST2_BLND_RZ_GS13_CUR_IN1_DQ
H1:ISI-ETMX_ST2_BLND_X_GS13_CUR_IN1_DQ
H1:ISI-ETMX_ST2_BLND_Y_GS13_CUR_IN1_DQ
H1:ISI-ETMX_ST2_BLND_Z_GS13_CUR_IN1_DQ
H1:ISI-GND_STS_ETMX_X_DQ
H1:ISI-GND_STS_ETMX_Y_DQ
H1:LSC-X_TR_A_LF_OUT_DQ
H1:PEM-EX_ACC_BSC9_ETMX_X_DQ
H1:PEM-EX_ACC_BSC9_ETMX_Y_DQ
H1:PEM-EX_ACC_BSC9_ETMX_Z_DQ
H1:PEM-EX_ACC_ISCTEX_TRANS_X_DQ
H1:PEM-EX_ACC_VEA_FLOOR_Z_DQ
H1:PEM-EX_MAINSMON_EBAY_1_DQ
H1:PEM-EX_MAINSMON_EBAY_2_DQ
H1:PEM-EX_MAINSMON_EBAY_3_DQ
H1:PEM-EX_MIC_VEA_MINUSX_DQ
H1:PEM-EX_MIC_VEA_PLUSX_DQ
H1:PEM-EX_SEIS_VEA_FLOOR_X_DQ
H1:PEM-EX_SEIS_VEA_FLOOR_Y_DQ
H1:SUS-ETMX_L1_WIT_L_DQ
H1:SUS-ETMX_L1_WIT_P_DQ
H1:SUS-ETMX_L1_WIT_Y_DQ
H1:SUS-ETMX_L2_WIT_L_DQ
H1:SUS-ETMX_L2_WIT_P_DQ
H1:SUS-ETMX_L2_WIT_Y_DQ
H1:SUS-ETMX_M0_DAMP_L_IN1_DQ
H1:SUS-ETMX_M0_DAMP_P_IN1_DQ
H1:SUS-ETMX_M0_DAMP_T_IN1_DQ
H1:SUS-ETMX_M0_DAMP_V_IN1_DQ
H1:SUS-ETMX_M0_DAMP_Y_IN1_DQ
Attached images are sample plots from ASC and HPI subsystem.
Full results are also attached.
Here are the coherence search results of all the single lines in ER9 data, which are listed in Keith’s post. I found 29 of all the 198 lines on the list and posted the results on my homepage here:
https://ldas-jobs.ligo-wa.caltech.edu/~duo.tao/ER9_single_lines/index.html