Changes between Version 1 and Version 2 of NightOperations/Commissioning/Plans/20161107


Ignore:
Timestamp:
Nov 7, 2016 11:42:27 PM (8 years ago)
Author:
sco
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NightOperations/Commissioning/Plans/20161107

    v1 v2  
    1 Plan 20161107
     1= 20161107 Commissioning Plan =
     2
     3Priorities 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 interval time.'''
     4
     5Highest Priority:   Engineering; do any support for Hanshin or Randy in support of Hanshin.   
     6
     7Lowest Priority:  Science and HETDEX engineering
     8
     9== Closed dome engineering for bad weather, or while stacking: ==
     10
     11=== Long VIRUS darks ===
     12
     13Purpose:   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.   
     14
     15=== Closed dome trajectories ===
     16
     17Purpose:  Exercise the system to find any problems with the upgrades recently done to TMCS and TCS.
     18
     19Procedure: 
     20 *  Send a trajectory from do_shuffle
     21 *  Setup on trajectory, including moving all guide probes to position
     22 *  Put one some light in the dome
     23 *  Run all cameras.
     24 *  Run pipelines for WFS
     25 *  Make offsets on all guiders and ACAM.
     26
     27Repeat multiple times during the night as long as the weather does not allow you to open.  Report any problems with shuffle or TCS.
     28
     29 === twilights with VIRUS with different tracker positions ===
     30
     31Purpose:  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.
     32
     33Procedure: 
     34 *  Setup the guide camera for sky twilight (GC2, 0.1 sec, B filter)
     35 *  When you hit the correct flux level (biased to a slight higher value, perhaps 5k) execute the specialtwilight script
     36
     37== On-sky engineering: ==
     38
     39
     40
     41===  Drift test:  GC1-GC2-ACQ ===
     42
     43Purpose:   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.
     44
     45Procedure:
     46 *  Get a good stack with good groc (GROC < 250).
     47 *  Record the GROC value and the truss temp.
     48 *  Setup for a full track with good focus
     49 *  Start saving images with GC1, GC2 and ACAM
     50 *  TO should maintain focus
     51 *  Be sure to run the DMI with 10 second interval.
     52 *  At the end of the test be sure to report the GROC value and final truss temp.
     53
     54=== Dither test on DWFS9 in IFU 052 ===
     55
     56Purpose:  We want to see the reproducibility of the dithers imaged through the DWFS9 point grey camera which might be in IFU052.
     57Procedure:
     58 *  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.
     59 *  If you can confirm that this is the right IFU slot try the following steps
     60     *  Setup on a 14th mag star for IFU052
     61     *  Guide on GC1 or GC2
     62     *  make sure GROC < 400
     63     *  make sure you are in dither position 1
     64     *  take a few images with the point grey camera dwfs9
     65     *  change to dither position 2 with {{{syscmd -P -v 'AdjustDither(pos=2)'}}}
     66     *  take a few images with the point grey camera dwfs9
     67     *  change to dither position 3 with {{{syscmd -P -v 'AdjustDither(pos=3)'}}}
     68     *  take a few images with the point grey camera dwfs9
     69     *  move back to dither position 1 and repeat the last 7 steps until you collect 3 cycles of data.
     70
     71 == Science with  LRS2-R and VIRUS Engineering ==
     72
     73Purpose:   LRS2-R is available for beware of grouped targets with LRS2-B.
     74
     75Procedure: 
     76 *  '''NOTE:   LRS2-R is in IFU slot 057 '''
     77 *  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}}}
     78 *  Do a blind offset setup, ie. do_shuffle RA DEC 0 X 057 0 0 test
     79