User's Guide

SCHEDIT

Schedule Editor

Function:

Allows editing of the master acquisition schedule. Entries may be added to the schedule using the -ADD subcommand. Entries may be deleted by a range of dates using the -DELETE or by scene ID using the -DELBYSID subcommand. Entries in a specified date range may be modified using the -MODIFY subcommand. Entries in a specified date range and from a specified receiving station may be modified using the -MODBYSTA subcommand. Entries with a specified scene ID may be updated using the -MODBYSID subcommand. A brief or full listing of the schedule may be generated using the -LIST subcommand. The schedule may be sorted by ascending starting acquisition time using the -SORT subcommand.

Parameters:

Subcommand -ADD:
Add entries to the schedule. Entries will be added to the schedule describing the date, time, satellite, orbit, and type of acquisition.

SATID
Satellite ID. The satellite that acquired the data. This routine will schedule acquisitions from NOAA satellites 10, 11 and 12.

  = N10:  NOAA-10
  = N11:  NOAA-11
  = N12:  NOAA-12
  = N14:  NOAA-14
  = N15:  NOAA-15
  = N16:  NOAA-16

ORBIT
Orbit number. The orbit number of the pass.

ASTADATE
Acquisition start date. The starting date of the acquisition. Three values should be entered as (month date year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTODATE(--)
Acquisition stop date. The ending date of the acquisition. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTATIME
Acquisition start time. The starting time of the acquisition. Three values should be entered as (hour minute second).

ASTOTIME
Acquisition stop time. The ending time on the ending date of the range of entries to be updated. Three values should be entered as (hour minute second).

PSTADATE(--)
Pass start date. The starting date of the pass, if different than the starting date of the acquisition. This may occur for LAC or GAC data, when a pass is recorded at one time and received at a different time. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

PSTODATE(--)
Pass stop date. The ending date of the pass, if different than the starting date of the pass. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g. 86 or 1986).

PSTATIME(--)
Pass start time. The starting time of the pass. Three values should be entered as (hour minute second).

PSTOTIME(--)
Pass stop time. The ending time of the pass. Three values should be entered as (hour minute second).

OPCODE(1)
Operation code. A code representing the type of data transfer scheduled.

  = 0 :  No data will be acquired.
  = 1 :  Data is transferred from dish to disk.
  = 2 :  Data is transferred from dish to tape.
  = 3 :  Data is transferred from dish to both disk 
         and tape.
  = 5 :  Data is transferred from tape to disk.

STATUS("P")
Acquisition status. This is a single character code indicating the status of the acquisition.

  = D :  Data was received on disk.
  = T :  Data was received on tape.
  = B :  Data was received on disk and tape.
  = P :  Data is pending.
  = M :  Data was missed.
  = N :  Data will not be acquired.

HDTRFILE(0)
HDTR tape file number. The number indicating the location of the file on the HDTR tape. If a pass is not on tape, the tape file location should be set to 0.

PRODFLAG(".")
Product order flag. This flag indicates the type, if any, of product ordered from this acquisition. If no product was ordered, PRODFLAG should be set to "." (a period).

STATION("SFL")
Station ID. The station that originally received the data.

  = SFL :  EROS Data Center, Sioux Falls, SD
  = NGC :  Fairbanks, Alaska
  = NOA :  Wallops Island, Virginia

ATYPE("HRPT")
Acquire type. The type of data to be acquired.

  = HRPT:  High Resolution
           Picture Transmission
  = LAC :  Local Area Coverage
  = GAC :  Global Area Coverage
Subcommand -DELETE:
Delete schedule entries. All entries within the specified date range are deleted from the schedule.

ASTADATE
Acquisition date range start. The first date in the range of dates for which entries in the schedule will be deleted. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTODATE(--)
Acquisition date range stop. The ending date in the range of dates for which entries in the schedule will be deleted. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTATIME
Acquisition time range start. The starting time on the starting date of the range of entries to be deleted. Three values should be entered as (hour minute second).

ASTOTIME
Acquisition time range stop. The ending time on the ending date of the range of entries to be deleted. Three values should be entered as (hour minute second).
Subcommand -DELBYSID:
Delete schedule entries by scene ID. The entry matching the specified scene ID is deleted from the schedule.

