I forgot to alog this, its been usable for a few weeks now.

I made a script that will create a map of all the nodes and who is managed by whom. It uses the same packages as the normal Guardian maps for a similar look, and the same colors as the medms. The script will only map the current management, so if managers change, it will have to be re-ran for a new map. I will try to make this better later, but for now this will have to work.

Location: /opt/rtcds/userapps/release/guardian/manager_map.py

I attached a sample output.

T240 Centering script results:

There are 18 T240 proof masses out of range ( > 0.3 [V] )!
ITMX T240 1 DOF X/U = -3.297 [V]
ITMX T240 1 DOF Z/W = 0.439 [V]
ITMX T240 2 DOF Y/V = 0.505 [V]
ITMX T240 3 DOF X/U = -3.301 [V]
ITMX T240 3 DOF Z/W = -0.341 [V]
ITMY T240 1 DOF X/U = -0.433 [V]
ITMY T240 1 DOF Y/V = 0.359 [V]
ITMY T240 1 DOF Z/W = 0.34 [V]
ITMY T240 2 DOF Y/V = 0.43 [V]
ITMY T240 2 DOF Z/W = -0.345 [V]
ITMY T240 3 DOF X/U = -0.941 [V]
ITMY T240 3 DOF Y/V = -0.319 [V]
ITMY T240 3 DOF Z/W = -3.275 [V]
BS T240 1 DOF Y/V = 0.904 [V]
BS T240 1 DOF Z/W = 0.384 [V]
BS T240 2 DOF X/U = 0.96 [V]
BS T240 2 DOF Z/W = 0.481 [V]
BS T240 3 DOF Z/W = 0.927 [V]


All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = 0.158 [V]
ETMX T240 1 DOF Y/V = 0.143 [V]
ETMX T240 1 DOF Z/W = 0.19 [V]
ETMX T240 2 DOF X/U = 0.061 [V]
ETMX T240 2 DOF Y/V = -0.052 [V]
ETMX T240 2 DOF Z/W = 0.168 [V]
ETMX T240 3 DOF X/U = 0.153 [V]
ETMX T240 3 DOF Y/V = 0.008 [V]
ETMX T240 3 DOF Z/W = 0.113 [V]
ETMY T240 1 DOF X/U = 0.066 [V]
ETMY T240 1 DOF Y/V = 0.006 [V]
ETMY T240 1 DOF Z/W = 0.046 [V]
ETMY T240 2 DOF X/U = -0.126 [V]
ETMY T240 2 DOF Y/V = 0.059 [V]
ETMY T240 2 DOF Z/W = 0.148 [V]
ETMY T240 3 DOF X/U = 0.045 [V]
ETMY T240 3 DOF Y/V = 0.038 [V]
ETMY T240 3 DOF Z/W = 0.152 [V]
ITMX T240 1 DOF Y/V = -0.16 [V]
ITMX T240 2 DOF X/U = -0.227 [V]
ITMX T240 2 DOF Z/W = 0.219 [V]
ITMX T240 3 DOF Y/V = 0.18 [V]
ITMY T240 2 DOF X/U = 0.219 [V]
BS T240 1 DOF X/U = 0.207 [V]
BS T240 2 DOF Y/V = 0.182 [V]
BS T240 3 DOF X/U = 0.072 [V]
BS T240 3 DOF Y/V = 0.241 [V]

Feb. 3 2016 16:38 UTC Reconnected conlog-test-master to the same 99,560 channels are h1conlog1-master.

Added 350 ml of water to the diode chiller, as I noticed the red LED was on with the error
message about low water level.

4f H4 looks clean except for a small wipe mark near 1 o'clock close to the
retaining ring.

4f H1 has streaks visible with green light.  Wipe spots between 3 and 6
o'clock.  Possible spot/damage mark in centre of optic.  Hard to see.
Try cleanroom cotton tip to wipe pump light side.  Drag wipe removed
centre smudge.

4f H2 has a streak mark around 6 o'clock near the edge.  Also has a
hard to spot streak lined up with 12 o'clock and is ~3 mm wide.  Not
visible with white light, only seen with green light.

4f H3 has a spot around 7 o'clock near the edge.  Does not blow off.
Spot is ~2-3 mm from the edge.  Possibly on the pump light side of
the optic.  Hard to get to with the quartz rotator in the way.

