autosched - add or replace autoscheduler records

autosched - Add or replace autoscheduler records

SYNOPSIS

autosched  [ parameter=value ]

Parameters are: receiver_lat, receiver_lon, telemetry, satellites, antenna, geost_hours, geost_start, geost_durat, min_rec_elev, master_file, min_trg_elev, min_sun_elev, priority, start_date, sched_days, start_time, one_time_only, replace_auto, rule_name, archive_pass, dev_name, catalog_pass, up_process.

DESCRIPTION

autosched is used to build automatic pass-scheduling records, which are stored in the file $PASSDIR/autosched. Each autosched record can reference exactly one telemetry, and a number of satellites that transmit that telemetry. Each satellite and its corresponding telemetries are defined in a Define file located in $PASSDIR/satel/satellite/Define.

Each autosched record refers to a specific antenna. The list of antennas and their corresponding telemetries is kept in the file $PASSDIR/config/antenna.config.

Rules for scheduling passes of polar orbiting satellites are based on master coverage. A master file is a TeraScan dataset that describes an area of the earth and its map projection. The center of the master is considered the pass target. If a master is not specified, the receiver site is considered the target.

The user specifies the minimum satellite elevation and the minimum sun elevation at the target. For a given pass, if the satellite elevation at the target never reaches the specified minimum, the pass is not scheduled. For a given pass, if the sun elevation at the target (at the time of maximum satellite elevation) is less than the specified minimum, the pass is not scheduled.

For polar orbiting satellites, pass duration is based on the minimum satellite elevation at the receiver, specified by the min_rec_elev parameter.

Rules for scheduling passes from geostationary satellites are based on hourly time intervals. For a given set of hours, the user can specify a start offset and pass duration in minutes and seconds; i.e., for each hour H, data is received from (H + offset) to (H + offset + duration).

autosched records can be perpetual or one-time-only. If a record is perpetual, the pass scheduling daemon tsched uses the record to update the list of scheduled passes $PASSDIR/schedlist, at intervals specified by the start_date, start_time, and sched_days parameters.

For a given perpetual autosched record, tsched schedules passes for the following intervals:

[start_date +0*sched_days +start_time, start_date +1*sched_days +start_time]
[start_date +1*sched_days +start_time, start_date +2*sched_days +start_time]
[start_date +2*sched_days +start_time, start_date +3*sched_days +start_time]
 ...

tsched increments the start_date field by sched_days each time it uses the record.

If a record is one-time-only, it is used to update schedlist once and is then discarded. It may never actually be stored in the autosched file.

Perpetual autosched records are automatically active to start. However, they can be deactivated via TeraCapCon or XCapCon without being removed from the file. The pass-scheduling daemon tsched ignores inactive autosched records.

Each autosched record can have a different name, specified by the rule_name parameter. These names are useful for identifying records for purposes of activation or deactivation.

It is possible to schedule passes that overlap in time. If two overlapping passes scheduled to be received via the same antenna (actually the same acc), there is a conflict.

The user can resolve conflicts by deleting schedlist records by editing schedlist pass start time and duration via TeraCapCon or XCapCon. Otherwise, conflicts are resolved as follows: (1) take the pass with the highest priority, otherwise (2) take pass with highest elevation relative to the receiver. The priority parameter is described below.

PARAMETERS

receiver_lat: Latitude of the receiver. The default is the current receiver position.

receiver_lon: Longitude of the receiver. The default is the current receiver position.

telemetry: Telemetry to receive. There is no default. The telemetry must appear in both the $PASSDIR/satel/satellite/Define file and the $PASSDIR/config/antenna.config file.

satellites: List of satellites to track. There is no default. Satellites are defined in the $PASSDIR/satel/satellite/Define file. Each satellite specified must transmit the telemetry specified by the telemetry parameter.

antenna: One-relative number of the antenna to use for reception. The default is 1, simply because most systems have only one antenna. The antenna/telemetry correspondence must be listed in the$PASSDIR/config/antenna.config file.

geost_hours: For geostationary satellites, a list of hours in the range [0, 23]. There is no default.

