HiCat Data Dictionary

Catalog: HiRISE
The main HiRISE catalog contains all the information used in operating the HiRISE camera after it is attached to the MRO spacecraft. The information is divided into those related to suggesting, planning, commanding, retrieving, processing, validating, and distributing the observations. The tag that follows an observation through all these catalogs (and from Earth to Mars and back) is the unique Observation_ID. This text representation also forms the core of the product names. The HiRISE catalog also contains ancillary information needed in various uplink and downlink activities, such as the people making image suggestions, MRO project uplink files, SPICE and engineering data, and public image releases.
Table:Calibration_Data
This table holds the calibration data generated from calibration EDRs. A number fields in this table are redundant with fields already in the EDR_Products table, and should possibly be merged together.

Field Description Type Null Limits Size Key Default Authority Source
ID This is a unique ID for each record of calibration data. The values should not be set by external programs. External programs inserting data into this table should ignore this field. The ID will be set automatically by the database when a record is inserted. INT(10) unsigned auto_increment Not Null Primary Key db server
EDR_PRODUCT_ID This is the Product_ID that would be found in the EDR_Products field if these files were being entered into HiCat as EDR_Products. This may happen at some point in the future, but not yet. VARCHAR(28) Not Null ingestion script
VERSION Version number of this record. VARCHAR(255) Not Null EDRgen
STATS_FILE The full path and filename of the summary file this data was ingested from. This field is potentially redundant since this information can be reconstructed from other information in this table. VARCHAR(128) Not Null ingestion script
TEST_NAME The name of the test being run. This value is munged from the name of the summary file. VARCHAR(25) Not Null ingestion script/ stats file
PATHNAME The full, logical path (filename included) of the processed data file within the HiRISE filesystem that this record was generated from. This path should be the hard link to the location of the data file in the EDRgen directory structure. VARCHAR(128) Not Null ingestion script/ stats file
INSTRUMENT The instrument this data came from: FLight system, SUbsystem, or Engineering Model. ENUM("FL", "SU", "EM") summary4XL2HiCat
FPGA FPGA code TINYINT(3) ingestion script/ stats file
IEA_SIDE ???? VARCHAR(20) summary4XL2HiCat/ stats file
IDL_PROC_VERSION The version of the IDL procedure that generated this record. INT(2) make_summary_save.pro ingestion script/ stats file
STATUS Status of the IDL processing of the image. Allowed values are OK, PR (problem), or NA (not available). VARCHAR(4) OK, PR, or NA
CCD The CCD number this data was generated from. TINYINT(2) Not Null 0 to 13 ingestion script/ stats file
CH The CCD Channel number TINYINT(1) Not Null 0, or 1 ingestion script/ stats file
LINETIME This is the same field as the SCAN_EXPOSURE_DURATION column in the EDR_Products table, so the units of this field are in microseconds. Limits are 74 to less than 10,000 FLOAT(10,5) unsigned 74 to 10000 ingestion script/ stats file
BIN The binning mode for this calibration. This may be a redundant field, since this data will be in the EDR table. TINYINT(2) unsigned 1, 2, 3, 4, 8, or 16 ingestion script/ stats file
TDI The Time Delay Integration mode for this calibration. This field may be redundant. TINYINT(3) unsigned 8, 32, 64, or 128 ingestion script/ stats file
TRIM The number of trim lines in this calibration INT(11) unsigned ingestion script/ stats file
NLINES The number of lines in the image INT(11) unsigned ingestion script/ stats file
NCOLS The number of columns in the image INT(11) unsigned ingestion script/ stats file
LUT_CODE The name implies that this is the LUT Number but the values in the fields look like large integers, what is this field? INT(10) unsigned ingestion script/ stats file
ILLUMINATED This is a software determined field. The software looks at the data values an image and tries to determine if the CCD was "illuminated" or not (probably by a stim lamp). Values are 1 (the CCD was illuminated), 0 (the CCD was not illuminated), or -1 (the software can't tell).... These codes need to be double-checked... TINYINT(2) -1, 0, or 1 ingestion script/ stats file
STIM0 STIM0 on or off (redundant with the STIMUMLATION_LAMP_* fields in the EDR table. TINYINT(1) unsigned 0, or 1 ingestion script/ stats file
STIM1 STIM1 on or off (redundant with the STIMUMLATION_LAMP_* fields in the EDR table. TINYINT(1) unsigned 0, or 1 ingestion script/ stats file
STIM2 STIM2 on or off (redundant with the STIMUMLATION_LAMP_* fields in the EDR table. TINYINT(1) unsigned 0, or 1 ingestion script/ stats file
TIMING_POS_0 The commanded timing position for sampling the CCD output wave form. These may be hex values, but when converted to decimal, the values should be: 00, 11, 22, 33, 44, 55, 66, 77, or 88 INT(4) 00, 11, 22, 33, 44, 55, 66, 77, or 88 ingestion script/ stats file
TIMING_POS_1 The commanded timing position for sampling the CCD output wave form. These may be hex values, but when converted to decimal, the values should be: 00, 11, 22, 33, 44, 55, 66, 77, or 88 INT(4) 00, 11, 22, 33, 44, 55, 66, 77, or 88 ingestion script/ stats file
TIMING_POS_2 The commanded timing position for sampling the CCD output wave form. These may be hex values, but when converted to decimal, the values should be: 00, 11, 22, 33, 44, 55, 66, 77, or 88 INT(4) 00, 11, 22, 33, 44, 55, 66, 77, or 88 ingestion script/ stats file
TIMING_POS_3 The commanded timing position for sampling the CCD output wave form. These may be hex values, but when converted to decimal, the values should be: 00, 11, 22, 33, 44, 55, 66, 77, or 88 INT(4) 00, 11, 22, 33, 44, 55, 66, 77, or 88 ingestion script/ stats file
POWER Was the CCD commanded to be powered on? on (1) or off (0) TINYINT(1) unsigned 0, or 1 ingestion script/ stats file
CHAN_STATUS Status of the IDL processing for this channel. What are the return values if there is a problem? VARCHAR(4) ok, or not ok? ingestion script/ stats file
IMAGE_MEAN Mean data value of the image area. FLOAT(7) ingestion script/ stats file
IMAGE_MEDIAN Median data value of the image area. This should be an integer, although the value is exported as a floating point (with 0 decimal values). INT(7) ingestion script/ stats file
IMAGE_NOISE Image noise. How is this currently being calculated? FLOAT(7) ingestion script/ stats file
SNR Signal to noise ratio FLOAT(7) ingestion script/ stats file
DARKCURRENT The dark current rate FLOAT(7) ingestion script/ stats file
OFFSET The DN value of pixels with no signal in them. This *should* be zero.... FLOAT(7) ingestion script/ stats file
BUF_OFFSET Another way calculating the OFFSET FLOAT(7) ingestion script/ stats file
OFFSET_MEDIAN Median of the OFFSET DN? INT(7) ingestion script/ stats file
RAMP_MAX Max DN for the RAMP image area. May be the mean of the maxima for each column. Does anyone know? FLOAT(7) ingestion script/ stats file
READ_NOISE RMS noise in the reverse portion of the image? FLOAT(7) ingestion script/ stats file
BUF_READ_NOISE read noise from the buffer area FLOAT(7) ingestion script/ stats file
FIXED_PATTERN_NOISE RMS value of the MASKED portion of the image? FLOAT(7) ingestion script/ stats file
QUALITY Autogenerated comment about the image quality. VARCHAR(40) ingestion script/ stats file
DROPPED_PIXELS The number of dropped pixels INT(10) ingestion script/ stats file
SHIFTED_PIXELS Number of shifted pixels. INT(10) ingestion script/ stats file
LOCK_STATUS_0 The syncronization lock status of DLL 0. This field should have a decimal value of 11, unless it's a hex value. INT(3) or 11 ingestion script/ stats file
LOCK_STATUS_1 The syncronization lock status of DLL 1. This field should have a decimal value of 11, unless it's a hex value. INT(3) or 11 ingestion script/ stats file
LOCK_STATUS_2 The syncronization lock status of DLL 2. This field should have a decimal value of 11, unless it's a hex value. INT(3) or 11 ingestion script/ stats file
LOCK_STATUS_3 The syncronization lock status of DLL 3. This field should have a decimal value of 11, unless it's a hex value. INT(3) or 11 ingestion script/ stats file
LOCK_STATUS_4 The syncronization lock status of DLL 4. This field should have a decimal value of 11, unless it's a hex value. INT(3) or 11 ingestion script/ stats file
LOCK_STATUS_5 The syncronization lock status of DLL 5. This field should have a decimal value of 11, unless it's a hex value. INT(3) or 11 ingestion script/ stats file
FPA_POS_Y_TEMP Temperature of the Focal Plane Array on the positive Y end of the array in celsius. FLOAT(7) ingestion script/ stats file
FPA_NEG_Y_TEMP Temperature of the Focal Plane Array on the negative Y end of the array in celsius. FLOAT(7) ingestion script/ stats file
FPE_TEMP Temperature of the Focal Plane Electronics in celsius. FLOAT(7) ingestion script/ stats file
PMIRROR_TEMP Primary Mirror Temperature, in celsius FLOAT(7) ingestion script/ stats file
SMIRROR_TEMP Secondary Mirror Temperature, in celsius FLOAT(7) ingestion script/ stats file
IEA_TEMP Instrument Electronics Assembly Temperature in celsious FLOAT(7) ingestion script/ stats file
STIM_TEMP STIM Lamp temperature???? FLOAT(7) summary4XL2HiCat/ stats file
FOCUS_POS Focus Position of the focus mechanism INT(5) summary4XL2HiCat/ stats file
DATE_TIME Date and time of the observation (possible redundancy with time fields in the EDR_table???) DATETIME ingestion script/ stats file
HOUR The hour the calibration was taken in decimal. Is this needed? FLOAT(7) ingestion script/ stats file
NOTES Notes input during the commanding of the observation. VARCHAR(255) ingestion script/ stats file
LAST_UPDATE The last time this record was updated TIMESTAMP db server

Table Options:

Copyright (C) 2015 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

Contact

Please send comments to: HiCat@pirlmail.lpl.arizona.edu.