Displaying reports 47381-47400 of 83383.Go to page Start 2366 2367 2368 2369 2370 2371 2372 2373 2374 End
Reports until 18:21, Tuesday 20 June 2017
H1 ISC
sheila.dwyer@LIGO.ORG - posted 18:21, Tuesday 20 June 2017 - last comment - 20:05, Tuesday 20 June 2017(37046)
Last night's pitch instability

Last night Jeff and Corey had difficulties with large pitch motion of the test masses.  

This is described in a couple of alogs from Corey, and can easily be seen on the summary pages

Suggestion for the operators if you have this problem again:

1) If you see noise in the ITMY oplev laser sum again, try moving CPY around to see if you can get rid of it.  (The ITMY laser is off for now, but you might still see noise on the SUM).

2)If you see that the circulating power is fluctuating at 0.4 Hz, try turning on the PSL 3rd loop. 

 

 

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 20:05, Tuesday 20 June 2017 (37052)

The fringes seen on ITMY must be due to fringes of the OpLev laser with an OpLev ghost beam coming off CPY.  

In the first attached screenshot I am driving CPY in L with 600 counts at 0.1 Hz in R0 DAMP L.  You can see that the fringing got worse then better as I moved CPY to improve the camera image (36936), then I moved the CP to maximize the fringes.  I went to the floor and unplugged the OpLev fiber, and the fringing went away, so this is not from IFO beams. 

Images attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 18:19, Tuesday 20 June 2017 (37049)
Sweep the LVEA
   Did a sweep of the LVEA in anticipation of going to Observing later this evening. 
H1 General
jeffrey.bartlett@LIGO.ORG - posted 18:17, Tuesday 20 June 2017 (37048)
LLO Down Due to Tropical Storm
   LLO called - They are down due to the approaching tropical storm, and are canceling the remaining night shift. They will reevaluate the situation in the morning.   
H1 INJ
evan.goetz@LIGO.ORG - posted 18:09, Tuesday 20 June 2017 (37045)
3 Burst Supernova Injections
The burst group has requested a couple of supernova hardware injections. These were done out of observing mode and while LLO was not observing.

Here are the schedule file settings:
1182041200 H1 INJECT_BURST_ACTIVE 0 1.0 config/Burst/Waveform/{ifo}/Ott+13_1135029608.842262268_{ifo}.txt    <--- during this injection, the ITMY CP was being moved, so an additional injection was made
1182041560 H1 INJECT_BURST_ACTIVE 0 1.0 config/Burst/Waveform/{ifo}/Ott+13_1136080824.676561355_{ifo}.txt
1182041920 H1 INJECT_BURST_ACTIVE 0 1.0 config/Burst/Waveform/{ifo}/Ott+13_1135029608.842262268_{ifo}.txt
Unfortunately, I can't upload the new schedule file to the daqsvn because it seems to be down. I'll have to get this in tomorrow or whenever the svn is back up and running. The relevant guardian log is attached.
Non-image files attached to this report
H1 AOS
sheila.dwyer@LIGO.ORG - posted 17:57, Tuesday 20 June 2017 - last comment - 19:13, Tuesday 20 June 2017(37044)
ITMY opLev laser switched off

FOr a test, the ITMY optical lever laser was turned off.  Because we want to return to observing before waiting a few hours for the laser to settle and stop glitching, we are going to leave it off for the night. 

Comments related to this report
sheila.dwyer@LIGO.ORG - 19:13, Tuesday 20 June 2017 (37050)

Turned back on, because LLO is down for the night anyway. 

H1 CDS
david.barker@LIGO.ORG - posted 17:32, Tuesday 20 June 2017 (37043)
ran some quick excitation tests on h1pemmx

to test diaggui aborting an excitation and ramping its excitation down, I ran some quick tests on chan20 pemmx. I'm done now, this system is green.

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 17:30, Tuesday 20 June 2017 - last comment - 12:00, Wednesday 21 June 2017(37042)
First look at 72 MHz AS WFS signals

Daniel, Kiwamu,

This is a quick summary of our activity today. Some more details will be posted later.

We have looked into the WFS 72 MHz signals (beatnote of the 118 MHz and 45 MHz) that are derived from the AS port WFSs A and B. They look good in the sense that their alignment signals are not buried under some noises.

After our measurements were done, we reverted the setup so that we can get back to observing.

