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
  Overview
  Instructions for
  ACP/PinPoint/
  MaximDL users
  Instructions for
  TheSky/CCDSoft/
  Orchestrate users
  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
Daily Operation



The daily operation of an automated observatory using TAO involves several actions, such as starting the observatory control software, updating target databases, scheduling and carrying out observations. These actions are described in detail in the next sections.


Step 1: Starting the observatory control software

Overview

As discussed in another section, observations scheduled with TAO may be executed on automated observatories which are controlled by either ACP/PinPoint/MaxIm DL CCD or TheSky/CCDSoft/Orchestrate. Other observatory control programs may also be used, provided they are supported in a custom version of TAO.

It is recommended that the observatory control software be run on a dedicated computer (not the same computer which is used to produce observation schedules). This allows the user to schedule observations while the observatory control computer is executing such tasks as taking calibration frames and science images, slewing the telescope, etc. Observatory control software often behaves unreasonably if it is run simultaneously on the same computer with CPU-intensive programs such as the scheduler. Besides, image downloading often causes the CPU to "freeze" during the process, which would be inconvenient if scheduling and other tasks are run on the observatory control computer.

The observatory control software is assumed to be running by the time the scheduled observations are due to start; one would normally start the observatory control software some time before the observations are due to begin, possibly in daytime. If you use a remote observatory through the Internet, you may use some remote-control software (such as TightVNC, pcAnywhere, or Microsoft's Remote Desktop) to start the observatory control software on the remote computer. ACP users could also start the TAO image acquisition script through ACP's built-in web interface, although this provides less flexibility than a remote-control program. Depending on the observatory's level of automation, you may need assistance from some person at the observing station for tasks such as opening a roll-off roof, turning telescope and computers on, synchronizing the telescope to the celestial sphere, and establishing Internet connections.

Either the target list or the Orchestrate scripts produced by the TAO scheduler need to be transferred to a suitable directory on the observatory control computer before the scheduled time for the start of the observations. If the observatory control computer and the computer used to produce observation schedules are on the same local network, the target list or the Orchestrate scripts may simply be copied from one computer to the other over the network. If you use a remote observatory, you will need to use a FTP client program to upload the target list or the Orchestrate scripts to the observatory control computer (or some other computer on the observatory's local network). This in turn requires that a FTP server program be running on some computer on the observatory's local network. Among the great variety of available FTP client programs, BulletProof FTP Client is particularly useful due to its ability to continuously monitor a specified directory for new files, and download them automatically as they appear. This feature allows one to automatically download image files in real time during the night. Serv-U and BulletProof FTP Server are two reliable and affordable FTP server programs. ACP users may also use the FTP server built into ACP.

Note: Two problems which are often encountered when configuring a remote observatory for Internet access are:

  1. How to determine the observatory computer's IP address when the ISP assigns a different IP address each time the computer connects to the Internet. Knowing the IP address is necessary for establishing FTP or remote-control connections to the observatory computer.
  2. How to ensure that the observatory computer automatically connects to the internet after it is rebooted, and that it tries to reconnect whenever the connection is lost.
The first problem may be effectively solved by using the DNS2Go service to register fixed domain names (such as sirius.dns2go.com) which will always point to the observatory computer despite its changing IP address. A good solution to the second problem is to use the free program 1st Dialer.

Previous: Station data, user profiles
Next: Instructions for ACP/PinPoint/MaximDL CCD users



© 1999-2004 Paulo Holvorcem