Displaying reports 58541-58560 of 77985.Go to page Start 2924 2925 2926 2927 2928 2929 2930 2931 2932 End
Reports until 13:26, Monday 27 July 2015
H1 AOS
leonid.prokhorov@LIGO.ORG - posted 13:26, Monday 27 July 2015 (19964)
OPLEV Charge measurements
We continue the charge measurements on ETMs.

About a week ago the bias sign was changed of both ETMs. Before this week data are consistent with positive charging for ETMY and negative charging for ETMX. Charging speed is about 10-20[V] per month. 
This week's data seems to be consistent with a changed sign of charging - negative for ETMY and positive for ETMX. 
Plots are in attachment. 
Images attached to this report
H1 SEI (CDS)
hugh.radkins@LIGO.ORG - posted 11:50, Monday 27 July 2015 (19961)
Yellow lights & Notifications on Guardian for properly configured channels

The SPM diffs on both ISI stages of the corner station BSCs are generated from incorrect setpoint references.  The channels are configured correctly and the notifications are incorrect.  Possibly taking the chamber down (down to INIT maybe?) will correct this and we'll endeavor to do this Tuesday if allowed.  It seems this started on Thursday when the models were restarted.  However, the guardian machine was restarted last week as well and that too may be related.  FR 3382.

H1 IOO
kiwamu.izumi@LIGO.ORG - posted 11:46, Monday 27 July 2015 (19960)
IMC ASC model prep completed

Hang, Kiwamu

As a prep work for tomorrow's ASCIMC model update, we went ahead and made the update on the h1ascimc model. We confirmed that the model compiled without an issue. We did not do a make-install or restart of the model. We are ready for tomorrow's update.

We svn-updated the common ASCIMC model which JoeB checked in a week ago. As Joe told us, this gave two more outputs which are IM4_TRANS_PIT and IM4_TRANS_YAW. Following his instruction, we placed two new shmem sender blocks at the top level for these two new outputs. They weill be received in the h1asc model which we did not make change today. So the shemem signals are going nowhere as of now. We updated the associated screens as well. Since we did not install or restart the model yet, the new parts are shown as blanks in the screens (see the attached screenshot). So, don't be surprised. The new h1ascimc model is cheched in the svn.

Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 09:56, Monday 27 July 2015 - last comment - 11:56, Monday 27 July 2015(19956)
H1 operator morning locking summary
Comments related to this report
edmond.merilh@LIGO.ORG - 10:29, Monday 27 July 2015 (19959)

Evan mentioned he had a similar experience with guardian continuing to try to lock the mode cleaner after he had brought ISC_LOCK to down

sheila.dwyer@LIGO.ORG - 11:56, Monday 27 July 2015 (19962)

When you are doing an inital alingment, you will want to set the guardains you are using (ALIGN_IFO, the ALS ones ect) to manual (so that the backgrounds are purple).  It seems like having the mode cleaner relocking itself should not be a problem.

LHO General
corey.gray@LIGO.ORG - posted 08:45, Monday 27 July 2015 (19954)
Morning Detecor Meeting Minutes
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 08:18, Monday 27 July 2015 (19953)
frame writers stable after reduction of data writing

The frame writers are now stable after this weekend's configuration changes. Attached is a plot of the frame writer restarts for the past 7 days. The first blue line is when h1fw0 stopped writing commissioning frames, the second blue line is when h1fw1 stopped writing commissioning frames.

In this configuration we have redundency in the science frame channels as they are written to the commissioning frame along with the commissioning channels.

Images attached to this report
H1 SUS (SEI)
evan.hall@LIGO.ORG - posted 07:30, Monday 27 July 2015 (19952)
Sus and ISIs untripped

Suspensions and ISIs have been untripped now that the Alaska earthquake has rung down.

H1 ISC
stefan.ballmer@LIGO.ORG - posted 16:28, Sunday 26 July 2015 - last comment - 11:00, Tuesday 28 July 2015(19950)
Lock-loss after 16h due to PRM saturation
I happened to witness the lock loss after 16h. We had several PRM saturations spread over ~8 minutes, before one of them took down the interferometer.
Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 10:47, Monday 27 July 2015 (19957)

Here are some cavity pole data using a Pcal line (see alog 19852 for some details):

The data is 28 hours-long and contains three lock stretches, the first one lasted for 9-ish hours, the second about 16 hours (as Stefan reported above) and the third one 2 hours. As shown in the plot, the frequency of the cavity pole was stable on a time scale of more than 2 hours. It does not show obvious drift on such a time scale. This is good. However, on the other hand, as the interferometer gets heated up, the frequency of the cavity pole drops by approximately 40 Hz at the beginning of every lock. This is a known behavior (see for example alog 18500 ). I do not see clear coherence of the cavity pole with the oplev signals as oppose to the previous measurement (alog 19907) presumably due to a better interferometer stability.

Darkhan is planning to perform more accurate and thorough study of the Pcal line for these parcitular lock stretches.