Re-examined 4f H4 with green light.  Smudge in middle visible.
Vague spot visible under green light from the pump light side.
Spots visible from the pump light side, not visible from the H3 side.
Drag wiped surface, spot is now gone.

Quartz rotator surfaces look good under white and green light.

Spot on resonator side of output coupler, a little more than half
way from the centre to the edge, around 2 o'clock.  Drag wiped
clean.

Perhaps out of an abundance of caution it was good that we examined
the surfaces with green light.  Certainly a few wipe marks that were
present and not visible under a bright light source, were just visible
in green.  It might be that the wipe marks are inconsequential but at
this moment, it seemed prudent to deal with them.

Replaced intra-cavity shutter blade with new model.  The shutter
blades shipped from Livingston do not fit the external shutter as
there is a handedness problem.  EXTERNAL SHUTTER STILL
NEEDS UPGRADING.

Front end laser beam centered through MM2 iris, slightly off
to the left of centre as you look at the MM1 iris.  It is not clear
whether or not the beam was centred in the first place.

12:46 (PT) Turned on front end laser power watchdog.

Original mode matching lens positions:
L02 = 13.38, L03 = 6.42
L02 = 14.26, L03 = 6.35

PMC we have an offset somewhere as it does not lock to the
maximum transmission level unless the power on the locking
photodiode is turned down below the nominal 1.5V unlocked.
Upon some navel gazing, the offset might be due to some light
in the wrong polarisation falling on the photodiode.

ISS - adjusted waveplate until PDA DC = -10.0V and 
PDB DC = -10.16V.  Zeroed ISS QPD; new readings are 
dX = 0.0005 mm, dY = 0.0013 mm.





Jason, Peter

Summary:  Fairly straightforward recovery from maintenance day activities, which didn't end until after 4pm PST.  Several locklosses due to commissioning effort. 

Activity log:

0:04 Kyle back from MY

0:30 PSL crew done

0:39 Fil done

1:07 Jeff K to turn on EY ESD driver

3:37 cleared H1SUSETMY tim error

There seem to be two new rf oddities that appeared after maintenance today:

• AS90 seems to jump back and forth between two different offsets, maybe about once every hour or so.
• POP90 and AS90 both show irregular low-frequency motion, similar to what we see when an in-loop OSEM (or its sensing chain) goes bad. Ease of locking doesn't really seem to be affected, unlike the previous experience with bad OSEM electronics.

Jeff Kissel graciously made 4 StripTool templates for OPS use when having issues with WFS running away during green locking, as happened today.  These templates are:

ALSX_GreenWFS_Pitch_Metrics.stp
ALSX_GreenWFS_Yaw_Metrics.stp   
ALSY_GreenWFS_Pitch_Metrics.stp 
ALSY_GreenWFS_Yaw_Metrics.stp

and can be found in the usual place for OPS templates: /ligo/home/ops/Templates/StripTool.

These will likely be used with the assistance of a commissioner since I didn't catch all the intricacies of manipulating the WFS enough to explain it here, but they are there to save some time when needed.

I have reset all WD saturation counters for the platforms with warning. 

Also, I reset the HAM6 watchdog counter, which is not found on the OPS_HEPI_L4C_WD_SAT_CUSTOM.adl screen.  However, I was notified that HAM6 watchdogs were beyond 75% full via DIAG_MAIN.  Perhaps we should add HAM6 to this MEDM screen?  Or maybe not, since this seems to have been an ACT saturation, not an L4C??

See attached pics for details of what was reset.

[Jenne, JeffK, EvanH, Travis]

On our very first lock attempt (that made it past DRMI) after today's maintenence, we lost lock during the BS coil driver switching state.  Thanks to today's data saving work (see alog 25329), we now have some data to look at!

Attached are 2 figures of the same lockloss, one of which shows the whole time we were in the COIL_DRIVERS state, and the other zoomed in on the lockloss itself. On the top row of these figures, the left 3 plots are just power buildups, to indicate when the lock was actually lost.  The right-most plot is the ISC guardian state - state 505 is COIL_DRIVERS.  The bottom row of plots are the new FASTIMONs for each OSEM of the BS M2 stage.

