40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 211 of 339  Not logged in ELOG logo
ID Date Author Type Categoryup Subject
  10594   Fri Oct 10 03:05:09 2014 ericqUpdateLSCWhich side of optical spring are we on?

 I made some measurements to try and see if any difference could be seen with different CARM offset signs. 

Specifically, at various offsets, I used a spare DAC channel to drive IN1 of the CM board, as an "AO Exciter." I used CM_SLOW to monitor the signal that was actually on the board. I used the CARM_IN1 error signal to see how the optical plant responded to the AO excitation. Rather than a swept sine, I used a noise injection kind of TF measurement. 

Here are plots of CARM_IN1 / CM_SLOW at different CARM FM offsets; I chose to plot this in an attempt to divide out some of the common things like AA and delays and make the detuned CARM pole more evident). The offsets chosen correspond roughly to powers of 2, 2.5, and 3. I tried to go higher than that, but didn't remain locked for long enough to measure the TF. 

comparison.pdf

By eye, I don't see much of a difference. We can zpk fit the data, and see what happens. 

 

  10595   Fri Oct 10 03:25:11 2014 JenneUpdateLSCWhich side of optical spring are we on (simulation)

I have a simulated version of the differences that we expect to see between the 2 different sides of the CARM resonance.  The point is that we can try to compare these results with Q's measured results (elog 10594) to see if we know if we are on the spring or antispring side.


I calculated the same transfer functions vs CARM offset again, although tonight I do it in steps of 20pm because I was getting bored of waiting forever.  Anyhow, this is important because my previous post (elog 10591) didn't have spring side calculations all the way down to 1pm.

This is similarly true for that elog 10591, but here are some notes on how I am currently getting the W/N units out of Optickle.  First of all, I am still using old Optickle1.  I don't know if there are significant units ramifications for that, but just in case I'll write it down.  Nic tells me that to get [W/N] out of Optickle1, I need to multiply sigAC (units of [W/m]) by my simple pendulum (units of [m/N]).  Both of these "meters" in the last sentence are "mevans meters", which are the meters you would get per actuation if radiation pressure didn't exist.  So, I guess they're supposed to cancel out?  I need to camp out in Nic's office until I figure this out and get it untangled in my head.

Plots of transfer functions for both sides of CARM resonance (same as prev. elog), as well as the ratio between the spring and antispring transfer functions at each CARM offset:

TFs_TRX_vsCARMoffset_PRFPMI_antispring.pngTFs_TRX_vsCARMoffset_PRFPMI_spring.pngTFs_TRX_vsCARMoffset_PRFPMI_differentials.png

 

TFs_REFLDC_vsCARMoffset_PRFPMI_antispring.pngTFs_REFLDC_vsCARMoffset_PRFPMI_spring.pngTFs_REFLDC_vsCARMoffset_PRFPMI_differentials.png

TFs_REFL11I_vsCARMoffset_PRFPMI_antispring.pngTFs_REFL11I_vsCARMoffset_PRFPMI_spring.pngTFs_REFL11_vsCARMoffset_PRFPMI_differentials.png

The take-away message from the 3rd column is that other than a sign flip, we don't expect to see very much difference between the 2 sides of the CARM resonance, particularly above a few hundred Hz.  (Note that we do not see the sign flip in Q's measurements because he is looking at CARM_IN1, which is after the input matrix, and the input matrix elements have opposite signs between the signs of the CARM offsets.  So, the sign flip between spring and antispring around the UGF is implied in the measurements, just not explicit).

Also, something that Rana pointed out to me, and I still don't know why it's true:  The antispring transfer functions (at least for the transmission) don't have all the phase features that we expect to see based on their magnitudes.  If you look at the TRX antispring plot, blue trace (which is about 500pm from resonance), you'll see that the magnitude starts flat at DC, has some slope in an intermediate region, and then at high frequencies has 1/f^2.  However, the phase seems to not know about this intermediate region, and magically waits until the 1kHz resonance to flip the full 180 degrees. 

Attachment 10: ForElog_9Oct2014.zip
  10598   Mon Oct 13 12:01:28 2014 ericqUpdateLSCWhich side of optical spring are we on?

 I went back into the DQ channels to look at the TF from AO injection to REFLDC (which is easy to do with this kind of noise injection TF).  

AOInjection_SqrtInv_REFLDC.png

I fear that REFL does not seem to have as much phase under the resonance as we have modeled, lacking about 10-20 degrees. This could result from the zero in the REFL DC response that we've modeled at ~200ish Hz is actually higher. I'll look into what affects the frequency of that feature. 

It is, of course, possible, that this measurement doesn't properly cancel out the various digital effects, but the REFLDC phase curves do seem to settle to (+/-) 90 after the pole as expected. 

DTT XML file is attached. 

Attachment 2: AOinjection_SqrtInv_REFLDC.xml.zip
  10603   Mon Oct 13 21:20:56 2014 JenneUpdateLSCWhich side of optical spring are we on? (No progress)

[Jenne, Diego]

In order to distinguish between the spring and antispring sides of the CARM resonance, we need to have transfer function measurements down to at least 100 Hz (although lower is better). 

We tried to get some transfer functions the same way Q did, but noticed that (a) we couldn't get any low frequency coherence, and (b) that when we increased the amplitude of the white (well, lowpass at 5kHz) noise, the coherence between the AO injection and REFL DC went down.  Not clear why this is.

Anyhow, we tried taking good ol' fashioned swept sine transfer functions, although eventually the lightbulb came on that the AO path has a highpass in it.  Duh, Jenne.  So, we started trying to actuate on MC2 position rather than the AO path laser frequency.  We didn't get too far though before El Salvadore decided to have a few 7.4 earthquakes.  We're bored of aftershocks knocking us out of lock, so we're going to come back to this tomorrow.

 

  10607   Wed Oct 15 02:58:03 2014 JenneUpdateLSCWhich side of optical spring are we on?

Some measurements.  Unclear meaning.  

We tried both positive and negative numbers in the CARM offset, and then looked at transfer functions at various arm powers. The hope is to be able to compare these with some simulation to figure out which side of the CARM resonance we are on.

The biggest empirical take-away is that we repeatedly (3 times in a row) lost lock when holding at arm powers of about 5 with negative CARM offsets.  However, we were repeatedly (2+ times tonight) able to sit and hold at arm powers of 10+ with positive CARM offsets.

 

 

 

I am not sure that we get enough information out of these plots to tell us which side of the CARM resonance we are really on.  Q is working on taking some open loop CARM measurements (actuating and measuring at SUS-MC2_LSC) to see if we can compare those more directly to Rana's plots.

Positive number in the digital CARM offset:

PRFPMI_MC2injection_PosCARMoffset_REFLDC_TRX_response_14Oct2014_TRX.pdf

PRFPMI_MC2injection_PosCARMoffset_REFLDC_TRX_response_14Oct2014_REFLDC.pdf

Negative numbers in digital CARM offset:

PRFPMI_MC2injection_NegCARMoffset_REFLDC_TRX_response_14Oct2014_TRX.pdf

PRFPMI_MC2injection_NegCARMoffset_REFLDC_TRX_response_14Oct2014_REFLDC.pdf

  10608   Wed Oct 15 02:59:04 2014 ranaUpdateLSCCARM W/N TFs

 In my previous elog in this thread, I showed the CARM OLG given some new digital filters and the varying CARM plant (spring side, not anti-spring). Jenne has subsequently produced the TFs for all of the rest of the CARM offsets.

These attached plots for several CARM offsets show that the anti-spring side is much more stable than the spring side and so we should use that. Annecadotedally, we think that positive CARM offsets are more stable when going to arm powers of > 10, so perhaps this means that +CARM = -SPRING.

The first PDF shows the spring OLGs and the 2nd one shows the antispring OLGs. I have put in some gain changes to keep the UGF approximately the same as the offset is changed.

The PDF thumbnails will become visible once Q and Diego install the new nodus.

 UPDATE OCt 16: this is all wrong! bad conversion of filters within the invbilinear.m function.

Attachment 1: spring.pdf
spring.pdf
Attachment 2: antispring.pdf
antispring.pdf
  10609   Wed Oct 15 13:38:33 2014 JenneUpdateLSCCARM W/N TFs

Here are the same plots, but the legend also includes the arm power that we expect at that CARM offset.  


Here is what the arm powers look like as a function of CARM offset according to Optickle.  Note that the cyan trace's maximum matches what Q has simulated in Mist with the same high losses.  For illustration I've plotted the single arm power, so that you can see it's normalized to 1.  Then, the other traces are the full PRFPMI buildup, with various amounts of arm loss.  The "no loss" case is with 0ppm loss per ETM.  The "150 ppm loss" case is with 150 ppm of loss per ETM.  The "high loss" case is representative of what Q has measured, so I have put 500 ppm loss for ETMX and 150 ppm loss for ETMY.

ArmPower_vs_Loss.png


And, the transfer functions (all these, as with all TFs in the last week, use the "high loss" situation with 500ppm for ETMX and 150ppm for ETMY).

TFs_TRX_vsCARMoffset_PRFPMI_antispring.pngTFs_TRX_vsCARMoffset_PRFPMI_spring.png

TFs_REFLDC_vsCARMoffset_PRFPMI_antispring.pngTFs_REFLDC_vsCARMoffset_PRFPMI_spring.png