SCENEID
Scene ID. The scene ID is used to identify the schedule record to be deleted.
Subcommand -MODIFY:
Modify schedule entries. All entries within the specified date range are updated with the specified fields.

ASTADATE
Acquisition date range start. The first date in the range of dates for which entries in the schedule will be modified. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTODATE(--)
Acquisition date range stop. The ending date in the range of dates for which entries in the schedule will be modified. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTATIME
Acquisition time range start. The starting time on the starting date of the range of entries to be modified. Three values should be entered as (hour minute second).

ASTOTIME
Acquisition time range stop. The ending time on the ending date of the range of entries to be modified. Three values should be entered as (hour minute second).

SATID(--)
Satellite ID. The satellite that acquired the data. This routine will schedule acquisitions from NOAA satellites 10, 11 and 12. If NULL, this field will not be updated.

  = N10:  NOAA-10
  = N11:  NOAA-11
  = N12:  NOAA-12
  = N14:  NOAA-14
  = N15:  NOAA-15
  = N16:  NOAA-16

OPCODE(--)
Operation code. A code representing the type of data transfer scheduled. If NULL, this field will not be updated.

  = 0 :  No data will be acquired.
  = 1 :  Data is transferred from dish to disk.
  = 2 :  Data is transferred from dish to tape.
  = 3 :  Data is transferred from dish to both disk 
         and tape.
  = 5 :  Data is transferred from tape to disk.

STATUS(--)
Acquisition status. This is a single character code indicating the status of the acquisition. If NULL, this field will not be updated.

  = D :  Data was received on disk.
  = T :  Data was received on tape.
  = B :  Data was received on disk and tape.
  = P :  Data is pending.
  = M :  Data was missed.
  = N :  Data will not be acquired.

HDTRFILE(--)
HDTR tape file number. The number indicating the location of the file on the HDTR tape. If a pass is not on tape, the tape file location should be set to 0. If NULL, the HDTRFILE field will not be updated.

PRODFLAG(--)
Product order flag. This flag indicates the type, if any, of product ordered from this acquisition. If no product was ordered, PRODFLAG should be set to "." (a period). If NULL, the PRODFLAG field will not be updated.

STATION(--)
Station ID. The station that originally received the data. If NULL, this field will not be updated.

  = SFL :  EROS Data Center, Sioux Falls, SD
  = NGC :  Fairbanks, Alaska
  = NOA :  Wallops Island, Virginia

ATYPE(--)
Acquire type. The type of data to be acquired. If NULL, this field will not be updated.

  = HRPT:  High Resolution
           Picture Transmission
  = LAC :  Local Area Coverage
  = GAC :  Global Area Coverage

ORBIT(--)
Orbit number. The orbit number of the pass. If NULL, the orbit field in the record will not be updated.
Subcommand -MODBYSTA:
Modify schedule entries by station and date range. All entries within the specified date range for the specified receiving station are updated with the specified fields.

ASTADATE
Acquisition date range start. The first date in the range of dates for which entries in the schedule will be modified. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTODATE(--)
Acquisition date range stop. The ending date in the range of dates for which entries in the schedule will be modified. Three values should be entered as (month day year), where year is a two-digit or four-digit integer (e.g., 86 or 1986).

ASTATIME
Acquisition time range start. The starting time on the starting date of the range of entries to be modified. Three values should be entered as (hour minute second).

ASTOTIME
Acquisition time range stop. The ending time on the ending date of the range of entries to be modified. Three values should be entered as (hour minute second).

UPSTA(--)
Update station. The station for which scheduled scenes will be modified. If NULL, the scenes for all receiving stations in the specified date range will be updated.

  = --:  All stations.  Entries in the specified date
         range will be updated regardless of 
         receiving station.
  = SFL :  EROS Data Center, Sioux Falls, SD
  = NGC :  Fairbanks, Alaska
  = NOA :  Wallops Island, Virginia

