As a prep for the PRC length measurements, I hooked up a DAC cable of LSC, CAB_H1_ISC_421, to the Dsub breakout board D1201450 at the 18th floor of the ISC rack R4 as specified in E1200408-v14. It is connected to the right half of the breakout unit.

Then I connected a TNC cable from the 2nd output port of the breakout board to the A excitation of the IMC servo board. This is a temporary configuration and allows us to remotely excite the IMC length using the LSC_EXTRA_AO_2 signal (see T1100242-v11 for the signal assignment).

Jeff and Andres report that SR2 now sits inside HAM4.  The installation arm remains on the chamber and will come off Tuesday morning.

I noticed last week that the IPC receive errors at all end station SUS and HEPI for the LSC signals is non-zero. Following the discovery of LLO LSC transmit errors to the end stations due to CPU overrun on the LSC model, I verified that our errors are also due to the LSC model running longer than its average of 40uS. The attached plot shows the error going to ONE at the time the LSC cpu increased to 44uS. The error latches, which is why we don't see any indication of the subsequent 45 and 44uS excursion.
I am running a script which clears the diagnostics on H1SUS-ETMX every minute. The next time an IPC error is seen it will reset after a minute ready for the next event.
All the error rates I've seen so far are only for ONE transmission of the 16384 sent that second. So the error rate is about 3 in an hour or 5.e-6 %

Currently underway (~1:30PM local):

** Doug is transitioning EY to laser hazard for IAS.  Betsy and Travis have been at EY this morning and might return this afternoon depending on Doug's results.
** Rich continues to test BS ISI.  He's pausing while Filiberto attends to a CPS cable at BSC2.
** A semi from LLO carrying storage containers, etc. has driven down the X arm.

This morning I finished rolling out available guardian updates for suspension (following alog 9733)

• Created and started a guardian process for : MC1 MC3 PR2 BS ITMY ITMX ETMX ETMY TMSX TMSY using the commands :

guardctrl create SUS_MC1

guardctrl start SUS_MC1

• Saved the alignment offsets to their current values (except PRM which is in parking position), in order to test if the align_save_burt python script is properly saving, and the guardian properly restoring those offsets.
• Table below summarizes those offsets :

• Modified the overview screens quad/hsts/hlts/tmts/bsfm to make the link to the guardian work

changed the command of the guardian button from  /ligo/apps/ubuntu12/guardian/bin/guardmedm to -> guardmedm

• What still needs to be improved / fixed :

- The sitemap needs to be started from a terminal in order to either save the offsets, or open a guardian medm screen.

- Managing the way the offsets are saved. For now there is 4 txt files per suspension under /opt/rtcds/userapps/release/sus/h1/burtfiles.

one .req file defining the two offset epics channels, one snap file for the aligned value, one snap file for the misaligned value, one file saving all the aligned offsets with the date it was changed.

Installed Trillium Interface Chassis S1101837 in Rack SEI-C1 (slot U18).
Trillium was placed close to southwest side of BSC9.
Outputs from Trillium were connected to AA Chassis U30, CH21-26 (Port 5).
Trillium may need to be zero-ed.

Filiberto Clara

Seismometer installation completed at 12:06.  Patrick had earlier returned from EX.

Seismometer installation completed at 12:06.  Patrick had earlier returned from EX.

The dust monitor at end X has stopped communicating. From trending back it appears to have stopped sometime around Jan. 31 2014 17:46 - 17:55 UTC (9:46 - 9:55 PST).

It is odd. The dust monitor itself acts as though it is receiving commands (the front panel goes into remote mode), but the software times out waiting for a response. I checked the front panel settings, the cabling, turned the dust monitor on and off, restarted the IOC and power cycled the Serial to Ethernet converter, all to no avail.

Rich will begin evaluating the low frequency performance of the beam splitter ISI.  

Rich M, Richard, Dave

Between the times 11:11 and 11:22 local I power cycled the h1seih16 front end and IO Chassis as part of the investigation of the intermittent 0.5Hz noise on HAM6 ISI CPS.
The procedure followed was:
in MSR
  Kill all user models and then the IOP model
  remove unit from Dolphin fabric
  power off the CPU from the console
in CER
  power down h1seih16 IO Chassis using front panel switch
  remove 24V power cord for about 15 seconds
  reapply 24V power cord
  power up IO Chassis using front panel switch, verify timing slave start correctly
in MSR
  power up h1seih16 CPU, verify no error on console

There's a huge 0.038Hz oscillation in ITMX OL laser intensity.

It's not compromising the OL PIT and YAW performance much if at all, but needs to be fixed at some point anyway.

Per WP #4422, Filiberto and Aaron have arrived at EX (11:00 AM local) to install the Trillium seismometer.  Patrick is there also investigating the dust monitor.

This morning I can see that the drip is forming at the Valve Cover and not at the Valve/Manifold seal.  The valve may still be working fine but it should be changed out and repaired.  This could be delayed if the glitches and being offline for a few hours tomorrow is untolerable but I'd prefer to get it done sooner rather than later.

Here is the list of commissioning task for the next 7-14 days:

Green team:

1. Implement optical lever feedback damping to address the mode hopping problem.
2. ETM drive diagonalization
3. Commission the red cavity lokcing signals.
4. Lock the arm cavity on red.
5. Make a mode scan of the red resonances
6. Commission the common mode hand-off including the AO path.
7. Measure difference between red and green locking offsets.
8. Commission the length feedback path to the ETM top suspension point to suppress microseism.
9. Asses the status of the reference cavity temperature controls.

Red team:

1. Mode matching measurements using ISCT1 and maybe IOT2R.
2. Mode cleaner characterization: Absorption, heating and scattering.
3. Optimize the thermal compensation of ITMY.
4. Calibrate SPOB 18.
5. Meausre the PRC length
6. Lock the PRMI using the 3f signals.
7. Investigate the REFLAIR45 whitening filter issue.

TMS:

1. Repair and exchange the in-vacuum cable for the beam diverter.

ISCTEY:

1. Complete the feedthrough panels.
2. Install the on table cabling.
3. Prepare for move to the end station.
4. Check out ALS electronics in EY.

SEI/SUS team:

1. CPS master clock and associated noise.
2. Improve performance.

(Alexa, Daniel, Stefan)

The RD rotation was adjusted to 120deg. This was determined such that the sideband signal was seen in only I, with nothing appearing in Q.

Note: the RF9 frequency is set to 9099471Hz  (only 300Hz from the FSR). We still see RF AM.

Bubba reports that the installation arm is now attached at HAM4.  Jeff B is preparing to install SR2.  They hope to have the optic inside HAM4 by lunchtime.

If anyone was looking at data from PRMI overnight, I just realigned the etm, causing it to drop lock. 

The MC2 roll mode notch (FM6 in ISCINF) was left off overnight, resulting in a rung up 28Hz peak in MC_L, which was producing a huge signal in PRCL. Once on the peak slowly disapeard.

PRMI locking is now quite reliable. However we still have relatively big power fluctuations.

I recorded today's settings in a setup script: sballmer/tempfixes/setPRMI
Really, this should be fed to a guardian.

 Spent some time looking at the noise of the CPS on the BSC after rerouting the sync signals

  One figure is a matlab plot of some calibrated signals using a fixed target on which there are some VERY bad BS channels

  the second plot is a dtt screen of all of the BSC CPS channels in counts, (BS-V3 is looking at a fixed target, all other channels are looking at motion) with all of the ISIs OFF.

  there are a number of icky channels