TFs_REFL11I_vsCARMoffset_PRFPMI_antispring.pngTFs_REFL11I_vsCARMoffset_PRFPMI_spring.png

  10612   Wed Oct 15 19:56:38 2014 JenneUpdateLSCWhich side of optical spring are we on? Meas vs Model

 I have plotted measured data from last night (elog 10607) with a version of the result from Rana's simulink CARM loop model (elog 10593).

The measured data that was taken last night (open circles in plots) is with an injection into MC2 position, and I'm reading out TRX.  This is for the negative side of the digital CARM offset, which is the one that we can only get to arm powers of 5ish.

The modeled data (solid lines in plots) is derived from what Rana has been plotting the last few days, but it's not quite identical.  I added another excitation point to the simulink model at the same place as the "CARM OUT" measurement point.  This is to match the fact that the measured transfer functions were taken by driving MC2.  I then asked matlab to give me the transfer function between this new excitation point (CARM CTRL point) and the IN1 point of the loop, which should be equivalent to our TRX_OUT.  So, I believe that what I'm plotting is equivalent to TRX/MC2.  The difference between the 2 plots is just that one uses the modeled spring-side optical response, and the other uses the modeled antispring-side response.

AntispringModel_NegOffsetMeas_comparison.pdf

SpringModel_NegOffsetMeas_comparison.pdf

I have zoomed the X-axis of these plots to be between 30 Hz - 3 kHz, which is the range that we had coherence of better than 0.8ish last night in the measurements.  The modeled data is all given the same scale factor (even between plots), and is set so that the lowest arm power traces (pink) line up around 150 Hz. 

I conclude from these plots that we still don't know what side of the CARM resonance we are on. 

 I have not plotted the measurements from the positive side of the digital CARM offset, because those transfer functions were to sqrtInvTRX, not plain TRX, whereas the model only is for plain TRX. There should only be an overall gain difference between them though, no phase difference.  If you look at last night's data, you'll see that the positive side of the CARM offset measured phase has similar characteristics to the negative offset, i.e. the phase is not flat, but it is roughly flat in both modeled cases, so even with that data, I still say that we don't know what side of the CARM resonance we are on.

 

 

  10613   Wed Oct 15 20:10:29 2014 ericqUpdateLSCInterim DARM Signal

I've done some preliminary modeling to see if there is a good candidate for an IR DARM control signal that is available before the AS55 sign flip. From a DC sweep point of view, ASDC/(TRX+TRY) may be a candidate for further exploration. 


As a reminder, both Finesse and MIST predict a sign flip in the AS55 Q control signal for DARM in the PRFPMI configuration, at a CARM offset of around 118pm.

dcAS55_DARM.pdfAS55Flip.pdf

The CARM offset where this sign flip occurs isn't too far off of where we're currently losing lock, so we have not had the opportunity to switch DARM control off of ALS and over to the quieter IR RF signal of AS55. 


Here are simulated DC DARM sweep plots of our current PRFPMI configuration, with a whole bunch of potential signals that struck me. 

Although the units of most traces are arbitrary in each plot (to fit on the same scale), each plot uses the same arbitrary units (if that makes any sense) so slopes and ratios of values can be read off. 

dcDARMSweep-300.pdfdcDARMSweep-120.pdfdcDARMSweep-50.pdfdcDARMSweep-0.pdf

In the 300 and 120pm plot, you can see that the zero crossing of AS55 is at some considerable DARM offset, and normalizing by TRX doesn't change much about that. "Hold on a second," I hear you say. "Your first plots said that the sign flip happens at around 120pm, so why does the AS55 profile still look bad at 50pm?!" My guess is that, probably due to a combination of Schnupp and arm length asymmetry, CARM offsets move where the peak power is in the DARM coordinate. This picture makes what I mean more clear, perhaps:

2dSweep.pdf

Thus, once we're on the other side of the sign flip, I'm confident that we can use AS55 Q without much problem. 


Now, back to thoughts about an interim signal:

ASDC by itself does not really have the kind of behavior we want; but the power out of AS as a fraction of the ARM power (i.e. ASDC/TRX in the plot) seems to have a rational shape, that is not too unlike what the REFLDC CARM profile looks like.

Why not use POPDC or REFLDC? Well, at the CARM offsets we're currently at, POPDC is dominated by the PRC resonating sidebands, and REFLDC has barely begun to decline, and at lower CARM offsets, they each flatten out before the peak of the little ASDC hill, and so don't do much to improve the shape. Meanwhile, ASDC/TRX has a smooth response to points within some fraction of the DARM line width in all of the plots. 

Thus, as was discussed at today's meeting, I feel it may be possible to lock DARM on ASDC/(TRX+TRY) with some offset, until AS55 becomes feasible.

