I have changed all of the oplevs and transmon QPDs to use the common ISC QPD library block, which differs mainly in its divide by zero protection.
c1scx.mdl and c1scy.mdl were directly changed for the transmon QPDs. The oplevs were done by changing the sus_single_control.mdl library part, which is used for all of the SOSs.
Then, because of the underscore introduced (i.e. OLPIT becomes OL_PIT because there is an OL block), I went on a sed safari to find and replace the new channel names into:
I've fixed everything that occured to me, and the usual ways I'm used to interacting with the oplevs all seem to work at this time, but it's entirely possible I've overlooked something.
One important note is: because we are now using an effectively immutable QPD library block, the oplev urad conversion has to take place in the DoF matrix. The EPICS records C1:SUS-[OPTIC]_OL_[DOF]_CALIB still exist, but do not multiply the fast signals. Rather, the OL_MTRX elements are multiples of the CALIB value. I thought about making a new QPD_CALIBRATED part or something, but then we're right back to using custom code, which is what we're trying to avoid.
All of the oplev DoFs are stable, I checked a few loop TFs like ETMY pitch and PRM yaw, and they looked normal.
In an effort to ease the IO load on the framebuilder, I've cleaned up the DQ channels being written to disk. The biggest impact was seven 64kHz channels being written to disk, on ADC channels corresponding to microphones.
The frame files have gone from 75MB to 57MB.
I noticed some diagnostic bits in the c1sus IOP complaining about user application timing and FIFO under/overflow (The second and fourth squares next to the DACs on the GDS screen.) Over in crackle-cymac land, I've seen this correlate with large excess DAC noise. After restarting all models, all but one of these is green again, and the optics are now all damped.
It seems there were some fishy BURT restores, as I found the TT control filters had their inputs and outputs switched off. Some ASS filters were found this way too. More undesired settings may still lurk in the mists...
The interferometer is now realigned, arms locked.
I've been able to get all models running. Most optics are damped, but I'm having trouble with the ITMs, BS and PRM.
The frontends have some paths NFS-mounted from fb. fb is on the ragged edge of being I/O bound. I'd suggest moving those mounts to chiara. I tried increasing the number of NFS threads on fb (undoing the configuration change I'd previously made here) and it seems to help with EPICS smoothness -- although there are still occasional temporal anomalies in the time channels. The daqd flakiness (which was what led me to throttle NFS on fb in the first place) may now recur as well.
At about 10AM, the C1LSC frontend stopped reporting any EPICS information. The arms were locked at the time, and remained so for some hours, until I noticed the totally whited-out MEDM screens. The machine would respond to pings, but did not respond to ssh, so we had to manually reboot.
Soon thereafter, we had a global 15min EPICS freeze, and have been in a weird state ever since. Epics has come back (and frozen again), but the fast frontends are still wonky, even when EPICS is not frozen. Intermittantly, the status blinkers and GPS time EPICS values will freeze for multiple seconds at a time, sporadically updating. Looking at a StripTool trace of an IOPs GPS time value shows a line with smooth portions for about 30 seconds, about 2 minutes apart. Between this is totally jagged step function behavior. C1LSC needed to be power cycled again; trying to restart the models is tough, because the EPICS slowdown makes it hard to hit the BURT button, as is needed for the model to start without crashing.
The DAQ network switch, and martian switch inside were power cycled, to little effect. I'm not sure how to diagnose network issues with the frontends. Using iperf, I am able to show hundreds of Mbit/s bandwidth betweem the control room machines and the frontends, but their EPICS is still totally wonky.
What can we do???
We tried several times tonight to engage the Fool path with the PRFPMI. No success.
First, we locked the arms on ALS, in CARM/DARM mode, and measured the cancellation ability, to make sure that the filter shape and gain was set correctly. For the PRFPMI, it was okay using the same shape as the single arm case, but the gain was +20.0. There might be a bit more cancellation to be gained if we adjust the shape at the ~1dB level, but we're already able to get 20dB of cancellation, so we decided that would be enough to give things a try. To get this much cancellation, we set the phase tracker loops to both have 2kHz UGFs, almost exactly. We should implement a UGF servo, or the amplitude method version of that as Koji suggested ages ago, so that the phase tracker is always at the same place.
I don't think that REFL 11 is seeing as much CARM as I expect. We ended up switching over to linearized REFL55 for our attempts. When we're close to zero CARM offset, the arms are constantly flashing through resonance, and we get the loud buzzing. REFL11 doesn't seem to see any of this, even though we should be close enough to see some PDH action. REFL55 does change as we get closer to resonance, so I think it's seeing some real CARM stuff.
We tried engaging the Fool, but I don't think it did anything too useful. We need to make an estimate of what we expect our gain of the REFL loop to be - or at least the sign.
The PRMI is still not stable enough. It keeps falling out of lock when we get to high-ish arm powers. Not good. More brain power tomorrow on the modulation cancellation issue.
Perhaps if things are stable at moderate arm powers, we can use an excitation to line up the ALS vs. REFL error signals, and then watch the noises of them change as we move around in CARM offset. This should tell us when the linearized REFL signal is quiet enough that it's worth triggering and trying to transfer over.
The last lockloss tonight, there was something funny going on, that we can't explain. Even though both arms were locked on the CARM/DARM combined ALS signals, beatx doesn't see the giant oscillation that causes carm to lose lock until much later. Fool was trying to do something, but that should affect both als individal signals in the same way. Mystery.
X end QPD has recieved 0.2+0.4 absorptive ND filters. Y end QPD got one at 0.6. This appears to have mitigated the saturations for now; the unwhitened signals no longer go negative. The digital gains have been reset.
Koji raised a good question about the step response I wrote about. Namely, if the UGF of the ALS servo is around 100Hz, we would expect it to settle with a characteristic time on the order of tens of milliseconds, not seconds, as was seen in the plot I posted.
I claim that the reason for the slow response was the fact that the feedforward FM stayed on after the kick, despite the MC filter bank being triggered off. Since it has filters that look like a oscillator at 1Hz, the ringdown or exponential decay of this filter's output in response to the large impulsive output of the PDH control signal just before being triggered down would slowly push the ALS error signal around through the feedforward path.
Given this reasoning, this should be helped by adding output triggering to the FF filter that uses the MC trigger matrix row, as I wanted to do anyways. I have now added this into the LSC model (as well as DQ at 2kHz for the MC_CTRL_FF_OUT), and the impulse response is indeed much quicker.
In the following plot, I hit ETMY with a five sample, 5000 amplitude, impulse (rather than a step, as I did yesterday). The system comes back to PDH lock after ~40ms.
I'm playing around with the lastest ALS fool feedforward on the Yarm, and I like what I'm seeing.
First, I verified that I could reproduce the TF shapes in ELOG 11041, which I was able to do with a gain of +9.3 and FMs 5 and 6 in the FF module.
Then, I locked the arm on ALS with full bandwidth, and on POY with the settings currently used the MC module, and took their spectra as references. (I put an excitation on the arm at 443Hz to line them up to the same arbitrary units.)
Then, with ALS at its usual 100Hz UGF and boosts on, the Fool path on, and the MC FM set to trigger on/off at 0.8/0.5, I slowly brought ALS towards zero offset and saw it pop right into resonance. I then manually triggered the PDH boosts.
Here are some spectra, showing that, with the Fool path on:
Once the PDH loop is running, the ALS loop can be switched out at the CARM FM output without much of an effect beyond a small kick.
However, looking at the loop shapes, maybe I got lucky here. I took the usual injection TFs at the MC FM, the CARM FM, and at ETMY, to get the overall OLG; all of them have >0.9 coherence pretty much everywhere except the first two points.
As desired, the PDH loop looks pretty normal.
I have no intuition about how the fooled CARM loop should look, since this is even more complicated than a two-loop system.
I don't currently know what is causing the odd feature in the overall at ~50Hz, and it spooked me out when I saw the multiple UGF crossings. The only thing I could think of happening there is the pole in the ALS phase tracker boost. I turned it off, and remeasured; the feature persists...
To wrap it up, here's something I think is pretty cool. Here's what happens when I give ETMY a 1000 count position step impulse (no ramp). [Here, CARM is on ALS with G=12, but only FM5 on]
Although the arm was controlled with IR before the kick, ALS maintained control. As soon as ALS brought the arm back towards resonance, the PDH loop picked it right back up.
Some random notes:
DTT data is attached, in case it's useful to anyone!
The modulation setting was reverted.
Demod phase for REFL11/33/55/165 and AS55 were reverted to the previous numbers too.
For tonight's experiment, I re-installed the delay line cable and changed the attenuation to 10dB for the 55MHz modulation.
I quickly locked the PLL and checked that the modulation is the ratio of the field strength between the worst (19ns) and best
case (28ns) is 31dB, that is ~35 times reduction.
Here is an updated cartoon, with the ALS sensor explicitly shown as the beatbox times the closed loop response of the phase tracker servo.
The most important transfer functions are written on the diagram. Others can be extracted from the attached Mathematica file (which corresponds to this diagram).
I re-did the Mathematica notebook according to the most current diagram (note to daytime self: attach .nb file!!!), and found that the denominator has changed, such that plugging in the new D=-A_refl*P_als*S_als gives the same
full-system closed loop gain of
where is the open loop gain, and the * indicates either the REFL or ALS portions of the system.
I have also plotted some things with Matlab, although I'm a little confused, and my daytime self needs to spend some more time thinking about this.
In the actuators (both for REFL and ALS), I include a pendulum, the digital anti-imaging filters that let us go from the 16kHz model to the 64kHz IOP and the analog anti-imaging filters after the DAC. Note to self: still need to include violin filters here.
For the servo gains, I copy the filters that we are using from Foton, and give them the same overall gain multiplier that is in the filter bank. For the ALS going through the CARM filter bank, this is FMs 1, 2, 3, 5, 6 with a gain of 15. For the RF (actually, POY here) going through the MC filter bank, this is FMs 4, 5, 7 with a gain of 0.08.
For the plants of each system, since this is still single arm lock, I just include a cavity pole (80kHz for ALS, 18kHz for REFL).
In the sensors (both for REFL and ALS), I include the analog anti-aliasing as well as the digital anti-aliasing to allow us to go from the 64kHz IOP to the 16kHz front end system. For the ALS I also include in the sensor the closed loop response of the phase tracker loop (H/(1-H), where H is the open loop gain of the phase tracker). For both sensors, I also include a semi-arbitrary number to make the full single-loop open loop gain have a UGF of 200Hz. In the ALS sensor, I also include a minus sign to make the full open loop gain have the correct phase.
Here I plot the open loop gains of the individual single loops, as well as the open loop gain of the full system (Hals + Hrefl - Hals*Hrefl). I feel like I must be missing a minus sign in my ALS loop, but I don't know where, and my nighttime brain doesn't want to just throw in minus signs without knowing why. That will affect how the final ALSfool (blue trace) looks, so maybe it's not really as crazy as it looks right now.
Also, I was trying to explain to myself why we are getting the shape that we are in our measurements of the cancellation (http://nodus.ligo.caltech.edu:8080/40m/11041). But, I can't. Below are the plots of the transfer functions from either point 9 or 10 (before or after the G_refl) to point 5, which is the ALS error point. The measurement in elog 11041 should correspond to the blue trace here. For these traces, the decoupling is set to just (-A_refl), although there aren't any noticeable changes in the shape if I just set D=0. If we start with the assumption that D=0, the shape and magnitude are basically identical to this plot, and then as we make D=-A_refl P_als S_als, the transfer functions both go to zero.
So. Why is it that with no decoupling, the transfer function from 10 to 5 is tiny? Why do the shapes plotted below look nothing at all like the measured cancellation shape? Daytime brain needs to think some more.
The cancellation went from ~10 dB to ~30 dB. This seems good enough. The new filter 'Comp1' is just constructed by eye. We then had to tune the filter module gain to a few %. Seems good enough for now, but we should really try to understand what it is and why it is the way that it is. In the above plot, the ORANGE trace is the old cancellation and the GREEN one is the new one. The filter TF is attached below - its not special, we made it by presing buttons in FOTON until the TF matched the measured TF of ALSY/LSC-MC_CTRL_FF_OUT.
Following this entry, I have made the same change in the controls account on rossa:
In the ~/.grace/gracerc file (create one if it doesn't exist), put in a line which reads:
PAGE LAYOUT FREE
Now we can scale our dataviewer live and playback plots by stretching the window with our mouse. The attached screenshot shows how I filled up one of the vertical monitors with a DV window for arm locking.
Dang it, yes. You're right. I should have caught that.
Since Dcpl and Srefl are both zero during the measurement (since it was an ALS lock), this is actually
So, I need to remove the effect of the ALS closed loop, to get the actual quantity I was looking for.
Wonkey shape: Looks like a loop supression. Your http://nodus.ligo.caltech.edu:8080/40m/11016 also suggests it too, doesn't it?
I have measured very, very carefully the transfer function from pushing on MC2 to the Yarm ALS beatnote. In the newest loop diagram in http://nodus.ligo.caltech.edu:8080/40m/11030, this is pushing at point 10 and sensing at point 4.
Since it's a bunch of different transfer functions (to get the high coherence that we need for good cancellation to be possible), I attach my Matlab figure that includes only the useful data points. I put a coherence cutoff of 0.99, so that (assuming the fit were perfect, which it won't be), we would be able to get a maximum cancellation of a factor of 100.
This plot also includes the vectfit to the data, which you can see is pretty good, although I need to separately plot the residuals (since the magnitude data is so small, the residuals for the mag don't show up in the auto plot that vectfit gives).
If you recall from http://nodus.ligo.caltech.edu:8080/40m/11020, we are expecting this transfer function to consist of the suspension actuator (pendulum with complex pole pair around 1Hz), the ALS plant (single pole at 80kHz) and the ALS sensor shape (the phase tracker is an integrator, with a boost consisting of a zero at 666Hz and a pole at 55Hz). That expected transfer function does not multiply up to give me this wonky shape. Brain power is needed here.
Just in case you were wondering if this depends on the actuator used (ETM vs MC2), or IFO configuration (single arm vs. PRFPMI), it doesn't. The only discrepancy between these transfer functions is the expected sign flip between the MC2 and ETMY actuators. So, they're all pretty consistent.
Before locking the PRFPMI, I copied the boost filter (666:55) from the YARM ALS over to Xarm ALS, so now both arms have the same boost.
Things to do for ALSfool:
Based on the measured modulation profiles, the depth of each modulation was estimated.
Least square sum minimization of the relative error was used for the cost function.
-8th, -12th~-14th, n=>7th are not included in the estimation for the nominal case.
-7th~-9th, -11th~-15th, n=>7th are not included in the estimation for the 3f reduced case.
m_f1 = 0.194
m_f2 = 0.234
theta_f1f2 = 41.35deg
m_IMC = 0.00153
m_f1 = 0.191
m_f2 = 0.0579
theta_f1f2 = 180deg
m_IMC = 0.00149
(Sorry! There is no error bars. The data have too few statistics...)
This KTP crystal has the maximum allowed RF power of 10W (=32Vpk) and V_pi = 230V. This corresponds to the maximum allowed
modulation depth of 32*Pi/230 = 0.44. So we probably can achieve gamma_1 of ~0.4 and gamma_2 of ~0.13. That's not x3 but x2,
so sounds not too bad.
Then Kiwamu's triple resonant circuit LIGO-G1000297-v1 actually shows the modulation up to ~0.7. Therefore it is purely an issue
how to deliver sufficient modulation power. (In fact his measurement shows some nonlinearity above the modulation depth of ~0.4
so we should keep the maximum power consumption of 10W at the crystal)
This means that we need to review our RF system (again!)
- Review infamous crazy attn/amp combinations in the frequency generation box.
- Use Teledyne Cougar ampilfier (A2CP2596) right before the triple resonant box. This should be installed closely to the triple resonant box in order to
minimize the effects of the reflection due to imperferct impedance matching.
- Review and refine the triple resonant circuit - it's not built on a PCB but on a universal board. I think that we don't need triple
resonance, but double is OK as the 29.5MHz signal is small.
We want +28V supply at 1X1 for the Teledyne amp and the AOM driver. Do we have any unused Sorensen?
I wonder if DRMI can be locked on 3f using this lower 55 MHz modulation depth. It seems that PRMI should be unaffected, but that the 3*f2 signals for SRCL will be too puny. Is it really possible to scale up the overall modulation depths by 3x to compensate for this?
3f modulation cancellation theory http://nodus.ligo.caltech.edu:8080/40m/11005
3f modulation cancellation adjustment setup http://nodus.ligo.caltech.edu:8080/40m/11029
Receipe for the 3f modulation cancellation http://nodus.ligo.caltech.edu:8080/40m/11032
Modulation depth analysis http://nodus.ligo.caltech.edu:8080/40m/11036
When I finished my measurements, the modulation setup was reverted to the conventional one.
If someone wants to use the 3f cancellation setting, it can be done along with this HOW-TO.
The 3f cancellation can be realized by adding a carefully adjusted delay line and attenuation for the 55MHz modulation
on the frequency generation box at the 1X2 rack. Here is the procedure:
1) Turn off the frequency generation box
There is a toggle switch at the rear of the unit. It's better to turn it off before any cable action.
The outputs of the frequency generation box are high in general. We don't want to operate
the amplifiers without proper impedance matching in any occasion.
2) Remove the small SMA cable between 55MHz out and 55MHz in (Left arrow in the attachment 1).
According to the photo by Alberto (svn: /docs/upgrade08/RFsystem/frequencyGenerationBox/photos/DSC_2410.JPG),
this 55MHz out is the output of the frequency multiplier. The 55MHz in is the input for the amplifier stages.
Therefore, the cable length between these two connectors changes the relative phase between the modulations at 11MHz and 55MHz.
3) Add a delay line box with cables (Attachment 2).
Connect the cables from the delay line box to the 55MHz in/out connectors. I used 1.5m BNC cables.
The delay line box was set to have 28ns delay.
4) Set the attenuation of the 55MHz EOM drive (Right arrow in the attachment 1) to be 10dB.
Rotate the attenuation for 55MHz EOM from 0dB nominal to 10dB.
5) Turn on the frequency modulation box
For reference, the 3rd attachment shows the characteristics of the delay line cable/box combo when the 3f modualtion reduction
was realized. It had 1.37dB attenuation and +124deg phase shift. This phase change corresponds to the time delay of 48ns.
Note that the response of a short cable used for the measurement has been calibrated out using the CAL function of the network analyzer.
- PD response [Attachment 1]
The AUX laser temperature was swept along with the note by Annalisa [http://nodus.ligo.caltech.edu:8080/40m/8369]
It is easier to observe the beat note by closing the PSL shutter as the MC locking yields more fluctuation of the PSL
laser freuqency at low frequency. Once I got the beat note and maximized it, I immediately noticed that the PD response
is not flat. For the next trial, we should use Newfocus 1611. For the measurement today, I decided to characterize the
response by sweeping the beat frequency and use the MAXHOLD function of the spectrum analyzer.
The measured and modelled response of the PD are shown in the attachment 1. It has non-intuitive shape.
Therefore the response is first modelled by two complex pole pair at 127.5MHz with Q of 1, and then the residual was
empirically fitted with 29th polynomial of f.
- Modulation profile of the nominal setting [Attachment 2]
Now the spectrum of the PD output was measured. This is a stiched data of the spectrum between 1~101MHz and 99~199MHz
that was almost simultaneously measured (i.e. Display 1 and Display 2). The IF bandwidth was 1kHz. The PD response correction
described above was applied.
It obviously had the peaks associated with our main modulations. In addition, there are more peaks seen.
The attachment 2 breaks down what is causing the peaks.
From the measured peak height, we are able to estimate the modulation depths for 11MHz, 55MHz, IMC modulations, as well as
the relative phase of the 11MHz and 55MHz modulation. (It is not yet done).
- 3f modulation reduction [Attachment 3]
Now, the redcution of the 3f modulation was tried. The measured modulation levels for the 11MHz and 55MHz were almost the same.
The calculation predicts that the modulation for the 55MHz needs to be 1/3 of the 11MHz one. Therefore the attenuation of 9dB and 10dB
of the modulation attenuation knob at the frequency generation box were tried.
To give the variable delay time in the 55MHz line, EG&G ORTEC delay line unit was used. This allows us to change the delay time from
0ns to 63.5ns with the resolution of 0.5ns. The frequency of 55MHz yields a phase sensitivity of ~20deg/ns (360deg/18ns).
Therefore we can adjust the phase with the precision of 10deg over 1275deg.
The 3rd-order peak at 61.8MHz was observed with measurement span of 1kHz with very narrow BW like 30Hz(? not so sure). The delay
time was swept while measuring the peak height each time. For both the atteuation, the peak height clearly showed the repeatitive dependence
with the period of 18ns, and the 10dB case gave the better result. The difference between the best (1.24e-7 Vpk) and the worst (2.63e-6 Vpk)
was more than a factor of 20. The 3rd-order peak in the above broadband spectrum measurement was 6.38e-6 Vpk. Considering the attenuation
of the 55MHz modulation by 10dB, we were at the exact unluck phase difference. The improvement expected from the 3f reduction (in the 33MHz signal)
will be about 50, assuming there is no other coupling mechanism from CARM to REFL33.
I decided to declare the best setting is "10dB attenuation & 28ns delay".
- Resulting modulation profile [Attachment 4]
As a confirmation, the modulation profie was measured as done before the adjustment.
It is clear that the 3rd-order modulation was buried in the floor noise. 10dB attenuation of the 55MHz modulation yields corresponding reduction of the sidebands.
This will impact the signal quality for the 55MHz series error signals, particularly 165MHz ones. We should consider to install the Teledyne Cougar amplifier
next to the EOM so that we can increase the over all modulation depth.
The ALS fool scheme is now diagrammed up in OmniGraffle, including its new official icon. The mathematica notebook has not yet been updated.
EDIT, JCD, 17Feb2015: Updated cartoon and calculation: http://220.127.116.11:8080/40m/11043
Right before the PSL beam goes into the vacuum chamber, it goes through an AR-wedged plate.
This AR plate produces two beams. One of them is for the IO beam angle/position monitor.
And the other was usually dumped. I decided to use this beam.
A G&H mirror reflects the beam towards the edge of the table.
A 45deg HR mirror brings this beam to the beat set up at the south side of the table.
This beam is S-polarlized as it directly comes from the EOM.
The beam from the PSL goes through a HWP and some matching lenses before the combining beam splitter (50% 45deg P).
The AUX laser beam is attenuated by a HWP and a PBS. The transmitted beam from the PBS is supposed
to have P-polarization. The beam alignment is usually done at the PSL beam side.
The combined beam is steered by a HR mirror and introduced to Thorlabs PDA10CF. As the PD has small diameter
of 0.5mm, the beam needed to be focused by a strong lens.
After careful adjustment of the beam mode matching, polarization, and alignment, the beatnote was ~1Vpp for 2.5Vdc.
In the end, I reduced the AUX laser power such that the beat amplitude went down to ~0.18Vpp (-11dBm at the PD,
-18dBm at the mixer, -27dBm at the spectrum analyzer) in order to minimize nonlinearity of the RF system and
in order that the spectrum analyzer didn't need input attenuation.
The PD signal is mixed with a local oscillator signal at 95MHz, and then used to lock the PLL loop.
The PLL loop allows us to observe the peaks with more integration time, and thus with a better signal-to-noise ratio.
The signal from the PD output goes through a DC block, then 6dB attenuator. This attenuator is added to damp reflection
and distortion between the PD and the mixer. When the PLL is locked, the dominant signal is the one at 95MHz. Without this attenuator,
this strong 95MHz signal cause harmonic distortions like 190MHz. As a result, it causes series of spurious peaks at 190MHz +/- n* 11MHz.
10dB coupler is used to peep the PD signal without much disturbing the main line. Considering we have 6dB attanuator,
we can use this coupler output for the PLL and can use the main line for the RF monitor, next time.
The mixer takes the PD signal and the LO signal from Marconi. Marconi is set to have +7dBm output at 95MHz.
FOr the image rejection, SLP1.9 was used. The minicirsuit filters have high-Z at the stop band, we need a 50Ohm temrinator
between the mixer and the LPF.
The error signal from the LPF is fed to SR560 (G=+500, 1Hz 1st-order LPF). I still don't understand why I had to use a LPF
for the locking. As the NPRO PZT is a frequency actuator, and the PLL is sensitive to the phase, we are supposed to use
a flat response for PLL locking. But it didn't work. Once we check the open loop TF of the system, it will become obvious (but I didn't).
The actuation signal is fed to the fast PZT input of the AUX NPRO laser.
[SUCCESS] The 3f sideband cancellation seemed worked nicely.
- Beat effeciency improved: ~30% contrast (no need for amplification)
- PLL locked
- 3f modulation sideband was seen
- The attenuation of the 55MHz modulation and the delay time between the modulation source was adjusted to
have maximum reduction of the 3f sidebands as much as allowed in the setup. This adjustment has been done
at the frequency generation box at 1X2 rack.
- The measurement and receipe for the sideband cancellation come later.
- This means that I jiggled the modulation setup at 1X2 rack. Now the modulation setup was reverted to the original,
but just be careful to any change of the sensing behavior.
- The RF analyzer was returned to the control room.
- The HEPA speed was reduced from 100% (during the action on the table) to 40%.
The RF analyzer was returned to the control room. There are two beat notes from X/Y confirmed.
I locked the arms and aligned them with ASS.
When the end greens are locked at TEM00, X/Y beat amplitudes were ~33dBm and ~17dBm. respectively.
I don't judge if they are OK or not, as I don't recall the nominal values.
As Koji found one of the spare channels of the ALS/FOL RF amplifier box nonfunctional yesterday, I pulled it out to fix it. I found that one of the sma cables did not conduct.
It was replaced with a new cable from Koji. Also, I rearranged the ports to be consistent across the box, and re-labeled with the gains I observed.
It has been reinstalled, and the Y frequency counter that is using one of the channels shows a steady beat freq.
I cannot test the amplitude of the green X beat at this time, as Koji is on the PSL table with the PSL shutter closed, and is using the control room spectrum analyzer. However, the dataviewer trace for the fine_phase_out_Hz looks like free swinging cavity motion, so its probably ok.
Depends on the plots of the whitening I guess; if its low freq sat, then we lower the light level with ND filters. If its happening above 10 Hz, then we switch off the whitening.
Went to zero CARM offset on ALS; transmission QPDs are still saturating :(
Maybe we need to switch off all whitening.
I first updated the DCC branches for the Xend and Yend to reflect the as-built situation from December 2014, and then I updated the drawings after Q's modifications today.
I have re-enabled the second whitening stage switching on each quadrant of each end's QPD whitening board, to try and avoid saturations at full power. Looking at the spectra while single arm locked, I confirmed that the FM2 whitening switch works as expected. FM1 should be left on, as it is still hard-wired to whiten.
The oscillations in the Y QPD still exist. Jenne is updating the schematics on the DCC.
We wanted to jump right in and see if we were ready to try the new "ALS fool" loop decoupling scheme, so we spent some time with CARM and DARM at "0" offset, held on ALS, with PRMI locked on REFL33I&Q (no offsets). Spoiler alert: we weren't ready for the jump.
The REFL11 and AS55 PDs had 0dB analog whitening, which means that we weren't well-matching our noise levels between the PD noise and the ADC noise. The photodiodes have something of the order nanovolt level noise, while the ADC has something of the order microvolt level noise. So, we expect to need an analog gain of 1000 somewhere, to make these match up. Anyhow, we have set both REFL11 and AS55 to 18dB gain.
On a related note, it seems not so great for the POX and POY ADC channels to be constantly saturated when we have some recycling gain, so we turned their analog gains down from 45dB to 0dB. After we finished with full IFO locking, they were returned to their nominal 45dB levels.
We also checked the REFL33 demod phase at a variety of CARM offsets, and we see that perhaps it changes by one or two degrees for optimal rotation, but it's not changing drastically. So, we can set the REFL33 demod phase at large CARM offset, and trust it at small CARM offset.
We then had a look at the transmon QPD inputs (before the dewhitening) for each quadrant. They are super-duper saturating, which is not so excellent.
We think that we want to undo the permanently-on whitening situation. We want to make the second stage of whitening back to being switchable. This means taking out the little u-shaped wires that are pulling the logic input of the switches to ground. We think that we should be okay with one always on, and one switchable. After the modification, we must check to make sure that the switching behaves as expected. Also, I need to figure out what the current situation is for the end QPDs, and make sure that the DCC document tree matches reality. In particular, the Yend DCC leaf doesn't include the gain changes, and the Xend leaf which does show those changes has the wrong value for the gain resistor.
After this, we started re-looking at the single arm cancellation, as Rana elogged about separately.
In the drawing, the FF path should actually be summed in after the Phase Tracker (i.e. after S_ALS). This means that the slow response of the phase tracker needs to be taken into account in the FF cancellation filter. i.e. D = -A_REFL * P_ALS * S_ALS. Since the Phase Tracker is a 1/f loop with a 1 kHz UGF, at 100 Hz, we can only get a cancellation factor of ~10.
So, tonight we added a 666:55 boost filter into the phase tracker filter bank. I think this might even make the ALS locking loops less laggy. The boost is made to give us better tracking below ~200 Hz where we want better phase performance in the ALS and more cancellation of the ALS-Fool. If it seems to work out well we can keep it. If it makes ALS more buggy, we can just shut it off.
Its time to take this loop cartoon into OmniGraffle.
- I built another beat setup on the PSL table at the South East side of the table.
- The main beam is not touched, no RF signal is touched, but recognize that I was present at the PSL table.
- The beat note is found. The 3rd order sideband was not seen so far.
- A PLL will be built tomorrow. The amplifier box Manasa made will be inspected tomorrow.
- One of the two beams from the picked-off beam from the main beam line was introduced to the beat setup.
(The other beam is used of for the beam pointing monitors)
There is another laser at that corner and the output from this beam is introduced into the beat setup.
The combined beam is introduced to PDA10CF (~150MHz BW).
- The matching of the beam there is poor. But without much effort I found the beat note.
The PSL laser had 31.33 deg Xtal temp. When the beat was found, the aux laser had the Xtal temp of 40.88.
- I could observe the sidebands easily, with a narrower BW of the RF analizer I could see the sidebands up to the 2nd order.
The 3rd order was not seen at all.
- The beat note had the amplitude of about -30dBm. One possibility is to amplify the signal. I wanted to use a spare channel
of the ALS/FOLL amplifier box. But it gave me rather attenuation than any amplification. I'll look at the box tomorrow.
- Also the matching of two beams are not great. The PD also has clipping I guess. These will also be improved tomorrow
- Then the beat note will be locked at a certain frequency using PLL so that we can reduce the measurement BW more.
The filters were already in the damping loops but missing the MC WFS path. I checked that these accurately cover the peaks at 16.5 Hz and 23.90 and 24.06 Hz.
I have modified the LSC trigger matrix screen, as well as the LSC overview screen, to reflect the modifications to the model from yesterday.
Also, I decided that we probably won't ever want to trigger the zero crossing on the Q phase signals of REFL. Instead, we may want to try it out with the single arms, so the zero crossing selection matrix is now REFL11I, REFL55I, POX11I, POY11I, in that order.
EDIT, JCD, 17Feb2015: Updated loop diagram and calculation: http://18.104.22.168:8080/40m/11043
Okay, Koji and I talked (after he talked to Rana), and I re-looked at the original cartoon from when Rana and I were thinking about this the other day.
The original idea was to be able to actuate on the MC frequency (using REFL as the sensor), without affecting the ALS loop. Since actuating on the MC will move the PSL frequency around, we need to tell the ALS error signal how much the PSL moved in order to subtract away this effect. (In reality, it doesn't matter if we're actuating on the MC or the ETMs, but it's easier for me to think about this way around). This means that we want to be able to actuate from point 10 in the diagram, and not feel anything at point 4 in the diagram (diagram from http://22.214.171.124:8080/40m/11011)
This is the same as saying that we wanted the green trace in http://126.96.36.199:8080/40m/11009 to be zero.
So. What is the total TF from 10 to 4?
So, to set this equal to zero (ALS is immune to any REFL loop actuation), we need .
Next up, we want to see what this means for the closed loop gain of the whole system. For simplicity, let's let , where * can be either REFL or ALS.
Recall that the closed loop gain of the system (from point 1 to point 2) is
, so if we let and simplify, we get
This seems a little scary, in that maybe we have to be careful about keeping the system stable. Hmmmm. Note to self: more brain energy here.
Also, this means that I cannot explain why the filter wasn't working last night, with the guess of a complex pole pair at 1Hz for the MC actuator. The ALS plant has a cavity pole at ~80kHz, so for our purposes is totally flat. The only other thing that comes to mind is the delays that exist because the ALS signals have to hop from computer to computer. But, as Rana points out, this isn't really all that much phase delay below 100Hz where we want the cancellation to be awesome.
I propose that we just measure and vectfit the transfer function that we need, since that seems less time consuming than iteratively tweaking and checking.
Also, I just now looked at the wiki, and the MC2 suspension resonance for pos is at 0.97Hz, although I don't suspect that that will have changed anything significantly above a few Hz. Maybe it makes the cancellation right near 1Hz a little worse, but not well above the resonance.
I've fixed the gpib scripts for the SR785 and AG4395A to output data in the same format as expected by older scripts when called by them. In addition, there are now some easier modes of operation through the measurement scripts SRmeasure and AGmeasure. These are on the $PATH for the main control room machines, and live in scripts/general/netgpib
Case 1: I manually set up a measurement on the analyzer, and just want to download / plot the data.
Make sure you have a yellow prologix box plugged in, and can ping the address it is labeled with. (i.e. 'vanna'). Then, in the directory you want to save the data, run:
SRmeasure -i vanna -f mydata --getdata --plot
This saves mydata_(datetime).txt and mydata_(datetime).pdf in the current directory.
In all cases, AGmeasure has the identical syntax. If the GPIB address is something other than 10, specifiy it with -a, but this is rarely the case.
Case 2: I want to remotely specify a measurement
Rather than a series of command line arguments, which may get lost to the mists of time, I've set the scripts up to use parameter files that serve as arguments to the scripts.
Get the templates for spectrum and TF measurements in your current directory by running
Set the parameters with your text editor of choice, such as frequency span, filename output, whether to create a plot or not, then run the measurement:
Case 3: I want to compare my data with previous measurements
In the template parameter files, there is an option 'plotRefs', that will automatically plot the data from files whose filenames start with the same string as the current measurement.
If, in the "#" commented out header of the data file, there is a line that contains "memo:" or "timestamp:", it will include the text that follows in the plot legend.
There are also methods to remotely trigger an already configured measurement, or remotely reset an unresponsive instrument. Options can be perused by looking at the help in SRmeasure -h
I've tested, debugged, and used them for a bit, but wrinkles may remain. They've been svn40m committed, and I also set up a separate git repository for them at github.com/e-q/netgpibdata
We woke up the PDFR measurement setup that has been sleeping since summer. We ran a check for the laser module and the multiplexer module. We tried setting things up for measuring frequency response of AS55.
We could not repeat Nichin's measurements because the gpib scripts are outdated and need to be revised.
PDFR diode laser was shutdown after this job.
The fibers around the PSL table were shielded to avoid any tampering.
The goals are:
- When the REFL path is dead (e.g. S_REFL = 0), the system goes back to the ordinary ALS loop. => True (Good)
- When the REFL path is working, the system becomes insensityve to the ALS loop
(i.e. The ALS loop is inactivated without turning off the loop.) => True when (...) = 0
Are they correct?
Then I just repeat the same question as yesterday:
S is a constant, and Ps are cavity poles. So, approximately to say, (...) = 0 is realized by making D = 1/G_REFL.
In fact, if we tap the D-path before the G_REFL, we remove this G_REFL from (...). (=simpler)
But then, this means that the method is rather cancellation between the error signals than
cancellation between the actuation. Is this intuitively reasonable? Or my goal above is wrong?
I have calculated the response of this new 2.5 loop system.
The first attachment is my block diagram of the system. In the bottom left corner are the one-hop responses from each green-colored point to the next. I use the same matrix formalism that we use for Optickle, which Rana described in the loop-ology context in http://nodus.ligo.caltech.edu:8080/40m/10899.
In the bottom right corner is the closed loop response of the whole system.
Also attached is a zipped version of the mathematica notebook used to do the calculation.
EDIT, JCD, 17Feb2015: Updated loop diagram and calculation: http://188.8.131.52:8080/40m/11043
I have been able to recover the ability to sit at zero CARM offset while the PRMI is locked on RELF33 and CARM/DARM are on ALS, effectively indefinitely. However, I feel like the transmon QPDs are not behaving ideally, because the reported arm powers freqently go negative as the interferometer is "buzzing" through resonance, so I'm not sure how useful they'll be as normalizing signals for REFL11. I tried tweaking the DARM offset to help the buildup, since ALS is only roughly centered on zero for both CARM and DARM, but didn't have much luck.
Turning off the whitening on the QPD segments seems to make everything saturate, so some thinking with daytime brain is in order.
How I got there:
It turns out triggering is more important than the phase margin story I had been telling myself. Also, I lost a lot of time to needing demod angle change in REFL33. Maybe I somehow caused this when I was all up on the LSC rack today?
We have previously put TRX and TRY triggering elements into the PRCL and MICH rows, to guard against temporary POP22 dips, because if arm powers are greater than 1, power recylcing is happening, so we should keep the loops engaged. However, since TRX and TRY are going negative when we buzz back and forth through the resonsnace, the trigger row sums to a negative value, and the PRMI loops give up.
Instead, we can used the fortuitously unwhitened POPDC, which can serve the same function, and does not have the tendancy to go negative. Once I enabled this, I was able to just sit there as the IFO angrily buzzed at me.
Here are my PRMI settings
REFL33 - Rotation 140.2 Degrees, -89.794 measured diff
PRCL = 1 x REFL33 I; G = -0.03; Acquire FMs 4,5; Trigger FMs 2, 9; Limit: 15k ; Acutate 1 x PRM
MICH = 1 x REFL33 Q, G= 3.0, Acquire FMs 4,5,8; Trigger FM 2, 3; Limit: 30k; Actuate -0.2625 x PRM + 0.5 x BS
Triggers = 1 x POP22 I + 0.1 * POPDC, 50 up 5 down
Just for kicks, here's a video of the buzzing as experienced in the control room
With the Y Arm locked, we checked that we indeed can get loop decoupling using this technique.
The guess filter that we plugged in is a complex pole pair at 1 Hz. We guessed that the DC gain should be ~4.5 nm count. We then converted this number into Hz and then into deg(?) using some of Jenne's secret numbers. Then after measuring, we had to increase this number by 14.3 dB to an overall filter module gain of +9.3.
The RED trace is the usual 'open loop gain' measurement we make, but this time just on the LSC-MC path (which is the POY11_I -> ETMY path).
The BLUE trace is the TF between the ALS-Y phase tracker output and the FF cancellation signal. We want this to be equal ideally.
The GREEN trace is after the summing point of the ALS and the FF. So this would go to zero when the cancellation is perfect.
So, not bad for a first try. Looks like its good at DC and worse near the red loop UGF. It doesn't change much if I turn off the ALS loop (which I was running with ~10-15x lower than nominal gain just to keep it out of the picture). We need Jenne to think about the loop algebra a little more and give us our next filter shape iteration and then we should be good.
The nonlinearity in the LSC detection chain (cf T050268) comes from the photodetector and not the demod board. The demod board has low pass or band pass filters which Suresh installed a long time ago (we should check out what's in REFL33 demod board).
Inside the photodetector the nonlinearity comes about because of photodiode bias modulation (aka the Grote effect) and slew rate limited distortion in the MAX4107 preamp.
In order to try out the new locking scheme tonight, I have modified the LSC model. Screens have not yet been made.
It's a bit of a special case, so you must use the appropriate filter banks:
CARM filter bank should be used for ALS lock. MC filter bank should be used for the REFL1f signal.
The output of the MC filter bank is fed to a new filter bank (C1:LSC-MC_CTRL_FF). The output of this new filter bank is summed with the error point of the CARM filter bank (after the CARM triggered switch).
The MC triggering situation is now a little more sophisticated than it was. The old trigger is still there (which will be used for something like indicating when the REFL DC has dipped). That trigger is now AND-ed with a new zero crossing trigger, to make the final trigger decision. For the zero crossing triggering, there is a small matrix (C1:LSC-ZERO_CROSS_MTRX) to choose what REFL 1f signal you'd like to use (in order, REFL11I, REFL11Q, REFL55I, REFL55Q). The absolute value of this is compared to a threshold, which is set with the epics value C1:LSC-ZERO_CROSS_THRESH. So, if the absolute value of your chosen RF signal is lower than the threshold, this outputs a 1, which is AND-ed by the usual schmidt trigger.
At this moment, the input and output switches of the new filter bank are off, and the gain is set to zero. Also, the zero crossing selection matrix is all zeros, and the threshold is set to 1e9, so it is always triggered, which means that effectively MC filter bank just has it's usual, old triggering situation.