I've updated the OS on some of the PSL workstations to the latest CDS image - pslws0 and pslws3.  I tried to do pslws1,2 as well, but when I restarted them as a test, they decided to shutdown instead.  So they need to be booted the next time someone is in the PSL enclosure, then I can try again for those two.

J. Warner, K. Venkateswara

Using Jeff K.'s model modifications, we were able to incorporate BRS tilt-subtraction to the GND_STS which was then output to STS_C channel (which was empty previously). This was then used for sensor correction by changing the cartesian conversion matrix. The tilt subtraction filter uses a simple acceleration to velocity converter, a gain matching and a high-pass filter.

Rich M. wrote for us a neat IIR filter to try out for the sensor correction filter bank. After the first attempt doubled the ground signal, we used this with a gain of -1.0 which worked well :)

We wanted to try out this sensor correction yesterday, but there was a lot of activity at ETMX which was disturbing the BRS as shown in the attached .png file. The good news is that immediately after the activity ceased, the BRS output settled down so the damper continues to work as expected.

This morning we had some time to try it out before EX activity resumed. The file NoSensCorr45mHzblnd.pdf shows the current ISI stage 1 performance with the 45 mHz blend filter. As I've mentioned before, notice the nice coherence with the GND_STS_X and ST1 T240_X between 0.1 to 0.6 Hz. The Y-axis is in counts (velocity).

For the uninitiated, sensor correction adds the ground sensor signal to the position sensor, thus it is effective only below the onboard inertial sensor blend frequency. In this case, since we wanted to do sensor correction in the 0.1-0.5 Hz band, we shifted the inertial sensor blend to 250 mHz. The two files NoSensCorr250mHzblnd.pdf and SensCorrOn250mHzblnd.pdf shows the Stage 1 motion without and with sensor correction respectively. Even with sensor correction on, this configuration seems to be a factor 2-5 worse in the 0.1 to 0.5 Hz band, but it is very interesting that the coherence with GND_STS_X is much smaller. And there is significant coherence with ST1_T240_Z at the microseismic peak. This might be related to what I mentioned before in 14426.

But to our surprise we were injecting noise below 0.1 Hz. I then rechecked our tilt-subtraction filter and it turns out we had one filter gain wrong. I've corrected it and I verified that the tilt-subtracted super-sensor was indeed smaller than the ordinary ground sensor. Unfortunately, EX activity resumed just then and we couldn't verify that the sensor correction was lowering the noise below 0.1 Hz. The ISIs were restored to the 45 mHz blends for commissioning activity.

Summary: Our first attempt at trying sensor correction with the ground 'super-sensor' was not terrible! :) We will do a more refined attempt tomorrow. We will also try doing sensor correction using HEPI which may give slightly different results.

re my 14425 aLOG Monday, this morning I indeed found the STS2 B misoriented; this is the unit in the beer garden.  Just as I suspected given the individual HEPI sensors' coherence with the X & Y signals, the X axis of the STS2 was ~-45degrees from our desired X axis.  I say ~ because we don't have a mess of X Y grid lines all over the floor.

I also found the level of the STS2 to be quite poor--the bubble was railed.  This might have been leveled upon installation, not sure when that was, but maybe the heavy instruments (55lbs) slowly differentially sinks into the vinyl floor.  Maybe the floor should be accessed to put the feet directly onto the concrete.  At least, I should look at it again in a week or something to check for tilting.

So I rotated the STS2 to align its X alignment point to be parallel with the X arm and then leveled the bubble.

I 'autoz'd the machine now several times but some axes still have relatively large values.  It may be suffering now from some thermal drift as the igloo must be removed to do the level and alignment.  We may need to rezero daily for a few or even several days.

Attached is a repeat of the measurement I posted log 14425 and as expected, now the X & Y conputed signals are strangly coherent with the STS2 X & Y outputs.  And, I think it makes sense, the 4 local HEPI sensors all have about the same marginal coherence to the ground sensor signals.

Now back where I started Monday, looking at the coherence between the ground STS2 and the HEPI L4Cs.  It is very strong between 0.15 and 4hz.  It falls pretty rapidly starting about 0.15hz and above 4hz.

model restarts logged for Tue 14/Oct/2014
2014_10_14 09:29 h1isietmx
2014_10_14 09:35 h1broadcast0
2014_10_14 09:35 h1dc0
2014_10_14 09:35 h1fw0
2014_10_14 09:35 h1fw1
2014_10_14 09:35 h1nds0
2014_10_14 09:35 h1nds1
2014_10_14 09:42 h1calex
2014_10_14 09:53 h1pemex
2014_10_14 09:54 h1calex
2014_10_14 09:58 h1pemey
2014_10_14 10:01 h1caley
2014_10_14 10:01 h1pemey
2014_10_14 10:03 h1broadcast0
2014_10_14 10:03 h1dc0
2014_10_14 10:03 h1fw0
2014_10_14 10:03 h1fw1
2014_10_14 10:03 h1nds0
2014_10_14 10:03 h1nds1
2014_10_14 11:49 h1fw0
2014_10_14 11:49 h1nds0
2014_10_14 11:54 h1calex
2014_10_14 11:54 h1pemex
2014_10_14 12:05 h1caley
2014_10_14 12:06 h1pemey
2014_10_14 12:31 h1fw1
2014_10_14 12:32 h1nds1
2014_10_14 12:35 h1broadcast0
2014_10_14 12:35 h1dc0
2014_10_14 12:35 h1fw0
2014_10_14 12:35 h1fw1
2014_10_14 12:35 h1nds0
2014_10_14 12:35 h1nds1

