PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2007-05-10 NOTE = "Description of contents of EXTRAS directory" END_OBJECT = TEXT END The EXTRAS directory is used primarily to document the history of the hardware and software state of the CRISM instrument. CP directory: This contains a model of the lossless compressibility of CRISM data. For every combination of binning, wavelength filter, lossless on or off, lossy compression on or off, and type of scene (background or bias calibration, scene or calibration lamps, or test pattern) the expect compression ratio is given with respect to uncompressed 12-bit data. DC directory: This contains the history of values loaded into selected data structures ('alarm limits' and 'parameters' per the CRISM software specification), as well as the start times at which that update became applicable. If a set of values is planned but not yet active, that is also indicated. The alarm limits are all in calibrated form in volts, degrees Celsius, or amperes. DR directory: This contains the history of values loaded into selected data structures ('alarm limits' and 'parameters' per the CRISM software specification), as well as the start times at which that update became applicable. If a set of values is planned but not yet active, that is also indicated. The alarm limits are all in raw form corresponding to 16-bit housekeeping values to which the alarms are keyed. EL directory: This directory contains time-stamped summaries of key activities during CRISM flight operations. Typical entries include major flight calibrations, power cycles, and macro loads. In addition a running total is kept of cooler on time, gimbal cycles, and shutter cycles. MACROS directory: This directory contains information on the characteristics of flight macros that were active during different periods of the MRO mission. The macros have several functions: some control engineering functions like powering subsystems. Others are called by internal autonomy if certain housekeeping items exceed alarm limits. Most of the macros are used for data acquisition: observations are triggered by sequential execution of several macros. The are three files for each macro load: the macro dictionary itself, a summary of each macro's function, and a description of the image data generated by each macro. OTT directory: The observation tracking table subdirectory contains ASCII tables that connect specific observations with regions of interest on Mars, science objectives, and specific observation conditions. There are up to five tables whose contents are described in detail in the Data Products SIS. SITE_ID_YYYYMMDD.TAB: This table is a description of the locations and physical features of sites of interest on Mars, compiled by the CRISM science team. This table defines the intended targets of observations by full and half resolution targeted observations or multispectral windows (see Applicable Document 3 for definitions of each class of observation; this implies CLASS= FRT, HRS, HRL, or MSW). The string YYYYMMDD in the file name is the date of the last update. ANCILLARY_YYYYMMDD.TAB: This ancillary information table describes physical properties of a 0.25 degree x 0.25 degree region centered on the center point of each site ID. The string YYYYMMDD in the file name is the date of the last update. REQ_ID_MCxx-yyyy_YYYYMMDD.TAB: These tables contain one or more entries specifying the desired observing conditions such as solar longitude for an observation of an entry in the SITE_ID table. For site IDs desired to be observed repeatedly, there are multiple entries. There is one table per site ID (MCxx-yyyy, in which xx is the Mars chart number in which the site is located, and yyyy is the ordinal number of the site within the Mars chart). OBS_ID_YYYY_MM_VV.TAB: The observation table summarizes the date and characteristics of each observation actually taken, included its planned instrument configuration and geographic location and the rationale for planning it, and the as-executed characteristics of the data including instrument configuration, geographic location, and data quality. There is one table for a given time span, whose starting month is given as MM in the file name. VV is the version number. CORRESP_YYYYMMDD.TAB: In the correpondence table, each line gives a site ID, request ID, and target ID where there is geographic overlap. For example, all the lines containing a particular site ID include the target IDs that cover it. SC: This directory contains information on the goals and hystereses for heaters and coolers. These are all set in software and the default state is off. The files give the values as well as the start times at which an update became applicable. If a set of values is planned but not yet active, that is also indicated. The values all in calibrated form in degrees Celsius. SR: This directory contains information on the goals and hystereses for heaters and coolers. These are all set in software and the default state is off. The files give the values as well as the start times at which an update became applicable. If a set of values is planned but not yet active, that is also indicated. The values all in raw form corresponding to 16-bit housekeeping values to which the alarms are keyed.