Displaying reports 60301-60320 of 84759.Go to page Start 3012 3013 3014 3015 3016 3017 3018 3019 3020 End
Reports until 18:20, Friday 22 January 2016
X1 DTS (CDS, DAQ)
james.batch@LIGO.ORG - posted 18:20, Friday 22 January 2016 (25112)
Rearrange file server exports
Reconfigure x1fs0 to export individual directories under /opt, rearrange nfs mounts for front ends, x1boot, and x1 DAQ computers.  This is to test proposed changes for the h1 system.
LHO General
patrick.thomas@LIGO.ORG - posted 16:09, Friday 22 January 2016 (25111)
Ops Day Shift Summary
SHIFT SUMMARY: Some locking success in the morning, but trouble in the afternoon with high winds and microseism. Jim W. tried putting the end stations on Quite_90 and enabling sensor correction. Ed took over locking attempts in the mid afternoon. The winds have come back down.

ACTIVITY LOG:
19:59 UTC Jeff B. and Nicole W. to LVEA to look at 3IFO baffles
20:06 UTC Stopping locking attempts while Jim W. runs transfer functions on ETMX
20:36 UTC Jeff B. and Nicole W. done
20:48 UTC Phone call from Hanford Emergency instructing personnel in 200 West to take cover
21:38 UTC Phone call from Hanford Emergency reporting the lifting of the take cover alarm
21:44 UTC Dick G. to optics lab
21:45 UTC Resuming locking attempts. Jim W. has put the end stations on Quite_90 and turned on sensor correction.
23:35 UTC Gerardo to mid X to retrieve empty tote
23:54 UTC Filiberto to mid X to check alarm on fire panel

Tour group in the control room around 19:50 UTC
Dave B. changed the vacuum overview medm on video1
H1 CDS (OpsInfo)
thomas.shaffer@LIGO.ORG - posted 16:07, Friday 22 January 2016 (25110)
Fixed Bug in Verbal and Saturations now just say optic name

Fixed bug: Previously, when Verbal could not connect to a channel through ezca, it would crash with an EzcaConnectError. Now it will make a small noise and write a notification that it cannot connect to the channel and repeat. This will begin to get very useful now that we are in the commission era.

Saturations will now just say the optic name.

I also removed the acknowledgement feature for the CW inj. It should still alert if the inj status changes, but operators do not have to acknowledge.

H1 ISC (ISC)
matthew.evans@LIGO.ORG - posted 15:58, Friday 22 January 2016 (25106)
Unidentified Noise with Coating Thermal Noise removed

I included the coating thermal noise (CTN) in the estimate made in entry 25039, and find that this changes little the conclusion.  It seems that the unidentified noise source has a slope close to 1/f.  Increasing the CTN estimate by 1.4 changes the conclusion, in that noise is more like 1/f^2.  I do NOT mean to suggest that this indicates higher CTN; that extra junk could be anything.  What this does mean is that we cannot use H1 to set a better limit than this (yet).

Images attached to this report
Non-image files attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 15:15, Friday 22 January 2016 - last comment - 18:33, Friday 22 January 2016(25109)
Switched EX/EY ISI blends to 45mHz

uSeism is approaching 1um/s and the winds have dies down to below 10mph.

Comments related to this report
edmond.merilh@LIGO.ORG - 18:33, Friday 22 January 2016 (25113)

I hadn't been informed about the sensor correction/Quite_90 situation when I was asked to lock the interferometer upon my arrival. We have ben locking steadily on the 45mHz blends all evening. I've just changed everything back to Quite_90 to have a look. OK, it looks good so far. Apologies, Jim there was a lack of communication.

H1 CDS (VE)
david.barker@LIGO.ORG - posted 14:51, Friday 22 January 2016 - last comment - 19:46, Friday 22 January 2016(25107)
New vacuum controls overview screen

WP5692 FRS4202

John, Kye, Gerardo, Dave:

I have modified the H0 vacuum overview screen to show an alarm border around bar monitor widgets. If the widet has no content, the alarm color is now visible in the border.

Images attached to this report
Comments related to this report
kyle.ryan@LIGO.ORG - 19:46, Friday 22 January 2016 (25116)
 Thanks Dave!

"no content", "no valid content", "value not valid for parameter represented", "something is broken" etc...
H1 SEI
hugh.radkins@LIGO.ORG - posted 14:29, Friday 22 January 2016 - last comment - 14:37, Friday 22 January 2016(25104)
Testing on Senscor Match Filters--leave SDF red unless we are going to observe--then accept, don't revert

