On Tuesday, while most of the IFO was down for various maintenance tasks, I grabbed a bunch of SUS spectra and started a Template directory.
I set all of the references to be the ~quiet, unlocked data from the down period of the IFO. These spectra could be run when trying to troubleshoot locking. On Tuesday, I was only able to collect the following, located in /ligo/home/ops/Templates/SUS_Spectra/
BS_NOISEMON_spectra.xml
BS_OSEMINF_spectra.xml
PR2_NOISEMON_spectra.xml
PR2_OSEMINF_spectra.xml
PRM_NOISEMON_spectra.xml
PRM_OSEMINF_spectra.xm
SR3_NOISEMON_spectra.xml
SR3_OSEMINF_spectra.xml
SR2_NOISEMON_spectra.xml
SR2_OSEMINF_spectra.xml
SRM_NOISEMON_spectra.xml
SRM_OSEMINF_spectra.xml
ITMX_NOISEMON_spectra.xml
ITMX_OSEMINF_spectra.xml
ITMY_NOISEMON_spectra.xml
ITMY_OSEMINF_spectra.xml
NOTE - Many of the lower stage NOISEMON channels look... weird. They should be used as a before/.after snapshot for troubleshooting only. Work to improve what the various strangenesses of these channels is on a few low priority to-do lists.
There are templates ready to collect the balance of the SUS spectra data, namely ETMs, MCs, PR3. We should do this when the IFO is set to DOWN for whatever reason. The spectra are quick to run, then update all references (currently bogus data) and resave.
21:44UTC
This was ok'd by Mike Landry. He's assisting Robert Schofield with PEM work.
FYI, I have suspended reporting of HWInjReport runs until I can fix the bug that is causing the anomalous absence of RAW and RDS injections. Once I have that fixed, I will perform a comprehensive run of HWInjReport starting from September 12, 2015 00:00:00 UTC.
Apologies for not giving notice sooner.
We remain in Science mode locked at 72Mpc. Activities are being filtered through Mike Landry via telephone. Kyle and Gerardo have gone to Mid Y to start vacuum pumps for leak hunting. Wind has increased to ≤25mph. Earthquake graph up to .23microns/s. Terramon reported an R-Wave velocity of .25µm from a 5.1 nea New Zealand and then a 5.2 near Chile. This is most likely the reason for the rise. Microseism is up to about .5microns/s. 2.5 hours - glitch free.
The LHO Advanced Ligo CDS web page (https://lhocds.ligo-wa.caltech.edu) has been modified to include screen shots from selected control room wall displays. Not all displays are included at this time, this is only a preliminary page. The update rate is once per minute. Click on the link "Control Room Screen Shots" to view.
TITLE: Oct 9 DAY Shift 15:00-23:00UTC (08:00-04:00 PDT), all times posted in UTC
STATE Of H1: Observing
OUTGOING OPERATOR: Travis
QUICK SUMMARY:IFO in Observation mode ~75 Mpc. All lights in LVEA, PSL and M/E stations are off. Wind is ≤10mph with occassional highr gusts. EQ sei plot is nominal. Microseism plot is elevated to ~.35microns/s. Cheryl had the first 2 hours of my shift as planned.
O1 days 18-21
model restarts logged for Thu 08/Oct/2015
2015_10_08 09:29 h1nds1
2015_10_08 12:37 h1asc
2015_10_08 12:47 h1broadcast0
2015_10_08 12:47 h1dc0
2015_10_08 12:47 h1nds0
2015_10_08 12:47 h1nds1
2015_10_08 12:47 h1tw0
2015_10_08 12:47 h1tw1
One unexpected restart of nds1. ASC restart for new model code, with associated DAQ restart.
model restarts logged for Wed 07/Oct/2015
No Restarts Reported.
model restarts logged for Tue 06/Oct/2015
No Restarts Reported
model restarts logged for Mon 05/Oct/2015
Many unexpected restarts of h1tw0 due to raid issues. No other restarts. Due to large size, full report in attached file.
HAM4 and HAM5 have had strong glitches for the past several weeks (sorry if I missed this being reported already, I didn't turn it up in a search, we found these by accident). They are sometimes completely not there, but sometimes happening as fast as twice per second! Attached are a slew of plots taken roughly every two days for H1:ISI-HAM4_BLND_GS13RZ_IN1_DQ (but I also see the same in H1:ISI-HAM5_BLND_GS13RZ_IN1_DQ).
We don't have a good lead on these, but wanted to report. They look an awful lot like what we have seen before when the HWS camera was on, see e.g., 18531. I noticed a note in the log on August 25 "15:54 Elli – Going to Hartman table at HAM4", and I also noticed that the glitches started showing up after a long hiaitus around August 27th. However, if I have my sign correct (0=off) for the camera switch channels, then the HWS cameras in the central station are currently off in O1 running.
Assuming it's not HWS, we should probably check ISI actuators for DAC glitches or overflows.
I can confirm that the corner station HWS cameras are all turned off. So 0=off is correct. And If I'm reading the spectrograms correctly the glitch rate seems to change from day to day. HWS camera doesn't do that.
Title: 10/9 Owl Shift 7:00-15:00 UTC (0:00-8:00 PST). All times in UTC.
State of H1: Observing
Shift Summary: Locked for the entire shift in Observing. Wind and seismic calm. Several ETMy saturations, none of which correspond to any RF45 glitching (since there was none that I saw).
Incoming operator: TJ
Activity log: None to speak of. Very quiet night.
Locked in Observing Mode for the duration of the shift so far. A few ETMy saturations, but none of them seemed to coincide with any RF45 glitching, as that has been stable.
TITLE: "10/08 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PDT), all times posted in UTC"
STATE Of H1: Observing at ~80 Mpc for the past 6 hours
SUPPORT: Jenne, Sheila
SHIFT SUMMARY: Few problems when we began to acquire lock. Smooth ride afterward. Wind speed dropped below 10 mph. No big earthquake. Only one ETMY saturation since we acquired lock. RF45 wan't acting up when the verbal alarm went off.
INCOMING OPERATOR: Travis
ACTIVITY LOG:
23:41 LLO delayed observing for another hour. We take sometimes to do some commissioning work.
0:44 Robert to LVEA to turn off stuff. No injection.
00:38 Locked at NOMINAL LOW NOISE
00:55 Cleared off ASCIMC excitation. Switched to Observing.
05:05 GRB Alert
The new rooftop camera is amazing. I can actually see things at night!
We set all quadrant gains of IMC WFSA to [1 1 1 1] from [1, 0.25, 1, 4]. (WFSB was already all 1.)
We also disabled IMCWFS error offsets in servo filters.
After this, we steered IM2 to bring the beam position on IM4 trans back (at first we tried IM3, but it would make the OSEM output to become larger, and they're already close to saturation).
IFO locked after this without any problem.
We haven't done any jitter coupling optimization and I don't know if Robert had time to do it.
The first and the second attachment show the current and the old settings, respectively.
In the first one, yellow boxes show what we changed. Red box show what we changed but are somehow reverted (automatically?).
This is just an observation related to entry 22482 where I was investigating the relation between ISS and IMC.
After Keita and Cheryl set the IMC WFS gains back to 1, it seems to have shifted the pointing to the ISS array a little bit. See the attached trend.
The QPD signals at the ISS array have moved by 0.1 or so both in PIT and YAW when the WFS gain was changed to 1. Both PIT and YAW moved towards the center of the QPD although SUM seems to have decreased at the same time. I am not sure what exactly was going on. We may need to optimize the pico-motors to minimize the jitter-coupling to the ISS array.
Only one ETMY saturation in 4 hours. Wind speed decreasing together with seismic.
TITLE: 10/8 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PDT), all times posted in UTC"
STATE Of H1: Observing at ~79 Mpc.
OUTGOING OPERATOR: Ed
QUICK SUMMARY: Sorry been busy. We spent about 1.5 hours at the begining of this shift trying to acquire lock. Had one lockloss and few other minor issues (ISS 2nd loop freaked out, had to find IR by hand). We locked again at NOMINAL LOW NOISE 00:38 UTC but since LLO wasn't Observing we took some time to do extra comissioning. The ifo state switched to Observing at 00:55 UTC. ~15 mph wind, EQ band seismic activity raised accordningly.
After today's Commissioning Day activities, we had quite a few SDF differences to clear out.
For the ASC, we accepted several things that will be regularly used for the A2L measurements. These are all channels of the ASC-ADS_ sub-subsystem. The things we accepted will have no effect on the interferometer, since during observation we don't use this system at all. We accepted things like the frequencies of the A2L measurements, the ramp times, and the matrix elements. Note that the "CLKGAIN", which is the acutal oscillator amplitude, is still set to zero in SDF, so if any excitation is happening, it'll be flagged in SDF.
I also accepted the new IM2 Pit and Yaw offset values, which were set after Keita and Cheryl did their IMC work today. (Since the IMC pointing moved slightly after their WFS work, they compensated by moving IM2 a bit). Keita and I also accepted several diffs from the ASCIMC model, that were changed as a result of their WFS work today.
Today I was able to remeasure the frequency noise coupling into DARM. I am not finished analyzing the data, but as a preview I am attaching the TF of the IMC VCO to the DCPD sum above 1 kHz. The coupling appears to go like 1/f, or perhaps slightly faster. A 1/f coupling would be consistent with what was found previously (a flat coupling from REFL9I power to DCPD photocurrent).
I was not able to get coherence between my CARM excitation and the IMC VCO below 1 kHz.
Attachment shows TF of demodulated REFL9 volts to DCPD sum (in milliamps). Compared to the previous measurement, the high-frequency portion is a factor of 3 higher. Additionally, we do not clearly see a transition to 1/f2 behavior around 250 Hz, as was seen in the last measurement. One might plausibly claim that the new measurement shows a knee around 100 Hz.
At 50 Hz, this TF predicts a frequency noise coupling that is a factor of 4 or so lower than the previous measurement.
Additionally, during the measurement I noticed that the nonlinear coupling into DARM was quite significant from 40 to 100 Hz; we could see broad wings around the excitation frequency.
The low-voltage electro-static driver (D1500016) includes monitors of the output quadrant drive signals that are sent to ADCs for sampling/monitoring (in a SUS IO chassis). The monitors look at the drive voltage after the normal inputs, test inputs, and parametric instability correction inputs are summed together. Each monitor path has a 1:4 voltage divider to fit the full driver range into the ADC input range.
Looking at these monitor channels for ETMY from a recent lock stretch shows several problems with these monitors as useful readbacks for the electro-static drive signals. In the attached plot, the two traces are:
There are several problems:
Followup work to do: i) check the behavior of the same channels on L1 for comparison; ii) test the behavior of the monitor channels with a spare unit on the bench, in the presence of a signal
It's analog. We need a usable whitening for this. (Daniel, Keita)
The noise floor is not a digital artefact, the analog gain seems to be too small to see anything useful at 100Hz. Even if we move 42Hz LPF up to 1k, we would still need a useful whitening, e.g. two stages of ISC style whitening.
In the first attachment top, red, blue and green are the same ETMY LL ESD low voltage monitor at different points, i.e. red is the test point in SUSAUX (2k), blue is DQ of the same (256), and green is in the IOP model (64k) before the signal comes into SUSAUX.
Also shown is the digital output test point (pink and cyan, pink taken at the same time as red) projected onto the LV monitor by removing the whitening and putting 40Hz LPF and adjusting the DC scaling. No wonder we're not seeing anything useful at 100Hz.
RMS of IOP channel is basically 1 count down to 8Hz or so, and this means that the noise floor is just ADC noise. RMS of this same signal goes only up to 180 or so counts at 1Hz. Changing 42Hz LPF with 1k is not enough for frequency lower than maybe 400Hz or so.
Boosting the analog gain by a factor of 100 or so, the RMS at low frequency would become uncomfortably large.
The second attachment shows what happens when there are two stages of ISC whitening (z=[1;1] p=[10;10]) plus 1kHz LPF instead of 42Hz, without changing DC gain.
The RMS between 1 and 10 Hz becomes 2000 counts-ish, RMS for f>10 becomes 100 counts-ish, and the monitor noise floor would be at least a factor of 10 larger than the noise floor for f<1k.
In the future, when our sensitivity increases by a factor of 3+ or something for f>100Hz and our drive drops by the safe factor, we might have to think about more whitening or more whitening gain. By that time, we might also be able to more aggressively cut down the low frequency part (f<5Hz) of the drive on ESD. According to Evan ESD-PUM crossover is about 20Hz (alog 19859) so it sounds doable.
[update 0:40 UTC] The third attachment shows the DQ channel (red), test point (blue) and IOP channel (green, which is almost completely masked by blue) measured at the same time up to 116Hz. They're the same except decimation filters.
While we were unlocked due to wind during my Sunday Owl shift, I managed to get through taking, updating, and resaving templates for:
ETMX_NOISEMON_spectra.xml
ETMX_OSEMINF_spectra.xml
ETMY_NOISEMON_spectra.xml
ETMY_OSEMINF_spectra.xml
PR3_NOISEMON_spectra.xml
PR3_OSEMINF_spectra.xml