These channels are plotted in units of ADC counts, but we have 40V/2^16 counts over a 40 ohm resistance, and the BS M2 actuation strength is about 1N/A.  The features in the LL channel are of order 100 counts, which corresponds to about 15 microNewtons.  For longitudinal, this is of order 60 nm of a kick to the BS.  The rms for MICH control above 10Hz is only 1e-14 m, so this is 6 orders of magnitude above the rms.  For pitch and yaw, this corresponds to about a 2 urad kick to the BS.  (Newtons to meters or radians from T1200404).

This seems like plenty to explain our locklosses. Next up: what to do about it?

When you have an xml file made by older diaggui, opening that file using the latest diaggui will cause some problem.

If you do that right after launching the new duaggui, the problem is most obvious because hitting the "Start" button will raise an error message: "No measurement channel defined: Unable to setup test channels."

You need to click and reselect each and every measurement channel. It seems as if these channels are already "selected", but select manually anyway. Hit "start" and this time the measurement starts.

OTOH, once you make any measurements using the new diaggui and open an old file later, hitting "start" will not cause an error, but sometimes not all channels are measured (but sometimes all channels are measured, not sure about the condition).

FRS ticket 4333 was filed.

J. Kissel

I'd found it frustrating that the ALS control system overview screens were not linked on the overall ALS overview screen, so I've added links. See attached screenshot.

Changes have been committed to the userapps repo, 
/opt/rtcds/userapps/release/als/common/medm/ALS_CUST_MAIN.adl

ACTIVITY LOG:

15:15 UTC Chris S. headed down X arm for beam tube enclosure sealing 3 doors from end X
15:24 UTC Peter transitioning LVEA to laser safe
15:34 UTC Peter done transitioning LVEA to laser safe
15:35 UTC Peter to H1 PSL to start HPO characterization
16:10 UTC Dale opening OSB receiving rollup door
16:11 UTC Hugh restarting guardian on HAM6 ISI
16:18 UTC Joe D. to LVEA to check batteries, eye wash stations, etc.
16:21 UTC Hugh done guardian update on HAM4 and HAM5, moving to HAM3
16:27 UTC Jeff B. to LVEA to get data from desiccant cabinets and work in the area between the changing room and LVEA
16:30 UTC Filiberto and Richard to LVEA to pull TCS EtherCAT cables from beer garden to mezzanine
16:32 UTC Betsy starting charge measurements
16:46 UTC Jason to H1 PSL to work with Peter
17:01 UTC Received SNEWS alarm as GRB in Verbal Alarms. No indication in GraceDB that it was a test. Arrived at time scheduled for test.
17:03 UTC Cheryl misaligning MC1 to check for light on photodiodes
17:04 UTC Jeff B. done
17:08 UTC Bubba to LVEA to work on crane shimming
17:15 UTC Joe D. done for now
17:17 UTC Hugh tripping HAM5 ISI for guardian update test
17:30 UTC LN2 delivery to mid Y
17:40 UTC Betsy done charge measurements
17:47 UTC Richard removing safety terminals from MSR Beckhoff chassis
17:53 UTC Filiberto done pulling TCS EtherCAT cables by beer garden, moving over to HAM6, Richard helping
18:05 UTC Hugh tripping ITMX for guardian update test
18:14 UTC Hugh done guardian update testing
18:14 UTC Karen and Christina to end stations to clean
18:22 UTC Kyle going to Y2-8.
18:25 UTC Hugh and Jeff B. to mid X, end X, end Y. 3IF0 inventory at mid X. HEPI maintenance at end X and end Y.
18:28 UTC Richard and Filiberto done in LVEA. Filiberto starting modification of Beckhoff Corner Chassis 4.
18:32 UTC Paradise water delivery
18:33 UTC Filiberto powering down Corner Chassis 4, removing chassis, adding terminals
18:47 UTC Corner Chassis 4 down
18:51 UTC Joe D. back to LVEA
18:57 UTC LN2 delivery to gate, Kyle directing driver to CP6
19:11 UTC Evan to CER
19:14 UTC I untripped MC2, noted that nothing was going to the DAC, was in safe mode, Cheryl put it to aligned
19:14 UTC Cheryl moving IMs
19:23 UTC Evan measuring voltage out of ITMY PUM coil driver
SUSAUX123 model restarted
19:29 UTC ASC model restarted
19:31 UTC Hugh back from end/mid stations, going to mechanical room
19:31 UTC Kyle to end X to pickup part
19:34 UTC SUS ITMX RMS UL WD tripped from Evan disconnecting coil driver
19:42 UTC Jim W. recompiling end X BSC ISI model (WP 5717)
19:49 UTC Jim W. taking ETMX to damped
19:51 UTC Coca Cola delivery through gate
19:54 UTC Kyle back to CS for lunch
19:58 UTC SUSAUX ETMX/Y models restarted
20:05 UTC Richard to roof to look at GPS antennas
20:12 UTC Richard back from roof
20:23 UTC TJ reloading ISC lock guardian
20:31 UTC DAQ restart
20:54 UTC Richard removing safety terminals from MSR Beckhoff chassis
20:58 UTC Bubba to LVEA to move cleanroom, continue working on crane shimming
21:01 UTC Richard done removing safety terminals
21:02 UTC ETMX working, Jim W. taking measurements
21:09 UTC Jason and Peter breaking for lunch
21:17 UTC Dave restarting ISS model
21:20 UTC Jim W. taking down all BSC ISIs except ETMX, preparing for model restart (ETMX already done)
21:35 UTC Dave restarting all BSC ISI models except ETMX
21:45 UTC DAQ restart
21:53 UTC Filiberto replacing Corner Chassis 4
21:56 UTC LSC filter module changes applied
22:05 UTC Filiberto done. Richard and Filiberto to end Y to look at chassis
22:12 UTC Jason to H1 PSL. Peter already there.
22:23 UTC Jenne taking graduate students from Australia to measure electronics by HAM6
22:34 UTC Kyle to LVEA
TJ leading tour in CR
22:46 UTC Jenne done
23:19 UTC Filiberto to LVEA to run RF cabling for ASC triplexor
23:26 UTC Dave and Jim B. running timing cable for conlog-test-master
23:30 UTC Kyle to CP3 overfill
23:31 UTC Bubba and John done crane shimming
23:55 UTC Evan redoing measurement from this morning

