40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 140 of 341  Not logged in ELOG logo
ID Date Author Typeup Category Subject
  5004   Wed Jul 20 19:24:12 2011 ranaUpdateSUSoplev gains today

I guess Valera forgot to elog it. Steve, please email him and get the info.

I started to check out the OL servos today so that our whole interferometer is not too floppy.

  • The ETMX OPLEV DAQ channels were not in the list. Jamie ran the activateDQ.py script and it came back. Right now, we have no diagnostics to know if people have run this or not so the frames will have missing data now and again depending on how forgetful the rebooters are. Perhaps we can get activateDQ put into the make file???
  • I turned ON all of the offset buttons on the OL1, etc. filter banks. This allows for the dark offsets to be set for the OL quadrants. With these buttons off it doesn't make any sense.
  • I noticed that there are white (INVALID) fields all over the OPTLEV_SERVO screens. This is just because the new SUS models have not captured all of the functionality of the old system. Needs fixing.

Untitled.png

Some of these OL spectra are not like the others...

 a.png

  5005   Wed Jul 20 19:48:03 2011 JamieUpdateSUSRe: oplev gains today

 

 We have been modifying models that need to have their channels renamed to run activateDQ when Joe's post_build_script to is run. 

The trick is to integrate things to get the post_build_script running after every model build (getting it hooked in to the make file somehow).  We're working on it.

 I've added the following epics channels to sus_single_control model using the epicsOutput part:

  • OL_SUM
  • OL_PITCH
  • OL_YAW

These channels are now all available.  I'm not exactly sure how to ensure that they're being trended.  I'll check that tomorrow.

  5006   Wed Jul 20 20:04:54 2011 JamieUpdateCDSC1:DAQ-FB0_C1XXX_STATUS sometimes unexplainably goes red

I have been noticing this happening occasionally, but I don't understand what is causing:

status-fb-red1.png

The channel in question above is C1:DAQ-FB0_C1SCX_STATUS.  This channel is (I believe) reporting some status of the front end model communication with the frame builder, but I'm not sure exactly what.

Usually this problem goes away when I restart the model or the frame builder, but it didn't work this time.  Tomorrow I will figure out what this channel means, why it's sporadically going red, and how to correct it.

  5007   Wed Jul 20 20:44:56 2011 JamieUpdateSUSAll sus models rebuilt and restarted

There were a couple of recent improvements to the sus_single_control model that had not been propagated to all of the suspension controllers.

Rebuilt and restarted c1mcs, c1sus, c1scx, and c1scy.  Everything seems to be working fine after restart.

  5008   Wed Jul 20 22:16:27 2011 Ishwita, ManuelUpdateElectronicslying seismometer cable and plugging it

We laid the cable along the cable keeper from the BACARDI seismometer to the rack 1X6, the excess cable has been coiled under the X arm.

We plugged the cable to the seismometer and to the seismometer electronics box in rack 1X6. We also plugged the AC power cable from the box to an outlet in rack 1X7 (because the 1X6 outlets are full)

With the help of a function generator we tested the following labeled channels of AA board...

2, 3, 11, 12, 14, 15, 16, 18, 19, 20 and 24

that are the channels that can be viewed by the dataviewer, also the channel 10 can be viewed but it's labeld BAD so we cannot use it.

We leveled the seismometer and unlocked it, and saw his X,Y,Z velocity signals with an oscilloscope.

  5009   Wed Jul 20 23:31:44 2011 SureshUpdateIOOMC Trans QPD is down

 

The mode cleaner is not locking because the MC Trans QPD signal is not present.  There is light on the QPD when the MC flashes and its position has not shifted.  The cable is plugged in well into the sensor head.  The signal cable is labled "MC2 Opt Lever"  and it arrives on the 1X4 rack along with other Optical Lever cables. Pressing the connector in did not solve the problem.

 

  5010   Thu Jul 21 09:04:59 2011 valera, steveUpdateSUSoplev gains were not optimized

 

Hi Steve,

 
I did change the ETMY optical lever configuration: http://131.215.115.52:8080/40m/4795
And I left it in that state per Jamie's request.
 
I was going to work on the servo tuning but found that the whitening was not working at that time.
What I was going to do is to measure the open loop gain to make sure the servo is stable, then 
measure the noise and minimize the rms motion by tuning the gain and the filter transfer function.
 
I plan to come to the 40m lab on August 22 for two weeks.
 
Valera.
  5011   Thu Jul 21 10:08:30 2011 steveUpdateSUSsus sensor summary

OSEM voltages to be corrected at upcoming vent: threshold ~ 0.7-1.2V, ( at 22 out of 50 )

ITMX_UL, UR, LL, LR, SD

ITMY_UL

ETMX_UL, UR, LL, LR, SD

ETMY_UL

SRM_UL, UR, LL

MC2_UR_SD

BS_UR, SD

MC3_UL, LR, LL

 

Attachment 1: sus_sensor.png
sus_sensor.png
  5012   Thu Jul 21 12:19:29 2011 Jamie, KiwamuUpdateIOOMC Trans QPD working, now locking

It turns out that the MC_TRANS_SUM signal was being derived from the SUS-MC2_OL_SUM_INMON channel in the ioo.db file. 

However, this channel name was recently changed to SUS-MC2_OLSUM_INMON (no underscore between OL and SUM) when

I added the new OL_SUM epics channel to the sus_single_control library model (I forgot to mention it in my previous log on this change,

apologies).  This is why there appeared to be no signal.  This was also what was preventing the mode cleaner from locking, since

the MC_TRANS_SUM signal is used as a trigger in the MC autolocker script.

