R&D (FilterCavity)
MichaelPage - 16:55, Wednesday 28 December 2022 (3138)
Suspension check

For the PR I remembered that I should try and realign using the picomotors to bring the oplev output beam to within the actuation range of the steering mirror. This is actually a common problem but because I am not so good independently operating FC I forgot, so others not so familiar with FC operation who are reading this should also take note.

For the health check, I looked at the terminal logs (fig 1) and it seems that there is a test timeout error on every measurement of the coils. What that means is that the program starts at coil PR_H1, sets up the frequency range to be iterated, then tries to measure the first frequency point but fails some sort of supervisory check in this measurement. Then, it aborts the opration but also says the data is saved into the file PR_H1 located in /Desktop/TAMA_VIS/check_after_earthquake. After that, it moves on to the next coil, PR_H2, and does the same thing for all 16 coils on PR, BS, IN, END. So, in short, it looks like the health check script isn't taking any data.

I tried deleting some of the data in /frames/full on the standalone PC but it took a really long time. I pressed Ctrl+C in terminal to stop the operation after about 40 minutes had passed, then checked the disk status with the df command, and it was still at about 76% capacity.

I took a snapshot using the button in the medm VIS overview interface. Then I restarted the standalone PC and pressed restore snapshot in medm VIS. But it seems to have not completely restored things, for example, the file structure seen when using ssh into standalone (fig 2). To be honest, it is not clear to me *exactly* what this snapshot function does, so this problem and procedure should be written down in the GWSP wiki under FC procedure to operate, when I figure it out.

Anyway, I had rebooted the standalone PC and there *should* be sufficient disk space to perform measurements. But I still keep getting the same test timeout error when I run the health check script. Everyone who can help with this problem is on holiday so I will just leave it for now.

Images attached to this report
3138_20221228085501_20221227210057testtimeout.jpg 3138_20221228085505_20221227224037snapshot.jpg