40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 127 of 339  Not logged in ELOG logo
ID Date Authorup Type Category Subject
  8689   Fri Jun 7 21:33:39 2013 ManasaUpdatePSLPSL green to Y- BEAT PD blocked

To allow Annalisa to work on the Y-green alignment as I work with the X-green, the part of the PSL green beam that goes to the Y-green beat PD has been blocked with an iris.

  8694   Tue Jun 11 22:16:56 2013 ManasaSummaryGreen LockingALS for X arm

I discussed with Yuta about the ALS servo and phase tracker and found that there was a lot of information lying around from last year but there aren't any clear elogs on how to enable ALS and obtain IR resonance.

 

Guide to enabling the ALS servo and find IR resonance:

The steps will explain in detail how to ressurrect the ALS servo for green X-arm and find IR resonance using ALS. The medm screens are very confusing right now.

 

(i) Finding the beat note

1. Get the IR to flash in TEM00 for the arm and lock it by enabling LSC (Locking the arm to IR keeps the arm cavity mirrors stable so that you can scan the temperature of the X-end laser to find the beat note).

2. Steer the X-green into the arm cavity such that the arm cavity locks in TEM00 for green as well. At this point you should also have the X-green reaching the PSL table.

3. Align the PSL doubled green (PSL-green) and the X-green in near-field (at the camera) and far-field (letting the beams to propagate beyond the Green-TRX PD).

4. Check cabling of the RF beat PD.

5. Change the X-laser temperature by sweeping the offset (C1: ALS-SLOW_SERVO2_OFFSET) in steps of 10.

6. Find the beat note and tune the alignment at the beat PD to maximize the beatnote amplitude. Disable LSC for X arm.

 

(ii) The GREEN HORNET explained

'Input signal conditioning' block takes I and Q signals after the delay frequency discriminator (DFD) in the beat box and these signals pass through C1ALS_BEATX_FINE filter banks. The output signal then enters the phase rotation matrix of the phase tracker. The phase tracker gives 'PHASE_OUT' which is the error signal that is fed to the ETM servo filter module (DOF filters)  through the 'Input matrix' in the medm. 

An offset can also be fed to the phase tracker which will scan the beat frequency (used to find IR resonance).

 

(iii) Scripts

1. easyALS.py - This runs from 'ON plus' or 'ON minus' buttons in the C1ALS_COMPACT. 

The script clears history of 'fine_phase' filter module and increases gain of the servo in steps ('ON plus' for positive gain and 'ON minus' for negative gain).

2. findIRresonance.py - This runs from 'IRres' button in the C1ALS_COMPACT.

It adds offset to the phase tracker in steps which scans the beat frequency to find IR resonance.

P.S. Check the scripts before enabling the servo so that the right filter modules are being turned ON. Using the wrong set of filter modules can kick the ETM.

____________________________________________________________________________________________________________________________________________________

X arm ALS progress:

I found the beat note and got ALS to work reasonably for the Xarm without kicking the ETM. I did this by manually toggling buttons and changing gains. The scripts need editing.

To do:

Modify the scripts to work as we want them to.

The ALS medm is SSSOOOO confusing. It definitely needs to be fixed (remove all unwanted parts of the screen that existed 'pre-phase tracker').

Find IR resonance.

 
  8698   Thu Jun 13 00:35:23 2013 ManasaUpdateGreen LockingY arm locked with green but bad mode matching
> Hmmm.  You seem to be saying that more light is reflected than is injected. Is this a units problem? Or was some IR on the power meter during the 'reflected' measurement? 
> We should look at it with fresh eyes in the morning. 

Also, if you have been measuring the power of green refl at the rejection port of the green faraday, the polarization of the light entering the green faraday should be checked once again to make sure that you are measuring 
only the reflected power from the arm cavity.
  8703   Thu Jun 13 22:31:12 2013 ManasaSummaryGreen LockingX arm ALS

Stabilized ALS and beat frequency sweep realized.

Procedure:

1. Enable appropriate filter modules and set appropriate servo gains.

Servo module

Filters Gain
C1:ALS-BEATX_FINE_I   FM2 FM3 1.0
C1:ALS-BEATX_FINE_Q FM2 FM3 1.0
C1:ALS-BEATX_FINE_PHASE FM1   300.0
C1:ALS-BEATX_FINE_OFFSET - 1.0
C1:ALS-XARM FM4 FM5 -0.25
C1:ALS-ETMX - 1.0


2. Clear history of C1:ALS-BEATX_FINE_PHASE

3. Enable the servo loop. I had set limits on the servo loop and ramp time for gain switching so that I don't kick the ETMY hard.
Gains were decided such that the error signal C1:ALS-BEATX_FINE_PHASE_OUT was minimized.

4. Beat frequency sweep is realized by stepping up on C1:ALS-BEATX_FINE_OFFSET_OFFSET (from 0 to 2100 in this case).

Video1 shows the difference that can be seen at the RF spectrum analyzer when ALS is enabled.

Video2 shows the beat frequency sweep as seen on the spectrum analyzer.

I could not get 'getdata' to work as I wanted. So I have attached the error signal trend before and after the ALS servo loop is enabled.

Thank you Jenne for helping retrieve more sensible data!

More info:
The beat note is very strong and we can clearly see its harmonics as well. Attached is the picture showing the several harmonics.
________________________________
Peak frequency(MHz)    Power(dBm)
________________________________
 47                                    -2.77
 93.5                                -27.56
 139                                 -32.75
 185.4                              -45.64
 231.9                              -57.10
 278.4                              -59.42
________________________________

To do:
1. Obtain IR resonance.
2. Check the digital anti-whitening filter after the beatbox.
3. The effect of the harmonics should be figured out.
4. Write scripts to enable ALS and findIRresonance.

Attachment 1: IMG_0659.JPG
IMG_0659.JPG
Attachment 2: ALS_stabilized_13June2013.png
ALS_stabilized_13June2013.png
  8709   Fri Jun 14 17:15:45 2013 ManasaUpdateGreen Lockingc1als model edited

