On Friday:

- Apollo finished staging the cleanrooms/garb/work tables/sticky mats, etc.

- Apollo did thorough cleaning of the cleanrooms/receivings/VEA.

- Travis and I staged the EQ needed to remove the lower structure (Ergo arm/pump/monitor box, scissor lift with 5-axis table, stool, tools, LSAT)

- We transported the new PUM, the new Test Mass, and an empty cake tin to Ex.

- Travis started staging the welding EQ - ran into a snag with missing chiller hose fittings (!)

- I started prepping the lower structure for removal (dropped the x-braces, vib absorbers, wedges, and most of the bolts holding the sleeve up).  There was a reason the procedures always called for SUS work to take place prior to TMS install.  Removing the LS with the TMS in place is a challenge.

It will take Angus, Travis, me, and Jeff or Andres all of Monday to get to the point where we are swapping in the new optics on Tuesday morning.  Slow as she goes.

Sheila, Kiwamu, Stefan, Alexa, Arnaud, keita.

Today we started out by projecting the spot on IM2 trans on the wall, and saw that it was so high that we were unable to steer it to the reference (from Oct 4th 2013) with our range (after the coil driver change).  After some investigation, we set things back to what we thik the alignment was in late september, using both HEPI and using the BOSEM readbacks for the suspension alingments.  After that we saw that the spot was still too high on the wall.  

We then started measuring the beam centering using the A2L coupling of MC3.  We used the A2L coupling to adjust the offset in the uncontrolled DOF (DOF4 pitch).  We have reduced the coupling by a factor of 10.  

New safe snapshots have been saved for MC1 MC2 MC3 with updated "correct state" for the lock bank (cf screenshot 2), updated bit masks (Bitmasks 8 and 9 were turned off) (cf screenshot 1), and updated alignment offsets during the lock. The ODC status has now its bit 1 to 7 turning green when necessary.

Bitmasks 8 and 9 were turned off using caput from the command line :

caput H1:SUS-MC3_ODC_CHANNEL_BITMASK 254

For x1work, installed nfs server and exported /usr1 for mounting as /ligo.

For x1ws0 (iMac), mounted x1work:/usr1 as /ligo to allow native OS X software to run on workstation.

Jim and Dave. We continued the investigation of the problem of incorrect slow channel data in the DAQ from Front Ends following the upgrade to RCG2.8.

The problem is more widespread that just h1hiitmy. We have also seen it in h1susitmy. It appears that only the non-filter-module floating-point slow channels are affected. The problem is related the channel list defined by the INI file. There is a point in the slow floating-point channel list at which channels above do not have the problem, channels below all have problems. The problem is actually a channel shift. For h1susitmy the channels are shifted by 3, for h1hpiitmy the channels are shifted by 2. The point at which the shift starts varies from model to model. It is after a few hundred floating point channels for h1susitmy, and immediately for h1hpiitmy.

Finding the break point is not trivial. Many of the slow channels are zero, or have rapidly changing signals. We are getting the data from the NDS and comparing it with a direct EPICS channel access read of the data.

We will work on scripts over the weekend to get more data on the problem. Hopefully when Rolf is here next week we can implement a fix. The silver lining is that little data has actually been lost, the data is being acquired by the wrong channel name.

Alexa, Stefan, Sheila and Kiwamu

Yesterday, we set up an optical spectrum analyzer on the PSL table to measure the characteristic of the EOM. The results look good except for the 24 MHz resonance . The resonance for the 24 MHz sideband is apart from the modulation frequency by 250 kHz or so. However the IMC doesn't need a large modulation depth and the IMC locking has been OK, we are good. Also, I took some impedance data and will put those data together into a DCC document for a record purpose.

The plots below are the measured modulation depth when driven hard as a function of the modulation frequencies. The vertical dashed-lines represent our actual modulation frequencies i.e. f1 = 9099471 Hz , f_mc = 24078360 Hz and f5 = 5 x f1.

LVEA Laser Hazard

08:28 Justin	To End-Y to check on laser setup
08:45 Mark	Moving ARGO arm to End-Y
08:45 Thomas	Optical lever work at ITM-X 
09:00 Sheila	Removing viewport cover for IM2
09:15 Mark	Craning ITM-Y lower structure over beam tube
09:25 Filiberto	Pulling cables by BSC3
09:40 Richard	Out to End-Y
10:30 Scrap metal recycler on site to swap recycle bins
12:55 Cyrus	At X-Arm spool area to terminate Cat-6 cables
13:15 Corey	Out to End-X TMS lab to recover tools for End-Y	
14:30 North Gate Electrical on site to deliver part

Removed gasket from 4.5" CFF blank on BSC9 (location of to be installed ESD interlock gauge) and left flange loose to exhaust wet purge air over the weekend -> Started QDP80 and Turbo -> Began pumping on BSC9 annulus

Safe.snap files were updated for every SEI platform involved in PRMI.