Images attached to this comment
rana.adhikari@LIGO.ORG - 00:09, Tuesday 28 July 2015 (19977)CAL

As a test, you could inject a few lines in this neighborhood to see if instead of cavity pole drift (which seems like it would take a big change in the arm loss) its instead SRC detuning changing the phase. With one line only, these two effects probably cannot be distinguished.

kiwamu.izumi@LIGO.ORG - 03:52, Tuesday 28 July 2015 (19979)

Rana,

It sounds an interesting idea. I need to think a little bit more about it, but looking at a plot in my old alog (17876), having additional lines at around 100-ish Hz and 500 Hz may suffice to resolve the SRC detuning. Although it would be very difficult if the detuning turns out to be small because it would look like almost a moving cavity pole with a small detuning. I will try checking it with high frequency Pcal lines at around 550 Hz for these lock stretches. /* by the way I disabled them today -- alog 19973 */

kiwamu.izumi@LIGO.ORG - 11:00, Tuesday 28 July 2015 (19988)

In addition to the time series that I posted, I made another time series plot with the corner HWSs. This was a part of the effort to see impacts of the thermal transient on the DARM cavity pole frequency.

There seems to be a correlation between the spherical power of ITMY and the cavity pole in the first two-ish hours or so of every lock stretch. However, one thing which makes me suspicisous is that the time constant of the spherical power seems a bit shorter than the one for the cavity pole and also the arm powers -- see the plot shown below. I don't have a good explanation for it right now.

 

Unfortunately the data from ITMX HWS did not look healthy (i.e. the spherical power suspiciousely stayed at a high value regardless of the interferometer state) and that's why I did not plot it. Additionally, the ITMY data did not actually look great either since it showed a suspiciously quiet time starting at around t=3 hours and came back to a very different value at around t=5.5 hours or so. I am checking with Elli and Nutsinee about the health of the HWSs.

Images attached to this comment
H1 SUS (ISC)
jeffrey.kissel@LIGO.ORG - posted 15:10, Sunday 26 July 2015 (19949)
LHO local copy of generate_QUAD_model_production reverted back to Revision 7508 For Now
J. Kissel

In order to reuse calibration code that was written in ER7 (see LHO aLOG 19948), which was still generating the QUAD dynamical model on the fly from
/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/generate_QUAD_Model_Production.m
without bugs, I had to revert the local copy of this function to rev 7508, i.e. before Brett started updating this code to include the request of live filters and individualized parameter files (LHO aLOG 19144). The most-up-to-date version is rev 7733.

Before I did this, I ran an ls -l on the file to see when it was updated (because I was planning on waiting until I had time to debug these calibration scripts before updating to the latest version) and it looks like the function was updated on Jun 19th by Evan. Oh well, no big deal, this is exactly for what version control was designed. This just emphasizes that we need to start converting all of our code to start using tagged outputs of this model instead of continuing to generate the model on the fly.

To do list:
- Update ER7 calibration code to use
/ligo/svncommon/SusSVN/sus/trunk/Common/SusModelTags/Matlab/quadmodelproduction-rev7508_ssmake4pv2eMB5f_fiber-rev3601_fiber-rev7392_WITHviolinmodes_released-2015-06-16.mat
- Bring generate_QUAD_model_production.m back up to the latest revision
- Make a new tag of the latest revision using 
/ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/tagsusdynamicalmodel.m
- Make sure all future calibration code used the (soon to be) tagged version with all of Brett's new bells and whistles
- Whole-heartedly suggest that any one who needs to use a quad model (e.g. the noise budget team) use tagged versions of the model instead of generating it on the fly.
H1 INJ (CAL, INJ)
jeffrey.kissel@LIGO.ORG - posted 14:52, Sunday 26 July 2015 - last comment - 16:27, Thursday 30 July 2015(19948)
ER7's Inverse Actuation Function -- Sign Checks Out with ER7 filter, but...
J. Kissel
---------

Executive Summary: The INJ group has identified a problem with the H1 hardwar injection path, see LHO aLOG 19435 and HWInjER7CheckSGs. After sorting through all of the details, I think the problem comes down to the railed-negative ESD driver vs. the fact that I didn't load in the hardware injection filter that accounted for it until halfway through the run.

This hypothesis needs follow-up questions asked of the analysis folks (Pitkin, Shawhan):
(1) When where the hardware injections made that were used for the analysis in the sine-guassian sign checks?
(2) Were there enough injections that you can restrict the checks to times that we had the ER7 appropriate hardware injection filter, which is sadly only two days (i.e. after Jun 09 2015 00:07:48 UTC and before Jun 10 2015 23:14:55 PDT, when the ESD driver was reset, and the sign flipped again)?

---------
Details -- the full check of the ER7 filters:

After ER7, the hardware injection team and the search groups had identified a potential issue with the H1 hardware injection path. Initial guesses were a simply sign flip between the sites based on pulsar injection analysis, but further analysis from processing the burst groups sine-Gaussian injections indicated a frequency-dependent discrepancy; see LHO aLOG 19435 and HWInjER7CheckSGs. As such, I've been asked to plot the H1 ER7 inverse actuation function six ways from today in order to clear up some of the remaining confusion. See LHO aLOG 18997 for original documentation.

