Displaying reports 54241-54260 of 84759.Go to page Start 2709 2710 2711 2712 2713 2714 2715 2716 2717 End
Reports until 12:44, Wednesday 09 November 2016
H1 PSL
daniel.sigg@LIGO.ORG - posted 12:44, Wednesday 09 November 2016 - last comment - 20:25, Wednesday 09 November 2016(31361)
PMC length noise injection

The attached plots show a length noise injection into the PMC using TFIN. The first plot is calibrated in Volts for the HV_MON, whereas the second plot is calibrated in displacement. The coupling coefficient at 1 kHz is about 3.5 x 10-8 between the PZT and DARM length.

The reference traces 0 and 1 are without injection, whereas reference traces 2, 3 and 4 are from before the changes on the PSL table on Tuesday.

A measurement done at the very beginning of the run had about half the coupling—indicating that the coupling depends on thermal lensing.

Non-image files attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 16:04, Wednesday 09 November 2016 (31370)

The attached plot shows frequency and intensity noise measured by the IMC/REFL and second loop ISS sensors.

There is coherence above 1 kHz with intensity  noise. Using the intensity noise coupling TF from alogs 30274 or 29926, one can conclude that it doesn't couple through intensity noise. The intensity noise is at 10-8 RIN/rtHz at 1 kHz. With a coupling of 10-13 m/RIN, we are far below the DARM noise.

The frequency noise produced by the PMC length noise is of the order of 1 Hz/rtHz at 1 kHz. It will be suppressed by the FSS, IMC and REFL. As such it is much too small to be responsible for the coupling directly. There is however, coherence with frequency noise as seen by REFL_A_RF9_I in the 1 kHz region. Assuming the REFL control signal is dominated by IMC sensing noise which seems to be around 2 x 10-4 Hz/rtHz at 1 kHz for 25 W input, see alog 31138, and using the noise coupling from alog 31176, we get a number around 10-19 m/rtHz at 1 kHz. So, it is conceivable that the PMC noise produces error point offsets in the REFL servo which in turn propagate to DARM as frequency noise.

Non-image files attached to this comment
daniel.sigg@LIGO.ORG - 20:18, Wednesday 09 November 2016 (31379)

We saw an increase of the PMC length noise coupling to DARM, when we misaligned SRM by 20 µrad. According T0900142 the requirement for SRM is 2.5 µrad which puts the required 3x10-6 /rtHz at 1 kHz with a safety factor of 10. So, for 20 µrad, a jitter of 7x10-6/rtHz at 1kHz is at the DARM noise level at full sensitivity. Our jitter was roughly 5x10-6/rtHz and it made a difference at the 1x10-19 level. Maybe somewhat higher than expected but close.

Non-image files attached to this comment
daniel.sigg@LIGO.ORG - 20:25, Wednesday 09 November 2016 (31380)

Looking at the IMC WFS signal we can clearly see the PMC length noise injection. If we take the 260 Hz periscope peak as a reference, this doesn't explain the coupling to DARM. What is surprising is that even without length noise injection (REF traces), the coherence between IMC WFS and PMC HVMon is large at frequencies between the jitter peaks.

This measurement was repeated with just the IMC locked at 25 W and ISS second loop enageged. This did not change the HV MON coherence with the IMC WFS nor the coherence with MC_F.

Non-image files attached to this comment
H1 SEI (GRD)
hugh.radkins@LIGO.ORG - posted 11:56, Wednesday 09 November 2016 - last comment - 01:02, Thursday 10 November 2016(31366)
ETMY ISI Blend did not switch

Sheila reported that Nutsinee switched the SEI_CONFs to BLEND_45mHz_SC_useism last night but looking this morning I see that it did not switch the Blend on ETMY.  I manually switched the (X & Y dof) Blends only; the Sensor Correction did switch to not use the BRS.  Otherwise all switching worked with Sensor Correction for all Test Masses and no BRS in use at the Ends.

Comments related to this report
hugh.radkins@LIGO.ORG - 12:04, Wednesday 09 November 2016 (31368)

by the way, I noticed this issue because I saw the SDF differences at the end stations were not the same.  Since this is a guardian controlled feature, it might be argued that it would be Not_Monitored.  Were that the case...

hugh.radkins@LIGO.ORG - 16:57, Wednesday 09 November 2016 (31377)

In case you are wondering what difference this can make...

The attached asd shows the ETMs 12 and 6 hours ago.  12 hours ago (ref traces) the ETMY was in 250mHz blends while the ETMX was in the 45mHz blend. 6 hours ago was after the ETMY was actually switched to 45mHz blends.

