Displaying reports 64161-64180 of 84437.Go to page Start 3205 3206 3207 3208 3209 3210 3211 3212 3213 End
Reports until 11:34, Monday 24 August 2015
H1 AOS (DetChar)
paul.schale@LIGO.ORG - posted 11:34, Monday 24 August 2015 - last comment - 12:30, Monday 24 August 2015(20823)
DQ Shift 20 August 00:00 UTC - 23 August 23:59 UTC

- Duty Cycle: 54%

- range: 75 - 85 Mpc

- PRM M3 LL coil driver caused noise in 10-60 Hz range on Friday, may have been responsible for some loud glitches

- Also on Friday there were some strange lines in the strain spectrogram at around 10Hz

- loud glitches that cause brief, large drop in range that we saw in ER7 continue; the rate is improved

- link to full DQ shift

Comments related to this report
sheila.dwyer@LIGO.ORG - 12:30, Monday 24 August 2015 (20824)CAL

Please note that the range on the summary pages is not correct.  The range displayed in the control room has been hovering around 60-65 Mpc, and this is much more realistic, although not yet blessed by the calibration group. 

H1 CAL (CAL)
darkhan.tuyenbayev@LIGO.ORG - posted 10:54, Monday 24 August 2015 (20819)
DARM OLGTF model for ER8

JeffreyK, Kiwamu, Darkhan

Overview

A DARM OLG TF model and its parts, sensing and actuation functions, are used for calculating the interferometer strain, h(t), and estimation of uncertainty in reported h(t).

On last Thursday we put together a DARM OLGTF Matlab model for ER8/O1 and compared it to a DARM OLGTF measurement taken on Aug 17, 2015. This model is mainly based on a similar model for ER7 (LHO alog 18769). Currently the model agrees with the measurement to only about +/-10% in magnitude and +/- 5 deg up to 200 Hz. So there's still work need to be done, probably changing parameter file needs some fine tuning of possibly following parameters: optical gain, CC pole frequency, ESD zeros and poles, ESD gain.

Details

Please, see a summary of things to be aware of when using this model (mostly listed differences from ER7 model):

[ol, par] = H1DARMmodel_ER8('par_file');

freq = 10 : 1 : 100;

G = par.G.getFreqResp_total(freq);

A = par.A.getFreqResp_total(freq); % total actuation function

% frequency responses of actuation stages can be obtained similarly

A_tst = par.A.getFreqResp_TST(freq);

% frequency responses of C with and without CC pole

C = par.C.getFreqResp_total(freq);

C_res = par.C.getFreqResp_noCavPole(freq);

We still need to take more DARM OLGTF and PCAL to DARM TF measurements and compare them to better estimate DARM model parameters.

The model was uploaded into calibration SVN (r1095):

CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/H1DARMOLGTFmodel_ER8.m

The parameter file associated with measurement taken on Aug 17 is in the same directory:

CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/DARMOLGTFs/H1DARMparams_1123894143.m

I believe that these scripts are in a reasonable shape to try it with LLO DARM parameters.

Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 10:42, Monday 24 August 2015 (20822)
HEPI Fluid Levels Checked--all good--no leaks--Accumulators would appear charged

The fluid levels are essentially unchanged since the end of July.  The EndX is down <1/16" but I'll wait for more data to claim a trend from a leaky Accumulator.  No further HEPI Maintenance needed tomorrow.

H1 SEI
thomas.shaffer@LIGO.ORG - posted 10:21, Monday 24 August 2015 (20821)
EX BRS Restarted

BRS software crashed at the end of last week. I got a chance to head to EX and restart the code from the desktop in the rack room.

I kept the damper OFF for now to see whether or not it is rung up.

H1 CAL (ISC)
jeffrey.kissel@LIGO.ORG - posted 09:49, Monday 24 August 2015 (20818)
Sketch of the Plan for LHO's Calibration Week
J. Kissel, K. Izumi, S. Karki, D. Tuyenbayev, R. Savage

I attach a picture of the whiteboard where we've sketched out our plan for the week. We've gone through T1500443, taken off items that we've already managed to capture before this week, and prioritized the remaining tasks accordingly.

Stay tuned for daily updates on progress.
Images attached to this report
Non-image files attached to this report
H1 CAL (ISC)
jeffrey.kissel@LIGO.ORG - posted 09:05, Monday 24 August 2015 (20817)
IFO Down for Calibration Measurements
J. Kissel, K. Izumi

At 16:02 UTC, we've taken the IFO down to begin calibration measurements.

