TAO
Tools for Automated Observing
  Previous page
  Next page
 
Introduction
  System requirements
 
Getting Started
  Installation
  Modeling slew times
  Measuring camera
  download times
  Specifying filter
  names and numbers
  Modeling the local
  horizon
  Creating user profiles
  Initializing target
  databases
  Customizing the
  scheduler
 
Daily Operation
  Starting observatory
  control software
  Updating target
  databases
  Generating a list of
  potential targets
  Preparing a list of
  observation requests
  Running the
  scheduler
  Starting scheduled
  observations
 
Image Acquisition with
the MU Script
  Customizing the
  script
  Starting MU
  Sequence of events
  during an observing
  run using MU
 
Timing Refinement
  Collecting timing
  data
  Analyzing timing
  data
  Adjusting the
  empirical timing
  correction
 
Other Tools
  Slew time
  measurement script
  Minor Planet Checker
  query script
  Regression program
 
Etc.
  Software updates
  License agreement
  Contact the author
Image acquisition with the MU script



Starting MU

To start an observing run using the MU script, follow these steps:
  • Start ACP and establish a connection to the telescope (Telescope -> Connect). If another program (such as PC-TCS) is used in conjunction with ACP to control the telescope, you may need start it before starting ACP. If TheSky is used in conjunction with ACP, it should automatically start and connect to the telescope when you click on Telescope -> Connect in ACP. If your telescope does not remain synchronized with the celestial sphere between successive observing runs, you will also need to re-synchronize it before establishing the connection from ACP to the telescope.

  • Click the Browse button in ACP, and select the script MU.vbe on the observatory control computer.

  • Click on the Main button to start the script.

When the MU script is started, it creates a subdirectory with a name of the form \yymmdd_telescopeName (where yymmdd is the UT date of the observing run and telescopeName is the name of the telescope as specified in MU.cfg) inside the directory specified by parameter obsDir in MU.cfg. For example if you have specified the value of obsDir as the directory C:\TAO\obs, MU will create a subdirectory C:\TAO\obs\yymmdd_telescopeName.

Notes:

  1. The UT date which serves to identify a night's observing run is defined as the UT date of the sunrise which immediately follows the end of the night at the observing station.
  2. If the telescope name is defined as an empty string in MU.cfg, the above subdirectory will have a name of the form \yymmdd.

The script will also create two files in subdirectory \yymmdd_telescopeName:

An accounting log file will also be created by MU when it starts. This file records every science image taken during the night, along with the ID of the user for whom it was taken, the amount of telescope and exposure time used, and other information. The accounting log file will be located in a subdirectory \Accounting, inside the directory specified by parameter userDir in MU.cfg. For example if you have specified the value of userDir as the directory C:\TAO\users, the accounting log will be stored in C:\TAO\users\Accounting. The accounting log file will have a name of the form Accounting_yyyymmdd_telescopeName.log.

Previous: Aiming exposure parameters
Next: Sequence of events during an observing run



© 1999-2004 Paulo Holvorcem