The thick green and brownish curves become much more like the others after the blend switching and moving the blend gain peaking away from the secondary microseismic peak.

The second attachment are trends of theX & Y ARM SUSPOINT Motions based on the ISI's onboard GS13s and the ETMY and ITMY SWSTAT showing when the ITMY blend switched but the ETMY did not and then this morning when the ETMY switched to the same blend as the ITMY.  When the two ISIs are in different blends, the motion is clearly larger although based on these trends.  Based on the XARM Motion though, not clearly a better blend overall.

Images attached to this comment
jim.warner@LIGO.ORG - 01:02, Thursday 10 November 2016 (31385)

ETMY_ST1_CONF wasn't switching properly because I had found an issue with the guardian when trying to write some different configurations. I forgot to revert the code to a properly working state. Sorry. I've fixed the configuration, and tested that it works on ETMY.

 

H1 General
cheryl.vorvick@LIGO.ORG - posted 11:38, Wednesday 09 November 2016 - last comment - 11:40, Wednesday 09 November 2016(31363)
Ops Day Update: 19:27UTC, 11:27PT

State of H1: aligned and locking, has made it to NLN but lost lock, ALS Y arm fiber polarization shot up to 28%, now adjusted back down

Activities:

H1 Observations:

Comments related to this report
cheryl.vorvick@LIGO.ORG - 11:40, Wednesday 09 November 2016 (31364)

Lockloss tool cannot connect.

Images attached to this comment
H1 General (CAL, DCS)
john.zweizig@LIGO.ORG - posted 11:15, Wednesday 09 November 2016 (31362)
DMT h(t) process managers restarted to ignore invalid data.
It appears that the new channels in the h(t) frames contain some NaN or inf values that the DQ program refused to process. This cause the low-latency data to hang.  In order to repair this I had to set an environment variable and restart the process managers on h1dmt0 and h1dmt2. Hopefully everything will run smoothly from here out.
H1 SEI (SEI)
travis.sadecki@LIGO.ORG - posted 11:01, Wednesday 09 November 2016 - last comment - 11:43, Wednesday 09 November 2016(31359)
BSC and HAM CPS sensor spectra

Attached are the results of the BSC and HAM spectra as requested by FAMIS 6871.  I didn't see anything glaring, but I also don't know what I'm looking at.

Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 11:43, Wednesday 09 November 2016 (31365)

Generally these all look fine with regard to the intention of this test.  There are no outlying base levels in the higher frequency (above the 'details' < 20 Hz) range.

H1 CDS
david.barker@LIGO.ORG - posted 10:57, Wednesday 09 November 2016 (31360)
timeline of Tuesday evening h1oaf0 DAC problem

here is the timeline of yesterday evening's h1oaf0 DAC problem which required a restart of the IOP model

All times are local PST.

Prior to the problem, h1iopoaf0 STATE_WORD is 512 (OVERFLOW)

delta-T time event
0:00 19:23:00 IOP DAC drives go to zero volts. h1iopoaf0 STATE_WORD=652(ADC,DAC,DACKILL,OVERFLOW)
+5:00 19:28 phone conversation, decision to restart IOP models
+11:00 19:33 models restarted after killing them, DAC drive is restored. Presumably killing model h1susprocpi caused lock loss
H1 PEM
edmond.merilh@LIGO.ORG - posted 10:33, Wednesday 09 November 2016 (31356)
PSL 101 Dust monitor alarms

Jeff,

      This monitor has been regularly sounding. Below are the PSL dust monitors in their current configurations. There were no incursions today. No fans or environmental controls were changed and winds are below 10 mph.

Images attached to this report
H1 PSL
jason.oberling@LIGO.ORG - posted 09:56, Wednesday 09 November 2016 (31354)
PSL Recovered from Trip

J. Oberling, E. Merilh

The PSL tripped out this morning due to the commissioning work detailed here.  The cause is the ILS losing lock, which then triggered the HPO power watchdog and shut off the HPO; the 35W FE and the chillers remained operational.  The system recovered without issue and is now back up and running.  I took the opportunity to reset the injection locking counter in both Beckhoff and the Laser MEDM screen, and tweaked up the beam alignment into the PMC (hooray for remote control!) to recover the PMC transmitted power we had yesterday (alignment drift due to temperature changes in the PSL enclosure with the environmental controls on and off).

H1 PSL
daniel.sigg@LIGO.ORG - posted 09:35, Wednesday 09 November 2016 (31353)
Looking at DC readouts of PMC/ILS locking diodes

