wiki:NightOperations/Commissioning/Plans/20161118

Version 8 (modified by sco, 7 years ago) (diff)

--

20161118 Commissioning Plan

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 LRS2 upgrade and closed-loop focus testing

Lowest Priority: Science and HETDEX engineering

On-sky engineering:

Run full tracks with bib camera+ to assess centroid drag

  • Use do_shuffle to setup on a V=12 star near start of track
  • See that previous two plans for notes on how we modified the flane.txt file for this.
  • Have TO focus up and have RA center at least one OWFS
  • Use GUI in PAS to move star to bib and hold probes on their targets
  • close focus loop
  • set bib exposure to 2sec (for V=12 star)
  • Record a time in the log
  • Use TO save images button to save gc1,gc2.wf1,wf2,bib images
  • It is good to chek that "Store Images" button is now clicked in all camera gu
  • In this test we should NEVER apply X,Y offset corrections
  • If TO makes a Tip-Tilt change record the time in the log
  • If TO makes a GRoC correction record the time in the log
  • Run until the end of track
  • when done, record a time in the log

Run full tracks with bib camera+ to assess WFS corrections

  • Use do_shuffle to setup on a V=12 star near start of track
  • See that previous two plans for notes on how we modified the flane.txt file for this.
  • Have TO focus up and have RA center at least one OWFS
  • Use GUI in PAS to move star to bib and hold probes on their targets
  • close focus loop
  • set bib exposure to 2sec (for V=12 star)
  • Record a time in the log
  • Use TO save images button to save gc1,gc2.wf1,wf2,bib images
  • It is good to chek that "Store Images" button is now clicked in all camera gu
  • In this test we should apply X,Y offset corrections as they become necessary
  • If TO makes a Tip-Tilt change record the time in the log
  • If TO makes a GRoC correction record the time in the log
  • Run until the end of track
  • when done, record a time in the log

VIRUS observations of Globular cluster

  • Use do_shuffle to set up on (center) of a globular cluster
    • NOTE: NGC7006 start track at 2:01UT
  • Have TO setup guiding on gc1 or gc2
  • After RA sets up at least one OWFS, have TO close focus loop
  • while at dither position 1, take bib images (you may have to manually open the PFIP shutter) and get the proper exposure time
  • start saving bib images
  • record start time in the log
  • Run the VIRUS dither.py script
  • stop saving bib images
  • record end time in the log

Dither test on DWFS9 in IFU 052

THIS MAY BE SOMETHING WE WILL DO WITH THE BIB CAMERA

Purpose: We want to see the reproducibility of the dithers imaged through the DWFS9 point grey camera which might be in IFU052. Procedure:

  • 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.
  • If you can confirm that this is the right IFU slot try the following steps
    • Setup on a 14th mag star for IFU052
    • Guide on GC1 or GC2
    • make sure GROC < 400
    • make sure you are in dither position 1
    • take a few images with the point grey camera dwfs9
    • change to dither position 2 with syscmd -P -v 'AdjustDither(pos=2)'
    • take a few images with the point grey camera dwfs9
    • change to dither position 3 with syscmd -P -v 'AdjustDither(pos=3)'
    • take a few images with the point grey camera dwfs9
    • move back to dither position 1 and repeat the last 7 steps until you collect 3 cycles of data.

Science with LRS2-R

Purpose: LRS2-R is available ifor shared-risk observatipns (beware of grouped targets with LRS2-).

Procedure:

  • The LRS2-B channel was returned to Austin on 20161118 UT and not available until further notice
  • You can use shuffle with the setup files from shuffle_config_matt or to try to compensate for the new ACAM angles try shuffle_config_matt3
  • Do a blind offset setup, ie. do_shuffle with 066 (Red)
  • If time is available, it would be useful to make a trajectory_offset to the LRS2-B position after the R channel observation is completed. After the offset is made, obtain an ACAM image and log the name of the image. We can use these images to assess how repeatabloe the offsets are. This can be done with probes='FALSE' or with probes='TRUE'.

Science with VIRUS Engineering

Purpose: Observe SHELA fields in the ENG16-2-666 program.

Procedure:

  • Use do_shuffle to set up on the 000 position
  • You can use shuffle with the setup files from shuffle_config_matt or to try to compensate for the new ACAM angles try shuffle_config_matt3
  • Conduct the VIRUS observation using dither.py

Drift test: GC1-GC2-ACQ

Purpose: 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.

Procedure:

  • Get a good stack with good groc (GROC < 250).
  • Record the GROC value and the truss temp.
  • Setup for a full track with good focus
  • Start saving images with GC1, GC2 and ACAM
  • TO should maintain focus
  • Be sure to run the DMI with 10 second interval.
  • At the end of the test be sure to report the GROC value and final truss temp.

Closed dome engineering for bad weather, or while stacking:

Long VIRUS darks

Purpose: 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.

Closed dome trajectories

Purpose: Exercise the system to find any problems with the upgrades recently done to TMCS and TCS.

Procedure:

  • Send a trajectory from do_shuffle
  • Setup on trajectory, including moving all guide probes to position
  • Put on some light in the dome
  • Run all cameras.
  • Run WFS1 and WFS2 with processing enabled.
  • Make offsets on all guiders and ACAM.

Repeat multiple times during the night as long as the weather does not allow you to open. Report any problems with shuffle or TCS.

twilights with VIRUS with different tracker positions

Purpose: 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.

Procedure:

  • 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