Comments related to this report
kiwamu.izumi@LIGO.ORG - 12:00, Wednesday 21 June 2017 (37061)

EDIT: The calculation of the modulation depth was corrected in response to Daniel's comment (shown below).

[Summary]

  • Modulation depth@118MHz ~ 1 mard 0.2 mrad.
  • Signal-to-noise ratio of the demod signals is worse than those of AS36 by some factor (depending on the PSL power).
  • With this SNR, the SRC alignment can be sensed in frequencies up to 5 Hz which should be good enough to make a slow ASC control loop.

[Setup]

In the CER, we have two IFR units for this measurement (36354). One is configured for 118 MHz, providing the modulation, and the other is configured for 72 MHz, providing the demodulation RF source. We unplugged the RF source for the 90 MHz system in the ISC R3 rack (the one by HAM6) and plugged the 72 MHz source. This means that we use the 90 MHz demodulation system for demodulating the RF components at 72 MHz. This allows us for a minimum hardware modification at the cost of losing the ASAIRB_RF90 signals. Currently, ASAIRB_RF90 is used only once in the locking sequence where the ISC_DRMI guardian checks whether the DRMI is locked on a hopped mode or not. During this test, we have commented out this action from the ISC_DRMI guardian so that it doesn't stop at this point.

We cranked up the RF power of the 118 MHz unit from -10 dBm to 10 dBm. Note that the RF amplifier that is directly connected to this IFR unit has a input rate of +10 dBm. According to the previous measurement (36354), this should provide 30 dBm at the input of the EOM. The RF power of the 72 MHz unit was set to 13 dBm which gave reasonable RF powers in all the 90 MHz demodulator systems.

BTW, the Triplexer doesn't give appreciable loss at 72 MHz (see table.2 of E1600027).

[Measurement concept: frequency-offset demodulation]

Today we introduced an intentional frequency offset of 205 Hz to the 72 MHz unit. This results in the demod signals rotating in the I-Q phase space at the offset frequency. The main motivation for doing this frequency-offset technique is that it allows us for relatively accurate measurement of the relative RF phase between the two IFR units and the main RF source (Wentzel OCXO).

Looking at the raw RF signals with an oscilloscope, we confirmed that the RF phase of the IFR units with respect to the Wentzel OCXO slips at a rate of roughly 2 pi / 10 seconds even though the IFR units are synchronized to the 10 MHz source which is locked to the GPS 1 pps signal. Not surprisingly the relative phase between the two IFR units don't seem to slip by appreciable amount. In future, we will get an harmonic generator so that the 72 and 118 MHz RF signals are synchronized to the main OCXO.

Regardless of whether the RF phase slips or not, the idea is to have a look at the ASC-AS_WFS_A(B)_RF118 signals in frequency domain so that the peak height at the offset frequency gives us a measure of the modulation depth.

[Modulation depth]

We estimated the modulation depth of the 118 MHz RF sidebands to be 1 mrad 0.22 mrad, much smaller than the others (15661).

Our measurement is essentially comparison of the signal strength between the 36 and 72 MHz demodulated signals given that we know the modulation depth for 9 MHz. The below shows the derivation.

  • DRMI was locked with both arm cavities set to off resonant point. PSL was set to 2 W.
  • Measuring the rms of the 205 Hz peak produced in the ASC-AS_A_RF90_I1_OUT, we determined the rms to be about 7 counts.
    • This corresponds to an amplitude of 10 counts or peak-to-peak amplitude of 20 counts at 205 Hz
  • Measuring the DC value of AS_A(B)_RF36_I(Q)_SUM, we found the quadrature sum  to be about 2000 counts.
  • Taking out the gain difference (a factor of 40 from the whitening gain, a factor of 1/5 1/16 from PD response and difference in the interferometer transmissivity by a factor of 11) from the 72 MHz calculation, we get a signal amplitude in the unit equivalent to the 36 MHz to be 5 cnts ( = 10 cnts x 4 segments x 1/40 whitening gain x 5 PD response 16 PD response x 1/11 ifo trans).
  • Therefore Gamma_118 / Gamma_9 = 1.45 cnts/ 2000 cnts.
  • Assuming Gamma_9 to be 0.3 rad, we get Gamma_118 = 0.75 mrad ~ 1 mrad 0.22 mrad.

[Signal to noise ratio]