Keita Daniel

Yesterday, a large oscillation around 1 MHz was observed on the DC readout of the PMC locking diode. The DC readout is tapped directly at the HF transimpedance amplifier with a 50 Ω series resistor, see D1002163. It is available at the rack and hooked to the trigger PD input of the field box. There doesn't seem to be any termination on the rack side! The DC level of the PMC readback was about 120 mV, whereas the ILS PD showed about 1 V. The transimpedance for the PMC locking diode is 1 kΩ, where it is 820 Ω for the ILS diode. No oscillation was observed. We also looked at the signal on the RF spectrum analyzer. But, when we tried it for the ILS, the HPO tripped. End of expedition.

H1 General
edmond.merilh@LIGO.ORG - posted 08:17, Wednesday 09 November 2016 - last comment - 10:33, Wednesday 09 November 2016(31352)
Shift Summary - Day Transition
TITLE: 11/09 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 0.0Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 12mph Gusts, 7mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.68 μm/s 
QUICK SUMMARY:
Comments related to this report
edmond.merilh@LIGO.ORG - 10:33, Wednesday 09 November 2016 (31358)

16:51 Daniel and Keita out to LVEA to work on PMC

17:09 Hugh reports that ISI_CONF reporting ETMY at BLEND_45mHz_SC_useism is actually incorrect. It's actually set to the 250mHz.

17:13 LASER tripped (injection locking) while Keita and Daniel working in PSL rack. Jason coming to control room to restart.

17:56 Relocking resumed

17:57 Cheryl on site

H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 01:09, Wednesday 09 November 2016 (31350)
Ops EVE shift summary
TITLE: 11/08 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lockloss
INCOMING OPERATOR: -
SHIFT SUMMARY: Commission and calibration most of the evening. We switched ISI blend on the test masses ISI. We had to revert some of the PI settings after oaf model restart did something weird to it. I don't think everything is back to where it was since we only dealt with whatever was causing problems (mainly mode 27 and 28)
LOG:
00:00 Dave and Jim to EY to look at BRS Beckhoff computer
0:15 Hugh back
0:24 Dave and Jim back
1:00 Jeff powercycle SR2 chasis
~9:00 Switched test mass ISI blends config to be using 45mHz blend.
9:05 Lockloss. Sheila tried to switch to REFL WFS. Since we have no Owl shift operator we're just going to leave the IFO this way (the request remains at NLN). It's been a depressing evening.
H1 SUS
sheila.dwyer@LIGO.ORG - posted 20:54, Tuesday 08 November 2016 - last comment - 07:41, Wednesday 09 November 2016(31346)
SR2 glitch

We had at least one lockloss tonight that seemed to be caused by SR2 glitches. Screenshot is attached. 

It seems like SR2 was noisier after maintence day today.  

But our main problem tonight was that the refl WFS (which we have taken in and out several times over the last week) don't work when the microseism is around the 90th percentile or more.  

Images attached to this report
Comments related to this report
krishna.venkateswara@LIGO.ORG - 22:26, Tuesday 08 November 2016 (31348)

For such high microseism situations, it may be worth switching back to the 45 mHz blends for all the test-mass chambers, with or without sensor correction.

sheila.dwyer@LIGO.ORG - 00:41, Wednesday 09 November 2016 (31349)

We are leaving the IFO in observe, but there is scattering from ISCT1 because we can't move to REFL wfs with the higher ground motion. This is something to look at in the morning, but it caused us many locklosses tonight.  

The IMC WFS offsets that were working early last week don't seem repeatable tonight.

Nutsinee switched the test mass ISIs to BLEND_45_SC_useism, that went OK except for some large glitches when switch ETMX, but when I tried switching to REFL WFS again we dropped the lock.  We probably need to look at finding a better matrix for refl WFS and getting rid of the oscialltion in the centering and IMC WFS. 

cheryl.vorvick@LIGO.ORG - 07:41, Wednesday 09 November 2016 (31351)ISC

Speculation about REFL WFS.  Yesterday I was concerned that PR2 had moved what seemed like a lot (8-10urad) when I did the Inital Alignment.  I would expect something smaller like 2urad.  I couldn't find a cause for that, but I did notice IM4 also changed by 20urad in yaw.  A change of 20urad in yaw of IM4, assuming PRM moved to match the change of the PRC input beam, would propigate to the REFL WFS, and my estimate for the change in beam position at REFL WFS to be 168um.  I don't know the beam size on REFL WFS, but the IMC WFS is about 250um, so if REFL WFS is about the same, the 168um is a beam position change of ~70%.

