Jax, Stefan

We verified that the whitening stage 1 of REFLAIR_A_RF45_I is indeed not switching on the analog side. We checked that the command bit (pin 25 / GND=pin 20) makes it to the board. Thus Jax will pull the board tomorrow and debug it..

Details:
Rack: ISC R2 slot 32
S/N: S1101590
Assembly: D1002559 (board2)

On Friday I replaced the glass former that had broken on ITMx. After the glass former was replaced the ring heater was flushed and run in the airbake oven. The lower ring heater attached to the quad structure without incident. Cables were re-routed and tied down with stainless steel strips. Attached are the install photos. 

The ITM03 test mass and it's PUM-ETM01 have been installed in the lower structure and the lower structure has been parked in the fiber weld cleanroom.  Equipment setup is almost complete.  We anticipate firing up the CO2 welder tomorrow.

Laser Status:
Output Power : 28.2w
FRONTEND Watchdog green
HPO WATCH is red (High Power Oscillator Offline)

PMC: 
Locked for : 0d 23h 16m
Reflected power : 1.3w
Power Sum : 11.7w

FSS: 
Locked for : 0d 0h 1m

ISS:
Diffracted power : 5.8% (recovering from sat event)
Last Saturation Event : 0d 0h 8m

Mitchell and I added 200lbs to the HAM now holding 800 lbs.  The 50lbs in the middle is sitting on the 600lb leg element on four 1/16" thick viton pads.  The three other 50s are on the ISI Optical Table but we couldn't get them to be non-rocking, two imperfect planes...  So we turned the masses over and set them on just three pads.

Next step, unlocking, torquing, cabling, TFs.

On friday, I had a chance to test the Y2Y UIM filter, by taking an open loop transfer function driving in yaw from uim and looking at the test mass optical lever. The open loop looks as expected, falling at 1/f^2 after a resonnance at 0.6Hz. The attachement shows the open loop without vs with the filter.

[Stuart A, Jeff B]

Templates have been committed to the sussvn for the H1 TMSY (TMTS) suspension, derived from L1 TMSX, as follows:-

2014-03-24_0900_H1SUSTMSY_M1_WhiteNoise_L_0p01to500Hz.xml
2014-03-24_0900_H1SUSTMSY_M1_WhiteNoise_T_0p01to500Hz.xml
2014-03-24_0900_H1SUSTMSY_M1_WhiteNoise_V_0p01to500Hz.xml
2014-03-24_0900_H1SUSTMSY_M1_WhiteNoise_R_0p01to500Hz.xml
2014-03-24_0900_H1SUSTMSY_M1_WhiteNoise_P_0p01to500Hz.xml
2014-03-24_0900_H1SUSTMSY_M1_WhiteNoise_Y_0p01to500Hz.xml

These can be made available by svn'ing up the /ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSY/SAGM1/Data/ directory.

Let me know if there are any issues with their use.

n.b. the reference included in these templates is for L1 TMSX at Phase 3b (in-vacuum) of testing.

We have accumulated for ~5 days on  Y1. Plot attached. Kyle will start to analyze the RGA data this week.

model restarts logged for Sun 23/Mar/2014
2014_03_23 10:44 h1broadcast0
2014_03_23 10:44 h1fw0
2014_03_23 10:44 h1fw1
2014_03_23 10:51 h1broadcast0
2014_03_23 11:19 h1dc0
2014_03_23 11:21 h1broadcast0
2014_03_23 11:21 h1fw0
2014_03_23 11:21 h1fw1
2014_03_23 11:21 h1nds0
2014_03_23 11:21 h1nds1
2014_03_23 11:36 h1broadcast0
2014_03_23 11:41 h1broadcast0
2014_03_23 11:43 h1broadcast0
2014_03_23 14:29 h1lsc
2014_03_23 14:32 h1lsc

All restarts were expected. h1lsc due to DAQ issues, h1broadcast0 has memory swapping issues.

The COMM guardian now has states to lock the IR to the arm using the refl bias path, I will leave this running overnight. 

Measuring the COMM noise with the refl DC bias path engaged gives repeatable results, while we did not repeatable results without it.  However, something seems to be wrong with our calibration.  Today, when the refl bias path is not engaged we wander over the peak in about 10 seconds, and all th way off resonance, so we know that the COMM noise is at least a fwhm of the IR resonance in the arm, 164Hz. 

