LOG-IN
Displaying reports 1081-1100 of 3274.Go to page Start 51 52 53 54 55 56 57 58 59 End
R&D (FilterCavity)
Print this report.
YuhangZhao - 21:25, Thursday 03 June 2021 (2557)Get code to link to this report
Comment to Filter cavity pointing loop control precision (Click here to view original report: 2555)

This 15Hz peak can be also amplitude noise.

To better calibrate, probably we should move slowly the pointing loop offset and see how much BS oplev signal response.

R&D (FilterCavity)
Print this report.
NaokiAritomi - 20:31, Thursday 03 June 2021 (2556)Get code to link to this report
FDS with CCFC around optimal detuning

In this measurement, PR pointing loop was used instead of BS pointing. The detuning fluctuation is still ~10Hz.

sqz_dB = 10.7;                    % produced SQZ (dB)

L_rt = 120e-6;                    % FC losses

L_inj = 0.31;                     % Injection losses 

L_ro = 0.24;                      % Readout losses

A0 = 0.05;                        % Squeezer/filter cavity mode mismatch

C0 = 0.05;                        % Squeezer/local oscillator mode mismatch

ERR_L =   1e-12;                  % Lock accuracy (m)

ERR_csi = 30e-3;                  % Phase noise (rad)

 

Note: In this calculation, shot noise level is assumed to be -133.2 dBVrms/rtHz, but actually it was -133.7 dBVrms/rtHz. So the result in this log is wrong...

Images attached to this report
2556_20210603133129_20210603ccfcfds.png
Comments related to this report
NaokiAritomi - 15:27, Friday 11 June 2021 (2568)

I analyzed again with correct shot noise level (-133.7dBVrms/rtHz) and 12% loss from visibility. The readout loss includes 12% loss from visibility, 2% loss from homodyne (dark noise, quantum efficiency, AR), and 20% loss from pick off BS.

sqz_dB = 11.8;                  % produced SQZ (dB)

L_rt = 120e-6;                  % FC losses

L_inj = 0.32;                   % Injection losses

L_ro = 0.31;                    % Readout losses

A0 = 0.05;                      % Squeezer/filter cavity mode mismatch

C0 = 0.06;                      % Squeezer/local oscillator mode mismatch

ERR_L =   1e-12;                % Lock accuracy (m)

ERR_csi = 30e-3;                % Phase noise (rad)

NaokiAritomi - 21:02, Monday 19 July 2021 (2631)

Yuhang and Michael fitted this data with mcmc. However, the detuning fluctuation is larger than that with least square... In this fit, the fit has been started from 60Hz and the detuning fluctuation could be smaller with higher fit starting frequency.

Left: mcmc (detuning: 50-68 Hz)

Right: least square (detuning: 49-61 Hz)

R&D (FilterCavity)
Print this report.
YuhangZhao - 18:59, Thursday 03 June 2021 (2555)Get code to link to this report
Filter cavity pointing loop control precision

Marc, Michael and Yuhang

The pointing loop control precision is an important parameter, which tells us the light beam spot moving range on filter cavity end mirror. The beam pointing loop is a very slow loop. To measure this beam pointing precision, we need to measure the error signal of this loop.

1. Calibration

We did calibration by sending a line for BS pitch/yaw. By overlapping BS oplev signal line and FC transmission PSD line, we can calibrate PSD pointing to the base of BS. The BS oplev calibration is from Eleonora elog1874.  Attached figure 1 and 2 show this overlap and the calibration factor of PSD.

2. Pointing precision

We took time series and spectrum of pointing loop error signal. By using calibration factor, we found our pointing precision for pitch is 4.04urad, for yaw is 10.10urad (from time series measurement). From spectrum measurement, pitch precision is 3.36urad, yaw precision is 11.44urad.

Remarks:

1. This measurement is done with PR and BS oplev open. Now the PR/BS oplevs are noisy above 10Hz, the closing of oplev loop may introduce noise but the resonance peak should be anyway reduced. It will be interesting to compare the pointing noise when PR/BS oplev is on/off.

2. This measurement is doen when BS pointing is closed. It has been found that pointing introduces noise for BS oplev when pointing loop acts on BS. So it will also be interesting to do the same measurement when pointing loop acts on PR.

3. Attached figure 5 and 6 show the comparison of BS oplev pitch/yaw and FC transmission PSD pitch/yaw. We can see PSD signal is higher than oplev after calibration, which means there are other noise sources are dominating PSD signal instead of BS pointing.

