Fire department called at 10:58a PDT, asking to check out a box at the South Mid-Station, so I said "sure, no problem." After speaking with Robert, he suggests that when they get a glitch in their alarm system, they have to send someone out to confirm its not a fire, which we suspect is the case -- no fire (confirmed by corner station camera), glitch in the system, routine check. Will post if we hear anything further/otherwise.

model restarts logged for Fri 18/Apr/2014
2014_04_18 10:21 h1susetmx
2014_04_18 10:43 h1susitmx
2014_04_18 10:43 h1susitmy
2014_04_18 10:49 h1broadcast0
2014_04_18 10:49 h1dc0
2014_04_18 10:49 h1fw0
2014_04_18 10:49 h1fw1
2014_04_18 10:49 h1nds0
2014_04_18 10:49 h1nds1
2014_04_18 13:25 h1susetmy
2014_04_18 14:21 h1suspr3
2014_04_18 14:21 h1sussr3
2014_04_18 14:37 h1susbs
2014_04_18 14:44 h1dc0
2014_04_18 14:44 h1nds0
2014_04_18 14:46 h1broadcast0
2014_04_18 14:46 h1fw0
2014_04_18 14:46 h1fw1
2014_04_18 14:46 h1nds1

no unexpected restarts.

(Sheila, Alexa)

When I was at EY taking the noise measurements, I noticed that the fiber polarization (in the wrong pol) was up to about 60%. I asked Sheila to readjust the controller box for me. Now it's back down to 18%, and the controller is off. We should keep an eye on this drift...

(Alexa posting as Sheila)

J. Kissel

In order to get started on the suspension software ECRs with top priority, I needed to first clean up the library parts and MEDM screen from the prototype optical lever damping. I've completed the needed changes as described in ECR E1400207. All changes have been installed in the front-end code, the affected models have been restarted and restored, MEDM screens have been modified, and all committed to the userapps repo. Details of the changes are spelled out below. I have *not* captured any new safe.snaps, as folks have begun to lock the Y-ARM. 

Over the weekend I'll begin making the high-priority changes, starting with removing redundant watchdog components to reduce the false alarm rate as per E1400102. 

Stuart -- you should wait to begin re-merging the LLO models with the library parts until I've completed the majority of the changes.

Details
-------------------
I've done the following to the following SUS types:
QUAD:
- Cleaned up ${userapps}/release/sus/common/models/FOUROSEM_STAGE_MASTER_OPLEV.mdl, piping the ODC state bit for the optical levers to the output.  These bits have been inserted in the middle, after the M0 and R0 damp bits, into bit 11 and 12. This means the L1, L2, and L3 LOCK state bits are now 13-15. Notably, the optical lever damping loop drive path goes *through* the DRIVEALIGN matrix, to gather any P2Y, Y2P, or Angle to Longitudinal decoupling that we install -- this is different from how the BSFM optical lever damping was originally installed.
- Added outputs to L1 and L2 optical lever state bits to ODC vector in ${userapps}/release/sus/common/models/QUAD_MASTER.mdl
- Cleaned up ${userapps}/release/sus/common/medm/quad/SUS_CUST_QUAD_OVERVIEW.adl, and added the 2 extra ODC bits in the bitword light representation in the top right corner.
- Added two extra bits to ${userapps}/release/sus/common/medm/quad/SUS_CUST_QUAD_ODC.adl.
I *have not* updated the bit representation channels, I'll that to the ODC team.

