40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 180 of 341  Not logged in ELOG logo
ID Date Author Typedown Category Subject
  11766   Mon Nov 16 11:48:34 2015 yutaroUpdateOptical LeversBeam centering for the oplev of ETMY

[yutaro, ericq]

 

We made the beam spot on QPD for the oplev of ETMY centered by changing the orientation of the mirror just before the QPD.

Before doing this, we ran dithering for Y arm and froze the output of ASS for Y arm.
 

  11767   Mon Nov 16 16:18:34 2015 gautamUpdateGeneralwater leak along Y-arm?

A Caltech maintenance staff dropped by at around noon today, and told me that he had seen a small puddle of water on the other side of the door along the Y-arm that is kept locked (about 10m from the end-table, on the south side of the arm). He suspected a leak in the lab. Koji and I went down to the said door and observed that there was indeed a small puddle of water accumulated there. There isn't any obvious source of a leak on our side of the door, although the walls tiles in the area suggest that there could be a leak in one of the pipes running through the wall/under the floor. In any case, the leak doesn't seem too dramatic, and we have decided to consult Steve as to what is to be done about this once he is back on Wednesday.

  11770   Tue Nov 17 00:57:21 2015 ericqUpdateSUSITMX UL calmed?

After running dither alignment for all mirrors, all oplevs were recentered. (Except ETMY, since we did that earlier today.)

Looking at Koji's template for OSEM signals, the ITMX UL sensor noise floor seems more in line with the LL sensor, though there continues to be more noise than in other mirrors. 

 

Trending the sensor signals over the past 7 days, Koji's measurement looks to have been taken during a time when the UL sensor voltage had jumped down. Did someone squish the satellite box cable? I have not done so. 

I think that the step right at the end is due to a new POS offset of -2k counts, which I think Koji put into place earlier today. 

According to the wiki, the Vmax/2 values and the current values are: 

Sensor

Vmax/2

Vnow

UL

0.985

0.75

UR

0.855

0.865

LR

0.735

0.938

LL

0.775

0.60

SD

0.835

1.16

Attachment 1: TM_nov17.pdf
TM_nov17.pdf
  11771   Tue Nov 17 10:06:53 2015 SteveUpdateGeneralwater leak in east arm
Quote:

A Caltech maintenance staff dropped by at around noon today, and told me that he had seen a small puddle of water on the other side of the door along the Y-arm that is kept locked (about 10m from the end-table, on the south side of the arm). He suspected a leak in the lab. Koji and I went down to the said door and observed that there was indeed a small puddle of water accumulated there. There isn't any obvious source of a leak on our side of the door, although the walls tiles in the area suggest that there could be a leak in one of the pipes running through the wall/under the floor. In any case, the leak doesn't seem too dramatic, and we have decided to consult Steve as to what is to be done about this once he is back on Wednesday.

The leak was found inside the wall. Fortunately the plumbers were able to access it from CES room 108

This has been leaking for sometimes. The damaged wall area is about 18 ft long and 1 ft high.

Attachment 1: eastArmLeakyPipeInsideWall.jpg
eastArmLeakyPipeInsideWall.jpg
Attachment 2: wd18ft.jpg
wd18ft.jpg
  11772   Tue Nov 17 14:31:25 2015 ericqUpdateCDS16Hz frame writing temporarily disabled

To test the effect on EPICS latency, I've restarted daqd with modified ini files which disable all frame writing of 16Hz channels. 

This happened at GPS:1131835955 aka Nov 17 2015 22:52:18 UTC

Last night, I started running a script written by Dave Barker that monitors a specified EPICS channel (in this case C1:IOO-MC_TRANS_SUM), to look for seconds in which it does not update the expected number of times. This is still running, so I will be able to compare the rate of EPICS slowdowns before and after this change. 

I will revert back to the nominal state of things in a few hours, or until someone asks me to. 

  11774   Tue Nov 17 15:59:23 2015 ranaUpdateSUSITMX UL calmed?

Although this noise is bad, we have always had these kind of humps around the bounce mode. Our interpretation in the past was that this was due to poor alignment of the OSEM in the frame, leading to a large vertical to horizontal coupling. Once you implement the BLRMS for the SUS channels, we'll be able to trend the noise over long periods of time.

  11777   Tue Nov 17 20:57:43 2015 ericqUpdateCDS16Hz frame writing running again

Back to nominal FB configuration at 1131857782, aka Nov 18 2015 04:56:05 UTC.

Weirdly, during this time, the script watching MC_TRANS_SUM from pianosa saw tons of freezes, but another instance  watching LSC-TRY_OUT16 on optimus saw no freezes. 

  11778   Wed Nov 18 10:10:53 2015 ericqUpdateCDSc1iscey IO chassis missing brackets

Steve and I inadvertently discovered that the c1iscey IO chassis doesn't have brackets to secure the cards where the ADC/DAC cables are connected, making them very easy to knock loose. All other IO chassis have these brackets. Pictures of c1iscey and c1lsc IO chassis to compare:

  11779   Wed Nov 18 11:22:13 2015 yutaroUpdateASCLoss maps of arm cavities

I got linear relation between these. The results and method are below.

Quote:

In preparation for the measurement of loss maps of arm cavities, I measured the relationship between:

the offset just after the demodulation of dithering loop (C1:ASS-YARM_ETM_PIT_L_DEMOD_I_OFFSET and C1:ASS-YARM_ETM_YAW_L_DEMOD_I_OFFSET)