Soft links were checked, and safe.snap files were commited in the svn.

ISI
HAM2, HAM3                  - r6572
BS, ITMY, ITMX, ETMX  - r6576 

HPI
HAM2, HAM3                   -r6574
BS, ITMY, ITMX, ETMX   - r6577 

Below is a summary of the available controls on SEI platforms, for PRMI. Platforms should run under their preferred configuration at all time.

HAM1:

• HEPI: Floating

HAM2:

• ISI: Lv3 Isolation, fed by 01_28 generic blend.
• HEPI: Position loops ON

HAM3:

• ISI: Lv3 Isolation, fed by 01_28 generic blend.
• HEPI: Position loops ON

• ISI: Lv3 Isolation, fed by:
  • Stage 1: T250mHz blend, with T100mHz_N0.44 on X and Y
  • Stage 2: 250mHz
• HEPI: Position loops ON

"Quick" circular AMP connectors had been added to this gauge pair wiring to facilitated disconnection/connection without the need to access the wiring terminations at the gauges themselves.  I suspect a voltage drop across this additional connection accounts for the apparent signal error.  Accessibility is not good to correct -> will live with this until opportunity to correct presents itself

A set of matlab transfer functions has been ran on the TMSX this afternoon after BSC9 was closed out, and while the ISI was damped. The pitch degree of freedom shows some excess noise between 0.7Hz and 3Hz, which is something I was not expecting to see since the measurement after the last work accomplished on TMSX was clean.

It might be related to some excess motion at the time of the measurement during the afternoon, which I will check by running undamped and damped TFs overnight in a quiter environment. We will see how repeatable the measurement is tomorrow morning.

It might also be the position of the cables that could have changed by themselves because of their weight. Or maybe some work that I'm not aware of that was done after the last measurement taken. In those cases we would probably need to physically check what is going on.

Results attached are described below :

(1) Comparison between the model and last TMSX TF

(2) Comparison between TMSX after the work done on Nov 20th (Orange trace), after the last time work has been done on Nov 22nd (black trace), and today (pink trace).

See the 5th page of (1) and (2) for the pitch dof

I am leaving the IMC locked for the night in order to see its stability. The ASC loops are all engaged.

It must be rock-solid because we fixed the EOM !!

An auto-locking script is locally running on opsws4. The script itself resides in /opt/rtcds/userapps/release/ioo/h1/scripts/imc/sballmer/ and it is called MClockwatch.

Hugh noticed that some HEPI ITMY slow channels were not correct in the DAQ. I did some investigation and found:

Of the slow channels (datarate=16) in H1ISIITMY.ini :

channels associated with the FEC were correct

channels associated with Filter Modules were correct

other slow channels were incorrect, either showing zero or other data (like channel hopping)

Fast channels appear to be OK (within the limited sample I used)

The problem is not seen with HEPI BS or ETMX. Looking at the models they all look identical.

Reboot/Restarts:

I first restarted h1hpiitmy. Then tried restarting all models on h1seib1. Then tried a restart of the mx-streamers. Then recompiled and reinstalled the h1hpiitmy model and restarted it, followed by a DAQ restart (DAQ status was good, so this should have been unnecessary). All to no avail.

The only thing I haven't done is reboot the computer.

It appears this problem appeared when we upgraded to RCG2.8 on Tue 12 November.

Steps taken to commission the ITMY ring heater pair:
- Updated to the recently committed Beckhoff code that Joe B and Adam M worked on yesterday.
- Added the calibration values that Aidan B had recommended for running the ring heaters.
- Opened up a strip tool to monitor the vacuum pressure with the closest gauge (HVE-LY:Y1_120BTORR)
- Turned the ring heaters on to low power (~.01 Watts) to make sure that the channels were working properly
- Increased the power to 1 Watt for a 4 hour period starting at 12:00PM Pacific Time, keeping an eye on the pressure gauge previously mentioned.


Upper:
Requested Power = 1.00 Watts
Measured Voltage = 5.94 Volts
Measured Current = 0.17 Amps 
Calculated Power = .99 Watts
Calculated Resistance = 34.94 Ohms

Lower:
Requested Power = 1.00 Watts
Measured Voltage = 5.92 Volts
Measured Current = 0.16 Amps 
Calculated Power = .98 Watts
Calculated Resistance = 37.0 Ohms

A four hour trend of the pressure gauge and ring heater settings is attached.

A quick, back-of-the-envelope calculations shows that the ring heaters are working properly. The next step for measuring the thermal lensing would be to measure the beam diameter of a single reflection off of the back of ITMX independently and then changing the radius of curvature of ITMY using the ring heater to match. This requires looking at the REFL beam either in the HAM1 chamber or on the ISCT1 table, depending on how much power we are able to get out of REFL.  The Thorlabs beam profile we have on site requires a minimum of ~1e-5 Watts of incident beam power to function.