LOG-IN
Displaying reports 1061-1080 of 3032.Go to page Start 50 51 52 53 54 55 56 57 58 End
R&D (FilterCavity)
Print this report.
NaokiAritomi - 15:51, Monday 30 November 2020 (2297)Get code to link to this report
Comment to CCFC successfully locked (Click here to view original report: 2182)

I attached OLTF of CCFC and green lock. Note that I flipped the sign of measured data to match the measurement and theory. The measured phase is not consistent with theory.

Images attached to this comment
2297_20201130092424_20200827ccfcoltf.png
R&D (FilterCavity)
Print this report.
NaokiAritomi - 00:20, Friday 27 November 2020 (2296)Get code to link to this report
Optimization of CC PLL frequency for CCFC

In elog1727, I tuned CC PLL frequency from the fitting of CC separation frequency and CC PLL frequency, but the error of the fitting parameters is quite large with respect to optimal CC separation frequency 108 Hz. So this method is not precise to decide the correct detuning.

As written in elog2294, current CCFC error signal is not consistent with theoretical plot with optimal detuning, but instead it is similar to the theoretical plot with 25 Hz detuning.

If the current detuning is 25 Hz, we have to change the detuning by 29 Hz to obtain optimal detuning 54 Hz. Using the formula in elog1727, the CC PLL frequency has to be changed by 2*29 Hz/1.907605 =  30.41 Hz. Since the current CC PLL frequency is 6.99704303 MHz, optimal CC PLL frequency should be either 6.99707344 MHz or 6.99701262 MHz. I checked both cases by looking at CCFC error signal and found that 6.99701262 MHz is correct one (In DDS, 6.99701253 MHz was set). 

Here is the new CC PLL setting. I saved this setting as 20201126_dds3_CCFC.

channel   function frequency (MHz)                 binary number
CH0 CC PLL 20.99103760  1010 10111111 01010110 01011000
CH2/3 CC1/CCFC demod 13.99402518    111 00101010 00111001 10010000
      6.99701253      11 10010101 00011100 11001000

 

 

 

 

Attached plot shows CCFC error signal with different CCFC demodulation phase. Amplitude of the CCFC error signal is normalized with 83mV which is the amplitude of CCFC error signal when CCSB are off resonance of FC and CC1 is scanned.

Now the shape of CCFC error signal is similar to theoretical plot. In addtion to that, zero crossing point of blue curve in second plot is around 58Hz which is almost optimal detuning.

Images attached to this report
2296_20201126162236_20201126ccfcall.png 2296_20201127152518_20201126ccfc.png 2296_20201127152526_ccfcdemod.png
R&D (FilterCavity)
Print this report.
NaokiAritomi - 20:37, Thursday 26 November 2020 (2294)Get code to link to this report
Comment to CCFC error signal characterization (Click here to view original report: 2289)

CCFC error signal with 25 Hz detuning is very similar to the measurement.

Images attached to this comment
2294_20201126123653_20201125ccfc.png 2294_20201126123658_ccfc25hzdetuning.png
R&D (FilterCavity)
Print this report.
NaokiAritomi - 20:19, Thursday 26 November 2020 (2293)Get code to link to this report
Comment to Frequency tuning of coherent control sidebands (CCFC) (Click here to view original report: 1727)

Actually, the errors of the fitting parameters are -1907605 +/- 36859 and 13347486 +/- 257882. This error is quite large with respect to 108 Hz. We need to fine tune CC PLL frequency by looking at CCFC error signal.

R&D (FilterCavity)
Print this report.
NaokiAritomi - 19:47, Thursday 26 November 2020 (2292)Get code to link to this report
Comment to CCFC error signal characterization (Click here to view original report: 2289)

By the way, optimal detuning should be 54 Hz. I attached CCFC error signal with optimal detuning. Normalized offset for I phase is 0.81 in the plot.

Images attached to this comment
2292_20201126123237_ccfclargedetuning.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 17:40, Thursday 26 November 2020 (2291)Get code to link to this report
Comment to CCFC error signal characterization (Click here to view original report: 2289)

I checked that for optimal detuning (70Hz), the expected in-phase demodulation CCFC error signal should have normalized offset 0.91.

In this measurement, we got the in-phase demodulation CCFC error signal normalized offset to be about 0.69. I checked that for this normalized offset, the detuning set by PLL will be 43deg.

The calculation is in the attached figure.

Images attached to this comment
2291_20201126093951_35.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 03:32, Thursday 26 November 2020 (2290)Get code to link to this report
Comment to CCFC error signal characterization (Click here to view original report: 2289)

