Duty factor in O4a and O3GK took into account periodical maintenance time, down time by some trouble, and trouble shooting time. On the other hand we have also commissioning time during the observing period in O4c. Though taking into account also commissioning time is suitable as the duty factor during O4c run, it's slightly unfair on the comparison with past observing runs as the operational duty factor of the Interferometer. So I tried to separate "periodical maintenance time", "down time by some trouble" and "commissioning time" by the information on klog and other activity logs because there is no dedicated flags for each activities (all activities out of observing mode were done just with retracting OBS_INTENT).

According to the evaluation until Jul. 16th, a time period of retracting OBS_INTENT is ~35% of total observing period. Maintenance time, trouble shooting time, and commissioning time are 12%, 6%, and 17% of total period, respectively (34%, 16%, and 49% of OBS_INTENT==OFF period, respectively). More details can be found in JGW-G2516753.

These activities periods are being served as Segment information in /users/OBS/O4c/segments/obs_intent_off/*.xml which contain
K1:DET-OBS_INTENT_OFF:1
K1:OBS_INTENT_RETRACT_MAINTENANCE:1
K1:OBS_INTENT_RETRACT_TROUBLE:1
K1:OBS_INTENT_RETRACT_COMMISSIONING:1.
Because they have a different purpose than the science mode subdivisions, so the file paths are separated from those uploaded to DQSEGDB.