Displaying reports 54021-54040 of 84767.Go to page Start 2698 2699 2700 2701 2702 2703 2704 2705 2706 End
Reports until 11:40, Friday 18 November 2016
H1 ISC
jenne.driggers@LIGO.ORG - posted 11:40, Friday 18 November 2016 (31607)
2 OMC values not-monitored in Observe.snap

I have not-monitored 2 channels in the OMC SDF Observe.snap file.  These are 2 channels that are written by guardian, and will be different every lock.

The channels are: H1:OMC-PZT2_OFFSET (scanned around to find OMC resonance) and H1:OMC-READOUT_X0_OFFSET (sets the DARM offset to keep OMC DCPDs at 20mA, no matter the PSL power).

Images attached to this report
H1 CAL (CAL)
jeffrey.kissel@LIGO.ORG - posted 11:06, Friday 18 November 2016 - last comment - 03:46, Monday 21 November 2016(31601)
Fourth Round of ER10 Calibration Measurements Complete -- Second at 30 W
J. Kissel, D. Tuyenbayev

Darkhan and I was able to get another round of calibration sweeps in last night, just after Sheila finished up her alignment test (LHO aLOG 31599). This set is at 31.92 W, with SRC1 Loops Closed -- and the second set of data with the anticipated O2 configuration.

Datasets live here: 
Sensing Function:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/DARMOLGTFs
2016-11-17_H1_DARM_OLGTF_4to1200Hz_fasttemplate.xml
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/PCAL
2016-11-17_H1_PCAL2DARMTF_4to1200Hz_fasttemplate.xml

Actuation Functions
2016-11-17_H1SUSETMY_L1_iEXC2DARM.xml
2016-11-17_H1SUSETMY_L1_PCAL2DARM.xml
2016-11-17_H1SUSETMY_L2_iEXC2DARM.xml
2016-11-17_H1SUSETMY_L2_PCAL2DARM.xml
2016-11-17_H1SUSETMY_L3_iEXC2DARM.xml
2016-11-17_H1SUSETMY_L3_PCAL2DARM.xml


I'd found that I'd stored the wrong channels in my new templates for the exploration of the UIM/L1 high frequency actuation on 2016-11-12 (LHO aLOG 31433), so I repeated those measurements as well storing the right channels this time:
2016-11-17_H1SUSETMY_L1_iEXC2DARM_HFDynamicsTest_100-250Hz.xml
2016-11-17_H1SUSETMY_L1_iEXC2DARM_HFDynamicsTest_250-350Hz.xml
2016-11-17_H1SUSETMY_L1_iEXC2DARM_HFDynamicsTest_300-500Hz.xml
2016-11-17_H1SUSETMY_L1_iEXC2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml
2016-11-17_H1SUSETMY_L1_PCAL2DARM_HFDynamicsTest_100-250Hz.xml
2016-11-17_H1SUSETMY_L1_PCAL2DARM_HFDynamicsTest_250-350Hz.xml
2016-11-17_H1SUSETMY_L1_PCAL2DARM_HFDynamicsTest_300-500Hz.xml
2016-11-17_H1SUSETMY_L1_PCAL2DARM_HFDynamicsTest_90-400Hz_SweptSine.xml