Jim's testing some alternate filter on the ETM senscor Match filters for the beam line axis.  Leave the SDF red for SEI reminder of this.  If needing to green sdf for observation mode, please accept rather than reverting the settings on these.  Many thanks, TeamSEI.

Comments related to this report
hugh.radkins@LIGO.ORG - 14:37, Friday 22 January 2016 (25105)

Well, decided to go ahead and accept as the objective is to go to observe tonight.  We'll just have to remember.

LHO General
patrick.thomas@LIGO.ORG - posted 13:29, Friday 22 January 2016 - last comment - 13:40, Friday 22 January 2016(25101)
Hanford notification for 200 West
We received a phone call in the control room at 12:48 PST from Hanford Emergency instructing personnel in 200 West to take cover and close all doors and ventilation. Other personnel are instructed to stay clear.

Richard M. informs me that this does not affect us (other than to stay clear of 200 West).
Comments related to this report
patrick.thomas@LIGO.ORG - 13:40, Friday 22 January 2016 (25103)
We received another phone call in the control room at 13:38 PST informing us that the take cover was due to a false alarm and has been lifted.
H1 PEM (DetChar, PEM)
robert.schofield@LIGO.ORG - posted 11:38, Friday 22 January 2016 (25098)
End-O1 PEM injection report for LHO

Summary: most coupling at LHO was measured to be about the same as for the pre-run injections. Magnetic coupling was found to be lower in the CS ebay, and vibration coupling was found to be lower at the PSL periscope and at EX, as we were expecting. Since changes were for the better, we conservatively use the values from the start of the run and nothing has to change in estimates of noise from the environment. I also injected at locations we didn’t reach during the first round; there is low but interesting acoustic coupling at both mid-stations.

We make an abbreviated set of injections at the end of the run in case coupling changed after the pre-run injections (link to pre-run injection summary: Link). We made at least one magnetic and one acoustic injection in the LVEA, the 3 electronics bays, the two VEAs and the PSL. These were designed to show if any coupling changed significantly, in which case we would investigate using further injections.  For O1 end-of-run injections, all significant changes were improvements, so we change no estimates, and do not alter the coupling functions and estimated ambient levels from the beginning of the run.

In addition, we made several injections that were planned but that we did not get to in the September round. These included shaking of ETMX and Y, and of the beam tube at the mid station.

Vibration coupling at mid-station

The smallest clear aperture in the beam tube between the corner and end stations is associated with the mid-station cryopumps. For this reason, the beam tube is instrumented with accelerometers at the mid-stations. We first injected at the mid-station during the current round of PEM injections because of time limitations during the first round.

Shaker sweeps on the beam tubes revealed several sensitive frequencies, possibly resonances of scattering structures. Figure 1 shows a comb injection at MX with one of the lines centered on a putative resonance. The feature in DARM has the side-band structure that is typically produced by scattering coupling.  The acoustic line at 130 Hz is about 3 orders of magnitude above background, which was also the approximate excitation level needed to produce features in DARM at several other frequencies at MX (250, 315 & 170 Hz) and MY (150 Hz).

While the normal acoustic levels at the mid stations are not a problem, it is not difficult to increase the sound pressure level by 3 orders of magnitude. A loud bang in a mid-station VEA may show in DARM, as might bumping into the beam tube. I suggest that we emphasize that when we are in observation mode, we record in the log when people are working in the VEAs at the mid stations.

Shaking of ETMX and Y

I used piezo shakers mounted on the blue cross beams of the ETM BSCs. This increased the amplitude of motion by about 2 orders of magnitude between about 100 and 1800 Hz. No effect was noted in DARM.

Reduced magnetic coupling in CS electronics bay.

For pre-O1 PEM injections, the only magnetic coupling that would prevent us from reaching our sensitivity goals was magnetic coupling in the corner station electronics bay (Link).  The coupling function was not the highest, but in combination with the high magnetic noise level in the ebay, the pre-O1 coupling would limit us to about 1e-18m/sqrt(Hz) at 12 Hz. However, Figure 2 shows that this coupling was found to be greatly reduced during the post-O1 injections. It is not clear when this improvement was made, but Richard remembered several activities in the ebay that could have improved cable shield connections etc., during the two weeks between when the measurements were made and the start of the run. 

Reduced acoustic coupling at EX.

We expected that the high acoustic coupling measured at EX (Link) would be reduced when the beam diverter was finally closed (Link) on Oct. 6. Post run injections showed that it was indeed reduced by a factor of about 5 in the 50-120 Hz region.

Reduced coupling at PSL

