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

Name

Format

Units

Measure

Comments

Columns

Data

TELESCOPE_NAME

String

Telescope name

CONFIG_NAME  

String

Name of the antenna configuration

NUM_ANTENNA  

Int

Number of antennas

ANTENNA_ID_SET  

Int(NUM_ANTENNA)

List, unsorted, 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 set of EXECUTE blocks associated to each SCHEDULE block; this forms the list of SCHEDULE actually used for the project. It is indexed directly from the DRAFT_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.
N.B.: It must be understood that this number does not necessarily corresponds to the number of rows in the ANTENNA  table; it may be smaller but never larger.
ANTENNA_ID_SET
Collection of a set of antenna identifiers ANTENNA_ID to know the ensemble of antennas which belong to the current array configuration. These identifier do not need to be given in a specific order but obviously this collection cannot contains two or more elements which are have the smae value. N.B.: If there are sub-arrays the subsets of antennas used for each sub-array is specified in the CONFIG_DESCRIPTION  table. The present list does not assumes that there is cross-correlation for some or all the antenna pairs which can be considered based on the antennas present in this collection.
BASE_RANGE
Baseline range (min, max). Baseline must be understood here as a eventualy a pure abstraction. For example it could be used to indicate the sampling when generating the phase structure function. The range is one property of this sampling.
BASE_RMS
rms along the minor and major axis in the baseline distribution. This provides an other characteristic of the array configuration.
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... ??? CECI EST EN CONTRADICTION AVEC OBSMODE QUI EST DANS LA TABLE STATE! Peut on considerer plusieurs niveau d’OBSERVING_MODE? Peut on dire que OBSERVING_MODE ne refere pas aux scans pour la calibration?
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, if the same script is used, 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 DRAFT_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 DRAFT_MAIN  table.
PROJECT
 
RELEASE_DATE
FLAG_ROW

Remark: CONFIG_NAME is added in this table. It provides the state of the antenna configuration during the execution of a SCHEDULING block, even if not all antennas are used for that execution. The actual description of a sub-array is given by an ANTENNA_ARRAY collection in the CONFIG_DESCRIPTION table. CONFIG_NAME allows to discriminate observations obtained while the array was in one or several array configuration. 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 set of antenna idenfiers in the collection ANTENNA_ID_SET is given here to allow fully describe the antennas defining the antenna configuration. 
N.B.: This table must contains as many rows as there were executions of SCHEDULING blocks in the project, i.e. sum i=1NsbNxbi.
SCHEDULE_ID and EXECUTE are not required to be unique, as it would be the case when a SB and an EXECUTE are repeated.
If this appears as useful one could add one attribute, NUM_SUBARRAY for the case of synchronized subarrays. Asynchrone subarrays must appear with different EXECUTE.