By looking at the normalized offset-removed plots, it seems for different demodulation phase, they have the 'same' peak but just somtimes folded.

If we compare it with calculation, it seems the measured peak is a factor of 2 smaller than calculation.

Images attached to this comment
2290_20201125193229_06.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 03:19, Thursday 26 November 2020 (2289)Get code to link to this report
CCFC error signal characterization

It has been a long time that we found CCFC error signal measurement doesn't match well with calculation. Recently, we found that this might be due to an offset, as reported in elog2286.

The CCFC error signal is equation 14/15 in Aritomi paper, which can be written as proportational to sin(a_p-a_m+a0_m-2d_p). Please check details from arxiv:2004.01400.
 
Here a_p and a_m are the upper and lower sidebands phase change caused by the filter cavity. When the filter cavity has detuning much larger than linewidth (70Hz), a_p-a_m will be close to zero. a0_m is the lower sideband phase change caused by the filter cavity when carrier detuning is optimal. When we change the demodulation phase of CCFC, we add another term phi_d to the sine function.
 
Therefore, in the case that FC is locked and detuned to 1kHz (CC1 locked), the CCFC error signal will be sine(a0_m+phi_d). Since a0_m is a fixed number, we expect to measure a shifted sine wave when scanning phi_d (from 0 to 2pi). For each phi_d, we expect an 'offset' from zero. We got a 'shifted' sine wave from the experiment. The result of this measurement is in the first attached figure. There is also a sinusoidal plotted in this figure. We could see that the measurement matches with sinusoidal. The difference still needs to be investigated (one further check could be a measurement of error bar for each point, the other could be to plot a histogram of measured data)
 
To double-check this expected offset, we performed the filter cavity scan around resonance (CC1 locked, FC locked while AOM scanned). The CCFC error signal for different phi_d is in the attached figure2. If we subtract the measured offset from figure2, we got figure 3. Not surprisingly, all offsets of CCFC error signals were removed. Thus we know this offset agrees with the calculation.
 
Then the question comes: why we saw a different CCFC error signal in an experiment different from a calculation that is not caused by an offset problem?
 
If we compare figure 2 with the calculation, we could see that every time the CCSBs cross resonance of the filter cavity, the appeared peak seems to be not deep enough. So we guess the problem is related to how the filter cavity changes the CCSBs phase when they cross resonance.

The CCFC error signal is equation 14/15 in Aritomi paper, which can be written as proportational to sin(a_p-a_m+a0_m-2d_p). Please check details from arxiv:2004.01400.

Here a_p and a_m are the upper and lower sidebands phase change caused by the filter cavity. When the filter cavity has detuning much larger than linewidth (70Hz), a_p-a_m will be close to zero. a0_m is the lower sideband phase change caused by the filter cavity when carrier detuning is optimal. When we change the demodulation phase of CCFC, we add another term phi_d to the sine function.

Therefore, in the case that FC is locked and detuned to 1kHz (CC1 locked), the CCFC error signal will be sin(a0_m+phi_d). Since a0_m is a fixed number, we expect to measure a shifted sine wave when scanning phi_d (from 0 to 2pi). For each phi_d, we expect an 'offset' from zero. We got a 'shifted' sine wave from the experiment. The result of this measurement is in the first attached figure. There is also a sinusoidal plotted in this figure. We could see that the measurement matches with sinusoidal. The difference still needs to be investigated (one further check could be a measurement of error bar for each point, the other could be to plot a histogram of measured data)

To double-check this expected offset, we performed the filter cavity scan around resonance (CC1 locked, FC locked while AOM scanned). The CCFC error signal for different phi_d is in the attached figure2. If we subtract the measured offset from figure2, we got figure 3. Not surprisingly, all offsets of CCFC error signals were removed. Thus we know this offset agrees with the calculation.

Then the question comes: why we saw a different CCFC error signal in an experiment different from a calculation that is not caused by an offset problem?

If we compare figure 2 with the calculation, we could see that every time the CCSBs cross resonance of the filter cavity, the appeared peak seems to be not deep enough. So we guess the problem is related to how the filter cavity changes the CCSBs phase when they cross resonance.

This not ideal CCSBs phase change could be caused by mode mismatch/misalignment or PLL setting. More investigation is required.

Images attached to this report
2289_20201125192047_figure0.png 2289_20201125192105_normalized.png 2289_20201125192333_normalized2.png
Comments related to this report
YuhangZhao - 03:32, Thursday 26 November 2020 (2290)

By looking at the normalized offset-removed plots, it seems for different demodulation phase, they have the 'same' peak but just somtimes folded.

If we compare it with calculation, it seems the measured peak is a factor of 2 smaller than calculation.

