Dave, Ansel, Camilla
Dave has written script /opt/rtcds/userapps/release/cds/h1/scripts/hws_camera_control.py that is running on in a tmux session called "camera control" ITMX and ITMY hws computers (h1hwsmsr/h1hwsmsr1). Now we will be able to see HWS data for lockloss, locking and power up without contaminating DARM with combs when observing: more details in 74915. FRS4559 updated.
It takes takes two arguments (optic_name and cam_id) and runs in an infinite loop, every minute it gets the camera status and the IFO lock state. It monitors if H1 is locked and turns the cameras on and off accordingly (via an external triggering setting): OFF if ISC_LOCK > 580, on if ISC_LOCK < 580.
It logs its actions to the screen. Each cycle it writes the camera status to a file /opt/rtcds/lho/h1/hws/{optic_name} with the future plan to write this to a trendable channel. For now we can trend if the camera is on or off by seeing if the HWS data is updating, see attached.
Looks like a success; no sign of the 7 Hz comb in DARM on Dec 20th. Pre/post plots attached to demonstrate the improvement.
Overnight, Dave's code sucessfully ran on ITMX. ITMY and ETMX, plot attached. The couple of times there is a jump in spherical power is when the the camera got re-requested to be off, this doesn't matter. This logs in the tmux session show same.
e.g. ITMX on h1hwsmsr:
