Reports of 29304
MIF (General)
takafumi.ushiba - 18:42 Thursday 21 November 2024 (31721) Print this report
Comment to PRMI 3f lock acquisition and HANDOVER from ALS to IR became hard (31702)

I checked REFL51 and REFL135 dark offsets at several different timing (fig1:10/30, fig2:10/29, fig3:10/25).
Small jump can be seen in REFL51I signals but there seems no jump in the others.
Also, the jump is not so large compared to the drift.
So, it is likely that the dark offset change was due to the drift of the offset.

Images attached to this comment
MIF (Noise Budget)
kenta.tanaka - 18:12 Thursday 21 November 2024 (31719) Print this report
Noise budget campaign: CARM

We measued TFs from PDA1_RF45_I_ERR and CARM_SERVO_MIXER_DAQ_OUT which are in-loop sensors for CARM to the DARM displacement (CAL-CS_PROC_DARM_DISPLACEMENT), and also measured the TF from PDA3_RF45_I_ERR, which is an out-loop sensor for CARM to the DARM displacement when we excited CARM from CARM_SERVO_EXC_A_CALI. Fig.1 shows the results. (Note that, the unit of the TF from MIXER_DAQ_OUT to DARM is m/V, the others' unit is m/cnt).

Then, we projected the current spectra of MIXER_DAQ_OUT as the in-loop sensor and PDA3_RF45_I_ERR as the out-loop sensor in DARM sensitivity by using each TF. Fig.2 shows each projection, magenta is the projection from MIXER_DAQ_OUT, green is from PDA3_RF45_I_ERR. According to the magenta line, the current in-loop CARM noise seems not to limit the current sensitivity. Unfortunately, the current PDA3 output in high frequency region seems to be dominate by the other noise due to the low input power to PDA3.

Next, we projected the sensing noises of MIXER_DAQ_OUT and PDA3_RF45_I_ERR. We picked up each raw sensing noise spectrum which were measured by Ushiba-san (see the detail in klog31636) in /users/Commissioning/data/CARM/2024/1114/SPE_CARM-20dB_CMS_sensingnoise.xml. Fig. 3 shows the projected sensing noises using each TF, the orange line is the sensing noise of MIXER_DAQ. Then, I tried to compensated roughly the input power difference between the orange and the magenta. The input power when the orange was measured was 2988 cnts, and the power when the magenta was measured was 846 cnts. So I assumed this orange sensing noise is only shot noise (honestly, orange line seems to have a shape so this assumption is overspeaking), and devided the orange line by (2988/846)^(1/2) ~ 3^(1/2). The black line is divied one. If the current sensing noise is only shot noise, the current CARM noise is limited by the sensing noise. 

Images attached to this report
DetChar (General)
shoichi.oshino - 14:52 Thursday 21 November 2024 (31718) Print this report
Check Omicron process
I found that the the Omicron process was stopped due to the remaining cache file like klog 31553.
Therefore, I deleted the cache file for GPS segment 14151.
MIF (General)
shinji.miyoki - 13:47 Thursday 21 November 2024 (31717) Print this report
Comment to DAC noise evaluation for ETMX (31716)

Could you please explain Fig.4? It shows the reduction of displacement.

MIF (General)
takaaki.yokozawa - 13:25 Thursday 21 November 2024 (31716) Print this report
DAC noise evaluation for ETMX
I performed the noise budget of the DAC noise for ETMX by turned off(on) the de-whitening filters in coil driver.
ITMX TM 1 stage -> 0 stage (off)
ITMX IMH/IMV 0 stage -> 1 stage (on)
ITMX MNH/MNV 2 stage -> 0 stage (off)

Similar results with other Type-A suspensions, we can see the excess when we turned off the de-whitening filter for the TM and MNV as shown in Fig.1. and Fig.2.
MNH no significant excess as shown in Fig.3.

I noticed the IMH and IMV were not performed the de-whitening filter, so I checked the spectrum when I turned on the de-whtening filter, then the noise level can be reduced(around 40 Hz) when performed it to IMV.

I changed the LSC_LOCK guardian to add the de-whitening filter to IMH and IMV at the same timing when we turned on the de-whitening filter to MNH and MNV.
If you noticed some trouble, please remove the L2054 and L2055 from LSC_LOCK guardian.
ezca['VIS-ETMX_BIO_IMH_STATEREQ'] = 2
ezca['VIS-ETMX_BIO_IMV_STATEREQ'] = 2
Images attached to this report
Comments to this report:
shinji.miyoki - 13:47 Thursday 21 November 2024 (31717) Print this report

Could you please explain Fig.4? It shows the reduction of displacement.

MIF (General)
takafumi.ushiba - 13:05 Thursday 21 November 2024 (31715) Print this report
Comment to Power estimation at AS during lockloss (31696)

>Even the OMC resonance peak happens to align with the peak of the lock loss blast, the energy deposited on OMC PDs (total of two PDs) for 10 W input will be
>10 * 19 W * 50 usec = 9.5 mJ

If we consider the speed of scan (5ms), OMC psses on the resonance 3 times within FWHM (15ms).
Even in that case, obtained energy of PD is less than 9.5mJ * 3 = 28.5 mJ, which satisfy the requirement (< 30mJ).

VAC (General)
takahiro.yamamoto - 12:18 Thursday 21 November 2024 (31713) Print this report
Comment to Improvement of VAC notification guardian (31661)
Enabling alert didn't work well last night though the readout pressure value became lower than the threshold.
This was a bug occuring the case that the threshold and the value which is two steps smaller than the threshold had different digits.
(e.g. 1.1e-5 => 9.9e-6, 1.0e-5 => 9.8e-6, etc.)

I fixed this bug and now VAC_MON guardian runs with the fixed code.
We can confirm this code really works fine in the next evacuation time.
MIF (General)
tomotada.akutsu - 11:04 Thursday 21 November 2024 (31714) Print this report
Comment to Power estimation at AS during lockloss (31696)

Too consistent, isn't it...?

MIF (General)
yuta.michimura - 10:28 Thursday 21 November 2024 (31711) Print this report
Comment to Power estimation at AS during lockloss (31696)

The lock loss blast with a peak height of 19 W and FWHM of 15 msec gives integrated energy of roughly 19 W * 15 msec = 0.3 J.
Intra cavity power with 1 W input for each arm is Pcav = Pin * PRG * 4/T_ITM / 2 = 1 W * 15 * 4/0.4% / 2 = 7.5 kW.
This means that total energy stored in XY arms is Ecav*2 = Pcav * 2 * 2 * Larm / c = 0.3 J.
Amazingly consistent (see also JGW-T2416173).
To have less than 30 mJ at OMC PDs (total of two PDs) when the input power is 10 W, we need to reduce the OMC duty factor to less than 30 mJ / (0.3 J * 10) = 1%.
Continuously sweeping OMC with a triangular wave of peak-to-peak of 1 FSR gives (effective) duty factor of 1/Finesse = 1/800 = 0.125%.
So, sweep of 0.125 FSR peak-to-peak would be enough.
Using 100 Hz triangular wave, time to sweep the OMC resonance peak will be
1 / 100 Hz / 2 * (1/Finesse) / 0.125 = 50 usec
Even the OMC resonance peak happens to align with the peak of the lock loss blast, the energy deposited on OMC PDs (total of two PDs) for 10 W input will be
10 * 19 W * 50 usec = 9.5 mJ
This is smaller than the 30 mJ requirement. So, sweeping with 0.125 FSR peak-to-peak at 100 Hz will be good.

MIF (Noise Budget)
takaaki.yokozawa - 10:18 Thursday 21 November 2024 (31712) Print this report
DAC noise evaluation for ETMY
I performed the noise budget of the DAC noise for ETMY by turned off the de-whitening filters in coil driver.
ITMX TM 1 stage -> 0 stage
ITMX IMH/IMV 3 stage -> 0 stage
ITMX MNH/MNV 2 stage -> 0 stage

(Fig.1.)In case of the TM, we can see the excess in 50-110 Hz, but this excess is less than 10 times, so ETMY TM DAC noise may not limit the sensitivity, but there are possibility "sum of DAC noise of several suspensions" affect to the DARM sensitivity.
(Fig.2. - 4.)No significant excess were detected in case of the IMH, IMV and MNH, so the DAC noise effect would be much less than current DARM sensitivity.
(Fig.5.)In case of the MNV, we can see some excess in 10-100 Hz, but this excess is less than 100 times, so ETMY TM DAC noise may not limit the sensitivity, but there are possibility "sum of DAC noise of several suspensions" affect to the DARM sensitivity.
(Blue : current sensitivity Red : DAC de-whitening filter off for certain stage.)
Images attached to this report
MIF (Noise Budget)
takaaki.yokozawa - 9:37 Thursday 21 November 2024 (31710) Print this report
DAC noise evaluation for ITMY
I performed the noise budget of the DAC noise for ITMY by turned off the de-whitening filters in coil driver.
ITMY TM 1 stage -> 0 stage
ITMY IMH/IMV 3 stage -> 0 stage
ITMY MNH/MNV 2 stage -> 0 stage

(Fig.1.)In case of the TM, we can see the excess in 50-110 Hz, but this excess is less than 10 times, so ITMX TM DAC noise may not limit the sensitivity, but there are possibility "sum of DAC noise of several suspensions" affect to the DARM sensitivity.
(Fig.2., 3.)Someexcess were detected in case of the IMH, IMV around 50 Hz, but this excess is less than 1000 times
(Fig.4., 5.)In case of the MNH and MNV, we can see some excess in 10-100 Hz, but this excess is less than 100 times, so ITMX TM DAC noise may not limit the sensitivity, but there are possibility "sum of DAC noise of several suspensions" affect to the DARM sensitivity.
(Blue : current sensitivity Red : DAC de-whitening filter off for certain stage.)
Images attached to this report
MIF (Noise Budget)
takaaki.yokozawa - 9:34 Thursday 21 November 2024 (31708) Print this report
DAC noise evaluation for ITMX
I performed the noise budget of the DAC noise for ITMX by turned off the de-whitening filters in coil driver.
ITMX TM 1 stage -> 0 stage
ITMX IMH/IMV 3 stage -> 0 stage
ITMX MNH/MNV 2 stage -> 0 stage

(Fig.1.)In case of the TM, we can see the excess in 50-110 Hz, but this excess is less than 10 times, so ITMX TM DAC noise may not limit the sensitivity, but there are possibility "sum of DAC noise of several suspensions" affect to the DARM sensitivity.
(Fig.2. - 4.)No significant excess were detected in case of the IMH, IMV and MNH, so the DAC noise effect would be much less than current DARM sensitivity.
(Fig.5.)In case of the MNV, we can see some excess in 10-100 Hz, but this excess is less than 100 times, so ITMX TM DAC noise may not limit the sensitivity, but there are possibility "sum of DAC noise of several suspensions" affect to the DARM sensitivity.
(Blue : current sensitivity Red : DAC de-whitening filter off for certain stage.)
Images attached to this report
MIF (Noise Budget)
takaaki.yokozawa - 9:34 Thursday 21 November 2024 (31706) Print this report
DAC noise evaluation for PRM, PR2 and PR3
I performed the noise budget of the DAC noise for PRM, PR2 and PR3 by turned off the de-whitening filters in coil driver.
PRM, PR2, PR3 TM 1 stage -> 0 stage
PRM, PR2, PR3 IMV/IMH 3 stage -> 0 stage

No significant change was detected in DARM sensitivity when we turned off the de-whitening filter.
So, the DAC noise from Type-Bp suspension was lower than 1/10 in current DARM sensitivity.

All results were placed in
https://dac.icrr.u-tokyo.ac.jp/KAGRA/DAWG/Detchar/klog/klog31706
(Blue : current sensitivity Red : DAC de-whitening filter off for certain stage.)
MIF (Noise Budget)
takaaki.yokozawa - 9:33 Thursday 21 November 2024 (31707) Print this report
DAC noise evaluation for BS, SR2 and SR3
I performed the noise budget of the DAC noise for BS, SR2 and SR3 by turned off the de-whitening filters in coil driver.
BS, SR2, SR3 TM 1 stage -> 0 stage
BS, SR2, SR3 IMV/IMH 2 stage -> 0 stage

No significant change was detected in DARM sensitivity when we turned off the de-whitening filter.
So, the DAC noise from Type-B suspension was lower than 1/10 in current DARM sensitivity.

All results were placed in
https://dac.icrr.u-tokyo.ac.jp/KAGRA/DAWG/Detchar/klog/klog31707
(Blue : current sensitivity Red : DAC de-whitening filter off for certain stage.)
VIS (EY)
ryutaro.takahashi - 9:28 Thursday 21 November 2024 (31709) Print this report
Comment to Drift of BF GAS (27941)

I changed the setpoint of the heater from 26.0° to 25.0° at 9:26 JST.

MIF (General)
takafumi.ushiba - 9:12 Thursday 21 November 2024 (31705) Print this report
Comment to Power estimation at AS during lockloss (31696)

I checked the signals last night and confirmed that OMMT2T trans DC PD was not saturated when lockloss happened.
Figure 1-3 shows the signals when the lockloss happened in this morning.
The first peak power is about 19W and the second is about 4W (fig1).
FWHM of the first peak and second is about 15ms (fig2) and 5ms (fig3), respectively.

After achieving PRFPMI_RF_LOCKED, maximum power at AS is about 500mW (fig4), so if we set the power treshold at AS as 1W or something, the trigger seems to work only when lockloss happens.
In addition, speed of power increase from 1W to 19W is about 20ms (fig5).

Images attached to this comment
MIF (Noise Budget)
takaaki.yokozawa - 8:49 Thursday 21 November 2024 (31704) Print this report
Noise budget MICH, PRCL and ISS
Based on the noise budget 2023 (klog25665), I measured the TF from each DoF(or out-of-loop PD) to DARM and projected to DARM sensitivity.

Fig.1. TF result MICH -> DARM (blue : 2023 red : 2024)
Fig.2. TF result PRCL -> DARM (blue : 2023 red : 2024)
Fig.3. TF result ISS out-loop-PD -> DARM (blue : 2023 red : 2024)
Fig.4. Noise projection result to DARM
Images attached to this report
CAL (XPcal)
dan.chen - 6:26 Thursday 21 November 2024 (31703) Print this report
Comment to Periodic integration sphere calibration for XPcal (31697)

Before this work, I checked the Pcal-X beam positions on the ETMX, and adjusted a little.
What I used are PCAL_EX2 picos.

Pico movment: 

  • PCAL_EX2 pico 1: +50
  • PCAL_EX2 pico 2: +100
  • PCAL_EX2 pico 4: +50

Beam positions on the ETMX changed by about 2mm:
Before ([0,0] means the design position.): Fig 1 = TCam_ETMX_00111_2024_1120_051540_fitting_comp.png

  • Pcal beam position (path1) [mm]: [3.91584, 2.40329]
  • Pcal beam position (path2) [mm]: [2.75383, 3.67881]

After: Fig 2 = TCam_ETMX_00111_2024_1120_054412_fitting_comp.png

  • Pcal beam position (path1) [mm]:  [3.98096, -0.55771]
  • Pcal beam position (path2) [mm]:  [2.67615, 1.67651]

During calibration at the end station, we found the beams were slightly(2-3mm) shifted from the centre on the RxPD.
Today, we proceeded the calibration without making the adjustment. The impact on the calibration results appears to be limited, but it may need to be adjusted in the future.

Images attached to this comment
MIF (General)
kenta.tanaka - 21:59 Wednesday 20 November 2024 (31702) Print this report
PRMI 3f lock acquisition and HANDOVER from ALS to IR became hard

Yokozawa, Michimura, Ushiba, Tanaka

This morning, Yokozawa-san found PRMI kicked when its 3f lock acquisition. We found that the phasing of RF51 seemed to be bad when the demod. phase value was 60 deg. So we rotated the phase to maximize the Q output when we excited MICH. The value after the rotation was 145 deg.

Next, HANDOVER from ALS to IR got hard because the glitch in MICH error signal when IR beam flashed in the arm cavity became large. This issue is the same as the one in klog30912. So we need to make the demod. phase worse in order to reduce the glitch

On the other hand, Michimura-san found that the RF51 and RF135 signals had dark offsets (~ several cnts). We subtracted them (fig.1) and then, the PRMI could locked smoothly even though the demod. phase of RF51 was 60 deg. HANDOVER also succeeded with this demod. phase. 

## NOTE

I also subtracted the dark offset of AS_PDA1_RF17_{I,Q}, REFL_PDA1_RF45_{I,Q}, POP_PDA1_RF{17,45}_{I,Q}, POP_PDA2_RF90_{I,Q} manually.

Images attached to this report
Comments to this report:
takafumi.ushiba - 18:42 Thursday 21 November 2024 (31721) Print this report

I checked REFL51 and REFL135 dark offsets at several different timing (fig1:10/30, fig2:10/29, fig3:10/25).
Small jump can be seen in REFL51I signals but there seems no jump in the others.
Also, the jump is not so large compared to the drift.
So, it is likely that the dark offset change was due to the drift of the offset.

Images attached to this comment
DetChar (General)
nami.uchikata - 17:43 Wednesday 20 November 2024 (31701) Print this report
Update segment lists and cache files during power outage
I have updated segment lists for the dates when kmst2 was down on Nov. 11th and 12th due to the power outage.
I have also updated incomplete cache files 14154.ffl/cache and 14155.ffl/cache, and segment lists of the relating date.
DGS (Test bench)
shoichi.oshino - 17:36 Wednesday 20 November 2024 (31700) Print this report
Installed k1nfs0 for the test bench
I installed k1nfs0 for the test bench system.

This k1nfs0 uses a NAS server.
It uses four 6TB HDDs and is configured in RAID 6.
LIGO mounts the k1boot opt directory with NFS.
We will test this configuration on the test bench.
The test bench will create the system many times, so if the model files can be used via NFS, it will reduce the time to copy them.
FCL (Electricity)
masakazu.aoumi - 16:35 Wednesday 20 November 2024 (31699) Print this report
Comment to Crackings of the utility pole for KAGRA power cable (27051)
2024/11/20 PM

Sinkodenki

new electric pole(a) The clay walls were repaired with clay and dug to a certain depth by hand to erect a telephone pole.
Put in soil and gravel on the 22th to consolidate.

new electric pole(b) Cleared the ground for concrete pouring.

new electric pole(c) Cleared the ground for concrete pouring.
Images attached to this comment
MIF (General)
takafumi.ushiba - 16:01 Wednesday 20 November 2024 (31698) Print this report
Comment to PAD installation at OMMT2 trans (31684)

[Tanaka, Ushiba]

We reduced OMMT2T PDA1 gain from 70dB to 30dB.
After that, dark noise was measured and subtracted (fig1 shows the signals when IMC was locked).
Also, calibration factor was increased by a factor of 100.

Images attached to this comment
CAL (XPcal)
dan.chen - 15:59 Wednesday 20 November 2024 (31697) Print this report
Periodic integration sphere calibration for XPcal

With Michimura

We performed the integrating shpere calibraiton for Pcal-X.
The results are similar to the previous measurements.

Result Summary:

Alpha values are voltage ratio between ISs in XPcal and WSK. 
alpha_RxPDpWSK_1 = 1.01099 +- 0.00028
alpha_RxPDpWSK_2 = 1.00658 +- 0.00034
alpha_TxPD1pWSK = 2.84929 +- 0.00030
alpha_TxPD2pWSK = 3.88791 +- 0.00037

e values are optical efficiency values. 
e_1 = 0.96496 +- 0.00020
e_2 = 0.95479 +- 0.00023

Comments to this report:
dan.chen - 6:26 Thursday 21 November 2024 (31703) Print this report

Before this work, I checked the Pcal-X beam positions on the ETMX, and adjusted a little.
What I used are PCAL_EX2 picos.

Pico movment: 

  • PCAL_EX2 pico 1: +50
  • PCAL_EX2 pico 2: +100
  • PCAL_EX2 pico 4: +50

Beam positions on the ETMX changed by about 2mm:
Before ([0,0] means the design position.): Fig 1 = TCam_ETMX_00111_2024_1120_051540_fitting_comp.png

  • Pcal beam position (path1) [mm]: [3.91584, 2.40329]
  • Pcal beam position (path2) [mm]: [2.75383, 3.67881]

After: Fig 2 = TCam_ETMX_00111_2024_1120_054412_fitting_comp.png

  • Pcal beam position (path1) [mm]:  [3.98096, -0.55771]
  • Pcal beam position (path2) [mm]:  [2.67615, 1.67651]

During calibration at the end station, we found the beams were slightly(2-3mm) shifted from the centre on the RxPD.
Today, we proceeded the calibration without making the adjustment. The impact on the calibration results appears to be limited, but it may need to be adjusted in the future.

Images attached to this comment
MIF (General)
takafumi.ushiba - 15:27 Wednesday 20 November 2024 (31696) Print this report
Power estimation at AS during lockloss

Abstract:

Power at AS can reach more than 4W even with 1W operation when the lockloss happens.
Due to the saturation, it is difficult to confirm how much power is going to AS when lockloss happens.

Detail:

To estimate the power at AS when lockloss happens, I calibrated K1:LSC-AS_PDA1_DC_OUT_DQ to OMC transmission.
Figure 1 shows the signals when OMC was locked with single XARM lock.
When OMC transmission was about 35.7mW, the value of K1:LSC-AS_PDA1_DC_OUT_DQ was 0.055, so the calibration factor from K1:LSC-AS_PDA1_DC_OUT_DQ to the power at OMC is 650 mW/cnt.

Figure 2 shows an example of lockloss with 1W operation.
It takes 20ms to increase the signals at AS from 0.2 to 6.2 (saturation), which are corresponding to 130mW and 4W.
After saturation, signals keep more than 6.2 cnts for 17.5ms but I'm not so sure the power to OMC keeps morethan 4W for 17.5ms because the signals had already saturated.

Since current PD gains at OMMT2T and POS are too high and they saturate before the saturation of AS PDs, it is necessary to reduce the PD gain to confirm the real trend of AS power.

Images attached to this report
Comments to this report:
takafumi.ushiba - 9:12 Thursday 21 November 2024 (31705) Print this report

I checked the signals last night and confirmed that OMMT2T trans DC PD was not saturated when lockloss happened.
Figure 1-3 shows the signals when the lockloss happened in this morning.
The first peak power is about 19W and the second is about 4W (fig1).
FWHM of the first peak and second is about 15ms (fig2) and 5ms (fig3), respectively.

After achieving PRFPMI_RF_LOCKED, maximum power at AS is about 500mW (fig4), so if we set the power treshold at AS as 1W or something, the trigger seems to work only when lockloss happens.
In addition, speed of power increase from 1W to 19W is about 20ms (fig5).

Images attached to this comment
yuta.michimura - 10:28 Thursday 21 November 2024 (31711) Print this report

The lock loss blast with a peak height of 19 W and FWHM of 15 msec gives integrated energy of roughly 19 W * 15 msec = 0.3 J.
Intra cavity power with 1 W input for each arm is Pcav = Pin * PRG * 4/T_ITM / 2 = 1 W * 15 * 4/0.4% / 2 = 7.5 kW.
This means that total energy stored in XY arms is Ecav*2 = Pcav * 2 * 2 * Larm / c = 0.3 J.
Amazingly consistent (see also JGW-T2416173).
To have less than 30 mJ at OMC PDs (total of two PDs) when the input power is 10 W, we need to reduce the OMC duty factor to less than 30 mJ / (0.3 J * 10) = 1%.
Continuously sweeping OMC with a triangular wave of peak-to-peak of 1 FSR gives (effective) duty factor of 1/Finesse = 1/800 = 0.125%.
So, sweep of 0.125 FSR peak-to-peak would be enough.
Using 100 Hz triangular wave, time to sweep the OMC resonance peak will be
1 / 100 Hz / 2 * (1/Finesse) / 0.125 = 50 usec
Even the OMC resonance peak happens to align with the peak of the lock loss blast, the energy deposited on OMC PDs (total of two PDs) for 10 W input will be
10 * 19 W * 50 usec = 9.5 mJ
This is smaller than the 30 mJ requirement. So, sweeping with 0.125 FSR peak-to-peak at 100 Hz will be good.

tomotada.akutsu - 11:04 Thursday 21 November 2024 (31714) Print this report

Too consistent, isn't it...?

takafumi.ushiba - 13:05 Thursday 21 November 2024 (31715) Print this report

>Even the OMC resonance peak happens to align with the peak of the lock loss blast, the energy deposited on OMC PDs (total of two PDs) for 10 W input will be
>10 * 19 W * 50 usec = 9.5 mJ

If we consider the speed of scan (5ms), OMC psses on the resonance 3 times within FWHM (15ms).
Even in that case, obtained energy of PD is less than 9.5mJ * 3 = 28.5 mJ, which satisfy the requirement (< 30mJ).

Search Help
×

Warning

×