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:
Seismic SVN:
To do list:
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!
Since the HEPI actuators are already attached (making adjustment difficult) and the yaw tolerance of the SR3 and SRM optics is large and adjusted on the table (unlike the BSC chambers we do not adjust HEPI to align the optics, we push them on the already aligned ISI) we will ask for a waiver on the ISI yaw.
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/
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.
I copied all the temporary blend fiters under:
/ligo/svncommon/SeiSVN/seimic/BSC-ISI/Common/Complementary_Filters_BSC_ISI/aLIGO/Temporary_Versions/
Now the regular blend filter folder only contains the ones to be used:
/ligo/svncommon/SeiSVN/seimic/BSC-ISI/Common/Complementary_Filters_BSC_ISI/aLIGO/
08:50 Corey, Thomas staging viewport covers by LVEA X arm beam manifold Kyle soft closed GV7 08:58 Betsy, Travis getting parts from ITM build area 09:11 David H, Matt H. working on TCSX, TCSY Kyle to open GV5, GV18 09:27 Alexa to end Y to take fiber noise measurements 09:27 Richard done installing lexan viewport cover
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.
For info, "ODC reports good times" when HEPI is position controlled (locked to the ground)
Looking at LLO Not sure if this is related, but I looked at LLO (within the last week) at times when the ISI state vector is green (since the HEPI state vectors are hardly ever green) over 5 minutes and compared the same things as above (L4C to ground STS). BS/ITMX/ETMX (first plot) shows very similar features at both sites - a peak at ~8Hz in the X and Y directions. However when looking at BS/ITMY/ETMY (second plot) the BS/ITMY chambers at both sites look the same with a peak at ~8Hz but ETMY at LLO has a much sharper and more pronounced peak at ~11Hz in the X and Y directions. This doesn't look exactly to same as the ETMY peaks at LHO but I thought it might be interesting!
model restarts logged for Thu 17/Apr/2014
2014_04_17 00:10 h1fw1
2014_04_17 00:14 h1fw1
2014_04_17 00:22 h1fw1
2014_04_17 03:03 h1fw1
2014_04_17 03:12 h1fw1
2014_04_17 03:23 h1fw1
2014_04_17 05:19 h1fw1
2014_04_17 05:25 h1fw1
2014_04_17 07:19 h1fw1
2014_04_17 07:24 h1fw1
2014_04_17 08:12 h1fw1
2014_04_17 08:23 h1fw1
2014_04_17 09:21 h1fw1
2014_04_17 10:05 h1isiham6
2014_04_17 10:07 h1isietmx
2014_04_17 10:27 h1fw1
2014_04_17 10:45 h1isietmy
2014_04_17 10:45 h1isiitmx
2014_04_17 10:47 h1isibs
2014_04_17 10:47 h1isiitmy
2014_04_17 10:49 h1isiham2
2014_04_17 10:49 h1isiham3
2014_04_17 10:49 h1isiham4
2014_04_17 10:49 h1isiham5
2014_04_17 10:51 h1isiham6
2014_04_17 11:09 h1broadcast0
2014_04_17 11:09 h1dc0
2014_04_17 11:09 h1fw0
2014_04_17 11:09 h1fw1
2014_04_17 11:09 h1nds0
2014_04_17 11:09 h1nds1
2014_04_17 12:22 h1fw1
2014_04_17 12:26 h1fw1
2014_04_17 12:55 h1fw1
unexpected restarts in red, daq restart in blue. Looks like the reboot of h1ldasgw1 has cleared the h1fw1 problem.
Yesterday, filters were installed on ETMY which is now in the same configuration as ETMX. This includes top mass length to angle decoupling, and angular plant inversion at all stages to facilitate loop design for wfs and/or oplev.
When driving in pitch through the drivealign matrix with the "invP2P" filter on, the transfer function from the drive to the test mass should give a single pendulum with a resonance at 0.45Hz, and a Q of 3.
When driving in yaw, the transfer function should be similar, but with a resonance at 0.6Hz.
Note : all the gains are set to 1
The length to angle decoupling for pitch and yaw from the top mass has been roughly tested by sending a longitudinal excitation at 0.5Hz and looking at the oplev signal. I didn't quantify it yet, but it seemed to reduce the angular motion when turning the filters on.
The two filters L2P1 and L2Y1 installed at the top mass should be used with a gain of -1
Left to do for EX and EY is length to angle decoupling on UIM and PUM.
Alexa, Sheila
We were able to lock the x arm again today.
First we lowered the bandwidth of the ALS COMM loop. Alexa and I had looked at her model a few days ago and saw that this will give us an improvement at high frequencies. This looks like factor of 2 decrease in the RMS when we plot the noise with the cavity pole removed. (The plot with the cavity pole still in is more relevant for the CARM handoff, but since this was an easy improvement we tried it anyway). The first plot attached shows the noise with the new and old nominal settings. The low frequency noise is not stationary, the new settings haven't really given us an improvement there although it looks that way from the plot. The improvements from 700Hz up are real and repeatable. After making this plot, we saw that the crossover was unstable, or we were ringing up one of the modes of MC2 possibly. We changed the gain settings to -4dB on In1 and 3dB fast gain to move the crossover back down and keep the ugf the same.
We also replaced the beamsplitter that splits the X arm transmission for DIFF and COMM with a high reflector to get more light on the COMM BBPD. While it seems like this might have improved the 1/f noise, we aren't sure that this will be repeatable since this noise is nonstationary.
In the last plot, we added an ND filter, to bring the light level back to what it would have been with the BS in place. The high frequency noise stayed low, so this isn't related to the power, (we don't know why this changed in the first place). The noise from 60-8Hz is back to the level with the BS, suggesting again that this is related to power.
We have locked the arm on a 01 mode for IR at times, and we see that the high frequency noise is larger when we do that.
The dolphin network stopped working on the test stand, ended up powering off all dolphin front-ends, power cycling the dolphin switch, and restarting x1boot. Front ends still wouldn't start until I ran dxadmin on x1boot to see what the problem was. At that point the dolphin system started working and the front-end computers finished booting.
Sheila switched the blends when the trilliums were still rung up.
was this using the new ramp code? that is less glitchy?
Yes, this was using the new ramp code but the trip has nothing to do with the ramping itself. The blends were just switched from Start (no T240) to TCrappy (with T240) while the Trilliums were still saturated, causing the ISI to trip on the actuators as soon as the T240s got into the blend.
Switching the blends after waiting for the Trilliums to quiet down, as recomended, worked perfectly fine.
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:
We compared the performance of BSC-EY with the performance of BSC-EX, with both platforms under BSC-EX's most used configuration:
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.
I previously wrote that the ~10Hz peak was mostly seen on the vertical L4Cs, while it is actually seen on the Horizontal L4Cs.
Safe.snap made just now.