Displaying reports 66581-66600 of 85652.Go to page Start 3326 3327 3328 3329 3330 3331 3332 3333 3334 End
Reports until 15:08, Sunday 12 July 2015
H1 ISC
sheila.dwyer@LIGO.ORG - posted 15:08, Sunday 12 July 2015 (19581)
Alignment recovery

We've been stably locked with a recycling gain of 38 at 23.3 Watts for almost 2 hours (I intentionally broke the lock).   There were some of the slow (20 second) oscillations that cause some of our locklosses durring ER7.  

When I first came in I had some trouble with locklosses durring ENGAGE_ASC.  One problem was just a typo, the other one seems to be when the gain is increased for the SRC2 loop.  I think this caused the increase in POP90 we were seeing last night, which went away.  This morning it kept increasing until the lockl dropped. I moved the transmon QPD offsets back to the pre-vent offsets, powered up to 18 Watts, turned off the ITM loops and adjusted the ITMY alingments slightly to get a decent recycling gain.    The green alignment in the arm was OK here, and the camera positions not off by more than 4 counts so I did not update the references. 

The offsets where we are stable with recycling gain of 38 and 23.3 Watts are:  

H1:ASC-X_TR_A_PIT_OFFSET       0
H1:ASC-X_TR_B_PIT_OFFSET       -0.11
H1:ASC-Y_TR_A_PIT_OFFSET       -0.128
H1:ASC-Y_TR_B_PIT_OFFSET       -0.516
H1:ASC-X_TR_A_YAW_OFFSET       -0.095
H1:ASC-X_TR_B_YAW_OFFSET       -0.067
H1:ASC-Y_TR_A_YAW_OFFSET       -0.174
H1:ASC-Y_TR_B_YAW_OFFSET       -0.1
 
The pre-vent offsets are:
H1:ASC-X_TR_A_PIT_OFFSET       -0.029
H1:ASC-X_TR_B_PIT_OFFSET       -0.158
H1:ASC-Y_TR_A_PIT_OFFSET       0.101
H1:ASC-Y_TR_B_PIT_OFFSET       -0.056
H1:ASC-X_TR_A_YAW_OFFSET       -0.007
H1:ASC-X_TR_B_YAW_OFFSET       0.105
H1:ASC-Y_TR_A_YAW_OFFSET       -0.127
H1:ASC-Y_TR_B_YAW_OFFSET       0.055
 
The "post-vent, not stable" offsets are:
caput H1:ASC-X_TR_A_PIT_OFFSET       -0.048
H1:ASC-X_TR_B_PIT_OFFSET       -0.148
H1:ASC-Y_TR_A_PIT_OFFSET       -0.118
H1:ASC-Y_TR_B_PIT_OFFSET       -0.369
H1:ASC-X_TR_A_YAW_OFFSET       -0.004
H1:ASC-X_TR_B_YAW_OFFSET       0.078
H1:ASC-Y_TR_A_YAW_OFFSET       -0.242
H1:ASC-Y_TR_B_YAW_OFFSET       -0.318
 
The new camera positions are (I did not update these since they are not verry different from the old ones):
H1:ALS-X_CAM_ITM_PIT_POS H1:ALS-X_CAM_ITM_YAW_POS H1:ALS-Y_CAM_ITM_PIT_POS H1:ALS-Y_CAM_ITM_YAW_POS
254.325
336.287
300.563
434.418 
H1:ALS-X_CAM_ITM_PIT_POS H1:ALS-X_CAM_ITM_YAW_POS H1:ALS-Y_CAM_ITM_PIT_POS H1:ALS-Y_CAM_ITM_YAW_POS
254.325
336.287
300.563
434.418
H1:ASC-X_TR_B_PIT_OFFSET       -0.11
H1:ASC-Y_TR_A_PIT_OFFSET       -0.128
H1:ASC-Y_TR_B_PIT_OFFSET       -0.516
H1:ASC-X_TR_A_PIT_OFFSET       0
H1:ASC-X_TR_B_PIT_OFFSET       -0.11
H1:ASC-Y_TR_A_PIT_OFFSET       -0.128
H1:ASC-Y_TR_B_PIT_OFFSET       -
H1:ASC-X_TR_A_PIT_OFFSET       0
H1:ASC-X_TR_B_PIT_OFFSET       -0.11
H1:ASC-Y_TR_A_PIT_OFFSET       -0.128
H1:ASC-Y_TR_B_PIT_OFFSET       -0.516
H1 ISC (ISC, SUS)
sheila.dwyer@LIGO.ORG - posted 14:26, Sunday 12 July 2015 (19579)
roll mode damping with AS 45 Q yaw

