Demonstrated MTP safety valve closes and turbo spins down with the removal of AC to the scroll pump -> This mimics the functionality of a loss of "Motor Run" signal from the nominal backing pump -> Shut down QDP80 and purge air supply

model restarts logged for Tue 01/Apr/2014
2014_04_01 12:39 h1susetmy
2014_04_01 12:39 h1susitmy
2014_04_01 12:42 h1broadcast0
2014_04_01 12:42 h1dc0
2014_04_01 12:42 h1fw0
2014_04_01 12:42 h1fw1
2014_04_01 12:42 h1nds0
2014_04_01 12:42 h1nds1
2014_04_01 12:51 h1susitmx
2014_04_01 12:52 h1susetmx

All restarts expected and part of Tuesday maintenance.

The attached log/log plot gives the estimate that it will take a little over three weeks
for the pressure to get to 3 x 10^-7 torr which will reduce to 1 x 10^-8 torr when the chamber
is open to the cryo pump.

There was a magnitude 8 earthquake in Chile, all BSC ISIs tripped. 

Y-end pumping interrupted for ~15 mins during valve install -> Flex line from MTP to Turbo Header can now be isolated at the MTP plumbing -> Flex line from MTP to locally mounted scroll pump can now be isolated at the MTP plumbing -> Currently both QDP80 and scroll pump are running, QDP80 backing MTP and scroll running but isolated from MTP -> ~500 watt scroll pump is currently being powered via an extension cord plugged into local vacuum 120VAC receptacle -> Would like to add a dedicated 120VAC receptacle local to the MTP control panel and eliminate the "scurge" of the extension cord

Since oplev damping might be used for Y arm commssioning as it is currently for X arm, I modified the QUAD_MASTER simulink model to have oplevs feedback on all the quads. 

• Created a common part called FOUROSEM_STAGE_OPLEV.adl living in /opt/rtcds/userapps/trunk/sus/common/models (copied from FOUROSEM_STAGE.adl) with a new path linking the oplev signal to UIM and PUM actuation (going through the DRIVEALIGN matrix) cf first screenshot.
• In QUAD_MASTER, the L1 and L2 parts were replaced with the newly created "FOUROSEM_STAGE_OPLEV"
• Hooked back h1susetmx and h1susitmx to QUAD_MASTER
• Modified the medm screens : Added a menu button at UIM and PUM levels. This screen might need to be revisited for clarity. Stuart is making a similar change at LLO with a better looking screen, so we will update when change is commited
• Took safe snapshots of the four quads with oplev switches off

Only FOUROSEM_STAGE_OPLEV.adl part was commited to the svn

Day Shift Summary
LVEA Laser Hazard

Apollo – End-Y drilling holes for Op-Lev

08:30 Jeff – LVEA beer garden checking dust levels
09:40 Thomas – in LVEA looking for parts
09:53 Andres – Working near HAM2
10:21 Water delivery
10:30 Apollo – finished at End-Y
10:30 Apollo – LVEA working on N2 plumbing near H2 Input Arm
10:39 Arron – Going to End-Y to pull op lev cables 
10:45 Kyle – At End-Y running HEPI vacuum near spool
10:56 Betsy – LVEA welding area
12:36 Dave – Restart SUS-ITMY model, SUS-ETMY model, and DAQ
12:50 Dave – Restart SUS-ITMX model and SUS-ETMX model 
12:55 Karen – Cleaning at End-Y
12:55 Cris – Cleaning at End-X
13:05 Dave – LVEA working on TCS
13:10 Thomas going to End-Y
13:30 Praxair Nitrogen delivery to CP-2
13:32 Ops – Recover ITMY, ETMY, ITMX, and ETMX after model restarts
13:45 Sheila – At End-X to remove viewport covers to look for green beam clipping
14:00 Kyle – Shutting down pumping at End-Y to make plumbing change
14:11 Apollo – Starting drilling at H2 Input Arm

Aidan. Eric G. Dave H. Alastair H. Greg G.

The third laser we plumbed in started leaking from the housing this morning. We contacted the manufacturer. It turns out that this is a known problem to them.

• The manifold on the early version of this laser is held in place with set screws - these allow for leaks according to Access
• The newer version of this laser has replaced the set screws with more robust round-head screws
• Our remaining two lasers have the round-head screws.
• We plumbed in laser #4. So far it shows no sign of leaking.

The photos show the old and new manifolds on the lasers.

SUS (Arnaud and Dave)

Cleaned up SUS QUAD models and added optlev input into L1 and L2 fourosem parts. Recompiled, installed and restarted the models h1susitmx, h1susitmy, h1susetmx, h1susetmy. We are leaving the common model QUAD_MASTER.mdl a local mod for now and not commiting to SVN.

GDS: Jim:

New version of GDS installed, please see Jim's entry for details

DAQ (Dave)

DAQ was restarted to take the SUS changes.

Conlog (Dave)

Conlog was reconfigured for the new channel list.

LDAP (Jonathan and Dave)

The CDS LDAP server was reconfigured to define user groups.

Model/DAQ restarts as of time of writing:

2014_04_01 12:39 h1susetmy

2014_04_01 12:39 h1susitmy

2014_04_01 12:42 h1broadcast0

2014_04_01 12:42 h1dc0

2014_04_01 12:42 h1fw0

2014_04_01 12:42 h1fw1

2014_04_01 12:42 h1nds0

2014_04_01 12:42 h1nds1

2014_04_01 12:51 h1susitmx

2014_04_01 12:52 h1susetmx

Here is the status of the YEND pumpdown.