YuhangZhao - 17:40, Thursday 26 November 2020 (2291)

I checked that for optimal detuning (70Hz), the expected in-phase demodulation CCFC error signal should have normalized offset 0.91.

In this measurement, we got the in-phase demodulation CCFC error signal normalized offset to be about 0.69. I checked that for this normalized offset, the detuning set by PLL will be 43deg.

The calculation is in the attached figure.

NaokiAritomi - 19:47, Thursday 26 November 2020 (2292)

By the way, optimal detuning should be 54 Hz. I attached CCFC error signal with optimal detuning. Normalized offset for I phase is 0.81 in the plot.

NaokiAritomi - 20:37, Thursday 26 November 2020 (2294)

CCFC error signal with 25 Hz detuning is very similar to the measurement.

R&D (FilterCavity)
Print this report.
YuhangZhao - 10:01, Wednesday 25 November 2020 (2288)Get code to link to this report
PR Oplev shows noise and recovered (similar with BS case)

Recently we are investigating HAMAMATSU PSD to be used for Oplev. This is due to the noise increase observed for BS Oplev spectrum, which was pointed out to be caused by PSD.

Last Friday, a similar problem was found also in PR Oplev. As shown in the attached figure 1 and 2, the PR Oplev noise has different noise increase at different time.

I also checked PR Oplev spectrum this Monday, the spectrum became normal as attached figure 3.

Images attached to this report
2288_20201125020616_princrease2.png 2288_20201125020627_prnoiseincrease.png 2288_20201125020635_pr20201124.png
R&D (FilterCavity)
Print this report.
RyutaroTakahashi - 12:57, Tuesday 24 November 2020 (2287)Get code to link to this report
Comment to System recovery after Mitaka power outage (Click here to view original report: 2278)

Oil under the rotary pump was there from the old days. I replaced the rotary pump to new dry pump (ACP15). The TMP with the dry pump is working now at the mid point.

Images attached to this comment
2287_20201124045659_newdrymp2.jpg
R&D (FilterCavity)
Print this report.
NaokiAritomi - 19:59, Friday 20 November 2020 (2286)Get code to link to this report
Changing CC1 and CCFC demodulation phase independently

DDS3 CH2 (14MHz) was split to used for both CC1 and CCFC demodulation so far. To change these demodulation phase independently, we used DDS3 CH3, which is usually used for CC2 demodulation, for CCFC demodulation. We changed CC1 and CCFC demodulation phase independently and checked CCFC error signal. We confirmed that changing CC1 demodulation phase is identical to changing CCFC demodulation phase for CCFC error signal.

R&D (FilterCavity)
Print this report.
YuhangZhao - 23:41, Thursday 19 November 2020 (2285)Get code to link to this report
Comparison of Thorlabs PSD (with amplification) and HAMAMATSU PSD (without amplification) for INPUT mirror oplev

To see the possibility of using HAMAMATSU PSD for INPUT mirror oplev, I did the comparison between Thorlabs PSD (with amplification) and HAMAMATSU PSD (without amplification) for INPUT mirror oplev.

The comparison result is shown in the attached figure.

Upper figure: (for INPUT pitch) REF0 is INPUT oplev spectrum with Thorlabs PSD. REF 2 Thorlabs PSD electronic noise after amplification. REF 4 INPUT oplev spectrum with HAMAMATSU 04 PSD. Red line: HAMAMATSU 04PSD electronic noise.

Lower figure: (for INPUT yaw)REF0 is INPUT oplev spectrum with Thorlabs PSD. REF 2 Thorlabs PSD electronic noise after amplification. REF 4 INPUT oplev spectrum with HAMAMATSU 04 PSD. Red line: HAMAMATSU 04PSD electronic noise.

It can be seen that Thorlabs PSD has a bit better SNR. This better SNR is proven to come from the amplification (proved in elog2114).

Images attached to this report
2285_20201119155941_inputcomp.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 23:26, Thursday 19 November 2020 (2284)Get code to link to this report
HAMAMATSU PSD electronic noise and DGS ADC noise

As reported in elog2281, the HAMAMATSU PSD electronic noise level is similar with DGS ADC noise. In this entry, I report a futher investigation of them.

1. I had a closer look into these two noise spectrum. As shown in the attached figure 1 (RED is elec noise, BLUE is ADC noise, GREEN/BROWN are integrated noise), elec noise is a bit higher than ADC noise but not a factor of  2. Therefore, to investigate further the electronic noise, we should amplify signal from PSD before it goes inside DGS system.