Before ER7 we noticed that we have a better signal for damping the ETMX roll mode in AS 45Q yaw than in pitch. Durring the vent we added a matrix to the ASC model to allow switching.  On Friday Nic found that the old settings for damping ETMX roll (using AS45Q PIT) were not working, so he found some settings that worked using DARM err alog 19561.  

Today I needed to damp ETMX roll again, so I tried using AS45 Yaw, this worked well, with a phase of -90 degrees relative to the settings we had for pitch (so we use bp 13.9, -60degrees, -30 degrees, -100dB and a gain of 60).  I also attempted to damp ITMX and ETMY using AS 45 Yaw (which has better SNR for these as well).    

While these settings seemed to work for each individual optic, when I turned all three on and left them on simultaneously for several minutes, they rang up all the modes.  

  ETMY ETMX ITMY ITMX
Frequency [Hz] 13.816 13.889 13.93 13.978
Filters FM3(-100dB) FM4 (bp13.9) FM2(-60deg)FM3(-100dB)FM4(bp13.9)FM7 (-30deg) FM1(+60deg) FM3(-100dB) FM4(bp13.9)

??

Gain -50 60 -80  

Reminder, the nominal settings for bounce and roll damping (with AS pit) can be found in alog18614.  

Images attached to this report
H1 SUS
sheila.dwyer@LIGO.ORG - posted 10:04, Sunday 12 July 2015 (19577)
some settings that were wrong after the vent

We've tracked down a few settings which became wrong durring our down time.  

BS OpLev yaw limit was set to 0, so we were not using yaw damping while trying to acquired DRMI (it has been working OK).

ITMY violin mode damping for mode6 had the wrong filters engaged.  This rang up the mode, meaning that we had to reduce the whitening gain for the DCPDs.  Now that the right filters are engaged the mode is coming down.  I went through and made sure that the handfull of violin mode damping settings that were not monitored are.  We use guardian to set the gains for these filterbanks, but not to choose the switch status.  

H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 02:42, Sunday 12 July 2015 - last comment - 05:16, Sunday 12 July 2015(19574)
More ASC work at high power
Sheila, Evan, Stefan,
With information for Sheila on Sun morning

