KAGRA Logbook

DetChar (General)

hirotaka.yuzurihara - 12:18 Monday 20 June 2022 (21190)

Sometimes DQR failed due to early MDC trigger time

I found that sometimes DQR jobs failed, for example see here (only availabe from DGS network).

The error message is :

RuntimeError: Cannot find all relevant data on any known server. Try again using the verbose=True keyword argument to see detailed failures.

I checked the log and found that the MDC trigger time is earlier than the time the latest frame file was generated. Due to this reason, the NDS on gwpy can't find the frame data and DQR jobs failed.

I chatted with YamaT-san about this issue. One of solutions is to run DQR at upper stream on DGS network called DMT network. We will continue to work on this.

Comments to this report:

hirotaka.yuzurihara - 15:35 Tuesday 05 July 2022 (21373)

To treat this issue, I added the retry option in each ini file. (See document)

I set `max_retries = 5`. I will check if this option works well or not.

hirotaka.yuzurihara - 19:54 Thursday 21 July 2022 (21561)

I found the way to run DAG jobs by using RETRY option. (see document)

I edited the original code (/users/yuzu/work/DQR/Script/o4-dqr-configuration/dqr_config/DQRdag.py) and added `self.retry = 5`. I left a note on DetChar wiki. Note that this is a temporal solution until the DQR process move to the upper stream.

Currently this modification is working well, except for omega-scan task.