(In practice, I figure we would divide by the sum of the powers, to reduce the influence of the DARM component of just TRX; we don't want to have DARM/DARM in the error signal for DARM)

Two caveats are:

  • The slope of this signal actually looks more quadratic than linear. Is this ok/manageable?
  • I have not yet made any investigation into the frequency dependent behavior of this thing. Transmission in the denominator will have the CARM pole in it, might get complicated. 

[Code and plots live in /svn/trunk/modeling/PRFPMI_radpressure]

 

  10614   Wed Oct 15 22:39:17 2014 JenneUpdateLSCThe Plan

 [Rana, Jenne]

We're summarizing the discussions of the last few days as to the game plan for locking.  

  1. PRMI on REFL165.  The factor of 5 in frequency will give us more MICH signal.    We want this.
    1. Drive CARM, measure coupling to PRCL, MICH while locked on REFL33.
    2. Switch to REFL165, re-measure CARM coupling.
    3. Hopefully this will reduce the AS port fluctuations, and reduce the POP22 power decrease as CARM offset decreases. 
  2. DARM transition from ALSdiff to an intermediate signal.  Simulate, and try empirically.
    1. Maybe try ASDC normalized by sum of transmissions?
    2. Maybe try difference of transmissions divided by sum of transmissions?  
  3. Look at data on disk.
    1. Do we have anything specific causing our locklosses (lately there haven't been obvious loop instabilities causing the locklosses)?
    2. How much do we think our lengths are actually changing right now (particularly DARM on ALSdiff)?
    3. Are there better ways of combining error signals that could be useful?
    4. Do we need to work on angular loops?
      1. Oplevs
      2. POP ASC for sidebands
      3. POP QPD or Trans QPDs for arms
  4.  Think about what could be causing ETMX to be annoying.  The connection that is most suspect has been ziptied, but we're still seeing ETMX move either at locklosses or sometimes just spontaneously.
  5.  RAM.  What kind of RAM levels do we have right now, and how do they affect our locking offsets?  Do we have big offsets, or negligible offsets?
  10615   Thu Oct 16 03:13:23 2014 JenneUpdateLSCPRMI on REFL165, and more

 The first thing I looked at tonight was locking the PRMI on REFL 165.

I locked the PRMI (no arms), and checked the REFL 165 demod phase. I also found the input matrix configuration that allowed me to acquire PRMI lock directly on REFL165.  After locking the arms on ALS, I tried to lock the PRMI with REFL 165 and failed.  So, I rechecked the demod phase and the relative transfer functions between REFL 165 and REFL 33.  The end of the story is that, even with the re-tuned demod phase for CARM offset of a few nanometers, I cannot acquire PRMI lock on REFL 165, nor can I transition from REFL 33 to REFL 165.  We need to revisit this tomorrow.

IFO configuration CARM offset [cts] REFL 165 demod phase [deg]
Found as-is N/A +145
PRMI, no arms N/A -135
PRFPMI +3 +110
PRFPMI +2 +110
PRFPMI +1 +110
PRFPMI +0.5 +120

 

IFO configuration REFL 33 I / REFL 165 I (PRCL) REFL 33 Q / REFL 165 Q (MICH)
PRMI, no arms +0.1 +0.22, although easier to acquire lock with +0.1
PRFPMI, CARM offset = +3 -0.09  (TF measured, no lock) +0.033  (TF measured, no lock)

For the PRMI-only case, I ended up using 0.1's in the input matrix, and I added an FM 1 to the MICH filter bank that is a flat gain of 2.2, and then I had it trigger along with FM2.

I turned this FM1 off (and no triggering) while trying to transition from REFL33 to REFL165 in the PRFPMI case, but that didn't help.  I think that maybe I need to remeasure my transfer functions or something, because I could put values into the REFL165 columns of the input matrix while REFL33 was still 1's, but I couldn't remove (even if done slowly) the REFL33 matrix elements without losing lock of the PRMI.  So, we need to get the input matrix elements correct.


I also recorded some time series for a quick RAM investigation that I will work on tomorrow.  

I left the PRM aligned, but significantly misaligned both ITMs to get data at the REFL port of the RAM that we see.  I also aligned the PRMI (no arms) and let it flash so that I can see the pk-pk size of our PDH signals.  I need to remember to calibrate these from counts to meters.  

Raw data is in /users/jenne/RAM/ .


I have not tried any new DARM signals, since PRMI wasn't working with 3f2.  

We should get to that as soon as we fix the PRMI-3f2 situation.

  10618   Thu Oct 16 16:21:42 2014 ericqUpdateLSCInterim DARM Signal

I've added (TRX-TRY)/(TRX+TRY) to the DC DARM sweep plots, and it looks like an even better candidate. The slope is closer to linear, and it has a zero crossing within ~10pm of the true DARM zero across the different CARM offsets, so we might not even need to use an intentional DARM offset. 

dcDARMSweep-300.pdfdcDARMSweep-120.pdfdcDARMSweep-50.pdfdcDARMSweep-0.pdf

 

  10619   Thu Oct 16 21:20:59 2014 ranaUpdateLSCmisleading modelling

 I think these are all very helpful and interesting plots. We should see some better performance using either of the DC DARM signals.

BUT, what we really need (instead of just the DC sweeps) is the DC sweep with the uncertainty/noise displayed as a shaded area on the plot, as Nic did for us in the pre-CESAR modelling.

Otherwise, the DC sweeps mistakenly indicate that many channels are good, whereas they really have an RMS noise larger than 100 pm due to low power levels or normalization by a noisy signal.

  10620   Thu Oct 16 22:35:05 2014 ranaUpdateLSCCARM W/N TFs

In my last CARM loop modelling, all of the plots are phony, so don't trust them. The invbilinear function inside of StefanB's onlinefilter.m was making bogus s-domain representations of the digital filter coefficients.

So now I've just plotted the frequency response directly from the z-domain SOS coeffs using MattE's readFilterFile.m and FotonFilter.m.

Conclusions are less rosy. The anti-spring side is still easier to compensate than the spring side, but it starts to get hopeless below ~130 pm of offset, so there we really need to try to get to REFL_11/(TRX+TRY), pending some noise analysis.

** In order to get the 80 and 40 pm loops to be more stable I've put in a tweak filter called Boost2 (FM8). As you can see, it kind of helps for 80 pm, but its pretty hopeless after that.

Attachment 1: carm_spring.pdf
carm_spring.pdf
Attachment 2: carm_antispring.pdf
carm_antispring.pdf
  10621   Fri Oct 17 03:05:00 2014 ericqUpdateLSCDARM locked on DC Transmission difference

 I've been able to repeatedly get off of ALS and onto (TRY-TRX)/(TRY+TRX). Nevertheless, lock is lost between arm powers of 10 and 20. 

I do the transition at the same place as the CARM->SqrtInv transition, i.e. arm powers about 1.0 Jenne started a script for the transition, and I've modified it with settings that I found to work, and integrated it into the carm_cm_up script. I've also modified carm_cm_down to zero the DARM normalization elements. 

I was thwarted repeatedly by the frequent crashing of daqd, so I was not able to take OLTFs of CARM or DARM, which would've been nice. As it was, I tuned the DARM gain by looking for gain peaking in the error signal spectrum. I also couldn't really get a good look at the lock loss events. Once the FB is behaving properly, we can learn more. 

Turning over to difference in transmission as an error signal naturally squashes the difference in arm transmissions:

TRdifflock.png


I was able to grab spectra of the error and control signals, though I did not take the time to calibrate them... We can see the high frequency sensing noise for the transmission derived signals fall as the arm power increases. The low frequency mirror motion stays about the same. 

Oct17lock.pdf


So, it seems that DARM was not the main culprit in breaking lock, but it is still gratifying to get off of ALS completely, given its out-of-loop-noise's strong dependence on PSL-alignment. 

  10622   Fri Oct 17 13:19:48 2014 JenneUpdateLSCPOP22 ?!?!

We've seen this before, but we need to figure out why POP22 decreases with decreased CARM offset.  If it's just a demod phase issue, we can perhaps track this by changing the demod phase as we go, but if we are actually losing control of the PRMI, that is something that we need to look into.

In other news, nice work Q!

Quote:

TRdifflock.png

 

  10625   Fri Oct 17 17:52:55 2014 JenneUpdateLSCRAM offsets

Last night I measured our RAM offsets and looked at how those affect the PRMI situation.  It seems like the RAM is not creating significant offsets that we need to worry about.


Words here about data gathering, calibration and calculations.

Step 1:  Lock PRMI on sideband, drive PRM at 675.13Hz with 100 counts (675Hz notches on in both MICH and PRCL).  Find peak heights for I-phases in DTT to get calibration number.

Step 2:  Same lock, drive ITMs differentially at 675.13Hz with 2,000 counts.  find peak heights for Q-phases in DTT to get calibration number.

Step 3:  Look up actuator calibrations.  PRM = 19.6e-9/f^2 meters/count and ITMs = 4.68e-9/f^2 meters/count.  So, I was driving PRM about 4pm, and the ITMs about 20pm.

Step 4:  Unlock PRMI, allow flashes, collect time series data of REFL RF siganls.

Step 5: Significantly misalign ITMs, collect RAM offset time series data.

Step 6: Close PSL shutter, collect dark offset time series data.

Step 7: Apply calibration to each PD time series.  For each I-phase of PDs, calibration is (PRM actuator / peak height from step 1).  For each Q-phase of PDs, calibration is (ITM actuator / peak height from step 2).

Step 8:  Look at DC difference between RAM offset and dark offset of each PD.  This is the first 4 rows of data in the summary table below.

Step 9:  Look at what peak-to-peak values of signals mean.  For PRCL, I used the largest pk-pk values in the plots below.  For MICH I used a calculation of what a half of a fringe is - bright to dark.  (Whole fringe distance) = (lambda/2), so I estimate that a half fringe is (lambda/4), which is 266nm for IR.  This is the next 4 rows of data in the table.

Step 10: Divide.  This ratio (RAM offset / pk-pk value) is my estimate of how important the RAM offset is to each length degree of freedom. 


Summary table:

  PRCL (I-phase) MICH (Q-phase)
RAM offsets    
11 4e-11 m 2.1e-9 m
33 1.5e-11 m ~2e-9 m
55 2.2e-11 m ~1e-9 m
165 ~1e-11 m ~1e-9 m
Pk-pk (PDH or fringes) PDH pk-pk from flashes MICH fringes from calculation
11 5.5e-9 m 266e-9 m
33 6.9e-9 m 266e-9 m
55 2.5e-9 m 266e-9 m
165 5.8e-9 m 266e-9 m
Ratio: (RAM offset) / (pk-pk)    
11 7e-3 8e-4
33 2e-3 7e-3
55 9e-3 4e-3
165 2e-3 4e-3

 


Plots (Left side is several PRMI flashes, right side is a zoom to see the RAM offset more clearly):

RAM_PRMI_PRMIflashing_REFL11I.pdfRAM_PRMI_Zoom_REFL11I.pdf

RAM_PRMI_PRMIflashing_REFL11Q.pdfRAM_PRMI_Zoom_REFL11Q.pdf

RAM_PRMI_PRMIflashing_REFL33I.pdfRAM_PRMI_Zoom_REFL33I.pdf

RAM_PRMI_PRMIflashing_REFL33Q.pdfRAM_PRMI_Zoom_REFL33Q.pdf

RAM_PRMI_PRMIflashing_REFL55I.pdfRAM_PRMI_Zoom_REFL55I.pdf

RAM_PRMI_PRMIflashing_REFL55Q.pdfRAM_PRMI_Zoom_REFL55Q.pdf

RAM_PRMI_PRMIflashing_REFL165I.pdfRAM_PRMI_Zoom_REFL165I.pdf

RAM_PRMI_PRMIflashing_REFL165Q.pdfRAM_PRMI_Zoom_REFL165Q.pdf

  10626   Mon Oct 20 17:50:30 2014 JenneUpdateLSCCARM W/N TFs (Others were all wrong!)

I realized today that I had been plotting the wrong thing for all of my transfer functions for the last few weeks! 

The "CARM offsets" were correct, in that I was moving both ETMs, so all of the calculations were correct (which is good, since those took forever). But, in the plots I was just plotting the transfer function between driving ETMX and the given photodiode.  But, since just driving a single ETM is an admixture of CARM and DARM, the plots don't make any sense.  Ooops.

In these revised plots (and the .mat file attached to this elog), for each PD I extract from sigAC the transfer function between driving ETMX and the photodiode.  I also extract the TF between driving ETMY and the PD.  I then  sum those two transfer functions and divide by 2.  I multiply by the simple pendulum, which is my actuator transfer function to get to W/N, and plot.

The antispring plots don't change in shape, but the spring side plots do.  I think that this means that Rana's plots from last week are still true, so we can use the antispring side of TRX to get down to about 100 pm.

Here are the revised plots:

TFs_TRX_vsCARMoffset_PRFPMI_antispring.pngTFs_TRX_vsCARMoffset_PRFPMI_spring.png

TFs_REFLDC_vsCARMoffset_PRFPMI_antispring.pngTFs_REFLDC_vsCARMoffset_PRFPMI_spring.png

TFs_REFL11I_vsCARMoffset_PRFPMI_antispring.pngTFs_REFL11I_vsCARMoffset_PRFPMI_spring.png

Attachment 1: PDs_vsCARMoffset_20Oct2014.mat.zip
  10627   Tue Oct 21 00:38:40 2014 ericqUpdateLSCsweep + RMS as uncertainty

Quote:

BUT, what we really need (instead of just the DC sweeps) is the DC sweep with the uncertainty/noise displayed as a shaded area on the plot, as Nic did for us in the pre-CESAR modelling.

I've taken a first stab at this. Through various means, I've made an estimation of the total noise RMS of each error signal, and plotted a shaded region that shows the range of values the error signal is likely to take, when the IFO is statically sitting at one CARM offset. 

I have not included any effects that would change the RMS of these signals in a CARM-offset dependent way. Since this is just a rough first pass, I didn't want to get carried away just yet. 


For the transmission PDs, I measured the RMS on single arm lock. I also measured the incident power on the QPDs and thorlabs PDs for an estimate of shot noise, but this was ridiculously smaller than the in-loop RIN. I had originally though of just plotting sensing noise for the traces (i.e. dark+shot), because the amount of seismic and frequency noise in the in-loop signal obviously depends on the loop, but this gives a very misleading, tiny value. In reality we have RIN from the PRC due to seismic noise, angular motion of the optics, etc., which I have not quantified at this time. 

So: for this first, rough, pass, I am simply multiplying the single transmission noise RMSs by a factor of 10 for the coupled RMS. If nothing else, this makes the SqrtInv signal look plausible when we actually practically find it to be plausible. 


For the REFL PDs, I misaligned the ITMs for a prompt PRM reflection for a worst-case shot noise situation, and took the RMS of the spectra. (Also wrote down the dark RMSs, which are about a factor of 2 lower). I then also multiplied these by ten, to be consistent with the transmission PDs. In reality, the shot noise component will go down as we approach zero CARM offset, but if other effects dominate, that won't matter. 


Enough blathering, here's the plot:

dcCARMSweep_uncertainties.png

Now, in addition to the region of linearity/validity of the different signals, we can hopefully see the amount of error relative to the desired CARM offset. (Or, at least, how that error qualitatively changes over the range of offsets)


This suggests that we MAY be able to hop over to a normalized RF signal; but this is a pretty big maybe. This signal has the response of the quotient of two nontrivial optical plants, which I have not yet given much thought to; it is probably the right time to do so...

  10630   Wed Oct 22 02:35:45 2014 JenneUpdateLSCEfforts at hopping PRMI to REFL165

[EricQ, Jenne]

The first half of our evening was spent working on CARM and DARM in PRFPMI, and then we moved on to the PRMI part.

I moved the DARM ALSdiff -> TransDiff transition to be after the CARM ALScomm -> SqrtInvTrans transition in the carm_cm_up script.  After I did that, I succeeded every time (at least  10?  We did it many times) to get both CARM and DARM off of the ALS signals. 

We tried for a little while looking at transitioning to REFL11 normalized by the sum of the transmissions, but we kept losing lock.  We also several times lost lock at arm powers of a few, when we thought we weren't touching the IFO for any transitions.  Looking at the lockloss time series did not show any obvious oscillations in any of the _IN1 or _OUT channels for the length degrees of freedom, so we don't know why we lost lock, but it doesn't seem to be loop oscillations caused by changing optical gain.  Also, one time, I tried engaging Rana's "Lead 350" filter in FM7 of the CARM filter bank when we were on sqrtInvTrans for CARM, and the arm powers were around a few, but that caused the transmission signals to start to oscillate, and after one or two seconds we lost lock.  We haven't tried the phase lead filter again, nor have we tried the Boost2 that is in FM8. 

We increased the REFL11 analog gain from 0dB to 12dB, and then reset the dark offsets, but still weren't able to move CARM to normalized REFL11. Also, I changed the POP22 demod phase from 159 degrees to 139 degrees. This seems to be where the signal is maximized in the I-phase, while the arms are held off resonance, and also partway up the resonance peak. 

We then decided that we should go back to the PRMI situation before trying to reduce the CARM offset further.  We can robustly and quickly lock the PRMI on REFL33 while the arms are held off resonance with ALS.  So, we have been trying to acquire on  REFL33 I&Q, and then look at switching to REFL 165 I&Q.  It seems pretty easy to get PRCL over to REFL165 I (while leaving MICH on REFL33 I).  For REFL33, both matrix elements are +1.  For PRCL on REFL165, the matrix element is -0.08.  We have not successfully gotten MICH over to REFL 165 ever this evening. 

We went back and set the REFL165 I&Q offsets so that the outputs after the demod phase were both fluctuating around 0.  I don't know if they were around +/-100 because our dark offsets were bad or what, but we thought this would help.  We were still able to get PRCL transitioned no problem, but even after remeasuring the MICH REFL33 vs. REFL165 relative gains, we still can't transition MICH.  It seems like it's failing when the REFL33Q matrix element finally gets zeroed out, so we're not really getting enough signal in REFL165Q, or something like that, and throughout the rest of the transition we were depending entirely on REFL33Q. 

So. Plan:

  • Get PRMI on REFL165 while arms are held off resonance. 
    • May require PRCL-MICH FF decoupling, by combining error signals?
    • May require looking back at simulations to see what we expect the relative gains and signs to be.
  • Look at CARM loop stability in simulation for REFLDC, REFL11, and normalized REFL11.  Is there a stable loop path from about 100pm down to 0pm on normalized REFL11?
  10631   Wed Oct 22 06:32:29 2014 ranaUpdateLSCsweep + RMS as uncertainty

 

 This is looking very useful. It will be useful if you can upload some python code somewhere so that I can muck with it.

I would guess that the right way to determine the trans RMS is just to use the single arm lock RIN and then apply that as RIN (not pure TR RMS) to the TR signals before doing the sqrt operation.

  10634   Thu Oct 23 02:08:40 2014 JenneUpdateLSCIncreased DARM gain

I changed the carm_cm_up.sh script so that it requires fewer human interventions.  Rather than stopping and asking for things like "Press enter to confirm PRMI is locked", it checks for itself.  The sequence that we have in the up script works very reliably, so we don't need to babysit the first several steps anymore. 

Another innovation tonight that Q helped put in was servoing the CARM offset to get a certain arm power.  A failing of the script had been that depending on what the arm power was during transition over to sqrtInvTrans, the arm power was always different even if the digital offset value was the same.  So, now the script will servo (slowly!!) the offset such that the arm power goes to a preset value.

The biggest real IFO progress tonight was that I was able to actually measure the CARM and DARM loops (thanks ChrisW!), and so I discovered that even though we are using (TRX-TRY)/(TRX+TRY) for our IR DARM error signal, we needed to increase the digital gain for DARM as the CARM offset was reduced.  For ALS lock and DC trans diff up to arm powers of 3, we use the same ol' gain of 6.  However, between 3 - 6, we need a gain of 7.  Then, when we go to arm powers above 6 we need a gain of 7.5.  I was also measuring the CARM loop at each of these arm powers (4, 6, 7, 8, 9), but the gain of 4 that we use for sqrtInvTrans was still fine. 

So, the carm_cm_up script will do everything that it used to without any help (unless it fails to find IR resonance for ALS, or can't lock the PRMI, in which case it will ask for help), and then once it gets to these servo lines to slowly increase the arm power and increase the DARM gain, it will ask you to confirm before each step is taken.  The script should get you all the way to arm powers of 9, which is pretty much exactly 100pm according to Q's Mist plot that is posted.

The CARM and DARM loops (around the UGFs) don't seem to be appreciably changing shape as I increase the arm powers up to 9 (as long as I increase the DARM loop gain appropriately).  So, we may be able to go a little bit farther, but since we're at about 100pm, it might be time to look at whether we think REFL11 or REFLDC is going to be more promising in terms of loop stability for the rest of the way to resonance.


Here are some plots from this evening. 

First, the time I was able to get to and hold at arm powers of 9.  I have a striptool to show the long time trends, and then zooms of the lockloss.  I do not see any particular oscillations or anything that strikes me as the cause for the lockloss.  If anyone sees something, that would be helpful.

ArmPowers9_1am_22Oct2014.png

Lockloss_ArmsAt9_1am_22Oct2014.png

LocklossZoom_ArmsAt9_1am_22Oct2014.png

This next lockloss was interesting because the DARM started oscillating as soon as the normalization matrix elements were turned on for DARM on DC transmissions.  The script should be measuring values and putting in matrix elements that don't change the gain when they are turned on, but perhaps something didn't work as expected.  Anyhow, the arm powers were only 1ish at the time of lockloss.  There was some kind of glitch in the DARM_OUT (see 2nd plot below, and zoom in 3rd plot), but it doesn't seem to have caused the lockloss.

Lockloss_ArmsAt1ish_TransOscillation_110am_22Oct2014.png

LocklossZoom_ArmsAt1ish_TransOscillation_110am_22Oct2014.png

LocklossZoomGlitch_ArmsAt1ish_TransOscillation_110am_22Oct2014.png

  10637   Fri Oct 24 02:14:05 2014 JenneUpdateLSCIncreased DARM gain even more

[Jenne, Diego]

We spent the afternoon working on the new scan for IR resonance script.  It is getting much closer, although we need to work on a plan for the fine scanning at the end - so far, the result from the wavelet thing mis-estimates the true peak phase, and so if we jump to where it recommends, we are only at about half of the arm resonance.  So, in progress, but moving forward.

Tonight we repeated the process of reducing the CARM offset and measuring the DARM loop gain as we went.  I'm not sure if I just had the wrong numbers yesterday, or if the gains are changing day-by-day.  The gains that it wanted at given arm buildups were constant throughout this evening, but they are about a factor of 2 higher than yesterday.  If they really do change, we may need to implement a UGF servo for DARM.  New gains are in the carm_cm_up script.

We also actually saved our DARM loop measurements as a function of CARM offset (as indicated by arm buildups).  The loop stays the same through arm powers of 4.  However, once we get to arm powers of 6, the magnitude around 100 Hz starts to flatten out, and we get some weird features in the phase.  It's almost like the phase bubble has a peak growing out of it.  I saw these yesterday, and they just keep getting more pronounced as we go up to arm powers of 7, 8 and 9 (where we lost lock during the measurement).  The very last point in the power=9 trace was just before/during the lockloss, so I don't know if we trust it, or if it is real and telling us something important.  But, I think that it's time to see about getting both CARM and DARM onto a different set of error signals now that we're at about 100pm.

 DARM_23Oct2014.pdf

  10641   Mon Oct 27 19:15:54 2014 ericqUpdateLSCTrying to PRMI on 165

I spent some time trying to debug our inability to get MICH onto REFL165Q while the arms are held off with ALS, to no real success. 

I set up our usual repeatable situation of PRMI on 33 I&Q, arms held off with ALS. I figured that it may help to first sideband lock on REFL55, since 165 is looking for the f2 sidebands and maybe there is some odd offset between the locking points for f1 and f2 or other weirdness. 


REFL 55 settings:

Demod angle 98->126 (was previously set for PRY locking)

PRCL = 0.5 * REFL55 I (UGF of ~200 Hz) (FM gain unchanged from REFL33 situation of -0.02)

MICH = 0.125 * REFL55 Q (UGF of ~60Hz) (same FM gain as 33)

Some REFL55 offset adjusting had to be done in order to not disturb the 33-initiated lock when handing off. 

I also adjusted POP110 phase to zero the Q when locked, and switched the triggering over to 110I


The PRMI can acquire lock like this with arms held off with ALS, no problem. 

Here, I tried to hop over to 165. PRCL was no problem, needing a +1 on 165I. However, I had no success in handing off MICH.   I twiddled many knobs, but none that provably helped. 

I saw indications that the sensing angle in 165 is small (~20deg), which is not consistent with current knowledge of the cavity lengths. We last interferometrically measured the PRC length by letting the PRMI swing and looking at sideband splitting in POP110. At LLO, they did a length measurement by looking at demod angle differences in PRMI carrier vs. sideband locking. (alog8562) This might be worth checking out...

  10649   Wed Oct 29 03:33:38 2014 ericqUpdateLSCTrying to PRMI on 165

 

Short report: Further frustrated by 165 tonight. The weird thing is, the procedure I'm trying with the arms held off on ALS (i.e. excitation line in MICH and PRCL, adjust relative gains to make the signs and magnitudes mach, ezcastep over) works flawlessly with the ETMs misaligned. One can even acquire SB PRMI lock on 165 I&Q, with 80-90 degrees of demod angle between MICH and PRCL. The only real difference in REFL55 settings for misaligned vs. ALS-offset arms is an extra factor of two in the FM gains to maintain the same UGF, so I hoped that the matrix elements for 165 with misaligned arms would hold for ALS-offset arms. 

Alas, no such fortune. I still have no clear explanation for why we can't get MICH on 165Q with the arms held off on ALS. 

I also gave a quick try to measuring the PRCL->REFL55 demod phase difference between carrier and sideband lock (with arms misaligned), and got something on the order of 55 degrees, which really just makes me think I wasn't well set up / aligned, rather than actually conveying information about the PRC length...

  10652   Thu Oct 30 01:21:37 2014 JenneUpdateLSCNo MICH in REFL165

[Koji, Jenne, Diego]

Summary:  We really don't have any MICH signal in REFL 165.  Why is still a mystery.

We made several transfer function measurements while PRMI was locked on REFL33 with the arms held off resonance, and compared those to the case where the ETMs are misaligned.  We fine-tuned the REFL165 demod phase looking at the transfer function between 10-300 Hz (using bandpassed white noise injected in the MICH FF filter bank and looking at REFL165Q), rather than just a single line.  We did that at CARM offset of 3 counts (ALS locked), and then saw that as we reduced the CARM offset, the coherence between MICH injection and REFL165Q just goes down.  Any signal that is there seems to be dominated by PRCL. 

So, we're not sure why having the arms eats the MICH 165 signal, but it does.  Everyone should dream tonight about how this could happen. 

Koji suggested that if the signal is just lost in the noise, perhaps we could increase our modulation depth for 55MHz (currently at 0.26, a pretty beefy number already).  Alternatively, if instead the problem is that the MICH signal has rotated to be in line with the PRCL signal, there may be no hope (also, why would this happen?).

Anyhow, we'd like to understand why we don't have any MICH signal in REFL165 when the arm cavities are involved, but until we come up with a solution we'll stick with REFL33 and see how far that gets us. 

The only really worthwhile plot that I've got saved is the difference in these transfer functions when PRMI-only locked and PRMI+arms locked.  Green is PRMI-only, with the demod phase optimized by actuating on PRM and minimizing the peak in the Q signal.  Blue is PRMI with the arms held off resonance using the ALS signals, with the demod phase set again, in the same way.  We were expecting (at least, hoping) that the blue transfer function would have the same shape as the green, but clearly it doesn't.  The dip that is around 45 Hz can be moved by rotating the demod phase, which changes how much PRCL couples into the Q phase.  Weird.  At ~3nm we had somewhat reasonable coherence to RELF165Q, and were able to pick -102deg as the demod phase where the dip just disappears.  However, as the CARM offset is reduced, we lost coherence in the transfer functions.

MICH_to_REFL165_29Oct2014.pdf

  10654   Thu Oct 30 02:54:38 2014 diegoUpdateLSCIR Resonance Script Status

[Diego, Jenne]

The script is moving forward and we feel we are close, however we still have a couple of issues, which are:

1) some python misbehaviour between the system environment and the anaconda one; currently we call bash commands within the python script in order to avoid using the ezca library, which is the one complaining;

2) the fine scan is somewhat not so robust yet, need to investigate more; the main suspects are the wavelet parameters given to the algorithm, and the Offset and Ramp parameters used to perform the scan.

Here is an example of a best case scenario, with 20s ramp and 500 points:

 

Attachment 1: AllPython_findIRresonance_WL_X_ramp_20_500_2.png
AllPython_findIRresonance_WL_X_ramp_20_500_2.png
Attachment 2: AllPython_findIRresonance_WL_Y_ramp_20_500_2.png
AllPython_findIRresonance_WL_Y_ramp_20_500_2.png
Attachment 3: AllPython_findIRresonance_WL_ramp_20_500_2.png
AllPython_findIRresonance_WL_ramp_20_500_2.png
  10656   Fri Oct 31 02:19:37 2014 ericqUpdateLSCSome SRMI progress

Earlier today, I did some simulations that suggested that PRC lengths on the order of a cm from our current estimated one could result in degenerate PRCL and MICH signals in REFL165 at 3nm CARM offset. I attempted more demod-angle derived cavity PRC length measurements with REFL11 and REFL55, but they weren't consistent with each other...

In any case, adding dual recycling, even with a SRC length off by 1cm in either direction, doesn't seem to exhibit the same possibility, so I spent some time tonight seeing if I could make any progress towards DRMI locking. 

I was able to lock SRY using AS55 in a very similar manner to PRY, after adjusting the AS55 demod angle to get the error signal entirely in I. I used this configuration to align the SRM to the previously aligned BS and ITMY. Oddly, I was not able to do anything with SRX as I had hoped; the error signal looks very strange, looking more like abs(error signal). 

I then was able to lock the SRMI on AS55 I & Q, the settings have been saved in the IFO configure screen.  I've used AS55Q for PRMI locking with a gain of -0.2, so I started with that; the final gain ended up being -0.6. PRMI/PRY gain for prcl is something like 0.01, so since I used a gain of 2 for locking SRX, I started the SRCL gain around 0.02, the final gain ended up being -0.03. I basically just guessed a sign for AS110 triggering. Once I lucked upon a rough lock, I excited the PRM to tune the AS55 angle a few degrees; it was luckily quite close already from the SRY adjustment. AS110 needed a bigger adjustment to get the power into I. (AS55: -40.25->-82.25, AS110: 145->58, but I put AS55 back for PRMI)

I briefly tried locking the DRMI, but I was really just shooting in the dark. I went back and measured various sensing amplitudes/angles in SRMI and PRMI configurations; I'm hoping that I may be able to simulate the right gains/angles for eventual DRMI locking.

  10660   Sat Nov 1 02:13:11 2014 KojiConfigurationLSCLSC settings

I'm leaving the iFO now. It is left with the IR arm mode.

I pretty much messed up LSC configurations for my DRMI locking. If one needs to recover the previous setting, use burtrestore.
I have all records of my LSC settings, so you don't need to preserve it. (Of course we can always use the hourly snapshots
to come back this DRMI setting)

 

  10661   Sat Nov 1 16:06:32 2014 KojiConfigurationLSCDRMI locked