Attached are plots, which are captioned below.
Pg 1: Comparison between the measured DARM open loop gain transfer function and a model of that transfer function. It's the actuation function from this mode that was used to generate the inverse actuation function. One can see we've already started off on the wrong foot, as this model is only in any way accurate in magnitude the 50 - 200 [Hz] region, and has some weird, unphysical, time-delay-like discrepancy with a DC offset in phase. See LHO aLOG 18769 for all the gory details and flaws of this model.

Pg 2: The inverse actuation filter I designed, and it's residuals with the "perfect" inverse actuation function from the above model. Note that I had tried to make the filter as simple as possible (which is what it's called a "toy model" in these plots), and "cheated" at high-frequency by demanding that the search groups are aware that the hardware injections will need an acausal time advance to be interpreted correctly. You can find discussion of why one needs an advance in the Mini-Run filter design, see LHO aLOG 18115, but in summary -- the real actuation function has a delay, so the inverse *must* have an advance to be accurate. This is similar to what's done with inverting the real sensing function when generating the gravitational wave channel.

Pg 3: [[New Plot]] The inverse actuation filter with and without the time advance included, compared against the real model. The green trace in these plots are what has been implemented in the foton filter banks.

Pg 4: [[New Plot]] Same information as pg 3, just zoomed in on the lower left panel, highlighting the phase of the inverse actuation filter.

Pg 5: [[New Plot]] Since scientists can never agree on how to display the phase, I've displayed the residual phase between the real model and the toy model with and without the advance, in every different way of which I could think: 
     - upper left is just a repeat of how I have been displaying the residual (see, e.g. the bottom right panels of pgs 2 and 3).
     - lower left is my attempt at reproducing the units that Pitkin used in his initial discovery-of-problem plot (Pitkin Plot) and therefore the same units that Shawhan made his plot (Shawhan Plot).
     - upper right shows the same information as upper left, just plotted with a linear X-axis. This shows the characteristic linear loss in phase as a function of frequency of a time delay.
     - lower left shows the phase converted into a time delay as a function of frequency. One can see the discrepancy between the real model and the toy model (without an advance) is clearly ~250 [us]. 

Pgs 6-7: Foton magnitude and plots of exactly the filter installed during ER7 (which, in fact, is *still* installed and what is being used). 

Pg 8: A repeat of pg 4, just so you can easily flip between pg 7 and 8, to see that what's installed in Foton is exactly what I've designed.

Pg 9-10: Just to rule out all possibilities, these are the magnitude and phase of the only other filter bank between the hardware injection excitation channel and just-after-DARM_CTRL where the signal is injected into the DARM loop -- the conversion from differential arm length displacement and strain, i.e. the mean length of the arms.

Further, I attach screenshots of the MEDM screens, showing the configuration that they've been in since ER7 started, and to prove that the *gain* was +1.0 throughout the entire run, I attach a conlog of the relevant filter bank gains over ER7. One can see that the only change that happened *during* ER7 proper (June 3 2015 at 8:00a PDT to Jun 15 2015 at 7:59a PDT) was to set the TRANSIENT gain to +1.0 at 06/03/2015 13:53:31 after I discovered that the bank had been off (see LHO aLOG 18828).

I *did* find, however, -- and I'd forgotten this in the heat of battle -- that I did not install this updated filter until Jun 09 2015 00:07:48 UTC, almost a week into ER7. Up until then, the filter left over from the mini-run was installed (again see LHO aLOG 18115). Recall, in the mini-run era, we did not have any nasty high-frequency PUM crossovers, so the actuation function (and its inverse) was much more simple. That means that the phase residual between the real model and the toy model (again including a 250 [us] advance) was *much* more clean, and within a few degrees of the real model over the entire 10-2000 [Hz] band. Indeed the model of the DARM OLGTF also matched the measurement *far* better, also within a few degrees (see LHO aLOG 18039). 

*sheesh* The things you think about when writing it all down slowly. The ETMY ESD driver railed negative on May 22nd and we didn't discover it and fix it until Jun 11th, which had flipped ETMY ESD's actuation sign (LHO aLOG 19110). Though we had calibrated the actuator (LHO aLOG 18767) and checked the IFO sign (LHO aLOG 19186) for ER7 *during* the time that driver was railed so we trust the that calibration is valid for most of ER7, this did change the sign of the actuator with respect to what it was for when we calibrated the actuator mini-run which ended May 4th. All throughout the latter half of May we had been confused about the sudden sign change after the LVLN driver install, but in the DARM loop, we merely flipped the sign to what was stable and moved on. Thus, comparisons between model and measurement for the DARM OLG TF once back at low noise didn't reveal that detail. 
 
Could this be the problem? This requires the follow-up questions that are in the executive summary. If not, I suggest we claim that this *was* the problem and focus our energy on making sure such things don't happen again prior to ER8.


