Changes between Initial Version and Version 1 of NightOperations/Commissioning/20161116


Ignore:
Timestamp:
Nov 16, 2016 7:35:55 PM (8 years ago)
Author:
sco
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NightOperations/Commissioning/20161116

    v1 v1  
     1= 20161116 Commissioning Plan =
     2
     3
     4Priorities for test are in the order listed in the plan below.   '''NOTE:  The DMI should now be run for every trajectory with a 10 second cycle time.'''
     5
     6Highest Priority:   Engineering; do any support for LRS2 upgrade and closed-loop focus testing
     7
     8Lowest Priority:  Science and HETDEX engineering
     9
     10
     11== Closed dome engineering for bad weather, or while stacking: ==
     12
     13=== Long VIRUS darks ===
     14
     15Purpose:   In each RA run take 10 x 6 minute dark with a dark dome with VIRUS.   Report this in the RA report and send e-mail to Karl that this has been done.   
     16
     17=== Closed dome trajectories ===
     18
     19Purpose:  Exercise the system to find any problems with the upgrades recently done to TMCS and TCS.
     20
     21Procedure: 
     22 *  Send a trajectory from do_shuffle
     23 *  Setup on trajectory, including moving all guide probes to position
     24 *  Put on some light in the dome
     25 *  Run all cameras.
     26 *  Run WFS1 and WFS2 with processing enabled.
     27 *  Make offsets on all guiders and ACAM.
     28
     29Repeat multiple times during the night as long as the weather does not allow you to open.  Report any problems with shuffle or TCS.
     30
     31 === twilights with VIRUS with different tracker positions ===
     32
     33Purpose:  There is some interest in seeing what the long term illumination correction changes look like including what different track positions do to them.    The script is "specialtwilight" in /home/mcs/astronomer/bin/.    It takes a single argument which is the Observation number.
     34
     35Procedure: 
     36 *  Setup the guide camera for sky twilight (GC2, 0.1 sec exposure, B filter)
     37 *  When you hit the correct flux level (biased to a slight higher value, perhaps 5k) execute the specialtwilight script
     38
     39== On-sky engineering: ==
     40
     41=== Run full tracks with bib camera+ ===
     42
     43 * Use do_shuffle to setup on a V=12 star near start of track555   
     44 * We must modify the usual do_shuffle run:
     45
     46{{{
     47To get bib to setup use this line in fplane.txt
     48555     0.0   -70.0     900     900     900     0.0     1.0
     49Use the new script:   shuffle_config_matt3
     50
     51When you have guide stars acquired, use this command to get final star centering on bib:
     52syscmd -T 'offset_trajectory(dx_ang=+5, dy_ang=+4, adjust_probes="true")' 
     53
     54NOTE: Eventually we can modify the X,Y values in the fplane.txt file and eliminate this last offset_trajectory step.
     55  I was going to do this, but at 3am I new I make a sign-change error and mess things up!
     56}}}
     57
     58 * Have TO focus up and have RA center at least one OWFS
     59 * Use GUI in PAS to move star to bib and hold probes on their targets
     60 * close focus loop
     61 * set bib exposure to 2sec (for V=12 star)
     62 * Record a time in the log
     63 * Use TO save images button to save gc1,gc2.wf1,wf2 images
     64 * Manual start saving bib images
     65 * Run until the end of track
     66 * when done, record a time in the log
     67
     68=== VIRUS observations of Globular cluster ===
     69
     70 * Use do_shuffle to set up on (center) of a globular cluster
     71   * NOTE: NGC7006 start track at 2:01UT
     72 * Have TO setup guiding on gc1 or gc2
     73 * After RA sets up at least one OWFS, have TO close focus loop
     74 * start saving bib images
     75 * record start time in the log
     76 * Run the VIRUS dither.py script
     77 * stop saving bib images
     78 * record end time in the log
     79
     80
     81=== Close-Loop Focus Tracks ===
     82
     83 * Set up on a foc09 star in the usual way (i.e. use do_shuffle or gstar to put the V=9 star in DWFS8 and guide stars in gc1,gc2).
     84 * Set up wf1/wf2 in usual way
     85 * Record time in log
     86 * Have TO close focus loop
     87    * Check the DMI pipeline is running.
     88    * Start Metrology loop and activate loop on DMI.
     89    * Make sure OWFS that you want to guide focus on is well centered.
     90    * Start and then Activate the metrology loop on the OWFS that you
     91      would like to start guiding focus on.
     92 * At end of track, record time
     93 * After each track set, adjust GRoC
     94
     95Niv and Jason have asked for a variety of structure AZ values, but we must stay away from AZ=64 (CCAS) as this is not implemented in the WFS pipeline yet.
     96
     97
     98
     99
     100=== TEST 5: ACAM focus (THIS NEEDS WORK BEFORE WE UNDERSTAND THIS TEST!) ===
     101  * Insure that temperatures are stable and DIMM seeing is better than 1.5"
     102  * Set up on geo-sat (probably GOES-14)
     103  * Have TO focus on satellite image using dwfs8
     104  * record  a dw data dump to capture telescope focus
     105  * insert the acq mirror and run /home/mcs/astronomer/scriptacq
     106  * have TO refocus with dwfs8
     107  * record  a dw data dump to capture telescope focus (to determine if significant drift occurred)
     108   
     109Analysis: Measure width of PSF to get acq focus curve and measure  focus offset (should be close to zero).
     110
     111=== TEST 6: Dither test on DWFS9 in IFU 052 ===
     112
     113Purpose:  We want to see the reproducibility of the dithers imaged through the DWFS9 point grey camera which might be in IFU052.
     114Procedure:
     115 *  Put a really bright star on IFU052 to confirm that we can actually confirm that it is right one (you will need a guide star to hold it steady.
     116 *  If you can confirm that this is the right IFU slot try the following steps
     117     *  Setup on a 14th mag star for IFU052
     118     *  Guide on GC1 or GC2
     119     *  make sure GROC < 400
     120     *  make sure you are in dither position 1
     121     *  take a few images with the point grey camera dwfs9
     122     *  change to dither position 2 with {{{syscmd -P -v 'AdjustDither(pos=2)'}}}
     123     *  take a few images with the point grey camera dwfs9
     124     *  change to dither position 3 with {{{syscmd -P -v 'AdjustDither(pos=3)'}}}
     125     *  take a few images with the point grey camera dwfs9
     126     *  move back to dither position 1 and repeat the last 7 steps until you collect 3 cycles of data.
     127
     128===  Drift test:  GC1-GC2-ACQ ===
     129
     130Purpose:   We want to see how much drift there is from one side of the IHMP to the other.  Generally we want to guide on one GC and watch the others.  This should be done in the south. At this time (20161107) HL has requested that we collect at least 20 sets of data collected as we describe below.
     131
     132Procedure:
     133 *  Get a good stack with good groc (GROC < 250).
     134 *  Record the GROC value and the truss temp.
     135 *  Setup for a full track with good focus
     136 *  Start saving images with GC1, GC2 and ACAM
     137 *  TO should maintain focus
     138 *  Be sure to run the DMI with 10 second interval.
     139 *  At the end of the test be sure to report the GROC value and final truss temp.
     140
     141
     142
     143 == Science with  LRS2-R and VIRUS Engineering (LOWEST PRIORITY) ==
     144
     145Purpose:   LRS2-R is available for beware of grouped targets with LRS2-B.
     146
     147Procedure: 
     148 *  '''NOTE:   LRS2-R is in IFU slot 057 '''
     149 *  You can use shuffle with the setup files from {{{shuffle_config_matt}}}  or to try to compenstate for the new ACAM angles try {{{shuffle_config_matt2}}}
     150 *  Do a blind offset setup, ie. do_shuffle RA DEC 0 X 057 0 0 test
     151