LOG-IN
Displaying reports 1101-1120 of 3032.Go to page Start 52 53 54 55 56 57 58 59 60 End
R&D (FilterCavity)
Print this report.
YuhangZhao - 16:01, Friday 30 October 2020 (2256)Get code to link to this report
Input mirror pitch DC output is reaching maximum (picomotor couldn't be moved to offload this DC ouput)

Today, when I align filter cavity, I found the output of Input pitch is very large. As shown in the first attached figure, the H3 coil has an output of 30,000. This is reaching the maximum of coil.

So I tried to offload this value with picomotor. However, there is an error coming out when I use labview to move picomotor. The error is shown in the attached figure 1. To fix this problem, I did following check:

  1. We tried to move PR picomotor, which worked. Therefore, the Labview should work well. And the network connection of the old PC should be also fine.
  2. We checked the ethernet cable connection to the picomotor box. But the cable is connected to a high cable (as shown in the attached figure 2). So it is not very easy to check if the cable is correct or not. But anyway, this cable is connected.
  3. We also tried to plug in and out the power cable for picomotor box, which didn't solve the problem.
  4. We checked also the IP address of picomotor box, which is consistent with the one used in Labview.

However, the picomotor still didn't work. I have already sent Takahashi-san an email to ask how to solve this problem.

Images attached to this report
2256_20201030080141_wxcamera1604035737498.jpg 2256_20201030080152_wxcamera1604035543598.jpg
Comments related to this report
YuhangZhao - 17:27, Friday 30 October 2020 (2257)

The problem is solved by using directly a long ethernet cable between computer and picomotor box.

R&D (FilterCavity)
Print this report.
YuhangZhao - 16:27, Monday 26 October 2020 (2255)Get code to link to this report
Comment to Comparison of AA/oplev signal (AA loop open/FC aligned) (Click here to view original report: 2245)

The measurement is the same with the last comparison of AA/oplev except for that the PR/BS local control is off.

But even in this case, the AA signal is still higher than oplev signal.

Images attached to this comment
2255_20201026082841_aaoplevcomp.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 16:05, Monday 26 October 2020 (2254)Get code to link to this report
Check the coherence of PR/BS oplev signal and AA diagonalized signal (no excitation) (PR/BS local control closed)

This coherence check was done between PR/BS oplev singal and AA diagonalized signal. Note that there is no excitation sent to PR/BS, but the PR/BS local control loop was closed.

Note: blue curves are PR/BS local control open, red curves are PR/BS local control closed.

We could see a strong coherence between PR pitch/yaw oplev signal and AA.

Therefore, the PR local control seems to be introducing noise in pitch/yaw from 10 to several tens of Hz.

Images attached to this report
2254_20201026080635_bspnoexc2.png 2254_20201026080640_bsynoexc2.png 2254_20201026080648_prpnoexc2.png 2254_20201026080656_prynoexc2.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 14:35, Monday 26 October 2020 (2253)Get code to link to this report
Check the coherence of PR/BS oplev signal and AA diagonalized signal (no excitation) (no PR/BS local control)

This coherence check was done between PR/BS oplev singal and AA diagonalized signal. Note that there is no excitation sent to PR/BS, the PR/BS local control loop was open.

It can be seen that there is almost no coherence above 10Hz. I think this is also reasonable, because PR/BS motion at high frequency should be similar.

Images attached to this report
2253_20201026063859_bspnoexc.png 2253_20201026063904_bsynoexc.png 2253_20201026063911_prpnoexc.png 2253_20201026063918_prynoexc.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 17:51, Thursday 22 October 2020 (2252)Get code to link to this report
The higher noise level seen from AA seems to be from PR/BS

As reported in elog2245, the AA noise level is in general higher than the noise of oplev from roughly 10Hz to 100Hz (looking at all Input/End pitch/yaw). This noise is suspected to come from PR/BS motion.

Therefore, the coherence check between PR/BS pitch/yaw excitation and AA signal was done. The result is shown in the attached figure 1-4. It can be seen that:

1. Compared with BS pitch excitation, all AA singals have high coherence between 10 and ~30Hz. (Fig 1)

2. Compared with BS yaw excitation, Input yaw shows the most coherence between several Hz to ~30Hz. (Fig 2)

3. Compared with PR pitch excitation, all AA signals have high coherence between ~30Hz to 100Hz. (Fig 3)

4. Compared with PR yaw excitation, Input yaw shows the most coherence between several Hz to ~30Hz. (Fig 4)

Besides, the AA signal with PR/BS local control loop open was also checked. The result is shown in the attached figure 5. It is clear that, the noise floor from ~10Hz to 100Hz becomes generaly lower. But there is no difference in End mirror yaw.

Images attached to this report
2252_20201022105221_coherencebsp.png 2252_20201022105226_coherencebsy.png 2252_20201022105231_coherenceprp.png 2252_20201022105237_coherencepry.png 2252_20201022105311_00.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 11:06, Thursday 22 October 2020 (2251)Get code to link to this report
Comment to The modification done for simulink file k1fds (Click here to view original report: 2248)

Later on, I found that all the filters disappear in foton.

Eleonora checked that we have archive file in the directory '/opt/rtcds/kamioka/k1/chans/filter_archive/k1fds'. The file used in foton is '/opt/rtcds/kamioka/k1/chans/K1FDS.txt'.

Then Shoda-san helped to check them. 'ls /opt/rtcds/kamioka/k1/chans/filter_archive/k1fds -all' was used to check the date of these files. The latest archived file in that directory was found to be 'K1FDS_201021_164656.txt' However, it was also shown in the terminal that this latest file has size of 3075 (usual size is 107155). We opened the file and found that the latest archived file is actually empty. In the end, we found  'K1FDS_201017_210326.txt' should be the latest useable file.

By using 'cp /opt/rtcds/kamioka/k1/chans/filter_archive/k1fds/K1FDS_201017_210326.txt /opt/rtcds/kamioka/k1/chans/K1FDS.txt', the filters are copied to foton. Now filters also work well!

R&D (FilterCavity)
Print this report.
YuhangZhao - 20:46, Wednesday 21 October 2020 (2250)Get code to link to this report
The difference of 'Gaussian' and 'Uniform' noise in Diaggui

When the transfer function is measured in diaggui, several choice could be used for measurement. Especially, when performing FFT measurement, there is 'Gaussian' and 'uniform' noise to be chosen. I checked today what is the difference of them.

I used Diaggui to generate these two noise as shown in the first figure. Then the spectrum of them was measured and shown in attached figure 2.

The conclusion is that both of them are white noise. But the 'Gaussian' noise is about twice the amplitude of 'uniform'.

Images attached to this report
2250_20201021134732_57.png 2250_20201021134738_41.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 20:24, Wednesday 21 October 2020 (2249)Get code to link to this report
Comment to The modification done for simulink file k1fds (Click here to view original report: 2248)

It was figured out that there were two problems happened at the same time and caused this problem.

1. Instead of using 'make install-k1fds', I was using 'make install -k1fds'. By using correct command, the problem was solved.

2. One of the directory was full (/opt/rtcds/kamioka/k1/target/fb/log/old was as large as 18GB) . Then I couldn't make k1fds. By using 'sudo rm -r old', this problem was solved.

Tips:

To check if k1fds is running, command 'lsmod' could be used. After using it, if you see the name k1fds is listed on the left side in a certain column, it means k1fds is running.

To check the space used by different directory, 'du -h --max-depth=2 .' should be used.

R&D (FilterCavity)
Print this report.
YuhangZhao - 16:34, Wednesday 21 October 2020 (2248)Get code to link to this report
The modification done for simulink file k1fds

Shoda and Yuhang

I found that the driving matrix of AA had large coupling last Friday. So I was thinking to make the driving matrix not seperate in pitch and yaw. It means to make the 2*2 matrix be a 2*4 matrix. For example, to control the yaw motion, there is not only signal coming from yaw but also from pitch.

Then I asked Shoda-san to modify the k1fds code. She helped me make the modification described as above.

But then, later on last Friday. By improving the driving matrix index with the separation of pitch and yaw, the pitch/yaw coupling becomes much better. So I decided by myself to modify it back.

However, after I modified it back. I found I couldn't make k1fds. The problem showed up as

gzip: stdout: Np space left on device.

make: ***[k1fds] Error 1

However, although this issue reased up, I was able to use control loops. So I didn't care about that.

Then, the day after, I found filters in foton disapeared. 

Comments related to this report
YuhangZhao - 20:24, Wednesday 21 October 2020 (2249)

It was figured out that there were two problems happened at the same time and caused this problem.

1. Instead of using 'make install-k1fds', I was using 'make install -k1fds'. By using correct command, the problem was solved.

2. One of the directory was full (/opt/rtcds/kamioka/k1/target/fb/log/old was as large as 18GB) . Then I couldn't make k1fds. By using 'sudo rm -r old', this problem was solved.

Tips:

To check if k1fds is running, command 'lsmod' could be used. After using it, if you see the name k1fds is listed on the left side in a certain column, it means k1fds is running.

To check the space used by different directory, 'du -h --max-depth=2 .' should be used.

YuhangZhao - 11:06, Thursday 22 October 2020 (2251)

Later on, I found that all the filters disappear in foton.

Eleonora checked that we have archive file in the directory '/opt/rtcds/kamioka/k1/chans/filter_archive/k1fds'. The file used in foton is '/opt/rtcds/kamioka/k1/chans/K1FDS.txt'.

Then Shoda-san helped to check them. 'ls /opt/rtcds/kamioka/k1/chans/filter_archive/k1fds -all' was used to check the date of these files. The latest archived file in that directory was found to be 'K1FDS_201021_164656.txt' However, it was also shown in the terminal that this latest file has size of 3075 (usual size is 107155). We opened the file and found that the latest archived file is actually empty. In the end, we found  'K1FDS_201017_210326.txt' should be the latest useable file.

By using 'cp /opt/rtcds/kamioka/k1/chans/filter_archive/k1fds/K1FDS_201017_210326.txt /opt/rtcds/kamioka/k1/chans/K1FDS.txt', the filters are copied to foton. Now filters also work well!

R&D (FilterCavity)
Print this report.
YuhangZhao - 08:32, Wednesday 21 October 2020 (2247)Get code to link to this report
DGS problem about k1fds doesn't work

Eleonora and Yuhang

Firstly, we found that all the filters disappeared in foton (as shown in the attached figure 1).

Then we tried to restart standalone computer. However, after that, k1fds stopped working (as shown in the attached figure 2).

At the same time, we found that by using command 'df', /dev/sda1 shows 100% used (as shown in the attahed figure 3).

Eleonora tried to ssh standalone, and used command 'lsmod', and found there was no k1fds. She tried command 'startk1fds'. But it didn't work (see attached figure 4).

So probably the problem is connected with the full of /dev/sda1.

Images attached to this report
2247_20201021013039_22.png 2247_20201021013052_21.png 2247_20201021013107_04.png 2247_20201021013213_01.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 16:27, Tuesday 20 October 2020 (2246)Get code to link to this report
Comparison of input/end oplev signal when AA loop is on/off

To check how AA affect input/end mirrors, I checked their oplev signals when AA loop is on/off.

From the measurement, the yaw motion of input/end mirrors is actually increased by AA loop.

Images attached to this report
2246_20201020092821_oplevaaonoff.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 14:19, Tuesday 20 October 2020 (2245)Get code to link to this report
Comparison of AA/oplev signal (AA loop open/FC aligned)

0. Note that PR/BS local control is closed in this case.

1. The noise spectrum of AA is higher than oplev (from 10 to 100Hz)

2. The input pitch coupling to input yaw is visible.

Images attached to this report
2245_20201020071947_aaoplev.png
Comments related to this report
YuhangZhao - 16:27, Monday 26 October 2020 (2255)

The measurement is the same with the last comparison of AA/oplev except for that the PR/BS local control is off.

But even in this case, the AA signal is still higher than oplev signal.

R&D (FilterCavity)
Print this report.
YuhangZhao - 12:50, Tuesday 20 October 2020 (2243)Get code to link to this report
Calibration of AA spectrum (Input/End pitch/yaw) with oplev

To compare oplev and AA spectrum, the first step is to calibrate both of them. The calibration is done as follows:

1. Calibrate oplev signal. The oplev signal calibration method was developed by Eleonora and written in elog1874

2. Clibrate AA signal. The 4Hz sine wave was sent to Input/End pitch/yaw. By adjusting calibration factor of AA signal, AA's 4Hz peak was matched to oplev's peak. Then the calibration of AA signal was decided. The comparison is shown in the attached four figures.

  oplev AA
input pitch 0.038 0.018
input yaw 0.027 0.013
end pitch 0.026 0.017
end yaw 0.018 0.013

unit: urad/counts

Images attached to this report
2243_20201020071114_ipcali.png 2243_20201020071120_iycali.png 2243_20201020071127_epcali.png 2243_20201020071132_eycali.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 16:40, Monday 19 October 2020 (2242)Get code to link to this report
Diagonalized sensing matrix coupling (test at 4Hz)

The first attached figure was the coupling (input pitch) situation before optimization.

The following figures show the coupling situation now.

Images attached to this report
2242_20201019093942_ipcoupling20201016.png 2242_20201019093948_ipcoupling20201019.png 2242_20201019093953_iycoupling20201019.png 2242_20201019094000_epcoupling20201019.png 2242_20201019094005_eycoupling20201019.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 23:40, Friday 16 October 2020 (2241)Get code to link to this report
New INPUT/END noise spectrum with AA loop (after diagonalization)

According to the suggestion of Raffaele, I checked the diagonalized sensing signal (driving signal). I found there are quite a lot of coupling between each DOF. Therefore, I optimized the invertion matrix. After that, I also increase the gain of each loop.

New driving matrix:

  WFS1 WFS2
input_p 1 -0.6
end_p 1 1.65
input_y

-1

0.8
end_y -1 -2

New gain:

input yaw: 10

input pitch: 8

end yaw: 10

end pitch: 12

The comparison of new spectrum and old one is shown in the attached figure. We could see:

1. The coupling is bascially not visible in the spectrum.

2. The control bandwidth is increased.

3. The AA helps to reduce input mirror pitch motion to 2urad. Reduce input mirror yaw motion to 1urad.

4. The AA helps to reduce end mirror pitch motion to 1.2urad. Reduce input mirror yaw motion to 0.8urad.

As we concived that the mirror angular motion results in the difficulty of mode matching, this situation maybe improved by the AA control.

Images attached to this report
2241_20201016164140_aaspec2.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 17:50, Friday 16 October 2020 (2240)Get code to link to this report
Use wavefront sensors to sense INPUT/END motion (w/wo AA, electronic noise)

Calibration factor: The calibration was done by sending 4Hz with 5urad expected motion (driving magnitude is shown in elog2216). (I didn't consider yet the transfer function of pitch/yaw. Since 4Hz is not far from resonance frequency, the pendulum effect is temporary neglected.) Beside, looking at the noise spectrums, at 4HZ, there is not the effect of AA loop. Then I check the peak value at 4Hz. After subtracting the offset (value at 4Hz without excitation), the value is divided by 5urad. Then I get calibration factor. I use it to calibrate the spectrum measured from wavefront sensor.

The measurement result is shown in the attached figure. (REF0,1,2,3: AA loop on. REF4,5,6,7: electronic noise. Others: AA loop off. )

1. From this measurement, End mirror is moving less than Input mirror.

2. The RMS motions of Input mirror reach about 7urad for both pitch/yaw.

3. The RMS motions of End mirror reach about 2urad for both pitch/yaw.

4. The spectrum is well above the sensor noise.

5. The control bandwidth situation could also be seen from this measurement. The control in yaw direction has larger bandwidth and reach about several Hertz. The control in pitch direction has smaller bandwidth, but also reach about 1Hz.

6. It seems that the coupling from pitch to yaw is not small. The peaks in pitch (around 8-9Hz) is visible also in yaw.

Images attached to this report
2240_20201016105201_aaspec.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 13:15, Wednesday 14 October 2020 (2239)Get code to link to this report
New measurement of AA loop transfer functions

The coherence in pitch direction is not very good in the last elog. Therefore, some new measurements were performed.

1. The first four figures are measured with gaussian noise excitation, resolution is 0.01Hz.

2. Figure 5 shows a measurement of END_yaw TF with uniform noise excitation. The measurement result is a bit different with guassian excitation.

3. I increase the input pitch gain from 0.3 to 2. The new TF is shown in figure 6.

Images attached to this report
2239_20201014061633_ip.png 2239_20201014061639_iy.png 2239_20201014061649_ep.png 2239_20201014061656_eygau.png 2239_20201014061703_eyuni.png 2239_20201014061709_ipg2.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 18:12, Tuesday 13 October 2020 (2238)Get code to link to this report
The transfer functions are measured again with fft method (gives more clear result at high frequency)

The transfer functions of AA loop was measured with swipe sine method and reported in elog2230. But the signal at high frequency was not quite clear. Therefore, Eleonora suggested me to measure with fft method. The excitations were uniform noise and sent to each degree of freedom, their amplitude are

Input_yaw 3000
Input_pitch 10000
End_yaw 2000
End_pitch 2000

Note that if the excitation is not large enough, the coherence between these two signals will be exactly 1 at almost all the frequencies.

The measurement result is shown in the attached figures.

Images attached to this report
2238_20201013111150_inputyaw.png 2238_20201013111155_inputpit.png 2238_20201013111202_endyaw.png 2238_20201013111209_endpit.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 17:46, Tuesday 13 October 2020 (2237)Get code to link to this report
some setting change after switching air-conditioner to warm up mode

The air conditioner was switch to warm up mode last week. After that, I found green injection direction was changed a lot. The green beam references on the PR/BS chamber are fine (as shown in the figure 1). But the green beam was quite far from good height on the first target in the arm (as shown in the figure 2 and 3).

Therefore, I checked the PR/BS oplev signals (as shown in the figure 4). From this figure, we see that mainly PR pitch was moved a lot. Additionally, BS pitch also moved in the direction. This movement is so large, so I used picomotor to recover PR position.  After recovering PR pitch, BS was moved up with oplev. With good alignment, the green beam on the first target is shown in the figure 5 and 6. However, after locking FC, the GR DC tra was found to be only around 3000.

I checked green power before AOM, it was only about 30mW, but the nominal value should be 52mW. So I changed SHG temperature from 3.096 to 3.068. Note that 3.068 makes SHG have a local maximum green output, which gives 52mW before AOM. The AOM modulation depth is 5.5dBm, which gives 14.5mW injected into FC.

Besides, recently we have SHG output oscillation problem. This is due to the gain of SHG servo is smaller than 2.25. After I put the SHG servo gain back to 2.25, oscillation disappeared.

Images attached to this report
2237_20201013105155_wechatimg25.jpeg 2237_20201013105207_wechatimg29.jpeg 2237_20201013105217_wechatimg31.jpeg 2237_20201013105233_wechatimg32.jpeg 2237_20201013105242_wechatimg28.jpeg 2237_20201013105250_wechatimg33.jpeg
R&D (FilterCavity)
Print this report.
NaokiAritomi - 20:06, Thursday 08 October 2020 (2236)Get code to link to this report
CCFC RF noise

[Aritomi, Yuhang]

We measured CCFC RF noise (before demodulation after amplification).

Setting of spectrum analyzer: RBW: 300kHz,VBW: 10kHz

We used 50:50 BS to pickoff CCFC error signal and pump green power is 42 mW.

Note that CCFC and CCFC FC unlock were measured with max hold while others are normal setting. I think that's the reason why the floor noise level in CCFC and CCFC unlock are a bit higher than TAMA PD noise level.

Images attached to this report
2236_20201008130626_ccfcrf20201008.png