We modified the ioo.db file at /cvs/cds/caltech/target/c1iool0/ioo.db [0,1] to change the name of the channel that the

C1:IOO-MC_TRANS_SUM signal is derived from.  The diff on the ioo.db file is:

--- /cvs/cds/caltech/target/c1iool0/ioo.db	2011-07-21 11:43:44.000000000 -0700
+++ /cvs/cds/caltech/target/c1iool0/ioo.db.2011Jul21	2011-07-21 11:43:36.000000000 -0700
@@ -303,7 +303,7 @@
 {
         field(DESC,"MC2 Trans QPD Sum")
         field(PREC,"1")
-        field(INPA, "C1:SUS-MC2_OLSUM_INMON")
+        field(INPA, "C1:SUS-MC2_OL_SUM_INMON")
         field(SCAN, ".1 second")
         field(CALC, "A+0.001")
 }

We then rebooted the c1iool0 machine, and when it came back up the MC_TRANS_SUM channel was showing the correct values.

We then found that the MC autolocker was not running, presumably because it had crashed after the channel rename?

In any event, we logged in to op340m and restarted the autolockerMCmain40m script.

The mode cleaner is now locked.

[0] Rana's log where this was initially defined

[1] All of the slow channel stuff is still in the old /cvs/cds/caltech path.  This needs to be fixed.

 

  5013   Thu Jul 21 16:05:15 2011 sureshUpdateIOOPSL beam into MC realigned

 I realigned the PSL beam going into the MC.

The MC beam was realigned so as to maximise the power in the MC.  I minimised the MC_RFPD_DCMON dial on the MC_ALIGN screen while adjusting the two zig-zag mirrors at the end of the PSL table.

  5014   Thu Jul 21 16:06:35 2011 steveUpdateSUSoplev gains today checked by conlog

 Present values agree with conlog records. It can be concluded that there were no big changes made. There are some 0.1-0.2 gain  and one polarity changes during the periods of Valera's visits.

 

  5015   Thu Jul 21 23:36:51 2011 JennyUpdate Fitting beam waist with MATLAB

I am starting work on the PSL table at the 40m. My goal is to lock the laser coming from the nearby table to the FP cavity and get a measurement of the response to a temperature step on the surrounding can.

I have to mode match the beam to the cavity. Specifically, I have to mode match to the beam coming from the PMC through the EOM to the polarizing beam splitter. Yesterday David and I measured the beam width at various distances (from a particular lens through which the beam traveled), and I fit that data using MATLAB to find the beam's waist size and location. However, I'm not convinced that the fit is any good, since we only took measurements at five spots and they had large error bars.

 

z (mm) 2w_vert (mm) 2w_horiz (mm)
180 4.68 3.38
230 4.64 3.49
305 4.68 3.47
370 5.1 3.81
510 5.5 4.17

Here is the fit I obtained using fminsearch. The horizontal beam width measurements were smaller than the vertical width measurements, suggesting that the incoming beam was elliptical. I fit the data for each set of measurements separately and got two waist locations. The red trace is the fit for the horizontal width and the blue represents the vertical width of the beam. Averaging the two fitted waist locations and sizes gives

vert z_0= -1760 mm (waist location)

horiz z_0= -1540 mm (waist location)

vert w_0 = 0.286 mm (waist size)

horiz  w_0 = 0.275 mm (waist size)

avg z_0= -1650 mm

avg w_0 = 0.281 mm

 

twobeamfit2.jpg

Here is the code I used:

I defined the function spotsize.m and then made a function gaussbeam.m that called it with input parameters and returned the least squares error. I then wrote another function twobeamfits.m that ran fminsearch to minimize the least squares error and made the above plot. I've pasted the code below.

spotsize

function omega = spotsize(z_0, w_0, z)
lambda=0.001064;
omega=w_0*(1+(lambda*(z-z_0)/(pi*w_0^2)).^2).^(1/2);

 

gaussbeam

function sse = gaussbeam(params,xvals,yvals)

%This f'n takes as its inputs
%three parameters (w_0, z_0, and lambda),
%a vector of x-values (distances),
%and an associated vector of y-values (spotsizes),


%It then generates a vector of fitted y-values by applying
%an exponential approach function (single pole), with the given parameters,
%to the x-values.

%It then returns the sum of the squares of the entries of the difference
%between the fitted y-vector and the actual y-vector

z_0=params(1);
w_0=params(2);
fityvals=spotsize(z_0, w_0, xvals);

error=(fityvals - yvals);% .*xvals;
% sse stands for sum of squares error
sse=sum(error.^2);

 

twobeamfits

function [outputs] = twobeamfits(guesses, dists, vert, horiz)


%This f'n takes as its inputs
%two starting guess parameters (w_0 and z_0),
%a vector of distances (x-values),
%and two associated vectors of measured beam radii,

%the radius measured along the vertical axis

%and the radius measured along a horizontal axis (y-values).

%It then calls the gaussbeam f'n for each set of y-values and minimizes its output (sum of squares error)
%using the fminsearch f'n. It outputs the fit parameters it settles on.

%It then plots the input data, the fitted curves, and the residuals


fminopts=optimset('TolFun',1e-6,'MaxIter', 100000);
vertparams=fminsearch(@gaussbeam,guesses,fminopts,dists,vert);
fitvert=spotsize(vertparams(1), vertparams(2), dists);
resid1=(vert-fitvert)./vert;
spoterror=[.1, .1, .1, .1, .1]; %uncertainties, all in mm

fminopts=optimset('TolFun',1e-6,'MaxIter', 100000);
horizparams=fminsearch(@gaussbeam,guesses,fminopts,dists,horiz);
fithoriz=spotsize(horizparams(1), horizparams(2), dists);
resid2=(horiz-fithoriz)./horiz;