geost_start: For geostationary satellites, the start offset in minutes and seconds (mm:ss) from the top of the hour. The default is 00:00.

geost_durat: For geostationary satellites, the pass duration in minutes and seconds (mm:ss). The default is 15:00.

min_rec_elev: For polar orbiting satellites, the satellite elevation relative to the receiver at which data reception starts and stops. This determines pass duration. The valid range is 0 to 90. The default is 0.

master_file: For polar orbiting satellites, the name of a master file, the center of which is assumed to be the reference point from which satellite elevation and sun elevation are measured. If no master is specified, the receiver is assumed to be the reference point for elevation measurements. By convention, masters used for pass scheduling are stored in the directory $PASSDIR/masters.

min_trg_elev: Specifies the minimum elevation that the satellite must reach at its highest point during a pass in order for the pass to be included in the Cataloged pass list. A given satellite pass will be included in the list only if the satellite’s highest elevation above the horizon meets or exceeds the value entered. Elevation is measured in angular degrees.; If you have specified a master in the Master field, the center of the area defined by the master is the reference point from which satellite elevation is measured. Otherwise, your receiving site is the point from which satellite elevation is measured. The allowable range of values for this field is 0 to 90. The default is 0.

min_sun_elev: Specifies the minimum elevation that the sun must reach at its highest point during a satellite pass in order for the pass to be included in the Cataloged pass list. A given satellite pass will be included in the list only if the sun’s highest elevation above the horizon meets or exceeds the value entered. Elevation is measured in angular degrees.; If you have specified a master in the Master field, the center of the area defined by the master is the reference point from which sun elevation is measured. Otherwise, your receiving site is the point from which sun elevation is measured. The allowable range of values for this field is 0 to 90. The default is 0, which means that all daytime and nighttime passes will be considered. To indicate that you want daytime passes only, enter a value of 1. (It is not possible to specify nighttime passes only.)

priority: Priority of passes scheduled via this autosched record. A number in the range [1, 5]. The default is 5. The lower the number, the higher the priority.

start_date: The starting date for the autosched record. The default is today. If the record is perpetual, the start_date will be incremented by sched_days, every time the record is used to update the list of scheduled passes.

sched_days: The number of days in each autosched interval. The default is 1. The valid range is [1, 30], but for perpetual records, sched_days may as well be in the range [1, 2].

start_time: The start time for the autosched record. The default is 0 GMT. For polar orbiting satellites, it is best to specify a time when no satellites are present, e.g., for NOAA satellites, local noon (converted to GMT) is good.

one_time_only: Specifies that the record is to be used once, as opposed to being perpetual. The default is yes.

replace_auto: If the record is perpetual, indicates that the record will replace all other records in the autosched file. The default is yes.

rule_name: Convenient name for identifying the autosched record in other programs. The default is the master name for polar orbiting satellites. The default is blank for geostationary satellites.

archive_pass: Determines whether or not passes scheduled by this record will be automatically archived after reception. The default is yes.

dev_name: If archive_pass=yes, this is the name of the tape device to use for archiving. The default is $TAPE. The tape device must be listed in the file $PASSDIR/devtable.

catalog_pass: If archive_pass=yes, this parameter specifies whether or not archived passes are to be cataloged in $PASSDIR/passcat. The default is yes.

up_process: The name of the program or shell script to run during/after pass reception. The default is blank, meaning no processing. By convention, these scripts or programs are stored in the directory $PASSDIR/postprocs, though this is not required.

FILES

autosched, schedlist, onlinecat, passcat, devtable

NOTES

It may seem like a good idea to base pass duration for polar orbiting satellites on master size, rather than on minimum satellite elevation at the receiver. This is currently not the case.

Most sites use the receiver as the target, scheduling as many satellite passes as are viewable from the receiver, and archiving each pass. Application targets are not necessarily known at the time of pass reception.

Still, in order to resolve conflicts, it should be possible to trim the pass start time and duration, so only the part of the pass covering the master area is received.

Last Update: $Date: 1998/10/17 22:51:35 $