Field | Description | Type | Null | Limits | Size | Key | Default | Authority | Source |
---|---|---|---|---|---|---|---|---|---|
ID | This is the unique ID for each Engineering Data File. The values here should not be assigned by external programs. Instead it can either be ignored, or NULL can be inserted, and the database will automatically assign the next ID. | INT(10) unsigned auto_increment | Not Null | Primary Key | db server | ||||
VERSION | Version number of this record. | VARCHAR(255) | Not Null | ||||||
START_TIME | The earliest time that this engineering data file covers in UTC. | DATETIME | |||||||
STOP_TIME | The latest time that this engineering data file covers in UTC. | DATETIME | |||||||
TYPE | The type of engineering data file this is. Does this need to be more verbose? Laz: in the DD, yes. There is the HiRISE camera data that is played back through the 1553 interface. AACS is stuff moving on the spacecraft. MCS is stuff moving on MCS. We will get info on gyros. And nobody knows what else! All placeholder for now. | ENUM("HIR", "AACS", "MCS", "OTHER") | |||||||
PATHNAME | The full logical path (filename included) of this engineering data file within the HiRISE filesystem. | TEXT | |||||||
LAST_UPDATE | This column records the last time that a record was updated. | TIMESTAMP | db server |
Table Options:
Copyright (C) 2005-2022 Arizona Board of Regents on behalf of the Planetary Image Research Laboratory, Lunar and Planetary Laboratory at the University of Arizona.
This page was generated from the XML HiCat Data Dictionary. HEAD
Please send comments to: HiCat@pirlmail.lpl.arizona.edu.