A new code is /users/Commissioning/scripts/NightlyMeasurements/scripts/nightly_measurement-devel.py
It includes following 3 major updates and a logging function stopped due to a bug was resumed.
I haven't completed tests with actual IFO and guardian operations.
After testing it, it will be pushed to the product version.

Separation schedule definition form the script code
From the view point of the code management, it's so inconvenient to update a time stamp of the script code even when only a definition of measurement schedule is modified. To solve this issue, a definition of measurement schedule was separated from the script code as /users/Commissioning/scripts/NightlyMeasurements/conf/schedule.pyobj which is completely same format as python dict. On the new version of script, a schedule file is given as --schedule option.

Solving conflicts with another works
Because a current nightly measurement script was written with assuming to use during observing run, there was various conflicts on uses during commissioning e.g. when IFO lock cannot be available such as recent vacuum GV issues, when Working-mode is requested by another works, etc. For this reason, we needed to stop the nightly measurement script during daytime and management of completed and failed templates became complicated.

So new functions to separate a request to LSC_LOCK/OBS_INTENT by the nightly_measurements itself from ones by another processes or human. Hopefully we don't need to stop the nightly_measurement script.

Integration of control room and remote access
This script is now working as a foreground process mainly on the real terminal of control room workstations. It's slightly inconvenient for working another tasks in the control room. And also, it's difficult for remote login user to operate a scrip launched in the control room and vice versa.

For improving this situation, a new script (/users/Commissioning/scripts/NightlyMeasurements/scripts/nightly_measurement-devel.sh) is prepared to launch a nightly measurement process on the virtual console. A process launched from the control room can be check its progress and can be gently stopped via remote access. A process launched via remote access due to some reason can be also accessed from the control room.