ALS build against RCG2.9.2 [WP5183]

Jeff, Jim:

h1alse[x,y] models were built against RCG Tag2.9.2 and restarted. No DAQ restart was required. RCG version number on the GDS_TP screens is 4002 for this build.

DAQ reconfiguration [WP5184]

Jeff, Jim, Dave:

The DAQ was restarted at the following local times: 07:24, 07:25, 09:58, 11:39

The first two restarts were to apply the new INI files if they had been updated (they had not). The first raised DAQ errors on certain front ends, the second was to see if they could be cleared.

The third was to apply the new H1BROADCAST.ini and H1EDCU_HWS.ini files. Again certain front ends needed their mx-streams restarted.

It was then found that dataviewer would not show any fast channels in the signal selection list, and the slow channels were not quite correct. Jim tracked this down to a badly formed line in my updated H1EDCU_HWS.ini file. I have forgotten to put a close-square-bracket at the end of one channel. This was corrected and the fourth DAQ restart applied the fix (this time no frontends were DAQ glitched).

Take home message, always run inicheck on new ini files.

Guardian Reboots:

Jamie, Betsy, Jeff, Dave:

we rebooted the h1guardian0 machine twice this morning. First was to see what the load averages start with after a reboot (answer, 7 after 1 hour running). The second was to apply Jamies newer version of guardian.

prior version (guardian, ezca) = 1390,443

new version = 1445:474

On Saturday, I was able to get some data on the effect of different blend filters on DARM.  It looks like we probably don't want to be using the 45mhz blends, or they need some re-working to reduce their low frequency performance. The attached plots are DARM  from 2 lock stretches on Saturday. This is the CAL CS DELTAL spectra, which Jeff helped  me calibrate, hopefully he'll explain in a comment. Blue traces are both end stations with 45mhz blends, orange traces are both end stations with 90 mhz blends, black is the ground. Ground was pretty similar between the 2 cases, range was similar, though slightly higher with the 90mhz blend, possibly better alignment? First plot is .01 hz to 3 hz, where most of the action is, the second plot is 1hz to 100hz.

The first plot  shows the 90 mhz blend does as well as the 45mhz blend down to .3 hz, then does a factor of several worse until ~50mhz, where the gain peaking on the 45mhz blend causes more motion.  Above 1 hz the 90mhz blend shows more RMS, I'm not sure of the cause, but there are features visible in the second plot at about 8-15hz that I don't understand. But they are probably not due to the blend change.

J. Kissel, D. Barker, B. Weaver

After the first reboot of the guardian machine this morning, all SEI chambers except HAM3 came up as expected: the SEI manager and ISI / HPI subordinates are coded to be smart enough to figure out what state the platforms are actually in and restore to that state upon initialization. HAM3's ISI subordinate did not. I was able to identify it because the HAM3 SEI manager was complaining that it's subordinate's request had changed. The solution was to simply by-hand change the request to HIGH_ISOLATED.

No big problem here, just want to start recording the outcomes of reboots so we can address any systematic issues. Note this did *not* happen on the second guardian machine reboot today.

Jason, Kiwamu,

We revisted the calibration of the oplev on ETMX and ETMY which showed calibration error of a factor of a few (alog 18218). In fact, they alll had underestimated the suspension angle by roughtly a factor of two. Here is a summary table of the calibration factors:

We also updated the SDF so that these new values are already reflected. Note that the number I updated yesterday was not accurate enough (alog 18218) since I was using the misaligned ETMX. We calibrated it again with the aligned suspension. I attach the measurement data nad fitting codes as a zip file.

Replaced QPD Whitening Filter Chassis S1101595 with S1101628. Keita reported 900 count DC offset on segment 2. 

Similar to yesterday's plot but I've added MICH SRCL & PRCL

See the attached three panel for all the three building Pressures coherence to trhe IFO control signals.

Corner Station had coherence approaching 0.7 with Mich at ~20mHz, everything else is less.

WP #5164

Replaced dataviewer and command line nds tools to remove warning message about communication protocol version being unexpected.

WP #5170

Update control room GDS tools to version 2.16.17.2-1, includes awgstream (compiled against new gds libraries, no code change).

This change fixes printing to files in diaggui and foton, gives the user the ability to set very small numbers in awggui, fixes a minor bug in allowed sample rates in foton. 

For the more obscure changes, foton can be used for non-aLIGO filter development involving non-standard sample rates (using a command line option).  In diag and diaggui, multiple broadcast addresses can now be specified as a comma-separated list in the LIGO_RT_BCAST environment variable.  Also in awggui, awgstream, diag and diaggui, setting testpoints can be restricted to specific models.

Comparison between the control channels used for the signal recycling cavity (SRC) alignment, H1 and L1:

Both IFOs use a AS port, 36 MHz WFS to control SRM alignment, though H1 uses WFS B and L1 uses WFS A. I don't know if this difference is arbitraty or reflects some real difference in sensing. Both IFOs use the AS port QPD, AS_C, to control the alignment of SR2, though H1 also feeds this signal to the SRM, to decouple the action of this loop (SRC2) from the SRC1 loop.

The other thing to notice is that the DoF (degree-of-freedom) naming between the H1 and L1 is swapped. This is just unfortunate and should be fixed.

J. Kissel

I had trouble compiling the 
/opt/rtcds/userapps/release/hpi/h1/models/h1hpibs.mdl
in that where all other HEPI top-level models had no problem, the BS wouldn't compile when the actuator output signals were connected to the DAC via a bus & tag system. I tried grabbing new busses and tags and reconnecting, I tried grabbing a new cop of the hepitemplate library part, neither of which worked. It would only compile if I directly connected the library outputs to DAC.

I'll ask the CDS crew to investigate.

J. Kissel

Plan for the morning:
- Recompile, reinstall, and restart BSC HPI models to absorb changes that were a residual from the HAM model updates
- Install ALS EX and EY models, which have been compiled against the tagged release of RCG 2.9.2 (it had only been compiled against the branch to date)
- Restart the frame builder / DAQ / h1cd0 to absorb new TCS Beckhoff channels and the updated channel list from the new BSC HEPI template.

Bringing all IFO guardians to DOWN and IMC guardian to OFFLINE, and bringing BSC Chambers to OFFLINE.

Summary of the PSL trips from 2015-5-1 to 2015-5-3 during the LHO mini run.  Every instance of the PSL tripping was due to the same interlock, H1:PSL-IL_DCHILFLOW, tripping with no apparent loss in coolant flow for the diode chiller, H1:PSL-OSC_DCHILFLOW.  The first three trips on 2015-5-3 were during the long interlock trip that Nutsinee reported in alog 18187.  Data for the other PSL trips over the last 10 days have been reported in alogs 18083 and 18134.  All times UTC.