Continued from ELOG 10659


DRMI locking

Following Jenne's elog entry in Aug 2013 (9049), DRMI was configured and locked. The lock was stable, indefinite, and repeatitive.

- DRMI Configuration

Demod phases has not been changed from PRMI

REFL11: WTN 0dB PHASE 21deg, REFL11I x0.1 -> PRCL
REFL55: WTN 21dB PHASE 25deg, REFL55Q x1 -> MICH, REFL55I x1 -> SRCL

AS110 phase was adjusted to maximize Q during the lock: +1deg (AS110Q_ERR was +4400 ~ +5500)

PRCL: GAIN -0.05 FM4/5 ON, Triggered FM 2/3/6/9, Servo trigger: POP22I 20up 10down, No Normaization.
MICH: GAIN +1 FM4/5 ON, Triggered FM 2/3/6/9, Servo trigger: POP22I 20up 10down, No Normaization.

SRCL: GAIN +2 FM4/5 ON, Triggered FM2/3/6/8/9, Servo trigger: AS110Q up 500 down 5, No Normaization.
(FM8 was set to be x2.5 flat gain such that the gain is increased after the lock)

MICH actuation is still BS+PRM and does not include SRCL decoupling yet.
This should be fixed ASAP.

DRMI Calibration

Let's use these entries 

