Changes between Version 8 and Version 9 of NightOperations/Commissioning/Plans/20161109

Timestamp:

Nov 9, 2016 2:20:17 AM (8 years ago)

Author:

justenp

Comment:

--

NightOperations/Commissioning/Plans/20161109

@@ -3 +3 @@
 '''THIS PAGE IS UNDER CONSTRUCTION BY SCO'''
 
-Priorities 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.'''
+Priorities 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.'''
 
 Highest Priority:   Engineering; do any support for Hanshin or Randy in support of Hanshin.   
@@ -23 +23 @@
  *  Send a trajectory from do_shuffle
  *  Setup on trajectory, including moving all guide probes to position
- *  Put one some light in the dome
+ *  Put on some light in the dome
  *  Run all cameras.
- *  Run pipelines for WFS
+ *  Run WFS1 and WFS2 with processing enabled.
  *  Make offsets on all guiders and ACAM.
 
@@ -35 +35 @@
 
 Procedure:  
- *  Setup the guide camera for sky twilight (GC2, 0.1 sec, B filter)
+ *  Setup the guide camera for sky twilight (GC2, 0.1 sec exposure, B filter)
  *  When you hit the correct flux level (biased to a slight higher value, perhaps 5k) execute the specialtwilight script
 
@@ -46 +46 @@
 Procedure:
  *  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).
- *  Have TO set-up and guide on either gc1 or gc2
+ *  Have TO set-up on IHMP position and guide on either gc1 or gc2
  *  Have TO use DWFS8 to focus the star (i.e. null the wavefront processing corrections) 
- *  Record GroC
+ *  Record GRoC
  *  Use /home/mcs/astronomer/script (modified by SIR on 20161107) to collect  GC1, GC2 images at different focus settings.
  *  Record GRoC 
@@ -57 +57 @@
 
 === TEST 1:Derive IHMP center on acam according to dwfs8 ===
- * Center a foc11 (or fainter) star with dwfs8 while guiding with gc1/gc2.
+ * Center a foc11 (or fainter) star on dwfs8 while guiding with gc1/gc2.
  * Move acam mirror in and take acam image being sure the foc11 star image is not saturated.
  * Immediately take a long (5-10 sec) exposure so that enough stars are obtained for a good wcs solution
 
 === TEST 2: Are the OWFS corrections the same as DWFS8? ===
-  * Run a track with stars ondwfs8-owfs1/2.
-  * At 10-min intervals save at least 5 images for ndwfs8-owfs1-owfs2
+  * Run a track with stars on dwfs8-owfs1/2.
+  * At 10-min intervals save at least 5 images for dwfs8-owfs1-owfs2
   * During the full track, bot RA and TO should observe the owfs images and try to observe cases of the "jumping overlays" that were discussed in the last meeting. In other words, note any cases where the yellow hexagon pattern changes position suddenly. Note the times of any such events. 
 
-=== TEST 3: Confirn OWFS offsets. ===
+=== TEST 3: Confirm OWFS offsets. ===
   * On a tracjectory, set up stars on dwfs8/wfs1/wfs2.
   * Instead of setting the focus/tip/tilt of the telescope using dwfs8, use wfs1 or wfs2 to set the focus/tip/tilt.
-  * Confirm the the calibration offsets are correctlyapplied. In other words, confirm that the dwfs8 corrections are also nulled out.
+  * Confirm the the calibration offsets are correctly applied. In other words, confirm that the dwfs8 corrections are also nulled out.
 
 === TEST 4:  Confirm CWFS-DWFS8 calibration ===
-  * set up cwfs on a satellite and offset the telescope to zero focus/theta/phi.
-  *  Move to dwfs8 to see if dwfs8 corrections are also close to nulled state 
+  *  Put a satellite on cwfs and null cwfs offsets to zero(focus/theta/phi offsets should be zero in cwfs).
+  *  Move to dwfs8 to see if dwfs8 corrections are also close to nulled state. 
 
 === TEST 5: ACAM focus (THIS NEEDS WORK BEFORE WE UNDERSTAND THIS TEST!) ===