SATID(--)
Satellite ID. The satellite that acquired the data. This routine will schedule acquisitions from NOAA satellites 10, 11 and 12. If NULL, this field will not be updated.

  = N10:  NOAA-10
  = N11:  NOAA-11
  = N12:  NOAA-12
  = N14:  NOAA-14
  = N15:  NOAA-15
  = N16:  NOAA-16

OPCODE(--)
Operation code. A code representing the type of data transfer scheduled. If NULL, this field will not be updated.

  = 0 :  No data will be acquired.
  = 1 :  Data is transferred from dish to disk.
  = 2 :  Data is transferred from dish to tape.
  = 3 :  Data is transferred from dish to both disk 
         and tape.
  = 5 :  Data is transferred from tape to disk.

STATUS(--)
Acquisition status. This is a single character code indicating the status of the acquisition. If NULL, this field will not be updated.

  = D :  Data was received on disk.
  = T :  Data was received on tape.
  = B :  Data was received on disk and tape.
  = P :  Data is pending.
  = M :  Data was missed.
  = N :  Data will not be acquired.

HDTRFILE(--)
HDTR tape file number. The number indicating the location of the file on the HDTR tape. If a pass is not on tape, the tape file location should be set to zero. If NULL, the HDTRFILE field will not be updated.

PRODFLAG(--)
Product order flag. This flag indicates the type, if any, of product ordered from this acquisition. If no product was ordered, PRODFLAG should be set to "." (a period).

STATION(--)
Station ID. The station that originally received the data. If NULL, this field will not be updated.

  = SFL :  EROS Data Center, Sioux Falls, SD
  = NGC :  Fairbanks, Alaska
  = NOA :  Wallops Island, Virginia

ATYPE(--)
Acquire type. The type of data to be acquired. If NULL, this field will not be updated.

  = HRPT:  High Resolution
           Picture Transmission.
  = LAC :  Local Area Coverage.
  = GAC :  Global Area Coverage.

ORBIT(--)
Orbit number. The orbit number of the pass. If NULL, the orbit field in the record will not be updated.
Subcommand -MODBYSID:
Modify schedule entries by the scene ID. The schedule entry with matching scene ID will be updated with the specified fields.

SCENEID
Scene ID. The scene ID is used to identify the schedule record to be modified.

SATID(--)
Satellite ID. The satellite that acquired the data. This routine will schedule acquisitions from NOAA satellites 10, 11 and 12. If NULL, this field will not be updated.

  = N10:  NOAA-10
  = N11:  NOAA-11
  = N12:  NOAA-12
  = N14:  NOAA-14
  = N15:  NOAA-15
  = N16:  NOAA-16

OPCODE(--)
Operation code. A code representing the type of data transfer scheduled. If NULL, this field will not be updated.

  = 0 :  No data will be acquired.
  = 1 :  Data is transferred from dish to disk.
  = 2 :  Data is transferred from dish to tape.
  = 3 :  Data is transferred from dish to both disk 
         and tape.
  = 5 :  Data is transferred from tape to disk.

STATUS(--)
Acquisition status. This is a single character code indicating the status of the acquisition. If NULL, this field will not be updated.

  = D :  Data was received on disk.
  = T :  Data was received on tape.
  = B :  Data was received on disk and tape.
  = P :  Data is pending.
  = M :  Data was missed.
  = N :  Data will not be acquired.

HDTRFILE(--)
HDTR tape file number. The number indicating the location of the file on the HDTR tape. If a pass is not on tape, the tape file location should be set to zero. If NULL, the HDTRFILE field will not be updated.

PRODFLAG(--)
Product order flag. This flag indicates the type, if any, of product ordered from this acquisition. If no product was ordered, PRODFLAG should be set to "." (a period).

STATION(--)
Station ID. The station that originally received the data. If NULL, this field will not be updated.

  = SFL :  EROS Data Center, Sioux Falls, SD
  = NGC :  Fairbanks, Alaska
  = NOA :  Wallops Island, Virginia

ATYPE(--)
Acquire type. The type of data to be acquired. If NULL, this field will not be updated.

  = HRPT:  High Resolution
           Picture Transmission
  = LAC :  Local Area Coverage
  = GAC :  Global Area Coverage