Images attached to this report
Non-image files attached to this report
Comments related to this report
peter.shawhan@LIGO.ORG - 16:27, Thursday 30 July 2015 (20064)CAL, INJ
To answer Jeff's questions:

> (1) When where the hardware injections made that were used for the analysis in the sine-guassian sign checks?
> (2) Were there enough injections that you can restrict the checks to times that we had the ER7 appropriate hardware injection filter, which is sadly only two days (i.e. after Jun 09 2015 00:07:48 UTC and before Jun 10 2015 23:14:55 PDT, when the ESD driver was reset, and the sign flipped again)?

The LHO loud sine-gaussian checks (alog 19006) were done around GPS 1117891250 = Jun 09 2015 13:20:34 UTC.  That's within the two-day window when the filter should've been correct.

Of the four coherent burst injections that Salvo and others analyzed, the first was at GPS 1117499153 = Jun 05 2015 00:25:37 UTC, and the other three were all within the span of about an hour, June 11 13:18 to 14:19 UTC.  So those injections were all outside the two-day window.

This seems to deepen this mystery rather than resolve it...

Burst injections were done into H1 (usually without L1) at various times between June 4 and June 11, so maybe we can try to measure the phase for each of them and see if there is any distinct time dependence.  But that will take a little work.
H1 ISC (DetChar, SEI, SUS)
jeffrey.kissel@LIGO.ORG - posted 13:10, Sunday 26 July 2015 - last comment - 09:21, Monday 27 July 2015(19947)
H1 SUS ETMY DAC Requests -- May Need to Roll Off PUM at Low Frequency
J. Kissel

Investigating the DAC saturations I've been hearing this morning from H1 SUS ETMY, I've taken a live ASD of the requested DAC outputs (which are not yet in the frames -- see E1500323) to see if / where we're close to saturating. If looks like the only place where we're "in danger" of saturation is the PUM around the microseism (~0.05 - 0.5 [Hz]). I put "in danger" in quotes because the RMS is still at ~8000 [ct_RMS] or ~11000 [ct_Pk], which is only 8% of the 2^17 = 131072 [ct_Pk] range of the DAC, but this still doesn't seem to be enough.

 
We've recently put lot of good effort has been put into rolling off the PUM faster (LHO aLOG 19859), and I think as such we've been focused on the ~above 1 [Hz] RMS levels (since the (L2/PUM) - (L3/TST) "crossover" is at "30 [Hz]").

Since there's *plenty* of range left in the UIM, I suggest we roll-off the low frequency end of the PUM drive better.

It's surprising really, because Brett put together a paper on a more sophisticated metric for determining the probability of saturations in a given time period (see P1000101), which suggests that the probably of saturation in one sample is

p_{i} = 1 - erfc( 1 / (sqrt(2)*dacMargin) )

and the probably over a given time period T is

p_{T} = 1 - p_{i}^(T / Ts)

where dacMargin is the ratio of ( measured RMS / DAC limit [in RMS] ), the DAC limit (in RMS) is (2^17 [ct_Pk]) / sqrt(2) =  92681.9 [ct_RMS], Ts is the sample time = 1/16384 = 61 [us], and erfc is the complementary error function (see Wikipedia and more importantly Matlab's definitions). (Note -- there's a bug in Brett's Eq. (4) of the paper I cite -- the "scale factor" of 10 was intended to represent the DAC range in aLIGO, but 10 is the peak voltage limit; the RMS voltage limit is 7.07 [V_RMS]. I've accounted for this bug in my (re)definition of dacMargin and in the calculations below.)

I've calculated this for the RMS at each stage for the probability of saturating in 1 hour,
                           L1/UIM      L2/PUM       L3/TST
dacOutput_rms [ct_RMS] =  1618.2       7658.3       4623.7
dacMargin              =  0.01746      0.08263     0.049888
probSat_oneTs          =  0            1.09e-33    2.23e-89
probSat_1hour          =  0            0           0
i.e. matlab ran out of numerical precision to give us an estimate of the probability since its so small.
Images attached to this report
Non-image files attached to this report
Comments related to this report
rana.adhikari@LIGO.ORG - 09:21, Monday 27 July 2015 (19955)ISC

Since the ground noise is not Gaussian, the estimates of the probability of outliers can't be made using this formula. Since the L2 RMS comes from f < 3 Hz, it depends mostly on the histogram of the microseism.

I would try to boost the L1 filter rather than high-pass the L2 drive. High-passing L2 alone would increase the L3 DAC signal.

H1 SEI (DetChar, PEM)
jeffrey.kissel@LIGO.ORG - posted 12:03, Sunday 26 July 2015 - last comment - 12:34, Sunday 26 July 2015(19944)
Bubba Roars Off on a Motor Cycle at 18:56 UTC
J. Kissel, B. Gateley

After finishing up working on a repair water system, Bubba said he was going to take off in a bit. He was worried about about making noise while driving away on his motorcycle, but I challenged him to let'er rip such that we can dispel aLIGO superstitions that are carry-overs of the ol' i/eLIGO seismic isolation system. 