Images attached to this report
2555_20210603115608_pcal.png 2555_20210603115612_ycal.png 2555_20210603115806_pointingtime.png 2555_20210603115901_pointingspectra.png 2555_20210603120840_p.png 2555_20210603120843_y.png
Comments related to this report
YuhangZhao - 21:25, Thursday 03 June 2021 (2557)

This 15Hz peak can be also amplitude noise.

To better calibrate, probably we should move slowly the pointing loop offset and see how much BS oplev signal response.

YuhangZhao - 12:47, Saturday 05 June 2021 (2561)

Marc, Michael, and Yuhang

We have done a calibration for pointing loop with a new method. We move the locking point of pointing loop and check how much BS needs to compensate.

Pointing pitch:

we move pointing pitch, as attached figure 1 [1,0] subplot, from  -24 to -34 [counts]. Then we found BS pitch, as attached figure 1 [0,0] subplot, needs to move from 275.8 to 326.0 [counts] to compensate. Taking into account the calbration of oplev, we got  calibration factor for pointing loop on the base of BS.

The pointing precision was estimated by a RMS integral of pointing loop error signal spectra. We also found that high frequency spectrum can be better if we center beam on PSD, which is shown in attached figure 1 [0,1] and [1,1] subplots. However, the RMS of these two seneriaos are the same, which is reasonable since the dominating noise is at low frequency. In conclusion, we got pitch pointing precision as 0.43urad.

pitch pointing loop calibration factor 1.3 urad/count.

Pointing yaw:

We have done the pointing yaw calibration in the same manner with pointing pitch. The details can be found in attached figure 2. In conclusion, we got yaw pointing precision of 0.65urad.

yaw pointing loop calibration factor 1.5 urad/count.

Note: to take a quicker measurement, we have increased pointing loop gain by factors of 3 and 5 for pitch and yaw. So you can see the BS compensation finishes within 1 minute. We have also tested the spectrum of poiting pitch/yaw don't show difference when gains are increased.

R&D (FilterCavity)
Print this report.
MarcEisenmann - 17:55, Thursday 03 June 2021 (2554)Get code to link to this report
Comparison of BS and PR pointing

I compared the BS and PR pitch and yaw oplev while either closing the pointing loop on BS or on PR.

It seems that closing the loop on BS is introducing noise on BS pitch and yaw above ~4Hz.

 On the other hand, the pointing loop closed on PR only slightly increases PR yaw noise between 1 and 6 Hz.

Therefore it seems better to close the pointing loop on PR from now on.

Images attached to this report
2554_20210603105520_bspitch.jpg 2554_20210603105525_bsyaw.jpg 2554_20210603105528_prpitch.jpg 2554_20210603105532_pryaw.jpg
R&D (FilterCavity)
Print this report.
MarcEisenmann - 17:31, Thursday 03 June 2021 (2553)Get code to link to this report
Oplev and AA SNR comparison

Today I sent 15 Hz line on input and end mirrors pitch and yaw to calibrate the AA signals.

The 4 attached figures show the comparison of Oplev signal with calibrated AA signals.

This line can also be used to estimate the SNR of both Oplev and AA signals.

  INPUT PITCH INPUT YAW END PITCH END YAW
Oplev 17 3 23 3
AA 47 11 54 6
Images attached to this report
2553_20210603103107_inputpitch.jpg 2553_20210603103112_inputyaw.jpg 2553_20210603103116_endpitch.jpg 2553_20210603103119_endyaw.jpg
R&D (FilterCavity)
Print this report.
MarcEisenmann - 00:24, Thursday 03 June 2021 (2552)Get code to link to this report
effect of OPO green back-scattering

Marc, Michael, Yuhang

Today we wanted to do 2 activities in parallel :

1 compare the oplev and AA snr

2 measure the OPO NL gain.

We locked the FC with all loops on green for activity 1 and locked OPO while sending 10 Hz line with 1 Vpp on GR phase shifter for activity 2.

We found out that this caused an increase of Oplev (especially end mirror) and AA noises level as shown in figure 1. The green and brown reference curves are without beam dump, the blue and red are with deam dump and have the expected noise level.

By moving a beam dump from in-between the GR phase shifter and the GRMC to just before the OPO we could remove this new noise.

Therefore it seems that the green back-scattered light is the culprit.

We'll do further check to understand the coupling path and mechanism of this noise.

Images attached to this report
2552_20210602172916_img20210603wa0002.jpg
R&D (FilterCavity)
Print this report.
MarcEisenmann - 00:20, Thursday 03 June 2021 (2551)Get code to link to this report
PR pointing loop

Marc, Michael, Yuhang

Today we added the PR pointing loop to medm.

It is basically a copy & paste of BS pointing loop except that we had to change the pitch gain sign.