The coupling in the PSL was changed Oct. 13 2015 when I epoxied the top mount on the periscope and fine tuned the peak frequencies using weights. This removed peaks around 300 Hz from DARM (Link). Figure 3 shows the new estimated levels of ambient noise. One peak is very near showing in DARM, but we hope that reductions in jitter coupling, towards the level at LLO, will keep this from limiting us.

Non-image files attached to this report
LHO FMCS
patrick.thomas@LIGO.ORG - posted 11:26, Friday 22 January 2016 - last comment - 11:31, Friday 22 January 2016(25099)
Temperature alarms
There are two channels alarming high for the temperature of the supplied air to the LVEA from air handlers 1 and 2. H0:FMC-CS_LVEA_REHEAT_1B_DEGF and H0:FMC-CS_LVEA_REHEAT_4_DEGF have both exceeded their alarm level of 100 deg F. Trends for the past 7 days are attached. John has been notified.
Non-image files attached to this report
Comments related to this report
patrick.thomas@LIGO.ORG - 11:31, Friday 22 January 2016 (25100)
FRS ticket 4264 opened.
H1 CDS
evan.hall@LIGO.ORG - posted 10:52, Friday 22 January 2016 - last comment - 13:38, Friday 22 January 2016(25096)
Certain elliptic filters crash foton

Sometime between last night and today, foton seems to have become unable to generate certain elliptic filters of high order.

For example: choose elliptic band pass, first frequency 5 Hz, second frequency 500 Hz, fifth order, 1 dB ripple. Foton freezes as soon as you click ok. Same for a sixth-order elliptic bandpass, and a fifth-order elliptic low-pass.

Last night, we were able to generate fifth-order elliptic filters no problem. What happened between then and now?

Comments related to this report
jeffrey.kissel@LIGO.ORG - 13:38, Friday 22 January 2016 (25102)CDS
H1 ISC
gabriele.vajente@LIGO.ORG - posted 22:40, Thursday 21 January 2016 - last comment - 10:58, Friday 22 January 2016(25089)
Diagonalization of MICH driving - step 1

[Sheila, Evan, Gabriele]

The goal is to cancel the PRCL length chane induced by driving MICH using only the BS. For this reason we plan to implement a path from MICH control signal to PR2.

  1. we injected a MICH motion using a differential drive on the two ITMs, and a PRCL motion using a common drive on the two ITMs. The PRCL error signal (POP_9I) sees the common mode about 20 times more than the differential mode. So we conclude that POP-9I sees MICH about a factoir 20 less than PRCL. It's therefore a good reference to disentangle MICH and PRCL in the BS drive
  2. we injected broad band noise in tBS and measured the transfer function to POP_9I. Let's call this transfer function TF_POP_BS. This measures how much PRCL we do when we drive BS
  3. we injected broad band noise in PR2 and measured the transfer function to POP_9I. Let's call this transfer function TF_POP_PR2.
  4. we fit the ratio TF_POP_BS / TF_POP_PR2 with a 6th order filter (see figure) and implemented this filter in the PR2 ISC input filter banks. We set the driving matrix to send MICH to PR2, and activated the filter

We checked the result with a MICH line at 132 Hz: when the compensation is on, the line amplitude in the PRCL error signal is reduced by at least a factor 10, as expected from the fit residual (figure 2).

We're not leaving this in the guardian.

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 10:58, Friday 22 January 2016 (25097)

The attachment shows the sensing matrix after this diagonalization. PRM and SRM were not remeasured (they are from the data taken on the 12th).

Non-image files attached to this comment
H1 General
edmond.merilh@LIGO.ORG - posted 20:05, Thursday 21 January 2016 - last comment - 08:47, Friday 22 January 2016(25087)
Mid-Shift Summary - Evening

Mid-SHIFT SUMMARY:

Comments related to this report
edmond.merilh@LIGO.ORG - 20:53, Thursday 21 January 2016 (25088)

I started a cleanup of SDF by doing some reverts on TRAMP values (some of which I changed in SUS trying to re-align yesterday). The changes effected were on: HAMs 2,4,5,6 ISI; and SUS-BS,IM, PR2, SR2, and SR3. Also, the Gain/State_Good on the BS ISI was reverted. If 'your' sub-system(s) are showing changes in SDF due to power outage recovery or just trying to make things mo' betta, please have a look and accept or revert.

hugh.radkins@LIGO.ORG - 08:47, Friday 22 January 2016 (25093)

ALL LHO SEI Platform SDFs were green'd Wednesday morning.  Any SDF reds Thursday evening were not related to the power outage.