2. Before amplification of PSD individual signal, I checked the time series of individual signal from PSD. This is shown in the attached figures 2. We could see that it has very large noise. Therefore, it is very diffcult to amplify such large noisy signal. Indead, I found SR560 could only give a factor of 2 amplification for it before saturation. But the good thing is that, after the combination inside DGS, this noise is cancelled and resulted in a clean pitch/yaw electronic noise.

So if we really want to check better the electronic noise, we should combine PSD individual signal before they go inside DGS system.

Images attached to this report
2284_20201119155856_04eleadc.png 2284_20201119170903_wechatimg42.jpeg
R&D (FilterCavity)
Print this report.
YuhangZhao - 23:07, Thursday 19 November 2020 (2283)Get code to link to this report
Comparing 03PSD and 04PSD

By replacing 03PSD with 04PSD for BS oplev, I compared their performance.

The measured oplev spectrums are shown in the attached figure 1 (RED 04PSD, BROWN 03PSD), while the electronic noise comparison with ADC noise is shown in the attached figure 2 (RED is elec noise, BLUE is ADC noise, GREEN/BROWN are integrated noise).

We could conclude that both 03PSD and 04PSD have almost the same performance. The difference in position resolution is not affecting their performance now. So I guess this position resolution maybe related with beam size.

Images attached to this report
2283_20201119155559_0304.png 2283_20201119155802_04eleadc.png
R&D (Cryogenic)
Print this report.
SatoshiTanioka - 18:18, Thursday 19 November 2020 (2282)Get code to link to this report
Q-mass does work

I tried to measure the residual gas molecules by a mass spectrometer.
The Q-mass could be operated by a front panel, and the pressure was 3.0*10-5 Pa, 7.8*10-7 Pa for H2o and N2 respectively.

Hoever, I could not connect to PC, and could not do degas.
This Q-mass needs degas but in order to do that, the connection to PC is needed...

I will ask the company.

R&D (FilterCavity)
Print this report.
YuhangZhao - 23:23, Wednesday 18 November 2020 (2281)Get code to link to this report
HAMAMATSU PSD C10443-03 test

Since we have problem of TAMA PSD, we considered to buy new PSD. Matteo asked two PSD from HAMAMATSU company for test. They are C10443-03 (we call it 03 later) and C10443-04 (we call it 04 later). The information of them can be found from this link.

From the datasheet, 03 and 04 PSD only have difference in position. I think the integrated noise spectrum can represent a position resolution. If so, the one with better position resolution should have a lower noise spectrum. Therefore, I firstly tested 03 which has a better position resolution. If it is better than the old PSD, we should use it in the future.

Together with Matteo, we made a customized circuit based on Mammoth connectors, bananna connectors and lemo connectors. In this way, the eight channels from HAMAMATSU PSD can be connected to power supply and ADC of DGS system. Four channels from PSD are used for power supply, which contain one plus(12V), one minus(-12V) ,and two grounds. Another four channels are called x1, x2, y1, and y2 separatly. The experimental set-up is shown in attached figure 1.

To convert four signal channels into pitch and yaw, I realized a matrix inside simulink file. This matrix is enclosed in a block called 'BS_test', as shown in the attached figure2.

Since old measurements have been saved in DGS system, I just plot new PSD data with old ones. As shown in the attached figure 3, there is comparison between old low gain TAMA PSD and 03PSD. We can see

1. REF0/1 (BS angular motion sensed by low gain TAMA PSD) is comparable with REF16/17 (BS angular motion sensed by 03PSD). This means that two PSD have the same gain.

2. REF8/9 (electronic noise of low gain TAMA PSD) is lower than REF24/25 (electronic noise of 03PSD).

3. Red lines in this figure shows the ADC noise. Actually this measurement is a bit strange. It shows that ADC noise is even higher than the electronic noise of low gain TAMA PSD. This can be correct if the ADC noise really becomes worse by itself.

4. Since the Red lines overlap with REF 24/25, it means the measured electronic noise maybe just ADC noise. So if we want to check better mirror angular motion, we need to amplify the signals coming from PSD.

I also compared the electronic noise between high gain TAMA PSD with 03PSD. The result is shown in the attached figure 4. Red lines are 03PSD electronic noise, which is lower than REF8/9 (high gain TAMA PSD electronic noise). 

We will also test 04 PSD to justify the relationship between PSD position resolution and noise spectrum.

Images attached to this report
2281_20201118152805_hamamatsupsd.jpeg 2281_20201118152850_img20201118105454.jpg 2281_20201118153026_untitled.png 2281_20201118153031_untitled2.png
R&D (Cryogenic)
Print this report.
SatoshiTanioka - 15:34, Wednesday 18 November 2020 (2280)Get code to link to this report
Q-mass does not work

