|
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
Na in the collection |
ANTENNA_ID_SET |
Int( Na) | | | 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 |
Double | s | EPOCH | Time
interval mid-point |
INTERVAL | Double | s |
| Time interval |
OBSERVER_NAME
| String | | | Name of
observers |
OBSERVING_LOG
| String(*) | | | Observing
log |
SCHEDULE_ID | Int | |
| Schedule identifier |
EXECUTEE_INTENT
| String(*) | | | Execute
intent |
EXECUTE_SCRIPT
| String | | | Project
execution script |
PROJECT | String |
| | Project identification
string |
RELEASE_DATE |
Double |
s | EPOCH | Target release
date |
| | Flags |
FLAG_ROW | Bool | |
| The row flag |
| |
|
Notes: This table gives the set of Executing Blocks associated to each Scheduling Block;
at the same time it gives the list of Scheduling Block actually used. It is indexed via the
identifier EXECUTE_IDdirectly from the HISTORY and as a secondary index, from the
TOTAL_POWER_MONITORING and MAIN tables.
-
TELESCOPE_NAME
- Name of the telescope, ALMA.
-
CONFIG_NAME
- String type to support names with current instruments (TBD).
-
NUM_ANTENNA
- Number of antennas Na (indicative) for the antenna configuration.
N.B.: It must be understood that this number does not necessarily correspond to the number
of rows in the ANTENNA table; it may be smaller but never larger. This number does not
correspond neither to Na in the CONFIG_DESCRIPTION table.
-
ANTENNA_ID_SET
- Collection: set of antenna identifiers ANTENNA_ID giving the
ensemble of antennas which belong to the current array configuration. These identifiers do
not need to be given in a specific order but obviously the members in this collection must
be unique.
Note that if there are subarrays ,the subsets of antennas forming these subarrays are
specified in the CONFIG_DESCRIPTION table. The present collection does not imply
that all its members are cross-correlated.
-
BASE_RANGE
- Baseline range (minimum, maximum).
N.B.: This range gives the extent over which the phase structure function is sampled.
-
BASE_RMS
- rms along the minor and major axis in the baseline distribution. This provides
one characteristic for the current array configuration. This could also characterize how is
sampled the atmospheric phase structure function.
-
BASE_PA
- Position angle in the distribution of baselines.
-
TIME
- Time mid-point interval. The same reference used for the TIME column in the MAIN
must be used.
-
INTERVAL
- Time interval. This is the difference between the end and begin TIME of the SB
execution.
-
OBSERVER_NAME
- Name of the observer.
-
OBSERVING_LOG
- Name of the observing log.
-
OBSERVING_MODE
- Observing mode, e.g. singleField, mosaic
The definition of the observing modes at the level of a ShedulingBlock are TBD.
-
SCHEDULE_ID
- Scheduling Block identifier. Not required to be unique.
-
EXECUTEE_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_SCRIPT
- 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 Executing Block has to be notified with one row in this table.
It is indexed directly from the MAIN table for a straightforward segmentation of whole
data base into data blocks.
EXECUTE_ID is used for data selection to define an Observation Unit (see the
OBSERVATION_UNIT sub-table).
-
PROJECT
- Project reference (TBD)
-
RELEASE_DATE
- Date the Executing Block becomes public.
-
FLAG_ROW
- True if the row does not contain valid data; does not imply flagging in the MAIN
table.
Remark:
CONFIG_NAME 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 configurations. If the plan is that ALMA 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 fully
describe the antennas defining the antenna configuration.
Note that this table must contains as many rows as there were executions of Scheduling Blocks in the
project, i.e. 
i=1i=NSBNXBi.
SCHEDULE_ID and EXECUTE_SCRIPT are not required to be unique, as it would be the case
when a SB and an EXECUTE_SCRIPT are repeated.
Sub-arrays operating asynchroneously must appear with different EXECUTE_SCRIPT.