I added a new GUARD_OVERVIEW screen to the sitemap, accessible from the blue GRD button on the sitemap.

Each block represents a guardian node.  There are place holders for nodes that I expect will show up eventually.  I also expect that more nodes will eventually be added that I haven't accounted for yet.

Each block has a button at the left that will open up the guardian control panel for the node.  The overall background color of the block represents the MODE of the node:

• orange: LOAD
• yellow: PAUSE
• blue: EXEC
• purple: MANAGED
• red: ERROR

There are three indicator lights, which, from left to right indicate:

• is there a notification in the node or not (yellow/green)
• does the current state equal the requested state (orange if not, green otherwise)
• the run status of the current state (various colors depending on the run status)

Blocks that are white indicate nodes that are current not running.

Keita K. informed me that whitening for OLs were off for both ITMX and ETMX and after looking at the spectra, I also agreed. So I went out to the field racks to check that the settings were correct.  

The OpLev whitening boards use a binary I/O daughter board to enable the gain stages.  They looked like they were on the correct settings for two levels of whitening, which matched the de-whitening filters set in software so I unplugged and plugged the board back in and this seemed to solve the problem.  I'm happy that this solved the problem, but I'm perplexed on how it happened.  The daughter boards just plug into the front of the chassis with no screws so it may have been bumped loose, not good.

I'm still investigating when this might have happened but it has some pretty big implications for the relatively new damping scripts that Stefan made, I've sent him an email.

As reported earlier, the IMC guardian code was upgraded.  This upgrade is now fully complete and committed.

The new IMC guardian module is located at:

USERAPPS/ioo/h1/guardian/IMC.py

This new guardian follows a newer paradigm, whereby we follow a slightly less scrict heirarchy:

Rather than three nodes controlling the IMC locking (ISC_IMC, SUS_MC2, IFO_IMC (manager)), we now have just one: IMC.   The SUS_MC2 module is now identical to all other suspensions, without additional controls states for IMC locking.  The IMC guardian module instructs all IMC suspension nodes (SUS_MC{1,2,3}) to go to their ALIGNED states, and monitors those states.  It then controls all of the "LOCKING" filters in the SUS MC2 controller directly.  The result is much simpler code and simpler control.  I expect that we'll use this paradigm for the rest of the ISC control as well.

The trade off is that we need to be much more carefull about defining which channels are under SUS control and which are under ISC control.  Two different guardians should still never touch the same channels.

The new IMC guardian also adds more sophisticated fault checking (for PSL, ISI, and SUS fault conditions), falling into a FAULT state if there is a problem.  This state then uses the new notification feature of guardian to notify the operator of what the problem is.  Once the fault has been cleared, it proceeds back to the state that was previously requested.

Relieving Corey G for a few hours.

- Fil and Luis moving cabling from test stand to BSC10 1:35 PM PT

- Karen cleaning at EY 1:15 PM PT

- Kiwamu doing a DAQ restart 3:01 PM PT

Evan, Yuta, Kiwamu,

Commissioning of the dithering system is underway.

A summary of the red commissioning from this morning:

• We locked the PRMI with the 1f signals and noticed that the lock was fragile.
• Then we realized that the demodulation phase of REFLAIR_RF45 was set back to 133 deg which should be 144.6 deg (see alog 9930) to make the two loops decoupled.
  • This was missing in the guardian
• Once we confirmed that the PRMI can stay locked, we moved on to PRX.
• We started commissioning the dither system (ADS = Alignment Dither System).
  • This is still an ongoing task.

(Alexa, Jeff)

The IMC-X_M1 and IMC-X_M2 wresg calibration filters are off by a minus sign. I have attached the plots depicted in foton and those produced by Jeff's model. The phase is 180 deg in foton, but should be 0 at DC. I have not updated foton, but an email has been sent out to the relevant parties.

The BSC-ISI watchdog plotting software was reported disfunctional by Hugh earlier this week.

I looked into the scripts and they were fine. What I had missed is that Charles had updated the BSC-ISI WD screens, wich thus needed to receive an svn up at the site to match the latest wd_plotting software update, performed when updating the HAM-ISI models last week.

I run the the svn up on: /opt/rtcs/userapps/release/isi/common/medm/ISI_CUST_CHAMBER_WATCHDOg.adl remotely.

The WD plotting software now works on all the SEI platforms of H1.

HAM2 and HAM3 as well as the HEPIs tripped at the exact same time (actuator trip for all of them) @ gps 1077061619 (15:46 PT)