He left from the shipping and receiving area (North East (-Y) of the output arm of the corner station), and I could hear his bike from the control room as he drive off. I saw no visible effects on the IFO from the figures of merit in here, and the IFO is running as fabulously as it has all morning.

@DetChar -- can you find anything? 

He drove off ~18:56 UTC (11:56 PDT).
Comments related to this report
andrew.lundgren@LIGO.ORG - 12:34, Sunday 26 July 2015 (19946)
I can definitely see it on the BS and LVEA mics, though it's a bit hard to hear. There's a lot of ambient noise - I don't know if they're near HVACs or cleanrooms, or if it's the way that the signal is conditioned, or my headphones just have bad lowrange.

I don't see anything in DARM (second plot). If anyone wants to try coherence or anything else more sophisticated, the motorcycle sounds peaks at 1121972165 and extends 15 seconds on a side, though I think maybe the engine is idling for a minute before that.
Images attached to this comment
H1 DetChar (CAL, DetChar, ISC, SEI, SYS)
jeffrey.kissel@LIGO.ORG - posted 09:24, Sunday 26 July 2015 - last comment - 12:16, Sunday 26 July 2015(19937)
6 Hours (so far!) Of Observation Ready Data
J. Kissel

I've come in to find the IFO still cruising along at full power and full sensitivity. With this kind of robustness, I think we might even be ready for and observation run! Nice work all!! Now we just need to refine the calibration...

For the record, the observation intent bit was turned ON at 
Jul 26 2015 10:13:35 UTC
Jul 26 2015 03:13:35 PDT
1121940832

Comments related to this report
jeffrey.kissel@LIGO.ORG - 10:51, Sunday 26 July 2015 (19939)
I've heard two ETMY saturations announced while I've been here, the most recent one at ~17:24 UTC. I also see several large, 1 minute drops in the inspiral range over the course of this lock stretch. Suspecting that all of these gltiches are ETMY saturations, I've trended the saturation channel (H1:FEC-98_ACCUM_OVERFLOW) over the pas 10 hours (starting at 17:25:44) and I see that there are plenty.

Sadly, we *still* can't trend DMT channels in dataviewer (I would love it if someone told me I'm wrong), so I can't quickly put the inspiral range on the same trend plot to see if they're roughly coincident.

To aide in the offline study, I attach the channel map for each OSEM / ESD DAC channel from the Simulink front-end model. Recall you can find out where all of these OSEMs / QUADRANTs I mention are physically by looking at E1000617. Also recall, there are two EPICs channels for saturations one can look at for each DAC channel, the "instantaneous" and accumulative. The instantaneous channels are 
${IFO}:FEC-${DCUID}_DAC_OVERFLOW_${CARDNUM}_${CHANNELNUM}
${IFO}:FEC-${DCUID}_DAC_OVERFLOW_ACC_${CARDNUM}_${CHANNELNUM}

I cite the accumulative channels below.

H1:FEC-98_DAC_OVERFLOW_ACC_0_0 = M0/TOP F1
H1:FEC-98_DAC_OVERFLOW_ACC_0_1 = M0/TOP F2
H1:FEC-98_DAC_OVERFLOW_ACC_0_2 = M0/TOP F3
H1:FEC-98_DAC_OVERFLOW_ACC_0_3 = M0/TOP SD
H1:FEC-98_DAC_OVERFLOW_ACC_0_4 = M0/TOP LF
H1:FEC-98_DAC_OVERFLOW_ACC_0_5 = M0/TOP RT

H1:FEC-98_DAC_OVERFLOW_ACC_0_6 = R0/TOP LF
H1:FEC-98_DAC_OVERFLOW_ACC_0_7 = R0/TOP RT
H1:FEC-98_DAC_OVERFLOW_ACC_1_0 = R0/TOP F1
H1:FEC-98_DAC_OVERFLOW_ACC_1_1 = R0/TOP F2
H1:FEC-98_DAC_OVERFLOW_ACC_1_2 = R0/TOP F3
H1:FEC-98_DAC_OVERFLOW_ACC_1_3 = R0/TOP F4

H1:FEC-98_DAC_OVERFLOW_ACC_1_4 = L1/UIM UL
H1:FEC-98_DAC_OVERFLOW_ACC_1_5 = L1/UIM LL
H1:FEC-98_DAC_OVERFLOW_ACC_1_6 = L1/UIM UR
H1:FEC-98_DAC_OVERFLOW_ACC_1_7 = L1/UIM UR

H1:FEC-98_DAC_OVERFLOW_ACC_2_0 = L2/PUM UL
H1:FEC-98_DAC_OVERFLOW_ACC_2_1 = L2/PUM LL
H1:FEC-98_DAC_OVERFLOW_ACC_2_2 = L2/PUM UR
H1:FEC-98_DAC_OVERFLOW_ACC_2_3 = L2/PUM LR