SRM: http://nodus.ligo.caltech.edu:8080/40m/10664
SRM = (19.0 +/- 0.7) x 10 -9/ f2

PRM: http://nodus.ligo.caltech.edu:8080/40m/8255
PRM:  (19.6 +/- 0.3) x 10 -9 / f2 m/counts

BS/ITMs http://nodus.ligo.caltech.edu:8080/40m/8242
BS     = (20.7 +/- 0.1)    x 10 -9 / f2 m/counts
ITMX = (4.70 +/- 0.02)  x 10 -9/ f2
m/counts
ITMY = (4.66 +/- 0.02) x 10 -9/ f2
m/counts

- PRCL Calibration

Lock-in oscillator module 675.13Hz 100 -> +1 PRM

Measurement bandwidth 0.1Hz -> Signal power BW 0.471232 (FLATTOP window)

C1:SUS-PRM_LSC_IN1: 97.45 cnt/rtHz => 4.19 pm/rtHz

REFL11I: 12.55   cnt/rtHz => 3.00e12 cnt/m
REFL11Q:  0.197  cnt/rtHz => 4.70e10 cnt/m
=> 0.90 deg rotated! (GOOD)

REFL33I:  1.63   cnt/rtHz => 3.89e11 cnt/m
REFL33Q:  0.196  cnt/rtHz => 4.68e10 cnt/m
=> 8.32 deg rotated!

