Issue #1
The k1bcst0 transmits 1 second-long data every second. However, when an IPC glitch occurs, the transmission occurs at intervals slightly less than 1 second from the previous transmission (Approximately 0.000 to 0.004 seconds faster. However, this number is not an accurate representation of the actual time of change, as it is not known how quickly the Frame_Log used for testing can respond to the arrival of a new frame.) This data is input to the low latency calibration pipeline, and its output is transferred to the Kashiwa by Framelink and further transferred to the CIT by Kafka. The IPC glitched data arriving at CIT was delayed about 1 second more than normal frames. As a result, the gwistat displayed on KAGRA status switches from Observing to Down, and Duration is reset to 0, even though KAGRA keeps locked and observing state. It is not yet known at why the data is transmitted early in the first place and what stage the data transmitted early is slowed down (Negative delay@k1bcst0 --> positive delay@CIT).

Issue #2
In low latency data stream, there is a loss of one frame approximately every few 10k seconds, which may also be resetting Duration on gwistat to 0. It is not yet clear at what stage this missing is occurring.

Issue #3
KAGRA status is sometimes shown as Down on the gwistat page even though the KAGRA interferometer is in Observing Mode and the summary page in KAGRA shows it as Observing Mode. This phenomenon occurs with a frequency of about a few hours per day. It is not yet clear what is causing it yet.

Operators name: Nakagaki, Yasui

Shift time: 16-24(JST)

Summary:

VAC, CRY, and TEMP had no problem.

16:00 OBSERVATION from the previous shift time

21:50 LOCK LOSS (21:49 M3.2 earthquake on the Noto Peninsula)

21:58 OBSERVATION (recovered automatically)

24:00 still in OBSERVATION

Do this? From GWADW2019 https://agenda.infn.it/event/15928/contributions/88922/attachments/63258/76101/BKamai_GWADW_final.pdf

I started to investigate the relationship between beam spot on ETMX and sensitivity curve of 300~400Hz. Summary slide is uploaded on JGW doc,  [slide].

Motivation is to find the characteristic relationship between the beam spot, the structure of 300~400Hz, and the inspiral range. For example, when the beam spot is off-center to specfic direction, the characteristic structure on the sensitivity curve of 300~400Hz will be mitigated or the inspiral range will be higher/lower than usual.

About plots : 

• left bottom : TCam image which was taken during PR3 alignment. At that time, we record the good oplev value of PR3.
• left top : time series of inspiral range, several minutes after the interferometer in observing mode.
• right top : whitened spectrogram of h(t), several minutes after the interferometer in observing mode. We focus on the specific frequency band 300 ~ 400Hz.
• right bottom : ASD of h(t) channel, several minutes after the interferometer in observing mode.  We fixed the frequency band and y-range.

Comments for the result

• The case of 5/31 (shown in page 8) might be good example. In the PR3 alignment, the beam spot is located at left lower from center [TCam image]. The inspiral range is lower than usual. ASD also shows broad bump.
  • I'm not sure this is a regular relationship. We need more samples.
• The case of 6/4 (shown in page 12) doens't show the characteristic large bump on 300 ~ 400Hz. I'm not sure the reason.

Comments for the further invetigation are very helpful!

Kimura, Uchiyama

2023/06/08

Kimura-sama updated the reference sheet for check items of cryogenics and URL of the sheet was pasted on the page of "Check Items during Shift".

Operators name: Miyakawa, Ushiba, Ikeda

Shift Time: unscheduled operations

Summary：

13:52 PR3 Alignment due to IPC glitch 
 => Miyakawa's PR3 Alignment Training
15:11 OBSERVATION

Operators name: Yasui, Nakagaki
Shift time: 16-24 (JST)

Summary:

Check Items:
VAC,CRY,TEMP There was no problem.

16:00 OBSERVING from previous shift time
19:22 LOCK LOSS (corresponding earthquake is unknown)
19:32 OBSERVING (automatically recovered)
24:00 still in OBSERVING