Roughing started at 18:20 utc on the 29th The cold cathode(PT410B) trace begins at 3:40 utc on the 30th.

See attached PT410B data.

For reference here is the XEND data from January - https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=9154

Values in the system manager are flat lined. There are multiple lines of errors in the EPICS IOC of the following (screen shot attached):

Error code 4: ~~~MYSTERY ERROR!!!~~~ Go Google "ADS return codes"!

and

Error code 1861: ~~~MYSTERY ERROR!!!~~~ Go Google "ADS return codes"


Googling "ADS return codes" gives:

4
Insert mailbox error
No ADS mailbox was available to process this message.
Reduce the number of ADS calls (e.g ADS-Sum commands or Max Delay Parameter)

1861
timeout elapsed
Check ADS routes of sender and receiver and your firewall setting

Recovered BSC1, BSC3, BSC9 and BSC10 after ITMX, ETMX, ITMY, and ETMY SUS models restart. 

We measured the WFS sensing matrix yet again. 

The green ones are consitent acros the measureemtns we've made to within a factor of 2.  ETMX PIT is the most consistent WFS B pit signal, the sign has stayed the same but the gain has changed by a factor of 3 .

We have some new settings for the Comm Handoff, so I repeated the usual measurements:

COMM PLL Servo Board

• Input gain: 27dB
• Common Fitler 1: ON
• Common Filter 2: ON
• VCO Comp: ON
• Low Pass: ON

CM Servo Board

• Input 1 gain: 11dB
• Input 1 pol: POS
• Input 2 gain: 6dB
• Input 2 pol: NEG
• Common Comp: ON
• Fast Gain: 6dB
• Fast pol: POS

LSC-CARM Filter

• Gain: 80
• FM1, FM4, FM5, FM8

LSC-REFL-SERVO-SLOW

• Gain:1
• FM1

MC2_M3_LOCK_L

• Gain: -300
• FM9

MC2_M2_LOCK_L

• Gain: 0.10
• FM3, FM4, FM10

MC2_M1_LOCK_L

• Gain: -1
• FM1, FM2

MC2_M3_ISCINF

• Gain: 1
• Filters OFF

1. Common path OLTF: Handoff_COMM_OLTF_mag/phase.txt
2. Inject into fast path, cf/1-cs OLTF: Handoff_cfast_OLTF_map/phase.txt
3. Inject into slow path, cs/1-cf OLTF: Handoff_cslow_OLTF_mag/phase.txt
4. Crossover using LSC_CARM inputs: /ligo/home/sheila.dwyer/ALS/HIFOX/COMM/Crossover_April1.xml

The UGF of the comm handoff is now 3kHz with 80 deg phase margin. The crossover between the fast and slow path is at 13 Hz with 19 deg phase margin.

The gds tools (awggui, diaggui, diag, etc) have been updated to 2.16.12 to provide access to the dmt servers using dmtviewer.

The dmtviewer program connects to dmt servers specified by the DMTWEBSERVER environment variable.  Since the dmt servers are not part of the cds system, a kerberos ticket is required to access the servers.  The command "kinit username" where username is your LIGO.ORG username will give you a ticket.  Don't forget to use the command "kdestroy" when you're finished to remove the kerberos ticket.

Chris, Sheila

Our measurements of the COMM noise with the WFS locked have an rms of 20Hz, measured down to 0.1 Hz.  To make sure this was reasonable, we turned off the refl bias path so that the laser was locked only to the green beat note. The transmitted power fluctuations are noticably less than the HWHM of 40Hz, so this seems believable. (StripTool is the second screenshot attached). 

We wanted to try locking the arm half way down the fringe so we could make a measurement of the noise using the transmitted power.  Since the IR trans PD is normalized to 1 when the cavity transmission is maximized, the calibration of this signal is just a high frequency gain of 84 (FWHM of the arm cavity), and to correct for the refl bias loop gain we have a pole at zero and a zero at 3Hz.  The correct calibration has a more complicated frequency dependence, so we would have to do the real calibration to make a comparison above about 42 Hz.  Neither of these traces have the cavity pole at 42 Hz corrected for.  You can see that the side of fringe measurement agrees with the normalized refl PD signal well up to 100 Hz . (1st screen shot attached)

We repeated the measurement in the normal configuration, where we lock on resonance using the refl bias path, and the noise is the same (30Hz rms down to 0.02Hz). The RMS is dominated by the pitch mode, so we will work on increasing the WFS bandwidth tomorrow. Tonight we tried OpLev damping (this added noise around 1 Hz) and turning up the pitch OSEM damping gains (inconclusive so far). 

We redid the measurement with the WFS outputs held, and saw that the noise was high again (100Hz rms down to 0.1Hz), with the WFS on again we were back to the low noise state. So we can safely say the WFS are helping.

We also checked that the noise is the same from 3-100Hz with and without the refl bias path engaged. 

For future reference I took a spectrum of the 5 HSTS (MC1 MC2 MC3 PR2 PRM) from monday morning before the corner station was vented.

The isolation and damping on HAM2 and HAM3 ISIs were ON, and feedforward was OFF. The suspensions damping loops were closed. The chambers were under vacuum.

The attached pdf shows a comparison between the 5 HSTS, for every "mass" levels (M1 M2 and M3) and every degree of freedom.

Few things to notice on the plot :

- The performances are really consistent from one chamber to an other

- Signal is really close to sensor noise, especially at the bottom mass

- There is an interesting feature between ~0.1Hz and ~1Hz seen for longitudinal transverse and vertical dofs. This is something I would need to double check, but I'm pretty sure it is transmitted ground motion.