and

the angle of ETMY measured with oplev (C1:SUS-ETMY_OL_PIT_INMONC1:SUS-ETMY_OL_PIT_INMON and C1:SUS-ETMY_OL_PIT_INMONC1:SUS-ETMY_OL_PIT_INMON)

while the dithering script is running. With the angle of ETMY, we can calculate the beam spot on the ETMY assuming that the beam spot on the ITMY is not changed thanks to the dithering. What we have to do is to check the calbration of oplev with another way to measure the angle, to see if the results are reliable or not.

I will report the results later.

 

RESULTS

 

 

METHOD

I added offset (C1:ASS-YARM_ETM_PIT_L_DEMOD_I_OFFSET and C1:ASS-YARM_ETM_YAW_L_DEMOD_I_OFFSET) to shift the beam spot on ETMY. For each data point, I measured the difference in angle of ETMY with oplev before and after adding offset. The precedure for each measurement I employed is following:

-- run dither

-- wait until error signals of dithering settle down

-- freeze dither

-- measure angle (10s avg)

-- add offset

-- wait until error signals of dithering settle down

-- freeze dither

-- measure angle (10s avg)

The reason why I measured the angle without offset for each measurement is that the angle which oplev shows changed with time (~several tens of minutes or something). 

 

DISCUSSION

At the maximum values of offsets, the arm transmission power started to degrade, so the range where I can do this measurement is limited by these values as for now. However, we have to shift the beam spot more in order to make loss maps of sufficiently broad area on the mirror (the beam width (w) on ETM; w ~ 5 mm). Then, we have to find out how to shift the beam spot more.  

  

Attachment 1: ETM_PIT_up.png
ETM_PIT_up.png
  11783   Wed Nov 18 17:32:36 2015 yutaroUpdateOptical LeversBeam centering for the oplev of ITMY

[yutaro, Koji]

We made the beam spot on QPD for the oplev of ITMY centered by changing the orientation of the mirror just before the QPD.

Before doing this, we ran dithering for Y arm and froze the output of ASS for Y arm.

  11784   Wed Nov 18 20:49:05 2015 ranaUpdateComputer Scripts / Programsnodus boot getting full

controls@nodus|~ > df -h
Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/nodus2--vg-root  355G   69G  269G  21% /
udev                         5.9G  4.0K  5.9G   1% /dev
tmpfs                        1.2G  308K  1.2G   1% /run
none                         5.0M     0  5.0M   0% /run/lock
none                         5.9G     0  5.9G   0% /run/shm
/dev/sda1                    236M  210M   14M  94% /boot
chiara:/home/cds             2.0T  1.5T  459G  77% /cvs/cds
fb:/frames                    13T   11T  1.6T  88% /frames

  11785   Wed Nov 18 22:26:33 2015 yutaroUpdateOptical LeversCalibration of oplevs for ITMY/ETMY

Based on elog 1403, I calibrated the oplevs for ITMY/ETMY.

Summary of this method is following:

We lock an arm, and slightly misalign one mirror of the arm. Then, the transmission of the arm starts to decrease quadratically as the misalign angle of the mirror changes. Here, how much the transmission decreases in terms of the misalign angle is determined by geometry of optics, so we can see how much the angle really changes from this quadratic curve.

 

RESULTS  

These are the relationship between misalign angles measured by oplev (the units are based on the calibration for now) and transmission power.

(I updated following figures on Nov 19 2015. You can find the figures I attached once here in the zipped folder attached.) 

 

 

According to this measurement, ratio of the calibration factor derived with this measurement (NEW) and the calibration factor for now (OLD), i.e. NEW/OLD was:  

ETMY_PIT: 5.0265  --->> 5.3922 (without an outlier; the outlier I removed is shown in the figure in zipped folder attached.)

ETMY_YAW: 4.6205

ITMY_PIT: 1.5010

ITMY_YAW: 1.2970

This results show that calibration of oplevs for ITMY is kind of OK, but that for ETMY is so BAD and the calibration factors should be updated.

 

NOTE

The calibration factors of the oplevs for ETMY/ITMY are   NOT UPDATED YET.  I updated on Dec 11, 2015

If these results are reliable, I will update them tomorrow.   

Attachment 1: calib_etmypit2.pdf
calib_etmypit2.pdf
Attachment 2: calib_etmyyaw2.pdf
calib_etmyyaw2.pdf
Attachment 3: calib_itmypit2.pdf
calib_itmypit2.pdf
Attachment 4: calib_itmyyaw2.pdf
calib_itmyyaw2.pdf
Attachment 5: calib_oplev.zip
  11786   Wed Nov 18 23:18:07 2015 ericqUpdateComputer Scripts / Programsnodus /boot cleared up

The /boot partition was filling up with old kernels. Nodus has automatic security updates turned on, so new kernels roll in and the old ones don't get removed. 

