[Ushiba, YamaT]

We deployed the new OMC_LSC guardian code to use the new camera client script for taking OMC_TRANS images.
Guardian logs (Fig.1) shows that new code can take multiple images with a short interval as expected.
After running it for a few days without major issues, it should be fine to remove all temporary measures like the 60-second sleep (klog#36364).

At this time, we also made two minor improvements as follows
1. Mitigation of a sign flip issue of sweep direction when guardian load is done in FIND_RESONANCE (Fig.2)
Because the sign of sweep direction is defined as global variable, loading guardian code during a stay in the run function makes undesirable a sign flip. In normal operation, such code loading isn't done, so it's not an issue. But it sometimes occur during a code development to escape from the user code error. This issue makes it difficult to distinguish whether the issue lies with the modified code or simply with loading a code in the run function. This improvement avoids undesirable sign flips caused by loading code within the run function, which should make future code development easier.

2. Reduction of a possibility to grab a same resonance when it's a non-TEM00 (Fig.3)
When guardian detects non-TEM00 lock, it makes a jump of the offset value to try to get away from that wrong resonance. But this offset jump is made with shorter time (in same cycle) than the decay time of analogue electronics, so the offset jump on the digital system doesn't sometimes work well. As a result, it detects non-TEM00 lock once, wrong lock is often repeated. This improvement makes the offset jump on the digital system effective to grab TEM00 with a small number of trial.

The difference before and after these minor improvements are available in
/opt/rtcds/userapps/release/omc/k1/guardian/patches/OMC_LSC-new-camera-client_260219.patch