points=linspace(-2000,1000,1000);
figure(1)
hold off
clf
subplot(2,1,1)
hold on
errorbar(dists, vert, spoterror, 'x')
grid
errorbar(dists, horiz, spoterror, 'r*');
plot(points,spotsize(vertparams(1), vertparams(2), points));
plot(points,spotsize(horizparams(1), horizparams(2), points),'r');
xlabel('Distance z (mm)')
title('Gaussian Beam Fits')
ylabel('Spotsize w (mm)')
legend('Vertical Spotsize','Horizontal Spotsize','Vertical Fit',...
    'Horizontal Fit','Location','SouthEast')
hold off

subplot(2,1,2)
plot(dists,resid1,'x')
hold on
plot(dists,resid2,'r*');
xlabel('Distance (z)')
title('Residuals')
ylabel('Fractional Difference')
legend('Vertical Fit Residuals','Horizontal Fit Residuals',...
    'Location','SouthEast')
grid

outputs=[vertparams horizparams];

 

 

 

Later on I may repeat some measurements and try to gain more certainty in my fit. In the mean time I will use this beam profile for mode matching. 

 

  5016   Fri Jul 22 10:13:41 2011 steveUpdateVACRGA scan at day 213
Attachment 1: pd70m213scan.jpg
pd70m213scan.jpg
  5017   Fri Jul 22 10:24:34 2011 steveUpdateVACpressure plot at day 213

Dec 21, 2010 we pumped down the MARK4 rebuilt 40m-IFO and the malev has been pumping on it since than

Attachment 1: p.jpg
p.jpg
  5018   Fri Jul 22 14:22:13 2011 Ishwita, ManuelUpdatePEMSTS-2 seismometer hardware testing

We have two STS-2 seismometer boxes... the blue box & the purple box. Initially we used the blue box for the STS-2 seismometer (named Bacardi by Jenne).

  • Oscilloscope powered on battery was used to test the blue box by observing the velocity output of the three axes (X, Y, Z).  It was found out that the mean value of DC volt of...

X = +10 V

Y = +11 V

Z = -0.1 V

Thus, X and Y axes showed abnormally high DC volt. It was also found out that in AC coupling mode of the oscilloscope... changes were observed in the signal received from Z axis when some seismic wave was generated near the Bacardi by jumping near it. No such changes were observed from signals received from X & Y axes.

  • We removed the blue box and used the purple box for the same Bacardi seismometer & used the oscilloscope powered on battery to test it. It was found out that the mean value of DC volt of...

X = +4.4 V

Y = +4.4 V

Z = +4.4 V

In Ac coupling mode of the oscilloscope... changes were observed in the signals from X, Y, Z axes when someone jumped near Bacardi.

  • The above voltages from the two STS-2 seismometer boxes are unsuitable for the ADC box since it works with voltages ranging from +2 V to -2 V.... meaning it will consider any voltage signal above +2 V as +2 V and any signal below -2 V as -2 V. Hence we need to find out how to use these STS-2seismometer boxes with the ADC box.
  • We also tried measuring the DC volt from the shield and the center of a BNC connector corresponding to Y axis of the purple box (lets call it 'BNC-test') by using BNC-to-banana adaptors and banana wires. Signal from shield of BNC-test was sent to oscilloscope's channel 1 (connected to center of its BNC connector) and signal from center of BNC-test was sent to oscilloscope's channel 2 (connected to center of its BNC connector). On the oscilloscope screen it was observed that both the signals gave the same mean voltage output (-2.2V).
  5019   Fri Jul 22 15:39:55 2011 haixingUpdateSUSmatching the magnets

Yi Xie and Haixing,

We used the Gauss meter to measure the strength distribution of bought magnets, which follows a nice Gaussian distribution.
We pick out four pairs--four fixed magnets and four for the levitated plate that are matched in strength. The force difference is
anticipated to be within 0.2%, and we are going to measure the force as a function of distance to further confirm this.

In the coming week, we will measure various transfer functions in the path from the sensors to the coils (the actuator). The obtained
parameters will be put into our model to determine the control scheme. The model is currently written in mathematica which can
analyze the stability from open-loop transfer function.

  5021   Sat Jul 23 02:24:10 2011 SureshUpdateIOOrestarted the frame builder

I restarted the fb twice during the last 15mins.   This was after I added test points into the C1IOO/WFS1.mdl and C1IOO/WFS2.mdl.

  5025   Mon Jul 25 00:35:44 2011 ranaUpdateSUSsomething wrong with ETMY LR sensor

a.png

Looks like either the LR OSEM is totally mis adjusted in its holder or the whitening eletronics are broken.

Also looks like the ETMY is just not damped at 1 Hz? How can this be?

I look at the SUS_SUMMARY screen which apparently only Steve and I look at:

bad.png

Looks like the suspensions have factor of 10-100 different gains. Why?

**  The ETMY just doesn't behave correctly when I bias it. Both pitch and yaw seem to make it do yaw. I leave this for Jamie to debug in the morning.

***  Also, the BIAS buttons are still broken - the HOPR/LOPR limits ought to be 5000 and the default slider increment be 100. Also the YAW button readback doesn't correctly show the state of the BIAS.

****  And.....we have also lost the DAQ channels that used to be associated with the _IN1 of the SUSPOS/PIT/YAW filter modules. Please put them back; our templates don't work without them.

  5029   Mon Jul 25 11:46:28 2011 steveUpdateSUSETMY sus problem hunt

[Kiwamu / Steve]

We checked some electronics noise on the ETMY shadow sensor system.