I started to test the segment production for missing/broken frame files. The script checks the list of missing/brok frame files, which was prepared by DMG. (see klog#25341)

The result segment file can be seen at /home/detchar/git/kagra-detchar/tools/Segments/Script/tmp/K1-DET_FRAME_AVAILABLE/2023/ , at Kashiwa cluster.

• The distances from the road construction area near the SK entrance to the KAGRA corner station: ~ 400m 
  • Excavators work for shaping the ground. ---> This is generating the excess seismic noise at MCF/IX(Y)V.
  • Dump truck transportation for filling ground.
• The distances from the future tunnel construction area around "Do" area to the KAGRA corner station: ~440m ~ 680m
  • Blasting
  • Excavators work for removing rocks outside.
  • Dump and concrete mixer truck transportation.
• The distances from the Sakonishi construction area to the KAGRA EX station: ~ 1300m
• The distances from the Sakonishi construction area to the KAGRA Corner station: ~ 1800m
• The distances from the Sakonishi construction area to the KAGRA EY station: ~ 4000m
  • Excavators work for moving/resetting rocks.
  • Rock crushing with a jackhammer.
  • Dump and concrete mixer truck transportation

Operators name: Ushiba, Ikeda

Shift Time: unscheduled operations

Summary：

13:57 PR3 Alignment due to IPC glitch 
13:20 request PRFPMI_RF_LOCKED
 => During the process, Ushiba-san LOCKED up manually.
15:53 OBSERVATION
 

Ushiba-san, Ikeda.

GigE camera settings that had a value of 0 after restart have been restored to the value of K-Log#25214.

MCE_TRANS, MC_REFL, POP, TMSX_G, TMSX_IR, TMSY_G, TMSY_IR
 ⇒Restored
AS, IFO_REFL, OMC_TRANS, PMC_REFL, PMC_TRANS
 ⇒Unchanged

Here is the ground motion comparison between MCF and "E"XYV. By eyeballs, the motion at MCF cannot be seen at EXYV. (Be careful of the vertical scale difference.)

Abstract

Details

I confirmed that the activities of excavators near the Kamioka mine company office generated the seismic noise enhancement at MCF and IXV as the attached file.

The numbers in the graph completely matched the excavators' activities status by my eyeballs.

1. I passed through the construction area and two excavators stopped (no engine sound at this time). I parked my car near the SK entrance and started monitoring the MCF/IXV ground motion via the EDUROM network.
2. I noticed the ground motion enhancement and moved my car to the near area of construction area where the mobile phone EM can be scarcely reachable. So I could keep monitoring the MCF/IXV ground motion. Only one excavator was working.
3. The second excavator started working. Then the excitation level was enhanced more!
4. One excavator stopped. So only one excavator was working.
5. One excavator started working. So two excavators were working.
6. One excavator stopped. So only one excavator was working.
7. One excavator started working. So two excavators were working.
8. Both excavators stopped.
9. Two excavators started working.
10. Both excavators stopped.

The sharp enhancement seemed to correspond to the horizontally large angle swing of arm of the excavator. I could not check the engine status when they stopped motions.

Operators name: M.Aoumi, M.Tamaki

Shift time: 00-08 (JST)
Summary:
Check Items:Vac, CRY,TEMP → There was no problem.
07:41 Lock loss(Automatic recovery).
08:14 OBSERVING

Although there were several earthquakes, we could keep the lock.

btw, it looks like the camera exposure for IMC REFL has been set to 0 before one knows (or maybe i just dont know).

Operators name: Nakagaki, Yasui
Shift time: 16-24(JST)
Summary:

VAC, CRY, TEMP; There was no problem.
The vacuum monitor problem that had been going on since yesterday(klog#25516) has not occurred for this shift time.

16:00 OBSERVATION from previous shift time
18:18 LOCK LOSS (18:17 M3.0 earthquake at Hida region)
          While LOCKING, the IFO guardian spoke an alert message. →Yamamoto-san is handling this matter(klog#25538).
18:33 OBSERVATION (recovered automatically)
24:00 still in OBSERVATION

I went to the Sakonishi-area and the road construction area near the Kamioka mine company office from 15:20~16:30.

No activities using heavy machinery around the Sakonishi area.

While there was excavator activity at the road construction area.

When I passed this area around 15:20, there was no activities of the excavator. After that, I went to the Sakonishi area, and there were no activities. After that, I went to the KAGRA entrance to get an internet connection and I monitored the ground motion, then I confirmed that the level denoted by green in the figure was low. After several decades of minutes, I noticed that the ground motion level was enhanced again. So, firstly I went to Sakonishi-area, but no activities. Then I went to the road construction area and found the excavator was working. I stayed near the SK entrance to obtain the EDUROM net to monitor the ground motion and the excavator activities. After the activity of the excavator was postponed, the ground level seemed to become low. Although I kept staying, the excavator did not restart its working until around 16:30.  I gave up and went back to the KAGRA DAB. However, the figure showed one more enhancement of the ground just before 17:00. I should be patient :(.

I would like to go there and check again if there is the ground excitation again tomorrow.

On the other hand, some activities around the Sakonishi-area was informed from the mid of June. So it is also important to check the relation.

This is a duplication post of CAL measurement (klog#25532).

I accepted the EPICS records related to the weekly calibration measurement as shown in Fig.1.
Channel list is also available in Secsion 1.2 of JGW-L2314962.

Today, I loaded down.snap once after accepting changes on observation.snap.
After then, I surely re-loaded observation.snap again and revert changes coming from
numerical rounding errors.
So I hope that troubles such as klog#25462 will not be occurred.