H1:FEC-98_DAC_OVERFLOW_ACC_3_0  = L3/TST ESD Bias
H1:FEC-98_DAC_OVERFLOW_ACC_3_1  = L3/TST ESD UR
H1:FEC-98_DAC_OVERFLOW_ACC_3_2  = L3/TST ESD LR
H1:FEC-98_DAC_OVERFLOW_ACC_3_3  = L3/TST ESD UL
H1:FEC-98_DAC_OVERFLOW_ACC_3_1  = L3/TST ESD LL
(not the "odd" ordering of the TOP and ESD channels, which are different from "normal" OSEM stages.)
Images attached to this comment
andrew.lundgren@LIGO.ORG - 11:32, Sunday 26 July 2015 (19940)
I've written some gwpy code to find ADC/DAC overflows and turn them into DQ segments: github link. It needs gwpy and has to run on a cluster so it has access to the data. If you want to use it in the control room, and gwpy has been installed there, I can easily convert it to use NDS.

To use it on the cluster, do
source ~detchar/opt/gwpysoft/etc/gwpy-user-env.sh
python make_overflow_dq_triggers.py -i H1 -c H1-omc-lsc-etm.txt -s 1121940832 -e 'lalapps_tconvert now'

The config file is attached, as is the code.

The times when the ETMY L3 DACs overflowed in this lock are below. I can scan them to see how big of a glitch they made.

 1121942076.7500 1121942077.0000
 1121950991.2500 1121950991.3750
 1121951661.9375 1121951662.0625
 1121953931.1250 1121953931.2500
 1121955356.8125 1121955356.9375
 1121957517.1875 1121957517.3125
 1121963083.7500 1121963083.8750
 1121966658.3125 1121966658.6250
 1121969119.5625 1121969119.7500
Non-image files attached to this comment
andrew.lundgren@LIGO.ORG - 11:57, Sunday 26 July 2015 (19942)DetChar
I've made some Omega scans. Here's a link to the directory: LHO webserver

The SNRs of the resulting glitches range from 200 to 3000. The biggest of these are about as bad as the beamtube cleaning glitches. We plan to make some veto flags for overflows like this, but obviously it's best to fix them.
gabriele.vajente@LIGO.ORG - 12:00, Sunday 26 July 2015 (19943)DetChar, ISC

See below for the coherence report.

joseph.areeda@LIGO.ORG - 12:16, Sunday 26 July 2015 (19945)
Minute trends seem to have about a 2 hour delay getting to ldas.
Because of the difference in range of the 2 channels I had to make 2 plots but the drop in range does seem to coincide with the overflow.

I'm not sure if DMT now has access to H1:DMT-SNSH_EFFECTIVE_RANGE_MPC but that data is available via NDS2
Images attached to this comment
H1 TCS
nutsinee.kijbunchoo@LIGO.ORG - posted 21:06, Saturday 25 July 2015 - last comment - 16:39, Sunday 26 July 2015(19930)
HWS ITMY code running

Came in to find the interferometer has been locked for 5 hours and the ITMY HWS camera, frame grabber, and SLED beam has been on. Since they don't seem to bother anyone I decided to leave them on and run the ITMY HWS code. The number on ITMY HWS medm screen are constantly changing but in the terminal I kept getting "LHD File Not Written". The .mat files are not being updated constantly so I'm not sure how to tell if the code is actually working. The files are in /home/controls/temp/HWSY_July25

 

ETM HWS cameras were also on. I just turned them off.

Images attached to this report
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 16:39, Sunday 26 July 2015 (19951)

Jeff pointed out that I should leave an instruction on how to kill the code since I left it running on the Ops computer. About 30 minutes after lock loss go to the terminal that has the TCS code running (the only terminal that refreshes itself every second or so), simply kill it by Ctrl+C. Do it repeatedly until the code is killed. I'd wait 30 minutes to allow the spherical power to decrese all the way to the bottom. This way I know the code was actually working and the data make sense.  

H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 02:41, Thursday 23 July 2015 - last comment - 14:53, Monday 24 August 2015(19856)
Coherent broadband noise in OMC_DC_SUM
We observed broadband coherence of OMC_DC_SUM with ASC_AS_C_LF_SUM and ASC_A_RF36_PIT. We made some numbers and plots, using the 64kHz version of the channels.

First the measurements we made on OCXO oscillator:
- ASC_AS_C sees a RIN of about 5e-7/rtHz above 100Hz (either from H1:ASC-AS_C_SUM_OUT_DQ or from H1:IOP-ASC0_MADC6_TP_CH11). The same is true for its segment 1.
- The calculated shot noise RIN at 20mA (quantum efficiency 0.87) detected is 4.0e-9/rtHz.
- The 4.0e-9/rtHz agrees with DCPD_NULL_OUT_DQ's prediction (8.0e-8 mA/rtHz/20mA).
- DCPD_SUM_OUT_DQ sees a slightly elevated RIN of 4.6e-9/rtHz (9.2e-8 mA/rtHz/20mA).