On today's docket:
- Actuation function frequency dependence checks
    - UIM, PUM Coil Driver TFs
    - ESD LVLN Driver TFs
- Sensing function frequency dependence checks
    - OMC DCPD AA Chassis
    - OMC DCPD PreAmp (with single bounce IFO)
H1 General
edmond.merilh@LIGO.ORG - posted 08:02, Monday 24 August 2015 (20816)
End of Shift Summary and Lock Log

ALL TIMES IN UTC

Science Mode Checklist: (beginning of shift)

Activity Log:

LOCK LOG:

Shift Summary:

H1 General
edmond.merilh@LIGO.ORG - posted 06:30, Monday 24 August 2015 (20815)
IFO set to Observing Mode

13:28UTC OIB and OOM set to Undisturbed/Observing

H1 General
edmond.merilh@LIGO.ORG - posted 05:11, Monday 24 August 2015 - last comment - 05:13, Monday 24 August 2015(20813)
Switching IFO to Observation Mode

ALL TIMES IN UTC

 

Science Mode Checklist:

Activity Log:


Comments related to this report
edmond.merilh@LIGO.ORG - 05:13, Monday 24 August 2015 (20814)

12:07 LockLoss. 

  1. 5.0113km E of Ust'-Kamchatsk Staryy, Russia2015-08-24 11:51:01 UTC31.7 km
H1 ISC (GRD)
evan.hall@LIGO.ORG - posted 04:49, Monday 24 August 2015 - last comment - 12:33, Monday 24 August 2015(20811)
Some cHard/PRC WFS investigation

Sheila, Evan

We looked again at the situation with the 45 MHz REFL WFSs, which are used as sensors for the PR3 ASC loop. In the end, we didn't implement any changes to the sensors or the associated loops.

We were motivated by the following:

  1. The current demod phases for these WFSs simply do not make sense; we expect that they should be similar (since the analog delays should be fairly well matched), but instead they are scattered by 100+ degrees.
  2. The cHard and PR3 loops are strongly cross-coupled. We would like to be able to turn up the gain of cHard without impressing extra motion from other optics into DARM. [20523, 20497]
  3. Any perturbation in the PR3 seems to couple into the SRC loops. We already know that the SRM loop is quite delicate, and we would like to get rid of this coupling if possible.

We tried the following:

After that, we couldn't get to full power because of an oscillation that showed up in dHard pitch when going to 20+ W. (We've seen this before, and it seems to be distinct from the angular instability mentioned above.) To get around this, we had to slightly beef up the resonant gain that gets turned on in dHard pitch when the power is increased.

Also, there were some small maintenance tasks that we did:

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 12:33, Monday 24 August 2015 (20825)

Two of the chaanges that we made last night we kept. 

With the new phasing for refl 45, it was no longer a good sensor to use in DRMI, so we changed PRC2 in this configuration to using the sum of refl A and B 9I.  This is in the DRMI guardian and works fine, so we've left it there. 

We left the DC coupled OpLev off, we think the cage servo will have less drift. 

H1 General
edmond.merilh@LIGO.ORG - posted 03:54, Monday 24 August 2015 (20812)
Mid-Shift Update: OWL

ALL TIMES IN UTC

On my arrival, Evan, Sheila and Dan on site (of course Jim also). Not really any wind to speak of (~10mph). Minor earthquake activity in the last couple of hours after about 5 hours of quiet. Everyone gone except for Evan.

 

Science Mode Checklist: (since beginning of shift)

Activity Log:

H1 General
jim.warner@LIGO.ORG - posted 23:59, Sunday 23 August 2015 (20809)
Shift Summary

Quiet night again.

IFO was locked when I arrived, but was knocked out by an earthquake.

Sheila and Evan have been working on ASC improvements since.

H1 General (DetChar, GRD, SUS)
cheryl.vorvick@LIGO.ORG - posted 16:03, Sunday 23 August 2015 - last comment - 00:11, Monday 24 August 2015(20808)
Ops Day Summary:

Lock loss where SRCL went first.

Guardian code issue stalled progress to Low Noise, now fixed.

ETMX PUM needed to be reset.

IFO has been locked for 2 hours and range is above 60MPC.

Currently in commissioning mode - Sudarshan, Sheila, and Evan are here.

Comments related to this report
sheila.dwyer@LIGO.ORG - 00:11, Monday 24 August 2015 (20810)

just to clarify, it was the UIM driver that needed to be reset

