40m QIL Cryo_Lab CTN SUS_Lab CAML OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 159 of 349  Not logged in ELOG logo
ID Date Author Typeup Category Subject
  5914   Wed Nov 16 17:29:46 2011 kiwamuUpdateGreen LockingSome updates on the Y end green PDH
Quote from #5894

 (Things to be done)

   [DONE]   1.1 Measurement of the arm fluctuation => to allow re-designing the servo shape
   [DONE]   1.2 temporary SR560 servo
   [ONGOING]1.3 Sanity checks on the modulation depth, reflectivity, PD dark noise and etc.,
   [DONE]  1.4 Make the servo more robust
   [DONE]  1.5 Some modifications on the medm screens
   [NOTYET]   1.6 Activation of the temperature feedback through the realtime digital control

Some updates on the Y end green PDH lock

(Measurement of the Y arm fluctuation)

In order to design the PDH box's servo shape we wanted to measure the Y arm fluctuation.
Here is the spectrum taken by looking at the control signal before the laser PZT.
 
 Yarm_fluctuation.png
 The scale of the Y axis is calibrated by using the PZT response of 5 MHz/V.
Above 10 Hz the spectrum shows 1/f noise which I believe the laser frequency noise.
 

(Temporary servo setup)

 We have found that the servo shape was not enough (#5890) to well-suppress the fluctuation shown above.
 Since the Newfocus fast servo box only makes 1/f shape, the error signal wasn't suppressed within the linear range.
So I have added an SR560 in the other input of the Newfocus servo box to make the filter shape 1/f^2.
Then the lock became more solid and the reflected DC light in time series is now much flat if the alignments are good.
I will post the servo shape and diagram later.

(Sanity checks)

 I looked at the reflected DC light when the laser was kept locked.
The reflectivity of the Y arm cavity went down to about 30% and this is good because it is supposed to be 27.5% when it is locked according the spec.
This means the mode-matching is not so bad.
  5915   Wed Nov 16 17:40:48 2011 MirkoUpdateIOOMC unlocked and misaligned.

MC fell out of lock and was then quite badly misaligned. Mostly in pitch. I realigned it and it locked ok.

Turns out the MC falls often out of lock when the WFS servo comes on. I think the MC2_Trans history is not cleared on lockloss. I cleared it manually and realigned. Seems fine for now.

  5916   Wed Nov 16 18:14:09 2011 KojiUpdateIOOMC unlocked and misaligned.

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

  5917   Wed Nov 16 20:30:27 2011 not KojiUpdateIOOMC unlocked and misaligned.

Quote:

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

 I suspect the integrators get fed a huge wrong signal on lockloss. Clearing the history on the trans DOFs when the MC was badly aligned gets it nicely aligned again. I switched off the alignment transmission DOFs for now.

  5918   Wed Nov 16 21:01:08 2011 JenneUpdateTreasureeom box

I made a super sweet new foam box for our EOM.  It's awesome, and should be reasonably easy to duplicate.  Check out the PHOTOS!

Notes:

* I didn't think I was going to cover the inside of the box at first, since the foam is non-fuzz-generating, but Koji suggested it would be a good idea anyway.  The foam was cut perfectly to the EOM, so adding the tape inside makes it a tight fit.  Especially height-wise...leave a little space next time.

* To cover the insides of the optical path holes, do it in 2 parts.  One half-cylinder, and then another.  Way easier than trying to do the whole thing at once.  Also, pre-cut the tabs on both sides of the foil before inserting.  Then you just have to grab the tabs with tweezers and flatten them, and they hold the aluminum tape in place. 

* Having 1" wide, 2" wide and 3" wide aluminum tape was handy.  3" to make the top, 2" for the sides, and 1" for the inside of the holes. 

  5919   Wed Nov 16 23:50:40 2011 DenUpdateAdaptive Filteringseismic noise injection

[Micro, Den]

Analyzing coherence of seismic noise and mode cleaner length we've figured out that at some days the coherence below 1 Hz is still present. For example, at Nov 13 we can see some coherence compared to most other dates when we are not able to see coherence as shown on the figure. On the top plot - psd of MC_L and GUR1_X at Nov 13 (red and blue) and Nov 15 (black and cyan). On the bottom plot is presented coherence between MC_L and GUR1_X on Nov 13 (red) and Nov 15 (black)

datespsd.jpg

datescoh.jpg

We can divide the psd plot for 2 parts - below 1 Hz and above 1 Hz. Above 1 Hz seismic noise on Nov 15 (cyan) was higher then on Nov 13 (blue) and correspondently MC_L at that region was higher on Nov 15. Below 1 Hz seismic noise was higher on Nov 13 but MC_L is still lower that on Nov 15. That is surprising. From the coherence plot we can say that once we have some more seismic noise than usually, we immediately see coherence.

Because of this we wanted to find out the level of the X noise that makes seismic noise invisible. We injected seismic noise by doing smooth physical exercises near MC_2 (1.5 m and 3 m apart). The MC_2 was in lock during the experiment.

injectionpsd.jpg

injectioncoh.jpg

In the coherence plot we can see that coherence between GUR1_X and MC_L increased with noise injection. The highest coherenced we obtained sittind down and standing up smoothly near MC_2 at distance 1.5 m. We did not want to come clother and break the lock. This measurement tells us that the X noise is approximately 3-4 times higher than seismic noise in the range 0.1 - 1 Hz. That means that it is approximately 1e-6 - 1e-8 m/sqrt(Hz) in this region. This noise goes down at frequencies from 2 Hz and not seen because of seismic noise. Actually, seismic noise can be filtered out with the Wiener filter and then we'll see the spectrum of X noise.

We now try to figure out the method to estimate the contribution of OSEM noise to the X noise.

  5920   Thu Nov 17 03:46:52 2011 kiwamuUpdateGreen LockingPSL doubling had been diabled

I found that the temperature controller of the PSL doubling oven had been disabled.

Because of that I took a little bit long time to recover the beat-note.
I have no idea why its been disabled.
I turned it on to make the PSL green beam bright,
Also the I-parameter of the PID temperature control was too big
and because of that a big overshoot in the temperature happened (overshoot of ~ 5 deg !).
So I decreased the I-parameter from 175 to 85 (250 is the maximum).
Now the intensity of the green light seems reasonably bright and stable.
  5921   Thu Nov 17 11:04:02 2011 JenneUpdateRF SystemStochmon?

Is there an update on Stochmon?  Are the signals acquired somewhere already?  What's the current deal-io?  The new EOM mount should be here later today, and I'm jazzed to start checking how my EOM box helps (hopefully) the amount of RFAM we see. 

I'll start making the adapter plate while I wait...

  5922   Thu Nov 17 11:27:58 2011 JenneUpdatePSLHEPA turned down

I was measuring things to see how big my adapter plate needs to be, and I decided that we'd had enough days of the HEPA being on full blast, so I turned it down to 50, from 100.  I think it's been on full since Katrin was working on the Y-green beat a week or so ago.

  5923   Thu Nov 17 11:35:27 2011 KojiUpdateRF SystemStochmon?

The  Stochmon channels for 11&55MHz have been reasonably working since last night.

The output is not yet calibrated as the RF power detector has a strange scaling.
I am analyzing the calibration data.

  5924   Thu Nov 17 11:51:14 2011 JenneUpdateEnvironmentIncandescent vs. fluorescent lights?

I'm just on an elog roll this morning...

Again while poking around inside the IFO room, I noticed that they have replaced all of our incandescent lights with CFLs.  Do we care?  The point of having the incandescent lights on a separate switch from the big fluorescent lights was so that we could have only 60Hz lines, not wide-band noise if we want the lights on while locking. 

I'm not sure that we actually care, because more often we just turn off all the lights while trying to do serious locking, but if we do care, then someone needs to ask the custodial staff (or someone else?) to undo the change.

  5925   Thu Nov 17 13:58:12 2011 SureshUpdateIOOMC unlocked and misaligned.

Quote:

Quote:

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

 I suspect the integrators get fed a huge wrong signal on lockloss. Clearing the history on the trans DOFs when the MC was badly aligned gets it nicely aligned again. I switched off the alignment transmission DOFs for now.

I have modified the 'mcwfson' and 'mcwfsoff' scripts to include the Clear History step for the MC2_TRANS_PIT and _YAW filters.  

These scripts can be run, by hand, from LOCKMC screen or from the WFS_MASTER screen.  Use the 'Turn WFS ON/OFF' button. 

The mcautolockmain script will now clear history on all ASC filter banks when the MC unlocks.

I have turned on ASC loops on the MC2_TRANS (= alignment transmission DOFs of the above elog) paths.

 

 

  5926   Thu Nov 17 14:38:16 2011 ZachUpdateRF SystemStochmon?

It turns out that we don't have all the parts I would need to do a full prototype of the precision temperature controller. I am guessing that we won't want to sit around and wait for the parts given the upcoming TAC meeting, so I'll do the next best thing:

  • Standard DC temperature readout using an AD590.
  • More-or-less complete heater driver

Does anyone have a suggestion for how this thing will be packaged? I.e., should it be in a box or should it be mounted in a rack, etc. In the end, a real board will be printed and stuffed, so this need not be a really professional job in the short term.

 

Quote:

Is there an update on Stochmon?  Are the signals acquired somewhere already?  What's the current deal-io?  The new EOM mount should be here later today, and I'm jazzed to start checking how my EOM box helps (hopefully) the amount of RFAM we see. 

I'll start making the adapter plate while I wait...

 

  5927   Thu Nov 17 15:19:06 2011 steveUpdateSUSTi spring plunger to hold OSEM is not affortable

Our existing 300 series SS plungers from McMastercar #8476A43 are silver plated as Atm2 shows.

Problems:  1, they become magnetized after years being close to the magnets

                     2, they oxidize by time so it is hard to turn them

                    

I looked around to replace them.

Titanium body, nose and beryllium copper spring. None magnetic for UHV enviorment.

Can be made in 7 weeks at an UNREASONABLE $169.00 ea at quantity of 50

Attachment 1: 20111116111042405.pdf
20111116111042405.pdf
Attachment 2: P1080216.JPG
P1080216.JPG
  5928   Thu Nov 17 17:03:28 2011 MIrkoUpdateIOOMC noise projection

Another go at the noise projection from MC1-3 pit/yaw to MC length. This time injecting into the MC autoalignment FB (e.g. C1:IOO-WFS1_PIT_EXC ).

LTPDA is working now, but still the NDS server is not so cooperative.

Summary: Alignment fluctuations of the MC mirrors don't significantly contribute to MC length changes up to at least 3.5Hz. Especially they can't explain the lack of coherence between seismometers and MC length below 1Hz that we worry about for the OAF.

At high frequencies >= 10Hz you can see angle to length coupling as is evident in Sureshes spot position measurements.

Whiteish noise injection:

Injection from 0.1-20Hz.Filtered by the servo filters and zp:[1],[1] , Gain = 1 @ 2Hz

 MCLengthToAngleCouplingNoiseProjection.png

Look at the coherence plots for the quality of the measurement:

Coherence_WFS1pit.png

Coherence_WFS2pit.png

 

Coherence_WFS1yaw.png

 Coherence_WFS2yaw.png

Injection details:

DOF      Amplitude[counts]        UTC Time (duration always 4mins)
WFS1p  70                               22:28
WFS1y  55                               22:03
WFS2p  70                               22:13
WFS2y  70                               22:18
None      -                                 22:23

Fixed sine injections:

To get some better SNR at low frequencies I did a fixed sine noise injection at 0.3Hz. See attached files.

DOF      Amplitude[counts]        UTC Time (duration always 4mins)    Lower limit of SNR MC length via mirror misalignment
WFS1p  4                                  00:05                                                29.3
WFS1y  4                                  00:14                                                22.0
WFS2p  4                                  00:19                                                18.5
WFS2y  4                                  00:25                                                18.0

Attachment 2: WFS1pit.png
WFS1pit.png
Attachment 3: WFS1yaw.png
WFS1yaw.png
Attachment 4: WFS2pit.png
WFS2pit.png
Attachment 5: WFS2yaw.png
WFS2yaw.png
Attachment 7: Coherence_WFS2pit.png
Coherence_WFS2pit.png
Attachment 11: NpWfs.pdf
NpWfs.pdf NpWfs.pdf NpWfs.pdf NpWfs.pdf NpWfs.pdf
  5929   Thu Nov 17 17:21:22 2011 kiwamuUpdateGreen LockingY end green PDH servo : it's okay

Quote from #5914
So I have added an SR560 in the other input of the Newfocus servo box to make the filter shape 1/f^2.
I will post the servo shape and diagram later.

The Y arm green PDH servo is working fine with a sufficient amount of suppression.

(Servo filters)

 As reported on the previous elog entry (#5914) an SR560 was installed to provide one more pole-zero combination in the servo filter.
Here is a plot showing the transfer function of the latest servo filter.
   servoTF.png

And the servo configuration looks like this :

  servofilter.png

 The demodulated signal is split into two path; one goes directly to the Newfocus servo box and the other goes through SR560.
With the SR560 the two way summing path makes a pole at 1 Hz and zero at 100 Hz with when the SR560 has a gain of 100.
The overall gain is adjustable from a knob on the Newfocus servo box.
 

(the Error signal)

 One of the reasons we wanted to increase the servo gain was that :
the laser frequency has to be tightly locked to the Y arm motion because the laser frequency must represent the arm motion in our scheme.
 
Our requirement for allowing a successful ALS is : RMS < 10 pm (1/100 of the cavity linewidth)

I took a spectrum of the error signal when the laser was locked to the Y arm and found that it meets the requirement.

   err_suppression.png

 In the plot I also put a dark noise from the PD to make sure the in-loop noise is above the dark noise.
Right now the power lines at 60 Hz and 180 Hz are lifting the RMS up.
Note that the UGF was at 20-30 kHz.
  5930   Thu Nov 17 18:20:26 2011 kiwamuUpdateGreen LockingY arm ALS : 1st trial of noise budget

The noise budget on the Y arm ALS has begun.

Right now the fluctuation of the green beat-note seems mostly covered by unknown noise which is relatively white.

(Though I feel I made a wrong calibration ... I have to check it again)

 

Yarm_ALS_2011Nov16.png

(Measurement condition)

 + The Y arm is locked to the PSL laser by acting o ETMY.
 + The end green laser is locked to the Y arm.
 + The fine resolution MFD (Mixer-base Frequency Discriminator) is used to observe the beat-note fluctuation
   (We have two MFDs : fine resolution and coarse resolution.)
  5931   Thu Nov 17 21:12:09 2011 KojiUpdatePSLHEPA setting changed

[Koji, Suresh]

8:50PM HEPA@100% for the test

8:55PM HEPA@0%

9:20-35PM HEPA level varies from 0%-50%

9:35PM HEPA@40% and left it running at this level

Nov18 1:40 AM HEPA@80% for a work around the PSL table (by KI)

Nov18 4:35 AM HEPA@40% (by KI)

  5932   Thu Nov 17 22:24:19 2011 DenUpdateAdaptive FilteringMC1_COIL

Analyzing coherence between MC length and signals on MC1, MC2 and MC3 coils we have noticed that MC1 COIL signal is not coherent to MC length at all at interesting frequencies 0.1 - 1 Hz.

We try to explain this phenomena.

 

Attachment 1: MC1COIL-crop.pdf
MC1COIL-crop.pdf
Attachment 2: MC2COIL-crop.pdf
MC2COIL-crop.pdf
Attachment 3: MC3COIL-crop.pdf
MC3COIL-crop.pdf
  5933   Thu Nov 17 23:38:40 2011 DenUpdateIOOMC unlocked

MC is unlocked to measure the free swing of the MC mirrors with the local sensors.

Autolocker is disabled.

  5934   Thu Nov 17 23:44:48 2011 DenUpdateIOOMC1_SENSOR

We've found that one of the  MC1_SENSORS does not work properly.

See the figure.

Attachment 1: MCSENSORS.pdf
MCSENSORS.pdf
  5935   Thu Nov 17 23:47:43 2011 DenUpdateIOOMC1_SENSOR

The most interesting plot did not uploaded in the previous elog.

Upload now local MC1_SENSOR signals.

Attachment 1: MC1SENSOR-crop.pdf
MC1SENSOR-crop.pdf
  5936   Fri Nov 18 00:25:10 2011 ZachUpdateelogrestarted

 with script.

  5937   Fri Nov 18 00:36:23 2011 ZachUpdateGreen LockingY-Arm PDH box modified

I modified the Y-Arm PDH box (S/N 17) to have the same TF as the one of the temporary setup described in Kiwamu's earlier entryNote that the TF below was taken with the gain knob set to 0, so that the proper DC gain is achieved with a setting of ~4. This is desirable because it gives us wiggle room.

The changes were:

  • R14: 25 -> 50
  • R29: 1k -> 10.5k
  • R30: 1k -> 20k
  • R28: 102 -> OMIT
  • C20: 84nF -> OMIT
  • R31: SHORT -> 475
  • R16: 10k -> 48.7k
  • R24: 10 -> 5

Below is the TF along with the LISO model. They are different at low frequencies because the box must have been railing internally (though the phase shows that the result is as expected), and there is a feature around 60 kHz that probably arises from some op amp instability. I will see if adding a small cap somewhere does the trick, and then take a new TF with a lower source voltage.

pdh17_tf_vs_liso_11_17_11.png

I'll try to lock the arm with the box tomorrow.

  5938   Fri Nov 18 01:12:14 2011 SureshUpdateCDSMC1 LR dead for > 1 month; now revived temporarily

[Den, Mirko, Suresh]

    We were investigating why there is no correlation between MC1 osem signals and seismic motion.   During this we noticed a recurrence of this old problem of MC1_LR sensor being dead.  I went and pressed down the chip holders where the AA filters used to sit and which now hold the jumper wire.  The board is large and flexible it is quite likely some solder joint is broken on the MC1_LR path on this board.

   The signal came back to life and is okay now. But it can break off again any time.

 

 

Quote:

 Since the MC1 LRSEN channel is not wasn't working, my input matrix diagonalization hasn't worked today wasn't working. So I decided to fix it somehow.

I went to the rack and traced the signal: first at the LEMO monitor on the whitening card, secondly at the 4-pin LEMO cable which goes into the AA chassis.

The signal existed at the input to the AA chassis but not in the screen. So I pressed the jumper wire (used to be AA filter) down for the channel corresponding to the MC1 LRSEN channel.

It now has come back and looks like the other sensors. As you can see from this plot and Joe's entry from a couple weeks ago, this channel has been dead since May 17th.

The ELOG reveals that Kiwamu caught Steve doing some (un-elogged) fooling around there. Burnt Toast -> Steve.

bt.jpg

993190663   =      free swinging ringdown restarted again

 

  5939   Fri Nov 18 01:27:04 2011 DenUpdateIOOMC locked

[Mirko, Den]

While the MC was unlocked (and the local damping off) we've measured the coherence between GUR1_X and OSEM sensors. It was rather high, close to 1 at frequencies 0.1 - 1 Hz. That means that stack does not kill all coherence between seismic noise and mirror motion.

Then we've turned on the local damping and measured the coherence again between GUR1_X and OSEM sensors. It decreased due to some noise and was on the level of ~0.5. We did reduced the motion between the mirror and the frame by local damping but it is not obvious that we lost some coherence due to this effect. Probably, actuator adds some noise.

When we locked the MC, we did not see any coherence at 0.1 - 1 Hz between GUR1_X or STS1_X and OSEM sensors of MC1 and MC3 but we did see with MC2. The MC1 sensor was fixed by Suresh.

 

Attachment 1: cohnolocalpumping-crop_4.pdf
cohnolocalpumping-crop_4.pdf
Attachment 2: cohlocalpumping4-crop.pdf
cohlocalpumping4-crop.pdf
Attachment 3: cohlock4-crop.pdf
cohlock4-crop.pdf
  5941   Fri Nov 18 01:51:37 2011 KojiUpdateIOOStochmon update

Update of the stochmon status

[Attachment 1: Circuit diagram]

- The new stochmon has a low noise amplifier (MAR-6SM) inside.
The RFAM signal from the PD has the power of -60~-50dBm, which is almost at the bottom of the sensitivity for the power detector.

- The band pass filters were doubled.

- I've suffered from some RF coupling from the power line as the power detector is quite sensitive to it.
The situation has been largely improved by the EMI filters in the power supply path, although the problem is still present.
The worst remaining problem is that we can not close the aluminum lid as it cause a huge sprious coupling.

 

[Attachment 2: Calibration result]

- The outputs were calibarted with Marconi. They showed the signals linear to dBm for the input powers between -70dBm and -10dBm.

- The calibration result was fitted with the empirical fit function. The function and the results are shown in the attachment.

[Attachment 3: Detection limit]

- The attached figure shows the power spectrum of the PD output. This measurement gives us the amount of the RF power given from the PD noise when there is no RF signal.

11MHz out passband noise: −72.7dBm ===> V11 = 2.0483
30MHz out passband noise: −64.6dBm ===> V30 = 1.9333
55MHz out passband noise: −71.2dBm ===> V55 = 2.0272

- Now 11MHz and 55MHz outputs seem indicating the power correctly, but the 29.5MHz output never provides useful information.
It is a constant value independent from the state of the incident beam. Strangely this problem disappears if the marconi is used
for the RF source. Thus this issue is not seen in the calibration measurement.

- So far, 11MHz, 29.5MHz, 55MHz, and DC outputs appear in the channels C1:IOO-RFAMPD_33MHZ, C1:IOO-RFAMPD_133MHZ, C1:IOO-RFAMPD_166MHZ, and C1:IOO-RFAMPD_199MHZ.
They will be renamed.

Attachment 1: stochmon.pdf
stochmon.pdf
Attachment 2: stochmon_calib.pdf
stochmon_calib.pdf
Attachment 3: RFAM_PD_noise.pdf
RFAM_PD_noise.pdf
  5942   Fri Nov 18 02:50:10 2011 kiwamuUpdateIOORF generation box : power switch malfunction

[Suresh / Kiwamu]

 The power switch button of the RF generation box is not properly working

For tonight we are leaving it as it is but it needs to be fixed at some point.

 

(the Story)

While I was working around the green broad-band RFPD, I noticed that the RFPD was detecting the 25 MHz modulation signal.
To confirm if it really comes from the modulation source, I switched OFF the RF generation box by pressing the blue LED power button on the rear side of it.
The 25 MHz signal in the RFPD disappeared. So it was indeed the 25 MHz modulation signal.
Then I pressed the LED button again to bring it ON, but the switch didn't stay in the clicked position.
Keeping pressing the button could make it ON but once I released my finger from it it became OFF.
So the mechanical thing in the LED button is not properly working.
I removed the box from the 1X2 rack to take a look at it.
With a help from Suresh we somehow managed to keep it ON after several trials of pressing it.

The temporary solution we decided is to leave it ON so that we can survive tonight.

The box was back in place. The MC is find and 11 MHz and 55 MHz seem okay.

 

Please be aware of it.

 

broken_power_switch.png

This is a picture showing the rear view of the RF generation box. The red arrow is pointing the blue LED switch button.

  5943   Fri Nov 18 08:29:35 2011 SureshUpdateIOOHEPA air-flow effect on WFS.

[Koji, Suresh]

    We investigated the effect of airflow from the HEPA filters on the PSL beam fluctuation and the resultant noise injected into the WFS loops.   The hint that the WFS are injecting PSL beam jitter into MC mirror motion lies in the MC2_TRANS_PIT and YAW signal's power spectrum shown here.  First, in the blue trace, which shows the spectrum when the WFS loops are off, we see that the WFS1 and WFS2 error signals have a different shape from that of MC2_TRANS.  Since WFS are affected by the PSL beam jitter while the MC2_TRANS_QPD is not, the WFS spectrum contain excess noise, while the MC2_TRANS signals show only the mirror motion.  Next, upon switching on the WFS1 and WFS2 loops, we notice that the MC2_TRANS  spectra acquire the same shape as the WFS spectra.  This shows that the excess noise from the beam jitter has been injected into the MC2 motion, and shows up in the MC2_TRANS spectra.

   To confirm these conclusions we repeated the above measurement with the HEPA fans at 0% (Blue trace), 20% (Red), 30% (Brown) and  100% (Green).   The plots are shown below.  We can see that there is no difference between 0 and 20% levels but beam jitter is visible at 30% HEPA level.  The WFS loops were ON during this time and we can can see the PSL noise injected in to MC2 motion (Green).

WFS_err_HEPA.png

 

The HEPA filter fans are now at 20%.  How can we be sure that they are really working at 20%, since we cannot see any difference between 0 and 20%?

Now that we have this quiet situation, we also investigated the effect (or lack thereof) of switching on the MC2_TRANS loops.  The figure below shows the spectra with all the loops turned off (Blue), with the WFS1 and WFS2  loops turned on (Green)  and with everything turned on (Red).   With the current output matrix, which is the same simple one as the one in this elog, we see some low frequency suppression.  But it also seems to add some noise into the other WFS loops.  I am not sure of this result, due the long duration of this measurement, the seimic noise level may have changed over the course of this measurement.

WFS_err_mc2t_effect.png

As they are not doing any good just now.  I have turned them off by setting the gain in MC2_TRANS PIT and YAW to zero.

 

  5944   Fri Nov 18 11:16:08 2011 ranaUpdateIOOeom box

Quote:

I made a super sweet new foam box for our EOM.  It's awesome, and should be reasonably easy to duplicate.  Check out the PHOTOS!

 These are great photos and a nice box, but I fear from the photos that there's too much air getting in. How to pack it so that there's no air flow? How does the temperature sensors wires get in?

  5945   Fri Nov 18 11:28:39 2011 ranaUpdateGreen LockingY end green PDH servo : it's okay

Quote:

Quote from #5914
So I have added an SR560 in the other input of the Newfocus servo box to make the filter shape 1/f^2.
I will post the servo shape and diagram later.

 Another way to make a 1:100 pole:zero boost is to use resistors and capacitors in a Pomona box 

mixer -> LB box -> Pomona box -> PZT

Pomona Box =     R1 = 7.2 kOhm, C2 = 22 uF, R2 = 72 Ohms     (sr560 = $2400, pomona ~ $50)

 

For the RMS calculation, it would be good to notch out the harmonics. They don't matter since our ALS feedback will have notches at those frequencies.

  5946   Fri Nov 18 12:11:24 2011 ZachUpdateGreen LockingY end green PDH servo : it's okay

Quote:

 

 Another way to make a 1:100 pole:zero boost is to use resistors and capacitors in a Pomona box 

mixer -> LB box -> Pomona box -> PZT

Pomona Box =     R1 = 7.2 kOhm, C2 = 22 uF, R2 = 72 Ohms     (sr560 = $2400, pomona ~ $50)

 

For the RMS calculation, it would be good to notch out the harmonics. They don't matter since our ALS feedback will have notches at those frequencies.

I wouldn't bother...

  5947   Fri Nov 18 15:35:18 2011 kiwamuUpdateIOORF generation box : power switch malfunction

Jenne gave me a spare LED power switch .

I will replace the broken one on Monday.

By the way here is a picture album of the RF generation box which I took last night.

            

Quote from #5942

 The power switch button of the RF generation box is not properly working

  5949   Fri Nov 18 15:45:11 2011 MirkoUpdateIOOMode cleaner noise projection

[Rana, Den, Mirko]

Updated the MC noise projection to include the longitudinal motion of the MC mirrors.

WholeMCNoiseProjection.png

=> Lots of OSEM - local dampling noise!

Consistent with static wiener filter showing only benefits in the 1 - 4Hz region.

Attachment 2: WholeMCNoiseProjection.fig
  5950   Fri Nov 18 16:37:14 2011 steveUpdateVACpreparing for ac power interruption

The vacuum is ready for no AC power for 1 hr on Sunday morning at 10am

 

I did the follwing:

 

Closed V1,  stopped the rotation of TP-1 maglev, waited till it reached 0 Hz_ rpm  and  turned it's controller off.

Closed V4 and stopped TP-2 rotating

Closed all annuloses and VA6

Closed VM1 and opened VM3 This means the RGA is being pumped by TP3. RGA is running in background mode. V5 will close instantly as the AC will be turned off.

VAC STATUS:  IFO envelope and annulosses are not pumped.  P1  pressure will reach 5-6 mTorr by Sunday morning.

                                 The PSL output shutter will be closed by the interlock at 3 mTorr

 

Kiwamu will turn off Piezo Jena PZT power supplies and computers Saturday.

I will be here around 1pm Sunday to star pumping. I will need EPICs MEDM running by than.

Attachment 1: planednopower.png
planednopower.png
  5951   Fri Nov 18 19:07:07 2011 JenneUpdateRF SystemFoam house on EOM

[Jenne, Zach, Frank]

Frank helped Zach and I cable up at PT-100 RTD, and make sure it worked with the Newport Model 6000 Laser Diode Controller.  We're using this rather than the Newport 3040 Temperature Controller because Dmass says the output of that isn't working.  So we're using just the temp control part of the Laser Diode controller.

The back of the controller has a 15-pin D-sub, with the following useful connections.  All others were left Not Connected. 

1 & 2 (same) - Pin 2 is one side of TEC output (we have it connected to one side of a resistive heater)

3 & 4 (same) - Pin 4 is the other side of the TEC output (connected to the other side of the resistive heater)

7 - connected to one side of PT-100 temp sensor

8 - connected to other side of PT-100 temp sensor

I used aluminum tape to attach the sensor and heater to the 40m's EOM, and we plugged in the controller.  It seems to be kind of working.  Zach figured out the GPIB output stuff, so we can talk to it remotely.

 

  5952   Fri Nov 18 19:57:19 2011 MirkoUpdateIOOMode cleaner noise projection

 

Some more info on this:
 

f > 1 Hz:

At these frequencies the pendulum should be quieter than the stacks. By quite a bit actually since there is the stack resonance at a couple Hz. 'Glueing' them together via the local control is not wise. We put an elliptic LP ( 2.5Hz, 4th order 6dB) into the C1:SUS-MC?_SUSPOS pathes and MC-F got better above 1Hz

MC_ELP.png

Added an extra LP @ 10 Hz afterwards. Doesn't make a visible difference.

f < 1 Hz:

Now here is more stuff to consider.

1. The OSEMs glue the MC mirrors to the stacks
2. The pendulum TF should be 1
3. It shouldn't matter if the OSEMs do or do not act on the mirror at these frequencies, assuming they don't add extra noise.
4. Page http://nodus.ligo.caltech.edu:8080/40m/5547 seems to indicate OSEM sensor noise is so low it can be neglected.

Reduced OSEM gain below 1Hz:

If we reduce the gain in the OSEMs by adding additional HP filters ( cheby2, HP 0.3Hz, 6dB 4th order ) the happens:

1. MC length gets a bit more noisy at low frequencies - should be looked into some more
2. Coherence between the GUR1 seismometer and MC length goes up between 1E-2 and 1E-1 Hz:

( Ref is with low OSEM gain )

WithAndWithoutHPs.pdf

Possible explanation:

The stacks might be more correlatedly moving together than the pendulums. This would be not so nice for OAF test, but really fine for actually using the MC.
Todo: Measure the OSEM to seismometer coherences with high and low OSEM gains.

For reference the seismometer coherence with one another:
SeismCoh.pdf

 

 

  5953   Fri Nov 18 23:44:33 2011 ranaUpdateIOOMode cleaner noise projection

Could use some more detail on how this measurement was done. It looks like you used the SUSPOS signal with the mirror moving, however, this is not what we want. Of course, the SUSPOS with the mirror moving will always show the mirror motion because the OSEMs are motion sensors.

Instead, what we want is to project how the actual OSEM noise in the presence of no signal shows up as MC length. For that we should use the old traces of the OSEM noise with no magnets and then inject that spectrum of noise into the SUSPOS filter bank with all the loops running. We can then use this TF to estimate the projection of OSEM noise into the MC length.

As far as improving the damping filter, the 2.5 LP is not so hot since it doesn't help at low frequencies. Instead, one can compute the optimal filter for the SUSPOS feedback given the correct cost function. To first order this turns out to be the usual velocity damping filter but with a resonant gain at the pendulum resonance. This allows us to maintain the same gain at the pendulum mode but ~3x lower gain at other frequencies.

In the past, we had some issues with this due to finite cross-coupling with the angular loops. It would be interesting to see if we can use the optimal damping feedback now that the SUS DOFs have been diagonalized with the new procedure.

  5954   Sat Nov 19 00:09:02 2011 ZachUpdateRF SystemFoam house on EOM

Quote:

I used aluminum tape to attach the sensor and heater to the 40m's EOM, and we plugged in the controller.  It seems to be kind of working.  Zach figured out the GPIB output stuff, so we can talk to it remotely. 

I stole the Prologix wireless GPIB interface from the SR785 that's down the Y-Arm temporarily. The address is 192.168.113.108. (Incidentally, I think some network settings have been changed since the GPIB stuff was initially configured. All the Prologix boxes have 131.215.X.X written on them, while they are only accessible via the 192.168.X.X addresses. Also, the 40MARS wireless router is only accessible from Martian computers at 192.168.113.226---not 131.215.113.226).

In any case, the Newport 6000 is controllable via telnet. I went through the remote RTD calibration process in the manual, by measuring the exact RTD resistance with an ohmmeter and entering it in. Despite this, when the TEC output is turned on, the heating way overshoots the entered set temperature. This is probably because the controller parameters (gain, etc.) are not set right. We have left it off for the moment.

Here are a couple command examples:

1. Turning on the TEC output 

nodus:~>telnet 192.168.113.108 1234
Trying 192.168.113.108...
Connected to 192.168.113.108.
Escape character is '^]'.
TEC:OUT on
TEC:OUT
TEC:OUT?
++read eoi
1
 
2. Measuring the current temperature
 
TEC:T?
++read eoi
32.9837
 
3. Reading and then changing the set temperature
 
TEC:SET:T?
++read eoi
34.0000
TEC:T 35.0
TEC:SET:T?
++read eoi
35.0000
 
4. Figuring out that the temperature is unstable and then turning off the TEC (this is important)
 
TEC:T?
++read eoi
36.2501
TEC:OUT off
TEC:OUT?
++read eoi
0
 
(The "++read eoi" lines are the commands you give the Prologix to read the controlled device output.)
 
As I understand, Frank has some code that will pull data in realtime and put it into EPICS. This would be nice.
  5955   Sat Nov 19 00:34:36 2011 ZachUpdateRF Systemwhy the Newport 6000 isn't working

 I just figured out why the Newport 6000 isn't stabilizing the temperature. It is designed to drive a TEC, so that when the temperature is too high, it just applies a negative current. Of course, this doesn't work with a resistive heater; it just keeps heating it up more.

I'm not sure if Frank has actually used this with a restive heater before, but it doesn't appear that you can limit the low-current level or add an offset.

  5956   Sat Nov 19 00:47:24 2011 ZachUpdateGreen LockingY-Arm locked with PDH Box #17

I installed the newly modified PDH box #17 and locked the Y-Arm.

I wasn't able to bring the REFL level down to the 30% that Kiwamu claimed to get, despite readjusting the alignment---I got ~40-45%. I attained a UGF of ~8 kHz, lower than the 20 kHz that Kiwamu said he got with the temporary setup, probably because the PDH box just isn't as fast. Despite that, it looks like the error suppression is actually better than before...

Here is an error spectrum:

error_sig_m_11_18_11.png

I have to admit that this calibration is worthy of suspicion and should be done more rigorously. I simply used the measured UGF frequency and known servo TF and PZT actuator gain to estimate the optical response. I am pretty confident that it's accurate to within a factor of 3 or so.

  5957   Sat Nov 19 01:26:16 2011 DenUpdateIOOMode cleaner noise projection

Quote:

Instead, what we want is to project how the actual OSEM noise in the presence of no signal shows up as MC length. For that we should use the old traces of the OSEM noise with no magnets and then inject that spectrum of noise into the SUSPOS filter bank with all the loops running. We can then use this TF to estimate the projection of OSEM noise into the MC length.

That's right. The easier problem arises if we consider one of  MC mirrors. The coherence between OSEM sensors and GUR1_X in free moving regime is equal to 0.9 at frequencies 0.1 - 1 Hz. But with local dumping coherence is 0.6. We have

Mirror -> Sensor -> Satellite Module -> Whitening -> ADC -> Computer -> DAC -> Dewhitening -> Satellite Module -> Actuator -> Mirror

Somewhere we produce noise that kills part of coherence. We can use this method with the injection of spectrum of noise into the SUSPOS filter bank only for one mirror and see how the coherence between OSEM sensor and GUR1_X will change. If the change is small, we deal with something else. It the coherence will change from 0.6 to ~0.4, than we have big OSEM noise.

It might be also the problem that the amplitude of COIL_OUT signal is ~25. If it is in counts we may have noise from DAC. 

  5958   Sat Nov 19 06:04:43 2011 SureshUpdateIOOMC_WFS Servo: The MC2_TRANS_PIT and YAW loops switched ON

Without adding significant amounts of noise to other WFS loops I have engaged the MC2_TRANS_PIT and YAW loops. 

After several attempts to measure the system response and computing the output matrix, none of which gave any useful results, I gave up on that and decided to find three orthogonal actuation vectors which enable us to close the loops.  So using the last good output matrix (below left side)  as a template, I rounded it off to the nearest set of orthogonal vectors and arrived at the following matrix (right side):

WFS_OUTMx_Lastgood.png        WFS_OUTMATRIX_20111118.png

 

I also decided that WFS1 and 2 need not drive MC2.  This is just to decouple the loops and minimise cross-talk.   This (albeit heuristic)  matrix seems to work pretty well and the real matrix is probably quite close to it.

I show below the suppressed error signals after tweaking the gains a bit.   The blue line is with no WFS, the green one with only WFS1 and 2 loops on, while the red is with all loops turned on.  The WFS1Yaw and MC2_Trans_pit loops might benefit from a more careful study to determine a better output matrix.

WFS_err_MC2T_on_OMx5_20111118.png

  5959   Sat Nov 19 10:41:30 2011 ranaUpdateIOOMC_WFS Servo: The MC2_TRANS_PIT and YAW loops switched ON

I'm quite sure that this is not good: since MC2 can produce a signal in WFS1 and WFS2, it cannot be removed in this way from the actuation without introducing a significant cross-coupling between the MC_TRANS and WFS loops.

Really need loop TFs measured and compared with the model.

The WFS noise model will also show that we need to have a much lower UGF in the MCT loop since that sensor is just a DC QPD: it can never have as good of a sensing noise as a good WFS. In the current case with no Whitening, this is even more so.

  5960   Sat Nov 19 12:57:55 2011 MirkoUpdateIOOMode cleaner noise projection

Quote:

Could use some more detail on how this measurement was done. It looks like you used the SUSPOS signal with the mirror moving, however, this is not what we want. Of course, the SUSPOS with the mirror moving will always show the mirror motion because the OSEMs are motion sensors.

Instead, what we want is to project how the actual OSEM noise in the presence of no signal shows up as MC length. For that we should use the old traces of the OSEM noise with no magnets and then inject that spectrum of noise into the SUSPOS filter bank with all the loops running. We can then use this TF to estimate the projection of OSEM noise into the MC length.

As far as improving the damping filter, the 2.5 LP is not so hot since it doesn't help at low frequencies. Instead, one can compute the optimal filter for the SUSPOS feedback given the correct cost function. To first order this turns out to be the usual velocity damping filter but with a resonant gain at the pendulum resonance. This allows us to maintain the same gain at the pendulum mode but ~3x lower gain at other frequencies.

In the past, we had some issues with this due to finite cross-coupling with the angular loops. It would be interesting to see if we can use the optimal damping feedback now that the SUS DOFs have been diagonalized with the new procedure.

 The measurement was done with the MC in lock and the OSEMS active.

1. I injected noise into MC1-3 SUSPOS_EXC at a level that domiated the SUSPOS output.
2. Then I calculated the coupling coefficients of the SUSPOS outputs to MC_F during the time the noise is injected.
3. Without noise injection I projected the SUSPOS outputs to MC_F by multiplying the coupling coefficients with the SUSPOS outputs.

All on 11-11-18. White noise inj. from 0.1Hz to 20Hz. Duration 4mins each.

DOF      Amplitude(counts)     Time(UTC)
MC1      200                           22:08
MC2      25                             22:25
MC3      25                             22:50

Some thoughts on this, bare with me:

As you say this does not show the dark / bright noise of the OSEMs. It shows the influence of the OSEMS output onto MC_F in normal operation of the MC. I would have expected that to be very low everywhere except at the pendulum resonance. Reason for that not to be true could either be the OSEMs having considerable gain off of the resonance, or noise intrinsic to the OSEMs knocking the mirrors around. Since we know the OSEM signal to MC_F TF we only need to compare the OSEM signal to OSEM noise to see the noise contribution to MC_F. We know from http://nodus.ligo.caltech.edu:8080/40m/5547 that the OSEM sensor bright noise is considerably below the OSEM signal above 0.1Hz in actual operation. We checked that the MC OSEM signals are above the noise in the reference above 0.1Hz by a factor 3-10.

We actually measured the cost function with the noise projection (valid to 10Hz). It's just the coupling coefficient, right?

CouplingMClengthsToMCF.pdf

 

Attachment 2: NpModeCleaner.pdf
NpModeCleaner.pdf NpModeCleaner.pdf NpModeCleaner.pdf NpModeCleaner.pdf NpModeCleaner.pdf NpModeCleaner.pdf NpModeCleaner.pdf NpModeCleaner.pdf
  5961   Sat Nov 19 15:58:04 2011 MirkoUpdateIOOSome more looks into OSEM noise

[Den, Mirko]

We looked some more into the the OSEM signals and their coherence to the seismometer signals.

We were able to verify that the coherence OSEM sensor <-> seismometer signal goes down with increasing the OSEM gain. This seems to indicate that the OSEM FB add noise to the distance mirror <-> frame. We injected some noise into the OSEMs to see how the coherence behaves.

MC2 SUSPOS, 0.1Hz - 0.8Hz, 3mins each

Inj. amplitude   Time(UTC) Note

-                     21:35          Free swinging
-                     21:42          Big LF OSEM gain
-                     21:48          Small LF OSEM gain
150                     21:56          -"-
300                     22:00          -"-
900                     22:05          -"-

Free swinging:

FreeSwinging.png

High OSEM gain:


LocalDampingOn.pdf

Low OSEM gain:

LowOsemGain.pdf

LowOsemGainInj150.pdf

Low_LF_OSEM_Gain_Inj300.fig

LowOsemGainInj900.pdf

 

We left the filters that lower the OSEM gain below 0.3Hz on.

Attachment 2: High_Osem_Gain.pdf
High_Osem_Gain.pdf
Attachment 4: Low_LF_OSEM_Gain.fig
  5962   Sun Nov 20 13:51:54 2011 steveUpdateVACvacuum is back up after ac interruption

State condition: Vac Normal,          CC1 ~8e-6 Torr

The IFO pressure peaked at  8.3 mTorr after 2days of not pumping.

Attachment 1: notpumping.png
notpumping.png
  5963   Sun Nov 20 14:48:55 2011 kiwamuUpdateGeneralrecovery from the power shutdown

Recovery from the power shutdown

 - Turned on the raid disk of linux1.

 - Woke linux1 up. No fsck this time.

 - Woke up all the lab machines.

 - Turned on all the electronics racks' AC powers

 - Woke up fb and then front end machine (the raid for fb had been already up as I turned on the AC powers)

 - Turned on all the electronics racks' DC powers (Sorensens, Kepcos, and etc.)

 - Turned on the Marcnois which is driving the RF generation box.

 - Woke up all the lasers (PSL and End lasers)

 - Some burtrestoring (c1ioo, c1sus, c1susaux, c1msc, c1psl, c1iool0, c1auxey, c1auxex, c1oaf, c1pem)

 - Ran autolockMC scripts on op340m => After relocking of PMC a lock of MC was acquired immediately.

 - Turned on the PZT HV drivers.

 

Some issues

 - One of the Sorensens in 1X8 rack is showing the current limit sign. This is exactly the same situation as we saw before (#5592).

       Currently it's off. It needs an investigation to find who is drawing such a large amount of current.

 - C1SCX is not properly running. Rebooting the machine didn't help. This needs to be fixed.

       The symptom is : (1) all the values are frozen in the screens. (2) the c1scx status screens shows NO SYNC sign. (3) however the timing board looks blinking happily.

 - One of the VME rack on 1X3 is not showing the +/-15V green LED lights.

   This is the one on very upper side of the rack, which contains the old c1lsc machine and c1iscaux2. If we are still using c1iscaux2, it needs to be fixed.

  5964   Sun Nov 20 15:11:09 2011 kiwamuUpdateIOORFAM monitoring test

DO NOT CHANGE THE IFO ALIGNMENT UNTIL TOMORROW MORNING OR FURTHER NOTICE.

Plus, MC has to be kept locked with the WFS.

 

An RFAM measurement is ongoing

 

 Since the Stochmon turned out to be tricky to calibrate the outputs, Koji and I decided to monitor the RFAMs using REFL11 and REFL55 RFPDs while the beam is single-bounced from PRM.
This is, of course, not a permanent RFAM monitor, but at least it gives us a long-term continuous RFAM information for the first time.
Before the measurement I ran the offset zeroing scripts, therefore any offsets from electronics must be tiny in the acquired REFL signals.
The measurement has begun from approximately 3:00 pm.
 
 Also I found C1LSC.ini file again became default (no channels had been acquired).
So I replaced it with an archived ini file and then restarted fb.
  5965   Sun Nov 20 15:33:37 2011 ranaUpdateGeneralrecovery from the power shutdown

 restarted Apache on Nodus for the SVN as per wiki instructions

ELOG V3.1.3-