7:50-9:14 Heading to End Y for cleaning - Karen
8:00 Crystal chiller refilled (Maintenance) - Justin
8:45-10:30 Heading to EndX/EndY to scan electronics – Filiberto
8:50-12:05 Working in LVEA – David H.
8:58 End Y transitioned to Laser Hazard- Jax
9:00-10:18 Searching for TCS parts in LVEA – Thomas
     LN2 delivery to CP1 – Praxiar
9:10-13:01 Going to End Y for TMS alignment – Corey/Jax
9:15-12:00 Chassis work on ISC racks in LVEA – Aaron
9:40-10:06 Heading to End X to check leaking valve – Hugh
9:42 Working at Mid Y – Jodi
10:00 Replacing RAM modules in h1broadcast0 - James
10:14 Rebooting H1 boot server – James
10:35-12:00 Cable work by HAM4 (LVEA) – Filiberto
10:45 Removing iLIGO RGA from BSC10 – Kyle
11:05 Heading into the LVEA – Betsy
11:42 Working on HAM5 – Hugh/Jim
12:07 DAC restart – Dave
12:44 Back to HAM4 – Filiberto
13:13 Monolithic welding of ITMx and ITMy at LVEA - Travis
13:15 Moving Laser barrier from HAM2 to BSC3 area – Justin
13:48 Heading into H2 PSL enclosure (Laser Hazar) – Gerardo
13:55 Going to End X - Cris

My estimate of N2 leak/outgassing for the Y1 module at LHO. The accumulation took place over 4.8 days.

Total pressure at the end according to the CC gauges was 5e-8 torr and the total RGA ion current was 2e-10 amps yielding 0.004 amps/torr(H2).

Ignoring the gauge factors I get an N2 leak/outgassing rate of 4e-9 tl/sec. There may also be a contribution from CO generated by the CC gauges.

Also, the RGA setup was coupled to the tube at an oring angle valve so

there are a number of small orings in close proximity to the RGA. Kyle did perform a mild bake on this setup. In addition, included in the accumulation

is the LN2 pump at YMID.

I would say we have no measureable air leak on Y1.

The RGA data is shown on a log plot for better visibilty - on a linear plot the curves appear straight.

I have been checking the status of the front end systems while h1boot was down between 17:13 ad 17:45UTC today.

• all front end models continued to run
• the epics sequencer froze up (trying to checksum the configuration files) meaning that no data was being transferred between the EPICS databases and the front end code
• On MEDM screens: monitor channels froze at their last value, control channels permitted changes which were then not applied to the model
• DAQ data (fast and slow) continued to flow from the front end models to the DAQ
• all models' CPU usage improved slightly, either speeding up by a microsecond or becoming less noisy, as EPICS data was not being transferred to the front end core.

as a consequence to this, CONLOG was recording changes which may not have been applied, and GUARDIAN was running on unchanging input data.

23 channels were removed for a new total of 122,602.

Taking advantage of the planned reboot to run an FSCK on h1boot, the following fixes/changes were applied to h1boot, h1build, and h1broadcast0:

Corrected missing console output at boot by following the instructions left in /etc/issue on these machines, namely:

-----------------------------------------------------
Your system seems to be missing critical device files 
in /dev !  Although you may be running udev or devfs, 
the root partition is missing these required files !