In the current freqeuncy-offset scheme, the ASC signals are upconverted to frequencies around 205 Hz. Looking at the spectrum of the demodulated signals when the interferometer was locked with a 2W PSL, we saw that the signal-to-noise ratio of the 72 MHz signals are worse than that of the 36 MHz by a factor of 10. See the attached dtt session.

After we reached a state equivalent to NOMINAL_LOW_NOISE, we took a look at the spectrum again to see how much the signal-to-noise ratio has improved. It seem to have improved by a factor of 5 or so even though the PSL power increased by a factor of 15  (2 W -> 30 W). See the second attachment. Some fraction can be explained by the 3 dB reduction of 45 MHz RF source power that takes place during the locking sequence.

It seems that we can sense the ASC signals up to 5 Hz before diving into some white noise.

[Future direction]

  • If allowed, modify h1asc and place a PLL block for measuring the RF phase.
  • If allowed, place a phase correction functionality for individual segments of AS118.
  • If allowed, record some relevant channels.
Images attached to this comment
daniel.sigg@LIGO.ORG - 10:49, Wednesday 21 June 2017 (37065)

The difference between the transimpedance gains at 36 and 72 MHz is taken from LIGO-T1300488. Looking at Figs. 5 and 6 on page 3, we read the response as +2 dB at 36 MHz (Q3 trace in Fig. 5) against –22 dB at 72 MHz (Q3 trace in Fig. 6). The gain difference is then estimated to be 24 dB, or a factor of ~16.

The transmission ratio towards the antisymmetric port between the 9 and 118 MHz sidebands is around ~1/10, see Hang's presentation LIGO-T1700215.

LHO FMCS
gerardo.moreno@LIGO.ORG - posted 16:45, Tuesday 20 June 2017 (37040)
Y-End Air Handling Fan Vibration Sensors (Fan 1)

(Filiberto, Richard, Gerardo)

Original cable for Fan 1 was shorted/broken sometime ago, removed broken cable.

A new cable was pulled and landed at the vacuum rack, sensors are now running.

 

H1 CAL (CAL)
sudarshan.karki@LIGO.ORG - posted 16:28, Tuesday 20 June 2017 - last comment - 17:34, Wednesday 28 March 2018(37039)
Down Conversion of Pcal Injection

SudarshanK, RickS

To study the downconversion of Pcal excitation we used a DB9 breakout at the back of the Pcal chassis and routed the excitation channel through H1:CAL-PCALX_WS_PD for now. This will be returned to its original configuration once the investigation is complete.

Images attached to this report
Comments related to this report
sudarshan.karki@LIGO.ORG - 18:17, Tuesday 20 June 2017 (37047)

The PcalX is still fully functional and hardware injection can be carried out if needed. The WS_PD channel through which the excitation channel is routed is a spare channel that is only used during the end-station PD calibration.

sudarshan.karki@LIGO.ORG - 12:30, Tuesday 27 June 2017 (37139)

Summary:

We have established that most of these down converted lines (the one that hurts us)  reported in alog 36959 arise from the aliasing of the harmonics of the injected high frequency calibration lines. The lines that have the possibility to show up in the DARM are the ones that lie between 10 Hz to few hundred Hz. We can avoid these lines by selecting the high frequency calibration lines such that  the aliased lines are not in the given low frequency region.

Details:

We ran into issues with low frequency lines (in 100 Hz range) showing up in DARM when we were running high frequency calibration lines in the region of 5.5 - 6 kHz. This was first noticed in this LHO alog 36959 and LLO alog 34346. To understand this problem we wanted to find where these lines were being produced, photon calibrator itself or the data acquisition system. We disconnected the cable that inputs the excitation to the Pcal electronics and used a DB9 breakout box to acquire the excitation signal so that we were getting these signal before it enters the Pcal system. We rerouted this signal through the H1:CAL-PCALX_WS_PD channel which was one of the unused Pcal channel. 

