Tools for Automated Observing
  Previous page
  Next page
  System requirements
Getting Started
  Modeling slew times
  Measuring camera
  download times
  Specifying filter
  names and numbers
  Modeling the local
  Creating user profiles
  Initializing target
  Customizing the
  Parameters of the
  Potential targets
  Scripting system
  Focus breaks
  Aiming exposures
  Station data
  User profiles
Daily Operation
  Starting observatory
  control software
  Updating target
  Generating a list of
  potential targets
  Preparing a list of
  observation requests
  Running the
  Starting scheduled
Image Acquisition with
the MU Script
  Customizing the
  Starting MU
  Sequence of events
  during an observing
  run using MU
Timing Refinement
  Collecting timing
  Analyzing timing
  Adjusting the
  empirical timing
Other Tools
  Slew time
  measurement script
  Minor Planet Checker
  query script
  Regression program
  Software updates
  License agreement
  Contact the author
Getting started

Step 8: Customizing the scheduler (continued)

Potential targets

  Targets directory:                                                  c:\TAO\targets
  Default list of potential targets:                                  c:\TAO\targets\targets.txt

This section specifies the location of the TAO target database and the default list of potential targets:

  • Targets directory. Specify the path of the TAO\targets directory. The path may be absolute (e.g., c:\TAO\targets or relative to the TAO\schedule directory (e.g., ..\targets).

  • Default list of potential targets. When program Schedule is run, it will read a list of potential targets produced by program Targets. Only targets which appear on this list can be scheduled for observation. A new list of potential targets is normally generated before each observing run. It would normally have the same file name on every night. You may specify a default path for this list, so that you don't need to specify the list of potential targets in the command line when running the scheduler. The path may be absolute (e.g., c:\TAO\targets\targets.txt or relative to the TAO\schedule directory (e.g., ..\targets\targets.txt). You may wish to wait until you run program Targets for the first time to specify the name of your default list of potential targets.

Scripting system

SCRIPTING SYSTEM (O=Orchestrate, A=ACP):                              A

Specify the scripting system you will use to control your telescope. The currently supported scripting systems are Orchestrate and ACP. If you use Orchestrate, this option should be set to "O" (the upper-case letter, not the number zero). If you use ACP, this option should be set to "A".

Orchestrate parameters

ORCHESTRATE PARAMETERS (Orchestrate users only):
  Directory for saving scripts:                                       c:\TAO\orchestrate_scripts
  File containing final commands:                                     FinalCommands.txt
  Use WaitUntil command in first script? (yes/no)                     no

This section contains options which are only useful for Orchestrate users. If you do not use Orchestrate, you can skip to the next section.

  • Directory for saving scripts. If you use Orchestrate, the scheduler will produce as output a number of text files, each one containing a short Orchestrate script which will command the telescope and camera to take one exposure. An example script file is shown below:

    WaitFor     ,     0                ,
    SlewToRADec , 10.14949h -86.68404d , C/2002 Y1   
    WaitFor     ,     2                ,
    SetResolution, Medium, 
    SetFrameMode, Light, 
    TakeImage   ,   180                , C/2002 Y1   

    This option of the scheduler configuration file specifies the path of a directory where your Orchestrate scripts will be saved. The path may be absolute (e.g., c:\TAO\orchestrate_scripts or relative to the TAO\schedule directory (e.g., ..\orchestrate_scripts).

  • File containing final commands. This option specifies a (possibly empty) text file containing a set of Orchestrate commands to be executed after the last exposure of the scheduled observing run is taken. For example, the sample file TAO\schedule\FinalCommands.txt contains the command

    SlewToAzAlt, 270d00m00s 45d00m00s ,    

    which moves the telescope to a point at azimuth 270 deg and altitude 45 deg.

  • Use WaitUntil command in first script? If you answer yes, the first Orchestrate script will contain a WaitUntil command, instructing Orchestrate to wait until the run's scheduled start time to begin executing the scripts. If you answer no, you must start the run yourself at the scheduled start time.

Previous: Equipment parameters
Next: Focus breaks, aiming exposures

© 1999-2004 Paulo Holvorcem