REFL55I:  0.0495 cnt/rtHz => 1.18e10 cnt/m
REFL55Q:  0.548  cnt/rtHz => 1.31e11 cnt/m => 84.8 deg rotated! (WHAT!)

REFL165I: 1.20   cnt/rtHz => 2.86e11 cnt/m
REFL165Q: 0.458  cnt/rtHz => 1.09e11 cnt/m
=> 20.9 deg rotated!

- MICH Calibration

Lock-in oscillator module 675.13Hz 100 -> -1 ITMX +1 ITMY

Measurement bandwidth 0.1Hz -> Signal power BW 0.471232 (FLATTOP window)

C1:SUS-ITMX_LSC_IN1: 121.79 cnt/rtHz => 1.26pm/rtHz
C1:SUS-ITMY_LSC_IN1: 121.79 cnt/rtHz => 1.25pm/rtHz

AS55Q:   12.45   cnt/rtHz => 4.96e12 cnt/m (STRONG)

REFL11I:  0.0703 cnt/rtHz => 2.80e10 cnt/m
REFL11Q:  0.0142 cnt/rtHz => 5.66e09 cnt/m
=> 78.5 deg rotated! (WHAT!)

REFL33I:  0.0473 cnt/rtHz => 1.88e10 cnt/m
REFL33Q:  0.0291 cnt/rtHz => 1.16e10 cnt/m => 58.4 deg rotated!

REFL55I:  0.00668cnt/rtHz => 2.66e09 cnt/m
REFL55Q:  0.0261 cnt/rtHz => 1.04e10 cnt/m => 14.4 deg rotated! (OK)

REFL165I: 0.0233 cnt/rtHz => 9.28e09 cnt/m
REFL165Q: 0.0512 cnt/rtHz => 2.04e10 cnt/m => 24.5 deg rotated! (GOOD)

- SRCL Calibration

Lock-in oscillator module 675.13Hz 100 -> SRM

Measurement bandwidth 0.1Hz -> Signal power BW 0.471232 (FLATTOP window)

C1:SUS-SRM_LSC_IN1: 121.77 cnt/rtHz => 5.08pm/rtHz

AS55I:    0.256   cnt/rtHz => 5.05e10 cnt/m
AS55Q:    0.3498  cnt/rtHz => 6.90e10 cnt/m

REFL11I:  0.00624 cnt/rtHz => 1.23e09 cnt/m
REFL11Q:  0.00204 cnt/rtHz => 4.02e08 cnt/m

REFL33I:  0.00835 cnt/rtHz => 1.65e09 cnt/m
REFL33Q:  0.0659  cnt/rtHz => 1.30e10 cnt/m

REFL55I:  0.0201  cnt/rtHz => 3.97e09 cnt/m
REFL55Q:  0.01505 cnt/rtHz => 2.97e09 cnt/m

REFL165I: 0.0238  cnt/rtHz => 4.69e09 cnt/m
REFL165Q: 0.0247  cnt/rtHz => 4.87e09 cnt/m

DRMI Openloop measurements
Servo filter TF measurements

The UGFs were ~250Hz for PRCL and ~100Hz for MICH, and ~250Hz for SRCL, respectively.
MICH showed (presumably) crosscoupling related peak ~350Hz. SRCL had small deviation from the model.
This may also be related to the cross couplig.

The OLTF was modelled by the servo and violin filters TF from foton, estimated TF of the AA/AI filters, and the constant time delay.

Displacement spectra measurement

- PRCL

The OLTF compensation was not actually succesfull at 300Hz, but otherwise the situation is very similar to the one with PRMI.

- MICH

Again the servo compensation at 300Hz was not successful. If we believe that AS55Q is the best MICH sensor, the out-of-loop
noise level of MICH was quite similar to the one in PRMI. We should try to use AS55Q for DRMI MICH for investigation purpose
to see which REFL signal has the best MICH quality. REFL165 seems to be iproved in the signal amplitude. Can we use this
for locking now?

- SRCL

It is in fact difficult to tell what is the correct out-of-loop noise level. AS55I has too much contamination from MICH and is not indicating
useful info. This measurement should be tried once the sensor diagonalization is done.

REFL55I is not seeing anything real abobe 30Hz. We should be able to reduce the UGF and the servo gain.

The absolute motion level of SRCL is something similar to PRCL, rather than MICH.

 

Attachment 1: DRMI_PRCL_OLTF.pdf
DRMI_PRCL_OLTF.pdf
Attachment 2: DRMI_MICH_OLTF.pdf
DRMI_MICH_OLTF.pdf
Attachment 3: DRMI_SRCL_OLTF.pdf
DRMI_SRCL_OLTF.pdf
Attachment 4: DRMI_PRCL_SPE.pdf
DRMI_PRCL_SPE.pdf
Attachment 5: DRMI_MICH_SPE.pdf
DRMI_MICH_SPE.pdf
Attachment 6: DRMI_SRCL_SPE.pdf
DRMI_SRCL_SPE.pdf
  10664   Mon Nov 3 17:56:57 2014 KojiUpdateLSCSRM calibration

SRM Calibration

After the DRMI measurements on Friday, SRY cavity was locked in order to compare ITMY and SRM actuators.

SRY cavity was locked with AS55Q ->  SRM servo with gain of +10?
(My memory is fading. I tried +50 and noticed it was saturated at the limiter. So I thought it was 10)

Then the transfer functions between SRM->AS55Q TF and ITMY->AS55Q TF were measured.

The ratio between two transfer functions was obtained as seen in the second attachment.
The average at f<100Hz was 4.07 +/- 0.15. Therefore the calibration is ... as you can find below


SRM: http://nodus.ligo.caltech.edu:8080/40m/10664
SRM = (19.0 +/- 0.7) x 10 -9/ f2

PRM: http://nodus.ligo.caltech.edu:8080/40m/8255
PRM:  (19.6 +/- 0.3) x 10 -9 / f2 m/counts

BS/ITMs http://nodus.ligo.caltech.edu:8080/40m/8242
BS     = (20.7 +/- 0.1)    x 10 -9 / f2 m/counts
ITMX = (4.70 +/- 0.02)  x 10 -9/ f2
m/counts
ITMY = (4.66 +/- 0.02) x 10 -9/ f2
m/counts

Attachment 1: SRY_SRM_CALIB_RAW.pdf
SRY_SRM_CALIB_RAW.pdf
Attachment 2: SRY_SRM_CALIB.pdf
SRY_SRM_CALIB.pdf
  10668   Wed Nov 5 01:58:54 2014 ericqUpdateLSC3F RFPD RF spectra

Given the checkout of the aLIGO BBPDs happening (aLOG link), wherein the PDs were acting funny, and Koji has made some measurements determining that intermodulation/nonlinearity of circuitry can corrupt 3F signals, I've made a similar measurement of the RF spectra of REFL165 when we're locked on DRMI using 1F signals. Maybe this could give us insight to our bad luck using REFL165...

In essence, I plugged the RF output of the PD into an AG4395, through a 10dB attenuator and downloaded the spectrum. I also did REFL33 as a possible comparison and because why not. The attached plots have the 10dB accounted for; the text files do not. 

REFL165 (Exposed PCB BBPD):

REFL165_DRMIspectrum.png

(What is all that crap between 8 and 9 fmod?)

REFL33 (Gold Box resonant RFPD):

REFL33_DRMIspectrum.png

Attachment 1: Nov52014_3fPD_DRMIspectra.zip
  10669   Wed Nov 5 11:09:44 2014 KojiUpdateLSC3F RFPD RF spectra

If you look at the intermodulation at 14 (4+10) and 16 (6+10), 15 (5+10) would make any problem, thanks to the notch at 1f and 5f.