I have edited the daq channels in c1als model.

Added: DQ channels for the error signal (phase tracker output)
Removed: DQ channels that existed for the beat_coarse signals

Installed and restarted the model on c1ioo.
Frame builder restarted.
Changes were committed to the svn. 

  8714   Mon Jun 17 23:12:19 2013 ManasaUpdateGreen Lockingcan't get IR to resonate

What I did: 

1. Followed the same procedure to enable ALS (http://nodus.ligo.caltech.edu:8080/40m/8703)
2. Enabling ALS servo stabilized the arm fluctuation and the beat frequency.
3. Beat frequency sweep was done (with ALS servo enabled) by changing offset C1:ALS-BEATX_FINE_OFFSET_OFFSET in steps.

Discussion:

I swept the beat frequency through ~10MHz and could not find IR resonance. But TRY TRX varied from 0 - 0.9 counts as the beat frequency sweep was done. I suspected that the offset steps might have been too big and I had jumped over the IR resonance. So, I repeated the offset sweep again in smaller steps (offset steps 0.1) and it did not help. 
I also played with the gain of the ALS servo to stabilize the loop and set the gain to the maximum (smallest error signal oscillating around '0') and did the frequency sweep. The arm cavity would still not resonate through the sweep but only evolve from no flashes to strong flashes for IR (0 - 0.9 counts).
  8718   Tue Jun 18 18:24:07 2013 ManasaUpdateIOOMC WFS turned OFF

[Jenne, Jamie, Manasa]

Jamie was working on the MC guardian today (I think he will elog about this soon).

After this, I received the MC locked in TEM00 with MC_REFL at ~2.5 counts from Jamie. Usually the WFS would do their job in this case to bring MC to a good locking condition and since this did not happen, I figured out that something was wrong with the MC_WFS.

What we did:

1. The WFS were turned off. 

2. As a first step, we wanted to run the WFS_OFFSET script (Koji's elog) which requires MC to be locked with MC_REFL<0.5 and spot positions centered. The autolocker was disabled and MC locked manually to MC_REFL<0.5. 

3. While running the WFS_OFFSETS script, Jamie pointed out that the inputs to the WFS servo had been turned off. After the WFS_OFFSET script finished running we turned ON the WFS inputs. 

4. Following this, the MC was relocked manually and MC spot positions were measured (all spot positions were decentered by < 2 mm). 

5. We ran the WFS_OFFSET script again and turned the WFS back ON. But this would still kick the MC out of lock. 
 

Status: MC is locked with WFS turned OFF. Jamie will be looking through what changes he had made earlier today to fix this problem. 

 

  8721   Wed Jun 19 01:45:49 2013 ManasaUpdateGreen LockingBeat frequency sweep for 3FSR

Measurements:

1. Calibrating offset :

I measured the shift in the beat frequency while scanning through the offset. Offset stepped by 50 resulted in 1MHz shift of the beat frequency.
 

2. Anti-whitening filter for beatbox output:

I made an anti-whitening filter for the beatbox output in the ALS_BEATX_FINE_I module by inverting the whitening filters that Jamie had installed in the beatbox earlier (elog).  I have kept the old anti-whitening filter in the module as well for the time-being because the new anti-whitening filter was not as good as the old one in stabilizing the servo (large error signals and unstable ALS).

 

3. Beat frequency scan for 3FSR:

With ALS loop enabled, I did an offset sweep corresponding to 3FSR (FSR = c/2L = 3.7MHz). The loop doesn't seem to be stable enough to reduce the arm fluctuation to get a resonance for IR. Time series of scan is shown below:

findIR.png

4. No-loop and in-loop spectrum:

I measured the spectrum of the error signal (C1:ALS-BEATX_FINE_I_IN1) with ALS loop enabled and disabled. To suppress the peaks at 3.2Hz and 16.5Hz, I turned ON the corresponding filters. I have recorded the error signal spectrum with only 16.5Hz res gain filter turned ON. Turning ON res gain 3.2Hz filter kicked ETM. 
Spectrum of error signal shown below:

findIR1.png

To resolve:

1. What is wrong with the new anti-whiteing filter?

2. Why would the res gain filters kick ETM and show no noise suppression?

  8738   Mon Jun 24 16:06:17 2013 ManasaSummaryGreen LockingALS model

 I am working on the basic ALS servo model. The simulink model for the same is attached. The loop is not yet complete (I'm still debugging it) ; but this is just an update of where I am right now.

Attached is the simulink and matlab file. 

 

 

 

 

 

Attachment 1: elog.zip
  8754   Wed Jun 26 11:32:11 2013 ManasaUpdateGreen Lockingc1als model edited

I have added more DAQ channels to the c1als model. Installed and restarted the model on c1ioo. Frame builder restarted.

DAQ channels added:
C1:ALS-XARM_IN1
C1:ALS-YARM_IN1
C1:ALS-OFFSETTER1_OUT
C1:ALS-OFFSETTER2_OUT

  8760   Wed Jun 26 23:32:15 2013 ManasaUpdateGreen Lockingc1als model edited

I have modified the ALS model to now include PHASE_OUT calibration for both X and Y. MEDM screen has not been edited to include these yet.

c1als_mdl.png

  9055   Thu Aug 22 21:16:47 2013 ManasaUpdateGreen LockingGTRY normalized

The Y arm green transmission has been measuring in counts all along. I modified the gain in the ALS-TRY filter module to normalise the transmission.

Transmission has been normalised with GTRY = 1 corresponding to 600 counts. 

  9091   Fri Aug 30 11:00:46 2013 ManasaUpdateGeneralSeries of earthquakes

There has been a series of earthquakes since the big 7.0 in Alaska this morning.

None of the watchdogs were tripped when I came in. But I could not retrieve any info about the suspensions from fast channels because c1sus was not talking to the fb and that required an mxstream restart to fix it.

MC is trying to lock itself, but the seismic doesn't seem to get quiet. So MC is not all that happy.

 Screenshot-Earthquakes_-_Mozilla_Firefox.png

SUSnSEIS.png

  9157   Tue Sep 24 22:19:57 2013 ManasaUpdateGeneralFPMI locked

 [Masayuki, Manasa]

We locked FPMI and measured the FPMI noise (power spectrum of error signal - MICH_IN1) which will be calibrated.

The arms were locked using POX11 and POY11. The sign of MICH gain was changed to lock FPMI (from -30 to +30). 

  9200   Fri Oct 4 01:09:33 2013 ManasaUpdateGreen LockingFrequency counter for ALS

I checked the BK precision 1856D manual. I found that although this frequency counter can measure upto 3.5GHz, it has 2 separate input channels to measure two range of frequencies.

One input to measure between 0.1Hz to 100 MHz and the other to measure between 80MHz to 3.5GHz. Our beat frequency desirable range is <100MHz for stable ALS. Also, the beat PD response falls off beyond ~150MHz . Should we be happy with this frequency counter and use it in the 0.1Hz-100MHz range or look for one with a better measuring range?

P.S. Right now we are using the spectrum analyzer in the control room set to frequency range from 10MHz - 140 MHz for beat note search. 

  9228   Wed Oct 9 22:58:34 2013 ManasaUpdateGreen LockingALS stabilization

After Jenne and Masayuki told that they were not able to stabilize the ALS for either arms yesterday, I looked into things with the ALS servo.

I had trouble initially trying to even stabilize the loop for a few minutes. So I measured the OLTF of the phase tracker loop and the ALS X arm servo. I changed phase tracker gain to 125 and that rendered UGF of 2KHz and phase margin of 45 degrees for the phase tracker loop.

The ALS servo gain was set such that UGF was 125Hz and phase margin 38 degrees (attached is the transfer function measurement for the servo).

I could stabilize the arm to ~500 Hz/rtHz (rms), which is twice that of what we had while we did the (PRMI+1arm ALS).

But ALS was still not stable long enough with the higher rms to even allow a cavity scan to find IR resonance. I suspect the problem to now lie with the PDH loop. We should be looking to stabilize the PDH for green if we need a stable ALS.

Attachment 1: ALS_XARM_OLTF.pdf
ALS_XARM_OLTF.pdf ALS_XARM_OLTF.pdf ALS_XARM_OLTF.pdf
  9593   Mon Feb 3 23:31:33 2014 ManasaUpdateGeneralAlignment update / Y arm locked

[EricQ, Manasa, Koji]

We measured the spot positions on the MC mirrors and redid the MC alignment by only touching the MC mirror sliders. Now all the MC spots are <1mm away from the center.

We opened the ITMY and ETMY chambers to align the green to the arm. The green was already centered on the ITMY. We went back and forth to recenter the green on the ETMY and ITMY (This was done by moving the test masses in pitch and yaw only without touching the green pointing) until we saw green flashes in higher order modes. At this point we found the IR was also centered on the ETMY and a little low in pitch on ITMY. But we could see IR flashes on the ITMYF camera. We put back the light doors and did the rest of the alignment using the pitch and yaw sliders.

When the flashes were as high as 0.05, we started seeing small lock stretches. Playing around with the gain and tweaking the alignment, we could lock the Y arm in TEM00 for IR and also run the ASS. The green also locked to the arm in 00 mode at this point. We aligned the BS to get a good AS view on the camera. ITMX was tweaked to get good michelson.

  9755   Wed Mar 26 22:22:43 2014 ManasaUpdateGeneralRecovery

The following that went unnoticed from yesterday were recovered today:

1. ETMX and ETMY 'misalign' scripts weren't running. Troubleshooting showed slow machines c1auxex and c1auxey weren't responding. The machines were reset.

2. PRM oplev gains were zero. Gain values were set looking back at the burt files.

3. X end PZT power supplies were turned ON and set to 100V.

4. X end doubler temperature was reset to the last optimal value on elog (36.35 deg).

 

Some hitches that should be looked into:

1. Check: ASS for X arm seems not quite doing its job. ETMX has to be moved using sliders to obtain maximum TRX and the arm alignment was seen to be drifting.

2. Check: Status of other slow machines and burt restore whichever needs one.

  10051   Tue Jun 17 17:14:14 2014 ManasaUpdateLSCIFO alignment recovery

 1. Recovered MC alignment and locked it manually after the ottavia cron failed to help.

2. Measured the MC spots and could not get the MC spots better looking than this.

spot positions in mm (MC1,2,3 pit MC1,2,3 yaw):
[1.6609930611758554, -1.4655939584833202, 1.3133188677545831, -1.9483764375494121, -1.6539541350121174, -0.8862744551298497]

3. Realigned the beams to the MC WFS and enabled WFS servo.

MC Trans SUM is ~17000 counts and MC REFL is ~0.5 counts.

To-do list

MC spots

MC WFS

IOO QPDS center

BBPD char

Recover REFL 33

MC REFL

MC autolocker cron

  10054   Wed Jun 18 11:28:19 2014 ManasaUpdateComputer Scripts / Programsautolocker confusion

Quote:

I renamed the Autolocker and described it in the elog from this weekend. To run it, you have to run it from the scripts/MC/ directory (as always). I restarted the autolocker on Ottavia with nohup.

> nohup ./AutoLockMC.csh &

To figure out how to get cron to run it, we will have to debug the difference between linux and solaris pgrep, so that's in progress.

I am NOT convinced that the autolocker script is running or doing anything. The MC was unlocked as of this morning and the autolocker wasn't doing anything to any of the MC servo buttons and sliders. The autolocker control shows that it is 'alive' but it still blinks 'MC down' even after I locked the MC manually. I am suspecting that this might have to do something with the caget and caput in autolock script itself rather than the CRON. I will look into this problem later today.

Moral of the story: The autolocker is not doing its job.

  10059   Wed Jun 18 16:44:55 2014 ManasaUpdateElectronicsBBPD installed for BEATX detection

This BBPD is the spare that we pulled out and is installed for ALSX-PSL beat note detection.

  10072   Thu Jun 19 14:41:00 2014 ManasaUpdatePSLISS disabled

I would like to measure the switching time of the AOM. So I have disconnected the modulation input to the AOM that comes from the ISS. I have also turned OFF the SR560's and the AWG that belong to ISS. 

Pics and cable connections of the state in which the ISS setup was left at, will be updated soon.

  10091   Tue Jun 24 13:02:54 2014 ManasaUpdatePSLRingdown PD installed

Quote:

I would like to measure the switching time of the AOM. So I have disconnected the modulation input to the AOM that comes from the ISS. I have also turned OFF the SR560's and the AWG that belong to ISS. 

Pics and cable connections of the state in which the ISS setup was left at, will be updated soon.

I installed a fast PDA10CF along the path of a leaking beam from one of the steering mirrors that direct the main beam to the PMC. This beam was dumped to a razor blade. I removed the razor blade and installed a Y1 to steer this beam through a lens on the PD.

Pics of the layout post-installation will be updated.

Also, I tested the AOM by giving it 0-1V modulation input from the AWG. This has been disconnected after the test. So everything should be as it was pre-testing.

Attachment 1: PSL_ringdown.png
PSL_ringdown.png
  10115   Mon Jun 30 22:40:21 2014 ManasaUpdatePSLAOM ringdown

Quote:

Quote:

I would like to measure the switching time of the AOM. So I have disconnected the modulation input to the AOM that comes from the ISS. I have also turned OFF the SR560's and the AWG that belong to ISS. 

Pics and cable connections of the state in which the ISS setup was left at, will be updated soon.

I installed a fast PDA10CF along the path of a leaking beam from one of the steering mirrors that direct the main beam to the PMC. This beam was dumped to a razor blade. I removed the razor blade and installed a Y1 to steer this beam through a lens on the PD.

Pics of the layout post-installation will be updated.

Also, I tested the AOM by giving it 0-1V modulation input from the AWG. This has been disconnected after the test. So everything should be as it was pre-testing.

Edit/manasa/ Data has not been fit correctly in here. A proper fit will follow this elog.

Proper fits and numbers are here :elog

Earlier last week I had tried to measure the AOM ringdown and concluded I could not make one.

I was proved wrong and I was able to make a measurement. I am still not sure why I was not able to make the measurement earlier with the very same settings and configuration.

What I did:

I gave the AOM a 0-1V modulation input using the signal generator (50 ohm feedthrough bnc was used to impedance match the AOM driver's modulation input). For the measurement here I used a 1Hz square wave. I used a 300MHz oscilloscope to look at the falling edge of the ringdown PD output installed.

I recorded a few ringdown samples. To get a quick number, I fit one such sample to find the AOM switching time as 1.48us (Plot attached). 

Attachment 1: AOM_ringSample1.pdf
AOM_ringSample1.pdf
  10180   Thu Jul 10 19:37:54 2014 ManasaUpdateGeneralPM980 fiber tested OK

[Harry, Manasa]

This is the update from yesterday that Harry missed to elog.

We pulled out the first spool of the PM980 fiber yesterday and checked it using the illuminator at the SP table. Harry will be using this for all his tests and characterisation of the fiber.

  10220   Wed Jul 16 21:23:35 2014 ManasaUpdatePSLPSL Innolight controller fan is dying

[Koji, Manasa]

The air flow from the dying fan was kinda weak and we decided to give a help with an external fan.

Koji brought a fan taken from a junk found at EE shop in W.Bridge.
The fan has been tied to the cage of the existing fan using cable ties to provide air circulation.
So even if the existing one dies anytime, we still don't super-heat anything.
The power supply for the fan rests next to the controller. 

The air from the fan ventilation was hot, and now with the additional fan this hot air is actually sucked
out with stronger flow. So this is relieving for now.

Attachment 1: IMG_1659.JPG
IMG_1659.JPG
Attachment 2: IMG_1658.JPG
IMG_1658.JPG
  10233   Thu Jul 17 21:01:28 2014 ManasaUpdateGeneral1X2 Rack Changes

Quote:

 Purpose

 

Steve and I moved some things around in the 1X2 rack in order to make room (roughly 6") for the electronics box that will contain rf frequency counters, ADC, and Raspberry Pi's for use in the Frequency Offset Locking apparatus

Picture

1X2Changes.png

Occurrences

First, we killed power by removing the fuse that the boxes we were moving were running through.

Then, we moved the boxes. I dropped//lost a washer. It didn't seem to cause any problems, so no further attempts to locate it were made.

The fuse was reinstalled, and everything was reconnected.

Moving Forward

We are now working on putting together the electronics box, which will contain ADC, and raspberry pi's. The frequency counters will be mounted on the front of the box.

Once complete, it will be installed for use in FOL.

Additional comments:

This was done based on the earlier proposed setup plan for the frequency counters that will be used to measure the beat note frequencies [Akhil's elog]

I switched off the power supply to the green PDs so that we don't cause any damage while moving the amplifier panel for the beat signals and beatbox. 

  10487   Wed Sep 10 10:49:39 2014 ManasaUpdateLSCY arm green + PSL green mode overlap

Quote:

Manasa, can you please estimate what kind of mode matching we have on the PSL table between the arm greens and the PSL green?  We *do not* want to touch any optics at this point.  Just stick in a power meter to see how much power we're getting from each beam, and then think about the peak height we see, and what that might tell us about our mode overlap.  If we determine it is total crap, we can think about measuring the beams that go either toward the camera, or the DC PDs, since neither of those paths require careful alignment, and they are already picked off from the main beatnote path.  But first, what is our current efficiency?  Yarm is first, then Xarm, since Yarm seems worse (peak height is larger for non-00 modes!)

Estimate loss along the Y arm beat path:

1. Measured the beam powers (before the beam combiner): 
Y Arm green = 35 uW
Y PSL green = 90 uW

==> Pbeat ~ 2 * sqrt (35 uW * 90 uW) ~ 112 uW

2. Expected power of RF signal
Assuming the PD to have transimpedance ~ 2kV/A and responsivity ~ 0.3A/W, 
the expected power of the RF signal = (Pbeat * Transimpledance* Responsivity)^2 / (2 * 50ohm) ~ 45uW = -13.5 dBm

3. Measured power of Y arm beat signal

Turned OFF the beat PDs and rerouted the RF cables such that the spectrum analyzer was reading the RF signal from the Y beat PD itself (without any amplifiers or the beat box itself in the path).  
Turned ON the beat PDs and the Y arm beat signal power on the spectrum analyzer measured -58dBm
Even if we consider for losses along the length of the cables, we are still at a very bad state. 

4. Bad mode matching??
I don't think mode matching is our main problem here.
Toggling the shutter several times, even with the non-00 modes, the maximum beat power we can see is -50dBm which is still very far from the actual expected value.

  7690   Thu Nov 8 20:54:08 2012 Manasa, AyakaUpdateAlignmentReconfirming on IPPOS, IPANG and oplevs centering

Quote:

" We found that IPANG was not on its photodiode, but determined that it was centered on all of the in-vac mirrors, and that it was just a little bit of steering on the ETMY end out-of-vac table that needed to be done."

Manasa took photos of all test mass chambers and the BS chamber, so we can keep up-to-date CAD drawings. 

Oplevs and IPPOS/IPANG are being centered as I type.  Manasa and Ayaka are moving the lens in front of IPANG such that we have a slightly larger beam on the QPD.

 

The lens in front of IPANG on the out-of-vac table was moved to get a larger beam giving reasonable signals at the QPD.

IPPOS did not need much adjustment and was happy at the center of the QPD.

All oplevs but the ETMY were close to the center. I had to move the first steering mirror about half an inch on the out-of-vac table to catch the returning oplev beam from ETMY and direct it to the oplev PD.

* We have taken reasonable amount of in-vac pictures of ETM, ITM and BS chambers to update the CAD drawing.

 

  7810   Tue Dec 11 11:40:07 2012 Manasa, AyakaUpdatePSLPMC drift

[Manasa, Ayaka]

I found that MC got unstable this morning. This is caused by the drift of PMC. The transmission of PMC was going down and eventually unlocked PMC.

PMCdrift121211.pdf

We adjusted 'Slow Actuator Adjust' in FSS and now the PMC is locked with transmission of ~ 0.735.
Also we aligned the MC to be locked. Now it is locked with transmission of ~ 0.5 with WFS and MCL on.

  7675   Tue Nov 6 17:22:51 2012 Manasa, JamieUpdateAlignmentAlignment- POY and oplevs

Right now, Manasa, Jamie and Ayaka are doing some finishing touches work, checking that POY isn't clipping on OM2, the second steering mirror after the SRM, and they'll confirm that POX comes out of the chamber nicely, and that POP is also still coming out (by putting the green laser pointer back on that table, and making sure the green beam is co-aligned with the beam from PR2-PR3.  Also on the list is checking the vertex oplevs.  Steve and Manasa did some stuff with the ETM oplevs yesterday, but haven't had a chance to write about it yet.

We were trying to check POY alignment using the green laser in the reverse direction (outside vacuum to in-vac) . The green laser was installed along with a steering mirror to steer it into the ITMY chamber pointing at POY.

We found that the green laser did follow the path back into the chamber perfectly; it was clipping at the edge of POY. To align it to the center of POY (get a narrower angle of incidence at the ITMY), the green laser had to be steered in at a wider angle of incidence from the table. This is now being limited by the oplev steering optics on the table. We were not able to figure out the oplev path on the table perfectly; but we think we can find a way to move the oplev steering mirrors that are now restricting the POY alignment.

The oplev optics will be moved once we confirm with Jenne or Steve.

 

[Steve, Manasa]

We aligned the ETM oplevs yesterday. We confirmed that the oplev beam hit the ETMs. We checked for centering of the beam coming back at the oplev PDs and the QPDsums matched the values they followed before the vent.

Sadly, they have to be checked once again tomorrow because the alignment was messed up all over again yesterday.

  7196   Wed Aug 15 17:17:58 2012 Manasa, JanUpdateIOORingdown measurements

Finally ringdown at IMC conquered and oopsie that came out so clean!

The finesse of the cavity from the current ringdown measurement, F= 453, differs from the measurements made in the document dated 10/1/02 on dcc...not sure if things have changed since then.

While I thought that the bumps observed at the end of the ringdown might be because of the cavity trying to lock itself, Jan commented that they have always existed in these measurements and their source is not known yet.

Ringdown_815.jpg

  8282   Wed Mar 13 03:12:47 2013 Manasa, JenneUpdateLockingTWO arms TWO colors

[Jenne, Manasa]

2 colors 2 arms realized!

1. Spot centering:

We spot centered the IR in both arms.
- Use TT1 and TT2 to center in Y arm (I visually center the spots on the ITM and ETM and then use TTs iteratively)
- Use BS-ETM to center in X arm

Spot positions after centering
               X arm            Y arm
         itmx    etmx        itmy    etmy
pitch    -0.86    0.37        1.51    0.05
yaw      0.01    -0.1        0.08    0.10


2. TT1 drifting in pitch (Bistable)
During the arm alignment routine for spot centering, we observed that TRY dropped (from TRY = 0.9 until the arm lost lock) every 40minutes or so. The arm was relocked by moving TT1 in pitch. The (locking - unlocking due to drift - relocking) cycle was monitored and we observed that it was bistable i.e. if TT1 was moved up in pitch (0.2 on the slider) to relock for the first time ; the next time it lost lock, TT1 had to be moved down by nearly the same distance to relock the arm.
Moving TT2 or the testmasses did not help with relocking the arms; so TT1 seems to be the one causing all th trouble atleast for today.

3. ALS - green alignment

We then moved on to Ygreen.  We used the out of vac steering mirrors to center the beam on the 2 irises that are in place on the table, which was a good starting place.  After doing that, and tweaking a small amount to overlap the incident and reflected beams on the green steering mirrors, we saw some mode lock.  We adjusted the end table steering mirrors until the Ygreen locked on TEM00.  We then followed Rana's suggestion of locking the IR to keep the cavity rigid while we optimized the green transmission.  Yuta, while adjusting ITMY and ETMY (rather than the out of vac mirrors) had been able to achieve a green transmission for the Yarm of ~2700 counts using the GTRX DC PD that's on the table. We were only able to get ~2200, with brief flashes up to 2500.

After that, we moved on to the X arm.  Since there are no irises on the table, we used the shutter as a reference, and the ETM optic itself.  Jenne looked through the viewport at the back of the ETM, while Manasa steered mirrors such that we were on the center of the ETM and the shutter.  After some tweaking, we saw some higher order modes lock.  We had a very hard time getting TEM00 to stay locked for more than ~1 second, even if the IR beam was locked.  It looks like we need to translate the beam up in pitch.  The leakage of the locked cavity mode is not overlapped with the incident beam or the promptly reflected beam.  This indicates that we're pretty far from optimally aligned.  Manasa was able to get up to ~2000 counts using the same GTRX PD though (with the Ygreen shutter closed, to avoid confusion).  Tomorrow we will get the Xarm resonating green in the 00 mode.

We need to do a little cleanup on the PSL green setup.  Yuta installed a shutter (I forget which unused one he took, but it was already connected to the computers.), so we can use it to block the PSL green beam.  The idea here is to use the 4th port of the combining beam splitters that are just before each beat PD, and place a PD and camera for each arm.  We already have 2 PDs on the table connected to channels, and one camera, so we're almost there. Jenne will work on this tommorrow during the day, so that we can try to get some beat signals and do some handoffs in the evening.

  7694   Fri Nov 9 17:15:05 2012 Manasa, Steve, AyakaUpdateGeneralWe're closed! Pumping down monday morning

Quote:

After a brief look this morning, I called it and declared that we were ok to close up.  The access connector is almost all buttoned up, and both ETM doors are on.

Basically nothing moved since last night, which is good.  Jenne and I were a little bit worried about how the input pointing might have been effected by our moving of the green periscope in the MC chamber.

First thing this morning I went into the BS chamber to check out the alignment situation there.  I put the targets on the PRM and BS cages.  We were basically clear through the PRM aperture, and in retro-reflection.

The BS was not quite so clear.  There is a little bit of clipping through the exit aperture on the X arm side.  However, it didn't seem to me like it was enough to warrant retouching all the input alignment again, as that would have set us back another couple of days at least.

Both arm green beams are cleaning coming out, and are nicely overlapping with the IR beams at the BS (we even have a clean ~04 mode from the Y arm).  The AS and REFL spots look good.  IPANG and IPPOS are centered and haven't moved much since last night.  We're ready to go.

The rest of the vertex doors will go on after lunch.

Jamie and Steve got the ETM doors on this morning.

We got the other heavy doors including the ITMs, BS and the access connector in place.

If nobody raises any concerns in reply to this elog, Steve will assume it as a green signal and will start pumping down first thing Monday morning after the final check on the access connector bellow screws.

 

Steve! 

Ayaka and I got the ITMY and BS door closed at 45foot pounds just now. 

  8085   Fri Feb 15 01:41:02 2013 Manasa, YutaSummaryAlignmentIFO aligned and ready for PRMI locking

[Yuta, Manasa, Jenne, Jamie, Steve]

IFO aligned and ready for PRMI locking

Alignment procedure

0. Measured MC centering (off by 5mrad) before getting the doors off.

1. Got the TTs to 0.0 in pitch and yaw.

2. Using the MMTs, the beam was centered on the TTs.

3. TT1 was adjusted such that the incident beam was centered at PRM (with target).

4. TT2 was adjusted such that the beam passed through the center of BS (with target).

5. Centered the beam on PR2 by sliding it on the table.

6. Moved PR2 and tweaked TT2 to center the beam on ITMY and BS respectively.

7. Using TTs, we got the beam centered on ETMY while still checking the centering on ITMY.

8. ITMY was adjusted such that it retro-reflected at the BS.

9. ETMY was aligned to get a few bounces in the arm cavity.

10. Centered on ITMX by adjusting BS and then tweaked ITMX such that we retro-reflected at BS.

11. At this point we were able to see the MI fringes at the AS port.

12. Tweaked ITMX to obtain reflected MI fringes in front of MMT2.

13. By fine adjustments of the ITMs, we were able to get the reflected MI to go through the faraday  while still checking that we were retro-reflecting at the BS.

14. Tweaked the PRM, such that the PRM reflected beam which was already visible on the 'front face back face of faraday' camera went through the faraday and made fine adjustments to see it fringing with the reflected MI that was already aligned.

15. At this point we saw the REFL (flashing PRMI) coming out of vacuum unclipped and on the camera.

16. Started with alignment to get the AS beam out of vacuum. We tweaked OM1 and OM2 (steering mirrors in the ITMY chamber) to center the beams on OM4 and OM3 (steering mirrors in the BSC) respectively.

17. We then adjusted steering mirrors OM5 and OM6 (in the OMC chamber) such that the beam went unclipped out of vacuum.

18. Note that we took out the last steering mirror (on the AS table) in front of the AS camera, so that we can find the AS beam easily. This can be fixed after we pump down.

 

 

Tomorrow

  0. REFL still looks like an egg, but leave it .

  1. Align PRMI (no more in-vac!) .

  2. Align POP/REFL/AS cameras and PDs.

  3. Setup PRM/BS/ITMX/ITMY oplevs.

  4. Balance the coils on these mirrors.

  5. Lock PRMI.

  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

  5034   Mon Jul 25 23:43:20 2011 ManuelHowToElectronicsManual for 1201 Low Noise Preamplifier

I found the manual for the Low Noise Preamplifier Model 1201 at this link and I attached it.

The one we have in the lab (S/N 48332) miss the battery packs and miss also the remote programming options input/output. Its inside battery compartment is empty and I found 2 unscrewed screws with washers and nuts inside the preamplifier box. The battery cable are disconnected and they have 2 green tape labels (-) and 2 red tape label (+).

 

 

Attachment 1: ITHACO_1201_Instruction_&_Maintenance.pdf
ITHACO_1201_Instruction_&_Maintenance.pdf ITHACO_1201_Instruction_&_Maintenance.pdf ITHACO_1201_Instruction_&_Maintenance.pdf ITHACO_1201_Instruction_&_Maintenance.pdf ITHACO_1201_Instruction_&_Maintenance.pdf ITHACO_1201_Instruction_&_Maintenance.pdf ITHACO_1201_Instruction_&_Maintenance.pdf ITHACO_1201_Instruction_&_Maintenance.pdf
Attachment 2: DSC_3249.png
DSC_3249.png
  5318   Mon Aug 29 16:27:34 2011 ManuelConfigurationSUSSUS Summary Screen

I edited the C1SUS_SUMMARY.adl file and set the channels in alarm mode to show the values in green, yellow and red according to the values of the thresholds (LOLO, LOW, HIGH, HIHI)

I wrote a script in python, which call the command ezcawrite and ezcaread, to change the thresholds one by one.

You can call this program with a button named "Change Thresholds one by one" in the menu come down when you click the  button.

I'm going to write another program to change the thresholds all together.

  5428   Thu Sep 15 22:31:44 2011 ManuelUpdateSUSSummary screen

I changed some colors on the Summary of Suspension Sensor  using my italian creativity.

I wrote a script in Python to change the thresholds for the "alarm mode" of the screen.

The script takes a GPS-format start time as the 1st argument and a duration time as the second argument.

For every channel shown in the screen, it compute the mean value during this time.

The 3rd argument is the ratio between the mean and the LOW threshold. The 4th argument is the ratio between the mean and the LOLO threshold.

Then it sets the thresholds simmetrycally for HIGH and HIHI threshold.

It does that for all channels skipping the Gains and the Off Sets because this data are not stored.

For example is ratio are 0.9 and 0.7 and the mean is 10, thresholds will be LOLO=7, LOW=9, HIGH=11, HIHI=13.

You can run the script on pianosa writing on a terminal '/opt/rtcds/caltech/c1/scripts/SUS/set_thresholds.py' and the arguments.

I already run my program with those arguments: 1000123215 600 0.9 0.7

The time is of this morning at 5:00 for 10 minutes

 

This is the help I wrote

HELP: This program set the thresholds for the "alarm mode" of the C1SUS_SUMMARY.adl medm screen.

 Written by Manuel Marchio`, visiting student from University of Pisa - INFN for the 2011 summer at Ligo-Caltech. Thrusday, 15th September 2011.

The 1st argument is the time in gps format when you want to START the mean

The 2nd argument is the DURATION

The 3rd argument is the ratio of the LOW and the HIGH thresholds. It must be in the range [0,1]

The 4th argument is the ratio of the LOLO and the HIHI thresholds. It must be in the range [0,1]

Example: path/set_thresholds.py 1000123215 600 0.9 0.7

and if the the mean is 10, thresholds will be set as LOLO=7, LOW=9, HIGH=11, HIHI=13

 

Attachment 1: sussum.png
sussum.png
  5171   Wed Aug 10 13:52:23 2011 Manuel , IshwitaUpdatePEMMoving Seismometers

We turned off the power of the seismometers and moved the Guralp1 close to the STS. Both are now situated below the center of the mode cleaner vacuum tube.

We oriented the X axis of the STS & Guralp1 along the X axis of the interferometer. Then we turned on the power again, but the STS channels don't give any signal. We think this is, because we didn't push the auto zero button.

  5187   Thu Aug 11 11:50:56 2011 Manuel , IshwitaUpdatePEMCalibration of Guralp and STS2

 

 We just checked with a function generator the calibration of the ADC. We set a square wave with amplitude 1V. We measured the voltage with the oscilloscope and we found on the data viewer that one volt is 3208 counts. That's what we expected (+/- 10V for 16bits) but now we are more sure.

 

  5045   Wed Jul 27 12:31:47 2011 Manuel, IshwitaSummaryPEMWeekly summary

We kept reading about digital filtering

We tested the seismometer last friday

Jan came and tested again the seismometer last monday

We wrote a simulation of the stacks transfer functions, and of the distance between the mirrors.

 

  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.

  5087   Mon Aug 1 23:29:24 2011 Manuel, IshwitaUpdateWienerFilteringGetting Data by matlab

We tried to acquire data from the seismometers and the mode cleaner using the Matlab function

datalist = NDS2_GetData({'C1:PEM-SEIS_GUR1_X_IN1_DQ'}, 996258376 , 10, CONFIG.nds.C)

and encountered the following error

Warning: daq_request_data failed
 
??? Error using ==> NDS2_GetData
Fatal Error getting channel data.

The same error was obtained with the following other channels

C1:PEM-SEIS_GUR2_X_IN1_DQ

C1:PEM-SEIS_STS_1_X_IN1_DQ

But we are able to get data from channel

C1:LSC-MC_OUT_DQ

for the same gps time.

We checked with Dataviewer that the data are saved (we viewed data of last 24h) for every channel.

  5102   Wed Aug 3 02:28:08 2011 Manuel, IshwitaUpdateWienerFilteringWiener Filtering in X-arm

Wiener Filtering was applied on the data collected from the X-arm during the time: GPS time-996380715 (Aug 02, 2011. 21:25:00. PDT) to GPS time-996382215 (Aug 02, 2011. 21:50:00. PDT) for a duration of 1500 seconds. During this time the X-arm was locked, we checked it by acquiring data from channel C1:LSC-TRX_OUT_DQ .

The seismometers were near the beam splitter (guralp2) and near MC2 (guralp1).

Target data was obtained from channel C1:LSC-XARM_IN1_DQ.

Schermata-6.png

Schermata-7.png

Following graphs were obtained after applying the Wiener filter:

 

      1.Seismic data acquired from Guralp1 (X and Y) and Guralp2 (X and Y)                              2.Seismic data acquired from Guralp2 X                                                              3.Seismic data acquired from Guralp2 Y 

WFgur1X1Y2X2YN20000srate2048.pngWFgur2XN20000srate2048.pngWFgur2YN20000srate2048.png

These graphs were obtained with srate = 2048 (sample rate) and N = 20000 (order of the filter).

Graph 1 is the best because the black (residual) line is below the red (target) line for low frequencies since we used seismic data from 4 channels. Graph 3 is the worst because we used seismic data from only one Y channel (Y axis of Guralp2) that is less related with the X-arm mirrors' motion since they are oriented orthogonally.

  5106   Wed Aug 3 12:24:08 2011 Manuel, IshwitaUpdateWienerFilteringWeekly summary

Last Friday (Jul 29) we reinstalled the blue breakout box, and changed the names of the C1:PEM channels. Elog Reference

We continued the work on the simulation ad applied wiener filter on the simulated ground motion, but the result is unsatisfactory, yet. We will post reasonable results soon.

We did wiener filtering for the first time on real data from the Xarm while it was locked. Elog Reference

  5157   Tue Aug 9 16:21:59 2011 Manuel, IshwitaUpdateWienerFilteringFirst results of our simulations

We did the simulation of the stacks by defining a transfer function for one stack (green plot) and another similar transfer function for the other stack.

We simulated the ground motion by filtering a white noise with a low pass filter with a cutoff frequency at 10Hz. (blue plot) (the ground motion for the 2 stacks are completely uncorrelated)

We simulated the electronic white noise for the seismic measurements. (black plot)

We filtered the ground motion (without the measurements electronic noise) with the stack's transfer function and subtracted them to find the mirror response (red plot), which is the target signal for the wiener filter.

We computed the static wiener filter with the target signal (distance between the mirrors) and the input data (seismic measurements = ground motion + electronic noise).

We filtered the input and plotted the output (light blue plot).

We subtracted the target and the output to find the residual (magenta plot).

We didn't figure out why the residual is above the electronic noise only under ~6hz. We tried to increase and decrease the electronic noise and the residual follows the noise still only under ~6Hz.

It also shows that the residues are above the target at frequencies over 20Hz. This means that we are injecting noise here.

simu1.png

We tried to whiten the target and the input (using an high pass filter) to make the wiener filter to care even of higher frequencies.

The residues are more omogeneously following the target.

We also plotted the Wiener filter transfer function without making whitening and with making whitening. It shows that if we do whitening we inject no noise at high frequency. But we loose efficency at low frequencies.

simu2w.png

TFwhitened2.png

We shouldn't care about high frequency, because the seismometers response is not good over 50Hz. So, instead of whitening, we should simply apply a low pass filter to the filter output to do not inject noise and keep a good reduction at low frequencies.

 

  5170   Wed Aug 10 12:33:34 2011 Manuel, IshwitaSummaryPEMWeekly summary

We got the results of the wiener filtering simulations (Elog Entry)

We got the power spectra and coherence of the seismic noise measurements from GURALPs and STS seismometers (Elog Entry)

We tried to whiten the target and the input signal for the computation of the wiener filter for the real data, but the results are unsatisfactory. We should not care about high frequencies in wiener filter computation so we will just filter them off in the filter output with a low pass filter.

We just found the right gain for the system seismometer-AAboard-ADC (Elog Entry)

  5213   Fri Aug 12 17:05:22 2011 Manuel, IshwitaConfigurationPEMSTS2 Cable configuration

The WWF_M connector is the end of the STS2 seismometer orange cable and the S1 connector is the end of the gray 26-pin-cable

01050901.PDF

  9044   Wed Aug 21 00:18:03 2013 MasayukiSummaryGreen LockingX-arm PDH OLTF measurement

[Manasa Masayuki]
Today we measured the openloop transfer function of the PDH green lock of the x-arm.

Edit //manasa// The excitation was given from SR785 source. SR560 was used as the summing node at the PDH servo box output where the loop was broken to measure the OLTF. The SR785 was used to measure the frequency response (CH2/CH1; CH1 A SR560 output and CH2 A PDH servo output) in sweptsine mode.

We measured with two different servo gain. We started with the servo gain of 3 and at that gain the UGF was 1.5 kHz and the phase margin was 50 degree. After that we increase the servo gain to 5.5 and at that gain the UGF was 6.2 kHz and the phase margin was 55 degree. In all the measurement we use the source amplitude of 1.0 mV for all frequencies (from 100 Hz to 100 kHz). We could not increase the gain and also the source amplitude any more because the green was kicked out of lock.

Next work list
1. In the earlier measurements we found the UGF of the PDH green lock of the x-arm as 10 kHz and the phase margin as 45 degree, so we will investigate what has changed from these measurements.elog 4490

2. We will measure the power spectrum of the error signal and the feedback signal.

3. We will calibrate the above signals to compare with ALS out of loop noise.

netgpib was taking forever to transfer data. So the measurements are just photos of the display.

attachment1 - servo gain 3

IMG_1226.JPG

attachment2 - servo gain 5.5

IMG_1228.JPG

ELOG V3.1.3-