|
|
|
Step 5: Running the scheduler
(continued)
Schedule output
The scheduler produces the following output files:
Log file. This is a transcript of the screen output, listing the requests
which were inserted in the scheduler, as well as the ones which could not be inserted.
The name of the log file is obtained from the name of the text file containing the
list of observation requests by changing its extension to .log.
For example, if the observation requests are contained in file
TAO\schedule\myRequests.stg, the log file will be
TAO\schedule\myRequests.log. A sample log file is shown
below:
Configuration file: myTelescope.cfg
Selected targets: 040814.stg
Output file (schedule): 040814.sch
Initial request number: 1
Potential targets: c:\TAO\targets\targets.txt
Start: 2004-08-14 22:30 UT
End: 2004-08-14 08:05 UT
Processing BC55427 (user=PRH). Request # 13 of 34
Processing search field ( 0, 0)... Successful.
Processing BC55384 (user=CGD). Request # 14 of 34
Processing search field ( 0, 0)... Successful.
Inserted 6 out of 6 requested exposures in time series.
Processing search field ( -1, 0)... Successful.
Inserted 6 out of 6 requested exposures in time series.
Processing search field ( 1, 0)... Successful.
Inserted 5 out of 6 requested exposures in time series.
Processing BC56702 (user=PRH). Request # 16 of 34... Successful.
Processing BC56703 (user=PRH). Request # 17 of 34
Processing search field ( 0, 0)... Successful.
Processing BC55289 (user=CGD). Request # 18 of 34
Processing search field ( 0, 0)... Successful.
Processing BC54817 (user=CGD). Request # 19 of 34... Successful.
Processing 2004 FU162 (user=PRH). Request # 24 of 34
Processing search field ( 0, 0)... Successful.
Processing search field ( -1, 0)... Successful.
Processing search field ( 1, 0)... Successful.
Processing search field ( -2, 0)... Successful.
Processing search field ( 2, 0)... Successful.
Processing 2000 BP27 (user=PRH). Request # 25 of 34... Failed.
Processing 2003 XR153 (user=PRH). Request # 26 of 34... Successful.
Processing 1998 RB4 (user=CGD). Request # 27 of 34... Successful.
Processing 2004 PY42 (user=CGD). Request # 28 of 34... Successful.
Processing 2001 KT (user=PRH). Request # 29 of 34... Successful.
Processing 2004 PR4 (user=PRH). Request # 30 of 34... Successful.
Generating summary of schedule... Finished.
Generating target list... Finished.
|
Scheduler summary. This is a text file which summarizes the observing schedule
in a form suitable for human inspection. The name of the scheduler summary file is
obtained from the name of the text file containing the
list of observation requests by changing its extension to .sch.
For example, if the observation requests are contained in file
TAO\schedule\myRequests.stg, the scheduler summary file will be
TAO\schedule\myRequests.sch. A sample scheduler summary
file is shown below:
|
OBSERVING SCHEDULE:
Start: 2004-08-24 21:54 UT (MJD 53241.91250)
End: 2004-08-25 08:26 UT (MJD 53242.35139)
User Images Total time used Exp. time used
PRH 257 325.7 min ( 51.53%) 267.0 min
VAR 205 282.4 min ( 44.68%) 205.0 min
Focus 11 19.8 min ( 3.13%)
Idle 4.1 min ( 0.66%)
Total 473 632.0 min (100.00%) 472.0 min
Observation requests: 269
Waiting time after slews: 2.0 sec
Slew Exposure Exp. Idle
Start (MJD) Start (MJD) UT Object RA dec HA alt (sec) (sec) Type Field dRA (h) ddec (deg) User Res. Mode Size Filter Req. ID File
53241.91181 53241.91184 21:53 Focus Break 0.00 0 FOCUS 0.000000E+00 0.00000E+00 1 l 1 10 (clear )
1 53241.91306 53241.91309 21:55 2000 XK18 19.4 -19 -144 56 60.00 0 E PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 1 l 1 2 (R ) C422-1 K00X18K.elm
2 53241.91402 53241.91444 21:57 2004 JB12 17.7 -16 -41 78 60.00 0 E PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 2 l 1 7 (V ) C410-1 K04J12B.elm
3 53241.91521 53241.91659 22: 0 U CEN 12.6 -55 272 31 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
4 53241.91751 53241.91770 22: 1 NCRU 2003 12.4 -60 284 29 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
5 53241.91863 53241.91877 22: 3 W CRU 12.2 -59 297 28 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
6 53241.91970 53241.91986 22: 5 HD 104994 12.1 -62 305 27 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
7 53241.92079 53241.92208 22: 8 2004 JB12 17.7 -16 -30 80 60.00 0 E PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 2 l 1 7 (V ) C410-1 K04J12B.elm
8 53241.92286 53241.92327 22:10 2000 XK18 19.4 -19 -129 60 60.00 0 E PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 1 l 1 2 (R ) C422-1 K00X18K.elm
9 53241.92420 53241.92543 22:13 RT CRU 12.6 -65 284 29 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
10 53241.92637 53241.92766 22:16 2004 JB12 17.7 -16 -22 81 60.00 1 E PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 2 l 1 7 (V ) C410-1 K04J12B.elm
11 53241.92844 53241.93049 22:20 C/2003 F1 17.0 -23 25 84 60.00 0 W PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 1 l 1 2 (R ) C409-1 CK03F010.elm
12 53241.93142 53241.93318 22:24 2000 XK18 19.4 -19 -115 63 60.00 0 E PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 1 l 1 2 (R ) C422-1 K00X18K.elm
13 53241.93428 53241.93605 22:28 C/2003 F1 17.0 -23 33 82 60.00 15 W PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 1 l 1 2 (R ) C409-1 CK03F010.elm
14 53241.93697 53241.93775 22:30 WX CEN 13.2 -63 264 31 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
15 53241.93868 53241.93883 22:32 Y MUS 13.1 -66 272 30 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
16 53241.93976 53241.94001 22:34 UW CEN 12.7 -55 297 28 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
17 53241.94093 53241.94180 22:36 C/2003 F1 17.0 -23 41 80 60.00 0 W PUBL ( 0, 0) 0.000000E+00 0.00000E+00 PRH 1 l 1 2 (R ) C409-1 CK03F010.elm
18 53241.94272 53241.94347 22:39 T APS 13.9 -78 229 29 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
19 53241.94440 53241.94499 22:41 RX CEN 13.9 -37 236 38 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
20 53241.94592 53241.94604 22:42 RT CEN 13.8 -37 240 37 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
21 53241.94696 53241.94749 22:44 S APS 15.2 -72 161 36 60.00 0 W FIXED ( 0, 0) 0.000000E+00 0.00000E+00 VAR 1 l 1 10 (clear ) Fixed.txt
...
|
|
The initial lines of the scheduler summary file give the start and end times
of the scheduled observing run, and a summary of telescope usage by each user (number
of requested images, telescope and exposure time used, expressed both in minutes and
as a percentage of the duration of the observing run). The amount of telescope time which
is not assigned to any observation (idle time) is also displayed.
The telescope schedule is specified by a table which lists each observation to be performed
in chronological order, including the following information:
- Image or script number.
- Times when the telescope will start slewing toward the target
(Slew Start) and when the camera's shutter will be opened
(Exposure Start); this last time is given both as a Modified
Julian Date and as a UT time in the format hh:mm.
- Target name (Object).
- Approximate target right ascension (RA, in hours),
declination (dec, in degrees), hour angle (HA, in minutes), and altitude
(alt, in degrees).
- Exposure time (Exp.).
- Idle time
(Idle) before the telescope starts moving
toward the target. Ideally, most of these idle times should be zero, and the longest
non-zero
idle times should not be greater than a few minutes. If you see a large "hole" in the
schedule, that is, a large chunk of idle time, you might try to add more requests to the
list of observation requests, so as to keep the telescope busy during
the formerly idle period. The newly requested targets should be at a sufficiently high
altitude during the time period corresponding to the "hole" one wishes to fill. Note that
requests for single images (such as supernova search images) are easier to insert in
a nearly filled telescope schedule than requests for sequences of 3 or more images (such as
those used in asteroid or comet astrometric follow-up).
- The side of the meridian where the observation will be performed
(E = East, W = West).
- Target classification in the target database (Type).
- Position of the field-of-view within a search mosaic (Field). In a
search mosaic, each field is specified by a pair
of integers (i,j) which indicates the offset of the field with
respect to the nominal position of the target. For observation requests which do
not specify a search mosaic, the single field-of-view is centered at the target's
nominal position, corresponding to field (0,0).
- Offsets (dRA, ddec) to
be applied to the target's nominal ephemeris position (in the case of solar system targets)
or to the target's nominal coordinates (in the case of other targets) when pointing the
telescope, before starting the exposure. These offsets will be zero except for
requests which specify a search mosaic.
- User name.
- Camera binning factor (Res.).
- Frame mode (Mode). Possible values are l = light, d = dark.
- Frame size (Size). Possible values are 1 = full frame,
2 = center subframe.
- Filter number and name.
- Request identifier.
- Name of the file in directory TAO\targets
which contains the position or ephemeris of the target.
Previous: Running the scheduler
Next: Schedule output (continued)
© 1999-2004 Paulo Holvorcem
|
|