ORBIT(--)
Orbit number. The orbit number of the pass. If NULL, the orbit field in the record will not be updated.
Subcommand -LIST:
List the schedule. A formatted listing of the schedule is sent to the appropriate destination.

PRINT(TERM)
Output destination. The destination of the schedule listing.

  = TERM:  Output is sent to the user's terminal.
  = LP  :  Output is sent to the printer defined by 
           $PRINTER.
  = FILE:  Output is sent to the user-supplied file 
           with the extension ";prt".

LISTOPT(BRIEF)
List option. The type of schedule listing to generate.

  = BRIEF:  Only schedule entries with OPCODE 1, 2, 
            3, or 5 (an actual data transfer) are 
            listed.
  = LONG:   All schedule entries are listed.
Subcommand -SORT:
Sort schedule by start acquisition time. The schedule will be sorted by ascending acquisition start time. No parameters are required.

Examples:

  1. LAS> schedit-add satid=n11 orbit=14112 astadate=(6 21 91) astatime=(18 33 16) astotime=(18 36 55) pstadate=(6 15 91) pstodate=(6 16 91) pstatime=(23 52 08) pstotime=(1 07 08) opcode=3 status=p hdtrfile=2 station=noa

    An entry will be added for an acquisition on 6/21/91 from 18:33:16 to 18:36:55. The pass time of the acquisition is from 23:52:08 on 6/15/91 to 00:07:08 on 6/16/91. It has a pending status and will be written to both disk and HDTR tape when acquired. The acquisition will be file two on the HDTR tape. The receiving station is Wallops Island.

  2. LAS> schedit-delete astadate=(5 3 91) astodate=(5 4 91) astatime=(1 10 00) astotime=(23 59 59)

    All entries between 01:10:00 on 5/3/91 and 23:59:59 on 5/4/91 will be deleted from the schedule.

  3. LAS> schedit-delbysid sceneid=ah11040391133623

    The entry for scene AH11040391133623 will be deleted from the schedule.

  4. LAS> schedit-modify astadate=(6 22 91) astatime=(16 19 27) astotime=(16 29 46) status=m station=noa orbit=14125

    The schedule entries for all acquisitions on 6/22/91 between 16:19:27 and 16:29:46 will be updated as "missed" acquisitions, with STATION "Wallops Island" and ORBIT 14125.

  5. LAS> schedit-modbysta astadate=(6 01 91) astodate=(6 30 91) astatime=(04 12 07) astotime=(16 29 46) upsta=sfl status=m

    All schedule entries between 04:12:07 on 6/01/91 and 16:19:27 on 6/30/91 from the EROS Data Center receiving station will be updated as "missed" acquisitions.

  6. LAS> schedit-modbysid sceneid=al11050192113701 status=b hdtrfile=4

    The schedule entry for scene AL11050192113701 will be updated to indicate that it was received on tape and disk, and its HDTR file number is four.

  7. LAS> schedit-list

    A brief listing schedule will be sent to the user's terminal. Only the acquired and yet-to-be acquired entries will be listed.

  8. LAS> schedit-sort

    The schedule will be sorted by ascending acquisition start time.

Description/Algorithm:

SCHEDIT is an interactive program which allows the user to update the master acquisition schedule. Multiple sets of parameters may be entered in one editing session. When all parameter sets have been entered, EXIT from the tutor screen. The schedule will then be updated with all of the information at once.

The information in the schedule includes the scene ID, satellite name, orbit number, acquisition start and stop time, pass start and stop time, operation status (e.g., received, pending, missed), the HDTR tape file number, a product order flag, the receiving station (EDC, Fairbanks, or Wallops Island), and the data type of the acquisition.

New entries to the schedule may be added using the -ADD subcommand. Entries may be deleted from the schedule using the -DELETE subcommand (based on range of time) and -DELBYSID subcommand (based on scene ID). Entries may be modified by range of time (the -MODIFY subcommand), by scene ID (the -MODBYSID subcommand), or by range of time and receiving station (the -MODBYSTA subcommand). The schedule may be listed to a terminal, printer, or file using the -LIST subcommand. It may be sorted using the -SORT subcommand. The schedule file is locked during updating to prevent multiple users from updating it at the same time.