The first plot shows the spectrum with a 5036 Hz excitation line (in blue) and without an excitation (in red). Some of the extra lines seen in the  blue spectra are the result of aliasing of the  higher order harmonics  of the injected as well as the imaged lines (imaging happens when going from 16khz to 64 kHz). In this particular case the 68 Hz line is the aliasing of the 13th order harmonic of 5036 Hz injected line. The second plot shows the predicted aliased lines (based on harmonics and upsampling) that would be produced for 5036 Hz injected line. Some of the predicted lines show up in the actual spectrum but not all and not all line that are present in the spectra are predicted. However, the lines that show up above few hundred Hz will be well below the DARM signal as the actuation transfer function goes as 1/f^2. Shivaraj, at LLO has taken some additional measurement to see if we can find the source of all the aliased lines. Report to follow.

 

Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 15:35, Tuesday 27 June 2017 (37171)CAL, CDS, DetChar
Tagging DetChar and CDS on this, so that the CW group can follow up with them to understand how to flag the data for this known issue.
sudarshan.karki@LIGO.ORG - 17:20, Wednesday 05 July 2017 (37340)CAL, CDS, DetChar

RickS, SudarshanK,

The breakout box used to acquire the analog excitation signal on X-end Pcal has been removed and the Pcal configuration is now back to normal. During the visit, Rick repeated some measurement that reproduced the 86 Hz line when a Pcal line was injected at 5950 Hz with an excitation amplitude of 25000 cts. This measurement was made at the DAC (analog) output using SR785. The 86 Hz line is about 70dB below the injected line. This still does not explain why we don't see 86 Hz line in analog output in the measurement (LLO alog 34495) that Shivaraj made using Agilent signal analyzer. :(

Images attached to this comment
sudarshan.karki@LIGO.ORG - 15:22, Tuesday 18 July 2017 (37592)

On Jeff's request, I am putting down the empirical formula that predicts the lowest frequency down-converted lines for each high frequency excitation.

DCF =  2^16 - EF * n, where DCF is the down converted frequency, EF is the excitation frequency and n is the harmonic number. For frequencies around 4-6 kHz, the harmonic number that produces the line in the bucket are between 11 and 13.

I don't have a physical intuition on why this happens. If we were looking at the resampled 16 kHz signals, the presence of these lines would not be surprising because these would be produced because of aliasing but we see these low frequency lines  on the DAC output, measured using the analog spectrum analyzer. Plots showing the same are attached.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 17:34, Wednesday 28 March 2018 (41194)CDS
Was associated with FRS Ticket 8335.
Now associated with IIET Ticket 10318.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:21, Tuesday 20 June 2017 (37038)
Ops Evening Shift Transition
Ops Shift Transition: 06/20/2017, Evening Shift 23:00 – 07:00 (16:00 - 00:00) - UTC (PT)
State of H1: IFO is locked at SRM_ASC_HIGH_POWER  
Intent Bit: Commissioning
Weather: Wind is 3 to 20mph; Skies are mostly clear; Temps in the lower 90s  
Primary 0.03 – 0.1Hz: X & Y Axis at 0.1um/s, Z Axis is at 0.02um/s 
Secondary 0.1 – 0.3Hz: At 0.07um/s   
Quick Summary: IFO is locked as commissioning work continues  
Outgoing Operator: Cheryl
H1 CDS (CDS)
sheila.dwyer@LIGO.ORG - posted 16:02, Tuesday 20 June 2017 - last comment - 16:52, Tuesday 20 June 2017(37037)
DTT abort lockloss?

I think that this lockloss was caused by DTT suddenly outputting a large excitation when I don't think it should have, at 1182033600.  I increased the amplitude of the noise excitation in the attached template from 10000 to 20000, the template has a 5 second ramp up time, but for some reason the excitation reached an amplitude of 45,000 counts very suddenly as shown in the attached screenshots. 

Since the input to the filter was off, the only thing coming into this filter should have been the excitation.  

Images attached to this report
Non-image files attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 16:52, Tuesday 20 June 2017 (37041)

This happened again, this time I just let the measurement finish and when it was ramping off the interferometer unlocked. Screenshots of the two incidents are attached.

 

Images attached to this comment
H1 General
cheryl.vorvick@LIGO.ORG - posted 15:55, Tuesday 20 June 2017 (37036)
Ops Day Summary:
H1 CDS
david.barker@LIGO.ORG - posted 14:44, Tuesday 20 June 2017 - last comment - 15:44, Tuesday 20 June 2017(37031)
New EPICS IOC started, h1viralert Virgo Alert System

As part of the Virgo Alert System, I have created a new pycaspy IOC running on h1fescript0 which runs the EPICS channels TJ's python script writes to.

Full details in the wiki

Comments related to this report
thomas.shaffer@LIGO.ORG - 15:44, Tuesday 20 June 2017 (37035)

