In order to reduce the number of saturating pixels, I changed the exposure time of the following digital cameras:
In particular, the OMC camera may be confusing when one checks whether OMC is on a correct resonance or not. Since I am currently not trying to get some useful quantities out of them, one can feel free to change them to other values.
Evan, Kiwamu,
As some of us have already noticed, there is a broadband noise with a 1/f^{0.5} shape in frequency from 60 to 200 Hz. This noise is unidentified.
Do not believe any statements in this report until futher analaysis. Something is fishy with the claibration of the cross-spectrum.
We are planing to check how stable this noise level is over the course of the entire O1.
The below shows an example spectrum of DARM.
Blue curves are twenty spectra of DARM (aka C01 frame, converted into displacement), each of which is made by the Pwelch with Hanning, detrended, 50% overwrap for a 12 minutes time series. The data starts at a GPS time of 1134604817. Green curves are the square-root of twenty cross-power-spectra of DCPD A and B which are reconstructed from the sum and null streams of the DCPDs. The DARM suppression effect was removed from the sum signal. The cross-spectra are then calibrated to the displacement using the latest O1 DARM model of the calibration group. No time varying correction (i.e. kappas) is applied. Red line is a 1/f^{0.5} line to show how steep the slope of the green curves is. I also attach the fig file.
Gabriele, Evan, Kiwamu
There was a human-error in my code for calibrating the cross-spectrum. It was removing the loop suppression after the power spectrum of the null stream was subtracted from that of the sum stream. This was fixed such that the subtraction happens after the removal of the suppression in the sum spectrum. The below is the latest plot.
The plot shows the ampitude spectral desnsities of the calibrated darm displacement (aka C01) and the calibrated cross-spectrum. The cross-spectrum should represent noises which are coherent between two OMC DCPDs.
As a coarse verification, I have eye-ball-fitted the shot noise level with the fixed cavity pole frequency of 341 Hz (shown as a dotted line in cyan). Then I subtracted the shot noise component quadratically out from the actual displacement spectrum (in black). The residual (in blue) agrees with the estimation from the cross-spectrum. In order to check the slope of the cross-spectrum, I also drew a 1/f line. The cross-spectrum seems to follow 1/f from 50-ish Hz to 150 Hz.
The fig file is attached as well.
An update can be found in entry 25106
A higher resolution version is attached. The frequency resolution is set to 0.1 Hz, 50% overlap with Hanning for 1 hour data. No new findings.
The 1 Hz comb feature (see for example alog 24695) is becoming visible in 20-50 Hz. By the way, the legend in the plot is wrong.
Seismic activity in the earthquake band has come back to its nominal after a 6.0M earthquake in Fiji. Useism stil high but trending downward (still at 90th percentile though). Wind <10mph. CDS overview thinks there's still an excitation to the LSC but Gabriele said he had already stopped the excitation.
Dave walked me through on how to clear the test points and excitations. I also cleared ETMY timing error. The ifo is now locked at NLN.
model restarts logged for Sun 17/Jan/2016 No restarts reported.
The message:
The second harmoinc upconversion we see in DARM is much larger than can be explained by a quadratic term in the actuator response on any one of the suspension stages we use to drive DARM. Also, the coil balancing for ETMY L2 is a little bit off.
Details:
We have seen that driving DARM at frequencies from 5-10 Hz creates a second harmonic in DARM (alog 21240). One of the tests Evan and I have been thinking about doing for a while is driving each suspension stage in pringle to look for a second harmonic in DARM. The idea is that if we drive pringle, as long as the coil balancing is good there should be no longitudnal DARM motion at the drive frequency, although there would be longitudnal motion at the second harmonic frequency. This allows us to look for a quadratic actuator reposnse without having to worry about any quadratic effect in the sensors.
The second harmoinc upconversion we see in DARM is much larger than anything we can see by driving pringle on EMTY L1, L2, L3 or ETMX L2. (all the stages we use for DARM, plus ETMX L2 as an extra).
I repeated an injection similar to what we did in alog 21240, injecting a 500 counts at 6Hz into ETMY ISCINF. This resulted in a similar level of second harmonic. Then, using the lockin I excited pringle on each stage individually, creating a drive to each actuator that was significantly larger than the drive generated by the DARM excitation.
First attachment: ETMY L1 pringle drive. In the case where I was driving DARM you can see the excitation at 6 Hz in L1 MASTER OUT and the second harmonic at 12 Hz, when I drove pringle a factor of 5 harder on each osem, there is no second harmonic showing up.
Second attachment: Same for ETMY L2, driven a factor of 10 harder for pringle than DARM. You can see in the DARM spectrum in the upper panel that the coil balancing is a little off, so the pringle drive couples to DARM at 6 Hz a little bit. Also it is difficult to see the darm second harmonic in the master out for L2, probably because ASC drive signals dominate. I did a similar test for ETMX L2, and there is similarly no second harmoinc in DARM.
Third attachment: Same for EMTY ESD. We would expect to have some quadratic term to the ESD actuation since we don't use the linearization for ETMY, and you can see that even in the green trace where pringle is driven. However, this quadratic term is clearly much smaller than the one that causes the second harmonic when we drive DARM.
There is a script to help set these measurements up, in /sheila.dwyer/Noise/UPCONVERSION/PRINGLE_SETUP.py
It seems like the next thing to check is the sensors, for which we would like to transition DARM control to a true differential arm.
1510 - 1540 hrs. local -> Back and forth to/from Y-mid. Took ~20 minutes with LLCV bypass valve open 3/4 turn Next manual overfill scheduled for Tuesday, Jan. 19 th before 4:00 pm
We have been locked for more than 12 hours durring a time of unusally high microseism for Hanford. We have had elevated ground motion in the EQ band (0.03-0.1 Hz) which Robert thinks is due to a storm off of Greenland which has been slowly dropping off over the last 24 hours, but is still at 0.1 um/sec. We also have a storm in the Pacific and the corner station Z axis is reaching 2um/second in the useism band (0.1-0.3 Hz).
We have what seems to be a scattering shelf in DARM reaching up to just above 10 Hz, when the 0.1-0.3 Hz band is especially bad. The attached screenshot shows two particularly bad examples one at 22:54 UTC and one at 22:47:15
model restarts logged for Sat 16/Jan/2016 No restarts reported.
TITLE: 1/16 EVE Shift: 00:00-8:00UTC (16:00-00:00PDT), all times posted in UTC
STATE of H1: Observing at 80 Mpc
Incoming Operator:
Support: Evan
Summary:
Adam called off hardware injection due to LLO being DOWN. Robert couldn't get to the mid stations so he did injection on BS BSC for the up-conversion study. The ratty looking POP_A_LF was likely due to high seismic activity but the low output was due to TMSY was kicked by couple of micron during the last lockloss and slowly drifted since this lock was acquired.
Shift Activities:
01:45 Briefly out of Observing to stop the Hardware injection.
01:55 Robert to LVEA. Switched to Commissioning.
03:57 Touched TMSY to increase arm output power. Gained ~10 Mpc back in the BNS range.
04:29 Robert done. Back to Observing
My shift is *kind of* over but I have things to do so I will stick around probably close to midnight. Call control room if anyone need anything.
TITLE: 1/16 DAY Shift: 16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC
STATE of H1: Observing with Injections.
Incoming Operator: Nutsinee
Support: Sheila
Quick Summary:
PEM Injections at the beginning of the shift & then a good 3.5hrs devoted to recovering from a lockloss.
Shift Activities:
So after the long overnight-lock, H1 dropped out of lock mid-shift (Robert was at EY, but we were running ragged for the last few hours with fairly high low-frequency seismic motion).
Note:
There were a few new tricks which Sheila taught me when we were working on locking H1 in these noisy conditions:
1) When the ALSy was having trouble locking, we did a Clear History (yellow button on the ALS screen). This then gave us a very misaligned Y-arm (but this was taken care of fairly easily by adjusting only yaw on only ETMy).
2) While waiting for PRMI, POP 18 & 90 looked pretty bad. So, while in this state, the PRM was misaligned and then we adjusted the BS by eye while looking at ASAIR video.
These were two new tricks which I was not aware of.
I just wanted to mention that the 'odd' behaviour in the 0.03-0.1 Hz band (EQ band) was caused by the larger than usual primary microseismic motion, which is peaked at 60-70 mHz (seen in the spectra) . This is usually small at Hanford and large at Livingston, which is the reason their EQ band rms is always larger. In the presence of a lagre primary microseism, the 90 mHz blend will almost certainly give worse performance due to it's gain peaking near 90 mHz.
So, in addition to wind and the secondary microseism, also watch out for the primary microseism :)
TITLE: 1/16 Eve Shift: 00:00-08:00UTC (16:00-00:00 PDT), all times posted in UTC"
STATE Of H1: Observing + Hardware injection on going
OUTGOING OPERATOR: Corey
QUICK SUMMARY: POP_A_LF seems lower than usual and ratty. High Useism (above 90th percentile) and earthquake band. Big tidal fluctuations. Hardware injection has been scheduled to end at 6pm.
As POP_A_LF continued to drop, Evan suggested I touch TMSY. I trended TMSY back to 2 hours before it lost lock and adjusted pitch and yaw accordingly. It worked awesomely. I already checked with Robert to make sure this doesn't affect him.
I've schedule more burst injections and CBC injections, these will begin at 20:00 PT (00:00 UTC). The last one will be at 21:40 PT (01:40 UTC). Here is the updated schedule: 1137024017 2 1.0 burst_GPS_76.259_ 1137025217 2 1.0 burst_GPS_76.262_ 1137026417 2 1.0 burst_GPS_76.263_ 1137027617 2 1.0 burst_GPS_76.264_ 1137028817 2 1.0 burst_GPS_76.266_ 1137030017 1 1.0 coherentbns1_1135135335_
FYI: I restarted the LDAS/DCS Disk2Disk script that copies raw data from the framewriter disks into the LDAS archive this morning, Jan. 16, at 10:04 am PST.
model restarts logged for Fri 15/Jan/2016
No restarts reported. h1tw0 continues to be down waiting h/w repair.
Slushy snowy morning here on site with useism slightly trending up (above 90 percentile at 0.7um/s), and the EQ band actually has been trending up slowly over the last 12 hrs from ~0.05 up to 0.2um/s. Winds are under 10mph.
H1 has been in Observing as TJ left it and it has been locked for 16hrs (for most of the night the range was hovering just under 80Mpc. Now it has been around 75Mpc for the last 2 hrs. On DARM, I can clearly see elevated noise in the 20-30Hz band, a line around 42Hz & also noise in between. POP A on the PRMI striptool & tidal channels on their striptool show oscillations at ~0.4Hz.
I believe I see Robert pulling onto site (as I was chatting with Landry).
I've tried contacting LLO Control Room (TeamSpeak & phone), but perhaps someone has just stepped out of the CR (According to their Summary Page, they someone has been working on bringing L1 up). Will touch base with them when they are available to coordinate double coincidence for a suite of hardware injections. In the meantime, Robert will be taking H1 for PEM injections soon. Robert has said that he can "stand down at any time to allow hardware injection work". Robert will be heading to an End Station for his PEM work.
Terramon after-the-fact notified us that there was a 4.9 Costa Rica quake at 17:23 with motion of 0.38um/s.
h1tw0 continues to be down (also causing a red EDCU)...not sure whether I need to keep reporting this. This comes up when operators run through the shift check sheet.
J. Kissel, R. Savage, LHO Operators Tallying up the progress so far on the schedule of PCALX excitations at high frequency (see plan in LHO aLOG 24802): Achieved Planned Frequency Amplitude Start Time Stop Time Duration Duration Success? (Hz) (ct) (mm-dd UTC) (mm-dd UTC) (hh:mm) (hh:mm) (Yes / No, reason if no) ------------------------------------------------------------------------------------------------------------------------------ 1001.3 35k 01-09 22:45 01-10 00:05 01:20 01:00 Yes 1501.3 35k 01-09 21:12 01-09 22:42 01:30 01:00 Yes 2001.3 35k 01-09 18:38 01-09 21:03 02:25 02:00 Yes 2501.3 40k 01-09 12:13 01-09 18:31 06:18 02:00 Yes 3001.3 35k 01-10 00:09 01-10 04:38 04:29 04:00 Yes 3501.3 35k 01-10 04:41 01-10 12:07 05:26 06:00 Good Enough! 4001.3 40k 01-09 04:11 01-09 12:04 07:55 08:00 Good Enough! 4501.3 40k 01-10 17:38 01-11 06:02 12:24 12:00 Yes 5001.3 40k 01-11 06:18 on-going (as long as we can get) Thanks to all of the operators who have been dilligently caring for these lines while we sleep! For the record, while these PCALX calibration lines are on, the majority (if not all) of the range is consumed, so we cannot perform PCALX hardware injections.
I used the high frequency calibration lines injected above to estimate the sensing function at those frequencies. For this analysis, SLM Tool was used to obtain the line amplitude and phase of these calibration lines at different relevant channels.
Sensing Function = DARM_ERR[ct] / PCAL_TXPD[m]
The DARM_ERR signal is dewhitened and the PCAL_TXPD is corrected to get metres using the scheme described in G1501518.
Furthermore, ratio of GDS/Pcal is calculated and is included in the attached plot.
A data quality flag has been created to capture times when these extra PCAL lines were in the data. It is H1:DCH-EXTRA_PCAL_LINES:1 and a description of this flag can be found on the detchar wiki.