Construct one attached to the indicated MeasurementSet
Construct one from another
The destructor
Assignment operator, reference semantics.
Attach this one to a MeasurementSet. This can also be used to re-attach to the same MeasurementSet when additional optional subtables have been added since this object was constructed.
These functions check on the validity of the appropriate value in the main table or sub-tables in the case of some Ids. The actual value stored is returned unless the sub-table does not exist (for optional subtables) or the indicated row number does not exist in that sub-table where appropriate.
The polarizationId comes from the DATA_DESCRIPTION subtable, so dataDescId must first be valid in order for this to also be valid.
These functions check on the validity of the appropriate value in the main table or sub-tables in the case of some Ids. The actual value stored is returned unless the sub-table does not exist (for optional subtables) or the indicated row number does not exist in that sub-table where appropriate.
The spectralWindowId comes from the DATA_DESCRIPTION subtable, so dataDescId must first be valid in order for this to also be valid.
These functions check on the validity of the appropriate value in the main table or sub-tables in the case of some Ids. The actual value stored is returned unless the sub-table does not exist (for optional subtables) or the indicated row number does not exist in that sub-table where appropriate.
the dopplerId comes from the SPECTRAL_WINDOW subtable so spectralWindowId must first be valid in order for this to also be valid. Since the DOPPLER subtable is not simply indexed by DOPPLER_ID, the DOPPLER subtable exists and a dopplerId can be found in the SPECTRAL_WINDOW subtable, that value will be returned, whatever it is.
These functions check on the validity of the appropriate value in the main table or sub-tables in the case of some Ids. The actual value stored is returned unless the sub-table does not exist (for optional subtables) or the indicated row number does not exist in that sub-table where appropriate.
The sourceId comes from the FIELD subtable so fieldId must first be valid in order for this to also be valid. Since the SOURCE table is also indexed by TIME, the only additional check is that a SOURCE table must exist in order for this to be valid.
These functions check on the validity of the appropriate value in the main table or sub-tables in the case of some Ids. The actual value stored is returned unless the sub-table does not exist (for optional subtables) or the indicated row number does not exist in that sub-table where appropriate.