wiki:NightOperations/Commissioning/Plans/20180505

20180505

Priorities

  • VIRUS twilight exposure (may need to pause or abort HPF cals)
  • High priority on sky Engineering tests
  • Priority 0 targets (HETDEX)
  • lower priority on sky engineering tests
  • Priority 1-3 targets
  • Closed dome engineering tests

High Priority Dome open engineering tests

Globular cluster NGC5272 dithering test

Purpose: There are two different reasons for this test 1) Look for orientation issues of the IFUs 2) Determine the difference that dithering and the guider orientation have upon each other, including probe position.

Procedure:

Note position 1 has already been done. Position two is the IHMP position.

Position 2 test:

Position: gstar 13:42:11.344 +28:22:44.26 83.3512 gc1

  • Observe this with iexp but change the following ngc5272_cw_gc2_000_E -texp 180 -dither
  • Setup on the globular cluster NGC5272 with IFU 000 target_setup -cat glob -ifu 000 6 E with probes false.
  • Once the track starts move the guiders to ccw positions mgp -radec -gc1=13:41:29.253,+28:25:27.07 -gc2=13:42:52.577,+28:18:44.82 -wf1=13:41:55.126,+28:13:27.87 -wf2=13:42:28.689,+28:31:59.01
  • Guide on GC1
  • Observe this with iexp but change the following ngc5272_ccw_gc1_000_E -texp 180 -dither
  • Switch to GC2
  • Observe this with iexp but change the following ngc5272_ccw_gc2_000_E -texp 180-dither
  • Now move the probes to center position mgp -radec -gc1=13:41:44.487,+28:16:04.55 -gc2=13:42:32.545,+28:31:05.43 -wf1=13:42:49.702,+28:18:04.13 -wf2=13:41:33.321,+28:26:54.08
  • Guide on GC1
  • Observe this with iexp but change the following ngc5272_center_gc1_000_E -texp 180 -dither
  • Switch to GC2
  • Observe this with iexp but change the following ngc5272_center_gc2_000_E -texp 180 -dither
  • Now move the probes to cw position mgp -radec -gc1=13:42:43.711,+28:15:54.87 -gc2=13:41:36.478,+28:27:36.90 -wf1=13:42:37.555,+28:30:28.33 -wf2=13:41:44.487,+28:16:04.55
  • Guide on GC1
  • Observe this with iexp but change the following ngc5272_cw_gc1_000_E -texp 180 -dither
  • Switch to GC2
  • Observe this with iexp but change the following ngc5272_cw_gc2_000_E -texp 180 -dither

Done with position 2

Now do position 3:

Position: gstar 13:42:10.45 +28:18:29.58 83.4785 gc1

  • Observe this with iexp but change the following ngc5272_cw_gc2_035_E -texp 180
  • Setup on the globular cluster NGC5272 with IFU 035 target_setup -cat glob -ifu 035 6 E with probes false.
  • Once the track starts move the guiders to ccw positions mgp -radec -gc1=13:41:30.216,+28:22:16.56 -gc2=13:42:54.236,+28:15:04.05 -wf1=13:41:57.536,+28:08:31.16 -wf2=13:42:26.202,+28:27:30.10
  • Guide on GC1
  • Observe this with iexp but change the following ngc5272_ccw_gc1_035_E -texp 180 -dither
  • Switch to GC2
  • Observe this with iexp but change the following ngc5272_ccw_gc2_035_E -texp 180 -dither
  • Now move the probes to center position mgp -radec -gc1=13:41:57.536,+28:08:31.16 -gc2=13:42:31.978,+28:27:02.99 -wf1=13:42:54.236,+28:15:04.05 -wf2=13:41:30.216,+28:22:16.56
  • Guide on GC1
  • Observe this with iexp but change the following ngc5272_center_gc1_035_E -texp 180 -dither
  • Switch to GC2
  • Observe this with iexp but change the following ngc5272_center_gc2_035_E -texp 180 -dither
  • Now move the probes to cw position mgp -radec -gc1=13:42:42.810,+28:13:19.76 -gc2=13:41:31.710,+28:24:10.86 -wf1=13:42:34.816,+28:26:15.11 -wf2=13:41:35.361,+28:12:10.91
  • Guide on GC1
  • Observe this with iexp but change the following ngc5272_cw_gc1_035_E -texp 180 -dither
  • Switch to GC2
  • Observe this with iexp but change the following ngc5272_cw_gc2_035_E -texp 180 -dither

Done with position 3

Low Priority Dome open engineering tests

ACAM stability test on sky

If we could track a star field on the ACAM along approximately the same track as was done for last night's test (AZ=70.1), while guiding, we should remove questions about the FCU moving and very importantly questions about small deflections of the WFC. Any WFC deflection will be followed by the guider and that will make any residual ACAM motion evident.

So, I wanted to get this on the agenda for the next time we are able to open. The test is:

  • Keep the ACAM inserted for the whole track
  • set up on a field that has a 14th mag star and hopefully some others that will allow shifts to be measured
  • guide using either GC1 or GC2 for the full track while taking ACAM images continuously.

Report the images saved, ie. start and stop time for the test. If you have time later in the night you might try using xregister on the frame using the 1st image as the reference.

Offsetting test

We have made some changes to the latency in the code involved with offsetting. Please setup on some stars and make some B->R offsets as well as some guide probe moves and fiducial moves.

Report any issues

Test sky brightness with g filter

A number of changes have been made to the sky brightness calculations.

Procedure:

  • Go on sky in an sdss field a little before center of track
  • setup all probes
  • make sure filters are set to g and clean is turned on
  • save some images through the center of the track. Report sky brightness value in night log or separate e-mail.
  • Note if the star mags make no sense then you might need another set of guide probe stars or it is to cloudy to evaluate.

Twilight i images

Take some twilight i band images with the guider with clean turned off for use as flat fields. Report images have been taken.

Gather some zero points for i images

This needs to be done when conditions are nearly photometric

Procedure:

  • Observe targets in the sdss fields and
  • look at the .cfg files for the iband magnitudes.
  • send these through the appropriate syscmd command to the guiders
  • save some images while near center of track and imaging through the i filters
  • look at the guider fits files to confirm that the i magnitudes are reported in the guide star magnitude array.

Closed dome engineering tests

ACAM stability with rho test

the ACAM motion is most likely due to the changing gravity vector due to rho motion rather than the smaller changes associated with the overall tracker motion, so we need to separate them. If the motion is entirely correlated with rho then it cannot be the FCU head moving,

Procedure:

  • set the tracker at X,Y=(0,0)
  • setup to image the FCU using the ACAM just like the insertion test
  • save an image
  • move the rho by 2 degrees
  • save an image
  • repeat the test over the full range of rho motion (+/- 18 degrees?)

Report the saved images or analyze them with xregister...

VIRUS cals

We have a new IFU installed and would like a set of VIRUS cals to evaluate it.

Offsetting test

We have made some changes to the latency in the code involved with offsetting. Please setup on some closed dome trajectories and make some B->R offsets as well as some guide probe moves and fiducial moves.

Report any issues

HPF cals

Practice taking HPF cals and take the morning set before 9 AM.

LRS2 cals

Last modified 6 years ago Last modified on May 5, 2018 4:21:44 AM