To rectify this situation, please do the following:
mkdir /mnt/fixit
mount --bind / /mnt/fixit
cp -a /dev/* /mnt/fixit/dev/
umount /mnt/fixit
rmdir /mnt/fixit

You may refer to these instructions at /etc/issue.  
If you previously had an issue file, it has been 
backed up at /etc/issue.devfix.  Once you've fixed 
your system, you will have to restore your old issue 
file in order to get rid of this warning.

Thanks for using Gentoo ! :)
http://bugs.gentoo.org/show_bug.cgi?id=40987
-----------------------------------------------------

And then removed the warning with:

# mv /etc/issue.devfix /etc/issue

Enabled logging boot messages to file by updating RC_BOOTLOG from "no" to "yes" in /etc/conf.d/rc:

# RC_BOOTLOG will generate a log of the boot messages shown on the console.  
# Useful for headless machines or debugging.  You need to emerge the 
# app-admin/showconsole package for this to work.  Note that this probably
# won't work correctly with boot splash.

RC_BOOTLOG="yes"

This requires emerging app-admin/showconsole, as noted in the config file:

--> Check what the emerge will touch
# emerge --pretend app-admin/showconsole
--> Install showconsole
# emerge app-admin/showconsole

Note, this generated the following warnings from emerge:

* IMPORTANT: 2 config files in '/etc' need updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.

This is because someone did not clean up after themselves on 29 Jul 2010:

# find /etc -iname '._cfg????_*'
/etc/ssh/._cfg0000_sshd_config
/etc/._cfg0000_ntp.conf

etc # ls -al        
total 1388
drwxr-xr-x 49 root root   4096 Mar 25 10:00 .
drwxr-xr-x 26 root root   4096 Feb 11  2012 ..
-rw-r--r--  1 root root   1517 Jul 29  2010 ._cfg0000_ntp.conf
 ...
etc # cd ssh
ssh # ls -al
total 176
drwxr-xr-x  2 root root   4096 May 24  2011 .
drwxr-xr-x 49 root root   4096 Mar 25 10:00 ..
-rw-------  1 root root   3740 Jul 29  2010 ._cfg0000_sshd_config
 ...

I did not correct this problem. The diffs did not show any substantial config options missing.

All systems were rebooted, forcing an FSCK on restart:

# shutdown -r -F now

model restarts logged for Mon 24/Mar/2014
2014_03_24 02:27 h1broadcast0
2014_03_24 02:33 h1broadcast0

unexpected restart of broadcaster due to memory swapping, hopefully fixed by todays upgrade

Here are the times h1boot and h1broadcaster0 were offline for today's maintenance work

[Travis Arnaud] This is a late alog from Friday

On friday afternoon,  B&K measurements on the cage structure of ETMY and TMSY were completed in chamber, with the ISI locked. For each suspensions, two degrees of freedom have been tested, in the horizontal plane, labelled as X and Y (respectively axis perpendicular to the arm and along the arm, see pictures).

TMSY Results (2014-03-21_Phase3a_H1ETMY.pdf)

* Clean data showing the resonnances in the Y direction @ 111Hz, 179Hz and 279Hz and in the X direction @ 163 Hz, 200Hz, 261Hz and 293Hz. No concerns here since there is there is no high Q resonnances below 150Hz. Data is compared with LLO TMSX

ETMY Results (2014-03-21_Phase3a_H1ETMY.pdf)

* Main resonnances at 72Hz (in the Y direction) and 76Hz (in the X direction) look well damped, with a similar Q than the other quad structures etmx and itmx previously tested.

[Method]

For this measurement we used the B&K hammer and tri-axis accelerometer setup, acquiring data with the Pulse software on the windows laptop. The template used has been copied fom T1000697.

Data collected lives under the svn in

/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/BandK

/ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSY/BandK

The accelerometer was mounted on the structures as described on the pictures, with detailled axis orientation.

Files attached.

This will affect all operator workstations, any file on /opt/rtcds will be unavailable.  This includes models, filter files, and medm screens.

Attached are transfer functions from TMSY TFs from last night, added to the other results of last week.
I also attached a spectra of the individual osems with the suspension undamped

Installing memory in the h1broadcast0 computer, affects the dmt system.

Laser Status: 
SysStat is good
Output power is 28.1 W (should be around 30 W)
FRONTEND WATCH is Active
HPO WATCH is red

PMC:
It has been locked 2 days, 21 hr 1 minutes (should be days/weeks)
Reflected power is 1.3 Watts and PowerSum = 11.4 Watts.
(Reflected Power should be <= 10% of PowerSum)

FSS:
It has been locked for 0 d 1 h and 21 min (should be days/weeks)
Threshold on transmitted photo-detector PD = 0.54 V (should be 0.9V)

ISS:
The diffracted power is around 9.94 % (should be 5-15%)
Last saturation event was 0 d, 11 h and 43 minutes ago (should be days/weeks)

[Corey Jeff Betsy Travis Arnaud]

Today, we had several in chamber rounds in order to improve the roll/vertical transfer functions of the TMSY suspension. Results from last thursday night attached were still showing badness, especially in the roll degree of freedom with an extra mode at 0.89Hz (first pdf), but no TF has been ran between Friday's work, and this morning. The pdf attached shows TF comparison of TMSY in April last year (orange, used as "reference"), TMSY March 11th (black, first in chamber TF, before alignment work), and TMSY last thursday, march 20th, (pink) 

In chamber work from today :

1) Corey and Jeff started by moving some of the earthquake stops (quick dtt tf was ran after, cf green curve of TMSY.png). No change, since 0.89Hz still present

2) Betsy tried centering some of the flags close from the edge of their osem (cf blue curve, taken after the work). No change

3) Finally, Travis and I modified the cable routing. First we gave some slack to the cable between ISI and top mass by changing the orientation of the clamp. This significantly moved the top mass, that was probably beeing hold by those cables. Some of the osems went completely out (cf Screenshot) so we had to recenter them. We took a quick dtt TF, but it still looked somehow not good enough. We then loosened the cablings between the table and the top mass. The red curve shows how the 0.89Hz moved to 0.8Hz after the overal work.

I will run long measurements overnight, to have an idea of what's happening on the other degrees of freedom, but it sounds like their will be more cable routing work, as well as alignments to check.
Note that LLO recently had the go through the same process, cf Stuart's alog, and mitigated the issue by modifying the cables routing.

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)

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).

Has the analog whitening settings changed on the ETMX optical lever? I've compared a high-frequency spectrum with a measurement I took in February, and there's reported tons more motion above 2 [Hz], when the ISI motion is roughly equivalent if not better at these frequencies (see attached). Looks there's an extra 1:10 analog filter that's not being compensated or something...