This morning Yokozawa-san reported a bug that the script was not working. The reason was a typo. I fixed it.

Before participating in O4c, we investigated the lockloss cause during the commissioning phase. After joining O4c, I switched the lockloss list. That list include the lockloss only from OBSERBING state (IFO Guardian value of 1000). It's same list with the klog34607 and O4c lockloss list.
if you want to see the data around lockloss at the time when IFO guardian is not in OBSERVING state (such as the OBS_INTENT flag is off), you can use the option using the GPS time directly instead of the index option of the lockloss.
For example,  

• Index option (index number can be taken from the lockloss list)
  • /users/yuzu/lockloss/run_lockloss_ndscope.sh -L -i 1 
• GPS time option
  • /users/yuzu/lockloss/run_lockloss_ndscope.sh -L 1433635583.1875