Noise from the WF, AA board and ADC are below the shadow sensor spectra on ETMY.

It means something funny is going on in the upstream side (including the satelight box and shadow sensors)

OR the coil drivers side are going crazy ??

 

As Rana pointed out in his entry (#5025), the spectra of the shadow sensors on ETMY were quite bad below 3 Hz. The floor are higher than that of ETMX by factor of 10 or so.

To check if the noise comes from some of the electronics, we disconnected D15-sub from pd to whitening in.

The spectra with/without shadow sensors are attached below.

The curves in brown and green are the ones taken when the shadow sensors were disconnected from the WF board.

So these two curves represent the summed noise of the WF, AA and ADC.

This tells us to look toward the OSEM.

 

Attachment 1: ETMY_AA_ADC.png
ETMY_AA_ADC.png
  5030   Mon Jul 25 13:01:24 2011 kiwamuUpdateCDSc1ioo Make problem

[Suresh / Kiwamu]

HELP US Jamieeeeeeee !! We are unable to compile c1ioo.

 

It looks like something wrong with Makefile.

We ran make c1ioo -- this was successful every time. However make install-c1ioo doesn't run.

The below is the error messages we got.

        make install-target-c1ioo
        make[1]: Entering directory `/opt/rtcds/caltech/c1/core/branches/branch-2.1'
        Please make c1ioo first

Then we looked at Makefile and tried to find what was wrong. Then found the sentence (in 36th line from the top) saying

        if test $(site)no = no; then echo Please make $$system first; exit 1; fi;\

We thought the lack of the site-name specification caused the error.

So then we tried the compile it again with the site name specified by typing

     export site=c1

in the terminal window.

It went ahead a little bit further, but it still doesn't run all through the Make commands.

 

  5031   Mon Jul 25 13:09:39 2011 JamieUpdateCDSc1ioo Make problem

> It looks like something wrong with Makefile.

Sorry, this was my bad.  I was making a patch to the makefile to submit back upstream and I forgot to revert my changes.  I've reverted them now, so everything should be back to normal.

  5032   Mon Jul 25 17:16:02 2011 JamieUpdateSUSNow acquiring SUSXXX_IN1_DQ channels

> And.....we have also lost the DAQ channels that used to be associated with the _IN1 of the SUSPOS/PIT/YAW filter modules. Please put them back; our templates don't work without them.

I have (re?)added the SUS{POS,PIT,YAW,SIDE}_IN1_DQ channels.  I did this by modifying the activateDQ.py script to always turn them on [0].  They should now always be activated after the activateDQ script is run.

[0] This script now lives in the cds_user_apps repo at cds/c1/scripts/activateDQ.py

 

  5033   Mon Jul 25 18:51:38 2011 ManuelUpdatePEMSTS-2 seismometer hardware testing with Jan

[Jan, Manuel, Jenne]

Jenne called Jan to check and figure out why the Streckeisen seismometer (SN #100151) doesn't work, hence we checked the output of the seismometer boxes as we did last friday. (This is the problem of seeing the X and Y channels saturated, when we look at them on a floating 'scope, as in the linked elog entry.)

Jan unplugged and plugged again the orange cable into the seismometer and nothing happened.   Well, what Jan was listening for was "clicks" inside the seismometer indicating that it was receiving power.  We heard these, and moved on to examining the breakout boxes.  Also, we checked that we could hear the "clicks" (one per mass) when we pushed the mass-centering button on the little green companion box.

We weren't sure that the purple box was working properly, so since we had seen the blue box work last time, we changed the purple box with the blue box in rack 1X6.

The Z-channel of the purple box returns a correct signal, that means that all the masses in the seismometer work (because the Z-signal is a linear combination of the three masses U, V, W), the X and Y channel have a DC component of about 10 Volts, Jan said that the recentering of the seismometer masses could need all the night, so we keep the power of the box on. If tomorrow morning the X and Y signal won't  both be zero mean, we will open and check the box.

The power of the box is still on so that the masses can recenter overnight.

Edits by JD

  5035   Tue Jul 26 03:15:52 2011 JenneUpdateLockingLatest MICH noise budget

[Jenne, Rana]

We had another look at the MICH noise budget tonight. Rana has verified that my techniques / math aren't too ridiculous. 

In the first attachment, you'll notice that the MICH noise is waay above the shot noise of 1mW on the beam splitter.  We don't know why.  One problem is that the modulation depth of the 55MHz is too low by ~a factor of 10.  Kiwamu and his magical resonant circuit are working on fixing this.  This will not, however, fix the huge discrepancy here.  More investigation and meditation is required!  For this measurement, the whitening gain of AS55 was set to 42dB for both I and Q.

In the 2nd attachment, the PSL shutter is closed, so all of these are dark measurements of AS55.  (The input matrix on the LSC screen is AS55Q * 1 -> MICH_IN1, so they're the same).  All we've done is change the whitening gain before the ADC.  For 0dB and 9dB, you can see that the low freq noise didn't change - here we're still limited by the ADC noise.  With 21dB and 42dB we're clear of the ADC, so either is fine.  Unfortunately, the high freq stuff when the loop is on matches up with the high freq part of the dark noise, so that's part of the problem....

Attachment 1: MICHnoise_shotNoise_25July2011.pdf
MICHnoise_shotNoise_25July2011.pdf
Attachment 2: MICH_darkNoise_whiteningGainChanging_25July2011.pdf
MICH_darkNoise_whiteningGainChanging_25July2011.pdf
  5036   Tue Jul 26 09:01:53 2011 JennyUpdateComputer Scripts / ProgramsMode matching

I found a mode matching solution to match the beam coming to the PSL table from the AP table so that I can lock the laser beam coming onto the PSL table to the reference cavity on the table. I determined that at the polarizing beam splitter, I want a beam with a q=(147+25.1i)mm (w0=58mm). This came from applying the ABCD matrices for three distances,

  • d1=693 mm,
  • d12=660.4 mm, and
  • d2=393.7 mm, separated
  • an f=229.1 mm planoconvex lens and
  • an R=300 mm curved mirror.

to a beam with q0 = 406.4i mm (w0=0.371 mm at the PMC).

I obtained the following mode matching solution, which I will try to implement on the PSL table:

The beam I have has waist 0.281 mm at -2.74 m (I set my origin at the polarizing beam splitter--the spot where I want my beam to match the beam coming from the PMC, so all waists are behind that point). These numbers  come from the beam-profiling and MATLAB-fitting I did (see 5015).

The solution I chose was: f = 1145.6 mm at -0.95 m and f = 572.7 mm at -0.62 m. This may need to be changed however, if I need to add in some beam steering, which would increase the path length traveled by the beam.

modematchparameters.png modematchpic.png

 

  5037   Tue Jul 26 11:38:45 2011 steveUpdateSUSETMY bias checked

 

 I test drove ETMY biases.

PITCH  worked well in slow and fast modes. Slow drive was from the IFO alignment screen C1:SUS-ETMY_PIT_COM and

the fast one from C1:SUS-ETMY_ASCPIT_OFFSET

YAW did not.  It was always diagonal. It was  specially bad with the fast drive. I compared them with ETMX. ETMX yaw is diagonal a little bit too.

The OPLEV return spots on the qpd ETMX and ETMY are big 5-6 mm diameter. The ETMY spot has weird geometry to qpd.

  5039   Wed Jul 27 01:57:28 2011 SonaliUpdateGreen LockingWeekly Summary

1. I have used the PMC  trans beam in my set-up as the required PSL beam.

2. I have superposed the ETMX-Fibre output with the PSL beam on the PSL table.

3. I have used suitable beam splitters and lens to match the power and the  sizes of the overlapping beams and have aligned them to the optimum.

4. A lens having f=7.6 cms is used to focus the beam into the PD.

5. Initially, I used the broadband 1611 NewFocus PD to find the IR beat signal by scanning the oven temperature. (using the digital sitemap controls.)

6. I checked the previous elog entries by Suresh and Koji on the green beat signal they had worked on and used their data to get an idea of the temperature range of the oven where I could obtain a beat.

7. I obtained peaks at three different temperatures as had been noted previously and set the temperature so that I am now sitting in the middle stable regime.

8. Then I switched to the 1811 100 MHz PD as it has a larger gain. It has a saturation power of 100 microWatts. The input power at the PD is measured to be 80 microWatts.

9. I was having trouble getting a clean peak due to presence of many harmonics as seen on the spectrum analyser. This happened because there was too much power incident on the PD which led to arising of non-linearity giving rise to harmonics.

10.To reduce the power entering the PD, I put in a ND 1.0 Filter just before the beam enters the PD and obtained a clean signal.

11. I will use  the frequency counter tomorrow to check the resonant frequency and try to connect the output to acquire a digital signal.

12. Otherwise I will proceed to build a Mixer Frequency Discriminator.

13. After the feed-back loop is completed, I will proceed to compare the frequency-noises of the green-beat lock and the IR-beat lock.

  5040   Wed Jul 27 01:58:23 2011 kiwamuUpdateLSClocking status

Through some locking exercise I found that several things are degrading.

Remember the interferometer is like a cat, so we have to feed and take care of her everyday. (Otherwise the cat will be dead !)

 

Beam axis:

 I guess that the beam axis has changed a lot to the horizontal direction.
The beam spots on the REFL and AS camera looked off-centered by a size of the spot.
The beam axis has to be well-aligned before the vent.

 

Locking of the Arms :

 didn't lock at all. It could be a problem of the demodulation phase on AS55.
Also the TRY camera looked pretty much off-centered. The spot is already getting out from the field of view.
We have to fix this issue, otherwise we cannot align the beam axis.
 
 

Locking of PRM :

 Sort of okay, I was able to lock both MICH and PRCL although I had to flip the sign of the MICH control gain due to the demod-phase change.
The suspensions don't look healthy. The beam spots on the REFL and AS camera move a lot even without any length feedback.
It means some of the suspensions are shaky.
  5041   Wed Jul 27 08:59:10 2011 SureshUpdateLSClocking status

 I had to realign PSL beam into the MC in order to reobtain the MC lock.  We lost lock at sometime around 8:30 AM on Tuesday.  See attached trend data for MC_RFPD_DCMON. 

The is the second time this week that I had to do this when we were unable to obtain the MC lock.  On both occassions the zig-zag at the end of the PSL table was tweaked to minimise the MC_RFPD_DCMON.

MC_RFPD_DCMon.png

 We have been using the MC as a Beam Axis Reference.  And therefore we are adjusting the PSL beam to maximise coupling into MC.  However if MC's beam axis has shifted, then would it not be best to use the pzt's to re-obtain coupling into the arm cavities? 

Quote from #5040

Beam axis:

 I guess that the beam axis has changed a lot to the horizontal direction.
The beam spots on the REFL and AS camera looked off-centered by a size of the spot.
The beam axis has to be well-aligned before the vent.

  5042   Wed Jul 27 10:04:29 2011 SureshUpdateIOOWFS transfer function measurements

This is part of the WFS activity.  So far I have completed the following tasks:

1)  I fixed the MEDM screens up to a point where they can be used for locking.  There are still some buttons which invoke non-existing screens and some blank fields.  But the basic filter banks and input  and output matrices are fixed.

2) I copied all the old filter banks into the new screens both in the WFS head and in the WFS Master, where the servo filters are located.  The I and Q filter banks in the WFS heads have been switched on.

3) I <=> Q phase settings in the WFS head for each quadrant:  We have assumed that the I and Q are orthogonal so D=90 for all cases.  I set the R phase to minimise the signal in all the Q lines.  So the signal is largely in the I phase.  I used Sine Response feature in DTT while supplying an excitation signal to MC2_ASCPIT_EXC.  At times I used the YAW instead of PIT if I did not get enough coherence.  This was set manually by watching the Q phase signal and minimising that by adjusting the R angle.  It was in general possible to get this correct to a deg.   There are several old scripts to do this in the MC/WFS but they do not work since most of them are based on the ezlockin or ezcademod functions.    I will try to fix the ezWFS1phase and ezWFS2phase scripts to automate this.  Some channel names have to be changed in these.

4) I measured the transfer function between the mirror motions [(MC1, MC2, MC3) x (PIT, YAW)] and the sensor DoF [(WFS1, WFS2) x (PIT, YAW)].  The measurements are reported below.  The plan is to invert this matrix and use it as the Out_Matrix.

WFS_TF_Phase_Sheet1.png

I list here the various steps I took in making this measurement.

a) Set the DC offsets on the individual quadrants to zero using an old script (which I updated with the new channel names).  The script is called McWFS_dc_offsets and is located in the $scripts$/MC/WFS directory.   Note that before doing this the PSL shutter was closed.  This script sets a basic EPICS parameter called AOFF for each channel.  These are listed in cvs/cds/caltech/target/c1iool0 .

b) Then the PSL beam into the MC was steered to optimise coupling into MC (described in my earlier post today).  This is because we use the input beam as a reference while setting up the WFS.

c) Unlock the MC and center the directly reflected beam from the MC on the WFS.  We use the DC monitors on the C1IOO_WFS_QPD.adl screen to center the spot on the WFS head. 

d) Then used the WFSoffsets script to set the offsets in the I and Q filter banks to zero.  This script uses the ezcaservo to look at the OUT16 channels and zeroes them by setting an appropriate offset.  I took care to switch off all slow filters in the I and Q filter banks before this operation was carried out .  Only the 60Hz comb filter was on.

e) Opened the PSL shutter and relocked the MC

f) Then I measured the transfer co-efs by oscillating the optic (exciting a specific degree of freedom) and observing the response in the WFS sensor degrees of freedom.   These are tabulated above.

Next

   I plan to use this matrix and prepare the Output matix and then close the WFS servo loops. 

 

 

  5043   Wed Jul 27 10:10:12 2011 steveUpdatePSLlocking status

 80 days: PMC is drifting

Attachment 1: 80dpmcMC.jpg
80dpmcMC.jpg
  5047   Wed Jul 27 15:38:01 2011 steveUpdateVACbeam traps for vacuum

We have cleaned, baked, rga scaned traps for vacuum. Thorlabs LB1 on 1" OD ss posts and forks. The effective surface area is 43 x 18 mm of stacked razors.

Seven pieces are mounted on New Focus #9962  1" OD SS vented-  pedestrals to 5.5" center height and 5 pieces to 4.875"

Attachment 1: P1080095.JPG
P1080095.JPG
  5050   Wed Jul 27 15:49:56 2011 steveUpdateSAFETYManuel receives safety training

Our surf student Manuel Marchiò received 40m specific safety training today.

Attachment 1: P1080096.JPG
P1080096.JPG
  5051   Thu Jul 28 02:33:04 2011 JenneUpdateLockingYarm flashing, but not yet locked

Because I'm too lazy to write a cohenrent elog right now, here's my notes that I wrote while working tonight:

Elog notes, 27July2011

Aligned Xarm, just to check on it.  Had to flip sign of TRX in DCPD filter bank (to gain of -1) to make the signal positive.

Restored Yarm, see some slight flashing, but no lock yet.
Adjusted phase rotation of AS55 from 56.5deg to 60deg, just by-eye trying to maximize AS55I, my arm error signal. AS55I goes from ~ -40 to +60 counts

Tried fitzing with Yarm gain, flipping sign, incr gain. No real change in signals, or flashing.


Incr. ETMY oplev gains to -0.4 from -0.2
Engaged ELP35's on Pit and Yaw, to be more similar to other optics.  However, right now all of the optics have different things in their filter banks.  Why??

Arm is flashing pretty reliably now, but still not locking.  The trigger threshold is always satisfied, so that's not it.

  5052   Thu Jul 28 13:51:00 2011 SonaliUpdateGreen LockingZHL-32A-S.

Initially I was using RFPD-1611to get the IR beat frequency. Its gain was not very high, so I was getting a very low signal of power -37 dBm.

I used ZHL-32A-S with a gain of 25 dBm to amplify it before feeding it into the spectrum analyser.

I connected the ground of the amplifier circuit to the red of the power supply, which blew the amplifier.

I learnt that there is a small tab indicating the ground side of the BNC to banana connectors which I should have noticed.

I learnt to plug in the side with th little tab on it into the ground of the power supply. (Learnt it the hard way I guess!!)

 

 

  5053   Thu Jul 28 16:00:28 2011 kiwamuUpdateComputer Scripts / Programsanother offset script : offset2

A new offset-zeroing script has been developed and it is ready to run.

 

 The motivation is to replace the old zeroing script called offset by a better one because this old script somehow failed to revert the gain settings on a given filter bank.

The new script, named offset2, does the same job, but uses tdsavg instead of using ezcaservo. So it doesn't screw up the gain settings.

Additionally the structure of the script is much simpler than the old offset script, and fewer ezca-functions.

I will modify some scripts which use the old offset script so that all the offset-zeroing is done by offset2.

 

P.S.

Useful scripts are listed on the 40m wiki

http://blue.ligo-wa.caltech.edu:8000/40m/Computers_and_Scripts/All_Scripts

  5054   Thu Jul 28 16:10:34 2011 kiwamuUpdateLSCBoth arm locked

[Nicole / Jamie / Rana / Kiwamu]

  The X arm and Y arm have been locked.

The settings for the locking were stored on the usual IFO_CONFIGURE scripts, so anybody can lock the arms.

In addition to that Nicole, Jamie and Rana re-centered the beam spot on the ETMY_TRANS camera and the TRY PD.

The next step is to activate the C1ASS servo and align the both arms and beam axis.

 

 

Xarm locking notes:

* Changed TRX gain from -1 to -0.02. Without this 50x reduction the arm power was not normalized.

* Had to fix trigger matrix to use TRX for XARM and TRY for YARM. Before it was crazy and senseless.

* Lots of PZT alignment. It was off by lots.

* Yarm trans beam was clipping on the steering mirrors. Re-aligned. Needs to be iterated again. Be careful when bumping around the ETMY table.

* YARM gain was set to -2 instead of -0.2. Because the gain was too high the alignment didn't work right.

ALWAYS HAVE an OPEN DATAVIEWER with the standard ARM channels going when doing ANY INTERFEROMETER WORK.

THIS IS THE LAW.

  5055   Thu Jul 28 16:26:42 2011 steveUpdateSUSITMX, ITMY & ETMY OSEM gains adjusted

 

OSEM damping gains were adjusted by observing  real time dataviewer to get Q of 5

OSEMs were kicked up one by one with 200 counts  ~1sec. The error signal was optimized to get 1/2 of exitation amplitude at the 5th sinusoid wave.

C1: SUS-ITMX_SUSPOS_N1 gain   111      ->        65,             PIT        7.2      ->    8,           YAW        12      ->     6,          SIDE     280

                  ITMY                                      277       ->     120,                        19.2     ->     7,                             24     ->     19,                        420    ->      470

                  ETMY                                       10        ->       32,                          20      ->     3,                             20     ->     10,                          50

                  ETMX                                       22        ->      25,                             3,                                                3,                                              -170  

ETMX having problems:  1, YAW can not be excited

                                             2, SIDE has no error signal in dataviewer. Sensing voltage on MEDM screen 0.142V

 

                      

 

  5056   Thu Jul 28 17:04:04 2011 NicoleUpdateSUSPhotosensor Head Calibration Curve

Here is the calibration curve (displacement versus voltage output) for the photosensor head that I made with the S5971 photodiodes and L9337 LEDs. This was made using a regular mirror. The linear region appears to be between 0.4 and 0.75cm. I will need to arrange the photosensor head so it measures displacements in the linear region of this plot. This plot was made using a 287 ohm resistor.

187K_resistor.jpg

  5057   Thu Jul 28 19:49:12 2011 SonaliUpdatePSLPMC trans beam aligned.

Kiwamu and I aligned the PMC transmitted beam the incident beam going to PMC today.

I learnt how to lock the PMC using the digital controls.

  5058   Thu Jul 28 21:52:40 2011 ranaUpdateComputersanother attempt to use pianosa
  1. Pianosa doesn't cache the SVN pwds so you need to re-enter at each SVN up or commit. This is different from the rest of our workstations. We need to determine what behavior we want.
  2. Tried to use the netGPIB scripts:

pianosa:gpib 0> ./readSR785.csh rb2
rb2
netgpibdata.py: Command not found.

  5059   Fri Jul 29 12:25:54 2011 Ishwita, ManuelUpdatePEMSTS-2 seismometer box

The 'Bacardi' STS-2 seismometer was tested with the "purple" breakout box and it was found out that all the three axes gave a voltage of 11 V (as shown on the screen of the oscilloscope) before pressing the auto-zero button and after pressing it the voltage shown was 6 V. We tried again the blue box and it was working perfectly after pushing the auto zero button (the auto zero took a few seconds). The power of the purple box is still on, we will wait a few hours, to see if something changes.

  5060   Fri Jul 29 12:39:26 2011 jamieUpdateCDSc1iscex mysteriously crashed

c1iscex was behaving very strangely this morning.  Steve earlier reported that he was having trouble pulling up some channels from the c1scx model.  I went to investigate and noticed that indeed some channels were not responding.

While I was in the middle of poking around, c1iscex stopped responding altogether, and became completely unresponsive.  I walked down there and did a hard reset.  Once it rebooted, and I did a burt restore from early this morning, everything appeared to be working again.

The fact that problems were showing up before the machine crashed worries me.  I'll try to investigate more this afternoon.

  5061   Fri Jul 29 16:04:51 2011 steveUpdateSUSETMX, PRM & SRM OSEM gains set

Jamei fixed the computer. Now I had a healthier ETMX with SIDE signal that allowed me to set gains to get Q of 5

The Y arm restore locked the arm at TRY -out 2.4V,    the X arm still did not lock or align to lock. It has some fringes.

ETMX  POS gain   22  -> 17,              PIT  3  ->  1,                    YAW  3,                     SIDE     -170    ->    -110

PRM                        50  ->  30,                     1,                                       2,                                       50

SRM                        55  ->  20,                    2.4  ->  1.5,                      4.8  ->  2,                          140   ->    100

Now all SUS OSEM gains are set

  5062   Fri Jul 29 16:25:06 2011 kiwamuUpdateASCbeam axis and Y arm aligned

Last night I aligned the incident beam axis and the Yarm by touching the PZT mirrors and the suspensions.

I didn't estimate how good they were aligned, but I guess the Y arm is now ready for the Y green light.

 Next : Y green alignment and the MC spots measurement / alignment.

 

 ++ Motivation ++

Prior to the coming vent we want to have the Y arm, incident beam axis and Y green light aligned so that we can align some necessary optics in the chamber.

Also alignment of the incident beam will allow us to re-position the incident beam alignment monitor (i.e. IPPOS and IPANG).

Our plan was to first align the Y arm using the ASS system and then align the Y green light to the Y arm.

 

++ what I failed ++

First I was trying to measure the spot positions on the MC mirrors to make me sure the beam axis has/hasn't changed.

Also I was going to align the MC suspensions to have nice spot position on each suspension using the MCASS system

because this will help us checking the beam clearance in the Faraday and perhaps re-positioning of the Faraday during the coming vent.

But essentially I failed and eventually gave up because MCASS didn't work. It seems that MCASS needs some modifications in the scripts.

Then, to make me feel better I moved on to the Y arm and beam axis alignment.

 

++ what I did ++

I tried using C1ASS to align the incident beam and suspensions on the Y arm, but it didn't work.

However the drive signals from ASS and its demodulated signals looked fine. Only the feedback did not work correctly.

Every time I enabled the feedback paths, the arm just lost the lock. Something is wrong in the feedback paths.

Then I started to align the cavity by my hands while looking at the demodulated signal from each LOCKIN module.

I aligned the things until each demodulated signal fluctuates around zero.

At the end the beam spots on the ETMY and ITMY camera looked well-aligned and the transmitted light became larger by a factor of 2ish.

  5063   Fri Jul 29 18:43:02 2011 Manuel, IshwitaUpdatePEMplugging seismometers to ADC

[Manuel, Ishwita, Jenne, Jamie]

We changed the C1PEM model and the names of the C1:PEM channels.

We reinstalled the blue breakout box, since the purple one still didn't work.

So, now the AA board channels are connected as follows...

C1 = C1:PEM-SEIS_GUR1_X

C2 = C1:PEM-SEIS_GUR1_Y

C3 = C1:PEM-SEIS_GUR1_Z

C4 = C1:PEM-SEIS_GUR2_X

C5 = C1:PEM-SEIS_GUR2_Y

C6 = C1:PEM-SEIS_GUR2_Z

C7 = C1:PEM-SEIS_STS_1_X

C8 = C1:PEM-SEIS_STS_1_Y

C9 = C1:PEM-SEIS_STS_1_Z

C11 = C1:PEM-SEIS_STS_2_X

C12 = C1:PEM-SEIS_STS_2_Y

C13 = C1:PEM-SEIS_STS_2_Z

C14 = C1:PEM-SEIS_STS_3_X

C15 = C1:PEM-SEIS_STS_3_Y

C16 = C1:PEM-SEIS_STS_3_Z

C17 = C1:PEM-ACC_MC1_X

C18 = C1:PEM-ACC_MC1_Y

C19 = C1:PEM-ACC_MC1_Z

C20 = C1:PEM-ACC_MC2_X

C21 = C1:PEM-ACC_MC2_Y

C22 = C1:PEM-ACC_MC2_Z

Although the channels for all 3 STS-2 seismometers are made but only one is installed. So only Channels C1 to C9 are now in operation...

We checked the data from the plugged channels with the Dataviewer. We could see the peak whenever someone jumped in the lab. Even Kiwamu jumped and saw his signal.

  5064   Sat Jul 30 00:33:33 2011 KojiUpdatePSLABSL Laser crystal temp left largely excited & left unattended for more than 3hours

I found that the ref cav trans CCD view was blinking with 30-50 fringe amplitudes. This meant the laser freq was swinging ~50GHz.

I checked the ABSL laser and the SG out of a lock-in amplifier was connected to the slow input.

This was shaking the laser temp from 29degC to 46degC. This was the cause of the fringe swinging.
This big excitation changing the output power too as the temp was changed across it mode-hop region.

I have disconnected the excitation from the laser no matter how useful experiments were took place as there was no e-log entry about this.

I need the explanations

1. Why our precious laser is exposed to such a large swing of temperature?

2. Why the excitation is left like that without any attendance?

3. Why there was no elogging about this activity?

  5065   Sat Jul 30 02:47:43 2011 ranaUpdatePSLABSL Laser crystal temp left largely excited & left unattended for more than 3hours

 Hmm. Should have only been +/- 1 GHz. Some setting got changed apparently...

This is a part of the RefCav temperature measurement setup. You'll get an elog from Jenny very soon.

  5066   Sat Jul 30 05:11:45 2011 SureshUpdateGreen LockingY- end table clean-up

The optics on the Y-end table which required to be moved have been repositioned.  Please see the attached pic for details.

The green beam is not yet aligned to the cavity. That is my next task.

Y-end_table_work.png

  5067   Sat Jul 30 06:24:06 2011 kiwamuUpdateASCY arm ASS fixed

The servos of C1ASS for the Y arm and the beam axis alignments were fixed.

Now we can correctly run the Y arm ASS from the C1IFO_CONFIGURE window as usual.

The sign of some control gains had been flipped for some reasons, so I changed them to the correct signs.

 

Next : Health-check for the X arm ASS, the loss measurements.

Quote from #5062

I tried using C1ASS to align the incident beam and suspensions on the Y arm, but it didn't work.

 

ELOG V3.1.3-