H1 CAL
jeffrey.kissel@LIGO.ORG - posted 13:59, Monday 07 November 2016 - last comment - 16:53, Sunday 20 November 2016(31289)
ETMY UIM and PUM CAL Lines Turn OFF
J. Kissel, D. Tuyenbayev

Following preliminary results from Darkhan on the individual actuation strength of the UIM and PUM stages for H1SUSETMY (see, thus far LHO aLOG 31275), and the current delightfully long lock stretch with them in place, I'm bringing this study to a close. I've turned off the temporary L1 and L2 calibration lines at 33.7 and 34.7 Hz, respectively. We do not intend on turning on these lines again for the duration of the run.

These lines were turned OFF at Nov 07 2016 21:21:49 UTC.
Images attached to this report
Comments related to this report
darkhan.tuyenbayev@LIGO.ORG - 20:10, Tuesday 08 November 2016 (31344)CAL

Summary

A refined analysis of the L1, L2 and L3 stange actuation strenghts was done using the data from last several days that include several low-noise lock stretches. Actuation strength factors are:

KU = 8.020-8 +/- 2.983-10 N/ct   ( std(KU) / |KU| = 0.0037 )

KP = 6.482-10 +/- 2.748-12 N/ct   ( std(KP) / |KP| = 0.0033 )

KT = 4.260-12 +/- 1.313-14 N/ct   ( std(KT) / |KT| = 0.0031 )

Details

Following 4 lines were used to calculate the factors: UIM (L1) line at 33.7 Hz, PUM (L2) line at 34.7 Hz, TST (L3) line at 35.9 Hz and PcalY line at 36.7 Hz. The most recent DARM model parameters were used for this analysis. Also, values past Nov 5 were calculated with the updated DARM filters (see LHO alog 31201), not accounting for this would produce results biased by 1-2%.

Each data point is a quantity calculated from 10s FFTs. The outliers were removed in two steps:
- took the mean and the standard deviation of all data points in intervals when the IFO range was >=50 MPC, removed 3-sigma outliers;
- removed the 3-sigma outliers from the mean of the remaining data points.

The mean values and the standard devitaions noted above were taken from GPS time interval [1162369920 1162413500], ~11 hours of low-noise data (blue markers). Standard errors on the mean values, std(Ki) / sqrt(N), are orders of magnitude smaller compared to the Pcal and the DARM loop model uncertainties (number of data points in the seletected interval - N=4251).

For preliminary results from Nov 4 data and before see related reports: 31183, 31275.

Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 12:27, Wednesday 09 November 2016 (31369)
Recall the ER8/O1 values for these coefficients were

    'Optic'      'Weighted Mean'    '1-sigma Uncertainty'    '1-sigma Uncertainty'
    'Stage'      '[N/ct]'           '[N/ct]'                 '%'                  
    'ETMY L1'    '8.17e-08'         '3.2e-09'                '3.9'                
    'ETMY L2'    '6.82e-10'         '5.2e-13'                '0.076'              
    'ETMY L3'    '4.24e-12'         '4.1e-15'                '0.096' 
from LHO aLOG 21280.

Comparing against numbers above,
    KU = 8.020-8 +/- 2.983-10 N/ct   ( std(KU) / |KU| = 0.0037 )
    KP = 6.482-10 +/- 2.748-12 N/ct   ( std(KP) / |KP| = 0.0033 )
    KT = 4.260-12 +/- 1.313-14 N/ct   ( std(KT) / |KT| = 0.0031 )

This means a change of
               (ER8 - ER10)/ER8 = 
    ETMY L1        0.0183
    ETMY L2        0.0495
    ETMY L3       -0.0047

We will compare these numbers against those determined by frequency-dependent transfer functions, e.g. the to-be processed data from LHO aLOG 31303, and update the low-latency/ calibration accordingly next week. It will also be interesting to re-cast the L1 and L2 numbers into a combined actuation strength change from ER10/O1, and compare it against the constantly calculated kappa_PU and check consistency there.
darkhan.tuyenbayev@LIGO.ORG - 10:16, Thursday 10 November 2016 (31391)CAL

Data points prior to DARM filter update mentioned in the report were analyzed with the help of following DARM model parameters:

ifoIndepFilename : ${CalSVN}/Runs/PreER10/Common/params/IFOindepParams.conf (r3519)
ifoDepFilename   : ${CalSVN}/Runs/PreER10/H1/params/H1params.conf (r3640)
ifoMeasParams    : ${CalSVN}/Runs/PreER10/H1/params/H1params_2016-10-13.conf (r3519)

