Reports 1-1 of 1 Clear search Modify search
DetChar (General)
Shunsei Yamamura - 0:37 Friday 26 May 2023 (25382) Print this report
Summary of Guardian LSC_LOCK state during 05/17 9:00 ~ 05/23 13:34 JST

I summarized the Guardian state.

  • Used data
    • start: 2023/5/17 9:00:00 JST = gpstime 1368316818
    • end: 2023/5/23 13:34:53 JST = gpstime 1368851711
    • The end time is not good number, because missing data happened after the time.
  • Duty cycle
    • 56.5 %  (= 302061 sec / 534893 sec)
    • total time = 534893 sec
    • locked time = 302061 sec
    • "locked" means that the state is "OBSERVATION" or "WORKING_WITH_OBSERVATION".
  • Recovery time from lockloss (Fig.1, Fig.2)
    • x-axis is recovery time, y-axis is the number of events
    • There was a long lockloss due to the lack of Green X (klog#25317) on 05/20. The lockloss is incuded in Fig.1, but it is not included in Fig.2.
    • Without the long lockloss (5/20),
      • mean = 2739.5 [s] = 45.7 [min]
      • median = 1308.6 [s] = 21.8 [min]
  • Livetime in each state (Fig.3)
    • x-axis is a state of Guardian, y-axis is cumulative livetime
  • Where and when lockloss occurred (Fig.4, .txt file)
    • (Fig.4) x-axis is a state of Guardian, y-axis is the number of events
    • (file) a list of the state and gpstime, when lockloss happened
Images attached to this report
Non-image files attached to this report
Comments to this report:
Shunsei Yamamura - 1:36 Saturday 03 June 2023 (25488) Print this report

I am so sorry that the last figure and text file in the above klog was wrong because I misunderstood the behavior of Guardian. 

This time, I define "lockloss" means being "DOWN" state without requesting it.

  • a plot of where the lockloss occurred (Fig.1)
    • x-axis is a state of Guardian, y-axis is the number of events
    • There are many lockloss at "ALS_XY_LOCKED" state.
  • a list of gpstime (lockloss_list.txt)
    • left is a state of Guardian, right is gpstime
  • a list of how long it took in the state until lockloss occurred (duration.txt)
    • left is a state of Guardian, right is duration [sec]
    • It stayed 0.1875 sec at "ALS_XY_LOCKED" state until lockloss.

memo:

In the previous klog, I used "LOCK_LOSS" state to define lockloss. However, there are a lot of lockloss which don't pass "LOCK_LOSS" state. So I use "DOWN" state to define lockloss this time. Additionally, I took into account whether the lockloss happened intentionally or not, by using "K1:GRD-LSC_LOCK_REQUEST_N" channel.

Images attached to this comment
Non-image files attached to this comment
Search Help
×

Warning

×