Brute Force coherence report is available here for last night lock:
https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1115716006/
Some highlights, which I find very interesting:
Not much is happening at higher frequency, at least for broad band coherence. However there are a lot of single frequency bins with significant coherence, and I can't list all of them here (I'm too lazy). So look into the table at your favorite line frequency, you might be rewarded with some coherence.
After the time that Gabriele looked at, the coherence of CARM with DARM went up to nearly 1 above 500 Hz (and 0.5 at 100 Hz). This seemed to continue for the rest of the lock. All of the loudest glitches, which had peak frequencies at about 200 Hz, showed up in CARM as well as DARM. What is going on? The first plot is a reproduction of Gabriele's coherence plot. The second is about a half hour later, and the third near the end of the lock. The last is a coherence spectrogram of CARM with DARM during this very loud glitch near the end of the lock, which showed up as strong in CARM as DARM.
LSC-CARM is not used anymore for any feedback to the IFO; we use it sometimes to make an audio channel out of DARM so that we can listen to the IFO. Stefan was tuning the audio filters after we hit the intent bit last night.
The actual feedback to MC2 from the CARM slow loop goes through the LSC-MCL filter bank. If you want an out of loop CARM sensor you can look at LSC-REFL_A_9I, for the error and control signals you can look at the common mode board channels, eg LSC-REFL_SERVO_ERR_DQ or CTRL_DQ
By the way, instead of stealing the CARM filter bank to process audio, you can apply the filter directly in the audio player:
$ cdsutils audio H1:CHANNEL-NAME -f 'filterspec'
where 'filterspec' is a filter design string, as you would type into Foton. (This was requested in CDS bug 797 and added in cdsutils r444.)
It seems unneccesarily confusing to use a named channel with a very clear symantic meaning for something other than it's intended purpose. Can we not just make some separate filter banks just for filtering audio output? Either that or use the built-in cdsutils audio filtering that Chris mentioned.
For historical reasons, the isolation loops that are installed on the BSC's were all quite different. I've been working on a consistent set of controllers for the ISI's and I've installed them on ETMX, ETMY and ITMX. I need to look in more detail at the BS, but ITMY needs to be redone, the filters in foton don't look anything like the ones Matlab says are installed, they look like Vincent's filters from several years ago. The ones I've done for ITMX are the cleanest plots, so I'm posting the comparison plots, Old_ITMX_controllers and New_ITMX_controllers pdfs. The goal was to get the unboosted isolation loops as similar as possible, use the same boosts every where and hopefully get all o the chambers to similar performance. Generally this resulted in loops with 30-45 hz UGF, 17-20 degrees of phase margin and gain peaking of 4-5. I was aiming for as close to a gain of 10 at 10hz as I could get and gains of 1000 at 1 hz.
I spent a bit of time this morning clearing out remaining SDF diffs in SUS, LSC, and ASC. This involved the usual alog hunt followed by some clarifications from commissioners. Things still showing diffs at the moment and why:
- We need to capture a new snap file for the OMC due to yesterday's model change which will clear out it's large SDF diff list.
- The ASCIMC still has one diff due to a 10e-17 size change in one value. I think this feature is due for an upgrade at some point, so until then, this 1 diff will be lingering.
- Same with ISCEX - there are 2 diffs with very small diffs which won't go away with the accept button. Will linger until update.
- We need some assistance with clearing the PSL diffs from team PSL.
- I've not paid much attention to the bottom monitors, namely ODC and CAL.
Comment posted to the wrong aLOG. Deleted!
With a lock stretch of over 7.5 hrs at ~23.2W & a range of ~57Mpc, here is a picture of last night's lock stretch. Just before 9am, H1 lost lock (no obvious reason, as we continued operating in an Undisturbed state), the Intent Bit was taken to Commissioning, and Ellie started SRCL work.
Here are the trends for the various DC, 18MHz and 90MHz powers. Some small variations are visible in the first hour, which are probably due to thermal loading.
Attached is a plot of the default lockloss file Travis and I ran for this lock. (time entered was 8:53:00am PST).
Sheila, Evan, Stefan - Reduced the whitening gain on both AS 36 ASC diodes. The new value is 24dB. We increase the input matrix values from 1 to 2 to compensate (for MICH and SRC1, i.e. the SRM loop). - We tried to phase the AS_A_36 quadrants by wiggling SRM in yaw and pitch, maximizing the I signal. Not sure how meaningful that was though, because the actual signal we ended up using was Q. - We switched the the sensor for SRC1_YAW (SRM) to 0.3*AS_A_36_Q + 0.3*AS_B_36I. This signal clearly reacted to our mysterious SRC cavity drifts, and had zero offset at the good locking point. - We increased the power to 23W. This is the maximum power currently available. With this new SRM yaw sensor the 23W was very stable. - The DARM offset was 14pm (or 1e-5 cts). - This gave us a recycling gain of 38. - Measured the open loop gain and verified the calibration. - This configuration was stable for 1h. - We took SRCL noise injections at: 8:46:15UTC and 8:59:40UTC (SRCL cut-off filter off and on) - We took MICH noise injections at: 8:52:15UTC and 8:55:40UTC (SRCL cut-off filter on and off) - Pushed the intent bit at 9:06:30 UTC. - The inspiral range seems quite remarkably flat at 57 Mpc. A stron indication that we are now purley electronics noise limited at low frequencies. To do tomorrow: - Explore DARM offset: the new OMC code is ready to install, and will allow on-the-fly OMC offset tuning. - Add the new ASC INMATRIX to Guardian. - Add the new DARM offset to Guardian. - Generate noise budget.
Attached is a new spectrum, before and after screenshots of the AS A 36 WFS phases, and 3 OLG measurements made at 3 different input powers.
Great progress, congratulations!!
I will take a closer look at the noise budget over the weekend, but it seems (roughly) that above 20 Hz we are currently limited by DAC→ESD noise and quantum noise. As usual, there is some uncertainty in coupling strength of the ESD to DARM, which may explain the discrepancy in the plot from 20 Hz to 100 Hz.
This is fantastic -- perfect timing for the low noise Electro-Static Driver installation next week!
Excellent news! Well done.
Looks like discharging and lower noise driver will do some good. Nice going.
Truly great progress. Nice work, LHO commissioning team!
Beautiful! Nice and stable as well! I was not able to change my slides for the invited LIGO talk at APS Northwest Section Meeting, but I did announce your success. Great timing too.
Well done all at LHO. That's great progress.
Tonight Dan went through some of the old violin mode damping settings, we have had all violin mode damping disabled for the past several weeks in the guardian since we improved the recycling gain. Dan found that the old settings work for 6 of the modes, ITMY mode 3,5 and 6, ETMY mode 5, and ITMX mode 3 and 6. For ITMY mode 4 we need a sign flip in the gain. All of the ones that Dan checked I put back into the gaurdian, some of which now have lower gain than before. I also added ETMY roll mode damping back in the guardian.
Bounce | Roll | ||
ETMY | 9.730 Hz | 13.816 Hz | 14854 |
ETMX | 9.77 | ||
ITMY | 9.8135 | 13.934Hz | 18395 |
ITMX | 9.8469 | 15400 |
the remaining roll modes are at 13.89 and 13.98 Hz, but we don't know which is from ETMX and which is from ITMX
The ITMY bounce mode is 9.83 Hz.
Elli, Nutsinee
The return SLED beam is now centered on the ITMX HWS. The QPD1 sum reads 1.71 (mean) and the QPD2 sum reads 1.32 (mean). Green light was resonates in both arms during the time of the measurement.
The current position of the HWSX lower periscope mirror is X: -286 Y: -927 and the current position of the HWSX upper periscope mirror is X: 300 Y: -300.
The Hartmann plate is off at the moment.
The move of the piezo mirror from the top of the periscope to the table top (Link) left large features in DARM at least in part because a resonance of the mirror mount that replaced the piezo mirror mount, overlapped with a higher frequency periscope peak, just as the lower frequency resonance of the piezo mounting had overlapped with a periscope peak at lower frequencies. Figure 1 shows, in red, periscope spectra before tuning, and, in blue, after tuning. The idea was to move the optic resonances, indicated by the high DARM coherence in red at 340 and 390 Hz, into the red valley centered at about 310 Hz by adding weight. The blue trace shows that the peaks were moved to 310 and 340 and the coherence with DARM was reduced.
Figure 2 is an “after” photo showing the weight that was clamped to the mirror mount to make this change. In addition, figure 2 shows the safety cover, which covers the vertical path of the beam, that is responsible for the peak just below 300 Hz. Unlike the rest of the periscope, this safety cover is not damped and definitely needs to be - the safety cover resonance is showing up in DARM.
I also added a little weight to the top of the periscope to reduce coherence with DARM at 190 Hz by splitting overlapping resonances. This also helped.
I think that the next step is to minimize jitter coupling from the PSL table to DARM, possibly by injecting a peak using the PSL piezo and modifying alignment to minimize the height of this peak in the IM4 pitch and yaw signals and eventually by minimizing the injected peak height in DARM.
Just for comparison LLO does not have this safety shield installed on the periscope anymore. It was removed when the PZT swapped happened at LLO.