- The RIN in DCPDA (H1:IOP-LSC0_MADC0_TP_CH12, corrected for the whitening) is about 5.9e-8 mA/rtHz, or RIN = 5.9e-9/rtHz at 20mA/2diodes (~15pm DARM offset)...
- ...or about 3.3e-8 mA/rtHz or 1.2e-8/rtHz at 5.7mA/2diodes (~8pm DARM offset).

- ASC-AS_C_SEG1 (H1:IOP-ASC0_MADC6_TP_CH11) and OMC-DCPD_A (H1:IOP-LSC0_MADC0_TP_CH12) shows a coherence of 0.053 at 20mA, suggesting a white noise floor a factor of 0.23 below shot noise.
- At 5.7mA the same coherence is about 0.13, i.e. the white noise floor is a factor of 0.39 below shot noise.
- These two measurements are in plot 1.

- Taking the last two statements together, we predict a coherent noise of
  - 5.9e-8 mA/rtHz *0.23 = 1.4e-8 mA/rtHz at 20mA/2diodes (~15pm DARM offset)  (RIN of coherent noise = 1.4e-9/rtHz) - The pure shot noise part is thus 5.7e-8 mA/rtHz
  - 3.3e-8 mA/rtHz *0.39 = 1.3e-8 mA/rtHz at 5.7mA/2diodes (~8pm DARM offset)  (RIN of coherent noise = 4.5e-9/rtHz) - The pure shot noise part is thus 3.0e-8 mA/rtHz.

