Displaying reports 69861-69880 of 84519.Go to page Start 3490 3491 3492 3493 3494 3495 3496 3497 3498 End
Reports until 13:28, Friday 14 November 2014
H1 CDS (ISC)
david.barker@LIGO.ORG - posted 13:28, Friday 14 November 2014 - last comment - 22:55, Friday 14 November 2014(15067)
investigation into strange LSC ramped mux matrix behavior last weekend

Alexa, Nic, Jim, Dave

Alexa reported strange LSC-PD_DOF_MTRX input ramped mux matrix behavior last weekend. Symptoms were: new element values were taken immediately without loading, ramping continued indefinitely. The current theory is that a rogue script is setting H1:LSC-PD_DOF_MTRX_LOAD_MATRIX to 1 frequently. On monday this channel was added to conlog, and conlog reported that during monday afternoon and early evening this EPICS channel was being set to 1 several times a second. We also discovered that the DAQ trends were not showing this high frequency activity, this underreporting is under investigation (only seen in the LOAD channel, all other matrix channels trend correctly).

At 11/10 20:19PST monday evening the rogue loader stopped running and has not restarted since. Initial scans of guardian and home account directories have not found any script which would be loading the matrix frequently. Guardian logs its PV settings and these are seen at very low rates (max 100 per day). We may have to wait for the problem to reappear in order to track it down further. Investigation is continuing.

Comments related to this report
jameson.rollins@LIGO.ORG - 14:36, Friday 14 November 2014 (15069)

This reeks of bad guardian programming to me.  I would put money on one of the ISC nodes writing a one to that LOAD_MATRIX channel every cycle.   Look for that channel name in whatever guardian node is actuating on that matrix, or just grep for it in all ISC nodes.

alexan.staley@LIGO.ORG - 17:07, Friday 14 November 2014 (15075)

Jamie, we had seen this behavior with all the ISC guardians set to "DOWN" and/or paused. I don't see any guardian that loads the matrix in the "DOWN" state.

H1 SUS
betsy.weaver@LIGO.ORG - posted 11:42, Friday 14 November 2014 - last comment - 16:28, Friday 14 November 2014(15062)
ETMy Temp excursion

As noted over the last few days, the temperature at LHO has dropped significantly over the last few days and the HVAC temp control of Ey and the LVEA have wandered more than normal.  For the record, attached is an 8 day trend showing the temperature drop at End-Y versus the ETMy main and reaction chain vertical, pitch, and yaw positions.

Images attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 11:41, Friday 14 November 2014 (15064)

In order to check model calibrations and to compare with LLO's temperature drift measuremenst from Aug (alog 14008), I looked closer at a smaller band of temperature change in the above plot.  I chose a quieter time when ETMy was not being manipulated by commisioning but during a 1.5 degC temperature change in the End Y VEA on 11/08.

 

During our -1.5 degC temp change the ETMy suspension shows the following drift in Pitch and Yaw:

ETMy M0 PIT * ETMy R0 PIT ETMy M0 YAW ETMy R0 YAW
35 urad 21 mrad + 7 mrad 2 urad 3 urad

With Vertical showing the following drift magnitude:

ETMy M0 V ETMy R0 V
18 um 16 um

 

Note, the ETMy R0 (reaction chain) seems to show some stepping which we are looking into, so the drift trend has a step in between the 21 um drift and a 7 um drift.

Images attached to this comment
betsy.weaver@LIGO.ORG - 11:39, Friday 14 November 2014 (15065)
Images attached to this comment
H1 SUS
keita.kawabe@LIGO.ORG - posted 11:24, Friday 14 November 2014 (15063)
New IM4 alignment slider values

New IM4 nominal bias sliders: [13350, -5056].

Good range for IM4 bias after the initial alignment procedure is [13350 +- 2400, -5056 +- 330] assuming that the MC is behaving well.

The "good range" gives you +-2 mm displacement on the PR2 baffle, which is a non issue for clipping, or +-60urad in IM4 rotation.

IM4 slider calibration was remeasured, it's: 0.025 rad/bogorad for PIT, 0.182 rad/bogorad for YAW.

The slider change from yesterday, i.e. [3364.4, -118] slider counts (micro bogorad), corresponds to [88.3, -21.5] urad physical rotation.