no unexpected restarts. Maintenance day. ISI ETMX, PCAL and DAQ work. Some DAQ restarts to support model work.

model restarts logged for Mon 13/Oct/2014
2014_10_13 02:52 h1fw1
2014_10_13 11:12 h1iopsush56
2014_10_13 11:12 h1susomc
2014_10_13 11:12 h1sussr3
2014_10_13 11:12 h1sussrm

unexpected restart of fw1. Power cycle of h1sush56 for 70Hz noise hunting.

Seismic: Would like to do a Guardian restart. Continuing seismic commissioning
Commissioning: Stand down in morning during Laser safe in LVEA during cleanup 
TCS: Packing up 3IFO parts
PCal: Wiring at End-X 
3IFO: Inventory work at both Mid-Stations
All: General post installation cleanup in LVEA 

For the records, and in order for us to define new threshold values, I am posting here the pressure fluctuations for all the BSC-ISI pods (L4C, GS13 and T240), for all units on both sites (I will link this to the LLO log).

The first table attached shows the variations of pressure and the average leak rates for LHO. The L4C varies more than the GS13. The T240 pressure readout is pretty much the same than six months ago.

In this sample of data, we observe larger fluctuations at LLO than LHO, in all pods. The variations are however very similar within all the pods of a given chamber. So it is likely temperature related.

The last table compares the average variations and apparent leak rate for both sites.

After ISCTEY rearrangement I looked at the WFS sensing, but it didn't behave well. Disappointing.

The difference between before and now, apart from the table rearrangement that shouldn't have caused much impact on the sensing, is the ITMY beam position. Maybe the WFS signal is dependent on the beam position?

Tomorrow I'll try to find a good set of centering offsets for the current beam location, as the alignment now is supposed to be good.

To get more range out of MCL PZTs, I swapped the position of fixed and PZT mirrors. See D1400241.

This should have increased the centering range of WFSA by a factor of 3.7, and WFSB by a factor of 9.4. Even though WFSB centering is heavily coupled to WFSA, there seems to be no problem.

I have written a new H1 commissioning reservation system. The user guide can be found at:

https://lhocds.ligo-wa.caltech.edu/wiki/H1CommissioningReservationSystem

Please email me any comments, problems, improvements.

ISI ETMX (Krishna, Jim W and Dave)

restart of h1isietmx and an associated DAQ restart

PCAL (Rick, Shivaraj, Dave)

modified h1calex.mdl and h1caley.mdl models to use one more ADC and DAC channel. This will permit simultaneous double duotone loop back timing measurements. This required new h1pemex and h1pemey models to relinquish DAC channels. These models were restarted several times, with associated DAQ restarts.

DAQ solaris memory upgrades (Cyrus, Jim)

The DAQ solaris QFS writer machines had additional memory installed to see if this fixes the frame writer restart problem.

DNS configuration (Cyrus)

All dns clients were confirmed to be using the new dns server. The old service on cdsfs0 was then turned off.

Observation bit already set to 'Commissioning'.

08:18 Ed to end X to remove whitening chassis for repair (WP 4897).
08:43 Aaron and Filiberto to end X to pull PCAL cables (WP 4896).
08:55 Betsy to LVEA West bay to work on 3IFO.
09:10 Jim W. driving ITMX ISI and HEPI.
09:12 Cyrus auditing DNS settings on CDS machines.
09:29 Ed back from end X.
09:30 Karen cleaning at mid Y, end Y.
09:40 Keita to end Y to align optics on ISCT1.
10:08 Chris cleaning at end X.
10:15 Keita back from end Y.
11:00 Ed to end X to return repaired whitening chassis.
11:17 Jim B. shutting down fw0. Cyrus installing memory in h1ldasgw0.
11:39 Karen done cleaning at mid Y, end Y.
11:42 Ed back from end X.
11:51 Dave restarting PEM and CAL models at end X.
11:53 Jim B. shutting down fw1. Cyrus installing memory in h1ldasgw1.
11:51 Dave making changes to end Y PCAL model.
13:02 Jim W. and Sudarshan to end X to check on status of activity.
13:06 Travis to LVEA. Turn off HAM5/6 and HAM2/3 cleanrooms. Work on 3IFO SUS quad build.
13:29 Jim W. and Sudarshan back.

Jim W., Sudarshan working on adding BRS signal to end X ISI model (WP 4895).
Rick, Dave, Shivaraj working on changes to PCAL model (WP 4894).

I've written a Matlab script to automate the blend switching of the BSC ISI's to the LLO configuration. It's called BSC_Blend_Switcher, and I've saved it locally to the Seismic common folder. To run, you will need to have the SEI path loaded (this can be done in matlab from the shortcuts on the contols account). The syntax at the matlab command line is:

BSC_Blend_Switcher('ITMX')

where, 'ITMX' can be replaced with any of the BSC optics, in whatever case you like. I haven't tested it yet, but the bits and pieces I tried worked. I'll test it tomorrow morning.

I only mean for it to be a temporary work around, as it will probably take a couple minutes to run, and it isn't very smart, just a bunch of ezca calls. Hopefully, Guardian or something smarter will replace it, sooner rather than later.

I have audited the DNS configuration on all of the machines in CDS to ensure that they use the current redundant pair of servers (ns0,1).  As a result, I have now also decommissioned the BIND config that was on cdsfs0 as it is no longer needed, and removed the associated BIND packages.

Added: 697
Removed: 98

No unmonitored channels.

Reset HAM3 and BS.