Science Operations

Operating TMS (updated)

Update (Oct 12, 2023):

Starting in 2023B, a software service running in the background will automatically switch between FPIA and TMS. After the observer has started the TMS active loop, they will not need to interact with TMS again until the LBC observations are finished. When they run FPIA (dofpia or dohybrid), TMS will automatically be stopped, and when FPIA converges successfully, a TMS reference will automatically be taken and the TMS loop resumed.

In this mode of operation, FPIA should no longer be run from the IDL window, but from a terminal window at the Linux shell prompt, using a slightly modified command syntax. The old syntax used commas to separate keywords, e.g. IDL> dofpia, /x2, whereas the new syntax uses the double-dash to indicate keyword options, e.g. obs1> dofpia --x2

This web page was updated on October 12, 2023 to reflect the new procedure with the background FPIA/TMS service.

Quick Review

  1. Turn on the TMS lasers and send an email to telescopework@lbto.org to let everyone know the lasers are ON. Instructions can be found at this link.
  2. Login to robs as user telescope and change directory to the one where the TMS scripts are located.
    1. ssh -X telescope@robs
    2. cd /lbt/lbto/supportscripts/MetrologySupport
  3. If there is a recent, good, reference, use it to get started (see Using the last good reference as a starting point… below):
    1. Copy it (4 files) to /tmp
      1. cp /home/telescope/TMS_logs/<YYYYMMDD>/telescope_*_tmsoffset.dat /tmp
      2. cp /home/telescope/TMS_logs/<YYYYMMDD>/tms_[s,d]x_ref.dat /tmp
    2. Run the active loop to position M1 to it:
      1. ./tms_loop.py for binocular operation (the default)
      2. ./tms_loop.py -s 0 for operation only with LBCB on SX
      3. ./tms_loop.py -s 1 for operation only with LBCR on DX
  4. Start “watcher” scripts. These are helpful because they show the TMS corrections that are being sent (labelled active) or reasons why TMS corrections are not sent (mirror or telescope moving, shutter open). Run each in its own, small, terminal window on telescope@robs:
    1. ./watch_tms_left.py
    2. ./watch_tms_right.py
  5. (Optional) Start LBTplot to monitor TMS corrections
    1. ssh -X telescope@robs  (it may suffice just to run it from robs – TBC)
    2. LBTplot and look for SXTMS and DXTMS tabs near the top right
  6. From here on, observe as usual with the LBCs, with the exception that dofpia/dohybrid will now be run from the Linux terminal window. The steps are outlined below for convenience:
    1. Slew to the copointing target for your first field. Stop the OB and wait for a TMS update before proceeding either:
      1. to take the pair of copointing images (from which you can assess image quality); or
      2. to run FPIA.
    2. run dofpia if necessary (TMS should hold collimation over slews and over time, so dofpia may not be necessary).
      1. The following examples are meant to illustrate the syntax. See Observing Procedure –> Collimating for all of the options which dofpia and dohybrid can take.
        • dofpia --askme --x2
        • dohybrid
        • dofpia --backout
    3. In IRAF, run lbcrangebal to correct pointing & copointing
      1. Note that with TMS running, these pointing and copointing corrections may be larger than normal (see the Notes section below).
  7. Slew to your target. Stop the OB and wait for a TMS update before starting the first exposure (look in the "watcher" script output for the first line marked "active"). Once you see the update, play the OB.
  8. Notes:
    1. WARNING: After you slew to a new field, always wait for a new TMS update before starting to take an exposure. (This is noted in red above, and worth repeating).
    2. To know whether TMS is sending updates, look for a new line with "active" printed to the terminal by the ./watch_tms_[left,right].py script
    3. For very low elevation targets, it is better to collimate at higher elevation where the seeing is better (~65-75 deg, though not > 80 deg because, here, rotational trailing may be an issue). Then set the reference and run the TMS loop to hold the collimation as you slew to the lower elevation target.
  9. After finishing the LBC observations:
    1. Stop the TMS loop (control-C in the terminal window where you launched tms_loop.py).
    2. Turn the TMS lasers off and send an email to telescopework@lbto.org to let everyone know that the lasers are now off.

Using the last good reference as a starting point

Be aware that an old reference will not work if the channels used for it do not match the currently available channels. This may result:

  1. if VXWorks has gone down, causing a mirror panic (a special case of mirror panic).
  2. If work near the primary has accidentally disturbed one or more collimators.
  3. from damage to any of the fibers

Troubleshooting

  1. If there are problems taking the reference:
    1. Check for missing channels. TMS requires at least 6 channels, at least 1 and no more than 4 on each of the 3 retroreflectors that are mounted on the LBC.
      1. Missing channels may be due to a misalignment. This has been known to occur after power bumps when the mirror goes down. If this is the cause, then the collimators will need to be realigned during the day.
      2. Missing channels may also result from system malfunction. Recent cases like this have been resolved by power cycling the TMS cabinet.
  2. If no corrections are being sent, check for missing channels in the screen output from tms_loop.py.
    1. But be aware that, TMS will not send corrections when:
      1. the LBCs are exposing;
      2. telescope is slewing;
      3. mirrors are moving;
      4. dofpia or dohybrid is being run.
  3.  The first pointing/copointing corrections after setting the collimation from an old reference may be large (Large enough to violate or warn about violating the copointing limit). If in doubt, retake the copointing pair (when this has happened, the repeated images have shown that the pointing and copointing corrections were made).

References

More detailed information about TMS operation can be found at this wiki page and links therein. This page provides the syntax for running the TMS loop in engineering modes.

PSF GUIs (with TMS corrections labelled)