Data Product Generation
| |
|
Data Product Generation |
Previous Next |
|
The following is an abbreviated description of the data product generation for the various Phoenix instruments. For more in depth information on data product generation, see the Instrument Software Interface Specifications (SISs).
The spacecraft contractor, LMCO, was responsible for the supply of the raw telemetry packet data to the Phoenix Science Team. EDRs/RDRs were produced by the Phoenix Science Team cognizant scientist. Raw ASE data packets were extracted from the telemetry stream and stored in data records, by product type and record length.
As the fundamental image data archive product, the EDR will be generated as “raw” uncalibrated data within an automated pipeline process managed by MIPL under OPGS at JPL as part of the critical path in RA operations. The size of an EDR data product is approximately 2 MB.
RDR data products will be generated by, but not limited to, MIPL using the Mars Suite of VICAR image processing software at JPL, the SSI and RAC science instrument teams using TAMCAL and RACCAL software at the SOC facility at the University of Arizona and at the teams’ home institution at Texas A&M Univerisity, and the MECA Science Team using same set of SSI/RAC software tools at JPL. The RDRs produced will be “processed” data. The input will be one or more Camera EDR or RDR data products and the output will be formatted according to this SIS. Additional meta-data may be added by the software to the PDS label. There may be multiple versions of a PHX Camera RDRs.
The MGSS-IOS element, supported by the Multi-mission Image Processing Lab (MIPL) at JPL is responsible for generation of the MECA non-imaging EDRs. Raw MECA data packets are extracted from the telemetry stream and stored in EDRs, by activity, product type and record length.
AFM RDR data products will be generated by the MECA Science Team using software at the Science Operations Center (SOC), the Jet Propulsion Laboratory (JPL) or their home institutions. The RDRs produced will be “processed” data (NASA Level 1). The input will be one or more MECA non-imaging EDR or RDR data products and the output will be formatted according to this SIS and consists of a data file with a .TAB file extension, a PDS label file that has the same name as the data file with a .LBL file extension and a text (.TXT) file that contains information about how the data was collected. Additional meta-data may be added by the software to the PDS label or the data product header table.
The two scan data AFM RDR data products are formatted to have a detached ASCII PDS label. The SDR and SDD data products consist of five attached data tables. The first table is the header table that describes the AFM scan parameters and other important information pertaining to that scan, followed by the calibrated scan data in four sequential ASCII TABLE objects.
TECP RDR data products will be generated by the MECA Science Team using software at the SOC, JPL or their home institutions. The RDRs produced will be “processed” data (NASA Level 1). The input will be one or more MECA non-imaging EDR or RDR data products and the output will be formatted according to this SIS. Additional meta-data may be added by the software to the PDS label or the data product header table.
There are four types of TECP data, electrical conductivity (designated EC), humidity (designated HUM), relative permittivity or dielectric constant (designated PRM) and temperature (TC). The EC data is formatted as six ASCII tables, a general comments table, an EC comments table, a conversions table, two tables with conversion constants, and a data table that contains a time-series of measurements. The HUM, PRM and TC data are all formatted as a general comments table, a data type specific comments table, a conversions table and a data table that contains a time-series of measurements. The conversions table contains the DN to physical unit equations for the particular data type. In some equations the abbreviation ADC is used for Analog to Digital Converter and is equivalent to DN.
WCL RDR data products will be generated by the MECA Science Team using software at the SOC, JPL or their home institutions. The RDRs produced will be “processed” data (NASA Level 1). The input will be one or more MECA non-imaging EDR or RDR data products and the output will be formatted according to this SIS. Additional meta-data may be added by the software to the PDS label or the data product header table.
MET data products will be generated by the MET Team led by Co-Investigator Whiteway at York University. The majority of the data processing for the MET-Lidar instrument is performed in the flight segment. The MET-Lidar takes measurements and nominally saves the data to instrument internal Flash memory (Record state). The system will be separately commanded to transmit the data immediately to the Lander (Transmit state). Raw telemetry data are received by the University of Arizona. A, and a number of automated computer processes are run to place data in the MET directory of the UA Science LAN in an ASCII formatted file. The MET-GDS software appends the Timestamp, and writes the data out to files. These are the Level 2 EDRs.
The Mars atmospheric opacity data products are produced by the SSI instrument team using processing procedures and software developed by Mark Lemmon, Texas A&M Univ.
TEGA data products will be generated by the TEGA Team led by Co-Investigator Boynton at the Lunar and Planetary Laboratory, University of Arizona. Once a TEGA measurement is collected, it is stored on the Lander and held for periodic download. The stored telemetry data are downloaded periodically from the Lander for relay to the Deep Space Network (DSN). Data received from the DSN are inserted into the Jet Propulsion Laboratory’s (JPL) Telemetry Data System (TDS). The University of Arizona (UA) queries the TDS for the most recent telemetry dataset. The dataset is output to a spooler that passes data to the UA. Raw telemetry data are received by the UA, and a number of automated computer processes are run to ingest the data into a database, and to transform the data into scientifically useful data products. |