VerbalAlarms has been modified to look for new events from these new channels. Operators may get alarms with "VIRGO" at the beginning of the notification.

H1 General
cheryl.vorvick@LIGO.ORG - posted 14:12, Tuesday 20 June 2017 (37030)
Maintenance Update: 21:00UTC
H1 SEI
jenne.driggers@LIGO.ORG - posted 13:56, Tuesday 20 June 2017 (37029)
NN array sensors back

[PaulM, JoeM, Jenne]

Most of the Newtonian noise sensors that had to be removed for the May vent are back.  We did not do the ~3 that are north of the HAM4 north door - I'll do that quickly next Tues.

H1 CAL (CAL, DetChar)
alexander.urban@LIGO.ORG - posted 09:26, Tuesday 20 June 2017 - last comment - 13:28, Wednesday 21 June 2017(37017)
GDS calibration pipeline restarted with gstlal-calibration-1.1.7

The primary and redundant h(t) pipelines were restarted at GPS second 1182010698. This pipeline restart is not accompanied by any filter changes, but does pick up gstlal-calibration-1.1.7. For more information on this version of the code, please see its redmine page.

For more information about the filters currently being run, please see the following aLOG entries:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=36864
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=36842

Comments related to this report
gregory.mendell@LIGO.ORG - 15:38, Tuesday 20 June 2017 (37034)

The corrected filter file needed for LHO Work Permit Number 7047 had already been staged on the DMT on June 14. Thus, this restart of the calibration code picked up the corrected filter file, and this completes LHO Work Permit Number 7047.

alexander.urban@LIGO.ORG - 13:28, Wednesday 21 June 2017 (37067)

Correction to this alog: the pipeline restart does not affect the version of gstlal-calibration running, since version 1.1.7 was already running at Hanford. However it does pick up corrected filters, but the file pointing to those filters had the same name so no command line change was needed. I apologize for the confusion.

H1 AOS (AOS, DetChar, SUS)
pep.covas@LIGO.ORG - posted 12:32, Friday 16 June 2017 - last comment - 15:01, Tuesday 20 June 2017(36941)
OpLev glitches spectra comparison with DARM
Sheila, Pep

The attached plots show the comparison between H1:GDS-CALIB_STRAIN and the OpLev channel (H1:SUS-ETMY_L3_OPLEV_SUM_OUT_DQ) for different glitch events, found in HVeto in this day: https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20170419/detchar/hveto/. We also show a comparison between these channels for times when the OpLev was not glitching.

To get these results, we have assumed that the only force on the mirror is the pressure radiation force of the OpLev laser. The equation is:

F=2*P/c=m*a,

where P is the power of the laser, c is light's velocity, m is the mass of the mirror (taken as 40 kg) and a is acceleration. In order to find the power of the laser, we have to use the relation between the counts detected by the QPD and the power, which is (DCC T1600085):

P = Counts * (40 [V] / ((2^16) - 1)) * (1 / Transimpedance [Ohms]) * (1 / Whitening Gain) * (1 / Responsitivity [A/W]) = Counts * 7.6295e-09 for the H1:SUS-ETMY_L3_OPLEV_SUM_OUT_DQ channel.

The transimpedance values can be found in DCC T1600085, the whitening gain values in dB can be found here in DCC T1500556-v4. These values have to be converted from dB using 10^(x/20). The responsitivity is 0.4, and can be found here: http://www.hamamatsu.com/us/en/product/alpha/S/4106/S5981/index.html#1328449179787
(the laser is at 635 nm).

After calculating the acceleration, we calculated the asd of this time series using gwpy, and after that we divided by the square of the frequency to have the displacement of the mirror. To compare these values to the ones in DARM, we divided by 4000 m to get the strain.
Images attached to this report
Comments related to this report
pep.covas@LIGO.ORG - 15:01, Tuesday 20 June 2017 (37032)AOS, DetChar, SUS
As Keita pointed out, the plots in the previous post were wrong, due to a missing factor of 1/(2*pi)^2 when converting from acceleration to displacement. I attach the same plots with the correct factor, and five new plots that use a window of 1 second around the time of the event instead of the window of 4 seconds that was used before
Images attached to this comment
Displaying reports 47381-47400 of 83383.Go to page Start 2366 2367 2368 2369 2370 2371 2372 2373 2374 End