Patrick, Jonathan, Sheila, TJ
During locking following maintenance Tue 18mar2025 we tried to move the BS camera from its old server (h1digivideo2) to its new server (h1digivideo5) for a second time. We had tried this the previous week but ran into locking issues with h1asc's use of this camera's centroid values and so had to move this, along with the ITM cameras back to h1digivideo2.
The plan was to just move one camera, h1cam26, to the new server and make the gain changes on h1asc's camera centering to compensate for the new video IOC, as was done when the ETM cameras were moved last year.
It became quickly apparent that the centroid values were more noisy with the new code in addition to being offset (plot shows CAM26_X, new code on left, old code on right).
We suspect the issue may be due image masking. The old code applied an image mask before calculating the centroids, the new code takes the image as a whole. The image snapshot shows that the edge of the optic is visible to the right, an issue the ETM images do not have.
We reverted CAM26 back to the old server at 17:00 PDT.
During the testing of BS on the new server I removed it from the camera dummy ioc. After it was reverted back to the old server I added its new PVs back to the dummy ioc to green up the EDC.
Here is the current camera situation, cameras running the old code are marked with the RED VID2
During our BS camera work there was a consensus that it would be good if the BS image was displayed on a control room FOM. It was generally agreed that the ITMX_SPOOL camera on nuc35 could be replaced with the BS camera.
I made the fom yaml change and rebooted nuc35 at 09:47 PDT. The new FOM screen is attached.