Analysis will be posted today (it's finished, we now just need to document it all), and we plan on updating the DARM model and front-end calibration by Monday.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:50, Friday 18 November 2016 (31609)CAL, CSWG, DetChar, SUS
The high-frequency dynamics measurements quoted in this aLOG have been analyzed. See results in LHO aLOG 31603.
darkhan.tuyenbayev@LIGO.ORG - 18:14, Saturday 19 November 2016 (31649)CAL

J. Kissel, K. Izumi, D. Tuyenbayev,

Overview

Actuation strengths [N/ct] for all three stages have been calculated with MCMC method. In In this analysis we used data from last set of measurements taken on Nov 17 (see above), together with measurements from Nov 7, 8, 10 and 12 (see LHO alogs 31303, 31371, 31403, 31433). The calculated actuation coefficients are:

KU = 8.1648-8 N/ct

KP = 6.844-10 N/ct

KT = 4.395-12 N/ct

The H1DARM model parameters were updated using these values, particularty:

UIM_NpA = 1.739; [N/A]
PUM_NpA = 0.0334; [N/A]
TST_NpV2_y = 1.612e-10; [N/V^2]

We will double check the overall DARM loop model, with the updated sensing and actuation, by comparing it to DARM loop TF measurements.

Notice that TST actuation coef came out as a negative quantity, we believe that there is a "-1" missing in the model of this stage.

Details

For this analysis we took each actuation stage to DARM TF and PCALY to DARM TF measurements at the same frequency vector and used only data points with coherences above 0.9, we adopted a Matlab script used at LLO for this part of the analysis (see EvanG's LLO alog 29438). For each actuation stage i, the test point excitation to DARM TF is

iEXC2DARM = Ai,meas * C / (1 + G)

and PCALY to DARM is

PCALY2DARM = C / (1 + G)

The ratio of the two gives:

iEXC2DARM / PCALY2DARM = Ai,meas

Then we divided this my the model of the given stage without the N/ct coefficient, Ai,model / Ki,model = Fi,model, gives measurement of the frequency-independent N/ct coefficient:

Ai,meas / Fi,model = Ki,meas

Then, we used GWMCMC library (https://github.com/grinsted/gwmcmc) for fitting amplitude and phase of the N/ct coefficient for each stage (if the frequency dependent part of the model is correct, then the phase should be 0 deg). The log likelihood function used for fitting is

logLike = log( ∏( 1 / sqrt(2πσi2) exp( - (Ki,meas - Kfit)2/(2σi2) ) )

Fit results for magnitudes are given above and the phases are at the order of 10-3 deg.

The KU, KP and KT coefficients calculated from multiple-frequency transfer function measurements differ from earlier estimations from single line (LHO alog 31344) by 1.7%, 5.3% and 3.1% for UIM, PUM and TST stages. Possibly some unaccounted systematics in the frequency reponses of the DARM model near 35 Hz (the previous analysis was done with the DARM model for ER9).

Non-image files attached to this comment
darkhan.tuyenbayev@LIGO.ORG - 17:47, Sunday 20 November 2016 (31668)CAL

Izumi K, Kissel J, Tuyenbayev D,

We used ER10 model to re-run an earlier actuation strength analysis using calibrartion line data from Nov 3 - Nov 8 (LHO alog 31344). The original analysis was done with the DARM model in which the positive N/ct sign was used for TST stage actuation, the correct KT sign must have been negative. Below we list the updated results from this single-line analysis, the values are taken from GPS time interval [1162369920 1162413500]:

KU = 8.613 × 10-8 ± 3.204 × 10-10 N/ct
KP = 6.802 × 10-10 ± 2.254 × 10-12 N/ct
KT = -4.341 × 10-12 ± 1.339 × 10-14 N/ct

Notice this analysis is used as an additional check of the multiple-frequency analysis (see above). The DARM model parameters for ER10/O2 will be based on the multiple-frequency analysis results (refined numbers and comparison results are coming soon).

Non-image files attached to this comment
darkhan.tuyenbayev@LIGO.ORG - 03:46, Monday 21 November 2016 (31677)CAL

Izumi K, Kissel J, Tuyenbayev D,

Overview

We calculated the actuation coefficients for the H1 DARM reference time model. For UIM (L1) and PUM (L2) stages the N/ct coefficients were fit based on actuation TF measurements on Nov 7, 8, 10, 12 and 15. These numbers have been reported earlier (see above). The TST actuation strength will have a trend over long time period due to charge accumulation, thus for TST stage it is better to estimate the coefficient based on measurements taken within a short period of time. Since we set the reference sensing function parameters based on measurements taken on Nov 12, for estimation of the TST (L3) stage actuation we decided to use measurements around that date, particularly measurements from Nov 10 and 12.

Contributions from each of the actuation stages to the overall DARM response drops as 1/f6, 1/f4 and 1/f2, for this reason MCMC (and LSQ) fitting were restricted to [0 10] Hz, [0 200] Hz and [0, 200] Hz for UIM, PUM and TST stages respectively.

Below are the resulting N/ct values, these values:

KU = 8.1648 × 10-8 N/ct (±  0.074% 1-σ)
KP = 6.844 × 10-10 N/ct (± 0.018% 1-σ)
KT = -4.389 × 10-12 N/ct (± 0.031% 1-σ)

And the H1DARM model were updated in the following way (only the N/V2 for TST stage is different from LHO alog 31649):

UIM_NpA = 1.739;         % [N/A]
PUM_NpA = 0.0334;        % [N/A]
TST_NpV2_y = 1.6097e-10; % [N/V^2]

New EPICS values used for DARM time-dependent parameters have been calculated with the updated H1 DARM model for ER10/O2 (see attachment 1).

Comparisons

MCMC and LSQ methods gave consistent results, fractional discrepancies between the two were at the order of 10-5 (LSQ fit was done only for magnitude).

Discrepancies between the new values and the ones currently installed in the CAL-CS front-end model are:

UIM: 0.05% (compared 8.1689 × 10-8 N/ct, the currently installed, old value)
PUM: 0.05% (compared to 6.8407 × 10-10 N/ct)
TST: 3.42% (compared to 4.239 × 10-12 N/ct)

Discrepancies between these values and an updated single-line analysis results (see LHO alog 31668 above) are 5.5% (UIM), 0.6% (PUM) and 1.4% (TST). A larger discrepancy between MCMC and the single-line analysis for UIM, we believe, is mostly due to 5-10% systematic errors in the UIM suspension model at ~36 Hz (see a residual plot attached to Kiwamu's LHO alog 31427).*

Although, the TST stage coefficient was calculated based on Nov 10th and 12th measurements, discrepancies between the values estimated for each of the 5 measurements (Nov 7 - 17), are within 0.5% (see attachment 2).

*Check out Jeff's LHO alog 31603 for more UIM HF investigations.

Details

TST stage fitting plots are attached below (see attachments 3 and 4). UIM and PUM fitting results did not change (see previous report above, LHO alog 31609).

The new EPICS values for DARM time-dependent parameters are committed to

${CalSVN}/Runs/ER10/H1/Scripts/CAL_EPICS/D20161120_H1_CAL_EPICS_VALUES.m

The up-to-date H1 DARM model parameters are commited to CalSVN:

${CalSVN}/Runs/ER10/Common/params/IFOindepParams.conf              r3752
${CalSVN}/Runs/ER10/H1/params/H1params.conf                        r3826
${CalSVN}/Runs/ER10/H1/params/2016-11-12/H1params_2016-11-12.conf  r3786

DARM model scripts (SRC detuning TF was modified to include Q-factor at r3814):

${CalSVN}/Runs/O2/DARMmodel/*  r3814

Actuation coefficient fitting script was uploaded to

${CalSVN}/Runs/ER10/H1/Scripts/FullIFOActuatorTFs/fitActCoefs_Npct.m  r3829

And the results are at

${CalSVN}/Runs/ER10/H1/Results/Actuation/2016-11-20_H1_SUSETMY_*.pdf

Non-image files attached to this comment
H1 AOS
sheila.dwyer@LIGO.ORG - posted 10:48, Friday 18 November 2016 (31599)
last night's alog

I meant to post this last night, will update soon.

Sheila, Keita, Jenne

A more complete alog will be coming, but this afternoon we once again measured the sensing matrix for refl WFS.  THen we attempted to increase the recycling gain by changing SOFT pitch offsets (not very effective) and using the PR3 spot move (equivalent to change POP A offsets).  We were able to increase the recycling gain from about 30.25 to around 31 by moving PR3 spot position.  As we did this, the jitter peaks changed, with the peaks around 300Hz become better, the 260 Hz peak that we can tune away with IMC DOF1P offsets getting worse, and perhaps the broad lump coming back somewhat.  (I think that we have moved back towards the alignment where the lump was a problem, but will check latter).  

Moving the spot position on PR3 using yaw was more effective at increasing the power recycling gain (we approached 32), and I didn't see a change in the noise while doing this.  

Since the noise was worse after these changes, I took them all out.  If I get a chance latter, I would try moving yaw and not pitch to see if we can get some more recycling gain without making the nosie worse. 

LHO VE
chandra.romel@LIGO.ORG - posted 10:34, Friday 18 November 2016 - last comment - 16:39, Friday 18 November 2016(31597)
RGA filaments ON
WP 6328

This morning we turned ON filaments of RGAs at EY and corner......from the control room! Gerardo will set the IP address for EX to complete WP. 

I was disappointed to find that we cannot connect to multiple devices at one time to monitor multiple scans in RGA software. Contacted vendor about this. Analog signal monitoring via CDS will help (ECR 1600307).
Comments related to this report
chandra.romel@LIGO.ORG - 16:39, Friday 18 November 2016 (31629)
We just needed the multiplexer software key so now we are connected to multiple RGA devices!
H1 SUS
hugh.radkins@LIGO.ORG - posted 10:26, Friday 18 November 2016 - last comment - 15:59, Friday 18 November 2016(31595)
Added L2_DRIVEALIGN_L2P_GAIN to OBSERVE.snap Not Monitored list for TMs

JeffK & HughR

This is to be ready for changes resulting from the A2L running on a regular basis.  While at it I snapped a view of the TMs L2 Drive Align L2P filter banks.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:17, Friday 18 November 2016 (31604)

These channels should probably be re-monitored.  You've unmonitored the L2Ps, when it's actually the P2Ls (and Y2Ls) that will change when we run A2L.  The P2L and Y2L gains are already not monitored for all the test masses.  I have re-monitored the L2P gains.

hugh.radkins@LIGO.ORG - 15:59, Friday 18 November 2016 (31620)

Doh! Smackforehead.

H1 OpsInfo
terra.hardwick@LIGO.ORG - posted 10:10, Friday 18 November 2016 - last comment - 15:45, Friday 18 November 2016(31593)
Op requests whenever we relock

Whoever is in the chair next when we have to relock (days from now I'm sure...), please:

Thanks a bunch - the past few days of everyone helping play this long timescale PI game has been super helpful. 

Comments related to this report
edmond.merilh@LIGO.ORG - 10:23, Friday 18 November 2016 (31594)

When you say a2l, do you mean the trio of them or just the one original, main one?

terra.hardwick@LIGO.ORG - 10:32, Friday 18 November 2016 (31596)

Ya just the main one: a2l_min_LHO. Thanks Ed.

sheila.dwyer@LIGO.ORG - 15:45, Friday 18 November 2016 (31619)

General comment for operators:

when you run a2l make sure you take the observatory mode to commisioning first, then you can put it back when the script finishes.  This way we can avoid confusing people.  Once we have SDF tied into the intention bit this would automatically drop us out of observing. 

H1 ISC
hugh.radkins@LIGO.ORG - posted 09:57, Friday 18 November 2016 - last comment - 11:36, Friday 18 November 2016(31591)
Channels added to the LSC not monitored list

Many of the gain changes I just accepted into the LSC OBSERVE.snap are showing as differences in the safe.snap.  With conference of JeffK, we are pretty positive these are values changed by Guardian.  So, I am adding these values to the safe.snap Not Monitored list--see attached.  They are ASAIR, POPAIR, POP, REFLAIR, & REFL: A & B, RF18/90/9/45, I & Q gains.  18 total channels.  This makes 125 not monitored channels yet with these additions, there are only 62 differences for all setpoints.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:36, Friday 18 November 2016 (31606)

I think these should be re-monitored in the safe.snap file.  These values (the ones that are the setpoints in the safe.snap screenshot) are written in the ISC_LOCK DOWN state.  If they are not correct, we may have trouble locking.  They are then changed by guardian to the values in the Observe.snap screenshot when we reduce the modulation depths of the 9 and 45 MHz.  So, the values that we want will be different in the safe and observe snap files, but we probably want to be monitoring them in both.

Actually, rethinking on it, Hugh's not-monitoring of these channels in the safe.snap file is totally consistent with everything we've been doing lately (not-monitoring channels that are written explicitly by guardian).  Whether our current strategy makes any sense is a larger conversation, but these channels are probably fine not being monitored.

H1 PEM (OpsInfo, SYS)
richard.mccarthy@LIGO.ORG - posted 09:41, Friday 18 November 2016 - last comment - 10:07, Friday 18 November 2016(31590)
End X VEA temperature
Raised the Heater setpoint from 8ma to 9ma.  We had approximately a 1/2 deg F drop in temperature in the VEA last night.  
Also raised AHU-3 heaters from 3ma to 5ma to turn one stage on.
Comments related to this report
john.worden@LIGO.ORG - 10:07, Friday 18 November 2016 (31592)

I noticed that the LVEA dipped a little yesterday morning so I increased 1A, 1B, 4, 5 all by 0.5 ma to 8.0 ma.

H1 CAL (CAL, DetChar)
jeffrey.kissel@LIGO.ORG - posted 09:16, Friday 18 November 2016 - last comment - 15:33, Friday 18 November 2016(31589)
PCALX Roaming Calibration Line Frequency Changed from 4301.3 to 4501.3 Hz
Beautifully high duty cycle over the past few says. Nice work team! 

Current Schedule Status:
Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W (see LHO aLOG 31546)
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC    Nov 18 2016 17:08:49 UTC      days     @ 30 W            
4501.3       40k                      10:00                   39322.0           Nov 18 2016 17:08:49 UTC                
4801.3       40k                      10:00  
5001.3       40k                      10:00
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 13:44, Friday 18 November 2016 (31611)DetChar
The 1083.7 Hz calibration line was turned OFF for a brief period (~1-2 hours) during this current 4501.3 Hz stretch. See LHO aLOG 31610 for details.
jeffrey.kissel@LIGO.ORG - 15:33, Friday 18 November 2016 (31618)
1083.7 Hz calibration line restored just after the lock loss at 2016-11-18 23:30 UTC.
H1 ISC
hugh.radkins@LIGO.ORG - posted 09:12, Friday 18 November 2016 - last comment - 16:01, Friday 18 November 2016(31588)
High Precision ASC & LSC Round off changes saved in OBSERVE.snaps

First attachment is the ASC changes accepted.  All the ones accepted are gains that have been rounded off to 4 places rather than 10.  I did miss one matrix value (circled) but I've corrected that in the file directly and reloaded that to the FE.  The 23 remaining differences are filters, offsets and matrix changes requiring more scrutiny.

For the LSC, the same applies.  There is one offset difference remaining--see attached.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:23, Friday 18 November 2016 (31605)

The one channel remaining in the LSC SDF was H1:PSL-POWER_SCALE_OFFSET, which is changed by the LASER_PWR guardian as it changes the PSL power into the vacuum.  This will be different every lock, so I have un-monitored it in the Observe.snap file.  Also, TJ has changed the guardian to round it to 4 decimal places, which is more than plenty of precision.

jenne.driggers@LIGO.ORG - 11:46, Friday 18 November 2016 (31608)

Looking right now, everything left in the ASC SDF is stuff that is actively being worked on (SOFT offsets, input matrix for PRC2, etc), so we don't know yet what we'll run with for O2.  These should all stay monitored.

All of the filters in the DC loops were notches that were turned on for a sensing matrix measurement, and should have been turned off.  When I turned the notches off, the diffs went away, so we already had the correct settings accepted.

hugh.radkins@LIGO.ORG - 16:01, Friday 18 November 2016 (31621)

Thanks for the fine-tuning and details--just what we need for good control--Thanks Jenne--H

H1 ISC
terra.hardwick@LIGO.ORG - posted 05:22, Friday 18 November 2016 - last comment - 11:05, Friday 18 November 2016(31583)
Mode Temperature Dependence cont.

Aidan, Terra

A continuation of alog 30522

Previously we'd found that frequency drift over a lock stretch is mode dependent - differential drumhead mode drifts more than that same optic's drumhead mode - but surmised that the ratio of (change of frequency / frequency) between two modes would be constant. However, this assumed a spacially uniform change in temperature --- fm = g(T) --- when a more realistic assumption is some radial dependence of T, so: 

fm = g(T(r)), where r is radial vector

Since the energy distribution of a given mode is also dependent on r, we can expect some modally unique self heating response. In other words, the more overlap between a given mechanical mode and the hot spots of the optic, the larger the frequency drift we'd expect that mode to have. 

I've looked at ETMY 15009 Hz diff drumhead mode shift compared with ETMY 8158 Hz drumhead shift during twelve hours of a recent lock. 15009 Hz relative frequency change is larger than drumhead relative change and the ratio begins to level off towards a constant after about six hours. We expect (and model) the opposite - the drumhead mode would have more thermal overlap and thus would shift more. This assumes a mostly centered beam spot (or equivalently, assumes r = 0 at the center of the optic). Looking at Jenne's recent beam spot investigation, ETMY spot position was fairly centered during this time, off in yaw by a few mm. The 15009 Hz mode is differential in pitch. (I still suspect some dependence on torsional vs. longitudinal mode movement as suggested in alog 30522.)

We've started having operators run a2l more regularly and before and after powerup at times to get assurance of beam spot position. 

Images attached to this report
Comments related to this report
terra.hardwick@LIGO.ORG - 11:05, Friday 18 November 2016 (31600)

Quick look at the frequency drift for ETMY 15009 Hz and Drumhead during the first 12 hours of the current lock. Ignore the giant vertical line of glitch terribleness. Also I tried fitting the Drumhead df/f with a sum of weighted exponentials (though note that tau == b is the same for each series element) as a very preliminary comparison with thermal lens response to power step. 

Images attached to this comment
H1 ISC
terra.hardwick@LIGO.ORG - posted 02:29, Friday 18 November 2016 - last comment - 11:14, Friday 18 November 2016(31577)
32 W PI modes update

After getting wack values for PI mode ring ups (many orders of magnitude off from expected) earlier in the week, I've refit ring ups and taken new ones and gotten much more reasonable values (I wasn't looking at long enough time stretches to get accurate ring up data before). Note that we haven't had any instability in Mode3 in many days so I haven't been able to remeasure it. 

Mode # Freq Optic tau Q
3 15606 Hz ITMX TBD TBD
26 15009 Hz ETMY 316 s 15 M
27 47495 Hz ETMY 92 s 5 M
28 47477 Hz ETMY 89 s 5.2 M

Mode 3 hasn't been unstable in many days and Modes 27 & 28 are only unstable during the initial ~ 1-2 hours of transient. Attached are two 30 hour stretches of the damping output of the three modes during recent long locks (Mode3 had no output so I left off) and the simulated HOOM spacing to get an idea of when the modes are ringing up enough to engage damping loops. Left is a few days ago and right is the current lock. Note that Mode26 looks continuously unstable during the 11/16 lock, but it could be that the damping gain is triggering below an actual unstable amplitude; compare to the current lock where we set the gain for Mode26 to zero just after 19:30 (so there would be no damping output) but it has remained stable and low since then with no need to damp. 

Operators and myself are currently turning off gain and measuring ring ups during different times of lock stretches to get gains at different stages of the thermal transient. 

Images attached to this report
Comments related to this report
terra.hardwick@LIGO.ORG - 11:14, Friday 18 November 2016 (31602)

Current damping status of this now > 25 hour 32 W lock: no damping required after the first 2 hours. Attached plots again show damping loop output over the past 26 hours and HOOM spacing for reference. 

Images attached to this comment
H1 ISC
daniel.sigg@LIGO.ORG - posted 17:14, Wednesday 16 November 2016 - last comment - 10:42, Friday 18 November 2016(31554)
Frequency Noise Spectra

The attached plots show the frequency noise seen by the reference cavity (green), the IMC (red), the REFL port (blue)  and the POP port (brown). The first plot also shows the estimated in-loop suppressed noise in a lighter color as well.

The second plot shows uncalibrated traces but with a 30 kHz bandwidth. The peaks at ~7250 Hz and at ~13.6 kHz are already present in the IMC spectra when the interferometer is unlocked, and, therefore, are not introduced by the REFL servo. The I' channels are the DAQ sensor channels closest to true in-phase signals.

Non-image files attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 10:42, Friday 18 November 2016 (31598)

A few notes to the calibrations:

  • The reference cavity calibration is based on the PZT sensitivity of the Innolight laser. It will be good up to the FSS crossover.
  • The in-loop curve is based on an FSS servo model which assumes a nominal ugf, but with a crossover a factor of 2 low. This in turn produces gain peaking around 2 kHz which is required to explain the coherence with MC_F.
  • The MC_F calibration is based on the VCO calibration.
  • The in-loop curve is derived from an IMC length model with an ugf of 64 kHz.
  • The LSC REFL calibration is based on alog 30549. It agrees with the IMC model and the VCO calibration.
  • The in-loop curve is derived from a interferometer REFL model with a ugf around 20 kHz.
  • The PRC calibration is based on a simple scaling so that it agrees with in-loop REFL at 7 kHz. This is motivated by a coherence of 100% at this frequency.
Displaying reports 54021-54040 of 84767.Go to page Start 2698 2699 2700 2701 2702 2703 2704 2705 2706 End