We could close the loop and things seem stable.

On medm there are now 2 buttons to close pointing with feedback on either BS or PR.

However, as pointed in entry 2493 PR is drifting more than BS so closing the pointing loop on PR instead of BS should be useful for long term stability.

R&D (FilterCavity)
Print this report.
NaokiAritomi - 16:10, Wednesday 02 June 2021 (2550)Get code to link to this report
Comment to Filter cavity misalignment can cause FDS detuning change (Click here to view original report: 2540)

I calculated the IR misalignment effect on CCFC error signal in I phase.

As you can see, even if the IR mode matching changes between 90% and 100%, the zero crossing point of CCFC error signal (detuning) changes by only ~ 0.06*54 = 3 Hz. So this effect cannot explain ~10Hz FDS detuning fluctuation.

Images attached to this comment
2550_20210807170651_ccfcmismatchcorrect.png 2550_20210807170657_ccfcmismatchenlargecorrect.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 14:41, Wednesday 02 June 2021 (2549)Get code to link to this report
A proposal to use Bayesian method to evaluate the cavity detuning information from FDS measurement

The Bayesian method to evaluate parameter in a function is a well-known prevalenty used method for parameter estimation in many research of fields. (such as gravitational wave detector signal analysis) You can check from this link, they did a simple demonstration that Bayesian method gives a more accurate parameter estimation. In our experiment, we are trying to fit the FDS measurement result to FDS degradation model to get information of cavity detuning and homodyne angle. To achieve this goal, we were using a least square curve fit method but the error of many parameters were not considered. Therefore, to better evaluate the filter cavity detuning information, I would propose to use Bayesian method.

To do Bayesian estimation, there is a package called 'emcee' developed in python environment. The method to do this Bayesian estimation is called 'MCMC'. To use this package, we need to move the FDS degradation function from matlab to python. I did this based on the FDS code provided from Eleonora. To make sure the python function I wrote is correct, I did the comparison of python and matlab results as the  attached figure 1. I found the python code I wrote gives quite the same result with Eleonora code.

Then I made a preliminary run of the mcmc code I wrote. (It was taking ~30 hours, but can be reduced if I use parallel calculation) Based on the result of MCMC, I made a violin plot of the cavity detuning fit result estimation, as attached figure 2.

I would like to do this analysis for the future measurement of FDS.

Images attached to this report
2549_20210602073723_fdscomp.png 2549_20210602100432_violin.png
R&D (FilterCavity)
Print this report.
MarcEisenmann - 14:36, Wednesday 02 June 2021 (2548)Get code to link to this report
preliminary QPD holder design

Using Inventor 2015 I tried to design the holder for KAGRA QPDs that will be used for all our OpLev sensors.

Figures 1 and 2 show the 2 parts I'm forseeing to use. Basically (as in figure 1)  a vertical spacer to mount the QPD board using 4 screws, a long hole to use a L to fix to a translation stage and 2 holes on top to fix the 15pin D sub connector.

Figure 2 shows the 15 pins D sub holder.

The main point is that there will not be vertical or horizontal translation stage (similar to current situation). I'm also planning to put a laser line filter on the translation stage along the beam axis.

If this preliminary design is fine, I'll translate it into documents usable by manufacturer.

Images attached to this report
2548_20210602073645_spacer.png 2548_20210602073649_dsubholder.png
R&D (FilterCavity)
Print this report.
MarcEisenmann - 14:31, Wednesday 02 June 2021 (2547)Get code to link to this report
unlocks and rack ground trouble ?

Aritomi, Marc, Michael, Yuhang

 

Yesterday during the work on CCFC, we found out that the FC can be unlocked if we touch some cable of the rack or some ground of mixers also connected to the rack.

The rack power supply ground is connected to tama ground. Using a powermeter we checked the voltage between the power supply ground and the ground cable and found that it was zero...

We might have to investigate directly on the rack.

Also we found out that even if the signal generator is turned off, if it is connected to some voltage driver it might introduce noise and cause some unlocks.

R&D (FilterCavity)
Print this report.
NaokiAritomi - 20:35, Tuesday 01 June 2021 (2546)Get code to link to this report
FDS with CCFC on 20210601

Although the locking accuracy is 1.8Hz with CCFC, the FDS detuning fluctuation is ~10Hz even with CCFC/Z correction/pointing/AA. The possible reasons are parameter estimation error and IR misalignment change and FC macroscopic length change.

sqz_dB = 10.5;                    % produced SQZ (dB)

L_rt = 120e-6;                    % FC losses

L_inj = 0.31;                     % Injection losses 

L_ro = 0.24;                      % Readout losses

