Table 1: EXECUTE_SUMMARY: Schedule and Execute information
EXECUTE_SUMMARY: Execute information

Name

Format

Units

Measure

Comments

Columns

Key

Data

TELESCOPE_NAME

String

Telescope name

CONFIG_NAME  

String

Name of the antenna configuration

NUM_ANTENNA  

Int

Number of antennas

ANTENNA_LIST  

Int(NUM_ANTENNA)

List of antenna identifiers

(BASE_RANGE)   

Float (2)

m

Minimum and maximum baseline lengths

(BASE_RMS)   

Float (2)

m

rms along the major and minor axis of the baselins distribution

(BASE_PA)   

Float

rad

Position angle of the major axis in the baseline distribution

TIME_RANGE

Double(2)

s

EPOCH

Start, end times

OBSERVER

String

Name of observers

LOG

String(*)

Observing log

SCHEDULE_ID  

int 

Scheduling Block identifier 

EXECUTEE_INTENT  

String(*)

Execute intent

EXECUTE  

String

Project execution

MAIN_ID  

Int(2)

Range of rows in the MAIN table

PROJECT

String

Project identification string

RELEASE_DATE

Double

EPOCH

Target release date

Flags

FLAG_ROW

Bool

The row flag


Notes: This table contains information specifying the observing instrument or epoch. It defines the list of EXECUTE associated to a given SCHEDULE and the list of SCHEDULE actually used for the project. It is indexed directly from the MAIN  table via the identifier EXECUTE_ID.
TELESCOPE_NAME
 
CONFIG_NAME
String type to support names with current instruments.
NUM_ANTENNA
Number of antennas (indicative) for the configuration.
ANTENNA_LIST
List of antenna identifiers to know which antennas belong to the current configuration
BASE_RANGE
Baseline range (min, max)
BASE_RMS
rms along the minor and major axis in the baseline distribution.
BASE_PA
Position angle in the distribution of baselines
TIME_RANGE
OBSERVER
LOG
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...
SCHEDULE_ID
Scheduling Block identifier. Not required to be unique.
EXECUTE_INTENT
Intent given for the execution of the SB. When the execution of a given SB is repeated the intent would be e.g. increaseUVcoverage, monitorVariability, increaseStoN etc... Not required to be unique.
EXECUTE
The same file name may be given here if what has been scheduled is exactly what has been executed. Not required to be unique. Each EXECUTE has to be notified in this table. It is indexed directly from the MAIN for a straightforward segmentation of whole data base into data blocks. EXECUTE_IDis used for data selection to define an Observation Unit (see the OBSERVATION_UNIT sub-table).
MAIN_ID
Range of identifiers (row numbers) in the MAIN  table corresponding to that EXECUTE. This is provided in this table to allow the user to access efficiently the section of interest in the MAIN  table.
PROJECT
 
RELEASE_DATE
FLAG_ROW
MAIN_ID
Lower and upper limits in the MAIN  table

Remark: CONFIG_NAME is added in this table. It would not be redundant with ARRAY_ID in the MAIN table. Since the ARRAY table does not exist any more, I propose to replace the non key attribute ARRAY_ID by SUBARRAY_NUM in the MAIN table. SUBARRAY_NUM would be used to discriminate observations obtained with different groups of antennas. CONFIG_NAME allows to discriminate observations from different epochs with antennas, from a few to all, at different locations. If the plan is that the array will be in continuous reconfiguration, then it will be quite common to have multi-configuration projects. CONFIG_NAME takes clearly its importance in this context. The list of antenna idenfiers, ANTENNA_LIST is also added; it allows to find which anttenas are being considered in the antenna configuration, this configuration being name in the second column of this table.  
N.B.: there would be as many rows in this table as there are executing blocks in the project. SCHEDULE_IDand EXECUTE are not required to be unique, as it would be the cases if a SB and an EXECUTE are repeated.