and after the the DARM filters were updated (GPS 1162336667) the following configuration was used:

ifoIndepFilename : ${CalSVN}/Runs/PreER10/Common/params/IFOindepParams.conf (r3519)
ifoDepFilename   : ${CalSVN}/Runs/PreER10/H1/params/H1params_since_1162336667.conf (r3640)
ifoMeasParams    : ${CalSVN}/Runs/PreER10/H1/params/H1params_2016-10-13.conf (r3519)

Scripts were uploaded to CalSVN at

${CalSVN}/Runs/PreER10/H1/Scripts/Actuation/2016-11-08/

5 days SLM data (75 MB): ${CalSVN}/Runs/PreER10/H1/Measurements/Actuation/2016-11-08/

Plots: ${CalSVN}/Runs/PreER10/H1/Results/Actuation/2016-11-08_H1_UPT_act_strengths_*

darkhan.tuyenbayev@LIGO.ORG - 16:53, Sunday 20 November 2016 (31670)CAL

We discovered that in the single-line analysis we had an incorrect sign for TST stage actuation (we incorrectly set the sign of the N/ct coefficient).

The updated results have been posted in LHO alog 31668.

H1 PSL
daniel.sigg@LIGO.ORG - posted 12:03, Friday 04 November 2016 - last comment - 09:58, Wednesday 09 November 2016(31203)
Comparison of ISS, ILS and PMC signals

This is a comparison between the ISS, ILS and PMC signals before (REF traces) and after the changes in the electroncis and the modulation depth, see 31095.

A few observations:

Non-image files attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 13:28, Friday 04 November 2016 (31205)

A better plot showing the relationship between the ILS and PMC mixer and HVMon signals.

Non-image files attached to this comment
daniel.sigg@LIGO.ORG - 15:23, Friday 04 November 2016 (31211)

Reducing the ILS gain by 16 dB increases the noise seen by the PMC by the same amount below 1 kHz. This change reduced the ILS ugf from ~10 kHz down to ~1 kHz.

Non-image files attached to this comment
daniel.sigg@LIGO.ORG - 09:58, Wednesday 09 November 2016 (31355)

PMC and HPO PZT characterization/calibration

The PMC PZT is decribed in alog 30729:

  • Model: PI PAHH-0013
  • Capacitance: 63 nF
  • Travel: 4 µm/kV
  • Series resistor: 3.3 kΩ
  • Pole: ~770 Hz.

The ILS PZT is

  • Capacitance: 120 nF
  • Travel: 15 µm/kV
  • Series resistor: 3.3 kΩ
  • Pole: ~400 Hz.
H1 ISC
stefan.ballmer@LIGO.ORG - posted 16:36, Thursday 03 November 2016 - last comment - 12:05, Wednesday 09 November 2016(31176)
Frequency nboise at least a factor of 8 below the noise floor.

Evan, Stefan,

We re-measured the frequency noise coupling to DARM from the four sensors we have: REFL9 (in-loop), and POP9, REFL45, POP45 (all out-of-loop).

Plot 3 shows that transfer function in m/ct.  (For REFL 9, the calibration from Evan 1.5e-7W/ct, see e.g. 30286. We didn't calibrate the others in W yet.)

Plot 1 shows the projection of all 4 sensors to DARM. The fact that POP9 disagrees with the others - but is coherent with them (Plot2) suggests that what limits our sensing is not frequency noise.

Finally, Plot 4 shows the relative calibration of the four sensors for frequency noise.

The xml files are in

/ligo/home/controls/sballmer/20161103/FreqNoiseProjection.xml

/ligo/home/controls/sballmer/20161103/REFLPOPV2.xml

Also, for reference, the frequency noise injection was done between 21:36:50 and 22:02:50 UTC on Nov 03 2016.
 

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 12:05, Wednesday 09 November 2016 (31367)

Here is a frequency coupling TF calibrated into meters per hertz, using the above data.

The calibration uses the whitening gain (12 dB), the digital gain (0.36 ct/ct), the ADC gain (216 ct / 40 V), the demod gain and transimpedance (2600 V/W), and an assumed CARM plant with a dc gain of 13 mW/Hz and a pole at 0.63 Hz. The numbers for the plant come from OLTF budgeting from O1 (so these numbers are quite old and may have changed).

Images attached to this comment
Displaying reports 54241-54260 of 84759.Go to page Start 2709 2710 2711 2712 2713 2714 2715 2716 2717 End