A0 = 0.05;                        % Squeezed field/filter cavity mode mismatch

C0 = 0.05;                        % Squeezed field/local oscillator mode mismatch

ERR_L =   1e-12;                  % Lock accuracy (m)

ERR_csi = 30e-3;                  % Phase noise (rad)

Note: In this calculation, shot noise level is assumed to be -133.2 dBVrms/rtHz, but actually it may not be true. So the result in this log could be wrong.

Images attached to this report
2546_20210601133537_20210601ccfcfds.png 2546_20210601143736_20210601lockingaccuracy.png
R&D (FilterCavity)
Print this report.
MarcEisenmann - 10:08, Tuesday 01 June 2021 (2545)Get code to link to this report
AA INPUT YAW transfer function

All AA filters are 'DC_damp2' with an additional gain of 0.002 for yaw and 0.005 for pitch.

I plotted as an example in the figure 1 both OLTF and filter of AA input yaw. But similar results for all other dofs.

The right  column shows the product of the OMTF with the associated filter.

It can be seen that the gain never reach 1.... This might be due to poor coherence during the measurement (even if it is not possible to drastically increase the excitation while keeping the FC locked).

Another possibility to do this measurement could be to estimate Type-C suspension TF from simulation and use a single line excitation to estimate the WFS gain.

Images attached to this report
2545_20210601030627_aainy.jpg
R&D (FilterCavity)
Print this report.
YuhangZhao - 12:37, Sunday 30 May 2021 (2544)Get code to link to this report
A Monte-carlo estimation of FDS cavity detuning and homodyne angle (comparison with least square curve fit)

We have seen detuning change more than we expect, such as elog 2512 and elog 2537. In elog 2512, we expect detuning change less than ~15Hz, but we observed detuning change of ~50Hz. In elog 2537, according to the alignment change calculated in elog2540, we expect detuning change of ~3Hz, but we observed detuning change of ~10Hz.

To understand in more detail why this can happen, we take into account the errors of other degradation parameters (shortly DP) (squeezing level, RTL, mode matching, optical losses, phase noise, locking accuracy) and use Monte-carlo estimation to see how the fit result changes. In this entry, I used data of one curve from elog2512, but the same calculation can be applied to other data. The code used in this entry is based on Eleonora's code.

From least square curve fit, the expectation and standard deviation are estimated by giving fixed DPs. The result is angle 11.22+/-0.13,  detuning 105.09+/-0.54.

The Monte-carlo estimation gives expectation and std based on random chosen of DPs within normrnd(mean,std). The means of DP are chosen as the same with least square curve fit, while std is chosen as indicated in PRL paper. This means that, for one calculation, 8 DPs are chosen randomly while cavity detuning and homodyne angle are left free, then matlab uses least square method to give a fit of the FDS measurement and gives center values of detuning and homodyne angle. After calculating for 1000 times, we have 1000 center values for [cavity detuning, homodyne angle], which took 1.5 hours. This result is plotted as two histgrams as the attached figrue.This gives result of angle 11.22 +/- 0.35, detuning 105.04 +/- 1.18.

We can see basically the fitting error becomes about two times larger.

Images attached to this report
2544_20210530053742_fdsmontcarol2.png
R&D (FilterCavity)
Print this report.
NaokiAritomi - 20:53, Friday 28 May 2021 (2543)Get code to link to this report
Comment to Filter cavity misalignment can cause FDS detuning change (Click here to view original report: 2540)

The CCFC error signal you analyzed is Q phase signal which is not used for CCFC lock. How about the detuning change with I phase?

R&D (FilterCavity)
Print this report.
NaokiAritomi - 20:24, Friday 28 May 2021 (2542)Get code to link to this report
OPO lock and FC lock problem

[Aritomi, Yuhang, Michael]

Today we found that there was a 250Hz noise in CCFC signal and this noise came from low UGF OPO lock due to OPO demodulation phase change. After reloading the DDS1, this problem was solved.

After that, we found that FC lock was unstable even when Z correction, pointing, AA were engaged. In the end, FC could not be locked at all. We will investigate it next week.

KAGRA MIR (Absorption)
Print this report.
MarcEisenmann - 18:42, Friday 28 May 2021 (2541)Get code to link to this report
preparation of KAGRA spare viewport characterization

Today I brought the KAGRA spare viewport that was sent together with the 2 dirty ETMY viewports.

It seems to be 10 cm diameter and 1 cm thick.

I tried to install it inside the holder for the shinkosha evaluation plate (similar thickness) BUT

- only one stabilizing screw can be used making me afraid that the viewport might move during a measurement

