Abstract:

I implemented ISC WD into LSC_LOCK guardian.
Now, ISC WD will be turned on at ENGAGE_ALS_DARM state.
Also, the threshould value is lowered at PRFPMI_LOCKED_WITH_3F state.

Detail:

To minimize the kick of suspension and unnecessary lockloss due to WD, I checked te value of K1:VIS-ETMY_ISCWD_WD_AC_L_RMSMON and set the proper threshould for WD.
Bottom left graph in fig1 shows the typical trend of RMSMON signals during the lock acquisition.
After ALS DARM is locked, RMS value is about 20000.
Then, it sometimes increase about 40000 during PRMI lock acquisition and handover due to the glitches on DARM signals.
So, I set the threshoud of 50000 during this period (I wrote this value at main function of ENGAGE_ALS_DARM state).

After PRFPMI is locked with 3F signals, RMS value becomes about 5000.
Due to the bad hadover method of local control to ASC (we can observe the oscillation during engaging ASC), it increases about 10000.
So, I set the threshould of 20000 during this period (setpoint of the threshould is changed at PRFPMI_LOCKED_WITH_3F state).

After setting the threshould, I confirmed IFO can reach PRFPMI_RF_LOCKED state.
If the threshould wil disturb the IFO lock acquisition or any other activity, please change the threshould by changing the guardian.