15:47 DAQ Restart. Support of h1lsc model change.

   Tested the dust monitors at End-Y. Found dust monitor #2 (in the test stand cleanroom) was not working. I moved dust monitor #1 (from the spool area cleanroom) to under the test stand, and verify its operation. Dust monitor #2 has been returned to Richard. 

Seems like it was yesterday's burt-restoring to a bad time for ALS WFS. Manually restored them.

At 14:25:00 and 14:26:00 a signal was injected into the seismometer channels for H1:PEM-MX to test a suspected delay in signals showing up in dataviewer displays in the control room.  There was no delay. Signal was injected by striking the floor of the VEA with a heavy plastic mallet.  There is a time conversion issue on playback in dataviewer in which the UTC time entered is not the time that gets played back, but if GPS time is used, it is correct.  This will be investigated and corrected.

Except for Corey doing some last moment inventorying, the Cartridge is ready for install.  The Test Stand is stripped of all field cables, in-vac cables are all tucked away, accessible areas of the ISI were wiped down (not too much collected it seemed,) and covers are on ready to drop around Stage0 when the assembly lifts from the Stand.  No incumberances seen at this time.

Thanks to Betsy & Mitchell.

Keita is getting started with green WFS, so we are doing the strait shot alignment first.

Baffle PD 1: PIT 221.0 YAW  -228.1, saved using the new guardian state

Baffle PD4 PIT 290.6 YAW -289.8 saved as well

Alinged: 255.8PIT  -259 YAW saved as Alinged

I didn't move PR3 since the spot already looks centered on the camera: -244 PIT -254 YAW

Installed DustMonitor 12 in clean room over Ham5.  Alarm levels are set high at the moment as the chambers are closed.

Cleaned the lens and repositioned the camera.  Zoomed in and focused on the ITM.  We can see PRMI spot on optic.  Someone may want to make more adjustments.  The camera view is probably upside down.

This completes dewar vacuum jacket pumping exercise.  Summary below: 

8514374 As found = 780 microns -> As left on 12/20/2013 TC = 4 microns, Pirani = 1.5 x 10-3 torr, 
8514372 As found = 28 microns -> As left on 1/23/2014 TC = 4 microns, Pirani = 1.4 x 10-3 torr, 
8514371 As found = 61 microns -> As left on 1/27/2014 TC = 7 microns, Pirani = 1.6 x 10-3 torr, 
8514375 As found = 45 microns -> As left on 1/31/2014 TC = 6 microns, Pirani = ? torr, 
8514376 As found = 49 microns -> As left on 2/4/2014 TC = 6 microns, Pirani = 1.7 x 10-3 torr, 
8514377 As found = 42 microns -> As left on 2/7/2014 TC = 6 microns, Pirani = 1.8 x 10-3 torr, 
8514379 As found = 81 microns -> As left on 2/13/2014 TC = 6 microns, Pirani = 2.0 x 10-3 torr, 
8514380 As found = 58 microns -> As left on 2/21/2014 TC = 7 microns, Pirani = 1.8 x 10-3 torr.

(Jax, Keita)

Yesterday morning we measured the sensing matrix for the ALS WFS. We did this by Injecting 30000cts at 5Hz into H1:SUS-L2_(I/E)TMX_L2_TEST_(P/Y)_EXC, then measuring the transfer function between H1:ALS-X_WFS_(A/B)_I_(PIT/YAW)_OUT and H1:SUS-(I/E)TMX_L3_OPLEV_(PIT/YAW)_OUT. 

In cavity basis:

Pitch Sensing Matrix: (WFS ct/uRad)

Pitch Input Matrix: (uRad/WFS ct)

Pitch Output Matrix:

Yaw Sensing Matrix: (WFS ct/uRad)

Yaw Input Matrix: (uRad/WFS ct)

Yaw Output Matrix:

Raw data: 

Useful information for determining sign conventions from raw data:

1. ETM/ITM Yaw is defined with positive as a counter-clockwise rotation of the optic around the z-axis. 

2. ETM/ITM pitch is defined as positive pitch "down", but ITM oplev is set such that an increase in pitch gives a decrease in oplev measurement.

ETM Yaw:

ETM Pitch:

ITM Yaw:

ITM Pitch:

The BS IS tripped on GS-13 watchdog at 1328 utc this morning.  Traffic, wind, something--plotting scripts still not functioning...

Anyway, I brought it back to lvl2 with 750mHz blends on stage2 and T250s on all Stage1 blends except T100mHz_0.44 blends on X & Y dofs.

I reset the target positions, there was about 700nrads on RX and <4um on Z, all other shifts were less.   Please let us know if this impacts any alignments.  This allowed for a one button isolation.