We tried to operate the ASC system at full power (24W), using two different sets of QPD offsets (I'll call them pre-vent and post-vent, see burt files below).

With the pre-vent offsets we
 - The ASC system was stable at full input power
 - We had a recycling gain of about 36. (Based on transmitted power.)
 - These QPD offsets are not compatible with the current initial alignment (i.e. the Guardian will drop lock during ENGAGE_ASC - however a slow 2-min offset ramp from post-vent to pre-vent, with 20dB lower gains on the ITM loops worked)

With the post-vent offsets we
 - Get a recycling gain of 40. (Based on transmitted power.)
 - These QPD offsets are compatible with the current initial alignment. The ENGAGE_ASC step works fine.
 - Assuming the higher recycling gain is real (and not due to a difference in QPD clipping), we'd like to keep those QPD offsets because of the higher recycling gain.
 - However we get a 0.41Hz oscillation which starts at about 20W or 21W.


About this 0.41Hz oscillation:
 - It shows up in arm build-up's as 0.41Hz modulation (i.e. 1-f).
 - It is CSOFT PITCH, i.e. all 4 test mass optical levers show it exactly in phase.
 - The arm powers are exactly out-of-phase with the optical level pitch signals, i.e. when all optics point downward (highest OL value), the arm power is at a minimum. (see plot)
 - 

To deal with this mode, we switched the ITM ASC loops for PITCH to the common/differential basis (i.e. DSOFT is now DITM, and CSOFT is now CITM). At the time of this elog we were still designing a filter to stabilize the oscillation.



========================================================================================
Pre-vent QPD offsets (in /ligo/home/evan.hall/Public/Burt/ItmQPDsPre.snap burt file):
H1:ASC-X_TR_A_PIT_OFFSET 1 -2.900000000000000e-02
H1:ASC-X_TR_B_PIT_OFFSET 1 -1.580000000000000e-01
H1:ASC-X_TR_A_YAW_OFFSET 1 -7.000000000000000e-03
H1:ASC-X_TR_B_YAW_OFFSET 1 1.050000000000000e-01
H1:ASC-Y_TR_A_PIT_OFFSET 1 1.010000000000000e-01
H1:ASC-Y_TR_B_PIT_OFFSET 1 -5.600000000000000e-02
H1:ASC-Y_TR_A_YAW_OFFSET 1 -1.270000000000000e-01
H1:ASC-Y_TR_B_YAW_OFFSET 1 5.500000000000000e-02

Post-vent QPD offsets (in /ligo/home/evan.hall/Public/Burt/ItmQPDsPost.snap burt file):
H1:ASC-X_TR_A_PIT_OFFSET 1 -4.800000000000000e-02
H1:ASC-X_TR_B_PIT_OFFSET 1 -1.480000000000000e-01
H1:ASC-X_TR_A_YAW_OFFSET 1 -4.000000000000000e-03
H1:ASC-X_TR_B_YAW_OFFSET 1 7.800000000000000e-02
H1:ASC-Y_TR_A_PIT_OFFSET 1 -1.180000000000000e-01
H1:ASC-Y_TR_B_PIT_OFFSET 1 -3.690000000000000e-01
H1:ASC-Y_TR_A_YAW_OFFSET 1 -2.420000000000000e-01
H1:ASC-Y_TR_B_YAW_OFFSET 1 -3.180000000000000e-01
Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 05:16, Sunday 12 July 2015 (19576)

After switching the ITM basis to common/differential, we tried for a while to measure the cITM pitch loop to see if we could put it to work in mitigating this 0.4 Hz resonance.

The attachment shows the loop OLTF at several different powers (yellow: 8W; green: 11 W; blue: 18 W). First, the ugf of the main, 1/f portion of the loop is about 40 mHz. Second, around 0.8 Hz there is a power-dependent resonance which is probably the hard mode. Third, we can see the 0.4 Hz resonance in the cITM loop, although the coherence of the measurement is not great between 0.4 Hz and 0.6 Hz. This makes the behavior of the TF around this resonance hard to interpret. Under the assumption that it's just a pair of complex poles, this means that the total TF will have a 180° lag at the resonance, and hence the loop will go unstable if the gain is increased too much. Hence this current loop shape cannot be used to control the instability.

Therefore, we designed a filter (FM6 in the cSoft filter bank) which flips the sign of the feedback near this resonance. It is a complex pair of RHP zeros at 0.3 Hz, and a complex pair of poles at 0.5 Hz. Together they give 180° of lag at 0.4 Hz. (There is also about 30° of lead and 10 dB of gain near the hard mode.)

We flipped this filter on and off a few times in lock at 18 W, and it seems to correlate well with the apperance and disappearance of the 0.41 Hz oscillation in the ITM error signals, the test mass oplevs, the arm buildups, and the sideband buildups. A quick OLTF shows that the suppression is pretty marginal; probably less than 2 dB. This is with the filter gain increased from -0.3 to -0.8.

Images attached to this comment
H1 GRD
evan.hall@LIGO.ORG - posted 02:23, Sunday 12 July 2015 - last comment - 21:19, Sunday 12 July 2015(19573)
Bat control

Sheila, Evan

Bat control is among the most challenging of control problems. In this case, some patience and a cardboard box were all that was needed to solve the problem.

Images attached to this report
Comments related to this report
jameson.rollins@LIGO.ORG - 02:46, Sunday 12 July 2015 (19575)

BAT_TRAP

jeffrey.kissel@LIGO.ORG - 10:31, Sunday 12 July 2015 (19578)INJ
@Jamie -- Is that a python script / guardian state developed to solve this problem? Could you please point us to the relevant aLOG, ECR, Integration Issue or FRS ticket?? ;-)
jameson.rollins@LIGO.ORG - 16:20, Sunday 12 July 2015 (19582)

The bat ate my ECR.

jeffrey.kissel@LIGO.ORG - 21:19, Sunday 12 July 2015 (19584)
OH! I'll file an FRS ticket.
H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 21:27, Saturday 11 July 2015 - last comment - 20:04, Sunday 12 July 2015(19572)
AS_A_36 phasing
Evan, Stefan

