40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 98 of 341  Not logged in ELOG logo
ID Date Author Typedown Category Subject
  6806   Tue Jun 12 17:29:28 2012 DenUpdateCDSdq channels

All PEM and IOO DQ channels disappeared. These channels were commented in C1???.ini files though I've uncommented them a few weeks ago. It happened after these models were rebuild, C1???.ini files also changed. Why?

I added the channels back. mx_stream died on c1sus after I pressed DAQ reload on medm screen. For IOO model it is even worse. After pressing DAQ Reload for C1IOO model DACQ process dies on the FB and IOO machine suspends.

I rebooted IOO, restarted models and fb. Models work now, but there might be an easier way to add channels without rebooting machines and demons.

  6807   Tue Jun 12 17:46:09 2012 JenneUpdateComputersrtcds: command found

Quote:

Quote:

We can't compile any changes to the LSC or the GCV models since Jamie's new script / program isn't found.  I don't know where it is (I can't find it either), so I can't do the compiling by hand, or point explicitly to the script.  The old way of compiling models in the wiki is obsolete, and didn't work :(

Sorry about that.  I had modified the path environment that pointed to the rtcds util.  The rtcds util is now in /opt/rtcds/caltech/c1/scripts/rtcds, which is in the path.  Starting a new shell should make it available again.

 Added TRX and TRY and POY11_I_ERR and POX11_I_ERR to the c1lsc.mdl using a new-style DAQ Channels block, recompiled, installed, started the model, all good.  Restarted the daqd on the framebuilder, and everything is green.  I can go back and get recorded data using dataviewer (for the last few minutes since I started fb), so it all looks good.

Note on the new DAQ Channels block:  Put the text block (from CDS_PARTS) at the same level as the channel you want to save, and name it exactly as it is in the model.  The code-generator will add the _DQ for you.  i.e. if you define a channel "TRY_OUT_DQ" in the lsc model, you'll end up with a channel "C1:LSC-TRY_OUT_DQ_DQ".

  6808   Tue Jun 12 20:35:46 2012 yutaUpdateGreen Lockingc1gcv recompiled

[Jamie, Yuta]

We recompiled c1gcv because the order of the channels were confusing. We found some change in the phase rotation module when we did this.

I did some cabling and checked each signals are actually going to the right channel. I labeled all the cables I know, which go into the AA chasis for ADC1 of c1ioo machine.

Below is the list of the channels. If you know anything about "unknown" channels, please let me know.

Current channel assignments for ADC1 of c1ioo machine:
  Red ones were added today. Green ones existed in the past, but channel assignment were changed.

cable

# on AA chassis name in Simulink channel name

connected
but unknown

J1A    
   
not connected J1B    
   
not connected J2 adc_1_2 C1:ALS-XARM_BEAT_DC
not connected adc_1_3 C1:ALS-YARM_BEAT_DC
connected
but unknown
J3    
   
connected
but unknown
J4    
   
connected
but unknown
J5    
   
connected
but unknown
J6    
   
connected
but unknown
J7    
   
beat Y arm fine I J8A adc_1_14 C1:ALS-BEATY_FINE_I
beat Y arm fine Q adc_1_15 C1:ALS-BEATY_FINE_Q
not connected J8B    
   
connected
but unknown
J9A    
   
not connected J9B    
   
connected
but unknown
J10    
   
connected
but unknown
J11    
   
not connected J12 adc_1_22 C1:ALS-BEATX_COARSE_I
not connected adc_1_23 C1:ALS-BEATX_COARSE_Q
not connected J13 adc_1_24 C1:ALS-BEATX_FINE_I
not connected adc_1_25 C1:ALS-BEATX_FINE_Q
beat Y arm coarse I
J14 adc_1_26 C1:ALS-BEATY_COARSE_I
beat Y arm coarse Q adc_1_27 C1:ALS-BEATY_COARSE_Q
not connected J15 adc_1_28 Broken! Don't use this!!
adc_1_29 (not broken)
not connected J16A adc_1_30 (not broken)
adc_1_31 Broken? Funny signal.
not connected J16B    
   

Memorandum for me:
  Recompiling procedure;

ssh c1ioo

rtcds make c1gcv
rtcds install c1gcv
rtcds start c1gcv

Attachment 1: c1gcv20120612-2.png
c1gcv20120612-2.png
  6809   Tue Jun 12 23:18:18 2012 yutaUpdateGreen LockingI-Q signals for the beat

[Mengyao, Yuta]

Yes!! We have I-Q signals for the beat!!

What we did:
  1. Aligned Y arm to the Y end green incident beam. The transmission to the PSL was about 195 uW.

  2. Aligned IR beam to the Y arm by adjusting PZTs and got the transmission, C1:LSC-TRY_OUT ~ 0.86.

  3. Aligned green optics on the PSL table to get the beat signal. The beat was found when;

  PSL laser temperature on display: 31.41 deg C
  C1:PSL-FSS_SLOWDC = 1.43
  Y end laser "T+": 34.049 deg C
  Y end laser "ADJ": 0
  Y end laser measured temperature: 34.14 deg C
  C1:GCY-SLOW_SERVO2_OFFSET = 29950
  Y end slow servo: off (was on)

  4. Connected the beat PD output to the beatbox.

  5. Kicked ETMY position to change the cavity length and while the ringdown, we run pynds to get data. We plotted C1:ALS-BEATY_FINE_I_ERR vs C1:ALS-BEATY_FINE_Q_ERR, and C1:ALS-BEATY_COARSE_I_ERR vs C1:ALS-BEATY_COARSE_Q_ERR (below). We got nice circle as expected.

FINEIQplot20120612.pngCOARSEIQplot20120612.png

Current setup:
  Only AA filers are put between the output of the beatbox and the ADC.

beatysetup20120612.png

  6810   Wed Jun 13 02:11:59 2012 yutaUpdateGreen Lockingmy first modescan (sort of)

I stabilized Y arm length by using only I phase coarse signal from the beat(C1:ALS-BEATY_COARSE_I_ERR).
I sweeped the arm length by injecting 0.05Hz sine wave from C1:ALS_OFFSETTER2_EXC.
Below is the plot of TRY and the error signal(ideally, Y arm length) while the sweep.

modescan20120612_1.png

I couldn't hold the arm length tight, so you can see multiple peaks close to each other.
We need to
  - adjust offsets
  - adjust rotation phase of I-Q mixing
  - adjust servo filters

to hold the length tighter.

Also, I couldn't sweep the Y arm length very much. I need to calibrate, but to do the modescan for many FSRs, we need to
  - introduce automatic phase optimizing system
There were sin/cos function in the CDS_PARTS, so I think we can feedback I_ERR to control rotation phase of I-Q mixing.

  6811   Wed Jun 13 02:24:02 2012 ranaUpdateGreen Lockingmy first modescan (sort of)

 That sounds goofy.

With the delay line technique, you can get a linear signal over 50 MHz with no phase shifting. What is with all this I/Q stuff?

  6812   Wed Jun 13 03:03:38 2012 yutaUpdateGreen Lockingmy first modescan (sort of)

Linear range df of the delay line technique is about df ~ c/(2D). So, the linear range for the fine signal(delay line length D=30m) is about 5 MHz.
Arm cavity FSR = c/(2L) = 3.7 MHz.
So, I think we need phase shifting to do mode scan for more than 2 FSRs by holding the arm length finely with fine servo.
For the coarse (D=1.5m), the linear range is about 100 MHz, so if we can do mode scan using coarse servo, it is OK.

In any case, I think it is nice to have linear signal with fixed slope even if we don't adjust the phase every time.

Quote:

 That sounds goofy.

With the delay line technique, you can get a linear signal over 50 MHz with no phase shifting. What is with all this I/Q stuff?

 

  6813   Wed Jun 13 11:10:56 2012 ranaUpdateGreen Lockingmy first modescan (sort of)

You can easily calculate whether or not the coarse readout will work by thinking about the scan resolution you need given the ADC dynamic range and the whitening filter that you use.

  6814   Wed Jun 13 11:19:05 2012 steveUpdateSUSIDC receptacles clamped

The MC_ IDC 64 pin cables from sat. amplifiers to junction-interface-board towards  whitening - dewhitening at the back of rack 1 X 5 are finally  clamped with

All other sus cables of the same kind have the correct short latch arm to lock them in for reliable contact.

Attachment 1: IMG_1341.JPG
IMG_1341.JPG
  6815   Wed Jun 13 17:39:13 2012 yutaUpdateGreen Lockingcalibrating the beatbox

[Jenne, Yuta]

We put 0 dBm sine wave to the RF input of the beatbox and linear-sweeped frequency of the sine wave from 0 to 200 MHz using network analyzer (Aligent 4395A).
(We first tried to use 11 MHz EOM marconi)

Whlile the sweep, we recorded the output of the beatbox, C1:ALS-BEATY_(FINE|COARSE)_(I|Q)_IN1_DQ. We made them DQ channels today. Also, we put gain 10 after the beatbox before ADC for temporal whitening filter using SR560s.

We fitted the signals with sine wave using least squares fit(scipy.optimize.leastsq).
Transision time of the frequency from 200 MHz to 0 Hz can be seen from the discontinuity in the time series. We can convert time to frequency using this and supposing linear sweep of the network analyzer is perfect.

Plots below are time series data of each signal(top) and expansion of the fitted region with x axis calibrated in frequency (bottom).

ALS-BEATY_COARSE_I_IN1_DQ.pngALS-BEATY_COARSE_Q_IN1_DQ.png
ALS-BEATY_FINE_I_IN1_DQ.pngALS-BEATY_FINE_Q_IN1_DQ.png


We got

C1:ALS-BEATY_COARSE_I_IN1_DQ = -1400 sin(0.048 freq + 1.17pi) - 410
C1:ALS-BEATY_COARSE_Q_IN1_DQ = 1900 sin(0.045 freq + 0.80pi) - 95

C1:ALS-BEATY_FINE_I_IN1_DQ = 1400 sin(0.89 freq + 0.74pi) + 15
C1:ALS-BEATY_FINE_Q_IN1_DQ = 1400 sin(0.89 freq + 1.24pi) - 3.4

(freq in MHz)

The delay line length calculated from this fitted value (supposing speed of signal in cable is 0.7c) is;

  D_coarse = 0.7c * 0.048/(2*pi*1MHz) =  1.6 m
  D_fine = 0.7c * 0.89/(2*pi*1MHz) = 30 m

So, the measurement look quite reasonable.

FINE signals looks nice because we have similar response with 0.5pi phase difference.
For COARSE, maybe we need to do the measurement again because the frequency discontinuity may affected the shape of the signal.

  6816   Thu Jun 14 01:36:34 2012 yutaUpdateGreen Lockingcan't scan Y arm for 1FSR

[Jenne, Koji, Yuta]

We tried to scan of the Y arm but we couldn't scan for more than 1FSR.
In principle, we can do that because the error signal we are using, C1:ALS-BEATY_COARSE_I_IN1, has the range of ~ 40 MHz, which is about 10FSR (see elog http://nodus.ligo.caltech.edu:8080/40m/6815).

ALS stays for more than 10 min when we don't do the scan. If we put some offset gradually from C1ALS-OFFSETTER2, the lock breaks.
We monitored PZT output of the Y end laser, C1:GCY-SLOW_SERVO1_IN1, but it stayed in the range when scanning. So, there must be something wrong in the ALS loop.

Current in-loop arm length fluctuation is about 0.1 nm RMS (0.5 counts RMS).
Below is the spectrum of the error signal when the ALS is off(green) and on (pink,red). Below ~ 50 Hz, the measurement of the Y arm length is limited by ADC noise (~ 2uV/rtHz).
BEATY_COARSE_LoopOnOff.png

  6818   Thu Jun 14 21:37:37 2012 yutaUpdateGreen Lockingsucceeded in 1FSR mode scan

[Jenne, Yuta]

We couldn't scan the Y arm for 1FSR last night because the ALS servo breaks while sweeping.
We thought this might be from the amplitude fluctuation of the beat signal. The amplitude of the beat signal goes into the beatbox was about -5 dBm, which is not so enough for the beatbox to get good LO. So, we put an amplifier (and attenuators) and the amplitude became +1 dBm. The range beatbox can handle is about -3 dBm to +3 dBm, according to our calculation.

This increased stability of the lock, and we could scan the arm for 1FSR. Below is the plot of scanned ALS error signal (blue), Y arm IR PDH signal (green) and TRY (red).

YarmScan20120614.png

For each slope, we can see two TEM00 peaks, some higer order modes(may be 01, 02, 02) and sidebands (large 11MHz, small 55MHz?).

We couldn't scan for more. This is still a mystery.

Also, we need to reduce residual Y arm length fluctuation more because we get funny TRY peak shape.

Scan speed:
  For C1:ALS-BEATY_COARSE_I_IN1, 1 count stands for 0.21 nm(see elog #6817). We sweeped 4000 peak to peak in 50 sec. So, the scan speed is about 17 nm/sec.
  This means it takes about 0.06 sec to cross resonant peak.
  Cavity build up time is about 2LF/(pi*c) ~ 40 usec. So, the scan is quasi-static enough.
  Characteristic time scale for the Y end temperature control is about 10 sec, so Y end frequency is following the Y arm length change with temperature control.

  Currently, sampling frequency of DQ channels are 2048 Hz. This means we have 100 points in a TRY peak. I think this is enough to get a peak height.

Next step:
  - Reduce RMS. We are trying to use a whitening filter.
  - Find why we can't scan more. Why??
  - ETMY coil gains may have some unbalance. We need to check
  - Characterize Y end green frequency control. Koji and I changed them last week (see elog #6776).
  - Calculate positions of RF SBs and HOMs and compare with this result.

  6819   Fri Jun 15 00:50:54 2012 yutaUpdateGreen Lockingscanned Y arm for 5FSR

I scanned Y arm for 5FSR (below).
I could done this after I put a whitening filter.
Currently, whitening filter between the beatbox and AA filter is made of

  Ponoma blue box(passive filter with zero at 1 Hz, pole at 10 Hz) + SR560(flat gain 100)

I couldn't do more than 5FSR because SR560 overloads. I checked it by staring at the indicator during the scan.
Reason why we kept loosing lock last night was the overload of  SR560. Mystery solved!

Anyway, 5FSR is enough.
Our next step is to reduce residual arm length fluctuation.

YarmScan20120614_2.png


Also, I increased the alingnment of IR. So, the higher order modes are less than the last scan.

  6820   Fri Jun 15 01:53:05 2012 KojiUpdateGreen Lockingscanned Y arm for 5FSR

Interesting. It seems for me that there is a dependence of the noisiness as the beat frequency is scanned.

As you increase (or decrease?) the offset, C1:ALS-BEATY-COARSE_I_IN1 becomes bigger and more crisp.
The resulting out-of-loop stability also seems to be improved as you can see from the crispness of the PDH signal.

Do you find why this happens? Is this because the beat S/N depends on the beat frequency due to the PD noise?

 

  6821   Fri Jun 15 13:33:39 2012 yutaUpdateGreen LockingADC noise contribution to ALS

ADC noise is not a limiting noise source in a current ALS setup.

Below is the calibrated spectrum of C1:ALS-COARSE_I_ERR when
  Y arm swinging with just damping (red; taken last night)
  terminated before AA (green)
  blocked PSL green beam (blue)

Blue and green curve tells us that noise from the beat PD to ADC is not contributing to the Y arm length sensing noise.

YarmALSnoise20120615.png

  6822   Sat Jun 16 01:03:21 2012 yutaUpdateGreen Lockingused longer delay line for mode scan

[Mengyao, Yuta]

Last night, I used 1.5 m delay line COARSE and got 5FSR mode scan. The range 5FSR was limited by the range of SR560.
So, this time, we used 6.4 m(21 feet) cable as a delay line for FINE servo. This should increase the sensitivity by factor of 4. But the range will be 4 tmes smaller, ~ 1.3FSR.

Below is the plot of the mode scan.
You can see the peak height difference between TEM00s, but it's just from the resolution of pixels.

You still can see noisiness goes up when blue plot goes down. But this time, 2000 stands for 27 MHz and -2000 stands for 15 MHz in the beat frequency because we flipped the filter gain this time.
Last night, the top of the triangle was about 40 MHz and bottom was about 60 MHz.


YarmScan20120615.png

We are going to derive mode-matching and some cavity parameters using this plot.

  6823   Sat Jun 16 12:03:41 2012 ZachUpdateGreen Lockingscanned Y arm for 5FSR

Is that time stamp really correct? I wanted to look at the signal closely to see if I could get any feeling for why it would look so different when positive vs. negative, but I do not see a triangle anywhere near this time (1023780144)...

Quote:

Interesting. It seems for me that there is a dependence of the noisiness as the beat frequency is scanned.

As you increase (or decrease?) the offset, C1:ALS-BEATY-COARSE_I_IN1 becomes bigger and more crisp.
The resulting out-of-loop stability also seems to be improved as you can see from the crispness of the PDH signal.

Do you find why this happens? Is this because the beat S/N depends on the beat frequency due to the PD noise?

 

 

  6824   Sat Jun 16 13:01:17 2012 yutaUpdateGreen Lockingscanned Y arm for 5FSR

Quote:

Is that time stamp really correct?

 Yes. I used pyNDS to get data, but here's a screenshot of dataviewer playing back 300 seconds from GPS time 1023780144.


YarmScanDV.png

  6825   Sat Jun 16 18:17:00 2012 yutaUpdateGreen LockingY arm length using 5FSR scan

Calibrating error signal to beat frequency;
  I injected 0 dBm RF sine wave into the beatbox and sweeped the frequency(just like we did in elog #6815).
  This time, we have different whitening filters. I sweeped the frequency from 0 to 100 MHz in 200 sec.
  The length of the delay line is ~1.5 m for COARSE.
ALS-BEATY_COARSE_I_IN1_DQ.png

Y arm length;
  Here, I think we need some assumption. Let's assume wavelength of IR lamb_IR = 1064 nm and Y end green frequency is nu_g = 2*nu_IR.
  There is a relation
    dnu_g / nu_g = dL / L
  So,
    dnu_g / (dL/lamb_IR) = 2*nu_IR * lamb_IR / L = 2c/L
  We know that dL/lamb_IR = 1/2 for difference in beat frequency between TEM00s. Therefore, slope of the dnu_g vs dL/lamb_IR plot gives us the arm length L(figure below, middle plot).

CalibYarmScan20120614_2.png

  Error estimation is not done yet, but I think the COARSE_I_IN1 error signal to the beat frequency calibration has the largest error because it seems like the amplitude of sine wave changes ~10% day by day.

Calibrating beat frequency to Y arm length change;
  I used L = 32.36 m (figure above, bottom plot).
    dnu_g / dL = c / lamb_g / L = 1.74 MHz/m

  6826   Sat Jun 16 18:51:44 2012 KojiUpdateGreen LockingY arm length using 5FSR scan

Quote:

Calibrating beat frequency to Y arm length change;
  I used L = 32.36 m (figure above, bottom plot).
    dnu_g / dL = c / lamb_g / L = 1.74 MHz/m

Wow. This is way too short.

You don't need to use Albertoo's arm length as his measurement was done before the upgrade.

  6827   Sat Jun 16 19:32:11 2012 yutaUpdateGreen LockingY arm length using 5FSR scan

I know!
But I think there's some error (~ 10% ?) in calibrating the beatbox. In elog #6815, slope near zero crossing point is about 68 counts/MHz, but now, its 60 counts/MHz. Also, zero crossing point in elog #6815 was 47 MHz, but now, its 45 MHz. 5FSR scan was done between these two calibration measurement.

Quote:

Quote:

Calibrating beat frequency to Y arm length change;
  I used L = 32.36 m (figure above, bottom plot).
    dnu_g / dL = c / lamb_g / L = 1.74 MHz/m

Wow. This is way too short.

You don't need to use Albertoo's arm length as his measurement was done before the upgrade.

 

  6829   Mon Jun 18 16:23:59 2012 JenneUpdateLockingLSC trigger update

The LSC triggers for the individual filter modules in a filter bank now works.  This is handy so that boosts can come on as soon as a cavity is locked, but will turn off when the cavity unlocks.

You choose which filter modules you want to be triggered, and which ones you want to be manually controlled. 

Example:  LSC-YARM    FM4 and FM5 should always be on, but FM2 and FM3 are controlled by the trigger.  You can set the trigger thresholds for the filter modules independently of the main DoF enable trigger thresholds.

  6831   Mon Jun 18 23:38:39 2012 JenneUpdateLSCAdded LSC channels to frames

Since the .ini files get overwritten every time a model is compiled now, we need to put all channels we want saved to frames in the DAQ Channels list inside the model.

I added the _ERR channels for all RFPDs (I and Q for each), as well as the _OUT channels for the DCPDs.  I also added the _OUT channels for the DoF servos (ex. C1:LSC-DARM_OUT).  I don't remember off the top of my head what else we used to save from the LSC model, but those all seemed like ones we'll possibly want access to later. 

We need to go through and do this to all the models we use regularly.

Since SUS hasn't been recompiled in a while, all those channels are saved (until such time as someone does a recompile).  Den has gone through and edited the PEM and OAF .ini files by hand each time he recompiles, so we have that data, although we need to put it into the model (which is the new proper way to acquire channels).

  6832   Mon Jun 18 23:54:31 2012 yutaUpdateGreen Lockingphase tracker for ALS

[Koji, Jenne, Yuta]

Summary:
  We put phase tracker in FINE loop for ALS. We checked it works, and we scanned Y arm by sweeping the phase of the I-Q rotator.
  From the 8 FSR scan using FINE (30 m delay line), we derived that Y arm finesse is 421 +/- 6.

What we did:
  1. We made new phase rotator because current cdsWfsPhase in CDS_PARTS doesn't have phase input. We want to control phase. New phase rotator currently lives in /opt/rtcds/userapps/trunk/isc/c1/models/PHASEROT.mdl. I checked that this works by sweeping the phase input and monitoring the IQ outputs.

  2. We made a phase tracker (/opt/rtcds/userapps/trunk/isc/c1/models/IQLOCK.mdl) and included in c1gcv model. Unit delay is for making a feed back inside the digital system. Currently it is used only for BEATY_FINE (Simulink diagram below). We edited MEDM screens a little accordingly.
newIQLOCK.png


  3. Phase tracking loop has UGF ~ 1.2 kHz, phase margin ~50 deg. They are enough becuase ALS loop has UGF ~ 100 Hz. To control phase tracking loop, use filter module C1:ALS-BEATY_FINE_PHASE (with gain 100). Sometimes, phase tracking loop has large offset because of the integrator and freedom of 360*n in the loop. To relief this, use "CLEAR HISTORY."

  4. Locked Y arm using C1:ALS-BEATY_FINE_PHASE_OUT as an error signal. It worked perfectly and UGF was ~ 90 Hz with gain -8 in C1:ALS-YARM filter module.

  5. Swept phase input to the new phase rotator using excitation point in filter module C1:ALS-BEATY_FINE_OFFSET. Below is the result from this scan. As you can see, we are able to scan for more than the linear range of FINE_I_IN1 signal. We need this extra OFFSET module for scanning because BEATY_FINE_I_ERR stays 0 in the phase tracking loop, and also,  error signal for ALS, output of PHASE module, stays 0 in ALS loop.
YarmScan20120618.png

  6. We analyzed the data from 8FSR scan by FINE with phase tracker using analyzemodescan.py (below). We got Y arm finesse to be 421 +/- 6 (error in 1 sigma). I think the error for the finesse measurement improved because we could done more linear sweep using phase tracker.
fine8FSRscan.png


Next things to do:
  - Phase tracker works amazingly. Maybe we don't need COARSE any more.
  - Install it to X arm and do ALS for both arms.
  - From the series of mode scan we did, mode matching to the arm is OK. There must be something wrong in the PRC, not the input beam. Look into PRC mode matching using video capture and measuring beam size.

  6834   Tue Jun 19 23:36:19 2012 yutaUpdateLSCcalibrated POY error signal

[Jenne, Yuta]

We calibrated POY error signal(C1:LSC-POY11_I_ERR). It was 1.4e12 counts/m.

Modeling of Y arm lock:
  Let's say H is transfer function from Y arm length displacement to POY error signal. This is what we want to measure.
  F is the servo filter (filter module C1:LSC-YARM).
  A is the actuator TF using ITMY. According to Kiwamu's calibration using MICH (see elog #5583),

  A_ITMY  = 4.832e-09 Hz^2*counts/m / freq^2

  We used ITMY to lock Y arm because ITMY is already calibrated.

What we did:
  1. Measured openloop transfer function of Y arm lock using POY error signal using ITMY (G=HFA). We noticed some discrepancy in phase with our model. If we include 1800 usec delay, phase fits well with the measurement. I think this is too big.
LSCyarmTF_usingITMY.png


  2. Measured a transfer function between actuator to POY error signal during lock. This should give us HA/(1+G).
LSCyarm_HAover1plusG.png

  4. Calculated H using measurements above. Assuming there's no frequency dependance in H, we got

  H = 1.4e12 counts/m

POYerrorcalibration.png

 For sanity check; Peak to peak of the POY error signal when crossing the IR resonance is about 800 counts. FWHM is about 1 nm, so our measurement is not so crazy.

  6835   Wed Jun 20 00:01:04 2012 JenneUpdateLSCcalibrated POY error signal

[Yuta, Jenne]

We have measured the out of loop residual motion of the Yarm while locked with the ALS.  We see ~70pm RMS, as compared to Kiwamu's best of ~24pm RMS.  So we're not yet meeting Kiwamu's best measurement, but we're certainly not in crazy-land.

The Yarm ALS was locked, I took a spectrum of POY11_I_ERR, and used the calibration that we determined earlier this evening.  For reference, I attach a screenshot of our ALS loop filters - we had on all the boosts, and both resonant gain filters (~3Hz and ~16Hz).

A large part of the RMS is coming from the 60Hz power line and the 180Hz harmonic....if we could get rid of these (how were they eliminated from the measurement that Kiwamu used in the paper?? - plotted elog 6780) we would be closer. 

Also, it looks like the hump (in our measurementf ~100Hz, in Kiwamu's ~200Hz) is not quite an order of magnitude higher in amplitude in our measurement vs. Kiwamu's.  We have ~5e-11 m/rtHz, Kiwamu had ~7e-12 m/rtHz.  This increase in noise could be coming from the fact that Yuta and Koji decreased the gain in the Ygreen PDH loop to prevent the PDH box from oscillating. 

While we should still think about why we can't use the same gain that Kiwamu was able to ~6 months ago, we think that we're good enough that we can move on to doing mode scans and residual motion measurements of the Xarm.

 

Attachment 1: LSC_POY_11_I_ERR_calib_19June2012.pdf
LSC_POY_11_I_ERR_calib_19June2012.pdf
Attachment 2: POY_calib_19June2012_FiltBankSettings.png
POY_calib_19June2012_FiltBankSettings.png
  6836   Wed Jun 20 00:02:16 2012 yutaUpdateGreen Lockingslower scan using phase tracking ALS

For those of you who want to see plots from slower scan.

YarmScan20120619.png

  6837   Wed Jun 20 01:02:20 2012 JamieUpdateGreen LockingRF amp removed from X arm ALS setup

I very badly forgot to log about this in the crush of surfs.

I removed Koji's proto-beatbox RF comparator amp from the X arm ALS setup.  I was investigating hacking it onto one of the discriminator channels in the new beatbox, now that Yuta/Koji's Yuta/Koji's phase tracker is making the coarse beatbox path obsolete.  Upon further reflection we decided to just go ahead and stuff the beatbox board for the X arm, and use the proto-beatbox to test some faster ECL comparators.  This will be done first thing in the morning.

In the meantime the old amp is in my cymac mess on the far left of the electronics bench.

  6838   Wed Jun 20 16:37:11 2012 yutaUpdateLockingETMX 1064 trans camera

[Jenne, Yuta]

We made ETMXT camera working.
We connected the camera to video mux, placed 10% pick off mirror in front of TRX PD, lead the beam go to ETMXT camera.
Transmission to the TRY PD was 23.8 uW, but now, it's 21.3 uW (2.3 uW goes to the camera).
So, we changed C1:LSC-TRX_GAIN from -0.00181818 to -0.00203158 (=-0.00181818*23.8/21.3).

There is a channel for power normalization, C1:LSC-TRX_POW_NORM, but is 1 and it looks like we are using this gain for the normalization. Situation of TRY is the same as TRX.

  6840   Wed Jun 20 18:09:23 2012 yutaUpdateLockingboth arms aligned, ITMX oplev centered

[Jenne, Yuta]

We aligned FPMI. I also centered ITMX oplev because the light was not hitting on QPD.
Alignment procedure we took was;

1. Align Y arm to the Y end green(Y green trans to PSL is now 195 uW with Y end laser measured temperature 34.14 degC).
2. Aligned IR using PZT2 to Yarm(Now, TRY ~ 0.90).
3. Aligned ITMX monitoring AS spots.
4. Aligned X arm so that TRX maximize.
5. Fine adjusted both BS and X arm(Now, TRX ~ 0.82).

Beam spot position on ETMX looks a little too high & left (from ETMXF camera), but we will leave it until ASS scripts is fixed.

FPMIalignment2010620.png

  6841   Wed Jun 20 18:43:57 2012 yutaUpdateLSCcalibrated POX error signal

[Jenne, Yuta]

We did the same calibration for POX. It was 3.8e12 counts/m. See elog #6834 for the details of calibration we did.

According to Kiwamu's calibration, actuator response of ITMX is;

A_ITMX  = 4.913e-09 Hz^2*counts/m / freq^2

Plots below are results from our calibration measurement.

LSCxarmTF_usingITMX.pngLSCxarm_HAover1plusG.pngPOXerrorcalibration.png

  6842   Thu Jun 21 01:58:29 2012 JenneUpdateGreen LockingXgreen preparations

[Yuta, Koji, Jenne]

Lots of small things happened tonight, in preparation for having both arms' ALS working simultaneously.

1. Xarm aligned in IR

     1.1 ETMX oplev centered

2. Xgreen coarsely aligned to Xarm

3. X beat setup on PSL table resurrected. 

     3.1 Steering optics for both X and Y green (before PBS) were touched to fix clipping Xgreen on some of the first mirrors after the light exits the chambers.

     3.2 Xgreen aligned to beat PD

     3.3 PSL green waveplate rotated so ~half of the light goes to X beat, other ~half goes to Y beat (recall we had rotated the polarization so we had max light on the Y beat PD a few weeks ago).

          3.3.1 Now we have ~80uW of PSL green going to each beat PD.

     3.4 PSL green aligned to X beat PD

          3.4.1 Replaced mount for mirror between PBS (which splits PSL green light) and BS (which combines PSL green and X green) so that I could get the alignment correct without having to use the full range of the knobs on the mount.

     3.5 Realigned (coarsely) Ygreen to Y beat PD - the mirrors just after the chambers had been touched, so Y green was no longer directly on the PD.  This will need to be done more finely when we're ready to lock the Yarm again.

     3.6 Dedicated cables for the DC of each beat PD were put in place, so we have those in addition to the DC transmission PDs which we are putting in temporarily each time we align the green to the cavities.  Some mystery unused cables that were running under the PSL table were removed.  The power for the X beat PD was rerouted so that it's much closer to the actual diode, and out of the way. 

4. Better alignment of X green to X arm.

     4.1 Put Green Transmission camera into place

     4.2 Noticed that the X green spot on the transmission camera is not nearly as steady as the Y green.  Increased the gain of the X green refl PD on the end table to see if it helped the spot be more steady, but it's still very wiggly.  We reverted the gain to what it was.  We need to fix this!!!!

    4.3 Removed camera, looked at X transmission DC (PD is temporarily in front of the beat PD), tried to increase the transmission.

     4.4 Aligning the green to the X arm has been really tough - there were a few more iterations of camera then DC PD.

     4.5 Measured X green power on the PSL table - 02 mode was ~150uW.  The 00 mode is still not very stable, which is frustrating, although we have a reasonable amount of power transmitted.   

     4.6 The X end green shutter was moved out of the beam path since the green beam was clipping while going through the shutter.  We need to put it back now that the beam is pretty much aligned.  The beam size and the aperture are roughly the same, so we should look to see if there is a different place on the table where the beam is a little smaller, where we can put the shutter.

5. Whitening filters (Pomona box-style) made for the Xarm I and Q channels - these are the same as the whitening for the Y arm.

6. 30m SMA cable made to be used for 2nd delay line.

     6.1 Steve reminded me this morning that we returned one of the fancy spools of cable that was purchased for the delay lines, since it was defective.  We didn't get it replaced because there was debate as to what is the best kind of cable to use.  We need to come to a conclusion, but for now we have a regular RG-405 cable.

7.  Jamie has started work on modifying the beatbox so that we can have 2-arm ALS.  Hopefully that will be done soon-ish, because we're otherwise pretty close to being ready.

  6844   Thu Jun 21 09:01:18 2012 steveUpdateSTACISthe resurrection of STACIS -surf

There is a small wood cabinet under the south end flow bench, labeled STACIS.

Unit is complete with extension cards and cables.

Attachment 1: IMG_1364.JPG
IMG_1364.JPG
  6845   Thu Jun 21 09:10:08 2012 steveUpdatePEMflow bench must be running all times

The south end flow bench HEPA filter should be run all times. You can turn it off for a measurement or two but remember we are storing clean optics there.

The zero count bench will reach  room particle count  ~ 10,000 in one minute.

  6846   Thu Jun 21 12:13:35 2012 JenneUpdatePEMflow bench must be running all times

Quote:

The south end flow bench HEPA filter should be run all times. You can turn it off for a measurement or two but remember we are storing clean optics there.

The zero count bench will reach  room particle count  ~ 10,000 in one minute.

 My bad.  I turned it off last night to see if it would help make the Xgreen more stable, and then when I woke up this morning I realized that I had forgotten to turn it back on.  Bad Jenne.

  6847   Thu Jun 21 12:56:49 2012 yutaUpdateLockingETMX 1064 trans camera

Quote:

[Jenne, Yuta]

We made ETMXT camera working.

 Xarm_EndTableLayout_NewTransCamera.png

Here's the new end table layout, for the transmitted IR stuff.

  6848   Thu Jun 21 15:00:55 2012 steveUpdateSAFETYSURFs 2012 safety training

Masha, Eric, Yaakov, Liz and Sasha received 40m specific basic safety training.

Attachment 1: surfs2012.JPG
surfs2012.JPG
  6849   Thu Jun 21 15:36:51 2012 yutaUpdateLockingX arm alignment

I aligned X arm so that the beam spot comes roughly on the center.

1. Use ITMX and ETMX (mainly ITMX) to make beam spot come on center of the optic using eyeball.

2. Use ETMX and BS to maximize TRX power (reached ~ 0.85)

3. Aligned green optics on X end. Transmission of X green measured at PSL table is now 255 uW and TEM00 has the most power.

It was not easy to increase X green transmission more because beam spot on green transmission PD is wiggly when X end table is opened. When closed, wiggliness is about the same for Y green and X green.
Turning off HEPA on the X end didin't helped, but there must be something bad in the X end table. If we couldn't figure out why, let's wait for PZTs to come for end tables.

Considering the laser power is different(X end 1 W, Y end 700 mW), X green transmission should reach ~400 uW. But I think we should go on to X beat search.

I placed green shutter for X end back for convenience. I put some spacers to adjust its height and avoid beam clipping.


[Steve, Yuta]

What causing wiggly X green transmission was the air flow from the air conditioner. When we turned it off, beam spot motion became quiet. Air flow from HEPA was not effecting much.

  6850   Thu Jun 21 20:07:18 2012 JamieUpdateGreen LockingImproved beatbox returns

I've reinstalled the beatbox in the 1X2 rack.  This improved version has the X and Y arm channels stuffed, but just one of the DFD channels (fine) each.

I hooked up the beat PD signals for X and Y to the RF inputs, and used the following two delay lines:

  • X: 140' light-colored cable on spool
  • Y: 30m black cable

The following channel --> c1ioo ADC --> c1gcv model connections were made:

  • X I  --> SR560 whitening --> ADC 22 -->  X fine I
  • X Q --> SR560 whitening --> ADC 23 --> X fine Q
  • Y I --> SR560 whitening --> ADC 24 --> Y fine I
  • Y Q --> SR560 whitening --> ADC 25 --> Y fine Q

The connections to the course inputs on the ALS block were grounded.  I then recompiled, reinstalled, and restarted c1gcv.  Functioning fine so far.

 

  6851   Fri Jun 22 02:21:57 2012 JenneUpdateGreen Locking2 arm ALS - Success!!!!

[Yuta, Jenne]

We locked both arms using the ALS system simultaneously!  Hooray!

Video of spectrum analyzer during lock acquisition of both beats is attached.

Jamie is super awesome, since he fixed us up a beatbox speedy-quick.  Thanks Jamie!!  speedy_gonzales-5257.jpg

 Details:

1:  Aligned PSL green optics

     1.1:  We added an amplifier of ~20dB after the X beat PD (more Xgreen power on the PSL table so the signal was ~3dB higher than Y, so required less amplification).  The ~24dB amplifier is still in place after the Y beat PD.  Both beat signals go to a splitter after their amplifiers.  One side of each splitter goes to one of the channels on the beatbox.  The other side of each splitter goes to a 3rd splitter, which we're using backwards to combine the 2 signals so we can see both peaks on the spectrum analyzer at the same time.

2:  Found both beat notes

     2.1:  Y beat was easy since we knew the temps that have been working for the past several days

     2.2:  X beat was more tricky - the last time it was locked was the end of February (elog 6342)

         2.2.1:  We found it by adjusting the PSL laser temp nearly the full range - DC Adjust slider was at 8.8V or so (Y beat was found with the slider at ~1.1V tonight)

          2.2.2:  We then walked the beat around to get the PSL temp back to "normal" by moving the PSL temp, then compensating with the Xend laser temp, keeping the beatnote within the range of the spectrum analyzer.

          2.2.3:  Fine tuned the temps of all 3 lasers until we had 2 peaks on the analyzer at the same time!!

               2.2.3.1:  Yend - measured Temp=34.14 C, thermal Out of Slow servo=29820

               2.2.3.2:  Xend - displayed temp=39.33 C, thermal Out of Slow servo=5070

               2.2.3.3: PSL - displayed temp=31.49 C, Slow actuator Adjust=1.100V

3:  Locked both arms using ALS!!

     3.1:  We were a little concerned that the Xarm wasn't locking.  We tried switching the cables on the beatbox so that we used the old channels for the Xarm, since the old channels had been working for Y.  Eventually we discovered that the input of the filter module for ETMX's POS-ALS input was OFF, so we weren't really sending any signals to ETMX.  We reverted the cabling to how it was this evening when Jamie reinstalled the beatbox.

          3.1.1:  We need to sort out our SUS screens - Not all buttons in medm-land link to the same versions of the SUS screens!  It looks like the ALS screen was modified to point the ETMY button to a custom ETMY SUS screen which has the ALS path in the POS screen, along with LSC and SUSPOS.  There is no such screen (that I have found) for ETMX.  The regular IFO_ALIGN screen points to the generic SUS screens for both ETMY and ETMX, so we didn't know until Yuta searched around for the filter bank that the ALS input for ETMX was off.  We just need to make sure that all of the screens reflect what's going on in the models.

     3.2:  See the video attached - it shows the beat peaks during locking!!! (how do I embed it? right now you have to download it)

          3.2.1:  First you will see both peaks moving around freely

          3.2.2:  Then X arm is locked briefly, then unlocked

          3.2.3: Y arm is locked, steadily increasing gain

          3.2.4:  X arm is locked, so both arms locked simultaneously

          3.2.5:  Yuta clicked a button, accidentally unlocking the Xarm

4:  The transmission of the X arm was not so great, and both of our green beams (although X green especially) were no longer nicely aligned with the cavities.  Yuta tried to align the X arm to the X green, but it's bad enough that we really need to start over with the whole IFO alignment - we leave this until tomorrow.  Since we didn't have any good IR transmission, we didn't bother to try to find and hold the Xarm on IR resonance using ALS, so we didn't measure a POX out of loop residual cavity motion spectrum.  Again, tomorrow. 

Attachment 1: P6210140.AVI
  6852   Fri Jun 22 03:37:42 2012 KojiUpdateGreen Locking2 arm ALS - Success!!!!

Are these correct?

1. It is a nice work.

2. This is not locking, but stabilization of the both arms by ALS.

3. We now have the phase trackers for both arms.

4. There is no coarse (i.e. short) delay line any more.

5. The splitters after the PDs are reducing the RF power to Beat-box.
Actually there are RF monitors on Beat-box for this purpose, but you did not notice them.

6. c1ioo channel list
https://wiki-40m.ligo.caltech.edu/CDS/C1IOO%20channel%20list
has to be updated.

7. Video can be uploaded to Youtube as Mike did at http://nodus.ligo.caltech.edu:8080/40m/6513

  6853   Fri Jun 22 10:52:18 2012 yutaUpdateGreen Locking2 arm ALS - Success!!!!

Answers to questions from Koji.

Are these correct?

1. It is a nice work.

Correct, of course!

2. This is not locking, but stabilization of the both arms by ALS.

Correct.

3. We now have the phase trackers for both arms.

Correct.

4. There is no coarse (i.e. short) delay line any more.

Correct. No coarse, only fine delay line (30m) with the phase tracker.

5. The splitters after the PDs are reducing the RF power to Beat-box.
Actually there are RF monitors on Beat-box for this purpose, but you did not notice them.

Oh, yes. But distance between beatbox and spectrum analyzer in the control room is longer than distance between BBPD on PSL table and the spectrum analyzer. We were too lazy to do cabling, but maybe we should.

6. c1ioo channel list 
https://wiki-40m.ligo.caltech.edu/CDS/C1IOO%20channel%20list
has to be updated.

Yes, we will.

7. Video can be uploaded to Youtube as Mike did at http://nodus.ligo.caltech.edu:8080/40m/6513

We didn't, but we can.

  6854   Fri Jun 22 13:37:17 2012 JenneUpdateComputersfb lost connection

...Perhaps related to the fact that Jamie is copying a lot of stuff over the network to back up Ottavia before converting her to Ubuntu, perhaps totally independent. 

After restarting the daqd, c1lsc was the only computer whose mx_stream came up on its own.  I restarted c1sus. c1ioo, c1iscey, c1iscex by hand.

  6855   Fri Jun 22 17:51:04 2012 JenneUpdateCamerasGreen Trans camera repositioning attempt

[Yuta, Jenne]

We tried to find a different place, not in the main green transmitted beam path, to place the trans camera for the green beams.  There is a little bit of leakage through the 3 high reflector mirrors which steer the beams from the direction when they first come out of the chamber over to the main green beat setup.  2 of these mirrors have virtually no space behind them for a camera (the first one the green beams encounters is right next to the EOM mount, and the 2nd one is pretty close to the Input Pointing QPDs.  We can potentially use the beam leaking through the 3rd steering mirror, if the camera is very close to the edge of the table (so that the camera isn't blocking the IR input pointing beams), but the X beam is so dim as to be nearly impossible to see, even when TEM00.  This precludes the point of the camera, which is to see the modes when we're aligning the beams.  (X power on the PSL table is pretty high - 330uW measured today, but those mirrors must transmit the Y beam's polarization more than the X beam's.)

Our other thought was to use one of the secondary beams coming out of the chambers.  This is kind of Mickey Mouse, but we thought that since this is just a camera to see the modes, as opposed to a PD, maybe it's okay.  This is a moot point however, since the secondary and tertiary beams (due to the wedge of the window) are clipped for the Y green.  We closed the PSL shutter then removed the beam pipe between the PSL table and the chamber so I could look inside. 

It looks to me like the main green transmitted beams are exiting through the window several inches from any edge, so they're definitely not clipping.  But the reflection from the window back into the chamber is hitting some optic.  The X green is hitting the face of the optic, while the Y green is hitting the edge of the optic and part of the mount.  The reflections from this mount then go back toward the chamber window and out toward the PSL table.  This isn't a big deal for the camera situation - we'll just use the leakage from one of the steering mirrors somehow, but it does mean that there is some green light reflected back onto an IR mirror, and potentially causing grief.  I didn't look to see if the mirror it's hitting is the 1st in-vac IR steering mirror (I don't think so) or something in the OMC / AS path (I think it's something here), but either way, we could be making trouble for ourselves.  We should try to dump the reflection from the window when we vent.  Jamie has put it on the List.

We replaced the beam pipe between the PSL table and the chamber before opening the shutter on the laser.  We are currently sticking with the plan of putting the camera in the main green trans path for initial alignment, then removing it for the rest of the work.

  6856   Fri Jun 22 19:52:47 2012 JamieUpdateComputersottavia reconfigured as CDS workstation

ottavia has been reinstalled with Ubuntu 10.04 LTS, and has been configured as a CDS workstation.

I have been maintaining a script that takes a stock 10.04 install and configures it as a workstation.  I've attached it here, but it lives at:

/users/controls/workstation-setup.sh

The script is designed to be idempotent, i.e. it can be run on a machine that has already been configured and it will either have no affect or update.

Attachment 1: workstation-setup.sh
#!/bin/bash

# This is a CDS workstation setup script for Ubuntu 10.04 It is
# idempotent, so running it on an already configured workstation is
# fine.

########################################
### controls

if [[ $(id -u controls) != 1001 ]] ; then
... 111 more lines ...
  6858   Fri Jun 22 20:58:15 2012 JenneUpdateGreen LockingCalibrated POX spectra - Xarm stabilized by ALS

[Yuta, Jenne, Koji]

We stabilized the Xarm using the ALS and took a spectrum of POX as our out of loop sensor.  We used the calibration from elog 6841 to go from counts to meters.

We find (see attached pdf) that the RMS is around 60pm, dominated by 1Hz motion.

 

In other, related, news, I took out the beam pipe connecting the AP and PSL tables and covered the holes with foil.  This makes it much easier and faster to get to the X beat setup for alignment.  Eventually we'll have to put it back, but while the AUX laser on the AP table is not being used for beating against the PSL it'll be nice to have it out of the way.

Attachment 1: POX11_I_ERR_calib_residualCavityMotion_better.pdf
POX11_I_ERR_calib_residualCavityMotion_better.pdf
  6859   Sat Jun 23 02:29:18 2012 yutaUpdateGreen LockingX arm mode scan results

X arm finesse is 416 +/- 6, mode-matching ratio is 91.2 +/- 0.3%

I did mode scan for X arm just like we did for Y arm (see elog #6832)

Servo design:
  Servo filters are as same as Y arm.
  UGF and phase margin of X arm ALS are 100 Hz and 14 deg.
  For phase tracking loop, they are 1.5 kHz and 56 deg.

Raw data from the mode scan:
XarmScan20120623.png


Fitted peaks and finesse:

fine8FSRscanXarm.png

By taking the average,

F = 416 +/- 6 (error in 1 sigma)
(For Y arm, it was 421 +/- 6. See elog #6832)


Mode matching ratio:
 From X arm 8FSR measurement using phase tracker, peak heights are

TEM00 0.834, 0.851, 0.854, 0.852, 0.876, 0.850, 0.855, 0.878
TEM01 0.031, 0.031, 0.017, 0.017, 0.009, 0.014, 0.009, 0.011
TEM02 0.053, 0.052, 0.057, 0.058, 0.061, 0.060, 0.061, 0.059
TEM03 0.011, 0.010, 0.010, 0.007, 0.006, 0.005, 0.006, 0.005

 So, the mode-matching ratio is

MMR = 89.7%, 90.1%, 91.0%, 91.2%, 92.0%, 91.4%, 91.8%, 92.1%

 By taking the average,

MMR =  91.2 +/- 0.3 (error in 1 sigma)
(for Y arm, it was 86.7 +/- 0.3 %. See elog #6828)


Discussion:
 - Mode matching ratio for both X and Y arm is ~90%, which is not so great, but OK. It seems like there's no huge clipping or mode-mismatch from MC to ITMs. I think we should go next for PRMI investigation.

 - Measured finesse seems too low compared with the design value 450. If we believe power transmission of ITM and ETM are 0.0138 and 1.37e-5, the measured finesse tells you that there's ~0.1% loss(F = 2*pi/(T_{ITM}+T_{ETM}+T_{loss})). We need some evaluation for the linearity of the sweep, before concluding that there's 0.1% loss for each arm. Using FINE_I/Q signal for calibration, or installing frequency divider for monitoring actual beat frequency would help.


Things to do for the beat setup:

 - Amplifiers after beat PDs shouldn't be on the PSL table. Move them near the beatbox.
 - Install DC PD (and camera?) at un-used port of the beat BS for monitoring green transmission power.
 - Make nice MEDM screens for our new phase tracking ALS.
 - Make a script to sweep arm length with ALS and find IR resonance.
 - Look into X end table. Beam spot of the X green transmission is wiggly when X end table is opened and there's air flow.

  6860   Sat Jun 23 18:44:15 2012 steveUpdateGeneralpower surge has no effect on the lab

I was notified by CIT Utilities that there was a power surge or short power outage this after noon.

Lab conditions are normal:  c1ioo is down.  The south arm AC was off......I turned it back on.

  6862   Sun Jun 24 00:10:45 2012 yutaUpdateGreen Lockingcurrent beat electronics

I moved amplifiers for beat PD at PSL table to 1X2 rack. Current beat setup from PD to ADC is shown below. Setup for X beat and Y beat are almost the same except for minor difference like cable kind for the delay line.

Currently, DC power for amplifiers ZHL-1000LN+ is supplied by Aligent E3620A.
I tried to use power supply from the side of 1X1 rack, but fuse plug(Phoenix Contact ST-SI-UK-4) showed red LED, so I couldn't use it.
Measured amplification was +25 dB for 10-100 MHz.

Measured gain from RF input to monitor output of the beat box was ~ -1 db for 10-100 MHz.

beatsetup20120623.png

  6863   Sun Jun 24 23:42:31 2012 yutaUpdateComputer Scripts / ProgramsPMC locker

I made a python script for relocking PMC.
It currently lives in /opt/rtcds/caltech/c1/scripts/PSL/PMC/PMClocker.py.

I think the hardest part for this kind of locker is the scan speed. I could make the scan relatively fast by using pyNDS.
The basic algorithm is as follows.

1. Turns off the servo by C1:PSL-PMC_SW1.

2. Scans C1:PSL-PMC_RAMP using ezcastep.bin. Default settings for ezcastep is

ezcastep.bin C1:PSL-PMC_RAMP -s 0.1 0.01 10000

So, it steps by 0.01 for 10000 times with interval of 0.1 sec.

3. Get C1:PSL-PMC_PMCTRANSPD and C1:PSL-PMC_RAMP online 1 sec data using pyNDS.

4. If it finds a tall peak in C1:PSL-PMC_PMCTRANSPD, kills ezcastep.bin process, sets C1:PSL-PMC_RAMP to the value where the tall peak was found, and then turns on the servo.

5. If tall peak wasn't found, go back to 3 and get data again.

6. If C1:PSL-PMC_RAMP reaches near -7 V or 0 V, it kills previous ezcastep.bin process and turns the sign of the scan.

I tested this script several times. It sometimes passes over TEM00 (because of the dead time in online pyNDS?), but it locks PMC with in ~10 sec.
Currently, you have to run this to relock PMC because I don't know how to make this an autolocker.

I think use of pyNDS can be applied for finding IR resonance using ALS, too.
I haven't checked it yet becuase c1ioo is down, but ALS version lives in /users/yuta/scripts/findIRresonance.py. ALS may be easier in that we can use fast channels and nice filter modules.

Other scripts:
 I updated /opt/rtcds/caltech/c1/scripts/general/toggler.py. It now has "lazymode". When lazymode, it toggles automatically with interval of 1 sec until you Ctrl-c.

 Also, I moved damprestore.py from my users directory to /opt/rtcds/caltech/c1/scripts/SUS/damprestore.py. It restores suspension damping of a specified mirror when watchdog shuts down the damping.

ELOG V3.1.3-