These changes relate to Jim & me making some guardian changes; we should have more quickly updated the SDFs.

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 13:24, Monday 18 January 2016 - last comment - 15:28, Wednesday 27 January 2016(25009)
f^{-0.5} noise in DARM ?

Evan, Kiwamu,

As some of us have already noticed, there is a broadband noise with a 1/f^{0.5} shape in frequency from 60 to 200 Hz. This noise is unidentified.

Do not believe any statements in this report until futher analaysis. Something is fishy with the claibration of the cross-spectrum.

We are planing to check how stable this noise level is over the course of the entire O1.

 


The below shows an example spectrum of DARM.

Blue curves are twenty spectra of DARM (aka C01 frame, converted into displacement), each of which is made by the Pwelch with Hanning, detrended, 50% overwrap for a 12 minutes time series. The data starts at a GPS time of 1134604817. Green curves are the square-root of twenty cross-power-spectra of DCPD A and B which are reconstructed from the sum and null streams of the DCPDs. The DARM suppression effect was removed from the sum signal. The cross-spectra are then calibrated to the displacement using the latest O1 DARM model of the calibration group. No time varying correction (i.e. kappas) is applied. Red line is a 1/f^{0.5} line to show how steep the slope of the green curves is. I also attach the fig file.

Images attached to this report
Non-image files attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 20:42, Tuesday 19 January 2016 (25039)ISC

Gabriele, Evan, Kiwamu

The spectral shape seems to be 1/f in the range from 50 to 150 Hz rather than 1/f½.

There was a human-error in my code for calibrating the cross-spectrum. It was removing the loop suppression after the power spectrum of the null stream was subtracted from that of the sum stream. This was fixed such that the subtraction happens after the removal of the suppression in the sum spectrum. The below is the latest plot.

 

The plot shows the ampitude spectral desnsities of the calibrated darm displacement (aka C01) and the calibrated cross-spectrum. The cross-spectrum should represent noises which are coherent between two OMC DCPDs.

As a coarse verification, I have eye-ball-fitted the shot noise level with the fixed cavity pole frequency of 341 Hz (shown as a dotted line in cyan). Then I subtracted the shot noise component quadratically out from the actual displacement spectrum (in black). The residual (in blue) agrees with the estimation from the cross-spectrum. In order to check the slope of the cross-spectrum, I also drew a 1/f line. The cross-spectrum seems to follow 1/f from 50-ish Hz to 150 Hz.

The fig file is attached as well.

Images attached to this comment
Non-image files attached to this comment
matthew.evans@LIGO.ORG - 14:52, Friday 22 January 2016 (25108)

An update can be found in entry 25106

kiwamu.izumi@LIGO.ORG - 15:28, Wednesday 27 January 2016 (25211)

A higher resolution version is attached. The frequency resolution is set to 0.1 Hz, 50% overlap with Hanning for 1 hour data. No new findings.

The 1 Hz comb feature (see for example alog 24695) is becoming visible in 20-50 Hz. By the way, the legend in the plot is wrong.

Images attached to this comment
Non-image files attached to this comment
H1 INJ (DetChar, INJ)
adam.mullavey@LIGO.ORG - posted 13:07, Friday 15 January 2016 - last comment - 09:46, Friday 22 January 2016(24969)
Detchar Safety Injection
Corey, Adam,

We're just about to start a detchar safety injection.
Comments related to this report
adam.mullavey@LIGO.ORG - 13:11, Friday 15 January 2016 (24970)
We've finished this injection. I'll post a few more details shortly.
adam.mullavey@LIGO.ORG - 10:05, Wednesday 20 January 2016 (25044)
More Details:

I injected the waveform from 'https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/detchar/detchar_03Oct2015_PCAL.txt'.

The injection start time was 1136927627.

The log file is checked into the svn - 'https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/detchar/O1/log_H1detcharinj_20160115.txt', although for some reason it only shows the start time.
andrew.lundgren@LIGO.ORG - 09:46, Friday 22 January 2016 (25095)DetChar, INJ
The time noted in the alog entry is incorrect. The correct time from the log is 1136927267. The injections are visible at the corrected time.
Images attached to this comment
H1 SEI
jim.warner@LIGO.ORG - posted 14:47, Wednesday 16 December 2015 - last comment - 08:53, Friday 22 January 2016(24245)
RY motion at ETMX causing ISI ring up