When we came in the winds were relatively high, so we decided to take another loock at the AS_A_36 phasing. We did so in DRMI.

- To take out the effect of WFS centering and the otherASC loops, we lowered the total ASC gain by a factor 10, and increased the WFS centering gain from 1 to 200 (raising the centering gain by a factor of 20).
- We then drove the SRM at 0.3Hz in PIT and YAW.
- Interestingly PIT and YAW totaly disagree on the phase, by about 125deg...
- Attached are screen shots for the old phases (picture 1), phased for PIT (picture 2), and phased for YAW (picture 3)
- Additionally, while all 4 quadrants show a reasonable signal for PIT, the YAW signal is weak in quadrant 1 and not present in quadrant 2
- We decided to make a pragmatic choice:
  - For PIT AS_B_36_I is already a fine signal - only for YAW it doesn't work
  - Thus we decided to phase AS_A_36_I for YAW...
  - ... and only use quadrants 3 and 4 (the lower two quadrants).
  - Quadrants 3 & 4 also have a similar strength signal (with opposite sign) and similar RF offset (with the same sign)
  - So: this new YAW signal AS_A_36_I should be fine now.

YAW Input matrix for I and Q now is:
H1:ASC-AS_A_RF36_I_MTRX_2_1    0
H1:ASC-AS_A_RF36_I_MTRX_2_2    0
H1:ASC-AS_A_RF36_I_MTRX_2_3    -2
H1:ASC-AS_A_RF36_I_MTRX_2_4    2

With this new YAW sensor we updated the ASC sensing matrix (pictures 3 and 4).

This sensor seemed to do a good job at 17W and at 24W. However at 24W we still saw a 0.4Hz instability - see next alog.
Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 20:04, Sunday 12 July 2015 (19583)
Some more screen shots
Images attached to this comment
H1 TCS
eleanor.king@LIGO.ORG - posted 13:20, Saturday 11 July 2015 - last comment - 18:02, Saturday 11 July 2015(19568)
Hws alignment ITMY

Nutsinee, Elli

When we arrived the IMC was not locking so we changed some settings to get it to lock.  Changed PSL differacted power to 7% up from 3% by changing H1:PSL-ISS_REFSIGNAL to -1.96V.PSL.  The PSL power was 1W when 2W  was requested at the rotation stage.  So we searched for home, and now requested power matches again.

We tried to lock the arms in green without success.  The X-arm PLL was not locked, we changed Crystal frequency to 100MHz and now it is locking, however the ALS_XARM and Y_ARM guardian still report faults "PLL; PHD", and "Ref. Cav. Power", which we couldn't fix.  We noticed the reference cavitytTPD has dropped from 0.85 to 0.7 V in the last 24 hours (see plot.)

We aligned the corner station optics using the oplev trend to where they were last night in order to do the HWS alignment.  We noticed BS oplev Yaw is showing zero as output.  Without the green from the arms this alignment was difficult.  in any case, we are starting to think that this HWSY alignment is proving too difficult with the current (wrong) in-vacuum lens installed-  the beam return beam is the same size as the mirrors we are using, and we have never been able to get rid of clipping patterns on the beam.

Images attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 18:02, Saturday 11 July 2015 (19571)PSL

The refcav normalized transmission threshold for the end-station PLLs was changed from 0.4 to 0.3 in order to allow the PLLs to lock.

If there is an incursion into the PSL next maintenance day, it might be good to touch up the refcav pointing.

H1 INS (ISC)
stefan.ballmer@LIGO.ORG - posted 00:08, Saturday 11 July 2015 (19565)
ASC stability work at 24W
Nic, Sheila, Evan, Stefan

- Turned on ITMX PIT oplev (ITMY PIT OPLEV was already on)
- DC coupled SRM PIT oplev turned on.
- Tried new SRCL input matrix YAW:
   AS 36    AI    AQ     BI    BQ         
   OLD:   -0.6   0.3    0.3   0
   NEW:    0     1.0    0     0
- This seemed better at higher power for RF offsets, but is too early for judgement.
- Also tried new SRCL input matrix PIT:
   AS 36    AI    AQ     BI    BQ         
   OLD:    0     0      2     0
   NEW:   -0.5  -0.5    0     0
- We didn't keep this one though because it seemed worse at low power.