What was done:

After the LVEA temperature settled, IM4 was scanned while the PR2 baffle and the SRM baffle was monitored. Before I started IM4 [P,Y] was [9985.6, -4938].

For IM4 YAW, I was able to see when the beam barely touched the PR2 baffle edge, and when the straight shot beam on SRM baffle disapperaed. I made the average to determine when the beam is 50% blocked.

For PIT the driver railed before I was able to completely block anything, I only recorded when the beam barely touches the PR2 baffle edge.

  barely touches Completely blocked Average
Left, Y bias 800+-100 1800+-100 1300+-70
Right, Y bias -6300+-200 -12200+-200 -9250+-140
Top, P bias -25300+-1000 NA NA
Bottom, P bias 52000+-1000 NA NA

Since baffle hole appears to be a 65.4mm diameter circle, and since the beam is supposed to be 26mm from the right edge, the new position is

P = (52000-25300+-1400)/2 = 13350+-700.

Y =26/65.4*(1300+-70) + 39.4/65.4 * (-9250+-140) = -5056+-90.

Slider calibration is the angle over the baffle diameter 65.4mm/17m divided by two divided by the slider difference, i.e.

calibration for P = 65.4e-3m/17m/2/(52000E-6+25300E-6+-1400E-6 bogorad) = 0.0249(1+-0.02) rad/bogorad

for Y = 65.4e-3/17/2/(1300E-6+9250E-6+-160E-6) = 0.182(1+-0.015) rad/bogorad

H1 SEI
hugh.radkins@LIGO.ORG - posted 10:26, Friday 14 November 2014 (15057)
WHAMs 2 & 4 GS13 gains set to low--will investigate

JeffK says may be a leftover from unexplained ISI trips.  I'll study.

Here are TFs from the Ground STSs to the ISIs GS13 in low gain.  I'll switch to high gain and compare when that transition won't potentially disturb the commissioners.

In low gain, there is good coherence bewteen 2 and ~10 hz.  Cross couple channels, shown for HAM2, are all pretty small.

Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 09:49, Friday 14 November 2014 (15058)
WHAM3 ISI Trips on GS13s--Doesn't look like anyone was in the LVEA

See plot...I don't know what this is.

So this ISI sat tripped for some 20 minutes until I was scanning the SEIs.  I will implement an alarm system so these do not languish.

Images attached to this report
H1 SUS
keita.kawabe@LIGO.ORG - posted 09:32, Friday 14 November 2014 - last comment - 11:59, Friday 14 November 2014(15056)
IM4 was found tripped in the morning.

It tripped at Nov 14 2014 03:48:32 UTC, which is 19:48:32 local time yesterday.

Comments related to this report
kiwamu.izumi@LIGO.ORG - 11:59, Friday 14 November 2014 (15066)

Probably it was me shaking the HAM2 ISI for checking the PR3 performance. Good catch !

H1 ISC (SUS)
hugh.radkins@LIGO.ORG - posted 09:28, Friday 14 November 2014 (15055)
LHO PR3 & SR3 OpLev Piers are contacted by Cleanrrom Curtains--maybe should be cleared

I noticed while walking by that air currents (from my passing) caused the curtains to swing free and then thump on the box.  This doesn't seem good.  The curtains could likely be tied back, easy.  Or maybe the cleanroom should be moved, a bit harder.

H1 General
keita.kawabe@LIGO.ORG - posted 09:13, Friday 14 November 2014 (15054)
Temperature settled.

Seems like the temperature was already good-ish as of 18:00 or so yesterday.

Images attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 08:55, Friday 14 November 2014 (15052)
morning meeting notes
Doug will rezero SR3 optical lever around 10am
The beam balance is misbehaving, Krishna will be here Tuesday to investigate
PEM cabling at end Y
Ken moving AC outlets at end X
Jeff and Andres packing and removing tooling at end X and end Y
H1 SEI
hugh.radkins@LIGO.ORG - posted 08:15, Friday 14 November 2014 (15051)
WHAM5 ISI found tripped this AM--Actuators--2011pst last night

Looks like an unwarranted glitch on the actuator.  The CPS aren't moving before the trip.  The GS13 respond quickly (hard to tell if this is cause or effect) but again there is no preamble.

