SCHEDULE Schedule characteristics.

Name

Format

Units

Measure

Comments

Columns

Data

SCHEDULE_INTENT

String Schedule intent

SCHEDULE_TYPE

String Schedule type

SCHEDULE_DURATION

Float s Approximate duration if executed

SCHEDULE

String Scheduling Block

NUM_SCAN

Int Number of different scans Nscan in this Scheduling Block

SCAN_INTENT

String( Nscan) Intent of each scan in the Scheduling Block

OBSERVING_MODE

String(*) Observing mode

Notes: This table contains the list of scheduling blocks generated by observation preparation tools. A summary of informations is attached to each scheduling block. It is indexed directly in the EXECUTE_SUMMARY table. The associations of Scheduling Blocks for processing are defined in the OBSERVATION_UNIT table using lists of SCHEDULE_ID identifiers.
SCHEDULE_INTENT
Goal of Scheduling Block (SB). Several SBs may share a common SCHEDULE_INTENT.
SCHEDULE_TYPE
The schedule type, with the current reserved types VLBA-CRD1  VEX2  WSRT3  ATNF4 For ALMA the reserved type(s) are TBD.
SCHEDULE_DURATION
Approximate duration which would be required to execute this SCHEDULE.
SCHEDULE
Unmodified schedule file, of the type specified, and as used by the instrument.
NUM_SCAN
Number of SCANs defined for the scheduling.
SCAN_INTENT
List of intents with these different SCANs.
OBSERVING_MODE
Observing mode, e.g. singleField, mosaic (origin: OT) One SB cannot have more than one observing mode Example: FS (for FastSwitching), RC (for with radiometric corrections), FSRC (for both FS and RC), mosaicingPointed, mosaicingOTF etc.

Remarks:

  1. Note that the same SCAN may be executed in different SCHEDULEs! This suggests to have a SCAN sub-table and a reference here via a list of SCAN_ID.
  2. This table could be generated at the stage of the preparation of the projects while the observations have not yet started.