HLTS:
- Modified ${userapps}/release/sus/common/models/HLTS_MASTER.mdl to use FOUROSEM_STAGE_MASTER_OPLEV.mdl on the M2 stage, modified the M3 stage to match the optical lever damping topology of the FOUROSEM_STAGE_MASTER_OPLEV.mdl (as usual, the bottom stage of every suspension type is different in some way, so it must remain unique). Both stages now output an optical lever damping bit to the ODC. As with the QUAD, the optical lever damping status bits have been inserted just after the M1 OSEM damping status bits. As such, bits 6 - 8 are M1, M2, and M2 damping, with 9, 10, and 11 being the M1, M2, and M3 LOCK status bits.
- Modified ${userapps}/release/sus/common/medm/hxts/SUS_CUST_HLTS_OVERVIEW.adl to include optical lever damping on M2 and M3, and added two bits to the ODC word lights in the top right.
- Created new screens ${userapps}/release/sus/common/medm/hxts/SUS_CUST_HLTS_[M2/M3]_OLDAMP_ALL.adl which contain the details of the two OLDAMP filter banks, virtually identical to the BSFM and QUAD versions.
- Modified ${userapps}/release/sus/common/medm/hlts/SUS_CUST_HLTS_ODC.adl to include two extra damping bits. As with the QUAD, I *have not* updated the bit representation channels, I'll that to the ODC team.

BSFM:
- Modified ${userapps}/release/sus/common/models/BSFM_MASTER.mdl to route the OLDAMP servo through the DRIVEALIGN matrix. Regrettably, because we will eventually need to install M1 to M2 stage OSEM damping to kill the highest Roll and Vertical modes of the suspension, we cannot just copy in and use FOUROSEM_STAGE_MASTER_OPLEV.mdl. Again, also worth note -- the OLDAMP path is now routed through the DRIVEALIGN matrix. There's currently no filters in the P or Y elements of the matrix, so the loop shape / design is unaffected. (The status bit had already been routed out from the M2 stage up in to the ODC vector).
- Made a few aesthetic changes to ${userapps}/release/sus/common/medm/bsfm/SUS_CUST_BSFM_OVERVIEW.adl such that the OLDAMP path matched the QUAD and HLTS.
- Modified ${userapps}/release/sus/common/medm/bsfm/SUS_CUST_BSFM_ODC.adl to include extra damping bits. As with the QUAD, I *have not* updated the bit representation channels, I'll that to the ODC team.

nm

Once IAS finished, Greg & I installed the ISI Blade Spring's TMDs.  SNs 22 23 24 on Springs 1 2 3 respectively.

We had a couple of earthquakes today, a 7.2 near Tecpan de Galeana, Mexico, a 5.6 near Noatak, Alaska, and a 5.5 at Balleny Islands region.

- 9:06 am, Andres to the CS VEA, retrieve items.--> done by 10:17 am.
- 10:01 am, Hugh to CS VEA, HAM5 area for HEPI work.
- 10:01 am, Kyle to Y-End station, open GV18--> done by 10:20 am.
- 10:25 am, Jeff K. from the CR, new code per WP#4573.
- 10:30 am, Kyle to CS VEA, open GV7 and GV5.
- 10:40 am, Corey to CS cleaning area, retrieve garb.
- 10:45 am, DAQ restart for new code.
- 1:00 pm, Karen to Y-End, cleaning.
- 1:05 pm, David to CS VEA, TCS work.
- 1:30 pm, Hugh to CS VEA, continue with HAM5 work.
- 1:55 pm, Matt H. to CS VEA, TCS work.
- 2:04 pm, Cyrus to X-End, comtrol check/work. -->done by 2:33 pm.
- 2:09 pm, Jeff K. more code.
- 2:20 pm, DAQ restart.
 

I ran into a "snag" with the RGA reconfiguration that I had envisioned and won't be able to pump the volume seen by PT246B until next week -> The pumping effect provided by the gauge isn't enough to match the out gassing and the pressure is rising as well as the rate of rise -> If it starts to "run away" I'll have to shut it off but, ideally, it will stay in its safe operating pressure range until I can pump it early next week.

Soft-cycled GV7 so that others could install viewport protector shutters etc -> Dumped unpumped gate annulus volume into pumped annulus volume, opened GV5 -> Dumped GV18's unpumped gate annulus volume into pump cart and decoupled pump cart from annulus plumbing -> Isolated and shut down Turbo and scroll pumps -> opened GV18

