Kiwamu, Daniel
The two Thorlabs PDs that measure the power after the EOM and at the bottom of the PSL periscope were originally intended for low frequency only. However, they can be useful for intensity noise characterization as well, so we used the two spare channels on the PD interface box to acquire AC coupled and amplified versions too. The AC coupling is at 4 Hz and the gain will be 200. The ascimc model has been updated with separate AC, DC and normalized channels. These are then used to form relative intensity noise channels.
Terra, Evan
We continued our examination of EY body mode Q factors and made a quick estimate of the resulting coating loss.
This time, we simultaneously rang up one of the butterfly modes and two of the drumhead modes during a 50 W lock and watched them ring down for about 45 minutes. The resulting Q factors are as follows, with the uncertainties determined by the χ2 of the fit.
Plots of the ringdowns, along with the fits, are attached. The script to generate the numbers and plots in this alog is also attached.
We have also used the rough FEA numbers given previously for the surface-to-bulk energy ratios to estimate the loss angles of the EY coating and substrate. We assume both losses are structural. The resulting posterior (assuming a log-uniform prior on each loss) is shown in the attached plot. The 1d marginalized loss estimates are as follows:
Using the formula from Nakagawa et al., this implies a thermal noise of 8.1(8)×10−21 m/Hz1/2 at 100 Hz, which is about 14 % higher than direct audio-band measurements on witness samples.
Future work:
17:07 Jim to EY to check on the BRS power supply and to change a setting so that it will come back up after a power outage.
17:11 BRS at EY switched off.
17:15 Jason and Peter ou to the PSL enclosure to begin work reducing flow to possibly mitigate intensity noise.
17:30 Betsy out to LVEA to do TCS inventory
17:31 Travis out to LVEA to retrieve ITM Pcal camera
17:32 Jim back from EY
17:32 Jeff K to begin charge measurements
17:36 Jason called from enclosure - LASER is going DOWN
17:59 Travis back from LVEA
18:33 Travis headed to end stations for Pcal camera work. Switching BRS Guardian to VERY_WINDY as per Jim's wiki page under the SEI tab
18:59 Jason and Peter out of the enclosure. THe LASER is ON.
19:00 DAQ restart
20:28 Start initial alignment
20:45 Switched BRS back on at both ends
21:00 Begin locking sequence
A quick inspection of the PMC output mirror and window was done whilst the PMC was
locked and unlocked. No obvious bright scattering points or marks, spots .... etc.
were apparent.
Nothing was spotted on the optics between the PMC and the IO EOM either.
Jason/Peter
The neutral density filter that was installed in front of the ISS photodiode box was removed. The half waveplate inside the ISS photodiode box was adjusted so that the output voltage of PDA was ~5 VDC when the ISS was unlocked. Jason/Peter
LN2 at exhaust after 6 minutes 26 seconds of having the LLCV bypass valve opened 1/2 turn -> restored bypass valve to as found (closed) state. Increased manual setting for LLCV from 16% to 17% Next CP3 overfill to be Wed., Sept 21st.
As requested, the flow rates through the laser heads was reduced from ~0.7 lpm to 6 lpm.
The minimum flow rate was dictated by the flow rate on head 4, which was lower than the
others from the outset. Its flow was set so that the flow rate was ~0.5 lpm. The flow
rate was reduced by adjusting the bypass valve on the cooling manifold. The flow rate
out of the chiller is already set to its non-zero minimum value.
The flow rate in the power meter cooling circuit was also reduced by adjusting the
pressure regulator.
Jason/Peter
2nd loop QPD output alignment signals didn't make sense (attached top), and this turns out to be whitening mismatch.
This QPD goes through the QPD interface and standard whitening, and there is one unswitchable zp=0.4,40 analog whitening. This is supposed to be compensated by zp=(40,0.4) anti whitener (which is unfortunately named 0.4:40), which was off.
I turned them ON (attached left) and now it makes sense (bottom).
J. Kissel I've measured this week's charge assessment early, just to get it out of Tuesday's way while opportunity struck during ISS improvements this morning. All is well: charge continues towards zero, and it looks like in a few weeks -- at the start of ER10 -- we can try regular ESD bias flipping again. Impressively, but perhaps inconsequentially, the rate of charge on ETMX has increased substantially over the past few bias flips. However, this may also be a function of how much time we've spent over the past few months commissioning with the DARM drive still on ETMX. The fluctuation of actuation strength of ETMX is not important to calibration, and lock acquisition is not-so-sensitive to it, but this fast rate may confuse our assessment of the charge from week-to-week while it hovers around zero. Perhaps we should consider -- during ER10 at least, if/when we begin regular flipping -- measuring charge twice a week, just to get more that one data point per flip.
WP6168. Daniel:
A new h1ascimc model was installed. This replaces two SPARE DAQ channels with 3 PWR_EOM channels in the commissioning frame (all at 2kHz). Additional filtermodules were added (no DAQ inclusion).
Model and DAQ were restarted at 11:55 PDT.
Pressure comparison between hot IG and cold cathode gauge on diagonal volume. Tomorrow CC will be decommissioned via WP 6166. (green trace is hot IG; red is CC that has been flaky and turning off periodically)
J. Kissel reporting for D. Sigg, K. Kawabe, L. Barsotti, M. Evans, K. Izumi, R. Savage, P. King, J. Oberling, J. Driggers, R. McCarthy The following ideas / action items were discussed at this mornings 9a LHO commissioning meeting to battle / reduce intensity noise; the primary high-frequency noise contribution/ limitation to the DARM sensitivity at the moment. I don't know every detail, so hopefully you can glean the action from the words I was able to capture from the meeting. The list is also in no particular order, but the hope is to accomplish most of these tasks over the next few days. - Look at recent DBB scans for any evidence of free-running intensity noise badness. - Reduce PSL HPO chiller flow rate from 0.7 [L/min] to 0.5 [L/min] returning to O1 level flow rate - Remove ND filter that had been recently installed to rule out scattering noise from the 1st loop PD array - Inspect PMC output ports for excessing scattering / badness - Move EOM on its translation stage, checking for changes in intensity noise output. - Install high-sensitivity electronics on EOM PD (IO_AB_PD3 in D0902114, read out as H1:IMC-PWR_EOM_OUT16) and IMC PWR IN (IO_AB_PD2 in D0902114, readout as H1:IMC-PWR_IN_OUT16) - Install extra high-sensitivity PD in ALS path on PSL table. (This path is upstream -- toward the front-end laser -- of the EOM. The PD will be used to compare the intensity noise upstream vs. downstream of the EOM which is currently an area of suspicion. The worry is that there is too much between the pickoff on the PSL and where this pickoff is already captured on ISCT1, which may confuse the intensity noise measurement) - ISS front-end model reboot in order to improve channel naming conventions for ISS channels (e.g. INNERLOOP / OUTERLOOP to FIRST/SECOND LOOP-like changes) - PEM front-end model changes to store PSL accelerometers at higher sampling rate - ASCIMC front-end model changes / or create a new front-end model to process/store EOM PD, IMC PWR IN PD, and IM4 TRANS at higher, (4? 16 kHz?) rate. - Modify new ISS 2nd loop analog electronics (drill a few holes in front panels) to pull out more signals to analog BNC spigots - Move IMC / IFO alignment offsets to find jitter coupling minimum. Hope this helps!
No restarts over this 3 day period. Test frame writer did some restarts Friday morning, none since we installed RCG3.2-daqd (aka Jonathan's code) Friday afternoon.
Here is the current state of the H1 DAQ.
h1fw0 and h1fw1 have been completely stable for several weeks, and following the code fix on Wednesday 9/7 the frames written by both are 100% identical. These systems have the same hardware and are running the same code, but h1fw0 occasionally asks for retransmissions and h1fw0 never does. The OS install is slightly different between the machines, and we will try cloning fw0 from fw1 next week.
h1fw2 is a front end computer, running U12 with a local disk system for frames. It was running the original daqd code, but went unstable after the Sat 9/10 power outage. We upgraded it to the rcg3.2 daqd this afternoon to see if this improves stability. It is now connected to UPS power.
Now that h1fw2 has the new set of EPICS diagnostics channels I have expanded the DAQ overview medm screen to show these.
as of monday morning, fw2 has been running 2.8 days. Looks like Jonathan's code has made it stable. It is still a mystery why the power outage apparently caused the instability of the old code (it has been power cycled since then).
Sheila, Kiwamu, Evan, Matt, Lisa, Jenne, Corey
Tonight the locking has been stable enough that we were able to try several low noise steps. We ended up with a range of about 20 Mpc, and were locked for 3.5 hours.
I used the 332 Hz and 1 kHz pcal lines to update the calibration front-end values for the DARM gain and pole. With these new values, we see that the DARM sensitivity is below the O1 sensitivitiy in the few kilohertz region (depending on the behavior of the intensity noise).
I did not change the value for the antispring or the actuation strengths.
J. Kissel, E. Hall
Providing some more quantitative details of Evan's calibration change:
The reference optical gain (newly installed in FM8, called "ER10gain") is now 8.40e-7 [m] / DARM_ERR [ct], changed from 1.102e-6 (installed in FM4, called "ER9 gain"), a change of 24%. This new optical gain, in physical units is 5.08 ([mA] of DCPD SUM) / ([pm] of DARM displacement), the expanded version of the Evan-loved units he simply calls "[mA/pm]."
The reference cavity pole frequency is now 342.0 [Hz], (newly installed in FM7, called "SRCD-2N") where it used to be 328.7 [Hz] (installed in FM3, dreadfully also named "SRCD-2N").
Both the optical gain and cavity pole were determined in rough fashion by taking the magnitude of the (PCALY's TX PD / DARM IN1) transfer function at the calibration line frequencies (331.9 and 1083.7 [Hz]), and solving the following system of equations for K (the optical gain) and fc (the cavity pole frequency):
( |H|_{@331.9 Hz} )^2 = K^2 / (1 + (331.9 / fc))
( |H|_{@ 1083.7 Hz} )^2 = K^2 / (1 + (1083.7 / fc))
i.e. the naive single-pole approximation. Solving such a system is a one-liner in Mathetmatica (which is what Evan did):
NSolve[{3.64^2 == (K^2 / (1 + (331.9 / fc)^2)), 1.52^2 == (K^2 / (1 + (1083.7 / fc)^2))},{K,fc}],
where 3.64 and 1.52 where the respective TX PD / DARM IN1 transfer function magnitudes at 2016-09-17 07:15 UTC, or Sep 17 2016 00:15:00 PDT). Evan chose PCALY's TX PD instead of PCALY's RX PD, simply because he wasn't aware that RX PD was the standard.
It should be mentioned that in trying to quantify from where he gathered these numbers for this aLOG comment, we grabbed the transfer function all through out the lock stretch of the above summarized night; highlighted in the screencap of the summary page. The transfer function values over the course of the lock (spot-checked every 15 minutes or so) yielded an optical gain and cavity that varied wildly, from optical gains from ~3 to 5 [mA/pm] and cavity pole frequencies from 250 to 370 [Hz]. We do not expect either physical parameter to varying that much. Thus, this method -- albiet delightfully simple and quick, we assume it has a very large uncertainty .
Also, though it was assumed that the optical spring frequency from SRC cavity detuning did not change (i.e. Evan did not change it), we're not confident that it has not changed. Regardless, for the time being, the reference optical spring frequency remains 9.81 [Hz].
In the words of Evan "I just wanted to do something quickly for the purposes of, and at the accuracy needed for, noise hunting. I knew the calibration group would do this much better within a week or two, so it wasn't worth the time to go through the whole shebang." I agree.
I've saved the template for the attached transfer function in
/ligo/home/jeffrey.kissel/Templates/H1DARM_Calibration_mA_per_pm.xml
which we can use for future quick-studies like this.
The BRS at EY has had a long term drift requiring periodic recentering. That drift seems to have stopped or changed sign, following the power outage on Saturday. Attached image is a 60 day trend for H1:ISI-GND_BRS_ETMY_DRIFTMON. The black streaks are from when the BRS went out of range and when it was recentered during Krishna's last visit. The little blip up to zero at the end is from the power outage, before the commissioners recovered the BRS code. Second image is the last 6 days, outage is when the signal goes to zero. Definitely looks like the drift has changed sign.
I checked the temperature ('H1:ISI-GND_BRS_ETMY_TEMPR') and it looks a bit lower than normal, so it doesn't account for the change in the drift. It may be good to go to EndY and check on the Ion pump controller and make sure that it is ON? If it didn't get turned on after the power outage, a rising pressure might be the cause for the change in drift. The Ion pump controller should have a High Voltage indicator which should be on and clicking the OK button should give you the pump current and pressure reading.
The ion pump was off. It took a couple tries to get it to come back on. Voltage was around 5200V and 9-12 mA when I left the end station, pressure was already back to ~1E-5 torr. The power supply is kind of hidden under some other stuff, under the beam tube. Gerardo tells me that the power supplies at each end station are different, the one at EX comes back on it's own, EY doesn't. I'll see about adding a note to the start up procedure in T1600103.
IP power supply status should be added to vacuum GUI in CDS so we can catch power failures right away.
I have updated the correction filter for the dtt DARM spectra that are projected in the wall and screens in the control room. I hope Evan will like it.
[The DARM spectra]
Here is a comparison of the newly corrected and previous DARM spectra.
As shown in the attached screenshot, the high frequency excess wing that has been shown above 3 kHz is now gone. The noise level at around 7 kHz now seems a bit too low compared with the f-shaped GWINC curve (shown in green). This maybe a real calibration error because I have applied the best and latest knowledge about the sensing chain for correcting the spectrum.
The correction filter is made by a matlab script:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER8/H1/Scripts/ControlRoomCalib/H1DARM_FOM_correction.m
This script creates a text file which contains the correction filter in [freq, dBmag, phasedeg] format from 1 Hz to 7444 Hz. The text file can be found at
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER8/H1/Scripts/ControlRoomCalib/DARM_FOM_calibration.dat
Both script and text files are checked in to the svn. Also I updated the latest FOM dtt template, H1_DARM_FOM_20150722.xml so that it now uses the new correction filter.
[Corrections newly included]
Here is a list of what I newly included.
Note that the previous correction was made only from the IOP down sampling filter and the numerical whitening zpk([1,1,1,1,1], [100,100,100,100,100]) which are still included in the new correction.
For those of us who like to look at the DCPD streams, I modified the script to also produce the appropriate correction TF (using the uncompensated preamp poles, the AA filter, and the downsampling filters only).
There is still a little bit of sloping at high frequencies, even in the null stream (which we expect to be flat above 100 Hz). Maybe the AA model needs to be tuned?
I happened to come across this code again to reproduce the calibration correction filter for O1. I then found some bugs in the code which are now fixed.