Images attached to this report
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 08:13, Friday 14 November 2014 (15050)
CDS model and DAQ restart report, Thursday 13th November 2014

model restarts logged for Thu 13/Nov/2014
2014_11_13 09:48 h1ioppsl0
2014_11_13 09:48 h1psldbb
2014_11_13 09:48 h1pslfss
2014_11_13 09:48 h1psliss
2014_11_13 09:48 h1pslpmc

restart of h1psl0 models during beckhoff chassis repair.

H1 SUS (ISC)
jeffrey.kissel@LIGO.ORG - posted 23:31, Thursday 13 November 2014 - last comment - 22:51, Monday 17 November 2014(15049)
Potentially New H1 SUS ETMY UIM (L1) L2P Filter Design
J. Kissel

I've measured new transfer functions necessary redesign of the H1SUSETMY UIM (L1) DRIVEALIGN frequency-dependent decoupling filters for L2P and L2Y. For the impatient, the last page of the last attachement shows a comparison between the proposed new design and the old, currently installed / in-use design. I have *not* installed this filter because I'd like to discuss the results with commissioners tomorrow morning (and it'll take me some time to resurrect quack to get these installed). In fact, this may argue for us to indeed just copy over ETMX's filter.

Details:
-----------------------------------------
I attach the measurement results (see 2014-11-13_H1SUSETMY_L1_drivealignfilters_rawdata.pdf), but the raw templates can be found here:

/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGL1/Results/Data/
2014-11-13_H1SUSETMY_L1_L2PY_WhiteNoise_ReactionChainTest.xml
2014-11-13_H1SUSETMY_L1_L2PY_WhiteNoise.xml
2014-11-13_H1SUSETMY_L1_P2PY_WhiteNoise.xml
2014-11-13_H1SUSETMY_L1_Y2PY_WhiteNoise.xml

Not that I drove through the TEST filter banks (instead of having to turn off all the existing filters in the LOCK and DRIVEALIGN banks), and made sure that optical lever damping was OFF, and local damping was the LLO design as described in LHO aLOG 14959.

I focus this entry solely on L2P, but the data exists for an L2Y filter if ever needed. in the first four pages, Pink curves are the current measurement, and black curves are what were used in the original design of the previous filter by Arnaud (see LHO aLOG 11832). The encouraging fact is that the data supports exactly what we'd model from the change in damping loop filter design (see green traces on pg 5 of first attachement to LHO aLOG 14959). As an aside -- just because Betsy made me think of it while chasing down slider values -- what effect does reaction chain alignment have on these off-diagonal, lower-stage transfer functions? One might guess that if the L2P cross-coupling isn't something fundamental but a result of dirt alignment affects between the coils on the reaction chain and the magnets on the main, then one would see a change in the L2P transfer function with different alignments of the reaction chain. The good news is that is doesn't have any effect -- see the last page of 2014-11-13_H1SUSETMY_L1_drivealignfilters_rawdata.pdf. I compare the same transfer function for 4 different reaction chain alignments. They still have the old dead-reckoned calibration factors installed, so we know they're not exactly [urads] but close enough for the scale of these offsets used; they use up about 1/2 the DAC range.

As far as the design goes, I used the same transfer function fitting routine and filter generation software suite that (I think) Arnaud used, namely the function
/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/FilterDesign/Scripts/Length2Angle_decoupling.m 
which is essentially a wrapper around the function,
/ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/happyVectfit.m 
which Keita's wrapper around the function,
/ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/vectfit3.m
All tweaking of input parameters to the fitting routine, and plots were made using the overarching script
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGL1/design_H1SUSETMY_L1_L2P_20141113.m

Notable key additions to the design software -- a computation of the final filter's impulse response, as well as a comparison to the previous design.

As I know Arnaud had struggled, I struggled to find a fit with which I was really happy, namely because we all *know* that the L2P transfer function should fall off as some large power of frequency (again, see the models of these TFs on pg 5 of LHO aLOG 14959), but I can't find a set of parameters happyVectFit / vectfit3.m that allows for such a roll-off at high frequency. Indeed, the height of the final flat part of the L2P fit transfer function directly determines the high-frequency gain of the decoupling filter, and directly impacts the impulse response time. I settled on a filter that does a poor job at reproducing the > 2 [Hz] behavior of the L2P measurement, BUT I think it's OK because
(a) the small magnitude of the high-frequency causes a significant drop in impulse response time, and
(b) At the UIM, we're typically driving below 2 [Hz] -- especially if the crossover remains at 0.9 [Hz] as quoted in LHO aLOG 15025, so the accuracy of inversion is not so critical. Though I didn't find any design aLOGs, this seems to have been the philosophy behind the ETMX UIM L2P filter because it ends up looking strikingly similar.
I should say also that having to tune the uncertainty tolerance, the order (i.e. number of poles) in the filter, the tolerance for when to throw out adjacent poles and zeros, the frequency range over which to fit -- all free parameters into happyVectFit.m -- as one has to do to get what one wants in the end really destroys the advantage of automating the fitting process. If only there was a better way...
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 17:55, Friday 14 November 2014 (15076)ISC, SEI
I've installed the filter into H1:SUS-ETMY_L1_DRIVEALIGN_L2P filter bank, in FMs 5&6 via autoquack. 

HOWEVER
(1) I have not tested the filter performance with transfer functions or step response
(2) I've split the L2P and (invP2P * rolloff) into two filter banks. Even with the rolloff, the (invP2P * rolloff) filter has more zeros than poles, so foton has added a whole bunch of high-frequency poles to compensate. Though the *total* filter's -- L2P * (invP2P * rolloff) --  number of poles is equal to the number of zeros, I think the high-dynamic range, zero pole, cancellation between the two filters isn't working out. This is resulting in a HUGE calculated impulse response, which may or may not be real.
(3) This is my first time using quack to install Matlab filters into foton in a *really* long time, so I'm nervous of its functionality.

I attach a series of comparisons with ETMX's filter. The bode plot, in the frequency band we care about (pgs 1 and 2) seems reasonable. Both ETMX and ETMY have some high-frequency garbage in their impulse response, but the overall amplitude of the impulse response in ETMY is many orders of magnitude larger than that of ETMX (!!!). Further, taking the transfer function out well beyond the Nyquist frequency, we see that they behave significantly differently at the Nyquist frequency (~7 [kHz]).

As such, I'm still entirely unsure that this new filter gunna work, and may require further tweaking.

Anyways, these are installed in 
FM5 "UIM_L2P"
FM6 "UIM_invP2P"
and should be turned on TOGETHER, with no other filters engaged in the module, if one would like to be bold and try it over the weekend.

P.S. in case you've forgotten, when you autoquack in a filter who's name has a space in it, and you try to load the new filter coefficients, Foton will hate you. You will, at least, get a nasty-gram on the GDS_TP screen's filter message, ${IFO}:FEC-${DCUID}_MSG saying "bad filter coeff definition on line 259 in .txt," pointing you to the exact line of the problem. So with Jim's confirmation that "Oh yeah, you DEFINITELY don't wanna do that." I changed spaces to underscores and all worked fine.
Non-image files attached to this comment
nicolas.smith@LIGO.ORG - 22:51, Monday 17 November 2014 (15117)

These filters did indeed run away and saturate the DAC. (The EPICS values were even showing “-Inf,” I’d never seen that before). I don’t think we can get away with more zeros than poles in a filter module, even if they are compensated by some other module.

I took the two filters (FM6 and 7) and viewed them in the foton “Multiple” mode, then I took the output in the “Alternate” box of foton and copied that into FM10.

When I tried this, instead of a huge mess I got a nice step response according to foton, and the frequency response was the same as the two original filters. As seen below (new is red, old is blue):

foton
However, stupid foton wouldn’t save the filter (but gave no error message). In the end, I had to take this “Alternate” output and split it up into two filters, being careful that each had more poles than zeros. This allowed me to save the foton file and load the filters into the frontend. I tested that the impulse response behaved nicely by putting an offset into the filter bank.

The two filters are in FM5 and FM10. Their names reflect my frustration.

Images attached to this comment
H1 SUS
kiwamu.izumi@LIGO.ORG - posted 21:05, Thursday 13 November 2014 (15048)
HLTS study: PR3 pitch transmission measurements

I silently started studying the performance of the HLTSs, i.e. PR3 and SR3. The major questions I want to answer in this study is:

I did not get a point where I can conclude something yet, but here are some summary of what I did today for it. To be continued.

 

(what I did)

To start off the study, I did measurements of the pitch transmission -- a transfer function from the suspension point to the mirror in pitch -- on PR3. Since SR3 did not have a GS13 witness sensor routed to the front end model yet, I was not able to get the same measurement on SR3 this time.

I shook ISO_RY_EXC of the HAM2 ISI in order to have better signal-to-noise ratio in the measurement. Note that a passive measurement without excitations did not give me good coherence and so for the reason I ended up shaking the ISI. I used random noise excitation in a frequency band of 10 Hz and limited the amplitude to be 200 counts in order not to trip the ISI watchdog. Also I have added 3rd order boosts below 1 Hz in the excitation in order to further improve the signal-to-noise ratio at the low frequencies. The dtt file currently resides in /ligo/home/kiwamu.izumi/Public/dtt/PR3_pitch_ISI_excitation.xml

I did the same measurement twice, one with the oplev damping loop running in pitch and the other without the oplev damping. The attached below shows the results. The red traces are the ones with the oplev running and the blue are without the oplev running. As seen, the oplev damping loop suppresses the components in 0.1-2 Hz at a cost of a gain peaking at 3 Hz. Since the rms is usually dominated by the components below 1 Hz, this confirms that the oplev damping loop is doing the right job.

 

(Next move)

As a next step, I would like to compare the pitch transmission with a model in order to see whethere it is something we expected or not.

Images attached to this report
H1 SUS (DetChar, ISC)
jeffrey.kissel@LIGO.ORG - posted 15:35, Thursday 13 November 2014 - last comment - 10:16, Friday 14 November 2014(15039)
H1 SUS ETMY Investigation Continues
J. Kissel, A. Staley, K. Izumi, K. Kawabe

Continuing investigations of why ETMY behaves poorly when attempting ALS DIFF (see LHO aLOG 15037) -- I've looked at two more things:
(1) Pitch-only optical lever Damping: This had been turned on only *after* it had been decided that ETMY was "fragile," i.e. any impulses would shake the SUS quite a bit -- but I checked it anyways. First attachment is comparing spectra with the PUM (L2) stage actuated, optical lever Pitch damping loop ON vs. OFF. It's damping pitch, as expected, and not injecting anything terrible. This of course is assessing the stationary noise, and we're worried about non-stationary problems ... but ruling things OUT with quantitative data, I feel, is just as important along the investigatory route.

(2) DRIVEALIGN Matrices: I attach comparisons between everything in the ETMs UIM (L1) DRIVEALIGN matrices (Only the P2P, Y2Y, and L2P have anything in them, so those are what's compared in the attachment). I believe the original design intent for P2P and Y2Y filters was to have global WFS transfer function be similar to the test-mass transfer functions -- hence the high-Q, plant inversion-y type stuff. They are slightly different between the two test masses, but, in-fact, they don't matter matter at all because we don't feed any angular signals to the UIM stage. 

However, I've found that the ETMY UIM L2P frequency-dependent decoupling filter in the UIM bank is significantly different than ETMX's -- and the filter has a much larger step response. I compare three different sets of filters on pgs 1 and 2:
ETMX -- FM1 & FM2, "L2P" & "L2P2" 
ETMY, Current -- FM1, FM2, & FM4 "L2P", "L2P2", and "BetterRolloff"
ETM, Legacy -- FM6 & FM7,  "L2Plegacy" & "L2P2legacy" 
It looks like the initial story here is laid out in LHO aLOG 11832, but there're several more aLOGs referencing UIM / L1 L2P Filters, and how they've been bad, they've been good, they've been turned off, they've been turned on...

The foton calculation of the step response disagrees with the measured step response LHO aLOG 14832 -- but recall that the filter step response is not the only thing measured in that 14832 measurement -- it's measuring both the filter AND mechanical step response. We now have local damping filters from LLO which has reduced the mechanical impulse response time by a factor of a few. This, coupled with a smaller impulse response filter should help, but we'll remeasure once a new filter is designed.

I'll move on to chasing this down -- re-measure the step response, and also remeasure the plant upon which these filters were designed.

Of course, an immediate, band-aid fix could be just to copy ETMX's L2P filter over to ETMY, but while we wait for the temperature in the VEAs to settle down, I've been given the green light to measure some TFs.
Non-image files attached to this report
Comments related to this report
alexan.staley@LIGO.ORG - 10:16, Friday 14 November 2014 (15059)

CORRECTION:

The first attached plot in alog 14832 shows the impulse reponse of ETMY L1 stage with:

  • ETMY, Current -- FM1, FM2, & FM4 "L2P", "L2P2", and "BetterRolloff"
  • ETMY, simple -- FM8 "z0.5p10"
  • ETMY, old roll off -- FM1, FM2 & FM3
  • ETMY, nothing -- all filters off

The trace the was *not* plotted was the ETMY, Legacy -- FM6, FM7. We had taken an impulse response of this configuration, but it was so bad that we did not leave it in the plot. Clearly this disagreed with Jeff's response.

H1 AOS
edmond.merilh@LIGO.ORG - posted 01:23, Tuesday 11 November 2014 - last comment - 10:23, Friday 14 November 2014(14962)
Gain and whitening stages for HAM2 and HAM3 oplevs

In preparation for tomorrow's maintenance on HAM2 and HAM3, I have set the following gains and whitening stages on HAM2 and HAM3 OPLEVs.

Whitening and Gain settings of Gain (dB) Whitening stages
HAM2 18 2
HAM3 6 2

I added the dewhitening filters in the input flter banks of the oplevs and switched on two stages to mirror the analog state.   The analog switch states are shown in the attached pics. The label on the cable tells us the name of the oplev that is addressed by the dip-switch board. 

The oplevs are, as yet, not calibrated.  The HAM3 shows an uncompensated whitening though I have switched on the dewhitening filters stages.   Will investigate further.

Images attached to this report
Comments related to this report
suresh.doravari@LIGO.ORG - 10:19, Friday 14 November 2014 (15060)
Ed writes such nice alogs about oplevs and whitening filters and diode lasers and stuff!!
edmond.merilh@LIGO.ORG - 10:23, Friday 14 November 2014 (15061)

Imagine how nice it would be if I knew what i was talking about!

H1 AOS (DetChar)
sheila.dwyer@LIGO.ORG - posted 10:25, Thursday 09 October 2014 - last comment - 09:07, Friday 14 November 2014(14381)
etmx oplev glitches

Jason, Sheila

There have been some glitches on the ETMX oplev, which don't seem to correspond to motion of the optic, the attached screen shot shows an example.  I think that I have seen glitches like this that were much larger in amplitude, but am not sure. 

One question for detchar is if they have a tool that can search for glitches like these, and give us some information about how often they are happening, how large they are, and maybe monitor to see if they are happening on other op levs

Another issue is that sometimes the lasers fail, which is often foretold by a several seconds oscillation in the oplev sum.  Can detchar set up some kind of monitoring for that?

Of course the real question is how can we fix it......

Images attached to this report
Comments related to this report
shivaraj.kandhasamy@LIGO.ORG - 14:40, Friday 10 October 2014 (14406)DetChar

Hi Jason and Sheila, here at LLO  Olmo Cerri, a summer student from UMISS, looked at the possible causes of glitches in OPLEVs. He worked with Suresh. Suresh earlier found that the the temperature variation could cause changes in the cavities of OPLEV laser and thereby changing the laser intensity which would look like glitches. Olmo looked at week long strecthes of data from a few OPELVs and charactersized how many glicthes we see (he wrote a matlab script to find the such gltiches).  They also implemetned a simple temperature stabilization method (LLO a-log) to reduce the gltiches. It seemed to work well. Here is a presentation by  Olmo on this work which shows data before and after the temperature stabilization setup. He is now looking into implemneting an online version of the code.

cody.arceneaux@LIGO.ORG - 09:07, Friday 14 November 2014 (15053)
I set Olmo's code to run on a cron job with the results here:

https://ldas-jobs.ligo-wa.caltech.edu/~codyca/MHoF_results/

We still need to put together a better way to present the results.  The code is set to remove glitches caused by human interaction by looking at the OPTICALIGN offsets.  Also, the results for LLO can be found here:

https://ldas-jobs.ligo-la.caltech.edu/~codyca/MHoF_results/
Displaying reports 69861-69880 of 84519.Go to page Start 3490 3491 3492 3493 3494 3495 3496 3497 3498 End