This is meant to capture the current process of sending a preset with LUCI+ARGOS, from the perspective of the telescope operator.

The ARGOS dichroic obstructs much of the off-axis guider patrol field outside of the LUCI 4' field. It is also fixed with respect to the telescope structure. Thus, any available space on the rotating patrol field may track into an obstructed area.

(For completeness, I've included the old and new ways of sending presets. Consider the newest methods the best unless otherwise noted)

METHOD #1 (<20151218 - monocular):

The way around this problem has been to put the guide probe on-axis during the preset, then once complete, move the probe out of the way.
  • Send ACE_ACTIVE preset from LUCI, probe on-axis.
  • When ready*, stop guiding (GCSGUI). This drops the preset down to ACE_TRACK, which is what we need.
  • home probe.
  • Have one of the ARGOS team members 'skip wait for collimation' on the LUCI TelescopeService GUI. This manually triggers an AcquireRefAO.
  • ARGOS team takes over closing the loop.
  • Begin science exposures.
*Ready means:
Reasonably collimated. I have found it easier to point/collimate nearby first (you can use off-axis guide stars, so long as they aren't too far from center; Coordinate move with Laser Operator). Alternatively, you can let collimation continue, but you want to stop guiding before the WFS RMS drops low enough to trigger an AcquireRefAO (LUCI waiting for collimation flag). This will fail if the probe is in the way. You can stop guiding before the preset completes - I've been doing it when PresetAO is triggered, after guiding is stable.

METHOD #2 (20151219 - monocular):

  • Send ACTIVE preset from LUCI TelescopeService GUI, probe on axis.
  • collimate until you're happy
  • refresh the pointing paddle GUI to get the current orientation of IE/CA, and then from the acquisition image, estimate the pointing correction to get the star closer to the hotspot (to help with ARGOS alignment). Cancel preset, apply estimated pointing correction.
  • Send ACE_TRACK from LUCI TelescopeService GUI
  • proceed with science script.

METHOD #3 (20151219 - monocular):

  • Prior to going to a new target, clear active optics on M1 and M2. ARGOS builds up pointing drift onto the optics, and so a large pointing change offsets their lasers with respect to the optical alignment of the telescope
  • Point and collimate nearby (you can use off-axis guide stars, so long as they aren't too far from center).
    • Alternatively, the observer may have a collimation star near their target you can use on-axis
  • Send ACE_TRACK from LUCI TelescopeService GUI
  • proceed with science script

METHOD #4 (20160316 - monocular or binocular):

  • We know that when they move their bayside stages autonomously (to automatically center the target on their CCD47), this get accumulated as a pointing drift in the 'Secondary Offload' buffer of the primary mirror. This is fallout from the usage of ACE_TRACK, which is susceptible to telescope pointing drift. The stages get reset to the center of their ranges on a new preset. The operator needs to remove the accumulation from the optics between presets:
    • Open PSF > Primary > Position Details subGUI
      • Click 'Remove Corrections' under the 'Secondary Offload' section. This should remove any uncleared built-up drift between presets
    • (If needed) find a pointing star near to their target, correct pointing
    • Have the observer run the observing script (which should contain an ACTIVE preset followed by an ACE_TRACK preset)
      • Note that running PseudoMono mode has problems, since PresetAO will fail on the passive side
  • If the target drifts off of their CCD47 during offsets (causing the ResumeAO to fail), do the following:
    • Record initial IE/CA (from the start of the preset), you'll need this for later
    • Have them use the spiral tool to find the star on CCD47, Their baysides will center it up automatically from there
    • continue science script
    • Revert IE/CA and clear 'Secondary Offload' on a new preset

There are plenty of special cases that crop up. These instructions will surely change, so use them as a guideline with caution.

-- %USERSIG{SteveAllanson - 2016-03-16}%


Topic revision: r8 - 17 Mar 2016, SteveAllanson
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback