mansched [ parameter=value ... ]
Parameters are: satellite, telemetry, start_date, start_time, duration, orbit_number, archive_pass, dev_name, catalog_pass, up_process.
mansched manually enters scheduling parameters for the capture of a particular pass. In order to schedule the pass, mansched requires the satellite, telemetry, start date, start time (gmt), duration, orbit number, archive parameters and a post-processing script. From the information provided, mansched will determine if the pass is capturable, e.g. is the specified satellite visible from the receiving site at the specified time. If the pass cannot be captured, mansched reports so. If it can be, the specified capture process is scheduled.
This is the satellite name. It must be entered in lower case.
There is no default.
This is the data telemetry type. It must be entered in lower case.
The default is [ hrpt ].
This is the start date of the pass to be captured.
Any valid date is allowed.
Default is today's date.
This is the start time of the pass to be captured.
Any valid time is allowed.
Default is the current time.
This is the specified duration time of the capture process for the pass.
Any valid time is allowed.
The default is [ 00:15:00 ].
This is the satellite orbit revolution counter. Use 0 if the orbit number is unknown.
The valid range is [ >= 0 ].
The default is [ 0 ].
Specifies whether or not to autoarchive the pass.
Valid responses are [ yes or no ].
The default is [ yes ].
Specifies the target device to autoarchive the pass to.
Valid responses are any full name from the devtable.
The default is [ $TAPE ].
Specifies whether or not to catalog the pass after archiving it.
Valid responses are [ yes or no ].
The default is [ yes ].
Specifies the post processing script to invoke after the pass has been captured. The full pathname is required.
Valid responses are any alphanumeric string less than 128 bytes long.
The default is [ ].
Manually schedule the capture of a noaa-11 pass. Then list the capture schedule to confirm the updated schedule and make sure no conflicts developed. The information for this pass was obtained using the passes_in_view button of the xcapcon program.
[1] % mansched
satellite : char(11) ? noaa-11
telemetry : char(75) ? [hrpt]
start_date : char(15) ? [91/07/20]
start_time : char(15) ? [18:59:22] 22:27:50
duration : char(15) ? [00:15:00] 00:07:30
orbit_number : int ? [0]
archive_pass : char( 3) ? [yes]
dev_name : char(255) ? [/dev/ncwd0]
catalog_pass : char( 3) ? [yes]
up_process : char(255) ? [] /extra/getit
[2] % llsched
# status satel telem date day time durat post_process
1 scheduled noaa-11 hrpt 91/07/20 201 09:43:40 15:00 /extra/getit
archive pass catalog pass device_name
y y /dev/ncwd0
track frame auto_align mode abort ongoing
y y n n
# status satel telem date day time durat post_process
2 scheduled noaa-11 hrpt 91/07/20 201 22:27:50 07:30 /extra/getit
archive pass catalog pass device_name
y y /dev/ncwd0
track frame auto_align mode abort ongoing
y y n n
devtable, schedlist
It is possible to enter a pass twice into the schedlist or otherwise create conflicts which result in the skipping of scheduled passes. Always review the schedlist entires after running mansched. Also keep in mind that the autoscheduler may create conflicting schedule entries.
Last Update: $Date: 1999/05/10 20:14:50 $