Stability test for ACQ camera mirror, FCU head, PV/CWFS mirror

SVN location: ​svn+ssh://cetus/svn/astronomy/stability_test

This page documents the new (circa 2021) script that tests the stability of four elements in the PFIP:

• ACQ camera mirror deployment
• FCU head deployment
• PV/CWFS mirror deployment
• PV/CWFS mirror change

It differs from our old script in a few ways:

• it can be run on juno or zeus (NOT as astronomer@mcs)
• it takes 00:10:30 to run with default parameters and assuming you answer "Y" right away
• it no longer requires the user to type in the current tracker temperature (uses headers to get ambient temperature)
• it requires the user to confirm that the hardware is in the correct positions:
  • ACQ and FCU tests require you (or ask the TO) to abort the tracker (optionally: move tracker to center)
    • NOTE: this script will NOT move the tracker - you must do it
  • PV/CWFS tests require dome lights on, PV/CWFS cameras powered on, PAS restarted

Below is an example of the test being run for the ACQ camera mirror (as we do daily at OPS), which takes about 10.5 minutes with the default parameters:

[stevenj@juno ]$ stability_test.py acq
You have requested a  stability test of the acq with 10 cycles,  0.7s exposures, and a pause of 15s between each move

 Please confirm the following:
   1) Tracker is aborted (optional: at center)
   2) No other cals using the FCU are running, including with HPF
[Y?]  Y
   connecting to TCS systems...
   cycle 1 / 10
   cycle 2 / 10
   cycle 3 / 10
   cycle 4 / 10
   cycle 5 / 10
   cycle 6 / 10
   cycle 7 / 10
   cycle 8 / 10
   cycle 9 / 10
   cycle 10 / 10
Test data acquisition complete!   Putting hardware back to neutral state, then I will run the analysis.
analyzing test for 20210215 UT
  N    dx[px]  dy[px]  
|----|-------|-------|
   1    --      --
   2   0.0167 -0.0005
   3   0.0358 -0.0007
   4   0.0520 -0.0007
   5   0.0711 -0.0005
   6   0.0869 -0.0006
   7   0.1010 -0.0006
   8   0.1160 -0.0007
   9   0.1292 -0.0006
  10   0.1363 -0.0007

averages on 9 comparisons:
-------------------------------
 dx =  0.0890 +/- 0.0420 [pixels]
 dy = -0.0006 +/- 0.0001 [pixels]
-------------------------------

This script also contains the analysis code to produce graphs and summaries of current/previous tests. It currently (Mar 2021) saves output to the /data1/archive/stability_test/ directory.

Most of the details can be found in the script's help:

[stevenj@juno ~]$ stability_test.py -h
usage: stability_test.py [-h] [-n [n]] [-t [t]] [-e [e]]
                         [--analyze [--analyze]] [-b [b]] [-f [f]]
                         [--meta [meta]]
                         instrument

    Analyze stability with repeated retract/deployments of ACQ mirror, FCU head, or PV/CWFS mirror

    ACQ mirror test and FCU head test require:
     -tracker at aborted (optionally: at center)
     -no other cals/instruments using FCU
    PV/CWFS mirror tests requires:
     -tracker at aborted (optionally: at center)
     -dome lights are ON
     -CWFS/PV cameras are powered on, PAS has been restarted
    
    Examples:
	  stability_test.py acq                    (runs ACQ mirror deployment test with default parameters)
	  stability_test.py acq -n 10              (runs a test with N images/repeats)
          stability_test.py acq -t 15              (runs a test with a 15s wait after each retraction and deployment)
          stability_test.py acq -e 0.7             (runs a test with a 0.7s exposure on the ACQ camera)
          stability_test.py acq --analyze 20201211 (runs analysis on that night's stored images)
          stability_test.py acq -b 5               (in analysis mode, ignore this many images when sorting list)
          stability_test.py acq --meta 10          (run multi-night meta-analysis on last 10 days of data, and email plot!)

	  stability_test.py fcu                    (runs FCU head deployment test with default parameters)
	  stability_test.py fcu -n 10              (runs a test with N images/repeats)
          stability_test.py fcu -t 15              (runs a test with a 15s wait after each retraction and deployment)
          stability_test.py fcu -e 0.7             (runs a test with a 0.7s exposure on the ACQ camera)
          stability_test.py fcu --analyze 20201211 (runs analysis on that night's stored images)
          stability_test.py fcu -b 5               (in analysis mode, ignore this many images when sorting list)

	  stability_test.py pv                     (runs PV mirror deployment test with default parameters)
	  stability_test.py pv -n 10               (runs a test with N images/repeats)
          stability_test.py pv -t 15               (runs a test with a 15s wait after each retraction and deployment)
          stability_test.py pv -e 3                (runs a test with a 3s exposure on the PV camera)
          stability_test.py pv --analyze 20201211  (runs analysis on that night's stored images)
          stability_test.py pv -b 5                (in analysis mode, ignore this many images when sorting list)

	  stability_test.py cwfspv                     (runs CWFS/PV swap test with default parameters)
	  stability_test.py cwfspv -n 10               (runs a test with N images/repeats)
          stability_test.py cwfspv -t 15               (runs a test with a 15s wait after each retraction and deployment)
          stability_test.py cwfspv -e 3                (runs a test with a 3s exposure on the PV camera)
          stability_test.py cwfspv --analyze 20201211  (runs analysis on that night's stored images)
          stability_test.py cwfspv -b 5                (in analysis mode, ignore this many images when sorting list)

          
    

positional arguments:
  instrument            Which instrument to test stability (acq, fcu, pv, cwfspv)

optional arguments:
  -h, --help            show this help message and exit
  -n [n]                Number of times to repeat the retraction/deployment
                        cycle
  -t [t]                Seconds to wait after each retraction and deployment
  -e [e]                Exposure time for ACQ camera (in seconds)
  --analyze [--analyze]
                        If selected, the UT date to analyze
  -b [b]                ignore this many images at end before collecting real
                        data in analysis
  -f [f]                force script to start test immediately without
                        requesting user confirmation that the system is ready
  --meta [meta]         multi-night meta analysis for this many nights (ACQ
                        only right now, will email plot)