BUT, this absolute level of 165MHz is too tiny for the demodulator. From the level of the demodulated signal, I can say REFL165 has
too little SNR. We want to amplify it before the demodulator.

Can you measure this again with a directional coupler instead of the direct measurement with an attenuator?
The downstream has bunch of non-50Ohm components and may cause unknown effect on the tiny 165MHz signal.
We want to measure the spectrum as close situation as possible to the nominal configuration.

90MHz crap is the amplifier noise due to bad power bypassing or bad circuit shielding.

I have no comment on REFL33 as it has completely different amplification stages.

  10672   Wed Nov 5 18:08:00 2014 ericqUpdateLSCPSL and AUXY beatnote in IR found

Green beatnotes recovered.

It was just a matter of aligning the arm greens and PSL greens on the PSL table. I suppose something knocked the PSL alignment out of whack... I was also able to simultaneously see the green beatnote and IR beatnote respond to Yend laser temperature. 

Locked arms on POX/POY, checked RMS of ALS-BEAT[X/Y]_FINE_PHASE_OUT_HZ channels. 

  • ALSY: 300Hz RMS
  • ALSX: 700Hz RMS

These seem fine. Locked CARM and DARM on ALS, found IR resonances. 

ALS is back in business 

  10673   Wed Nov 5 22:25:42 2014 ericqUpdateLSC3F RFPD RF spectra

 

Now that I have followed the chain, the PD signal is indeed being amplified at the LSC rack. It goes into a ZFL-1000LN+ amplifier (~23dB gain at 165MHz and 15V supply), followed by a SHP-100 high pass filter, and then enters the RF IN of the demod board. 

I repeated the measurement in two spots.

First, I took a spectrum of the RF MON of the REFL165 demod board during DRMI lock; this was input-referred by adding 20dBm. 

Second, I inserted a ZFDC-10-5 coupler between the high pass and the RF input of the demod board. This was input-referred by adding 10dBm. 

REFL165_demod_DRMIspectrum.png

My calibration isn't perfect; the peaks above the high pass corner seem to be different by a consistent amount, but within a few dBm. 

Thus, it looks like the demod board is getting a little under -40dBm of 165MHz signal at its input. 

  10674   Thu Nov 6 01:48:30 2014 diegoUpdateLSCIR Resonance Script Status

 Tonight I tried some more tests on the script; it seems to work better, with both performance and robustness improved, although the Xarm behaved badly almost all the time. I did not perform all the tests I wanted because the ALS lock was pretty unstable tonight (not only because of the X arm), with more than a few lock losses; after the last lock loss, however, I couldn't restore the Xarm. I'll do some more tests as soon I can recover it, or post the result of the first batch of tests.

In addition, I encountered the following error multiple times, but I have no idea about what could it be:

Thu Nov 06 02:00:13 PST 2014
medmCAExceptionHandlerCb: Channel Access Exception:
Channel Name: Unavailable
Native Type: Unavailable
Native Count: 0
Access: Unavailable
IOC: Unavailable
Message: Virtual circuit disconnect
Context: fb.martian.113.168.192.in-addr.arpa:5064
Requested Type: TYPENOTCONN
Requested Count: 0
Source File: ../cac.cpp
Line number: 1214
 

  10675   Thu Nov 6 01:58:55 2014 KojiUpdateLSC3F RFPD RF spectra

Where is the PD out spectrum measured with the coupler???

  10676   Thu Nov 6 03:29:00 2014 diegoUpdateLSCIR Resonance Script Status

EDIT on X arm: I found different settings in C1SUS_ITMX, with respect to ETMX, ITMY and ETMY (namely LSC/DAMP is OFF and LSC/BIAS is ON); I don't know if this is intended or for some reason ITMX was not recovered properly after the lock loss, so I didn't change anything, but it may be worth looking into that.

 

Still no luck in recovering the X arm, I am giving up for tonight; honestly I didn't try many things, as I don't know well the system and didn't want to mess things up.

 

Preliminary results so far:

I confirm that the best settings for the ramp of the ALS scan are 20s and 500 points; this causes however the script to be fairly slow (80s for the scan/data collection, 7s for the coarse peak finding, 17s for the fine peak finding, total ~2 min); in the best cases the TR*_OUT obtained is around 0.90, as shown in the first plot (early in the evening, all the following plots are in chronological order, if that can help finding the reason for the X arm misbehaviour...):

AllPython_findIRresonance_WL_ramp_20_500_0.png

 

However, after a few minutes somehow the TR*_OUT went down a bit, without any kind of intervention; also, it is visible the instability of the X arm:

AllPython_findIRresonance_WL_ramp_20_500_0_1.png

 

Even when X arm was somewhat stable, its performance and robustness were (far) worse than the Y arm ones:

AllPython_findIRresonance_WL_ramp_20_500_6.png

The following plot shows (about the Y arm only) that there is still some margin, as the maximum value of TRY_OUT is not completely kept at the end of the procedure:

AllPython_findIRresonance_WL_ramp_20_500_7_Y_rise.png

 

Finally the last plot I managed to obtain, before the X arm went completely crazy...

AllPython_findIRresonance_WL_ramp_20_500_9.png

 

The next step, after obviously figuring out the X arm situation, is to try some averaging during the fine scan, I don' t know if this will improve the situation, however it shouldn't impact on the execution time. Tomorrow I'll post something more detailed on the script itself and the wavelet implementation.

  10679   Thu Nov 6 11:49:58 2014 ericqUpdateLSC3F RFPD RF spectra

Quote:

Where is the PD out spectrum measured with the coupler???

 The "coupled" port of the coupler went to the AG4395 input, the output of the Highpass is connected to the "IN", and the "OUT" goes to the demod board. 

  10682   Thu Nov 6 14:41:49 2014 KoijUpdateLSC3F RFPD RF spectra

That's not what I'm asking.

Also additional cables are left connected to the signal path. I removed it.

  10683   Fri Nov 7 02:21:12 2014 ericqUpdateLSC3F RFPD RF spectra

 

