aLIGO LHO Logbook

H1 CAL (CDS, ISC, SUS)

jeffrey.kissel@LIGO.ORG - posted 05:45, Tuesday 20 December 2016 - last comment - 07:31, Tuesday 20 December 2016(32766)

Calibration Measurements Beginning for H1 SUS ETMY PUM/L2 Driver Characterization

J. Kissel

Title says it all. Will take about an hour while L1 is down.

Comments related to this report

jeffrey.kissel@LIGO.ORG - 07:31, Tuesday 20 December 2016 (32767)

Link

Actuator measurements complete. Data committed and exported to:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/FullIFOActuatorTFs/2016-12-20/
2016-12-20_H1SUSETMY_L1_iEXC2DARM.xml
2016-12-20_H1SUSETMY_L1_PCAL2DARM.xml
2016-12-20_H1SUSETMY_L2_iEXC2DARM.xml
2016-12-20_H1SUSETMY_L2_PCAL2DARM.xml
2016-12-20_H1SUSETMY_L3_iEXC2DARM.xml
2016-12-20_H1SUSETMY_L3_PCAL2DARM.xml

Got half-way through the PCAL2DARM sweep for the sensing function then the IFO broke lock. Not the end of the world. Templates saved anyways, in case it does:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/SensingFunctionTFs/
2016-12-20_H1DARM_OLGTF_4to1200Hz.xml
2016-12-20_H1_PCAL2DARMTF_4to1200Hz.xml


Analysis to come, but preliminary results from the DTT templates themselves indicate that there has been very little change in the L2 stage response. *phew*!
Since we were able to get these full IFO measurements out of the way, and it happens to be maintenance day, I still think it prudent for us to go down to EY an remeasure the poles and zeros of the new PUM coil driver box, however, unless we decide to revert the driver back. Evidence (i.e. the BNS range) from the ~2 hours of data before I got here seems to point to not too much of a change in glitch rate.

Note, my estimate of "about an hour" was an *underestimate* if I were to have stuck with the plan of only measuring L2/PUM. However, because L1 called to say they're start maintenance early, I just went for the whole calibration suite shebang.