Today I set up the LASER_UP state which monitors the system once the locking is done.  The power output and PZT voltage output are monitored and if they exceed allowed values guardian goes back to the FIND_LOCK_POINT state to try to find a new locking point.

I also added another assert class that monitors the chiller temperature setpoint throughout the locking process including the final LASER_UP state, so that the temperature set point doesn't run away to a value that can cause the chiller to trip off.  When a chiller setpoint that is outside of the allowed range is detected it goes back to the DOWN state, resets the chiller setpoint and then starts moving back up through to LASER_UP.

Guardian has now also been set up for the X-arm laser, tested, and is now working.

Dave has taken a safe snap of the system in the DOWN guardian state to record new gain settings and the filter settings for when the servos are off.

Dave, Cao, Evan

We wanted to check briefly how the electronics noise of the PUM coil drivers compares to the excess noise in DARM.

With an SR785, we measured the voltage noise spectra out of the IX and IY coil driver chassises (going to the satellite boxes), and below 80 Hz we found them all to be below to the noise floor of the SR785 (40 nV/rtHz at 10 Hz, 10 nV/rtHz at 100 Hz). On the other hand, in order to explain a 1/f⁴ DARM noise of 1×10⁻¹⁹ m/rtHz at 30 Hz, this would require a white voltage noise at the coil output of 190 nV/rtHz for a single coil, or 50 nV/rtHz for 16 coils with uncorrelated noise.

If we want a good measurement (not just an upper limit) of this coil driver noise, we should use a FET-buffered preamp for reading out the signal.

Today, Kissel and I worked through completing the following (taken from ECR E1600033) for the SUSAUX QUAD and BS models.  This meant recompiling and restarting h1susauxb123, h1susauxex, and h1susauxey with CDS and building new medms screens.

1) Remove SUS NOISE and VOLT MONs from all UPPER stages of SUSes, and non-globally controlled LOWEST stages, and replace with FAST_I_MONs with same data rate.

2) Remove SUS NOISE and VOLT MONs from frames of 10 SUSes under global control and replace with FAST_I MONs (or Fast LV ESD MONs where applicable) with increased data rate of 16k.

3) We will add associated filter banks for every FAST_I_MON.

Data rate calculations show that there will be a zero sum gain to the Science frames by performing the above (see supporting spreadsheet on DCC page).

New FASTIMON screens are shown below.  All model and medm changes have been committed to the SVN.