Reports 1-1 of 1 Clear search Modify search
CAL (General)
hirotaka.yuzurihara - 14:23 Monday 10 July 2023 (25923) Print this report
Operation test of script to take TCam image (ITMX/ITMY/ETMX/ETMY) during mirror cooling

I implemented the script to take TCam image (ITMX/ITMY/ETMX/ETMY) during mirror cooling.

  • When launching the script, the state of LSC_LOCK guardian and pcal-x/y guadian will be stored. After finishing the script, the script will restore these states.
    • Only when the pcal state number > 20, we request OFS_CLOSED_LOW_P state.
  • It takes ~12 minutes (in total) to take 4 images for each mirror.
  • At that time of waiting too long time for locking GreenX, the script will launch the ushiba-san's script (klog#25049) to find the good position of PR3/ITMX/ETMX for GreenX.
  • During the operation tests, I didn' find any troubles.

usage

on workstation at control room,

  1. open terminal
  2. launch the following script ( /users/Commissioning/scripts/TCam/TCam_weekly_photo.py )
  3. wait until the message 'Done : requested PSL_LOCKED state to GRD-IO_REQUEST' appeared (it will take ~12 minutes.)
Comments to this report:
hirotaka.yuzurihara - 21:38 Monday 24 July 2023 (26075) Print this report

I updated the script to take TCam images during mirror cooling.

  • check the laser shutter for Green at the beginning of the code
  • send the log (the start time and the end time of the script) for the tcam channel of Slack

Note that from tomorrow, we will start regularly monitoring the mirror by taking TCam images.

hirotaka.yuzurihara - 14:15 Monday 31 July 2023 (26147) Print this report

YamaT-san pointed out the bug that REQUEST_S of Pcal guardian was still OFS_CLOSE_LOW_P even if it had been in READY before the photo session. See summary page (TCam photo session started on 19:20).

The cause was my mistake in the code. I have already fixed that bug. I hope the script restores the pcal status after the TCam photo session in today's evening. 

hirotaka.yuzurihara - 10:41 Wednesday 16 August 2023 (26335) Print this report

Commissioners pointed out the issue that the LSC_LOCK guardian didn't return to the DOWN state and it stopped at the RESET_ASC_FEEDBACK state when the original state was DOWN state. I fixed the script.

Search Help
×

Warning

×