ObservatoryScope's proprietary Telescope
Automation Made Simple (TAMS) scripts make full automation and robotic
operation of the telescope extremely easy to do. TAMS supports a wide variety
of data formats for the target lines and includes a large selection of
directives which control how the data is obtained and how the instrumentation
is controlled. ObservatoryScope also has other proprietary scripts for
calibrating the telescope's drive systems, for automatically obtaining
calibration frames for the CCD camera, for checking and testing that all
equipment is properly hooked up, for automatically measuring and computing
corrections for the telescope's polar alignment and optic tilt, and for
simulating the operation of the observatory including the telescope and all
auxiliary equipment.
TAMS makes it easy for you and for students, for
example, to easily create a "plan file" for the following night's observations
during the day. Once the plan file is passed to TAMS, the computer will wait
until it is dark and then execute your plan file to autonomously obtain that
night's observations. So, you ask, just how easy is it to create a plan file
for an automated observing run with your ObservatoryScope? To answer this
question, let's look a a few practical examples which are shown below. Let's
assume you simply want to:
In the above examples, we highlighted the use of
just a few of the many directives which are available for controlling how image
data is acquired and now the telescope and the observatory is automatically
controlled. We could go into the details about large list of target list
formats which are supported, but this would require a few more pages of
documentation. Suffice it to say that a wide variety of target list formats are
supported and that custom target list formats can easily be added to TAMS at
any time for your specific needs.
You might be wondering what directives for target
acquisition and telescope control are currently available within TAMS. A
complete list follows of the fully tested and functional directives or
commands. These directives may be combined in your plan files to create
powerful fully automated imaging sequences for your ObservatoryScope.
DIRECTIVES These are commands which you can
add to your "plan file" for controlling the automated acquisition of target
data by TAMS. |
Description:
The plan file may contain "directive" lines which control
the image acquisition process. All directives begin with "#" followed by the
directive name and any required parameters. Directives are NOT case
sensitive.
NOTE: Virtually all directives which consist of more than one
word can be written with spaces between the words, hyphens between the words or
without either spaces or hyphens between the words. This feature makes it
easier when creating your plan files since you don't have to remember the exact
preferred syntax for each directive.
NOTE: Many directives require a
value after the directive. It is not necessary to put a space after the
directive and the directive's value, but doing so makes it easier to read your
plan files. Likewise, multiple spaces may be placed between the directive and
the directive's value which follows the directive.
NOTE: Any directives
which are not supported by TAMS, which were incorrectly typed in or which have
an incorrect value following the directive will be ignored and an appropriate
message will be displayed and logged.
Here are the currently implemented
directives which you may use in your plan files: |
| #SAY |
Allows you to display your own messages to ACP's
console and have these messages logged in the log file. Quotes are not used
around the text you want displayed and logged.
For example:
#SAY
This is Thursday night's observing run.
would display and log the
message "This is Thursday night's observing run. |
| #START |
Equivalent to #WAITUNTIL but with a simple time
format. Tells TAMS when to start processing any target lines and directives
which follow. Time is in simple 24 hour decimal or sexagesimal format based on
your computer's local time.
For example:
#START 18 #START
18.0 #START 18:00 #START 18:00:00 #START 18h00m00s
tells TAMS
to start at 6:00 p.m. local time.
#START can also be used later in the
plan file to delay execution of the remainder of the plan file. If used later
in the plan file, remember that it delays the rest of the plan file until the
local time is greater than #START. TAMS does check whether the #START is later
than #STOP. Scope will always park at the #STOP time, no matter
what. |
| #STOP |
Equivalent to #SHUTDOWNAT but with a simple time
time format. Can be placed anywhere within the plan file. Use only once. If
used more than once, then the last #STOP encountered in plan file becomes the
default stopping time for TAMS. Time is in simple 24 hour decimal or
sexagesimal format based on your computer's local time.
For
example:
#STOP 5.75 #STOP 5:45 #STOP 05:45 #STOP
5:45:00 #STOP 05:45:00 #STOP 05h45m00s
Tells TAMS to stop at 5:45
a.m. local time. |
| #CHILL |
Sets the camera cooler to the Celcius temperature
specified after the #CHILL directive.
For example:
#CHILL
-30
Tells TAMS to chill the camera cooler to a temperature of -30
degrees Celcius. |
#DOME-OPEN #DOME OPEN #DOMEOPEN |
Comands the dome or enclosure to open. This
directive is overridden if a weather monitoring station is installed which
indicates that it currently is not safe to open the dome or the
enclosure.
For example:
#DOME-OPEN #DOME
OPEN #DOMEOPEN
Tells TAMS to open the dome or enclosure if it is safe
to do so. |
#DOME-CLOSE #DOME CLOSE #DOMECLOSE |
Comands the dome or enclosure to close. This
directive will automatically park the telescope (if it is not already parked)
and close the dome or enclosure.
For
example:
#DOME-CLOSE #DOME CLOSE #DOMECLOSE
Tells TAMS to
park the scope, if necessary, and close the dome. |
| #SYNC |
Sync the telescope at the declination specified
after #SYNC or at the Standard Sync Position if nothing is specified after
#SYNC. If the telescope does not support hard syncs, then a soft sync is
performed and Sync Compensation is automatically used throughout the observing
run, whether or not UseSyncCompensation is enabled. DEC is in simple decimal or
sexagesimal format.
Directive may be used multiple times in your plan
file. A sync will be attempted up to 3 times to initially sync the scope.
Failure to find matching stars results in no sync of the scope and TAMS will
simply continue.
For example:
#SYNC
would sync the scope
at the Standard Sync Position.
#SYNC 35 #SYNC 35.0 #SYNC
35°00'00" #SYNC 35:00:00 #SYNC 35 00 00
would sync the scope
at +35 degrees declination. |
| #HOME |
This directive tells the telescope to slew and home
itself using its homing sensors.
For example:
#HOME |
| #AMBIENT |
This directive forces TAMS to use longer AutoFocus
intervals during the early part of a plan file. Use this directive if you are
using TAMS's Intelligent AutoFocus feature and the telescope is already cooled
down to ambient temp.
For example:
#AMBIENT |
| #SETS |
Tells TAMS to run the entire plan file a given
number of times. This directive is particularly useful if you wish to search
for comets and asteroids. The number of sets to take is specified using an
integer ranging from 2 to 999. The images within the entire plan are acquired
in round-robin order. This directive should be placed at the top of the plan
file, after any #START, #STOP or #SYNC directives, or unpredictable results
might occur. The set number, in "-000" format, would be appended to the target
name, followed by any #LOOP and #REPEAT appendages which would be added by
#LOOP or #REPEAT directives encountered while processing the remainder of the
plan file.
For example:
#SETS 3
would take 3 sets of every
target in the plan file.
NOTE: All relevant TAMS flags are reset to
their default values and all active directives are killed upon looping for the
next set. Therefore, all directives relevant to image acquisition should be
placed after the #SETS directive.
NOTE: Use #LOOP, #LOOP-UNTIL, #REPEAT,
#REPEAT-ALL directives for individual or groups of targets within a plan file
which you wish to image a number of times (see below). |
#TRACK-ON #TRACK ON #TRACKON |
Initiates orbital tracking of solar system bodies.
This directive remains in effect until cancelled by #TRACKOFF. Orbital tracking
will only be done for solar system bodies, so deep space targets may be
intermixed in your plan file without harm. Autoguiding is disabled if orbital
tracking is active since it is highly unlikely that the autoguider will lock on
to the moving target.
For
example:
#TRACKON #TRACK-ON #TRACK ON
Tells TAMS to
initiate orbital tracking. |
#TRACK-OFF #TRACK
OFF #TRACKOFF |
Cancels orbital tracking. This remains in effect
until re-enabled with #TRACKON.
For
example:
#TRACKOFF #TRACK-OFF #TRACK OFF
Tells TAMS to kill
orbital tracking. |
| #LOOP |
Similar to #SETS, except that #LOOP, when combined
with the #LOOP-END directive, allows multiple sets of images to be taken of a
group of targets within only part of a plan file. #LOOP - #LOOP-END directives
may be used multiple times within a plan file. As with the #SETS directive,
images are acquired in round-robin order. The loop number, in "-000" format
(the same format as #SETS to indicate round-robin image acquisition), would be
appended to the target name after any #SET appendage and before any #REPEAT
appendages.
For example: #LOOP 4
tells TAMS to loop 4 times
for all targets between the #LOOP and #LOOP-END directives.
NOTE: Unlike
the #SETS directive, TAMS flags are NOT reset and active directives are NOT
killed upon looping for the next set. This feature actually allows the you to
create simpler plan files. |
#LOOP-UNTIL #LOOP
UNTIL #LOOPUNTIL |
Similar to the #LOOP directive, except that TAMS
will loop until the specified time is reached. Hyphen or space is optional, in
case you forget it. Time is in simple 24 hour decimal or sexagesimal format
based on your computer's local time.
NOTE: The loop until time is only
checked at the beginning of each successive loop, thus assuring that the
currently running loop has completely finished, even if the current loop runs
past the specified loop until time.
Some examples:
#LOOP-UNTIL
1.5 #LOOP UNTIL 1:30 #LOOPUNTIL 01:30:00
tells TAMS to loop until
1:30am local time for all targets between the #LOOP-UNTIL and #LOOP-END
directives. |
#LOOP-END #LOOP END #LOOPEND |
Specifies the end location of a previous #LOOP or
#LOOP-UNTIL directive in a plan file. Hyphen or space is optional, in case you
forget it.
For example:
#LOOP-END #LOOP
END #LOOPEND
tells TAMS that this is the endpoint of the list of
targets looped by a #LOOP or #LOOP-UNTIL.
NOTE: Unlike #SETS, any active
directives are not reset to their defaults at the end of a loop. Remember to
kill any active directives, which you no longer wish to remain active, when
finishing the loop sequence or when looping for another loop. Kill any active
directives, either immediately before or after the #LOOP-END directive, as is
appropriate. |
| #REPEAT |
Take X number of images of the next target, as in
"repeat" until X number of images are acquired. The number of images to take is
specified with an integer ranging from 1 to 999. The sequence number, in "_000"
format (the "_" indicating sequential image acquisition), will be appended to
the target name after any #SETS and #LOOP appendages.
For
example:
#REPEAT 10
would take 10 images of the target and add a
sequentially numbered extension, starting with _001, to the target
name. |
#REPEAT-ALL #REPEAT
ALL #REPEATALL |
Take X number of images of subsequent targets.
Hyphen is or space optional, in case you forget it. Usage and syntax similar to
#REPEAT, above, except that this directive applies to all subquent
targets.
For example:
#REPEAT-ALL 10 #REPEAT ALL
10 #REPEATALL 10
would take 10 images of subsequent targets and add a
sequentially numbered extension, starting with _001, to each target
name. |
#REPEAT-END #REPEAT
END #REPEATEND |
Kills any #REPEAT-ALL directive currently in
effect. Hyphen or space is optional, in case you forget it.
For
example:
#REPEAT-END #REPEAT END #REPEATEND |
| #DIR |
Change the directory into which subsequent images
are to be stored. The directory is created if needed. At present, only ONE
subdirecory level may be created within an within an existing directory
structure.
For example:
#DIR
C:\Images\TonightsWork #DIRC:\Images\TonightsWork
will create, if
necessary, the specified path and save subquent images to this path. Notice
that in one of the above examples we forgot the space after the "#DIR"
directive. This is acceptable. |
#DIR-TEMP #DIR TEMP #DIRTEMP |
Temporary directory where to save subsequent images
such as reshoots, comets, etc. The currently active directory, before any and
all #DIR-TEMP directive(s) are encountered, is saved so that it can be restored
by using #DIR-END (see below). Hyphen or space is optional, in case you forget
it.
For example:
#DIR-TEMP D:\Reshoots\01-Oct-2001 #DIR
TEMPD:\Reshoots\01-Oct-2001 #DIRTEMP D:\Reshoots\01-Oct-2001
will
create, if necessary, the specified path and save subquent images to this path
on drive D. Notice that in one of the above examples we forgot the space after
the "#DIR TEMP" directive. This is acceptable.
NOTE: Any drive letter
substitutions you specify in your USER Constants file are NOT used with
#DIR-TEMP. Make sure the drive letter specified with #DIR-TEMP actually exists.
This particular functionality is specifically engineered into TAMS on
purpose! |
#DIR-END #DIR END #DIREND |
Kills a #DIR-TEMP directive currently in effect,
and the previous #DIR directive is restored. Hyphen or space is optional, in
case you forget it.
For example:
#DIR-END #DIR
END #DIREND
would restore the imaging directory to the most recent
directory before the #DIR-TEMP directive went into effect. |
| #INTERVAL |
Set the final target exposure interval in seconds
for subsequent targets in the list. May be used multiple times in the plan
file.
For example: #INTERVAL 30
NOTE: You can reset to the
default exposure interval by specifying #INTERVAL followed by
nothing.
For example:
#INTERVAL would reset the exposure
interval to the default exposure interval as defined in ACP. |
| #BINNING |
Sets the binning for subsequent images. If the
detector does not support the requested binning, the closest supported value
will be used. Auto Calibration is NOT performed for values other than the value
of the DefaultBinning constant, below.
For example:
#BINNING
2
NOTE: You can reset to the default binning with another #BINNING
followed by nothing.
For example:
#BINNING
would reset the
binning to the default binning as defined in the constants section,
below. |
#SUB-FRAME #SUB
FRAME #SUBFRAME |
Sets the fraction of the chip to be used for
subsequent images. Legal values range from 0.1 To 1.0 (full frame). For
example, if the chip size is 1K by 1K (1024 by 1024), a SUBFRAME of 0.5 will
result in using the center 512 by 512 pixels of the chip. Auto Calibration is
NOT performed for subframe values other than 1.
For
example:
#SUBFRAME 0.5 #SUB-FRAME 0.5 #SUB FRAME 0.5
NOTE:
All pointing exposures are ALWAYS performed using a full frame. The #SUBFRAME
directive only applies to science exposures.
NOTE: You can reset to
default the default subframe with another #SUBFRAME followed by
nothing.
For example:
#SUBFRAME #SUB-FRAME #SUB
FRAME
would reset the subframe to the default subframe. |
| #DARK |
Take a dark frame for the target using the current
exposure interval, binning and subframe settings. Multiple auto-numbered dark
frames can be taken by preceding the #DARK directive with a #REPEAT directive.
The dark frame(s) is saved in the currently active directory.
For
example:
#DARK
A sequence of dark frames will be taken only if
the #DARK directive is used in combination with the #REPEAT directive;
otherwise a single dark frame is taken.
For example:
#DIR-TEMP
C:\My_300sec_dark_frames; save them here #INTERVAL 300; take 300 second
darks #REPEAT 10; we want to take 10 dark frames #DARK #INTERVAL;
reset interval to default #DIR-END; switch back to previously active dir
would take 10 five minute darks, save them in C:\My_300sec_dark_frames,
then restore the default interval and restore the previously active directory
for future images. |
#AUTO-FOCUS #AUTO
FOCUS #AUTOFOCUS |
Slew to a star that is close to the zenith and
perform an AutoFocus before going to the next target in the plan file. Hyphen
or space is optional, in case you forget it.
For
example:
#AUTOFOCUS #AUTO-FOCUS #AUTO FOCUS
NOTE: This
directive is ignored, if this TAMS's Intelligent AutoFocus feature (automatic
focusing intervals) is enabled. This allows older plan files to be run with
TAMS, without having to remove the #AUTOFOCUS directives in the older plan
files, if you are using TAMS's Intelligent AutoFocus feature. |
#FOCUS #DO-FOCUS #DO
FOCUS #DOFOCUS |
Force an AutoFocus no matter what. Useful if using
TAMS's Intelligent Autofocus feature and you want to force an AutoFocus before
any specific targets or image sequences in your plan file. The hyphen, space or
"DO" is optional, in case you forget it.
For
example:
#FOCUS #DOFOCUS #DO-FOCUS #DO FOCUS |
#POINTING #POINT |
Schedule a pointing update for the next target.
Handy for reshoots to make sure that they are centered.
NOTE: #POINTING
or #POINT is also used to cancel a #POINT-ALL directive, or to cancel the
effect of a #POINT-NONE directive (see below) by restoring the defaults for
pointing updates.
For example:
#POINTING #POINT
would
schedule a pointing update for the next target, or would cancel a previous
#POINT-ALL or #POINT-NONE command currently in effect. A pointing update will
be performed, regardless, for the next target. |
#POINT-ALL #POINT
ALL #POINTALL |
Schedule pointing updates for all subsequent
targets. Hyphen or space is optional, in case you forget it.
For
example:
#POINT-ALL #POINT ALL #POINTALL |
#POINT-NONE #POINT
NONE #POINTNONE |
Cancel pointing updates for all subsequent targets.
Also used to kill a #POINT-ALL directive. Hyphen or space is optional, in case
you forget it.
NOTE: You can also check the "Disable all pointing
updates" checkbox in ACP's preferences dialog to disable pointing updates for
all plan files.
For example:
#POINT-NONE #POINT
NONE #POINTNONE
would cancel pointing updates or kill a previous
#POINT-ALL directive. |
| #FILTER |
Use the specified filter for subsequent images. The
value can be either a number or a filter name (as configured in MaxIm DL's
filter configuration window). The name is not case sensitive. If the number is
out of range, or the name is not one of the configured MaxIm filter names, then
the clear/empty filter (as set in ACP's preferences) is used instead. If no
filter wheel is present, the directive is ignored.
TAMS expects that the
clear, red, green and blue filters have names, beginning with certain
characters, assigned in MaxIm and in the separate USER_Constants file. Required
characters at the start of each filter name for these filters (not case
sensitive) follow, along with suggested names in [ ] (again, not case
sensitive).
Tricolor filter letters and names:
clear/empty filter
= C or L, [Clear or Luminance] red filter = R [Red] green filter = G
[Green] blue filter = B [Blue]
Photometric filter letters and
names:
ultraviolet filter = U [U] blue filter = B [B or Bu] visual
filter = V [V] red filter = R [R or Rc] near infrared filter = I [I or Is
or Iz or Ic]
The letter representing the filter color will be appended
to the filename using a "_" and the letter representing the filter color. The
filter letter is appended after the filename and again after any #SETS or
#REPEAT appendages. This allows for both sorting by image name and color in
Explorer, and for automatic color combining in MaxIm. MaxIm looks for the
letters R, G, B, and L at the end of the file names when combining images into
color.
For example, if filter #6 is the blue filter:
#FILTER
6 #FILTER Blue
would append _B to the target name and append _B after
any #SETS or #REPEAT appendages.
NOTE: If the clear/empty filter is
specified, then the clear filter name normally is not appended to the target
name. The #LRGB, #RGB, #LRGB-ALL and #RGB-ALL directives do append the
clear/empty filter name so you can easily sort and combine your tricolor
shots.
NOTE: As mentioned, #FILTER applies to subsequent images. If
tricolor (#LRGB, #RGB, #LRGB-ALL or #RGB-ALL) directives follow a #FILTER
directive, the filter color specified by the #FILTER directive will still be
active after finishing each tricolor directive or tricolor cancel directive
(#LRGB-END or #RGB-END).
NOTE: You can reset the filter wheel to the
clear or empty slot by using the #FILTER directive followed by
nothing.
For example:
#FILTER
would reset the filter to
the clear/empty filter. |
| #RGB |
Take an RGB color image of the next target only.
The letter representing the filter used will be appended to the filename in the
same fashion as the #FILTER directive.
For
example,
#RGB
would take tricolor images of the target and append
"_" followed by the filter color letter to the filename for each
color. |
#RGB-ALL #RGB ALL #RGBALL |
Takes RGB color images of all subsequent targets.
Hyphen or space is optional, in case you forget it.
For
example:
#RGB-ALL #RGB ALL #RGBALL |
#RGB-END #RGB END #RGBEND |
Kills any #RGB-ALL directive currently in effect.
Hyphen or space is optional, in case you forget it.
For
example:
#RGB-END #RGB END #RGBEND |
| #LRGB |
Take an LRGB color image of the next target only.
Similar to the #RGB directive, except that a luminance image is taken first,
followed by the RGB image sequence.
For
example:
#LRGB |
#LRGB-ALL #LRGB ALL #LRGBALL |
Take LRGB color images of all subsequent targets.
Hyphen or space is optional, in case you forget it.
For
example:
#LRGB-ALL #LRGB ALL #LRGBALL |
#LRGB-END #LRGB END #LRGBEND |
Kills any #LRGB-ALL directive currently in effect.
Hyphen or space is optional, in case you forget it.
For
example:
#LRGB-END #LRGB END #LRGBEND |
| #UBVRI |
Take UBVRI photometric data
for the next target only. Each filter color is used only if that filter color
is enabled in the user constants section. The letter representing the filter
used will be appended to the filename in the same fashion as the #FILTER
directive.
NOTE: Filter letters which are not configured in the USER
Constants file, either because you do not have them or wish to use them, will
be skipped.
For example:
#UBVRI |
#UBVRI-ALL #UBVRI
ALL #UBVRIALL |
Take UBVRI photometric data
for all subsequent targets. Hyphen or space is optional, in case you forget
it.
For example:
#UBVRI-ALL #UBVRI
ALL #UBVRIALL |
#UBVRI-END #UBVRI
END #UBVRIEND |
Kills any #UBVRI-ALL
directive currently in effect. Hyphen is optional, in case you forget
it.
For example:
#UBVRI-END #UBVRI
END #UBVRIEND |
| #CENTER |
Allow USER centering of the next target only. When
the telescope has reached the target, TAMS will pause, allowing you to use
ACP's nudge buttons or TheSky's buttons to compose the target. TAMS will alert,
asking you to continue once you have composed (centered) the target to your
liking. The scope position is recorded when you resume TAMS. The telescope will
automatically return to this position, even after an autofocus, during a long
tricolor image sequence.
For example:
#CENTER |
#CENTER-ALL #CENTER
ALL #CENTERALL |
Allow USER centering of all subsequent targets.
Hyphen or space is optional, in case you forget it.
For
example:
#CENTER-ALL #CENTER ALL #CENTERALL |
#CENTER-END #CENTER
END #CENTEREND |
Kill any #CENTER-ALL directive currently in effect.
Hyphen or space is optional, in case you forget it.
For
example:
#CENTER-END #CENTER END #CENTEREND |
#WAIT-FOR #WAIT FOR #WAITFOR |
Pause for the given number of seconds before
continuing to process the lines which follow in the plan file. Hyphen or space
is optional, in case you forget it.
For example:
#WAITFOR
30 #WAIT-FOR 30 #WAIT FOR 30 |
#WAIT-UNTIL #WAIT
UNTIL #WAITUNTIL |
Pause until the given UTC date/time if taking the
given set. If the given time has passed, of taking a different set, the
directive is ignored. The complete UTC date and time MUST be given! Note the
comma separating the set number and the wait-until time. Hyphen or space is
optional, in case you forget it.
For example:
#WAITUNTIL 1,
21-Apr-2001 08:02:00 #WAIT-UNTIL 2, 21-Apr-2001 08:32:00 #WAIT UNTIL 3,
21-Apr-2001 09:02:00
The above would wait till the given times in each
image set. This could be used to force a minimum interval between sets when
acquiring images for asteroid hunting. The date and time format is flexible,
and follows the standard formats for your PC's language and locale. For US
English, acceptable formats include:
7/1/01 08:22 07/01/2001
18:34:24 07-July-2001 06:34 PM |
#QUIT-AT #QUIT AT #QUITAT |
Set a "quitting time" at which TAMS will stop
acquiring images. Directive should be placed at the top of plan file before any
targets. The quitting time is in UTC format as above. Note that the scope is
not parked and the camera is not shut down, as with the #SHUTDOWNAT directive
described below. Hyphen or space is optional, in case you forget it.
For
example:
#QUITAT 7/1/01 08:22 #QUIT-AT 7/1/01 08:22 #QUIT AT
7/1/01 08:22
The UTC date/time format is flexible as described above. If
TAMS completes acquiring images before the quit time is reached, it exits as
usual. |
#SHUT-DOWN-AT #SHUT DOWN-AT #SHUT-DOWN
AT #SHUT DOWN AT #SHUT-DOWNAT #SHUTDOWN-AT #SHUT
DOWNAT #SHUTDOWN AT #SHUTDOWNAT |
Same as #QUITAT, except the scope is parked and the
camera is shut down at the quitting time, OR AT NORMAL EXIT of TAMS. Time is in
UTC format. Hyphens or spaces are optional, in case you forget them.
For
example:
#SHUTDOWNAT 7/1/01 08:22 #SHUT-DOWNAT 7/1/01 08:22 #SHUT
DOWNAT 7/1/01 08:22 #SHUTDOWN-AT 7/1/01 08:22 #SHUTDOWN AT 7/1/01
08:22 #SHUT-DOWN-AT 7/1/01 08:22 #SHUT-DOWN AT 7/1/01 08:22 #SHUT
DOWN-AT 7/1/01 08:22 #SHUT DOWN AT 7/1/01 08:22 |
#PARK #STOW |
May be placed anywhere in your plan file. This
command tells TAMS to park the telescope at the end of the run. Note that the
camera cooler is NOT turned off. Hyphen or space is optional, in case you
forget it.
For example:
#PARK #STOW |
#SHUT-DOWN #SHUT
DOWN #SHUTDOWN |
May be placed anywhere in your plan file. This
command tells TAMS to park the telescope, close the observatory and turn off
the camera cooler at the end of the run. Hyphen or space is optional, in case
you forget it.
For example:
#SHUTDOWN #SHUT-DOWN #SHUT
DOWN
Implemented in TAMS. |
| #CHAIN |
Use this directive to chain together plan files. If
TAMS is currently doing the last set when this directive is encountered, then
TAMS stops reading image acquisition lines from the current plan file, opens
the new plan file, resets the set counter, and begins reading from the new plan
file. If TAMS is NOT doing the last set, then TAMS will wait until it is
finished with the last set before executing this directive.
For
example:
#CHAIN C:\Program Files\ACP2\Plans\LateNight.txt
NOTE:
This directive should be placed at the end of the plan file's target
list.
NOTE: The #DIR, #START, #STOP, #QUITAT, and #SHUTDOWNAT directives
are retained from the previous plan file unless new #DIR, #START, #STOP,
#QUITAT or #SHUTDOWNAT directives are encountered in the new plan file. ALL
other active directives are immediately killed upon chaining to the new plan
file. |