Crate rubbl_casatables

source ·
Expand description

I/O on CASA table data sets.

This crate provides I/O access to the CASA table data format. This format is commonly used for storing radio astronomical visibility data in the Measurement Set data model, but is not limited to that particular application — it is a generic data format for tabular scientific data. This crate provides only lower-level I/O interfaces and not higher-level abstractions for dealing with the specific semantics of Measurement Set data.

Because the on-disk representation of the CASA table format is quite complex and essentially undocumented, this crate’s implementation relies on wrapping a substantial quantity of C++ code from the casacore project. The goal is to provide access to the data format in a way that is completely safe and as idiomatic as possible, given the limitations imposed by the architecture of the underlying C++ code.

The entry point to this crate is typically the Table struct that represents a handle to a CASA table data set.

Structs

An error type used when the wrapped “casacore” C++ code raises an exception.
Information describing the properties of a particular column of a table.
A complex number in Cartesian form.
An error type used when a scalar column was expected but a vector was found.
A CASA data table.
Information about the structure of a CASA table.
A dictionary-like data structured that can be stored in a CASA table.
A type for examining individual rows of a CASA table.
An error type used when the expected data type was not found.

Enums

Different data types supported by the CASA tables format.
Modes in which a casacore table can be created.
Different modes for creating a CASA table description.
An error type capturing all potential problems when interfacing with Tables.
Modes in which a casacore table can be opened.

Traits

A type that can be translated into a CASA table data type.
A type that maps to one of CASA’s scalar data types.

Type Definitions

An array that owns its data uniquely.
An array with copy-on-write behavior.