When we lock the refl bias path, measure a spectrum and correct for the gain of the refl DC bias path, the rms should be the noise of the refl bias path.  However, we are consistently measuring a noise around 35 Hz (with cavity pole corrected for) or around 9 Hz without taking out the cavity pole.  However, we know this is wrong. 

At least with a repeatable measurement we can evaluate what make the noise worse and better, even if we don't yet trust the calibration. Attached is a plot of the COMM noise measured with refl DC bias engage, the gain of that path corrected for but not the cavity pole.  In the blue trace the OpLev damping was on for both pitch and Yaw, in the green trace the pitch damping was off on both the ETM and ITM.  The coherence are shown in the bottom panel, the solid lines were measured with no damping, the dashed lines with damping.

With the damping on, the noise at 0.45Hz is reduced by a factor of 5.5, although it doesn't seem to change the rms much in this plot. 

The green trace was measured with lower bandwidth because the lock was not lasting more than a few minutes today, especially with the damping off.

Hugh graciously ran new tf's on Saturday. I came in today to look at them and, once again we have some issues. I'm betting we have some rubbing stops on TMS again...sigh. We had this problem before, Corey went in and did some adjusting, my first attached image shows he mostly fixed it, although I believe Arnaud had told me they had reason to believe the TMS was still rubbing some then (you can still see a little something at 2.5hz). My second image shows the TF from yesterday, and a peak that I had seen before at 2.5hz has re-appeared. Not as bad as the stuff at the beginning of the month, but we were doing better just a few days ago.

Dave O, Stefan

While attempting to lock the PRC we noticed that POB_Air_B_RF_I_Err was low on signal. We traced this back to a low de-mod signal (see attached plot). We traced this down to a tripped fused in the ISC_R2_Rack. This tripped on the 17th March. We tried to reset it but it simply re-tripped again.

When we locked PRX and PRY, we were also surprised that we needed to flip the feed-back sign in PRCL to lock on the carrier (compared to the settings the LSC guardian uses).

Updated the IMC ODC bitmask to again include the min trans power checks - not sure why they went missing.
Also updated the cds/h1/scripts/h1setODCbitmask script.

After about 30 mins of disk activity h1boot completed its reboot. Here is the current status of the systems:

DAQ

DAQ Frame Data Was Lost. Here are the frame gaps on the two frame writers

So no data from 08:30 to 10:45PDT. We should investigate if we cannot make the DAQ more independent of h1boot. During run time the DAQ logs to the target area, and I assume that is why the frame writer stop times are after h1boot's demise and at different times.

At 11:18 I performed a clean restart of the DAQ since the framewriters and broadcaster had restarted themselves. All came back ok except:

h1lsc model is showing a DAQ error in its STATEWORD. No error from h1dc0 on this node.

h1broadcaster0 shows the same swap memory problems, I rebooted this unit to clear the error. We will add more memory soon to fix this.

Front Ends

All the front ends EPICS updates became unfrozen, no restarts were needed. The DAQ restart cleared the h1iopoaf0 0x2000 status (model change last week) but an h1lsc DAQ error is showing (see above)

Workstations

Good news on the workstations, they all became unfrozen and appear to be operational. Some wall mount TV servers seem to be not operational, we can fix these tomorrow.

Remote Monitoring

The Vacuum and other MEDM screens are being updated on the cds  web page.

Remote access using 2FA now working.

SysAdmin

Looking at dmesg and logs on h1boot I cannot determine if a full FSCK was ran. We should still schedule this for Tuesday.

I have switched the RSYNC backup of h1boot by cdsfs1 on again.

IFO

I'll leave the verification of IFO operations to the commissioning crew to check.

(Sheila, Daniel)

We used the normalized PDH signal to feed back to the additive offset of the common mode servo which in turn moves the mode cleaner and the laser frequency. The loop bandwidth was 20Hz with a 1/f shape. This kept the red laser light on resonance in the arm cavity for good. We then swept the offset of the normalized PDH error signal to scan the cavity resonance. The attached plot shows the sweep. It took about 20 seconds. The FWHM as measured by the red transmitted light corresponds to 49.7 units. However, it should be 165Hz. The calibration factor was set to 0.208 (from 0.063).