We found that DMF/ was not an SVN working copy, so I wiped out the SVN version, imported the on-disk copy, moved it to DMFold/ and then checked out the SVN version.
We can delete DMFold/ whenever we are happy with the SVN copy.
I (think I) restarted DMF. It's on Mafalda, running in matlab (not the complied version which Rana was having trouble with back in the day). To start Matlab, I did "nohup matlab", ran mdv_config, then started seisBLRMS.m running. Since I used nohup, I then closed the terminal window, and am crossing my fingers in hopes that it continues to work. I would have used Screen, but that doesn't seem to work on Mafalda.
Just kidding. That plan didn't work. The new plan: I started a terminal window on Op540, which is ssh-ed into Mafalda, and started up matlab to run seisBLRMS. That window is still open.
Because Unix was being finicky, I had to open an xterm window (xterm -bg green -fg black), and then ssh to mafalda and run matlab there. The symptoms which led to this were that even though in a regular terminal window on Op540, ssh-ed to mafalda, I could access tconvert, I could not make gps.m work in matlab. When Rana ssh-ed from Allegra to Op540 to Mafalda and ran matlab, he could get gps.m to work. So it seems like it was a Unix terminal crazy thing. Anyhow, starting an xterm window on Op540m and ssh-ing to mafalda from there seemed to work.
Hopefully this having a terminal window open and running DMF will be a temporary solution, and we can get the compiled version to work again soon.
While waiting for the installation of the 32-bit Matlab 2009a to finish, I tried updating our seisBLRMS.m code.
Although DMF is in SVN, we forgot to check it out and so the directory where we have been doing our mods is not a working copy and our changes have not been captured: Shame.
We will probably have to wipe out the existing SVN trunk of DMF and re-import the directory after checking with Yoichi for SVN compliance.
Also wrote a script: LSC/x2mc, which will transition from regular ETM based X Arm locking to the MC2 based locking. It ran once OK, but I get a segfault on the 'trianglewave' which was trying to run the 'ezcastep' perl script which was calling 'ezcastep.bin'.
I also restarted the seisBLRMS.m on a terminal on Mafalda in the new Matlab 2009a to see if it loses its NDS connection like it did with 2007a. I also reduced the 'delay' parameter to 4 minutes and the 'interval' to 1 minute. This should be so that the total delay is now 5 minutes between seismic noise and seismic trend.
I've brought 4 DO-32L-PE cards from WB for BHD upgrade for Jon.
I have added a DQ block to the sus_single_control library part. This means that all sus models will automatically generate DQ channels based on what is specified in this doc block:
So for instance, for BS will have the following DQ channels:
etc. The channels names modified by the activateDQ.py script after install are still modified appropriately.
This is now the place where we should be maintaining DQ channels.
I have copied over the complete frame files from two DRFPMI lock acquisitions + locks to /frames/archive. The data should be safe from the wiper script here.
One, under the subfolder DRFPMI_Mar29_cal is the lock where the CAL-DARM channel is properly calibrated at GPS time 1143274087.
The other lock, under DRFPMI_MAR29_nocal, does not have the calibration set up yet, but was a much quicker acquistion (<2 min from ALS acquisition to DRFPMI) and longer lock (~8min).
Three RF-only locks longer than a minute tonight, out of 5 total attempts.
Last week, I determined that the beam spot on the RF POP PD is too large. This still needs to be fixed. I updated the ASS model to use REFLDC as a PRCL dither error signal; it works.
There seems to be some excess angular motion of ETMY tonight. This is evident in the oplev spectra (as compared to ETMX), and the GTRY camera, and even the retroreflected beam from a misalgined ETMY on the ITMY face when the PRC is carrier locked.
Gautam and I mostly focused on setting up the CAL-DARM_CINV block to produce this (mostly) calibrated spectrum starting from GPS 1143274087. [Darm on unwhitened AS55, DRMI on 3F, one CARM boost]
Here are the control and error signal spectra:
[DTT files attached]
Note to self: archive some of this data
For real this time.
Fast ALS was still a problem tonight. I don't think high frequency ALS noise saturating the PC drive is the issue; I put two 10k poles before the CM board (shooting for just 2-3kHz bandwidth), and the PC drive levels would be stable and low up until the lockloss, which was always conincident with a step in the AO gain.
After working with that for a few hours, we turned back to our more standard locking attempts. First, we dither aligned the PRMI, and then centered the REFL beam on REFL11. It's hard to say for certain, but we may have been a little close to the edge of the PD. The only other thing that differed from Monday's attempts was using 6dB less AO gain when trying the up the overall gain.
The script now reliably breaks through to stable high powers, we had a handful of pure-RF locks tonight. The digital DARM gain needs tuning, and the CARM bandwidth still isn't at its final state, but these are very tractable. Off the top of my head, the way forward now includes:
Unrelated: I feel that the PRC angular FF may have deteriorated a bit. I'm leaving the PRC locked on carrier to collect data for wiener filter recalculation.
in addition to Koji's words I feel like we should also thank those who made small but positive contributions. Its hard not to notice that this locking only happened after the new StripTool PEM colors were implemented...
From the times series plot I guess that the fuzz of the in-loop DARM is 1 pm RMS (based on memory). This means that the ALS was holding the DARM at 10 pm from the RF resonances.
There is no significant shift in the DRMI error signals, so new weird CARM effect. Would be interesting to see what the 1f signals do in the last 60 seconds before RF lock.
For documentation, perhaps Gautam can post the loop gain measurements of the 5 loops on top of the Bode plots of the loop models.
We worked on getting the DRFPMI back up and running, hoping the ALS performance was good enough.
We did succeed in bringing in enough of the AO path to stabilize arm powers > 100, but failed at the full RF DARM handoff.
REFL165 angle was adjusted to -86 to minimize PRCL in the Q signal.
The AS110 signals are mysteriously huger than they used to be. Whitening gain reduced to 15dB from 27dB. Old trigger thresholds are still fine.
The new AUX X laser has a different sign for the temperature-> frequency coupling, so our usual convention of "beatnote goes up when temp slider goes up" meant the ALSX input matrix elements had to change sign.
We think the POPDC PD (which I think is the POP2F PD) may be miscentered, since in PRMI configuration, its maximum does not coincide with the REFLDC minimum, and leaves a sizeable TEM10 lobe on the REFL camera. This was a pain.
Highlight of the night: the DRFPMI was held at arm powers > 110 for 20 seconds. ALS feedback was still running though, but so was some nonzero REFL11 AO path action.
In short, time was spent finding the right FM trigger settings to keep the DRMI locked while CARM is fluctuating through resonance, what CARM offset to acquire DRMI lock at, order of operations of turning on AO / turning up overall CARM gain, etc.
Sadly, for the past hour or so, the DRMI has refused to stay locked for more than ~20 seconds, so I haven't been able to push things much further. This is a shame, since I'm very nearly at the equivalent point in the PRFPMI locking script where the ALS control is turned off completely.
Progress was made. CARM was stably locked on RF only. DARM was RF only for a few moments before I typed in a wrong number...
A change was made to the LSC model's triggering section to make the DRMI hold more reliably at zero CARM offset. Namely, the POPDC signal now has its absolute value taken before the trigger matrix. Even unwhitened, it occaisionally would somehow go negative enough to break the DRMI trigger.
AUX X laser was acting up again. As before, tweaking laser current is the temporary fix.
Please clarify: I wonder if you were at the zero offset for CARM and DARM or not. I am 25% excited right now.
Please clarify: I wonder if you were at the zero offset for CARM and DARM or not.
Yes, this was at the full DRFPMI resonance.
Give us a lockloss or other kind of time series plot so we can bask in the glory.
Look upon this three second lock, ye Mighty, and rejoice!
I hope the grappa was already cold, and ready to drink!
Before Yuta left, I asked him to restore all optics to last saved values, to avoid hysteresis.
Some interesting modes appear at ETMYT and ETMXT. The cavities aren't super well aligned right now, especially since we have been seeing this input pointing drift, but it's cool to see our first DRFPMI flashes. SRM, in particular, hasn't been aligned since before pumpdown. If I misalign SRM, the mode content at the trans cameras improves somewhat, but it still isn't all low-order modes.
Here is the note that I wrote on youtube describing the video:
Upper left is AS, upper right is POP
lower left is Xarm Trans (ETMXT), lower right is Yarm Trans (ETMYT)
Arms were last aligned several hours ago, and we know input pointing drifts, so at least some of the higher order modes in the arm transmissions are due to poor input pointing. All optics are "restored" to their last saved values, including SRM, which has not been aligned since before pumpdown.
TRX DC PD values are flashing to as high as 10
TRY DC PD values are flashing to as high as 7
Since uploading the video, I have seen TRY flash (once) to 45. Yes, forty five!!! Both arms are usually flashing to ~3ish, with an occasional medium flash (5-10), and then a few rare TRY flashes above 20.
We may have officially lost the bet of having arms locked by 9am Monday, but I think Team Grad Student / Postdoc still deserves some beer from Team Faculty / Staff.
If its true that there have been large flashes, then there indeed might be beer. But first I'd have to see a calibrated plot. And make sure that the flashes are not overamplified due to a whitening filter imbalance.
Is it the readout of a PD with no whitening/antiwhitening? IF so, its much easier to believe.
A handful of DRFPMI locks tonight, longest one was ~7 minutes.
EPICS/network latency has been a huge pain tonight. The locking script may hang between commands at an unstable place, or fail to execute commands altogether because it can't find the EPICS channel. This prevented or broke a number of locks.
I made some CARM OLG and crossover measurements, and found the AO gain for the right crossover freq (~100Hz) to be ~8dB different than what's in the PRFPMI script, which is weird. Right now, the CARM bandwidth / ability to turn on boosts is limited by the gain peaking in the IMC CLG due to the high-ish PC/PZT crossover frequency we're using.
Gautam turned on some sensing excitations during the last couple of locks, but they weren't on for very long before the lock loss. Hopefully I can pull out at least some angles from the data.
I'm also more convinced that the PRC angular FF needs retuning; there is more residual motion on the cameras than I'm used to seeing. I've taken more data that I'll use to recalculate a wiener filter tomorrow.
The PMC, ALSX beat and ITMX oplev all needed a reasonable pitch realignment tonight.
The length of DRFPMI lock did not increase much tonight, but we got a ~80 second sensing matrix measurement, and got the CARM bandwidth up to 10k with two boosts on.
NB: I did not measure the CARM loop gain at its excitation frequency, so the plotted sensing element is supressed by the CARM loop. However, this is still useful for gauging the size of the PRCL signal vs. the residual CARM fluctuations. The excitations are fairly closely spaced between 309 and 316 Hz.
For comparison, I'm also re-plotting the DRMI sensing measurement from a few weeks back taken at CARM offset of -4. We can see some change in the PRCL sensing, likely due to the CARM-coupled path. MICH/PRCL sadly looks pretty degenerate, but REFL55 looks more reasonable.
I think the main limitation tonight was SRC stability. Even before bringing CARM to zero offset, we would see occasional sharp dives in AS110 power. One lockloss happened soon after such an occurance, but I checked the values, and it was not sufficient to trigger the Schmitt trigger down; instead it may have been a real optical loss of signal. The SRCL OLTF looks sensible.
Tonight was kind of a wash.
We spent some time retaking single arm scans with Gautam's frequency counting code to confirm the linewidths he measured before his most recent round of code improvements. During this, ETMX was being its old fussy self, costing us gentle realignment time. For the time being, we started actuating on ITMX for single arm locks. Also, out of superstition, I changed the static position offset that had been at +1k for the last N months to -1k.
ETMX broke us out of a few DRFPMI lock trials as well, as did poor SRM alignment. I finally set up dither alignement settings for SRM in DRMI though, which helped (even in the arms-held-off-resonance situation). I still prefer doing the PRM/BS dither alignment in a carrier PRMI lock, because I think the SNR should be better than DRMI.
We know that the ETMX excursions can happen without length drive exciting them, but also that length drives certainly can excite them. For future locks, I'm going to try out avoiding ETMX drive altogether; the sites use a single ETM for their DARM actuation and let the CARM loop take care of the resultant cross coupling, so hopefully we can do the same without angering the mode cleaner.
Anyways, we didn't really ever make it far enough to do anything interested with the DRFPMI tonight
I did some simulations to see if we are susceptible to HOM resonances as we reduce the CARM offset. I restricted my search to HG modes of the Carrier+[-55,-11,0,+11,+55]MHz fields with n+m<6, and used all the real physical parameters I could get ahold of.
In short, as I change the CARM offset, I don't see any stray resonances within 2nm of zero, either in PRFPMI or DRFPMI.
Now, the mode matching in my simulation is not the real mode matching our real interferometer has. Thus, it can't tell us how much power we may see in a given mode, but it can tell us about our susceptibility to different modes. I.e. if we were to have some power in a certain mode coming out of the IMC, or present in the vertex, we can see what it would do in the arms.
Since my simulation has some random amounts of power in each HOM coming into the interferometer, I simply swept the CARM offset and looked for peaks in the power of each mode. Many of the fields exhibited gentle slopes over the range, and we know we ok from 3nm->~100pm, so I made the selection rule that a "peak" must be at least 10 times as big as the minimum value over the whole range, in order to see fields that really do have CARM dependence.
In the following plots, normalized IFO power is plotted and the locations of HOM peaks are indicated with circles; their actual heights are arbitrary, since I don't know our real mode content. However, I'm not really too concerned, since all I see is some -11MHz modes between 2-3nm of full resonance, where we have no problem controlling things... Also, all of the carrier HOMs effectively co-resonate with the 00 mode, which isn't too surprising, and I didn't include these modes in the plots.
Finally, I visually inspected the traces for all of the modes, and didn't really find anything else peeking out.
Code, plots attached.
So, with my last entry, I was guilty of just throwing stuff into the simulation and not thinking about physics... so I retreated to Siegman for some algebraic calculations of the additional Guoy phase accumulated by the HOMs in the arms -> their resonant frequencies -> the arm length offset where they should resonate. Really, this isn't completely precise, as I treated the arms independently, with slightly differing ETM radii of curvature, but I would expect the "CARM Arm" to behave as a sort of average of the two arm cavities in this regard. (EDIT: Also, I didn't really consider the effect of the coupled vertex cavities... so there's more to be done)
The basic idea I used was:
In practice, I threw together a python script to do this all and print out a table. I've highlighted the values within 10nm, but the closet one is 3.8nm
########## X Arm HOM Resonance Locations in nm ##########
Mode Order: 0 , 1 , 2 , 3 , 4 , 5
Carrier : +0, +156.21, -219.58, -63.376, +92.832, +249.04
LSB 11 : +59.563, +215.77, -160.02, -3.8126, +152.4, -223.4
USB 11 : -59.563, +96.645, +252.85, -122.94, +33.269, +189.48
LSB 55 : -234.18, -77.975, +78.233, +234.44, -141.35, +14.857
USB 55 : +234.18, -141.61, +14.6, +170.81, -204.98, -48.776
########## Y Arm HOM Resonance Locations in nm ##########
Carrier : +0, +154.82, -222.35, -67.531, +87.292, +242.11
LSB 11 : +59.313, +214.14, -163.04, -8.218, +146.6, -230.57
USB 11 : -59.313, +95.51, +250.33, -126.84, +27.978, +182.8
LSB 55 : -235.43, -80.611, +74.212, +229.04, -148.14,
USB 55 : +235.43, -141.74, +13.08, +167.9, -209.27, -54.452
I started two scripts, senseDRM and loadDRMImatrixData.m, which Peter will bang on until they're correct. They're in the $SCRIPTS/LSC directory. The first is a perl script which uses TDS tools to drive the DRM optics and measure the response at the double demod photo-detectors, and write these results to a series of files loadable by matlab. The second loads the output from the first script, inverts the resulting sensing matrix to get an input matrix, and spits out a tdswrite command which can be copied and pasted into a terminal to load the new input matrix values.
What's left is mainly in figuring out how to do the matrix inversion properly. Right now the script does not account for the output matrix, the gains in the feedback filters at the measurement frequency, or the fact that we'll likely want the UGF of our loops to be less than the measurement frequency. Peter's going to hash out these details.
We can reliably lock the DRMI with the arms held off on ALS.
I have not been able to hold it at zero CARM offset; but this is probably just a matter of setting up the right loop shapes with enough phase margin to handle the CARM fluctuations ( or figuring out high bandwidth ALS...)
Right now, it's the most stable at CARM offsets larger (in magnitude) than -1. Positive CARM offsets don't work well for some reason.
The key to getting this to work was to futz around, starting from the misaligned arms DRMI settings, until brief locks were seen (triggering all 3 DRMI DoFs on POP22, since the correct AS110 sign was amiguous). I could tell from how the control signals responded to gain changes that REFL165Q, which was being used as the MICH error signal, was seeing significant cross coupling from both PRCL and SRCL, suggesting the demod angle of REFL165 had to be adjusted. I randomly tweaked the REFL165 demod angle until a 20 second lock was achieved, with excitations running. Then, I downloaded that data and analyzed the sensing matrix. This showed me that the REFL33 demod angle was ok, and the PRCL-from-SRCL subtraction factor determined with the arms misaligned was still valid. The main difference was indeed the SRCL angle in REFL165.
With the REFL165 demod angle properly adjusted, the DRMI would briefly lock, but the DRMI had become somewhat misaligned at this point, and the SRC could be seen to mode hop. Interestingly, the higer order modes had an opposite sign in AS110, with respect to the TM00. At that point, I went back to PRMI on carrier to dither-align the BS and PRM.
With alignment set, the DRMI would lock on TM00 readily, still only triggering on POP22. I set the AS110 angle, and moved SRCL triggering over to that, which sped up acquisition even more. The input matrix and FM gains from no-arms DRMI still work for acquistion; UGF servos were used to adjust overall gains a bit.
At CARM offsets larger in magnitude than -1, the DRMI lock seems indefinite. I just broke it to see how fast it would acquire; 3 seconds.
Lastly, here is the sensing matrix at CARM offset of -4, measured over five minutes. REFL11 is the only degenerate looking PD. Thus, I feel like controlling the DRMI of the DRFPMI should be more managable than I had feared.
(I didn't include/excite CARM or DARM, because I'm not sure it would really mean anything at such a large CARM offset)
Looking good. How many meters of CARM is '-1 counts'?
The DRMI has been locked!! And at least one time, it was for more than one minute!!
We are not 100% sure yet that it's correctly sideband locked. The test of this was to put a 50% BS in front of the AS camera (so after the beam has gone to AS55), and send the light over to a PDA10CF Thorlabs PD. I locked the Michelson on carrier for the alignment of this diode. Then I strung a cable to the control room, and plugged it into the RF spectrum analyzer. (First, I had turned off the green beat PD power, so there wasn't any RF stuff on the line that I unplugged). It's hard to watch the screen and a tv / dataviewer at the same time, so I've taken a video, so that we can see the nicely locked round DRMI beam on the AS camera, and the spectrum analyzer. My phone is working very hard at uploading the video, but we may have to wait until tomorrow for that. However, I think that we're locked on the 55MHz sideband. (Also, maybe I'm too tired or excited or something, but how do you make the real cameras take video??)
EDIT: Video uploaded. Pause the video at 10 seconds, and you'll see that we've got a strong 110MHz peak!! Hoooray! The TV in the upper right side of the video is AS. You can see as we flash, the peaks go up and down. When there's no resonance, the 110 peak goes away. (Ex., when I'm PRMI locked on the sideband, there isn't a visible peak).
Alignment procedure was as normal: Lock and align the arms. Misalign ETMs. Check that MICH fringes look good (ASS does a nice enough job that I don't actually lock and align the Michelson anymore). Restore the PRM. Lock PRMI. Tweak PRM alignment to maximize POP110I. At this point, Koji and I played a little with the PRMI, but when we finished with that, we restored the SRM, and tweaked its alignment by making nice overlap on the AS camera.
Then, we tried some DRMI settings, started seeing some locks, and played a bit with trying to optmize the settings that we have.
PRCL ASC is on (with loop triggering). MICH gain = -0.8, PRCL gain = +0.05. FM4, FM5 always on, FM2 triggered. Loop and filter module triggering on POP22I. No power normalization. MICH and PRCL locked on REFL55 I&Q, with 1's in the LSC input matrix. PRCL actuating on PRM with +1, MICH actuating on BS with +0.5, PRM with -0.267.
I took transfer functions between REFL55 I&Q and REFL11 I&Q, to determine the relative gains and signs. REFL11I's gain should be -18dB relative to REFL55I, with the opposite sign. We tried PRMI locking with MICH = 1*REFL55Q and PRCL = -0.125*REFL11I for the input matrix. Still no power normalization (we haven't used power norm at all today, so I'll quit writing that).
I took transfer functions between REFL55 I&Q and REFL33 I&Q. REFL33I's gain is -8dB relative to REFL55I, but they have the same sign. We tried locking PRMI with MICH = 1*REFL55Q and PRCL = +0.6*REFL33I. Success.
Next up, some Optickle simulations, to help us go in the right direction for DRMI locking. I checked the signs of the error signals REFL55I (PRM sweep), REFL11I (PRM sweep) and REFL55Q (MICH sweep) in both PRMI and DRMI configurations. For all of these cases, the signs were the same (i.e. no sign flips needed to happen for DRMI locking, relative to PRMI locking). I checked the sensing matrices for DRMI and PRMI for those same signals, and took the ratios of the sensing matrix elements. This gave me the ratio of optical gains for each error signal, in the DRMI case vs. PRMI case, so any servo gain changes should be the inverse of these numbers. These numbers are all DRMI/PRMI: REFL55I PRCL response = 0.76, REFL11I PRCL response = 0.99, REFL55Q MICH response = 18. So, when trying to lock the DRMI, we wanted to keep the gains for PRCL about the same, reduce the servo gain for MICH by a factor of ~20, but keep the same signs for everything.
In doing that, we started seeing some short DRMI locks, so we twiddled some parameters (mostly the elements in the LSC input matrix) a bit. We eventually settled on: PRCL = -0.125*REFL11I, MICH = 0.1*REFL55Q, and SRCL = 1.0 * REFL55I. The output matrix was the same (MICH pushing on BS and PRM, PRCL on PRM), with the addition of a +1 in the SRCL -> SRM element. For all 3 degrees of freedom (PRCL, MICH, SRCL), FMs 4 and 5 were always on. For PRCL, FMs 2,3,6 were triggered to come on after 0.5 seconds of delay. The PRCL FM triggers helped enormously. I tried several other things, including changing the MICH input matrix element up and down in value, changing the SRCL input matrix element up and down in value, and engaging triggering for a few different filters in the MICH and SRCL degrees of freedom. However, none of these made things better, and several made things worse. Most notably, for SRCL, engaging triggering for FMs 2 and 3 kicked the cavities out of lock, which implies that perhaps our gain isn't high enough yet (and thus our UGF isn't very high yet). I changed FM1 of SRCL to be +3dB of gain (from +10dB), and it would live through that coming on (trigger delayed by 1 sec, then ramping up over 1 second), but within a second after the filter finishing coming on, the cavity would fall out of lock (not violently kicked, just not locked anymore).
At this point, we were trying to figure out a way to confirm what kind of lock we had. I checked Optickle again, and we do not expect to see a significant change in POP110I between the PRMI and DRMI cases, so that isn't a useful check. We dreamed of having our AS110 demod board, or the AS OSA set up, but neither of those was going to happen tonight. Instead, Koji suggested hooking up the PD, and looking directly at the output.
To-do: Set up the AS OSA. Also, perhaps temporarily borrow the 110 demod board from POP. We were triggering on POP22 tonight, and that seemed to work okay.
Very nice!! I was wondering, shouldn't the driving matrix be such that MICH pushes on SRM as well?
Wonderful ! I like the video -- the spatial mode looks pretty clean and much cleaner than what I observed in the old days.
Hmmm, yes, that's a very good point. I think you're right, and I'll give that a try today.
Don't go for a hacky solution. We want to climb a staircase step by step.
Prepare an independent 110MHz demod ports.
To-do: Set up the AS OSA. Also, perhaps temporarily borrow the 110 demod board from POP. We were triggering on POP22 tonight, and that seemed to work okay.
Friday night locking
Much more stable DRMI lock was achieved, partly thanks to the Friday-night quiet seismic,
and partly because of the improved servo gain and LF boosts
I wanted to confirm the enhancement of the 110MHz signal at the AS port.
As the AS110 PD is placed in the CCD path, there is nothing visible with PRMI.
The Thorlabs PD was moved to the main AS path. Now the AS110 PD is receiving 50% of the power.
With PRMI 110MHz peak was -30dBm (As it was fluctuating, anything more precise number did not make sense)
When the DRMI was locked, the peak was enhanced to 0dBm.
The 2f signal comes from the beat between the sidebands.
Thus the amplitude of the intensity is proportional to the power of the sidebands (assuming the +1 and -1 order sidebands have the same amplitude)
-30dBm -> 0dBm means 31.6 times amplitude of the intensity. Therefore the amplitude transmission of the sidebands is 5.6 times more. (Is this true?)
According to the wiki, the AS port thru-put (i.e. power transmission) for the 55MHz sideband is 0.0026 and 0.43 for PRMI and DRMI respectively.
This corresponds to the amplitude difference of ~13. So we still have only half of the sidebands leaking out from the IFO. This could be attributed
to both the smaller PR gain and SR gain.
Same as the one Jenne used the other day. Later I engaged several additional triggers.
The following is the trigger setting I used
MICH: Delay 2 sec, FM1/FM2/FM3/FM6/FM7
PRCL: Delay 0.5 sec, FM2/FM3/FM6
SRCL: Delay 5 sec, FM1/FM2/FM3/FM6
SRCL FM1 was modified from +3dB to +6dB
Once lock is acquired, it lasts tens of minutes. (see the attached striptool chart.)
Even the lock is lost, it reacquires quickly.
The videos to show the lock acquisition and the in-lock stability are attached below.
The AS port beam is very round. It is not so shaky, but some yaw motion is visible.
The mode at the AS port is defined by the SRM, putting a QPD at the AS port would help to
stabilize the spot.
IFO state upon leaving
I left the 40m with the arms aligned, PRM and SRM slightly misaligned, and LSC setting is for the DRMI locking.
- AS110I/Q for triggering
- PRCL/MICH/SRCL normalization
- We should resurrect the IFO config scripts.
- Remove BS->SRCL actuation coupling
- Handing off to 3f signals (preparation for the full lock)
- Improve ALS stability
- SRM ASC: AS QPD for SRM control
Lock Acquisition Video
UL (REFL) / UR (POP)
LL (AS) / LR (PRM Face)
UL (REFL) / UR (POP)
LL (AS) / LR (PRM Face)
We can put our scripts for the MICH, PRMI, and DRMI into the IFO CONFIGURE screens for now and then it should be easy to get them into the Guardian once Jamie has the bugs worked out.
This screen can also be used to setup and start the dither alignment for each configuration (once we have one working for DRMI / SRM).
Also, now that the notches/bandstop filters for the violin modes have been move from the SUS into the LSC, we should fix the triggering to engage them a few seconds after the boosts.
I spent this weekend doing a more careful investigation of the DRMI noise. I think I have some new information/insights. Attachment #1 is the noise budget (png attached because pdf takes forever to upload, probably some ImageMagick problem. The last attachment is a tarball of the PDF). Long elog, so here are the Highlights:
The DAC noise is not limiting us anywhere when the coil de-whitening is switched on.
So I don't understand the measured Dark Noise level, and it is limiting us at frequencies > 200Hz. Some busted electronics in the input signal chain? Or can the LSC demod daughter board gain of ~5 explain the observed noise?
Edit 1730 9 Oct: I had missed out the factor of 5 gain in the demod board in calculating the shot noise curve. Attachment #7 shows the corrected shot noise level. Explicitly:
, where is to convert shot noise in W to displacement units.
This seems to be limiting us from saturating the dark noise once the coil de-whitening is engaged. But lack of coherence means the mechanism is not re-injection of SRCL/PRCL sensing noise? Need to think about what this means / how we can mitigate it.
I've also made several changes to the NB code - will push to git once I finish cleaning stuff up, but it is now much faster to make these plots and see what's what.
My last characterization of the AS55 PD was on Feb 2013. ELOG 8100
There I said the dark noise at the PD output was 16nV/rtHz. I don't have the measurement of the Voltage noise at the output of the demod board.
Note that the PD can only be limited by shot noise when the DC current is larger then 4mA.
Some days ago, I had tried to measure the SRCL->MICH and PRCL->MICH cross couplings using broadband noise injected between 120-180 Hz, a frequency band chosen arbitrarily, in hindsight, I could have done a more broadband test. I've spent some time including the infrastructure to calculate "White-Noise TFs" in the noise budgeting code, where a transfer function is estimated by injecting a "broadband" excitation into a channel of interest, and looking at the resulting response in MICH. I figured this would be useful to estimate other couplings as well, e.g. laser intensity nosie, oscillator noise etc.
I estimate the transfer function of the coupling using the relation (MICH is the median ASD of the MICH error signal in the below expression, and similarly for PRCL)
Attachments #1 and #2 show the spectra of the MICH, PRCL and SRCL signals during 'quiet' times and during the injection, while Attachment #3 shows the calculated coupling TFs using the above relation. These are significantly different (more than 10dB lower) than the numbers I reported in elog 13367, where the measurement was made using swept sine. As can be seen in the attached plots, the injected broadband excitation is visible above the nominal noise level, and I calculated the white noise TFs using ~5mins of data which should be plenty, so I'm not sure atm what to make of the answers from swept-sine and broadband injections being so different.
Attachment #4 shows the noise budget from the October 8 DRMI lock with the updated SRCL->MICH and PRCL->MICH couplings (assumed flat, extrapolated from Attachment #2 in the 120-180Hz band). If these updated coupling numbers are to be believed, then there is still some unexplained noise around 100Hz before we hit the PD dark noise. To be investigated. But if Attachment #4 is to be believed, it is not surprising that there isn't significant coherence between SRCL/PRCL and MICH around 100Hz.
Nov 8 1600: Updating NB to inculde estimated Oplev A2L.
why no oplev trace in the NB ?
#4 shows the noise budget from the October 8 DRMI lock with the updated SRCL->MICH and PRCL->MICH couplings (assumed flat, extrapolated from Attachment #2 in the 120-180Hz band). If these updated coupling numbers are to be believed, then there is still some unexplained noise around 100Hz before we hit the PD dark noise. To be investigated. But if Attachment #4 is to be believed, it is not surprising that there isn't significant coherence between SRCL/PRCL and MICH around 100Hz
also, this method would work better if we had a median averaging python PSD instead of mean averaging as in Welch's method.
The Oplev trace is missing for now, as I have not re-measured the A2L coupling since modifying the Oplev loop shape (specifically the low pass filter and overall gain) to allow engageing the coil de-whitening.
The averaging for the white noise TFs plotted is computed using median averaging - I have used a python transcription of Sujan's matlab code. I use scipy.signal.spectrogram to compute the fft bins (I've set some defaults like 8s fft length and a tukey window), and then take the median average using np.median(). I've also incorporated the ln(2) correction factor.
It seems like GwPy has some in-built capability to compute median (and indeed various other percentile) averages, but since we aren't using it, I just coded this up.
After the ISS work, I aligned the IFO and confirmed that DRMI locks with good SPOB and AS166 values.