I ran apt-get autoremove, which removed several old kernels. (apt is configured by default to keep two previous kernels around when autoremoving, so this isn't so risky)

Now: /dev/sda1                    236M   94M  130M  42% /boot

In principle, one should be able change a setting in /etc/apt/apt.conf.d/50unattended-upgrades that would do this cleanup automatically, but this mechanism has a bug whose fix hasn't propagated out yet (link). So, I've added a line to nodus' root crontab to autoremove once a week, Sunday morning. 

  11787   Wed Nov 18 23:40:01 2015 ranaUpdateOptical LeversCalibration of oplevs for ITMY/ETMY

OMG. Please try to use larger fonts and PDF so that we can read the plots.

Quote:

Based on elog 1403, I calibrated the oplevs for ITMY/ETMY.

I'm not sure that these calibration measurements are reliable. I would feel better if Steve can confirm them using our low accuracy method of moving the QPD by 1 mm and doing trigonometry.

  11788   Thu Nov 19 14:50:34 2015 Max IsiUpdateGeneralNew 2D histogram plot for summary pages

A new type of plot is now available for use in the summary pages, based on EricQ's 2D histogram plots (elog 11210). I have added an example of this to the SandBox tab (https://nodus.ligo.caltech.edu:30889/detcharsummary/day/20151119/sandbox/). The usage is straighforwad: the name to be used in config files is histogram2d; the first channel corresponds to the x-axis and the second one to the y-axis; the options accepted are the same as numpy.histogram2d and pyploy.pcolormesh (besides plot limits, titles, etc.). The default colormap is inferno_r and the shading is flat.

Attachment 1: C1-ALL_AB3834_HISTOGRAM2D-1131926417-86400.png
C1-ALL_AB3834_HISTOGRAM2D-1131926417-86400.png
  11789   Thu Nov 19 15:16:24 2015 ericqUpdateCDSc1iscey IO chassis now has brackets

[Steve, ericq]

Brackets for the c1iscey IO chassis cards have been installed. Now, I can't unseat the cards by wiggling the ADC or DAC cable. yes

  11790   Thu Nov 19 16:06:54 2015 yutaroUpdateOptical LeversCalibration of oplevs for ITMY/ETMY

I'm sorry. I will be careful about that. And I updated the plots in elog 11785.

Quote:

OMG. Please try to use larger fonts and PDF so that we can read the plots.

 

Quote:
Quote:

Based on elog 1403, I calibrated the oplevs for ITMY/ETMY.

I'm not sure that these calibration measurements are reliable. I would feel better if Steve can confirm them using our low accuracy method of moving the QPD by 1 mm and doing trigonometry.

 In this morning, Steve and I looked at the ETMY table and we found that the measurement you suggested might interfere with other optics or detectors because of space constraint. So, before doing this measurement, I roughly estimated the calibration factors for ETMY oplev by using the rough value of the arm length of the optical lever and the beam width of the light just before the QPD.

 

How I got the arm length and the beam width:

I measured the length of the optical path between ETMY and the QPD. Then I measured the beam width with an iris to screen the beam. To get the beam width from the decrease of the power of the beam detected by QPD, I used this formula: P/P_{max}=1-\exp(-2r^2/w^2).

Then I got:   (arm length) = 1.8 +/-0.2 m,    w= 0.56 +/- 0.5 mm.

 

How I estimated the calibration factors from these:

The calibration factors (such as C1:SUS-ETMY_OL_PIT_CALIB; (real angle) / (normalized output of QPDXorY)) can be calculated with: \sqrt{\pi/32}\times w\,/\,(\mathrm{arm\,length}). Then, I got

130\,\pm\,20 \,\mu \mathrm{rad},

though the calibration factors, C1:SUS-ETMY_OL_PIT_CALIB C1:SUS-ETMY_OL_YAW_CALIB, right now are 26.0 and 31.0, respectively. (If I express this in the same way as elog 11785, 5.0 and 4.2 for ETMY_PIT and ETMY_YAW, respectively. they are consistent with yesterday's results.) 

I believe that the calibration factors I estimated today are not different from the true values by a factor of 2 or something, so this estimation indicates that the oplev calibration measurements I did yesterday are reliable, at least for the oplev for ETMY. 

 

 

  11794   Sat Nov 21 00:45:30 2015 KojiUpdateIOOIMC fix

Based on the observation of the PMC error signal, I started measuring the IMC OLTF. Immediately, it was found that the overall IMC loop gain was too low.
The UGF was ~40kHz, which was really marginal. It had been >100kHz when I have adjusted it about a year ago. (Next entry for the detail)

The first obvious thing was that the SMA cables around the IMC servo have visible degradation (Attatched photos).
I jiggled the signal cable from the demodulator Q_out to the MC servo. The openloop gain seemed fluctuating (increased) based on the cabling.
I decided to repair these cables by adding solder on the shield.

Even after the repair, the open loop TF didn't show any improvement. I checked the LO level and found that it was -16.7dBm.

I traced the problem down to the frequency generator unit (T1000461). The front panel of the unit indicates the output power for the 29.5MHz output is 13dBm,
while measurement showed it was 6~8dBm (fluctuating). The T1000461 document describes that there is only a wenzel oscillator inside. Does this mean the oscillatorwas degraded??? We need to open the box.

I was not sure what was the LO level. I naively assumed the input is 0dBm. Reducing the attenuation of the dial on the AM Stabilizer unit from 12dB attn to 0dB.
This made the LO level -3.3dBm.


Later at home, I thought this nominal LO level of 0dBm could have been wrong.

The demodulator circuit (D990511) has the amplifier ERA-5 (G=~20dB) at the input. Between the input and the ERA-5 there is a pattern for an attenuator.
Assuming we have no attenuator, the ERA-5 has to spit out 20dBm. That is too much for this chip. I need to pull out the box to see how much is the nominal LO for this box using an active probe.

This decrease/increase of the LO level affects the WFS demod too. According to D980233-B, the input stage has the comparator chip AD96687, which can handle differential voltage of 5.5V.
Therefore the effect is minimal.

Attachment 1: PDRFsignal_cable.JPG
PDRFsignal_cable.JPG
Attachment 2: Qsignal_cable1.JPG
Qsignal_cable1.JPG
Attachment 3: Qsignal_cable2.JPG
Qsignal_cable2.JPG
Attachment 4: Qsignal_cable3.JPG
Qsignal_cable3.JPG
  11795   Sat Nov 21 00:46:33 2015 KojiUpdateIOOIMC OLTF

Here is the comparison before and after the fix.

Before the work, the UGF was ~40kHz. The phase margin was ~5deg. This caused huge bump of the frequency noise.

After the LO power increase, I had to reduce the MC loop gain (VCO Gain) from 18dB to 6dB. This resulted 4dB (x2.5) increase of the OLTF. This means that my fix increased the optical gain by 16dB (x6.3). The resulting UGF and phase mergin were measured to be 117kHz and 31deg, respectively.

 

Now I was curious to see if the PMC err shows reasonable improvement when the IMC is locked. Attachment 2 shows the latest comparison of the PMC err with and without the IMC locked. The PMC error has been taken up to 500kHz. The errors were divided by 17.5kHz LPF and 150kHz LPF to compensate the sensing response. The PMC cavity pole was ignored in this calculation. T990025 saids the PMC finesse is 4400 and the cavity pole is 174kHz. If this is true, this also needs to be applied.

Observations:

1. Now we can see improvement of the PMC error in the region between 10kHz to 70kHz.

2. The sharp peak at 8kHz is due to the marginally stable PMC servo. We should implement another notch there. T990025 suggests that the body resonance of the PMC spacer is somewhere around there. We might be able to damp it by placing a lossy material on it.

3. Similarly, the features at 12kHz and 28kHz is coming from the PMC. They are seen in the OLTF of the PMC loop.

4. The large peak at 36kHz does not change with the IMC state. This does mean that it is coming from the laser itself, or anything high-Q of the PMC. This signal is seen in the IMC error too.

5. 72kHz, 108kHz, 144kHz: Harmonics of 36kHz?

6. Broad feature from 40kHz to 200kHz. The IMC loop is adding the noise. This is the frequency range of the PC drive. Is something in the PC drive noisy???
 

7. The feature at 130kHz. Unknown. Seems not related to IMC. The laser noise or the PMC noise.


Remaining IMC issues:

Done (Nov 23, 2015) - 29.5MHz oscillator output degraded. Possibly unstable and noisy. Do we have any replacement? Can we take a Marconi back from one of the labs?

Done (Nov 23, 2015) - Too high LO?

- Large 36kHz peak in the IMC

- IMC loop shape optimization

- IMC locking issue. The lock streatch is not long.

- IMC PC drive issue. Could be related to the above issue.

Maybe not relevant - PC drive noise?

Attachment 1: IMC_OLTF.pdf
IMC_OLTF.pdf
Attachment 2: PMC_noise_comparison.pdf
PMC_noise_comparison.pdf
  11796   Sun Nov 22 07:09:01 2015 ranaUpdateIOOIMC fix

On the demod board there is a 10 dB attenuator (AT1), which lowers the level to -10 dBm before the ERA-5. Then it should be 10 dBm before going to the rest of the parts. But I guess the ERA-5 chips which come later on in the circuit could be decaying like the ones in the PMC LO board.

Quote:

Later at home, I thought this nominal LO level of 0dBm could have been wrong.

  11797   Sun Nov 22 12:07:09 2015 KojiUpdateIOOIMC fix

TO DO

Done (Nov 23, 2015) - Check if the attenuator is still there in the input chain

Done (Nov 23, 2015) - Check if the actual LO levels at the 17dBm mixers are reasonable.

- Check if the actual LO levels for the LSC demods are OK too

  11798   Sun Nov 22 12:12:17 2015 KojiUpdateIOOIMC OLTF

Well. I thought a bit more and now I think it is likely that this is just the servo bump as you can see in the closed-loop TF.

Quote:

6. Broad feature from 40kHz to 200kHz. The IMC loop is adding the noise. This is the frequency range of the PC drive. Is something in the PC drive noisy???

  11799   Mon Nov 23 14:45:39 2015 ericqUpdateComputer Scripts / ProgramsNew software

COMSOL 5.1 has been installed at: /cvs/cds/caltech/apps/linux64/comsol51/bin/comsol

MATLAB 2015b has been installed at: /cvs/cds/caltech/apps/linux64/matlab15b/bin/matlab 

This has not replaced the default matlab on the workstations, which remains at 2013a. If some testing reveals that the upgrade is ok, we can rename the folders to switch. 

  11800   Mon Nov 23 20:32:43 2015 KojiUpdateLSCFrequency source fixed, IMC LO level adjusted

The frequency source was fixed. The IMC LO level was adjusted.

IMC is locked => OLTF measured UGF 144kHz PM 30deg.

  11801   Mon Nov 23 21:48:49 2015 KojiUpdateLSCFrequency source fixed, IMC LO level adjusted

The trouble we had: the 29.5 MHz source had an output of 6 dBm instead of 13 dBm.

The cause of the issue: A short cable inside had its shield cut and had no connection of the return.


- The frequency source box was dismantled.
- The power supply voltages of +28 and +18 were provided from bench supplies.
- The 29.5 MHz output of 5~6 dBm was confirmed on the work bench.
- The 11 MHz OCXO out (unused) had an output of 13 dBm.

- Once the lid was opened, it was immediately found that the output cable for the 29.5 MHz source had a sharp cut of the shield (Attachment1).
- OK. This cable was replaced. The output of 13 dBm was recovered.

- But wait. Why is the decoupling capacitor on the 29.5 MHz OCXO bulging? The polarity of the electrolytic capacitor was wrong!
- OK. This capacitor was replaced. It was 100 uF 35 V but now it is 100 uF 50 V.

- I further found some cables which had flaky shields. Some of them were twisted. When the panel cable s connected, the feedthroughs were rotated. This twists internally connected cables. Solder balls were added to the connector to reinforce the cable end.

- When the box was dismantled, it was already noticed that some of the plastic screws to mount the internal copper heat sinks for ZHL-2's were broken.
They seemed to be degraded because of the silicone grease. I didn't try to replace all as it was expected to take too much time, so only the broken screws
were replaced with steel screws with shoulder washers
at the both side of the box.

- After confirming the circuit diagram, the box was returned to the rack. The 29.5 MHz output of 13 dBm there was confirmed.

Attachment 1: IMG_2136.JPG
IMG_2136.JPG
Attachment 2: IMG_2129.JPG
IMG_2129.JPG
Attachment 3: IMG_2133.JPG
IMG_2133.JPG
  11802   Mon Nov 23 22:12:10 2015 KojiUpdateIOOLO level check for the IMC demod board

In order to check the proper LO level, the IMC demod board was checked. As a short summary, -8dBm is the proper input for the IMC demod board. This was realized when the variable attenuator of the RF AM Stabilizer was set up be -7dB.


Initially, I tried to do the measurement using the extender board. But every board had the issue of +15V not working. After several extender boards were tried, I noticed that the current draw of the demod board burned the 15V line of the extender board.

Then I moved to the work bench. The signals were checked with the 10:1 probe. It's not properly the 50Ohm system, exactly to say.

I found that the LO signals at the mixers have huge distortion as it reaches the nominal 17dBm, and I wondered if ERA-5s were gone. Just in case I replaced the ERA-5s but didn't see any significant change. Then I thought it is due to the mixer itself. The mixer was removed and replaced with a 50Ohm SMD resister. Then the output of the last ERA-5 became sinusoidal, and the level was adjusted to be ~17dBm (4.52 Vpp) when the input power was measured to be -7.7dBm with the RF power meter. Once the mixer was reinstalled, it was confirmed that the waveform becase rectangular like, with the similar amplitude (4.42Vpp).

Now the module was returned to the rack. The RF level at the LO input was adjusted to be -8dBm by setting the attenuator level to be 7dBm.

Once the IMC is locked with this setting, the open loop transfer function was measured. The optical gain seemed almost unchanged compared with the recent nominal. The UGF and PM were measured to be 144kHz and 30deg.

Attachment 1: IMG_2137.JPG
IMG_2137.JPG
Attachment 2: IMG_2138.JPG
IMG_2138.JPG
  11803   Mon Nov 23 23:42:56 2015 ericqUpdateLSCALSY recovered

[ericq, gautam]

Gautam couldn't observe a Y green beatnote earlier, so we checked things out, fixed things up, and performance is back to nominal based on past references. 

Things done:

  • Marconi carrier output switched back on after Koji's excellent RF maintence
  • BBPD power supplies switched on
  • Removed a steering mirror from the green beatY path to do near/far field alignment. 
  • Aligned PSL / Y green beams 
  • Replaced mirror, centered beam on BBPD, moved GTRY camera to get the new spot.
  • POY locked, dither aligned, beatnote found, checked ALS out-of-loop noise, found to be in good shape. 
  11804   Tue Nov 24 01:14:23 2015 KojiUpdateLSCALSY recovered

Sorry, I completely forgot to turn the Marconi on...

  11805   Tue Nov 24 11:18:47 2015 yutaroUpdateOptical LeversBeam centering for the oplev of ITMY

I made the beam spot on QPD for the oplev of ITMY centered by changing the orientation of the mirror just before the QPD.

Before doing this, I ran dithering for Y arm and froze the output of ASS for Y arm.

  11806   Tue Nov 24 14:58:40 2015 yutaroUpdateLSCITMX misaligned

I misaligned ITMX. The oplev servo for ITMX is now turned off. You can restore ITMX alignment by running "restore".

  11807   Wed Nov 25 04:24:21 2015 ranaUpdateIOOLO level check for the IMC demod board

Hmmm. Very non-standard demod. From the photo, looks like someone did some surgery with the attenuators (AT1, AT2, AT3) in the LO path. (might be me from a long time ago).

-8 dBm input to a circuit is a not a low noise situation. It would be best to remove the amplifiers in the I&Q paths and just have a single amplifier in the main path. Ideally we want the LO to never go below -3 dBm and certainly not below 0 dBm while outside of the board.

I doubt that all of the LSC demods were modified in this way - this one ought to get some sharpie or stickers to show its difference.

  11808   Wed Nov 25 10:07:10 2015 KojiUpdateIOOLO level check for the IMC demod board

I didn't finish making the DCC entry for this module yet.

But the attenuators are
- AT1: 10dB. There is a sign that it was 3dB before ---  a 3dB chip was also attached on the boardnext to 10dB.
- AT2/3: Removed. They were replaced with 0Ohm resistors.

Currently the input is -8dBm. The input and output of the first ERA-5 are -17dBm and +7dBm, respectively.
Then the input and output of the second ERA-5 are -2dBm and 17dB, respectively.

In order to remove the second amplification stage, the first stage has to produce 26dBm. This is too much for either ERA-5 or any chips that fits on the foot print. If we use low gain but high output amp like GVA-81 (G=10dB, DF782 package), it is doable

Input 0dBm - [ATTN 3] - -3dBm - [ERA-5 G=20dB] - +16~+17dBm - [Circuits -9dB] - +7dBm - [Attn 0dB] - +7dBm - [GVA-81 G=10dB] - +17dBm

I think we should check the conditions of all the LSC demods.

  11809   Wed Nov 25 14:46:53 2015 gautamUpdateCDSc1lsc models restarted

I noticed that all the models running on C1LSC had crashed when I came in earlier today. I restarted all of them by ssh-ing into C1LSC and running rtcds restart all. The models seem to be running fine now.

  11810   Wed Nov 25 16:40:32 2015 yutaroUpdateLSCround trip loss of Y arm

I measured round trip loss of Y arm. The alignment of relevant mirrors was set ideal with dithering (no offset).

Summary:

 round trip loss of Y arm: 166.2 +/- 9.3 ppm

(In the error, only statistic error is included.)

How I measured it: 

I compared the power of light reflected by Y arm (measured at AS) when the arm was locked (P_L) and when ETMY was misaligned (P_M). P_L and P_M can be described as 

P_M=P_0(1-T_\mathrm{ITM})

P_L=P_0\left[1-(1-\alpha)\frac{4T_\mathrm{ITM}}{T_\mathrm{tot}^2}T_\mathrm{loss}\right].

The reason why P_L takes this form is: (1-alpha)*4T_ITM/(T_tot)^2 is intracavity power and then product of intracavity power and loss describes the power of light that is not reflected back. Here, alpha is power ratio of light that does not resonate in the arm (power of mismatched mode and modulated sideband), and T_tot is T_ITM+T_loss. Transmissivity of ETM is included in T_loss. I assumed alpha = 7%(mode mismatch) + 2 % (modulation) (elog 11745)

After some calculation we get

1-P_L/P_M\simeq \frac{4(1-\alpha) T_\mathrm{loss}}{T_\mathrm{ITM}}-T_\mathrm{ITM}.

Here, higher order terms of T_ITM and (T_loss/T_ITM) are ignored. Then we get

(1-\alpha) T_\mathrm{loss}=\frac{T_\mathrm{ITM}}{4}(1-P_L/P_M+T_\mathrm{ITM}).

Using this formula, I calculated T_loss. P_L and P_M were measured 100 times (each measurement consisted of 1.5 sec ave.) each and I took average of them. T_ETM =13.7 ppm is used.

Discussion: 

-- This value is not so different from the value ericq reported in July (elog 10248).

-- This method of measuring arm loss is NOT sensitive to T_ITM.  In contrast, the method in which loss is obtained from finesse (for example, elog 11740) is sensitive to T_ITM.

In the method I'm now reporting, 

\Delta T_\mathrm{loss}/T_\mathrm{loss}\simeq\Delta T_\mathrm{ITM}/T_\mathrm{ITM},

but in the method with finesse,

\Delta T_\mathrm{loss}\simeq\Delta T_\mathrm{ITM}.

In the latter case, if relative error of T_ITM is 10%, error of T_loss would be 1000 ppm.

So it would be better to use power of reflected light when you want to measure arm loss.  

  11811   Wed Nov 25 16:46:10 2015 KojiUpdateIOOLO level check for the IMC demod board

Awwww. I found that the demod board has the power splitter (PSCJ-2-1) with one output unterminated.
This power splitter should be removed.

https://dcc.ligo.org/D1500443

Attachment 1: D990511-40m_151123.pdf
D990511-40m_151123.pdf
  11812   Wed Nov 25 20:07:35 2015 ranaUpdateIOOLO level check for the IMC demod board

Perhaps we can replace T1 with a mini-circuits hybrid 0-90 deg splitter and then remove the trim caps. (JSPQ-80, JYPQ-30, SCPQ-50)

  11813   Wed Nov 25 22:37:12 2015 yutaroUpdateLSCremoval of Gautam's cable in 1Y2 and restoration of POYDC

[yutaro, Koji]

We disconnected the cable that was connected to CH5 of the whitening filter in 1Y2, then connected POYDC cable to there (CH5). This channel is where POYDC used to connect.

Then we turned on the whitening filter for POYDC (C1:LSC-POYDC FM1) and changed the gain of analog whitening filter for POYDC from 0 dB to 39 dB (C1:LSC-POYDC_WhiteGain).

  11814   Wed Nov 25 22:59:42 2015 yutaroUpdateLSCAS table optics realignment

I slightly changed the orientation of a few mirrors on AS table that are used to make the AS light get into PDs, in order to confirm that the strange behavior of ASDC (I will report later) is not caused by clipping related to these mirrors or miscentering on PDs.

Then output level of ASDC, AS55, and AS165 could have changed.   

So take care of this possible change when you do something related to them. But the relative change of them would be at most several %, I think.

 

  11815   Wed Nov 25 23:17:34 2015 yutaroUpdateLSCstrange behavior of ASDC

[yutaro, Koji]

I noticed that ASDC level changes depending on the angle of ITMY when trying to take some data for loss map of YARM. We finally found that ASDC level behaves strangely when the angle of ITMY in yaw direction is varied, as you can see in Attachment 1. Now, AS port recieved only the reflection of ITMY. 

NOTE: This behavior indicates that angular motion could couple to length signal in AS port.      

Koji suggested that this behavior might be caused by interference at SR2 or SR3 between main path light and the light reflected by the AR surface. By rough estimation, we confirmed that this scenario would be possible. So it would be better to measure AR reflection of the same mirror to ones used for SR2 and SR3 in term of incident angle.     

Ed by KA: This senario could be true if the AR reflection of teh G&H mirrors have several % due to large angle of incidence. But then we still need think about the overlap between the ghost beam and the main beam. It's not so trivial.

Attachment 1: 14.png
14.png
  11816   Wed Nov 25 23:34:52 2015 yutaroUpdateLSCround trip loss of Y arm

[yutaro, Koji]

Due to the strange behavior (elog 11815) of ASDC level, we checked if it is possible to use POYDC instead of ASDC to measure the power of reflected light of YARM. Attached below is the spectrum of them when the arm is locked. This spectrum shows that it is not bad to use POYDC, in terms of noise. The spectrum of them when ETMY is misaligned looked similar.

So I am going to use POYDC instead of ASDC to measure arm loss of YARM. 


Ed by KA:
The spectra of POYDC and ASDC were measured. We foudn that they have coherence at around 1Hz (good).
It told us that POYDC is about 1/50 smaller than ASDC. Therefore in the attached plot, POYDC x50 is shown.
That's the meaning of the vertical axis unit "ASDC".

Attachment 1: 14.png
14.png
  11817   Thu Nov 26 19:39:27 2015 KojiUpdateLSCCurrent state of the frequency source, and possible improvement

Uploaded on T1000461 too.

Attachment 1: RF_Frequency_Source.pdf
RF_Frequency_Source.pdf RF_Frequency_Source.pdf
  11819   Fri Nov 27 22:20:24 2015 yutaroUpdateLSCround trip loss of Y arm

Here, I upload data I took last night, including the power of reflected power (locked/misaligned) and transmitted power for each point (attachement 1).

 

And I would like to write about possible reason why the loss I measured with POYDC and the loss I measured with ASDC are different by about 60 - 70 ppm (elog 11810 and 11818). The conclusion I have reached is: 

It could be due to the strange bahavior of ASDC level. 

This difference corresponds to the error of ~2% in the value of P_L/P_M. As reported in elog 11815, ASDC level changes when angle of the light reflected by ITMY changes, and 2% change of ASDC level corresponds to 10 urad change of the angle of the light according to my rough estimation with the figure shown in elog 11815 and attachment 2. This means that 2% error in P_L/P_M could occur if the angle of the light incident to YARM and that of resonant light in YARM differ by 10 urad. Since the waist width w_0 of the beam is ~3 mm, with the 10 urad difference, the ratio of the power of TEM10 mode is (10\,\mu \mathrm{rad}/ \theta_0)^2\sim0.01, where \theta_0=\lambda/\pi w_0. This value is reasonable; in elog 11743 Gautam reported that the ratio of the power of TEM10 was ~ 0.03, from the result of cavity scan. Therefore it is possible that the angle of the light incident to YARM and that of resonant light in YARM differ by 10 urad and this difference causes the error of ~2% in P_L/P_M, which could exlain the 60 - 70 ppm difference. 

Attachment 1: log.txt.zip
Attachment 2: 17.png
17.png
  11820   Sat Nov 28 11:46:40 2015 yutaroUpdateLSCpossible error source of loss map measurement

I found that TRY level degraded and the beam shape seen with CCD camera at AS port was splitted when the beam spot on ETMY was not close to the center. This was because dither started not working well. I suspect so because in such a case TRY level went up when I did iteration with TT1 and TT2 after freezing dither. Splitted beam shape indicates that incident light did not match well with the cavity mode.

TRY level for each point was this:

TRYDC
[[ 0.6573      0.8301      0.8983      0.8684      0.6773    ]
 [ 0.7555      0.8904      0.9394      0.8521      0.6779    ]
 [ 0.6844      0.8438      0.9318      0.8834      0.6593    ]
 [ 0.7429      0.8688      0.9254      0.8427      0.6474    ]
 [ 0.7034      0.8447      0.8834      0.8147      0.6966    ]]

 In the worst case, TRY level was 70 % of the maximum level. Assuming that this degrade was totally due to the mode mismatch, this corresponds to ~50 urad difference between the angle of incident light and resonant lighe in the arm (see elog 11819).

  11821   Sun Nov 29 05:23:57 2015 ranaUpdateLSCCurrent state of the frequency source, and possible improvement

I need some more hints to understand the improvement, although its generally good to re-build it considering the sad state of the assembly/installation that you found.

I see that the current design brings the 11 MHz signal to -2 dBm before intering the first ZHL-2+, but since that has a NF of 9 dB, that seems to only degrade the phase noise to -2 - (-174 +9) = -163 dBc. That seems OK since we only need -160 dBc from this system. Probably the AM noise is worse than this already (we should remember to hook up a simple AM stabilizer in 2016, as well as the ISS).

What else are the main features of this improvement? I can reward a good summary with some Wagonga.

  11822   Sun Nov 29 12:32:26 2015 KojiUpdateLSCCurrent state of the frequency source, and possible improvement

I'm not claiming we need to modify the frequency source immediately as we are not limited by the oscillator amplitude or phase noise.
I just wanted to note something in mind before it goes away quickly.

Alberto's T1000461 tells us that the oscillator and phase noise are degraded by factor of ~3 and ~5 due to the RF chanin.
My diagram is possible removal of up-down situation of the chain.

Maybe more direct improvement would be:

- Removal of two amplifiers out of four. The heat condition of the box is touch thought it is not critical.

- The modification will allow us to have a spare 11MHz channel at 1X2 rack that would be useful for 3f modulation.

  11823   Mon Nov 30 10:41:45 2015 yutaroUpdateLSCDoes a baffle in front of ETMY have effect on loss map measurement?

It might have, so I think I need to estimate shift of beam spot more preciely.

 

According to Steve's drawing, radius of the hole of the baffle is 19.8 mm.

Intensity distribution of fundamental mode in x axis direction is this (y is integrated out):

I(x)=\frac{1}{\sqrt{2\pi(w/2)^2}}e^{-\frac{1}{2}\left(\frac{x}{w/2}\right)^2}

With the radius of curvature of ETMY of 60 m and the arm length of 37.78 m, the beam width w on ETMY is estimated to be 5.14 mm. From this expression of the intensity, \int^\infty_{x=9.56\mathrm{mm}}\mathrm{d}xI(x)=100\,\mathrm{ppm},\,\int^\infty_{x=10.00\mathrm{mm}}\mathrm{d}xI(x)=50\,\mathrm{ppm}, for example. If round trip loss is considered, these values are doubled.

Although maximum shift of beam spot from the ideal spot on ETMY is estimated to be sqrt(6.0^2+(1.7+1.7)^2)=6.9 mm, this value could have error of several tens of % because I am not sure to what exten the calibration is precise, which means that the maximum shift could be ~10 mm and seperation between the baffle and the beam could be ~10 mm.

Therefore, I need to check how much the beam spot shifts with another way, maybe with captured image of the CCD camera. 

 

  11824   Mon Nov 30 12:19:38 2015 yutaroUpdateComputer Scripts / Programsimage capture

On VIDEO.adl, Image Capture and Video Capture did not seem to work and gave me some errors, so I fixed following two things:

1. just put one side of a USB cable to Pianosa the other side of which was connected to Sensoray; I don't know why but this was unconnected.

2. slightly fixed /users/sensoray/sdk_2253_1.2.2_linux/imsub/display-image.py as fpllows   

L52:       pix[j, i] = R, G, B     ->     pix[j, i] = int(R), int(G), int(B)  

It seems to work, at least for some cameras including ETMYF and ITMYF. 

  11825   Mon Nov 30 14:12:14 2015 ericqUpdateLSCLO level check for the LSC RF distribution box

I checked the RF levels at the LSC LO distribution box, with the agilent scope and a handful of couplers. This was all done with the Marconi at +13dBm. 

I only checked the channels that are currently in use, since the analyzer only measures 3 channels at a time, and rewiring involves walking back and forth to the IOO rack to make sure unpowered amps aren't driven, and I was getting hungry. 

For the most part, the LO levels coming into the LSC demod boards are all around +1.5dBm (i.e. I measured around -18.0dBm out of the ZFDC-20-5 coupler, which has a nominal 19.5dB coupling factor)

The inputs piped over from the IOO rack, labeled as "+6dBm" were found to be 4.7dBm and 2.9dBm for 11Mhz and 55MHz, respectively. 

The 2F signals were generally about 40dB lower, with two exceptions:

  • REFL165's ~332MHz signal was around -18dBc
  • POP22 had many more visible harmonics than any other LO signal
    • 11MHz: -32 dBc
    • 33MHz: -32 dBc
    • 44Mhz: -15dBc 

Here are the raw numbers I measured out of the couplers, all in dBm:

  • 11MHz in: -14.8
  • 55MHz in: -16.6
  • POX11:    -18.7
  • POY11:    -18.0
  • REFL11:   -18.0
  • REFL33:   -18.3
  • POP110:   -17.9
  • AS110:    -18.1
  • POP22:    -19.9
  • REFL165:  -18.5
  • AS55:     -18.6
  • POP55:    -18.8 (this port is used as the REFL55 LO)
  11826   Mon Nov 30 15:17:57 2015 KojiUpdateLSCLO level check for the LSC RF distribution box

T1000461 tells us that the nominal LO input is 2dBm although we don't know what's the LO level is at the mixers in the demod boards.

  11827   Mon Nov 30 16:33:06 2015 ericqUpdateLSCstrange behavior of ASDC

One possible explanation of this behavior is simply poor centering of the AS beam on AS55 (whose DC level provides ASDC, if memory serves me correctly).

I misaligned ETMY, and moved ITMY through its current nominal alignment while looking at the POYDC and ASDC levels. 

In both pitch and yaw, the nominal alignment is fairly close to the "plateau" in which the AS beam is fully within the PD active surface. I.e. it doesn't take much angular motion to start to lose part of the beam, and thus introduce a first order coupling of angle to power. (Look at the plateaus at around -2min and -0.5min, and where the rapidly changing oplev trace crosses zero)

Furthermore, POYDC seems to be in some weird condition where it is actually possible to increase the reported powerwhen misaligning in pitch, but somehow there is more angular coupling in this state. 

In any case, I would advise that the POY11 and AS55 RFPDs have their spots recentered with optics in their nominal aligned states. In fact, given how we found REFL11 alingment to be less-than-ideal not so long ago, all of the RFPDs could probably use a checkup. 

ELOG V3.1.3-