Chapter 3. Integration header

Table of Contents

sdmDataHeader element
Children
Attributes
time element
dataOID element
Attributes
execBlock element
Children
Attributes
scanNum element
subscanNum element
integrationNum element
numAntenna element
axes attribute
baselineFlags element
Attributes
actualTimes element
Attributes
actualDurations element
Elements
Attributes
lut element
Elements
Attributes
zeroLags element
Attributes
numAPC element
baseband element
Children
spectralWindow element
Attributes
crossData element
Attributes
autoData element
Attributes

The primary purposes of this header, which appears once per integration, are to provide an identifier for the data file, and to provide the metadata needed to read the binary data from the file. References to the binary tables in the file are represented in the header by MIME Content-IDs, which are identifiers for the sub-parts of multipart MIME documents. The header is in the form of an XML document conforming to the schema given in the section called “Data header XML schema”. The following sections provide short descriptions of the header element and its descendents.

[Note]Note

Several elements in the header have a ref attribute, used to refer to other sub-parts of the same multipart MIME message (that is, within the same integration). These references use the Content-ID URI scheme [RFC2111], which provides a syntax for referring to Content-IDs within multipart MIME messages. Because Content-IDs are required to be world-unique, the values of the ref attributes cannot be fixed for EVLA, in contrast to the ALMA specification.

The following sections should be read with reference to the schema (the section called “Data header XML schema”). These sections are meant to provide a descriptive summary of the elements and attributes in the integration header, and do not provide enough information to produce a conforming XML header document.

sdmDataHeader element

The top-level element; all other elements are descendents of this element.

Attributes

byteOrder

Binary data endianness.

[Note]Note

ALMA has fixed the value to be “IEEE Low_Endian”. EVLA prefers to allow the choice of values “little endian” and “big endian” because 1) there's no reason for the schema to fix the value if the attribute is present (whether or not it's fixed in practice is another issue), and 2) the term is non-standard.

axisOrder

Axes are given an integer id as follows: 1. polarization product, 2. spectral channel, 3. apc, 4. bin, 5. spectral window, 6. baseband, 7. baseline. Data in tables are ordered by a *column-major* traversal of the axes in this order. Note that the attribute value is fixed to be '1234567'.

schemaVersion

Schema version number.

[Note]Note

There should be some convention for the version numbering that accomodates both ALMA and EVLA yet differentiates them.