H1 DetChar
cheryl.vorvick@LIGO.ORG - posted 15:38, Sunday 23 August 2015 (20806)
Lock Loss at 17:46:26UTC - SRCL went first, then PRCL

Plot attached shows SRCL goes at -30 seconds, then PRCL goes at -12 seconds.

Images attached to this report
H1 GRD
cheryl.vorvick@LIGO.ORG - posted 13:46, Sunday 23 August 2015 - last comment - 15:39, Sunday 23 August 2015(20800)
H1 issues and relocking

Lock Loss right after PRM saturation - lock loss plot shows an issue in SRCL came first, then PRCL responded, then lock loss

- plot attached shows PRM _M3_LOCK_L_OUTPUT 

--- signal changes directions at 17:46:14UTC

--- exceeds it's normal range at 17:46:17UTC

--- abrupt change of the signal at 17:46:22UTC

--- signal exceeds it's normal range (negative) at 17:46:25UTC, Lock Loss

 

Relocked:

- didn't make it through RF_DARM

 

Relocked:

- didn't make it through RF_DARM, and I tried to diagnose it, but couldn't, so put the IFO Mode to "unknown,"

 

Guardian Code issue, corrected:

- Sheila arrived and she diagnosed the problem - Guardian code was waiting for OMC_LOCK to be in "ready to hand off" but OMC wasn't ready.

- Sheila corrected the code so now it only looks at the two arms to see if they are ready.

 

LSC_LOCK was waiting for OMC to be ready, but OMC wasn't ready, so we cleared that and tried to go on t DARM_WFS and the IFO made some progress but then lost lock.

 

 

Relocked

- lost lock at DARM_WFS again - reason unknown.

 

ETMX Coil issue, corrected:

- after lock loss, ETMX coils died, Sheila went to EX to fix.

 

Back in Observing/Undisturbed Mode:

- ETMX fixed, relocking went well, and as of 20:36UTC Obs/Und Mode bit set.

 

NOTE: on the observatory mode screen