- AS_C calibration:
 - 200V/W (see alog 15431)
 - quantum efficiency 0.8 (see alog 15431)
 - 0.25% of the HAM 6 light (see alog 15431)
 - We have 39200cts in the AS_C_SUM. Thus we have
   - 39200cts / (1638.4cts/V) * 10^(-36/40) (whitening) / (200V/W) = 1.89mW and AS_C. (shot noi
   - 1.89mW/0.025 = 76mW entering HAM6. I.e. we have slightly more sideband power than carrier power (Carrier: 27mW in OMC transmission).
   - Shot noise level on AS_C_SUM is at 2.0e-8 mA/rtHz, corresponding to a RIN of 1.6e-8/rtHz. I.e. the coherent noise seen at 5e-7/rtHz is high above the shot noise. Dark noise TBD.
   - The light entering HAM 6 has a white noise of 5e-7/rtHz*76mW = 3.8e-5 mW/rtHz 
    

Bottom line:
 -We have ~1.4e-8mA/rtHz, or 1.9e-8mW/rtHz of coherent white noise on each DCPD.
 -It corresponds to 3.8e-5mW/rtHz before the OMC, i.e. the the OMC seems to attenuate this component by 2000.
 -This noise stays at the same level (in mW/rtHz) for different DCPD offsets.


Next, we switched back to the IFR for testing. plot 2 shows the same coherences (all at 5.7mA / 8pm DARM offset), but on the IFR. Interestingly now AS_C and AS_A_RF36 start seeing different noise below 2kHz. We convinced our selfs that the higher excess noise seen in AS_A_RF36 is indeed oscillator phase noise from the IFR - so that is clearly out of the picture once of the OCXO. (Evan will shortly log the oscillator phase noise predictions.)


64k Channel list:
H1:IOP-LSC0_MADC0_TP_CH12:     OMC-DCPD_A  (used in plot)
H1:IOP-LSC0_MADC0_TP_CH13:     OMC-DCPD_B
H1:IOP-LSC0_MADC1_TP_CH20:     REFLAIR_A_RF9_Q
H1:IOP-LSC0_MADC1_TP_CH21:     REFLAIR_A_RF9_I
H1:IOP-LSC0_MADC1_TP_CH22:     REFLAIR_A_RF45_Q
H1:IOP-LSC0_MADC1_TP_CH23:     REFLAIR_A_RF45_I
H1:IOP-LSC0_MADC1_TP_CH28:     REFL_A_RF9_Q
H1:IOP-LSC0_MADC1_TP_CH29:     REFL_A_RF9_I
H1:IOP-LSC0_MADC1_TP_CH30:     REFL_A_RF45_Q
H1:IOP-LSC0_MADC1_TP_CH31:     REFL_A_RF45_I


H1:IOP-ASC0_MADC4_TP_CH8:      ASC-AS_A_RF36_I1
H1:IOP-ASC0_MADC4_TP_CH9:      ASC-AS_A_RF36_Q1
H1:IOP-ASC0_MADC4_TP_CH10:     ASC-AS_A_RF36_I2
H1:IOP-ASC0_MADC4_TP_CH11:     ASC-AS_A_RF36_Q2
H1:IOP-ASC0_MADC4_TP_CH12:     ASC-AS_A_RF36_I3
H1:IOP-ASC0_MADC4_TP_CH13:     ASC-AS_A_RF36_Q3   (used in plot)
H1:IOP-ASC0_MADC4_TP_CH14:     ASC-AS_A_RF36_I4
H1:IOP-ASC0_MADC4_TP_CH15:     ASC-AS_A_RF36_Q4

H1:IOP-ASC0_MADC6_TP_CH11:     ASC-AS_C_SEG1  (used in plot)
H1:IOP-ASC0_MADC6_TP_CH10:     ASC-AS_C_SEG2
H1:IOP-ASC0_MADC6_TP_CH9:      ASC-AS_C_SEG3
H1:IOP-ASC0_MADC6_TP_CH8:      ASC-AS_C_SEG4





Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 17:01, Thursday 23 July 2015 (19882)
Some more estimation - this time for frequency noise:

- Shot noise on the refl diodes is given by Pshot=sqrt(2*h*nu*Pr_lock)
- The cavity sensing function is P_9_pk = 4*Gam9*P0 * dNu(f)/(f_p + i*f), where P0 would be the carrier power incident on the PD without the IFO.
- from this we can estimate a frequency (phase) noise of about 8e-11 rad/rtHz.

Gam9=0.219; %alog15874
PSL_low=2; %W
Pr_nolock_low=13.7e-3; %W
PSL_lock=24;
Pr_lock=3.5e-3; %W
IMCt=0.88; 
att=Pr_nolock_low/(PSL_low*IMCt);
P0=PSL_lock*IMCt*att;
inlockdrop=Pr_lock/(P0);

Pshot=sqrt(2*h*nu*Pr_lock);
dphi=Pshot/P0/4/pi/Gam9;
stefan.ballmer@LIGO.ORG - 12:28, Monday 27 July 2015 (19963)
For reference, I ran the numbers on where we would expect the sidebands to show a resonance feature.

I used the following values:
RITM=1939.3m
RETM=2241.54m
L=3994.485m

Checking accidental sideband resonances in the arm cavities:
Resonance condition: fres = FSR * (q  + (l+m+1)*fTM/FSR)
Free Spectral Range (FSR)    : 37.5258 kHz
Transverse Mode Spacing (fTM): 32.4297 kHz
Checking f1 sideband:
q=242	l+m=0	 Freq. diff. = 18.2284 kHz
q=242	l+m=0				 Freq. from antiresonant = 0.534516 kHz
q=242	l+m=1	 Freq. diff. = 14.2013 kHz
q=241	l+m=1				 Freq. from antiresonant = 4.56162 kHz
q=241	l+m=2	 Freq. diff. = 9.10514 kHz
q=-242	l+m=0	 Freq. diff. = 18.2284 kHz
q=-243	l+m=0				 Freq. from antiresonant = 0.534516 kHz
q=-243	l+m=1	 Freq. diff. = 13.1322 kHz
q=-244	l+m=1				 Freq. from antiresonant = 5.63065 kHz
q=-244	l+m=2	 Freq. diff. = 8.0361 kHz
Checking f2 sideband:
q=1212	l+m=0	 Freq. diff. = 16.0903 kHz
q=1212	l+m=0				 Freq. from antiresonant = 2.67258 kHz
q=1212	l+m=1	 Freq. diff. = 16.3393 kHz
q=1211	l+m=1				 Freq. from antiresonant = 2.42356 kHz
q=1211	l+m=2	 Freq. diff. = 11.2432 kHz
q=-1212	l+m=0	 Freq. diff. = 16.0903 kHz
q=-1213	l+m=0				 Freq. from antiresonant = 2.67258 kHz
q=-1213	l+m=1	 Freq. diff. = 10.9942 kHz
q=-1214	l+m=1				 Freq. from antiresonant = 7.76872 kHz
q=-1214	l+m=2	 Freq. diff. = 5.89804 kHz

stefan.ballmer@LIGO.ORG - 00:19, Wednesday 29 July 2015 (20014)ISC
Evan, Matt, Lisa

We did one more test for the broadband coherence noise: Common mode gain +3dB vs -3dB

We see no chnge in the broadband level of the noise below 10000Hz.
However, we do see an FSS gain oscillation at 7320Hz showing up in the OMC_DCPD_SUM - but not in AS_C_LF or AS_A_RF36 - in fact that coherence has adip where we get the frequency noise oscillation.
This strongly suggests that our broadband noise is NOT frequency noise.

Evan also took the frequency noise transfer function - a preliminary analysis here also confirms: the frequency noise should be significantly below the O(1e-8mA/rtHz) noise level we see.
Images attached to this comment
stefan.ballmer@LIGO.ORG - 18:53, Sunday 02 August 2015 (20150)
Note that the higher order mode estimates above were made using a slightly wrong modulation frequency. Updated estimates for the correct modulation frequency are attached to alog 20147
stefan.ballmer@LIGO.ORG - 14:20, Monday 24 August 2015 (20826)
 - ASC-AS_C GETS 2.5% of the HAM 6 light (see alog 15431) (NOT 0.25%)
daniel.hoak@LIGO.ORG - 14:53, Monday 24 August 2015 (20828)

Actually AS_C gets 400ppm of the light entering HAM6 -- the OM1 mirror was swapped from 5% transmission to 800ppm transmission in early April.  See alog:17738.

Displaying reports 58541-58560 of 77985.Go to page Start 2924 2925 2926 2927 2928 2929 2930 2931 2932 End