The input matrices for WHAM5 are populated and calibration filters are loaded.  With the Actuators attached, the IPS and even better, the Cartesian Position Biases are valid.  The IPSs were zeroed immediately after the IAS look this morning.  So, the 'aligned' position is zero on this chamber.  Likely once I do range of motion etc tests, the system will de stress and certainly local numbers will change.  Usually though the cartesian values tend to cancel, we'll see.

Recommended controls for the different SEI platforms:

BSC-ISI (All) - Guardian ON
Blend: TBetter on all DOF but RZ
Isolation loops: ISO Lv3
Tilt decoupling: gnd-st1 (Matrix, always ON)

HAM-ISI (HAM2, HAM3) - Guardian ON
Blend: 01_28
Isolation loops: ISO Lv3

HEPI (ETMX, ITMX, BS, ITMY, ETMY, HAM2, HAM3, HAM6*) - Command button
Position loops blend filters: 0 on L4C, 1 on IPS
Isolation: Position Loops (Level 1 in command window)

Note: ground-stage1 sensor correction (SENSCOR) is available on BSC-IY and BSC-EX

Recent Updates:

• Smooth ramp installed for the ISI blend switch
• 122880 saturations (60s worth of samples) allowed on HEPI models
• Blend filters cleaned up, and re-installed
• 5Hz UGF generic position loops were installed on HAM4-HEPI*
• ETMY-ISI controls were brought to performance similar to ETMX-ISI
• Every SEI Safe.snap file was updated

Seismic SVN:

• H1 folders (BSC, HAM) cleaned up, and commited

To do list:

• Investigate ~10Hz peak seen on ETMX
• *HAM4-HEPI position loops keep tripping. Gain and phase margin seem ok. Some investigation to be done here.
• Commission HAM5 HEPI
• Clean up H1 HEPI folder and commit.
• Install ISO Lv2 and LV3 on HAM4-ISI
• SENSCOR: BS, and ETMY need gains tweaked
• Install controls (INF, OUTF, Damp, Blend, 3 levels of ISO) on HAM5 and HAM6

I have started to repeat the same noise measurements we made during HIFOY, in particular for the PLL loop (see alogs 9846 and 9251). So far I have made the following PLL measurements:

EY PLL OLTF: see alog 11180. The UGF is at 23kHz with a phase margin of 52 deg.

Beanote measurement: I measured the beatnote out of the direct monitor (-1dBm) of the pre-amplifier. Using the Agiliant spectrum anylzer, the signal strength was -20dBm at 39.62MHz with 100Hz BW. Notably, the medm screen reads back -5dBm which is after the +13dBm. The PLL BBPD DC readback was 2V with 17.8mW. I adjusted the calibration to 0.055A/W (different from at EX).

AG spectrum analyzer noise floor: I measured the noise floor of the spectrum analyzer to be at -122dBm at 100Hz BW.

BBPD dark noise: With the PD completely blocked, the noise was at -116dBm at 100Hz BW.

Shot noise: With only the fiber light blocked at the PD, the noise was at -108dBm at 100Hz BW.

PLL error signal: With the loop locked, I measured the error signal at the IMON of the PFD (i.e. this is a suppressed error signal). I have attached the data; measurements were taken with both the SR785 (EY_PLL_NoiseSpecV_Raw) and with the AG spectrum anaylzer (BBB2.txt) for high frequencies. I have also attached the concatenated data.

Once again, I've had to restore the mapping of keys on the control room keyboards for the controls account so that the caps lock key works.

PLEASE DON'T CHANGE THE KEYBOARD SETTINGS!  IT CHANGES IT FOR EVERYBODY, NOT JUST YOURS!

JimW, HugoP,

With the recent blend design activities, a lot of filter files (.mat) were created, some were duplicated multiple times in the folder tree, while only a few were actually used. Some filters were also installed in the wrong slot, with the wrong name. For example: Start filters were installed in ITMX's TCrappy, TBetter was installed in ETMX's TCrappy. This can be quite mis-leading for the commissioners and we should avoid it.

We figured out which filter files should be used. We took those and gave them clear names in the common BSC part of the seismice SVN as follow, and removed every duplicate we found in the folder tree:

