Displaying report 1-1 of 1.
Reports until 22:15, Tuesday 20 September 2016
H1 ISC (CAL, DetChar)
jeffrey.kissel@LIGO.ORG - posted 22:15, Tuesday 20 September 2016 - last comment - 12:11, Wednesday 19 October 2016(29856)
DCPDs have 2.1% Imbalance; Imbalance Now Compensated
J. Kissel, S. Dwyer, L. Barsotti

At the advice of DetChar (LHO aLOG 29828) we've balanced the DCPDs, which indeed hasn't been done since the new breadboard and PDs were installed (LHO aLOG 28862). Unlike the previous pair of DCPDs which were out-of-the-box perfectly balanced (see LHO aLOG 17650), the current pair has an imbalance of 2.1106%. This value has been entered into H1:OMC-DCPD_BALANCE, and accepted into the SDF "down" state for the h1omc model.

Method:
For the DCPD sum, we take an average of the two: A/2 + B/2.
The h1omc front-end infrastructure is built such that the percentage imbalance, e, is applied to both equally: A*(1 + e)/2 + B(1 - e)/2
So, the transfer function measurement of DCPD A/B is (1+e)/(1-e) ~ 1 + 2e. Since the transfer function magnitude is 0.957788, then the imbalance we enter will be e = ((A/B) - 1) / 2 = 0.021106 = -2.1106%.

We also found this value gradually (because we weren't sure how the infrastructure worked), by confirming the imbalance that minimized the DCPD NULL stream (and the coherence drops to zero). Overshooting the imbalance (e.g. by entering in -4.2%) shows a clear sign flip from the reference trace where there is 0% imbalance compensation.
Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 12:11, Wednesday 19 October 2016 (30666)

This is not relevant anymore, since the OMC model has been changed to a more transparent matrix, but there was no divide by 2 in the old scheme.  The sum was just a plain sum of the balanced values.  (Trying to incorporate that non-existent factor of 2 just caused a lockloss while trying to implement the new matrix, which is the only reason I mention it).

Displaying report 1-1 of 1.