Abstract:

Code development was finished except for FinesseMeasurement_developing.py, which is the modified version of current finesse measurement script.
I will test finesse measurement script tomorrow.

Detail:

I tested the developing code to detect the first lockloss on the day and changing the state of guardian for the finesse measurement.
This function seems to work well, and the script is now stored at /users/ushiba/script/python/automeasurement/finesse_automeasurement.py.
This code might be usuful for the weekly measurement which needs to down IFO.

The next step is to check if the new script for finesse measurement (/opt/rtcds/userapps/trunk/lsc/common/scripts/FinesseMeasurement_developing.py) will work properly.
I will check it tomorrow.

I tested the new finesse measurement code (/opt/rtcds/userapps/trunk/lsc/common/scripts/FinesseMeasurement_developing.py).
The change from the old function is as follows:

1. Fitting function modification:
In the old script, fitting function of the power decay is a*exp(-t/c).
This fitting function works well if the dark offset of the PD is well managed, but it is not the case in KAGRA now.
If the signals are large enough and cut properly before the signals become too small, the fitting works well but otherwise not.
It is not good situation that the finesse measurement result is affected by the condition of SNR too much, so I changed the fitting function as a*exp(-t/c)+b.
This modification seems to work well as shown in fig1 though I have just tested one time.

2. Implementation of the function to rotate IFO_REFL HWP
Since the CARM loop becomes unstable at several frequency such as 23kHz, 27kHz, and 50kHz, increasing the laser power without adjusting the CARM gain is sometimes difficult.
So, I added the function to rotate not only PSL HWP but also IFO_REFL HWP so that CARM UGF is kept around 10kHz.

3. Maagement of IO and XARM guardian request
There are several unnecessary and unwanted guardian management in the script, so I modified them.
One is request IO guardian to IMC_LSC_LOCKED state only when IMC is not locked.
This will avoid to down IMC from PROVIDING_STABLE_LIGHT state for the measurment.
Second is request DOWN state to XARM guardian if IMC is not locked.
Since XARM guardian and IMC guardian sometimes conflict with each other, it will help to improve the stability of XARM lock.

I will perform end-to-end test of the script soon.

I performed the end-to-end test yesterday.
Basically, the script worked well but I found several bugs though they don't affect the finesse measurment.
I will fix the bug and test it at some point.

I updated several bugs and started end-to-end test on k1ctr15.
Though it should not affect any works unless the first lockloss on the day happens during someone's work, please stop the script with Ctrl+C at k1ctr15 with remote desktop if some conflicts will happen.

I changed the file name of old finesse measurement script to FinesseMeasurement_old251211.py and new finesse measurement script to FinesseMeasurement.py.
So, the new script runs when the finesse measurement is started from the medm screen for finesse measurment.