/ligo/svncommon/SeiSVN/seimic/BSC-ISI/Common/Complementary_Filters_BSC_ISI/aLIGO/

• Start:
  Start_Filters_BSC_ISI_2014_02_25.mat  ->  Start_Blend.mat
• T750mHz:
  uses Start_Blend.mat, generic routine automatically adds the trillium to the blend.
• TCrappy:
  some_blend_crappy_fitlers.mat   ->  TCrappy.mat
• TBetter:
  some_modified_blend_crappy_fitlers_040914.mat  ->  TBetter.mat

The Step_6 unit-specific scripts were modified for each BSC-ISI chamber to prevent accidentaly loading the wrong filter into the wrong slot again.

Every BSC-ISI blend filter was reloaded this morning at 9:35AM, from the agreed generic blends mentioned above.

Work will be commited to this SVN today, to facilitate next week's commissioner hand-off.

Arnaud & Hugh

We quickly looked at this.  We didn't expect an effect but HEPI PS control runs at ~10hz (Epics) and we could check so we did.  The attached looks at the Pier top horizontals over the ground STS2.  All the horizontsl HEPI signals looked the same wrt both horizontals of the STS2s.  First Ref is ISI OFF, HEPI position loop ON, Second Ref is ISI OFF, HEPI Position Loop OFF, current trace is with the fluid flow zeroed.  No affect evident.

I've been looking in to the pier resonance in different chambers over 5 minutes worth of data on 16th/17th of April when the ODC reports good times for a specific chamber. The pier resonance usually appears as an increase in motion (by about an order of magnitude) when you compare the L4Cs at the top of the HEPI piers to the ground STS at ~8 Hz. The first attached image shows this comparison for BS/ITMX/ETMX which all show this pier resonance in the X and Y directions only (this plot is 5 minutes worth of data from the time in the name). If you look at however ETMY (second attached image) things look different. In this image I compared the L4C to the PEM ACC since the GND STS is outputting values close to zero. However the pier resonance seems to be amplified more than other chambers, particularly by this feature at ~11Hz which shows up in X/Y/Z directions. This is causing an extra order of magnitude increase in noise than I would normally expect for the pier amplification at ~11Hz in the X and Y directions. The third plot just shows the BS/ITMY/ETMY aswell. I've looked at several different times of day over both days and the results all look the same. It does not seem to change according to the time of day.

JimW and I worked on getting the performance of BSC-EY comparable to the performance of BSC-EX, before handing off to SUS.

BSC-EY now has the following control tools installed:

• Blend filters: Start, T750mHz, TCrappy, TBetter
• Isolation loops: Lv1, Lv3
• Tilt Decoupling: GND-ST1
• Sensor correction: gains need to be tweaked.

We compared the performance of BSC-EY with the performance of BSC-EX, with both platforms under BSC-EX's most used configuration:

• Blend filters: TBetter
• Isolation loops: Lv3
• Tilt Decoupling: GND-ST1
• Sensor correction:  off
   

Attached Plots show comparable performance of the ISIs, at the projected suspension point, for similar ground motion at both end stations. (plots calibrated in nm and nrad).

One can notice a 10Hz peak, on BSC-EY spectra. We went ahead and took performance spectra at EY with the Isolation off. The peak is also there when the isolation and damping loops are off. Hence, the peak seen at 10Hz is neither caused, nor amplified, by the ISI active controls.

Since SUS provides plenty of isolation at 10Hz, we decided to give them the go ahead to start their testing.

Meanwhile, JimW and I kept investigating. We noticed that HEPI L4Cs were seeing the 10Hz peak too, and that it is mostly seen on the vertical L4Cs (see Page 1 of last attachment). We were able to reduce this peak's amplitude by a factor of ~10 by simply turning HEPI position loops off (see Page 2 of last attachment). It looks like HEPI-EY position loops are somehow amplifying the 10Hz peak, but they are not its source, as the peak still appears clearly with HEPI off.