Nonfatal Error Messages:

  1. [schedit-dayn] Error occurred setting day/night indicator for <xxx> acquisition Setting indicator to DAY

    An error occurred while checking if the acquisition with start time xxx is a day or night pass. The flag was set to DAY. Ensure the satellite's ephemeris file is up to date, because the ephemeris information is used to calculate whether the pass is day or night.

  2. [schedit-duprec] Duplicate record found, <xxx> not entered

    When trying to add to the schedule, a record was found with the same starting time. The record with the specified scene ID was not added to the schedule.

  3. [schedit-nodel] No records to be deleted

    When trying to delete from the schedule using the -DELETE subcommand, no records were found that fell within the specified date range. No records were deleted from the schedule.

  4. [schedit-nomod] No records to be modified

    When trying to modify the schedule using the -MODIFY or -MODBYSTA subcommand, no records were found that matched the search specification. No records were modified.

  5. [schedit-noscene] Record with scene ID <xxx> not found

    When modifying the schedule using the -MODBYSID subcommand or when deleting from the schedule using -DELBYSID, the record with the specified scene ID was not found and updated.

Fatal Error Messages:

  1. [schedit-aopen] Error opening acquisition input file

    An error occurred opening the input file used to update the master schedule. Ensure this file exists in the current working directory.

  2. [schedit-argc] Invalid number of arguments

    An invalid number of arguments was supplied when SCHEDIT was called. Rerun SCHEDIT with two arguments: processing option and input/output file.

  3. [schedit-fatal] Fatal error encountered

    A fatal error has occurred. The preceding message describes the error encountered.

  4. [schedit-find] Error retrieving value of ADAPSTABLES

    The value for the ADAPSTABLES directory could not be retrieved. Ensure the environment variable is set to the directory which contains the master schedule.

  5. [schedit-maxrec] The maximum number of master schedule records has been reached

    The master schedule has reached its maximum size of 600 records, and no more records may be added. Delete old or unused records to allow room for new ones.

  6. [schedit-mopen] Cannot open the master schedule file

    An error occurred opening the master schedule file. Ensure the file exists in the ADAPSTABLES directory with the correct permissions.

  7. [schedit-noup] Master schedule was not updated

    The updates in this session were not saved to the master schedule file. Check that the schedule allows write permission. The updates are saved in a temporary file in the current directory. The update may be retried by running SCHEDIT from the system prompt (see User Note 1).

  8. [schedit-rcp] Error copying master schedule to current system

    An error occurred copying the master schedule from the acquisition system to the current system for listing. Contact the System Administrator if the problem persists.

  9. [schedit-ropen] Error opening report file <xxx>

    An error occurred opening an output file for the -LIST subcommand. Check that the current working directory allows write permission.

User Note:

  1. The master schedule is maintained on the scheduling computer system (indicated by the variable SCH_SYS). If SCHEDIT is run to modify the schedule on another computer system, all updates will be sent to the SCH_SYS and will be applied to the master schedule there. If SCHEDIT-LIST is run on another computer system, the master schedule will be copied from the SCH_SYS to the current system, a listing will be generated, and the local copy of the schedule will be deleted. If SCHEDIT is run on SCH_SYS and a fatal error occurs, the user may try to run it again from the system prompt if the necessary update file still exists. On UNIX systems, $ADAPSBASE must be in the user's path. The following is a list of commands to update the schedule corresponding to SCHEDIT subcommands:

       -ADD       type: schedit -af add_170499234643.sch
       -MODIFY    type: schedit -mf modify_170499234643.sch
       -MODBYSID  type: schedit -ms modsid_170499234643.sch
       -MODBYSTA  type: schedit -ma modsta_170499234643.sch
       -DELETE    type: schedit -df delete_170499234643.sch
       -DELBYSID  type: schedit -ds delsid_170499234643.sch
       -LIST      type: schedit -rb my_output.file      (brief)
                    or: schedit -rl my_output.file      (long)
    
       (where "170499234643" is a unique time stamp)