After some enlightening conversation with Koji, we figured that the RF amplifier in the REFL165 chain is probably being saturated (the amp's 1dB compression is at +3dBm, has 23dB gain, and there are multiple lines above -20dBm coming out of the PD). I took a few more spectrum measurements to quantify the consequences, as well as a test with the highpass connected directly to the PD output, that should reduce the power into the amplifier. However, I am leaving everything hooked back up in its original state (and have removed all couplers and analyzers...)

I also took some DRMI sensing measurements. In the simple Michelson configuration, I took TFs of each ITMs motion to AS55Q to make sure the drives were well balanced. They were. Then, in the DRMI, I took swept sine TFs of PRCL, SRCL and differential ITM MICH motion to the Is and Qs of AS55 and all of the REFLs. I constrained the sweeps to 300Hz->2kHz; the loops have some amount of coupling so I wanted to stay out of their bandwidth. I also took a TF of the pure BS motion and BS-PRM MICH to the PDs. From these and future measurements, I hope to pursue better estimates of the sensing matrix elements of the DRMI DoFs, and perhaps the coefficients for compensating both SRCL and PRCL out of BS motion. 

I'm leaving analysis and interpretation for the daytime, and handing the IFO back to Diego...

  10685   Fri Nov 7 14:41:18 2014 ericqUpdateLSC3F RFPD RF spectra

Quote:

 After some enlightening conversation with Koji, we figured that the RF amplifier in the REFL165 chain is probably being saturated.

The measurements I took yesterday bear this out. However, even putting the high-pass directly on the PD output doesn't reduce the signal enough to avoid saturating the amplifier.

We need to think of the right way to get the 165MHz signal at large enough, but undistorted, amplitude to the demod board. 


 The current signal chain looks like:

AS Table                                  LSC RACK
[ PD ]----------------------------------->[ AMP ]------>[ 100MHzHPF ]----->[ DEMOD ]
      (1)                                        (2)                 (3)

I previously made measurements at (3). Let's ignore that. 

Last night, I took measurements with a directional coupler at points (1) and (2), to see the signal levels before and after the amplifier. I divided the spectrum at (2) by the nominal gain of the amplifier, 23.5dB; thus if everything was linear, the spectra would be very similar. This is not the case, and it is evident why. There are multiple signals stronger than -20dBm, and the amplifier has a 1dB compression point of +3dBm, so any one of these lines at 4x, 6x and 10x fMod is enough to saturate. 

 165_ampSaturation.png


I also made a measurement at point 4 in the following arrangement, in an attempt to reduce the signal amplitude incident on the amplifier.  

AS Table                                           LSC RACK
[ PD ]->[ 100MHzHPF ]----------------------------------->[ AMP ]--------->[ DEMOD ] 
                                                                (4) 

 Though the signals below 100MHz are attenuated as expected, the signal at 110MHz is still too large for the amplifier. 

165_HPatPD.png


Minicircuits' SHP-150 only has 13dB suppression at 110MHz, which would not be enough either. SHP-175 has 31dB suppression at 110MHz and 0.82dB at 160MHz, maybe this is what we want.

  10686   Fri Nov 7 16:15:53 2014 JenneUpdateLSC3F RFPD RF spectra

I have found an SHP-150, but no SHP-175's (also, several 200's, and a couple of 500's).

Why do you say the SHP-150 isn't enough?  The blue peak at 10*fmod in your plot looks like it's at -12 dBm.  -13 dB on top of that will leave that peak at -25 dBm.  That should be enough to keep us from saturation, right?  It's not a lot of headroom, but we can give it a twirl until a 175-er comes in.  

Koji also suggests putting in a 110 MHz notch, combined with either an SHP-150 or SHP-175, although we'll have to measure the combined TF to make sure the notch doesn't spoil the high pass's response too much.

Quote:

165_HPatPD.png


Minicircuits' SHP-150 only has 13dB suppression at 110MHz, which would not be enough either. SHP-175 has 31dB suppression at 110MHz and 0.82dB at 160MHz, maybe this is what we want.

 

  10687   Fri Nov 7 17:44:10 2014 diegoUpdateLSCIR Resonance Script Status

Yesterday I did some more tests with a modifies script; the main difference is that scipy's default wavelet implementation is quite rigid, and it allows only very few choices on the wavelet. The main issue is that our signal is a real, always positive symmetrical signal, while wavelets are defined as 0-integral functions, and can be both real or complex, depending on the wavelet; I found a different wavelet implementation, and I combined it with some modified code from the scipy source, in order to be able to select different wavelets. The result is the wavelet_custom.py module, which lives in the same ALS script directory and it is called by the script. In both the script and the module there the references I used while writing them. It is now possible to select almost any wavelet included in this custom module; "almost" means that the scipy code that calls the find_peaks_cwt routine is picky on the input parameters of the wavelet function, I may dig into that later. For the last tests, instead of using a Ricker wavelet (aka Mexican hat, or Derivative of Gaussian Order 2), I used a DOG(6), as it also has two lesser positive lobes, which can help in finding the resonance; the presence of negative lobes is, as I said, unavoidable. I attach an example of the wavelet forms that are possible, and in my opinion, excluding the asymmetric and/or complex ones, the DOG(6) seems the best choice, and it has provided slightly better results. There are other wavelet around, but they are not included in the module so I should implement them myself, I will first see if they seem fitting our case before starting writing them into the module. However, the problem of not finding the perfect working point (the "overshoot-like" plot in my previous elog) is not completely solved. Eric had a good idea about that: during the fine scan, the the PO*11_ERR_DQ signals should be in their linear range, so I could also use them and check their zero crossing to find the optimal working. I will be working on that.

Attachment 1: wavelets.nb.zip
  10689   Sat Nov 8 11:35:05 2014 ranaUpdateLSC3F RFPD RF spectra

 

 I think 'saturation' here is a misleading term to think about. In the RF amplifiers, there is always saturation. What we're trying to minimize is the amount of distorted waveforms appearing at 3f and 15f from the other large peaks. Usually for saturation we are worried about how much the big peak is getting distorted; not the case for us.

  10690   Sat Nov 8 16:01:32 2014 ericqConfigurationLSCDRMI sensing

Here are some preliminary results from the sensing sweeps I did the other night. 

Notes:

  • The analog AS55I signal chain is almost certainly busted in some way. This would also explain the odd looking error signals in SRX, and was actually hypothesized by Koji when discussing the SRX oddness. 
  • I used the same mirror calibration numbers from Koji's recent Elogs to turn these into counts/m.
  • MICH was excited via differential ITM motion.  I also performed a TF with BS driven MICH, with the compensating PRM output matrix in place, and it looks different, but I haven't looked too deeply into it yet. 
  • The angles plotted are in regard to the analog I and Q signals (i.e., I took TFs to I_ERR and Q_ERR and then unrotated by the digital rotation angle); this is why I suspect AS55I is broken, as all of the signals are entirely in the analog Q.
  • The amplitudes seem to be roughly consistent with Koji's recent observations. 
  • I still need to cut out the violin-filter-corrupted data points to quote the sensing elements with error bars...

Plots!

 REFL11.pngREFL33.png

REFL55.pngREFL165.png

AS55.png

xml files, and DttData matlab script used to generate these plots is attached. 

Attachment 6: DRMIsensing.zip
  10692   Mon Nov 10 18:11:57 2014 ericqUpdateLSC3F RFPD RF spectra

 Jenne and I measured the situation using a SHP-150 directly attached to the REFL165 RF output, and at first glance, the magnitude of the 165MHz signal seems to not be distorted by the amplifier. 

 165signals.pdf

We will soon investigate whether 165 signal quality has indeed improved. 

  10693   Mon Nov 10 18:23:10 2014 ericqConfigurationLSCDRMI sensing

ARG, I accidentally permuted the digital demod angles. This significantly weakens the argument for believing AS55I is broken... In fact, Jenne and I did some investigations this afternoon that showed that the channel is indeed working. SRX error signal strangeness remains unexplained, however. 

Also, I have yet to compensate for the gain of the violin filters; the actuator calibration numbers I used were for the SUS-LSC FMs, not the LSC FMs where I was injecting. New measurements will be taken soon, as well, since REFL165 is hopefully improved. 

Corrected plots are below. 

REFL11.pngREFL33.png

REFL55.pngREFL165.png

AS55.png

  10695   Tue Nov 11 01:38:23 2014 KojiUpdateLSCNotch at 110MHz

To further reduce the RF power at 110MHz in the REFL165 chain, I made a twin-t notch in a pomona box.

It is tuned at 110.66MHz.

The inductor is Coil Craft 5mm tunable (164-09A06SL 100-134nH).
Without the 10Ohm resister (like a usual notch), the dip was ~20dB. With this configuration, the notch of -42dB was realized.

Q >> Please measure the RF spectrum again with the notch.

 

Attachment 1: twin_t_notch.pdf
twin_t_notch.pdf
Attachment 2: notch_tf.pdf
notch_tf.pdf
  10696   Tue Nov 11 03:48:46 2014 JenneUpdateLSC3f DRMI

I was able to lock the DRMI on 3f signals this evening, although the loops are not stable, and I can hear oscillations in the speakers.  I think the big key to making this work was the placement of the SHP-150 high pass filter at the REFL165 PD, and also the installation of Koji's 110 MHz notch filter just before the amplifier, which is before the demod board for REFL165.  These were done to prevent RF signal distortion.

DRMI 3f:   With DRMI locked on 1f (MICH gain = 1, PRCL gain = -0.05, SRCL gain = 2, MICH = 1*REFL55Q, PRCL = 0.1*REFL11I, SRCL = 1*REFL165I), I excited lines, and found the signs and values for 3f matrix elements.  I was using the same gains, but MICH = 0.5*REFL165Q, PRCL = 0.8*REFL33I and SRCL = -0.2*REFL165I.  Part of the problem is likely that I need to include off-diagonal elements in the input matrix to remove PRCL from the SRCL error signal. 

With the DRMI locked on 1f, I took a sensing matrix measurement.  I don't think we believe the W/ct of the photodiode calibration (we need to redo this), but otherwise the sensing matrix measurement should be accurate.  Since the calibration of the PDs isn't for sure, the relative magnitude for signals between PDs shouldn't be taken as gospel, but within a single PD they should be fine for comparison. 

As a side note, we weren't sure about the MICH -> ITMs balancing, so we checked during a MICH-only, and with the locking apparatus we are unable to measure a difference between 1's for both ITMs in the output matrix, and 1 for ITMX and 0.99 for ITMY.  So, we can't measure 1% misbalances in the actuator, but we think we're at least pretty close to driving pure MICH. 

We kind of expect that SRCL should only be present in the 55 and 165 PDs, although we see it strongly in all of the REFL PDs.  Also, PRCL and SRCL are not both lined up in the I-phase.  So, I invite other people to check what they think the sensing matrix looks like. 

  • The excitation lines (and matching notches) were on from 12:14am (
  • Nov 11 2014 08:14:00 UTC / GPS 1099728856) to 12:20am (
  •  
  • Nov 11 2014 08:20:00 UTC / GPS 
  • 1099729216) for 360sec. 
  • MICH was driven with 800 counts at 675.13 Hz, with +1*ITMY, -1*ITMX. 
  • PRCL was driven with 1000 counts at 621.13 Hz with the PRM. 
  • SRCL was driven with 800 counts at 585.13 Hz using the SRM. 

All 3 degrees of freedom have notches at all 3 of those frequencies in the FM10 of the filter banks (and they were all turned on).  During this time, DRMI was locked with 1f signals. 

DRMI sensing matrix:

 SensMatMeas_10Nov2014_DRMI.png

Earlier in the evening, I also took a PRMI sensing matrix, with the PRMI locked on REFL33 I&Q.  Watch out for the different placement of the plots - I couldn't measure AS55 in the DRMI case, since cdsutils.avg freaked out if I asked for more than 14 numbers (#PDs * #dofs) at a time.

SensMatMeas_10Nov2014_PRMI.png

Rana, Koji and I were staring at the DRMI sensing matrix for a little while, and we aren't sure why PRCL and SRCL aren't co-aligned, and why they aren't orthogonal to MICH.  Do we think it's possible to do something to digitally realign them?  Will the solution that we choose be valid for many CARM offsets, or do we have to change things every few steps (which we don't want to do)? 

Things to work on:

* Reanalyze DRMI sensing matrix data from 12:14-12:20am. 

* Make a simulated scan of higher order mode resonances in the arm cavities.  Is it possible that on one or both sides of the CARM resonance we are getting HOM resonances of the sidebands? 

* Figure out how to make DRMI 3f loops stable.

* Try CARM offset reduction with DRMI, and / or PRMI on REFL 165.

ELOG V3.1.3-