Table 1: | MAIN table: Data, coordinates and flags |
| MAIN table: Data, coordinates and flags
Name | Format | Units | Measure | Comments |
| Columns |
| Keywords |
EDF_VERSION | Float | | | EDF format version |
| Key |
TIME | Double | s | EPOCH | Integration midpoint |
(TIME_EXTRA_PREC) | Double | s | | extra TIME precision |
CONFIG_DESCRIPTION_ID | Int | | | Config. description id. |
FIELD_ID | Int | | | Field id. |
| Non-key attributes |
INTERVAL | Double | s | | Sampling interval |
INTEG_NUMBER | Int | | | Integration number |
EXECUTE_ID | Int | | | Execute id. |
STATE_ID | Int | | | State id. |
|
|
MAIN table: continued
Name | Format | Units | Measure | Comments |
| Data |
EXPOSURE | Double(Nbb) | s | | Effective integration
tiome |
TIME_CENTROID | Double(Nbb) | s | EPOCH | Time centroid |
DATA_OID | String | | | Reference to the data
object |
| Flag information |
FLAG | Float
(form of
DATA_OBJECT) | | | Cumulative data flags |
FLAG_CATEGORY | Float
(form of
DATA_OBJECT,Ncat) | | | Flag categories |
FLAG_ROW | Bool | | | The row flag |
|
|
Notes: Nbb = number of basebands (attribute of the CONFIG_DESCRIPTION table), The form
of the data object is determined by the attributes in the Data description section of the
CONFIG_DESCRIPTION table and Nc = the numbers of correlators, Nf = the numbers of frequency
channels and Nphc all those derived via the identifiers in the DATA_DESCRIPTION_ARRAY
collection. Ncat = is number of flag categories.
-
EDF_VERSION
- EDF revision number, expressed as major_revision.minor_revision. A string
containing NONE1
reflect no sort order.
-
TIME
- Mid-point (not centroid) of data interval.
-
TIME_EXTRA_PREC
- Extra time precision
-
CONFIG_DESCRIPTION_ID
- Configuration descriptor identifier (> 0) providing a direct
index into the CONFIG_DESCRIPTION sub-table row number. Note that two or more
sub-arrays cannot refer to the same CONFIG_DESCRIPTION_ID identifier.
-
FIELD_ID
- Field identifier (> 0)
-
INTERVAL
- Data sampling interval. This is the nominal data interval, it does not include the
effects of bad data or partial integration.
-
INTEG_NUMBER
- INTEGRATION number. The enumeration is relative to the
OBSERVATION (ALMA glossary). The enumeration of the observations is implicit; each
time INTEG_NUMBER is decrementing from one row to the next in this DRAFT_MAIN
table the OBSERVATION number is implicitly incremented. N.B.: the OBSERVATION
intent is in the STATE sub-table.
-
EXECUTE_ID
- This provides access to a row number in the EXECUTE_SUMMARY table.
This meta coordinate defines the data-base in term of an implicit collection of data blocks.
-
STATE_ID
- State identifier (> 0). Would be always 0 if the sub-integration are not considered.
-
EXPOSURE
- Effective duration of an INTEGRATION (or a SUB_INTEGRATION if
STATE_ID is > 0).
-
TIME_CENTROID
- Time stamp reflecting the average time the non-blanked data was
integrated.
-
DATA_OID
- Reference to the data cell object. It is an object identifier and, as such, is of type
String.
-
FLAG
- An array of Boolean values with the same shape2
array as the DATA_OBJECT representing the cumulative flags applying to this data matrix,
as specified in FLAG_CATEGORY . Data are flagged bad if the FLAG array element is
True.
-
FLAG_CATEGORY
- An array of flag matrices with the same shape as the DATA_OBJECT,
but indexed by category. The category identifiers are specified by a keyword CATEGORY ,
containing an array of string identifiers, attached to the FLAG_CATEGORY column and
thus shared by all rows in the MS. The cumulative effect of these flags is reflected in column
FLAG . Data are flagged bad if the FLAG array element is True.
-
FLAG_ROW
- True if the entire row is flagged.
Remarks:
The attribute SUBARRAY_NUM is removed, the CONFIG_DESCRIPTION_ID attribute
reflecting a sub-array. With CONFIG_DESCRIPTION_ID as a key this table can have rows for
different arrays, even if their are not synchronized in time. The EXECUTE_SUMMARY table
contains an ANTENNA_IDSET attribute which represents a collection which should correspond to the
union of the ANTENNA_ARRAY collections.
N.B. In case of a multi-configuration data sets, note that CONFIG_NAME is added in the
EXECUTE_SUMMARY table; in that context it is possible to distinguish the case of several
sub-arrays and the case of several array configurations.