THESE CALIBRATION FACTORS HAVE CHANGED

Per Keita's ALOG 10331 and 10454, I have adjusted the optical lever calibration gains for ETMX and ITMX to reflect a more accurate method of calibration that was performed by Keita with the baffle diodes.

ETM

ITM

This morning Mitchell, Travis and Andres installed the ACB.  Mitchell and Travis aligned it with IAS in the afternoon.  Travis left the ETMy SUS unlocked such that final balance checks can be made (and or TFs) this weekend by SEI.  SEI is starting HEPI work there now.

In Keita's ALOG 10454, he pointed out that the  ETMX optical lever yaw sign convention is backwards from the SUS convention.  I fixed this to make them match at 3:35 PM PT and Jeff K is did a save.snap.

Cyrus R., Jim B.

We racked the computer and IO chassis for h1pemmy today at the mid-station.  All of the computing parts are connected, the computer is attached to the network, and the timing chassis is patched through to the master fanout in the MSR. We boot tested the front end as well, without running any models, and Jim verified the BIOS settings.  We are now waiting for an AA chassis with the appropriate PEM modifications to complete the physical install (and in-rack cabling for said chassis has not yet been done).  Models for the FE will also need to be completed/compiled, and the rtsystab/etc. updated.

Aligned the ACB in WBSC10 this afternoon after this morning's installation.  The errors are as follows:

• Lateral: -0.6 mm (South)
  • Tolerance: ±2.0 mm
• Vertical: +0.5 mm (high)
  • Tolerance: ±2.0 mm
  • Note: this is after accounting for the -1.4 mm vertical shift caused by the weight of the alignment target

(Alexa, Sheila)

For the noise budget, we had tried measuring the PDH shot noise by misaligning ITMX and reading out the amplitude spectrum from IMON of the demod. This amplitude spectrum was clearly not pure shot noise at low frequency; there seemed to be some scattering and fringe wrapping (see green line in plot). We went to investigate this by putting a HR 532nm mirror at the bottom of the periscope and repeating the measurement; the noise at low frequency subsequently decreased significantly (see red line in plot -- unfortunately I should have taken more frequency spans). There is stil some acoustic noise at around 100Hz but it's less than in the first measurement (and in the overall PDH noise, the fiber noise is dominant in this region anyway). We removed the HR mirror and tried misaligned ITMX to various different positions and saw that the amplitude spectrum changed around. Clearly, in this measurement we are picking up scattering in the cavity which comes about from misaligning ITMX. We have now convinced oursevles that we do not have any major scattering on the ISCTEX table. 

I have attached the data with the HR mirror in place.

The awgstream software for the control room has been updated to increase the size of the channel list it reads.  This should solve the problem encountered Wednesday in which H1:SUS channels could not be excited using awgstream.

Yesterday night and this morning some diagonalization measurements were taken with pum drive on etmx and itmx. The low coherence for the pitch drive described on the previous alog was due to the optic not centered enough on the oplev, so both ETMX p2p and y2y were remeasured. Those measurements can actually be really fast (15/20min each).
ITMX measurement has some calibration factor of 1.56 for Yaw and 1.83 in Pitch. T1100378 was the reference for calibrating the drive from cts to N.

Attached are the plots comparing the measurement and the model (wirerehang for itmx, fiber for etmx). Note that there is a sign error in ETMX Yaw, so we should double check if that comes from the Oplev sign convention.
 

• The data was processed (removed points with bad coherence) and calibrated in rad/N.m. It lives in :

ITMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Results/quad_{p2p/y2y}.mat

ETMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL2/Results/quad_{p2p/y2y.mat

• Dtt templates were saved under : 

ITMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Data/2014-03-06_H1SUSITMX_{P2PY/Y2PY}_WhiteNoise.xml

ETMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Data/2014-03-04_H1SUSETMX_{P2PY/Y2PY}_WhiteNoise.xml

• The data was processed with the scripts : 

ITMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Scripts/itmx_L2_diag.m

ETMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL2/Scripts/etmx_L2_diag.m

The HEPI and ISI are locked at EndY.  SUS is being stopped down and ACB staging/prep is ongoing for installation.

These will be running continuously for the next week or two (part of portable RGA assembly/Y1 accumulation data collection).

With Jim needing to connect In-Vac cables to feedthrus today, I wanted to update the EY TMS Cable Table (mainly to show recent change of swapping damaged D1000223 cable with D1000225).  All of this follows the BSC10 Cable Routing Configuration (D12000111) & is in the following ICS Assy Load.

While I certainly appreciate the acumen of Stefan and Sheila on all things interferometeric, I showed yesterday in 10580 that HEPI did not move.  That said I do understand not always being able to catch all alogs that go in, I'm sure I'm very behind in my reading there too.

A couple things, that was not a glitch in HEPI, it was a trip condition that lasted for ~1.5+ hours.  I'm not sure how to figure out exactly what caused this trip in HEPI but the trend would suggest it is the last time this HEPI tripped and the MEDM says it was SUS.

I see ISI target changes on Tuesday and Thursday on stage1 timed with the HEPI Trips--likely model restart and ??  I suspect Stage2 sees this too.  This certainly will regulary impact alignment if it is recurring.  I think Sebastian must look through this closely and propose preventive measures here.

While I certainly appreciate the acumen of Stefan and Sheila on all things interferometeric, I showed yesterday in 10580 that HEPI did not move.  That said I do understand not always being able to catch all alogs that go in, I'm sure I'm very behind in my reading there too.

A couple things, that was not a glitch in HEPI, it was a trip condition that lasted for ~1.5+ hours.  I'm not sure how to figure out exactly what caused this trip in HEPI but the trend would suggest it is the last time this HEPI tripped and the MEDM says it was SUS.

I see ISI target changes on Tuesday and Thursday on stage1 timed with the HEPI Trips--likely model restart and ??  I suspect Stage2 sees this too.  This certainly will regulary impact alignment if it is recurring.  I think Sebastian must look through this closely and propose preventive measures here.

In addition to realigning the TMS, I also moved ETMX, ITMX, PR3, PR2 and IM4 tonight. 

I initially aligned the straight shot to ISCT1 using TMS and the baffle diodes, then PR3 for the camera spot.  Then I locked the cavity and tried engaging WFS.  I was able to engage PIT DOF1 and YAW DOF 1, and although the error signals were eventually brought to zero, the cavity build up dropped compared to the hand alignment.  The spot position also moved away from the spot on the camera that I had centered the single shot beam to.  I tried engaging PIT DOF2, but the gain was set to 0, and has been for a few days. I tried a gain of 1, which was bad, and a gain of 0.1 which seemed to have no impact. 

I gave up on the WFS and alinged the cavity by hand.  By moving TMS in pitch I was able to get the cavity build up to 800 counts again, so I decided to abandon WFS for tonight and go on to locking COMM.  The ALS_XARM guardian now has states for WFS. 

I was able to lock COMM using the guardian, and it was stable tonight with high gain ( I mean that the lock didn't drop unless I did something).  The noise measured by the linearize error signal is a bit worse tonight, 200Hz.  The first higher order modes were resonanting at the frequency were we though we had found the 00 mode last night.  I found the 00 mode at -5990Hz, and tweaked up the alingment using IM4 and PR2. 

Right now IM4 is at PIT -3077 YAW -5707 PR2 at 445 YAW at -383.1  I didn't save these using the IFO align screen in case the red team wants to restore their alignment from this morning using the current saved offsets. 

I did save TMSX, ETMX, ITMX and PR3.

After I restarted the corner beckhoff machine, the timing system did not come back.  I has an error on Corner Master A, Fanout 15, VCXO control voltage.