- Attempts later tonight were hampered by winds up to 30MpH in the corner.
H1 CDS
sheila.dwyer@LIGO.ORG - posted 22:07, Friday 10 July 2015 - last comment - 18:32, Sunday 12 July 2015(19566)
EPICs freezing

We've noticed two more examples of epics channels freezing for a few seconds.  Yesterday (July 9 16:25:09 UTC) and tonight (0:22:49 UTC July 11)

Comments related to this report
david.barker@LIGO.ORG - 08:07, Saturday 11 July 2015 (19567)

I have opened an FRS on this issue (#3279) which contains details of my investigation. I have seen two extended CA freeze-ups of LSC over the past two days (11 and 14 seconds in duration) with an apparent increase in CPU load on h1lsc0 at the time. The DAQ data does not show any drop-out, this only impacts CA access to LSC data. This is an inconvenience for MEDM and StripTool, but has potentially more serious implications for Guardian. Investigation is continuing. With only one large event per day it unfortunately takes some time to gather data. I'm also trying to reproduce the issue on the DTS.

https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=3279

evan.hall@LIGO.ORG - 18:32, Sunday 12 July 2015 (19569)

Just to build statistics, we observed these dropouts as well:

  • 2015-07-11 00:21:40 Z
  • 2015-07-13 01:31:20 Z
H1 AOS (ISC, SYS)
sheila.dwyer@LIGO.ORG - posted 21:36, Friday 10 July 2015 - last comment - 21:09, Monday 13 July 2015(19562)
OMC fringe wrapping

Nic, Sheila

We put an excitation into the HAM6 ISI ISO Y filter bank, (30000 counts at 0.3 Hz) from about 3:17-3:19 UTC July 11.  We then did a by eye fit  (on a log log scale)for a fringe wrapping model.  We expected the excitation to result in 30 um motion of the OMC, but we had to use 36 um to get the fringe speed right. We get an amplitude reflectivity of 1.6e-7 for the single pass shelf. (compare to 1e-5 measured in 17919)  We see no evidence of a second shelf or a shelf in the null stream.  

We plan to make measurements in exactly the same was as 17919, if we get a chance again tonight.

Images attached to this report
Non-image files attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 21:09, Monday 13 July 2015 (19609)

There is a typo in this alog, the reflectivity is r=160e-7, as the legend in the plot says, not 1.6e-7 as I wrote.  

H1 SUS (ISC)
nicolas.smith@LIGO.ORG - posted 18:19, Friday 10 July 2015 (19561)
Settings for ETMX roll mode damping

(stefan sheila evan nic)

We had to modify the mode damping settings to get the ETMX roll to decay. These might not be stationary, but here is the record of the settings that worked.

damping settings

Images attached to this report
H1 ISC (SEI)
sheila.dwyer@LIGO.ORG - posted 18:06, Friday 10 July 2015 (19560)
High wind DRMI

Sheila, Stefan, Evan, Nic

Today we've had winds around 25 mph most of the day, now the gusts are approaching 40mph.  The attached screenshot shows a failed DRMI acquisition right before a successful one.  In the top panel, the limits are set to the DAC saturation.  In the failed attempt we saturated PRM M3 after 4 seconds, in the successfully lock we don't engage the offload to M2 until 16 seconds after the lock is acquired. 

A screenshot of the guardian log during the successfully lock is attached, we engage the WFS centering before offload.  I've rearranged the guardian to engage the offload before engaging the centering and also speed up the engaging.  It now takes about 2.5 seconds from locking to engaging the offload.  

 

Images attached to this report
Non-image files attached to this report
H1 SUS (CAL, DetChar, ISC, SUS, SYS, VE)
leonid.prokhorov@LIGO.ORG - posted 13:11, Friday 10 July 2015 - last comment - 20:58, Friday 10 July 2015(19547)
OPLEV charge measurements; Data are beginning to be consistent with a small increase in charge, consistently negative
Leonid.Prokhorov, Jeffrey.Kissel

We continue the charge measurements on ETMs. The data are beginning to be consistent with a small increase in charge, consistently negative.
For the past few weeks since the discharging the charge has been small (<10 [V] Effective Bias Voltage), and roughly consistent with a parent Gaussian distribution with a mean about 0.0 [V] Effective Bias Voltage. However, as we get more data, we're beginning to see a case for a slow negative charging of the test masses (about 2-5 V/week) in at least half the quadrants (ETMX UR, UL, and LR; ETMY (the pitch estimates of) UR, UL, and LR). The uncertainty of these measurements is too large to state that the trend is statistically significant, but yellow flags have gone up. 

This argues that we should continue roughly daily (say, thrice a week) measurements of the charge, and we need to continue to do so for another week or three.

There are three sets of plots, each which show the same data in a different way:
(1) ETMX.png & ETMY.png show the "raw" data, where the result of each estimate of the effective bias voltage shown *since* the discharging. Each single data point is an estimate of the effective bias voltage, i.e. the charge, as determined by driving the test mass while varying the requested bias voltage and measuring the response with the optic's optical lever.
(2) ETMX_Mean.png & ETMY_Mean.png shows both the mean and standard deviation, and weighted mean and sqrt(weighted variance) of the charge measurements for a given day (which can be from ~4 to ~15 of these 12 minute measurements per mean point). We believe this better shows the long-term trend of the charge.
(3) ETMX2015.png & ETMY_2015.png shows the mean charging measurement results since January 2015, i.e. it includes data when the test masses were charged and shows the discharge which happened in Mid-June.
Images attached to this report
Comments related to this report
rainer.weiss@LIGO.ORG - 20:58, Friday 10 July 2015 (19564)SUS, VE
It is useful to note that if the bias is going in a negative direction, the charge on the test mass
is going positive. This would be consistent with uv or xuv photoemission from the front surface of
the test mass. Refer to DCC  T1400647-v1. The slow growth of charge on the LLO etmy is also going in the same direction
toward positive charge.
H1 ISC
nicolas.smith@LIGO.ORG - posted 16:38, Thursday 02 July 2015 - last comment - 20:22, Friday 10 July 2015(19432)
Couldn't make fringe wrapping with bright michelson

(evan jenne nic)

We wanted to investigate the OMC alignment/backscatter problem. Driving the OMC SUS in Yaw has been known to cause backscatter noise due to the modulation of the optical path length when the OMC moves in Yaw.

Our procedure was to lock the vertex optics in a bright michelson configuration (a state has been added to the IFO_ALIGN guardian to make this easy). Then we wanted to drive the OMC in yaw and choose the yaw->longitudinal matrix element such that the center of rotation would be about the input beam, rather than the omc center of mass. This would be determined by minimizing the scatter as measured by either OMC trans, or the MICH error point.

I was surprised that we were not able to induce any significant backscatter fringe wrapping noise in this configuration. We drove the OMC SUS in longitude up to the point that the beam was misaligning enough to noticibly affect the OMC DC trans.

We also drove the ISI table directly by putting a 1Hz 1mm injection into the Y isolation loop error point. 

Driving the path length, we both listened and had a live spectrum running. We saw no evidence of scatter in either OMC trans or MICH_IN1.

We will need to think if there is another configuration (available to use without arms) that will be more sensitive to backscatter.

Comments related to this report
nicolas.smith@LIGO.ORG - 16:52, Thursday 02 July 2015 (19433)

I forgot to mention that we turned on the AS fast shutter and OMC pzt high voltage supplies for HAM6.

nicolas.smith@LIGO.ORG - 20:22, Friday 10 July 2015 (19563)

This measurement didn't work because I was wrong about the calibration. The isolation loop error points are in nanometers, not micrometers. So we were moving the table 1000 times less than I thought.

H1 CAL (AOS, CAL)
sudarshan.karki@LIGO.ORG - posted 10:01, Wednesday 17 June 2015 - last comment - 14:41, Sunday 12 July 2015(19186)
Gravitational Wave Strain h(t) sign convention determination using Pcal

Calibration Team

Sign of h(t):

The gravitational wave strain h(t) is given by  h(t) = Delta L/L where Delta L  is is computed using

                         Delta L = ± (Lx - Ly)

The sign of Delta L can be determined using Pcal actuation on the test mass. Pcal only introduces a push force  so pcal readout signal (truly pcal excitation) is minimum when the testmass is away from the corner station (closer to pcal laser). From the first plot the phase between DARM/PCAL is ~ -180 degrees (DARM lags PCAL) which suggests that DARM signal from ETMX will be maximum when pcal is minimum (ETMX further away from corner station). Similarly, from second plot, since DARM and PCAL have a phase difference of ~-360 degrees (essentially 0 degrees), the  DARM signal from ETMY is minimum when the pcal is minimum. This shows that the sign convention for the Delta L is '+'

Time Delay between Pcal and DARM:

Also the slope of the curve gives the time delay between Pcal and DARM signal chain. The time delay is about 125±20 us. This time delay can be accounted for, within the uncertainity, from the difference in signal readout chain outlined in Figure 3 attached.

Refer to LLO alog #18406 for the detailed explanation behind this  conclusion.

Images attached to this report
Comments related to this report
peter.shawhan@LIGO.ORG - 10:04, Friday 03 July 2015 (19437)CAL
I believe this sign check and the sign check at LLO are correct.  For the record, below is how I reached that conclusion:

The photon calibrator laser can only push, but there is a nonzero baseline intensity and you modulate the intensity around that.  The question is, if you apply a positive voltage to the PCAL system input, do you get more force or less force on the test mass?  Figure 21 of the PCAL final design document seems to show that the undiffracted beam through the AOM is what is sent to the test mass, so increasing the amplitude of the 80 MHz drive to the AOM REDUCES the force on the test mass.  However, the AOM driver electronics could introduce a sign flip when it conditions the input voltage.  To check that, I pulled up PCAL excitation and receiver photodiode data (e.g. H1:CAL-PCALX_EXC_SUM_DQ and H1:CAL-PCALX_RX_PD_OUT_DQ) and plotted a short time interval at GPS 1117933216.  I saw that the PCAL photodiode signal variations are basically in phase with the PCAL input excitation, with just a ~30-40 degree phase lag at ~500 Hz, presumably from filter delay.  So, applying a positive voltage to the PCAL system input causes more force on the test mass, and anyway the PCAL receiver photodiode measures intensity directly.  I confirmed this for all four PCALs (H1 and L1, X and Y) and also confirmed that the transmitter and receiver photodiodes vary together.

The PCAL pushes on the front of the ETM, i.e. on the face that the primary interferometer beam reflects off of.  This being a pendulum, the ETM is closest to the laser (i.e., the arm is shortest) when the force is at its MAXIMUM.  LLO alog 18406 has a comment consistent with that: "Theory of pendulums suggests that Pcal signal will be minimum when ETM swings further away from corner station".  LHO alog 19186, above, has a statement, "pcal readout signal (truly pcal excitation) is minimum when the testmass is away from the corner station (closer to pcal laser)", which is more ambiguous because the ETM being away from the corner station would put it FARTHER from the PCAL laser.  But both draw the correct conclusion from the data: with the intended sign convention, DARM should be at its positive maximum when the X arm is longest (ETMX is farthest from the corner station; PCALX intensity is at its minimum) or when the Y arm is shortest (ETMY is closest to the corner station; PCALY intensity is at its maximum), and that is what was reported at both sites.
darkhan.tuyenbayev@LIGO.ORG - 10:33, Tuesday 07 July 2015 (19466)

Peter,

I disagree with one assumption in your argument, but it does not disprove (or support) the rest of your conclusions.

"The question is, if you apply a positive voltage to the PCAL system input, do you get more force or less force on the test mass? Figure 21 of the PCAL final design document seems to show that the undiffracted beam through the AOM is what is sent to the test mass, so increasing the amplitude of the 80 MHz drive to the AOM REDUCES the force on the test mass. However, the AOM driver electronics could introduce a sign flip when it conditions the input voltage."

As far as I know there's no sign flip in AOM electronics. Undiffracted beam gets dumped in BD2, while diffracted beam is sent to the ETM.

Unfortunately I couldn't find an explicit noting of it in our recent DCC documents.

peter.shawhan@LIGO.ORG - 14:41, Sunday 12 July 2015 (19580)CAL, INJ
Oh, the diffracted beam gets sent to the test mass?  Then I agree, there isn't a sign flip in the electronics.  (In figure 21 in the document, it looks like the undiffracted beam went to the test mass.)

BTW, I've posted a multi-frequency look at the hardware injection actuation sign (and amplitudes and time delays) at https://wiki.ligo.org/Main/HWInjER7CheckSGs.
Displaying reports 66581-66600 of 85652.Go to page Start 3326 3327 3328 3329 3330 3331 3332 3333 3334 End