- from the lowest point of the mirror up to ~3.5 cm will be hidden by the holder.

I guess a possible quick fix could be to buy ~6cm stabilizing screw and use the TAMA size holder or drill new holes in the SHINKOSHA holder to move the screws and metallic rode to a good position.

Images attached to this report
2541_20210528114241_img20210528182501.jpg
R&D (FilterCavity)
Print this report.
YuhangZhao - 12:23, Friday 28 May 2021 (2540)Get code to link to this report
Filter cavity misalignment can cause FDS detuning change

In elog2187, we measured FDS with CCFC loop locked. Meanwhile, there were no GR automatic alignment (AA) and input mirror feed back (InputFB). And we have seen detuning changed by about 10Hz, which should not happen since CCFC works to remove the detuning change with precision of 1Hz (could be a bit worse in elog2187). I have thought about this in more detail, and I found misalignment can impact on CCFC lock.

I have a code Aritomi-san provided about CCFC error signal calculation. By using this code, as elog2300, I added mode matching influence for this error signal and found the shape change of this signal, which was confirmed with experiment. I made this simulation again with mode matching level of 100%, 95%(our current situation), and 90%. The simulation result is shown in the attached figure (figure 1 is the zoom in of figure 2). We can see that the CCFC error signal zero crossing point changes with different mode matching level. Let's remind that when CCFC is used to lock filter cavity, we lock filter cavity to the zero point of CCFC error signal. Since CCFC zero crossing point changes with mode matching level, a misalignment for squeezing field will translate into FDS detuning change.

Attached figures show zero crossing point changes from 1.954 to 1.895, which are normalized by detuning frequency 54Hz. Therefore, this corresponds to a frequency change of 3.2Hz. Without automatic alignment, and considering the experience of our mirror suspension system change, this misalignment induces detuning change and prevents us from the goal of 1Hz detuning stabilization. Even with GR automatic alignment, the alignment is actually fluctuating and results in ~95% misalignment, which should introduce already 3.2Hz detuning change.

To achieve really detuning change less than 1Hz, IR automatic alignment will be necessary!

Images attached to this report
2540_20210528052327_mm.png 2540_20210528052331_zoomout.png
Comments related to this report
NaokiAritomi - 20:53, Friday 28 May 2021 (2543)

The CCFC error signal you analyzed is Q phase signal which is not used for CCFC lock. How about the detuning change with I phase?

NaokiAritomi - 16:10, Wednesday 02 June 2021 (2550)

I calculated the IR misalignment effect on CCFC error signal in I phase.

As you can see, even if the IR mode matching changes between 90% and 100%, the zero crossing point of CCFC error signal (detuning) changes by only ~ 0.06*54 = 3 Hz. So this effect cannot explain ~10Hz FDS detuning fluctuation.

R&D (FilterCavity)
Print this report.
MarcEisenmann - 12:20, Friday 28 May 2021 (2539)Get code to link to this report
Pointing loop OMTF

On Thursday morning I measured the opto-mechanical transfer function of the pointing loop with FC locked with all loops.

For BS pitch the amplitude was 9000 and BS yaw 3000 (higher would cause unlock).

Results are presented in figure 1 and 2.

Images attached to this report
2539_20210528090123_pointbsp.jpg 2539_20210528090130_pointbsy.jpg
R&D (FilterCavity)
Print this report.
MarcEisenmann - 12:16, Friday 28 May 2021 (2538)Get code to link to this report
AA OMTF and QPD SNR

Marc, Michael, Yuhang

On wednesday morning we started the AA characterization.

First, we measured the SNR of one QPD segment (here QPD1_I1) but similar results are expected for other segments.

You can see in figure 1 that we have reasonable SNR up to about 100 Hz.

Then we measured the input opto-mechanical transfer function by injecting white noise in input pitch (amplitude 9000) and yaw (amplitude 6000) and checking the signal reconstructed by the AA.

Note that to make these measurements with diagui we had to close the mirror damp loops.

The results are presented in figure 2 and 3.

Then when we tried to inject noise to end we unlocked the FC.

Actually, even if the damp loops are not used (gain to 0), there were several filters and large offsets that caused issues.

So on Thursday morning I repeated these measurements for end mirror  with identical amplitude without particular troubles.

Next step is to combine these measurements with the filter that we are using to check the bandwidth, UGF, phase margin to see if we can improve the AA filter.

Images attached to this report
2538_20210528051133_qpdsnr.jpg 2538_20210528090036_aainpomtf.jpg 2538_20210528090044_aainyomtf.jpg 2538_20210528090049_aaendpomtf.jpg 2538_20210528090056_aaendyomtf.jpg