I used the UNKNOWN mode for locking issues (since the cause was unknown to me) and for the ETMX fix (because Corrective Maintenance just didn't seem to fit what was an equipment failure).

Comments related to this report
cheryl.vorvick@LIGO.ORG - 15:32, Sunday 23 August 2015 (20805)

ETMX coils didn't actually die... it was the PUM driver, and it was reset... 

Repairs planned for Tuesday Maintenance.

H1 General
travis.sadecki@LIGO.ORG - posted 10:56, Friday 21 August 2015 - last comment - 15:47, Sunday 23 August 2015(20744)
PCal line turned back on

Sudarshan reports that a PCal line was turned off sometime last night.  He is turning it back on at 17:53.

Comments related to this report
sudarshan.karki@LIGO.ORG - 11:30, Friday 21 August 2015 (20747)

Darkhan, Sudarshan

Pcal Lines got turned off last night during a pcal sweep measurements (LHO alog 20734 and  20732) because the optical follower servo got unlocked. We  turned two lines one at 36.7 Hz and the other one at 331.9 Hz back on. We ramped it slowly to avoid any lock loss but we still saw some drop in the range. We left the higher frequency line at 1083.7 Hz off for now. We will turn this back on during the comissioning period or next lockloss opportunity.

Attached is a trend of  Optical Follower Servo error signal showing when the lines got turned off.  (around 2015-08-21 07:20:00 UTC)

Images attached to this comment
laura.nuttall@LIGO.ORG - 13:54, Friday 21 August 2015 (20754)

Are we meant to be able to see the PCal lines in the normalised spectrogram of DARM? You can see them disappear and turn on again at about the times you mention, see the first plot (this is GDS strain). Also PCal End Y doesn't look so happy, see second plot. Plots were taken from the PCal part of the summary pages

Images attached to this comment
sudarshan.karki@LIGO.ORG - 14:47, Friday 21 August 2015 (20759)

Yes, Pcal line are supposed to appear in h(t).

Also, the third line at 1083.7 Hz is turned back on after the lockloss.

corey.gray@LIGO.ORG - 22:43, Friday 21 August 2015 (20773)

What's the best way for Operators to confirm whether PCal (and DARM) Cal Lines are present?  (seeing Excitation on CDS Overview?  looking for lines on DARM spectra?  Navigating to Calibration Line medms?)

Let us know and we can put this in checklists for operators to check.

sudarshan.karki@LIGO.ORG - 15:47, Sunday 23 August 2015 (20804)

I made  a DTT template which has all the calibration lines  on it. May be we can arrange to display this on the screen (A screenshot is attached.).  The template sits on the following location.

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/Templates/ Calibration_line_template.xml

The other way  is to head to PCAL medm screen and look at the OFSPD plot on the screen. If there is no excitation this plot should be flat.

Images attached to this comment
H1 ISC
peter.fritschel@LIGO.ORG - posted 15:48, Wednesday 05 August 2015 - last comment - 10:08, Monday 24 August 2015(20270)
SRCL, MICH, and PRCL: open loop and residual noise spectra

Using the calibrated DRMI channels created and described by Kiwamu in entry 18742, I grabbed data from the lock of August 3, 2015, starting at 04:20:00 UTC. The attached 4 page PDF shows spectra of the open loop and residual displacement noise for SRCL, MICH and PRCL. The 4th page shows the coherence of SRCL with the other 2 degrees of freedom.

Degree of freedom Residual rms Shot noise level
SRCL 8 pm 1.3 x 10-15 m/rtHz
MICH 3 pm 1.5 x 10-16 m/rtHz
PRCL 0.8 pm 4 x 10-17 m/rtHz

The SRCL spectra has a curious shape: it comes down quickly with frequency to 10 Hz, then is fairly flat from 10 Hz to 50 Hz, then falls by a factor of 5 or so to the (presumed) shot noise level that is reached above 100 Hz. What is this noise shelf between 10 Hz and 80 Hz? That is exactly the region where the SRCL noise coupling to DARM is troublesome. Our usual approach is to send a SRCL correction path to DARM to reduce the coupling, but this spectrum shows that there should also be some gain to be had by reducing this noise shelf.

The last page of the PDF shows the coherence between SRCL and MICH & PRCL, and it indicates that the SRCL noise shelf could be coupling from PRCL noise -- the coherence is fairly high in this band, though not unity. This suggests that the DRMI signals could use some of the demodulator phase and input matrix tuning that Rana has recently done on L1, reported in LLO log entry 19540.

To complete this log entry, it would be useful if someone at LHO could add the open loop transfer functions for each loop (models), and other pertinent info such as DC photocurrents for these detectors and the input matrix coefficients.

Non-image files attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 17:54, Saturday 22 August 2015 (20789)

The shelf appears to be gain peaking in SRCL. We have an 80 LPF to get rid of SRCL control noise in the bucket, but it makes the control noise from 30 to 60 Hz a bit worse.

I had the filter off between 2015-08-23 00:36:00 Z and 00:39:00 Z. The attachment shows the error and control signals with filter off (dashed) versus filter on (solid).

Images attached to this comment
keita.kawabe@LIGO.ORG - 10:08, Monday 24 August 2015 (20820)

Evan, is the shelf in Peter's open loop spectrum there because of OLTF model without LPF? Otherwise, we still need to investigate.

H1 ISC (ISC)
hang.yu@LIGO.ORG - posted 11:37, Friday 24 July 2015 - last comment - 14:32, Sunday 23 August 2015(19904)
Estimation of beam position

Kiwamu, Hang

We did an estimation of the beam position on test masses based on the a2l gains that gave us best decoupling.

The result was shown in the first image attached. The blue line indicated the boundary of L3 and the red spot the position of the beam on the test mass. It seemed that the beams were <~1 cm off center.

  Trans. [mm] Vert. [mm]
ITMX 3.0 -7.3
ITMY -6.3 -3.5
ETMX 5.3 -4.7
ETMY -2.7 4.1

===================================================================================================================================

In case that you are interested in how we obtain the results:

The basic idea is to excite the pitch (yaw) motion of L2 stage, and let this excitation go through both

1): the L2->L3 P2P (Y2Y) path, and

2): L2->L2 P2L, and then L2->L3 L2L and L2P.

The ratio of L3's L over L3's P will then give us the vertical position of the beam on test masses. See the second picture for a graphic representation.

===================================================================================================================================

The code to re-run this analysis is available at:

/opt/rtcds/userapps/release/isc/h1/scripts/a2l

You can do the analysis by entering

./run_GrabBeamSpot.sh

in the command line

Images attached to this report
Comments related to this report
rana.adhikari@LIGO.ORG - 14:32, Sunday 23 August 2015 (20802)SUS

But isn't there a static component of L2P -> L3L that we have to worry about? If there is something like that it seems like it would be static, but it might shift the absolute beam position by some amount.

Displaying reports 64161-64180 of 84437.Go to page Start 3205 3206 3207 3208 3209 3210 3211 3212 3213 End