I pumped down the cryostat and turned on the Q-mass.
The LED lamp next to "POWER" turned on, though that of "Pa" did not.
It seems that this Q-mass may not be used anymore.

Furthermore, in order to degas the Q-mass, we need to pump down below 10-4 Pa, though it cannot reach below 6*10-4 Pa...
I gave up the measurement.

Images attached to this report
2280_20201118073419_qmass20201118.jpg
R&D (FilterCavity)
Print this report.
MatteoLeonardi - 15:46, Tuesday 17 November 2020 (2279)Get code to link to this report
Comment to System recovery after Mitaka power outage (Click here to view original report: 2278)
Some additional information regarding the recovery of the TAMA vacuum system after the power outage.

1) Two vacuum sensors were found not working. They are END station (arm side) and MID station (TAMA central side). The controller seems to work properly but it provide a "FAIL" message when reading the sensors.

2) The rotary pump in MID station has what it seems an oil leakage (see picture 1 and 2). I did not noticed this leakage when shutting it down on Friday but I did not payed particular attention to it, so I cannot tell if the problem was already present.

3) I could not find where to switch on the air dryer of South Arm. The West Arm air dryer are working.
Images attached to this comment
2279_20201117074132_img20201116113347.jpg 2279_20201117074141_img20201116113406.jpg
R&D (FilterCavity)
Print this report.
YuhangZhao - 15:28, Tuesday 17 November 2020 (2278)Get code to link to this report
System recovery after Mitaka power outage

Eleonora, Matteo and Yuhang

All facilities and devices were recovered after the Mitaka power outrage.

The Mitaka power outage was done on 14th Nov., while the recovery work was done on 16th Nov.. Although everything was recovered, there were some issues we encountered during the recovery work.

1. The main power switch for the filter cavity arm lights were not found at the beginning. The reason is that this switch is located in the middle of filter cavity arm (I didn't know this at the beginning).

2. The sound issue of DDS. The solution is provided in elog1794.

3. To power on DAC, there is a DC voltage supply. At the beginning, I forgot to provide negative 18V. Then, while I increased the positive voltage, the maximum can reach only around 6.5V.

4. This time, none DDS channels flipped phase by 90deg.

5. The optimal temperature of SHG has been changed from 3.074 to 3.102. On the second day, the value changed back to 3.081.

6. The position of suspended mirror didn't change a lot. We don't need to change largly voltage offset sent to mirrors to recover FC flash.

7. PDH signal of FC lock has large 5kHz resonance even when FC is unlocked. It was figured out that this oscillation comes from SHG. And the problem is solved by reduce the gain of SHG to 2.1.

8. It was found that the input value of DGS doesn't change on medm. We checked medm sitemap/CDS. The situation is shown in the attached figure 1. It was figured out later that this is because I was using sine wave instead of square wave. After correcting to the good waveform, DGS worked again. The good sitemap/DGS is shown in the attached figure 2.

9. It was found that ratory pump in the middle arm has oil leakage.

Images attached to this report
2278_20201117075250_wechatimg40.jpeg 2278_20201117075315_good.png
Comments related to this report
MatteoLeonardi - 15:46, Tuesday 17 November 2020 (2279)
Some additional information regarding the recovery of the TAMA vacuum system after the power outage.

1) Two vacuum sensors were found not working. They are END station (arm side) and MID station (TAMA central side). The controller seems to work properly but it provide a "FAIL" message when reading the sensors.

2) The rotary pump in MID station has what it seems an oil leakage (see picture 1 and 2). I did not noticed this leakage when shutting it down on Friday but I did not payed particular attention to it, so I cannot tell if the problem was already present.

3) I could not find where to switch on the air dryer of South Arm. The West Arm air dryer are working.
RyutaroTakahashi - 12:57, Tuesday 24 November 2020 (2287)

Oil under the rotary pump was there from the old days. I replaced the rotary pump to new dry pump (ACP15). The TMP with the dry pump is working now at the mid point.

R&D (FilterCavity)
Print this report.
NaokiAritomi - 21:13, Monday 16 November 2020 (2277)Get code to link to this report
Comment to SHG cavity scan (Click here to view original report: 2269)

I measured SHG cavity scan again. This time, I put SHG temperature 2.8kOhm to avoid green conversion while nominal temperature is 3.1kOhm. Peak shape is still not completely symmetric possibly due to high IR injection power, but measured finesse is 70 which is reasonable value. 

Images attached to this comment
2277_20201116131337_shgcavityscan.png 2277_20201116131342_shgcavityscan2.png