wiki:NightOperations/Commissioning/Plans/20161026

20161026 Commissioning Plan

Priorities for test are in the order listed in the plan below.

Highest Priority: Engineering; do any support for Hanshin or Randy in support of Hanshin.

Lowest Priority: Science and HETDEX engineering

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 one some light in the dome
  • Run all cameras.
  • Run pipelines for WFS
  • 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.

Twilight Tests

OWFS on the blue sky as a function of probe position

Purpose: We want to get an idea of how the orientation changes with different probe positions.

Procedure:

  • Tell the RA that you are going to take the images (will move the probes but won't interfere with anything).
  • Retract the ACAM and CWFS
  • On a jove terminal Move the probes to the home5 position with the command home5
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • On a jove terminal Move the probes to the home3 position with the command home3
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • On a jove terminal Move the probes to the home1 position with the command home1
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move back to the home3 and home5 positions each in a row (this keeps the probes from getting confused and slow.
  • On a jove terminal Move the probes to the home8 position with the command home8
  • Save a few exposures which are not saturated with both WFS1 and WFS2.

OWFS on the blue sky as a function of rho

Purpose: We want to get an idea of how the orientation changes with rho.

Procedure:

  • Tell the RA that you are going to take the images (will move the probes but won't interfere with anything).
  • Retract the ACAM and CWFS
  • Move to center position 0,0,0,0,0 but select rho to be -20
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be -15
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be -10
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be -5
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be 0
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be +5
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be +10
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be +15
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • Move to center position 0,0,0,0,0 but select rho to be +20
  • Save a few exposures which are not saturated with both WFS1 and WFS2.

OWFS on the blue sky as a function of tracker position

Purpose: We want to get an idea of how the orientation changes with tracker position.

Procedure:

  • Tell the RA that you are going to take the images (will move the probes but won't interfere with anything).
  • Retract the ACAM and CWFS
  • Move to center position 0,0,0,0,0
  • Set exposure times so that WFS1 and WFS2 are not saturating
  • Turn off the loop and pipeline for WFS1 and WFS2
  • execute syscmd -v -T 'tracker_move_itf ( type="abs", vel="SLEW_FAST", x=0.0, y=0.0, z=0.0, theta=0.0, phi=0.0, rho=0.0 )'
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • execute syscmd -v -T 'tracker_move_itf ( type="abs", vel="SLEW_FAST", x=-1581.754294, y=0.0, z=93.8484821, theta=0.0, phi=-6.790973268, rho=0.0 )'
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • execute syscmd -v -T 'tracker_move_itf ( type="abs", vel="SLEW_FAST", x=1581.754294, y=0.0, z=93.8484821, theta=0.0, phi=6.790973268, rho=0.0 )'
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • execute syscmd -v -T 'tracker_move_itf ( type="abs", vel="SLEW_FAST", x=0.0, y=1581.754294, z=93.8484821, theta=6.790973268, phi=0.0, rho=0.0 )'
  • Save a few exposures which are not saturated with both WFS1 and WFS2.
  • execute syscmd -v -T 'tracker_move_itf ( type="abs", vel="SLEW_FAST", x=0.0, y=-1581.754294, z=93.8484821, theta=-6.790973268, phi=0.0, rho=0.0 )'
  • Save a few exposures which are not saturated with both WFS1 and WFS2.

start doing 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, B filter)
  • When you hit the correct flux level (biased to a slight higher value, perhaps 5k) execute the specialtwilight script

On-sky engineering:

Calibration of OWFS using either CWFS or DWFS8

Purpose: We want to calibrate the OWFS using DWFS8 or CWFS (depending on what stage of the testing we are in, Feedback from Hanshin) on a sidereal trajectory at one of the following Az:

a normal star for Az 180, 234, 292, 335, 0 We want two more sets of these Az to be complete.

  • setup on an 11 mag star on the IHMP
  • move all 4 guide probes to the correct RA and DEC positions from gstar or shuffle. NOTE: because of he recent FPA work you might need to alter gstar or use shuffle_config_matt2
  • save probe positions in the RA log with /home/mcs/astronomer/caldwell/shoprobes
  • If the test is to use DWFS8 then skip this step otherwise offset telescope and probes by the amount to get to CWFS: syscmd -T 'offset_trajectory(dx_ang=-5.5, dy_ang=-1.0, adjust_probes="true")'
  • move the guide probes so that the guide stars are well centered
  • guide with either GC1 or GC2
  • get decent focus and then check and correct any GROC
  • Retract ACAM
  • Open the PFIP shutter syscmd -P -v 'OpenShutter()'
  • null out the X, Y, Focus, Theta, Phi from DWFS8
    • To make X or Y offsets you will need to:
      • open the loop on the guider
      • make your offset with the handpaddle
      • clear the fiducial
      • watch as new fiducials are set to see if it looks good
      • close the loop on the guider
    • To make the Theta and Phi offsets you will need to:
      • open the loop on the TTC
      • make your offset with the handpaddle
      • clear the fiducial
      • watch as new fiducials are set to see if it looks good
      • close the loop on the TTC
    • The X and Y prescribed corrections are between -1 and 1.
    • The Theta and Phi prescribed corrections are between -10 and 10.
    • The Focus prescribed correction is between -0.05 and 0.05
  • make small offsets with the OWFS1 and OWFS2 to get the lenslet centered.
To move the wfs probes:
syscmd -T -v 'WFS1_offset_probe( dx_ang=1.0, dy_ang=0.0) '
syscmd -T -v 'WFS2_offset_probe( dx_ang=0.0, dy_ang=-0.5) '
The coordinates are in units of arcseconds.
  • save probe positions in the RA log with /home/mcs/astronomer/caldwell/shoprobes
  • save at least 15 images (at the same time) with all cameras that are running: GC1, GC2, WFS1, WFS2, DWFS8, TT NOTE: This can be done one jove terminal as startsaving followed by stopsaving
  • wait 10 minutes
  • null out corrections on DWFS8 or CWFS
    • NOTE: if you need to make X and Y offsets you should probably do this with a trajectory offset with probes=true to keep the WFS1 and WFS2 well centered
    • e.g. syscmd -T 'offset_trajectory(dx_ang=0.0, dy_ang=-0.3, adjust_probes="true")'
  • check GROC, make correction is required ( > 500 um correction)
  • null out corrections on DWFS8 or CWFS again if required
    • The X and Y prescribed corrections are between -1 and 1.
    • The Theta and Phi prescribed corrections are between -10 and 10.
    • The Focus prescribed correction is between -0.05 and 0.05
  • save at least 15 images (at the same time) with all cameras that are running: GC1, GC2, WFS1, WFS2, DWFS8, TT
  • repeat the last 5 steps until the end of the track.
  • Close the PFIP shutter syscmd -P -v 'CloseShutter()'

Repeat test: choosing a new star at the next Az in the list: 180, 234, 292, 335, 0. We want two more sets of these Az to be complete.

Science with LRS2-R and VIRUS Engineering

Purpose: LRS2-R is available for beware of grouped targets with LRS2-B.

Procedure:

  • NOTE: LRS2-R is in IFU slot 057
  • 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
  • Do a blind offset setup, ie. do_shuffle RA DEC 0 X 057 0 0 test
Last modified 8 years ago Last modified on Oct 26, 2016 3:01:18 AM