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.

at 10:09PDT I rebooted h1boot via front panel reset button after finding its console locked up. For the past 20 mins it looks like it is file checking the mirror raid, those two disks are continuously active.

The vacuum overview medm on the VE workstation is live and everything looks good.

The DAQ units are updating their UPTIME counters, but it appears that h1broadcaster0 is down, so most probably no DMT data is being sent. I'll check the frame file status when h1boot is healthy.

MEDMs associated with front ends are visible, but frozen at 06:42:21PDT this morning (GPS time 1079617357).

The frame writers file listings I'm getting from h1fw0 and h1fw1 are confusing. h1fw0 says it last wrote a frame at 08:10PDT, and h1fw1 has a last time of 08:30PDT. I'm not sure why these are exactly on a 10 minute boundary (only second trends use that time) and I'm not sure why they would stop at different times and over an hour from the h1boot problem.

The external epics gateway is still running, I am able to report CP levels are good:

HVE-LY:CP1_LT100               91.5751

HVE-LX:CP2_LT150               92.5519

HVE-MY:CP3_LT200               90.9646

HVE-MY:CP4_LT250               91.6972

HVE-MX:CP5_LT300               91.5751

HVE-MX:CP6_LT350               91.5751

HVE-EY:CP7_LT400               92.7961

HVE-EX:CP8_LT500               91.3309

I'm noticing a possible problem with h1boot, the NFS server of the /opt/rtcds file system. Machines which mount this file system are not letting me log in (they freeze after accepting my password) and h1boot is not responding to ping requests.

The disk-to-disk backup of h1boot at 05:00 this morning completed normally at 05:04. MEDM snap shot images suggest the problem appeared at 06:42 this morning.

As Kyle mentioned in his alog of Friday he is running an accumulation measurement in Y1. Alarms were expected as the pressure rises in the module and this morning we have them. Pressures are at 4e-8 so there is no cause for worry. The rate of rise is close to 1e-8 torr per day. Monday this measurement will be terminated if all goes well.

model restarts logged for Sat 22/Mar/2014
2014_03_22 12:33 h1fw1

unexpected restart of h1fw1.