**Short version: Increased RY input motion (maybe HEPI, maybe wind/ground) causes ISI X loops to ring up when running 45mhz blends. The suspension/tidal is not the cause. The 90mhz blends seem to be immune to this. Other than using 90mhz blends, I'm not sure how to fix the ISI's configuration, short term to prevent the ISI from ringing up. But we should put a StripTool of the end station ISI St1 CPS locationmons somewhere in the control room so operators can see when ground tilt has rung up an ISI. Alternatively, we could add a notification to VerbalAlarms or the DIAG node when an ISI has been moving something like 10 microns peak to peak for several minutes.

This morning while the IFO was down for maintenance, Evan and I looked at ETMX to see if we could figure out what is causing the ISI to ring up. First we tried driving the L1 stage of the quad to see if some tidal or suspension drive was the cause. This did not have on the ISI, so I tried driving on HEPI. When I drove HEPI X, the ISI rang up a bit, but no more than expected with the gain peaking of the 45mhz blends. When I drove HEPI in RY, however, the ISI immediately rang up in X, and continued to ring for several minutes after I turned the excitation off. The attached image shows the ISI CPS X(red), RY (blue), HEPI IPS RY(green) and X (magenta). The excitation is visible in the left middle of the green trace, also visible in the sudden increase in the red trace. I only ran the excitation for 300 seconds (from about 1134243600 to 1134243900), but the ISI rang for twice that. After the ISI settled down I switched the blends to the 90mhz blends and drove HEPI RY again. The ISI moved more in X but it never rang up even after I increaed the drive by a factor of 5. The second plot shows the whole time series, same color key. The large CPS X motion (with barely noticeable increase in the IPS RY) is the oscillation with the 45mhz blend , the larger signal on the IPS RY (with small increase in CPS X) is with 90mhz blends. The filter I used for each excitation was zpk([0 0],[ .01 .01 .05 .05], 15111).

Images attached to this report
Comments related to this report
brian.lantz@LIGO.ORG - 23:14, Thursday 21 January 2016 (25090)
Did a bit more analysis of this data - 
Not sure why things are so screwy.
There might be non-linearity in the T240s.

Jim's entry indicates that it is NOT a servo interaction with the tidal loop.
so it is probably something local - still not really sure what. Based on the plots below 
I strongly recommend a low-freq TF of Stage 1 (HEPI servos running, ISI damping loops on, iso loops off)
drive hard enough to push stage 1 T240s to +/- 5000 nm/sec 

what I see
fig 1 (fig_EX_ringingXnY)- time series of X and Y and drive signal 
- This is the same as Jim's data, but we also see significant motion in Y
- In the TFs we need to look for X and Y cross coupling

fig 2 (fig_X_ringup_time) - this is the time I used for the other analysis -
We can see the CPS-X and T240-X signals here. Note that I have used bandpass_viafft to keep only data between 0.02 and 0.5 Hz.
The T240 and CPS signals are clearly related - BUT - does the T240 = derivative of the CPS?
signals are at input to the blend filters

fig 3 (fig_weirdTFs) - These are some TFs from ST1 X drive to ST1 CPS X and from ST1 X drive to ST1 T240.
If all the drive for X is coming from the actuators, then the CPS TF should be flat and the T240 TF should be Freq^1
The CPS TF looks fine, I can not explain the T240 TF 
The coherence between T240 and CPS sigs are in the bottom subplot

fig 4 (fig_coh) Coh for drive -> CPS, drive -> T240 and CPS->T240. All are about 1 from 0.03 to .15 Hz.
So the signals are all related, but not in the way I expect.
NOTE - If the ground were driving a similar amount to the actuators, then these TFs would be related by the loops and blend filters - 
I don't think this is the case. decent driven TFs would be useful, here.

fig 5 - sensor_X_difference : Take the numerical derivative of the CPS and compare it to the T240 as a function of time.
Also - take the drive signal * 6.7 (plant response at low freq from TF in fig 3) and then take the derivative of that.
These 3 signals should match - BUT they do not. The driven plant and the CPS signals are clearly similar, but the T240 is rather different looking, esp in the lower subplot. As if the higher frequency motion seen by the CPS is not seen by the T240.  
What the heck?

fig 6 - fig_not_gnd - could it be from ground motion? So I add the ground motion to the CPS signal - but this doesn't look any more like the T240 signal than the straight CPS signal. So the signal difference is not from X ground motion.

Non-image files attached to this comment
richard.mittleman@LIGO.ORG - 08:53, Friday 22 January 2016 (25094)

Has the tilt decoupling on stage 1 been checked recently?  with the 45mhz blends running we are not far from instabilty in this parameter (a factor of 2 maybe?)

Displaying reports 60301-60320 of 84759.Go to page Start 3012 3013 3014 3015 3016 3017 3018 3019 3020 End