PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = " 2012-02-21 Cornell:BTCarcich incorporated comments from Ken Klaasen. 2014-05 Latchmoor:BTCarcich updated for re-calibration of Wild 2 and and Annefrank data 2015-10 Latchmoor:BTCarcich Lien resolution " RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 80 MISSION_NAME = "STARDUST" INSTRUMENT_HOST_NAME = "STARDUST" OBJECT = TEXT PUBLICATION_DATE = 2014-07-31 NOTE = "Stardust archive data. This is the 'Read me first' file for this data set. It is duplicated in two places in the data set: in the top-level directory as AAREADME.TXT; in the DOCUMENT/ directory as AAAREADME.TXT. The Planetary Data System (PDS) standard requires the former former but PDS does not guarantee its preservation, so it is duplicated in the DOCUMENT/ directory." END_OBJECT = TEXT END Stardust Planetary Data System (PDS) archive data set for NAVCAM EDR (raw) data. This file is the "Read me first" file for this data set. Its purpose is to be the starting point for any user who wishes to view and understand the data in this data set. It contains a high-level description of the contents of this data set, and points the user to other documents in this data set that contain more detailed descriptions of the data along with pointers to additional documentation. If the information in this data set is represented as a tree, with each file as a leaf covering a specific area or sampled data, then this file is the root of the tree. Some of the 'leaves' contain reference to external information sources such as journal articles or other data sets; those references are considered an integral part of this data set and are often critical for understanding the data. Where possible and if allowed by journal publisher policies and applicable copyright law, versions of those publications have been provided in the documentation of this data set; those provided versions may be pre-print or draft versions, and may not be identical to the published version; such situations will be called out in the documentation labels; data set users will have to contact the publisher directly and may need to pay to obtain the published version. All of the EDR and RDR data sets for the Stardust mission NAVCAM instrument data have been prepared in a similar manner, so the "Read me first" files for these data sets will be identical. For data set-specific details e.g. specific targets, see the CATALOG/ and DOCUMENT/ 'branches'. This file comprises the following sections: 1) Introduction to this data set, including pointers to other files that explain what is in the data set 1.1) Quick start 1.2) Product description 2) Data set medium format 3) File formats - where to learn about the formats used in this data set 4) Data set contents - a high-level description of the directory layout 5) Recommended computer software 6) Errata, Disclaimer and PDSDD 6.1) PDS Data Dictionary (PDSDD) 7) Whom to Contact for further Information 1) Introduction =============== This volume contains NAVCAM CODMAC level 2/3 products from the Stardust prime mission. It also contains documentation which describes these products. 1.1) Quick start: ----------------- The data set files are laid out with a directory (a.k.a. folder) structure. The most important top-level directories are CATALOG/, DOCUMENT/ and DATA/. The CATALOG/ directory contains high-level PDS catalog files which describe the mission, spacecraft, instrument and other information related to this data set. The catalog files also contain references to external materials such as journal articles. See CATALOG/CATINFO.TXT for more details. The DOCUMENT/ directory contains more detailed descriptions of this data set. See DOCUMENT/DOCINFO.TXT for more details. The DATA/ directory contains the data in this data set. Subdirectories partition the data by date and/or by target. Each data product has a corresponding Planetary Data System (PDS) data label in accordance with the Standards reference, Version 3.8, document JPL D-7669. See DOCUMENT/DATAINFO.TXT for more details. The BROWSE/ directory contains a browsing facility for the data. See BROWSE/BROWINFO.TXT for more details. 1.2) Product description ------------------------ This data set contains raw (EDR) data from the Stardust NAVCAM instrument. Each NAVCAM raw (EDR) product comprises two sections: the image pixel data from the CCD in either 8-bit or 16-bit format; the BaseLine Stabilization (BLS or bias) pixels from the CCD electronics. Note that, to save on limited downlink at the time some image observations were made, only rectangular window subsets of the the full-frame of pixels were telemetered to Earth. This can be identified by WINDOW objects in PDS labels, and by the appearance of the image as gray/white rectangle against a rectangles against a black background in the BROWSE/ images. Note that BLS pixels are not avalable in these windowed images, which affects their calibration. Refer to the documentation and the calibration paper [KLAASENETAL2011B] for more detail about the effect windowing has on data calibration. See also DATA/DATAINFO.TXT, CATALOG/DATASET.CAT and DOCUMENT/DOCINFO.TXT for further details. The products archived in this volume have all been released by the Stardust Project. 2) Data set medium format ========================= This data set has been delivered to PDS in an electronic format, transferred via either the Internet or portable disk drive. User access will typically be via a web browser over the Internet to a web server at the Small Bodies Node of PDS (PDS-SBN; currently http://pdssbn.astro.umd.edu/). Duplicating the directory hierarchy and contents recursively from the directory which contains this AAREADME.TXT file and below is all that is required to copy this data set. 3) File format ============== Each data product and all files with content have a PDS label. The PDS label is the definitive and complete source describing the data layout and format in each product in this data set. The PDS label may be attached or detached. Attached labels are in the same file as the data at the start of the file. Detached labels are separate files with pointers to the data files; detached label filenames always end in .LBL or .lbl. The label files conform to the Planetary Data System (PDS) Standards, Version 3.8, Jet Propulsion Laboratory (JPL) document JPL D-7669 Part 2; refer to this standards reference for details in interpreting the label and contents of any file in this data set. PDS labels for data products also contain parameter values such as the start and end times of the data in the data product. NAVCAM image data products are stored as Primary Data Unit (PDU) images and multiple Extension Data Units (EDUs) in FITS files; see http://fits.gsfc.nasa.gov/iaufwg/iaufwg.html FITS-savvy users may use existing FITS software to view and process these data. However, the PDS labels adequately describe both the conditions of each observation (geometry, camera parameters, &c) and the data layout and format in the files, so FITS software is not necessary to work with these data. The FITS headers in the files were developed for use by the science team and are provided as-is with no documentation beyond the comments that follow most FITS header keyword values. All detached label files contain 80-byte fixed-length records, with a carriage return character (ASCII 13) in the 79th byte and a line feed character (ASCII 10) in the 80th byte. This format allows the files to be read by many different operating systems (e.g. MacOS, Windows, DOS, Unix, Linux, VMS etc.). All tabular files are also described by PDS labels, either embedded at the beginning of the file (attached) or detached. If detached, the PDS label file has the same, or a similar, name as the data file(s) it describes, with the extension .LBL; for example, the file INDEX.TAB is accompanied by the detached label file INDEX.LBL in the same directory. Tabular files are formatted so that they may be read directly into many database management systems on various computers. All fields are separated by commas, and character fields are enclosed in double quotation marks ("). Character fields are left justified, and numeric fields are right justified. The "start byte" and "bytes" values listed in the labels do not include the commas between fields or the quotation marks surrounding character fields. The records are of fixed length, and the last two bytes of each record contain the ASCII carriage return and line feed characters. This allows a table to be treated as a fixed length record file on computers that support this file type and as a normal text file on other computers. 4) Data set contents and directory layout ========================================= The following ASCII graphic describes the file layout of this data set. TOP-LEVEL-DIRECTORY/ | +--AAREADME.TXT The text version of the "Read me first" file. | This file is the starting point for documentation | describing this data set. A duplicate of this | file has been placed in the DOCUMENT/ directory | as AAAREADME.TXT because PDS does not guarantee | preservation of this top-level AAREADME.TXT file. | +--ERRATA.TXT File listing known data set anomalies and errors | +--VOLDESC.CAT Description of the contents of this volume. | +--CATALOG/ Directory containing PDS catalog objects; refer | | to CATINFO.TXT for details. | +--CATINFO.TXT File with detailed description of contents of | | CATALOG/ directory. | +--*.CAT Catalog files (mission, spacecraft, instrument, | data set, personnel, references) | +--DATA/ Directory containing NAVCAM data files; refer to | | DATAINFO.TXT for details. | +--DATAINFO.TXT File describing the layout of data files under | | the DATA/ directory along with any optional | | subdirectories. | |.../ Optional subdirectories of DATA/, described in | | DATAINFO.TXT. | |.../*.LBL Optional detached labels for data files | |.../*.* The data files themselves | +--DOCUMENT/ Directory containing documents necessary for | | understanding this data set; refer to DOCINFO.TXT | | for details. | +--DOCINFO.TXT File with detailed description of contents of | | DOCUMENT/ directory | | | +--AAAREADME.TXT Duplicate of top-level AAREADME.TXT; see above | | | +--*.TXT Documents with attached labels | +--*.LBL Detached PDS labels, one for each document. | | Each label may refer to more than one file. | | Each label has a DESCRIPTION keyword, the value | | of which describes the document. | +--*.* The documents themselves | | | +--*/ Subdirectory(ies) of DOCUMENT/. See | DOCINFO.TXT for more information. | +--INDEX/ Directory containing tabular summaries of the | | data and files in this data set; refer to | | INDXINFO.TXT for details. | +--INDXINFO.TXT File with detailed description of contents of | | of INDEX/ directory. | +--*.LBL PDS labels, one for each index. | +--*.TAB Index tables | +--BROWSE/ Directory containing data set browse facility; | | refer to BROWINFO.TXT for details | +--BROWINFO.TXT File with detailed description of contents of | | of BROWSE/ directory. | | | +--*.LBL PDS labels | +--*.* Browse files | | | +--*/ BROWSE/ subdirectories | +--EXTRAS/ Directory containing additional information that | may be useful for understanding this data set, | but which does not readily fit in one of the | other PDS categories. See EXTRINFO.TXT for | details. +--EXTRINFO.TXT File with detailed description of contents of | EXTRAS/ directory. | +--PDSDD_NEXT.FULL Proposed PDS Data Dictionary (See 6.1 below) | +--*.* Any EXTRAS/ files. +--*/ Any EXTRAS/ subdirectories. 5) Recommended computer software ================================ As noted above, this data set was delivered to PDS-SBN in electronic format. Any computer system capable of replicating the directory (folder) structure should be able to maintain a usable copy of this data set. At the time of the delivery of this data set (2011 A.D.), that specification will be met by computers running the following operating systems: Microsoft Windows; Apple Mac OSX; Unix(tm) derivatives including Linux; VMS. Tabular data may be imported into a spreadsheet application (OpenOffice.org Spreadsheet or Microsoft Office Excel) or a database application (MySQL, PostgreSQL, Microsoft SQL Server or Microsoft Office Access). Tabular data may also be viewed with a PDS tool called NasaView: http://pds.nasa.gov/tools/nasa-view.shtml PDS supplies tools that may be of use in viewing the data files in this data set: http://pds.nasa.gov/tools/index.shtml http://pds.nasa.gov/tools/other-tools.shtml NAVCAM image data can be viewed with NasaView, as well as by using FITS libraries within other programming environments: FITSIO library in several environments (C, FORTRAN, etc.) (http://heasarc.gsfc.nasa.gov/fitsio/) Native FITS reader in Matlab IDL Astronomy Library (http://idlastro.gsfc.nasa.gov/) Documentation and data labels may be viewed with word processing applications: OpenOffice.org Word Processor; Microsoft Office Word; editors such as VI, VIM, GEDIT and others in the Linux/Unix(tm) environment. ASCII files, such as tables and PDS labels, may be viewed with many web browsers. Some documentation files are stored as PDF (Portable Document Format) files; PDF filenames will end in .PDF (case-insensitive). A PDF reader (e.g. Acrobat reader on Windows and Mac OSX, acroread on Unix, Document Viewer on Linux, or a PDF plug-in for a web browser) is necessary to view these files, but in the absence of such readers most PDF documents also have alternate versions that will be easier to view. 6) Errata, Disclaimer and PDSDD =============================== A cumulative list of anomalies and errors is maintained in the file ERRATA.TXT at the root directory of this volume. Over time and multiple versions of this data set it is anticipated that the errors will be corrected and the anomalies incorporated into the data set documentation. Users should always check the latest ERRATA.TXT file for this data set before using the data for any purpose. Although considerable care has gone into making this volume, errors are both possible and likely. Users of the data are advised to exercise the same caution as they would when dealing with any other unknown data set. At the time of delivery of this data set no known anomalies exist and the ERRATA.TXT file comprises only its attached label. Reports of errors or difficulties would be appreciated; please contact PDS. 6.1) PDS Data Dictionary (PDSDD) -------------------------------- This data set presupposes and proposes the following STANDARD_VALUE_SET entries will be added to the PDS Data Dictionary (relative to PDSDD 1r92), plus some other minor changes also listed below. See also the file PDSDD_NEW.FULL in the EXTRAS/ directory. Until those entries are added, PDS validation tools may generate errors and/or warnings when run against this data set, as well as recent Stardust-NExT data sets. Changes proposed for all Stardust instrument data sets (CIDA, DFMI, NAVCAM) are included here so PDS personnel do not have to browse several data sets to compile the proposed changes. 6.1.1) STANDARD_VALUE_TYPE additions to PDSDD --------------------------------------------- STANDARD _VALUE Keyword _TYPE New entry ------------ --------- --------- DATA_SET_ID FORMATION SDU-A-NAVCAM-2-EDR-ANNEFRANK-V3.0 DATA_SET_ID FORMATION SDU-A-NAVCAM-2-EDR-WILD2-V3.0 DATA_SET_ID FORMATION SDU-A-NAVCAM-3-RDR-ANNEFRANK-V1.0 DATA_SET_ID FORMATION SDU-A-NAVCAM-3-RDR-WILD2-V3.0 DATA_SET_NAME FORMATION STARDUST NAVCAM RAW IMAGES OF \ ANNEFRANK - VERSION 3.0 DATA_SET_NAME FORMATION STARDUST NAVCAM CALIBRATED IMAGES OF \ ANNEFRANK - VERSION 1.0 DATA_SET_NAME FORMATION STARDUST NAVCAM CALIBRATED IMAGES OF \ 81P/WILD 2 - VERS 3.0 DATA_SET_NAME FORMATION STARDUST NAVCAM RAW IMAGES OF \ WILD 2 - VERSION 3.0 DOCUMENT_FORMAT DYNAMIC MICROSOFT EXCEL DOCUMENT_FORMAT DYNAMIC WAVE DOCUMENT_TOPIC_TYPE SUGGESTED DATA LOG FILTER_NAME DYNAMIC OPNAV INSTRUMENT_MODE_ID DYNAMIC NEGATIVE ION MODE INSTRUMENT_MODE_ID DYNAMIC POSITIVE ION MODE MISSION_PHASE_NAME DYNAMIC ANNEFRANK ENCOUNTER MISSION_PHASE_NAME DYNAMIC CHECKOUT MISSION_PHASE_NAME DYNAMIC CRUISE 5 MISSION_PHASE_NAME DYNAMIC CRUISE 6 MISSION_PHASE_NAME DYNAMIC TEMPEL 1 ENCOUNTER MISSION_PHASE_NAME DYNAMIC WILD 2 ENCOUNTER PRODUCT_TYPE SUGGESTED CONFIGURATION_PARAMETERS PRODUCT_TYPE SUGGESTED FDAQ_CALIBRATION PRODUCT_TYPE SUGGESTED GLOBAL_VARIABLES PRODUCT_TYPE SUGGESTED HOUSEKEEPING PRODUCT_TYPE SUGGESTED SPECTRUM VOLUME_SET_NAME DYNAMIC STARDUST CIDA DATA VOLUME_SET_NAME DYNAMIC STARDUST CIDA EDR/RDR DATA VOLUME_SET_NAME DYNAMIC STARDUST DFMI EDR/RDR DATA VOLUME_SET_NAME DYNAMIC STARDUST NAVCAM EDR DATA VOLUME_SET_NAME DYNAMIC STARDUST NAVCAM RDR DATA 6.1.2) Other changes to PDSDD ----------------------------- 6.1.2.1) New PDS keyword: SDU:TARGET_RIGHTUPOFFSETWRTLEFTBOT This is a new, mission-specific keyword; see DOCUMENT/ONLABELS.TXT and EXTRAS/PDSDD_NEW.FULL for details. 6.1.2.2) Change GENERAL_DATA_TYPE to DECIMAL for PDS keyword CHECKSUM The current GENERAL_DATA_TYPE value of INTEGER limits CHECKSUM values to signed 32-bit values (see Note 1); the CHECKSUM keyword is further limited to non-negative values (the MINIMUM is set to zero). The new SDU-C-NAVCAM-2-EDR-WILD2-V3.0 data set has one image label (N0643WE02.LBL) with a checksum of 2,155,792,173 (1024x1024 pixels with a mean value of 2055+), which is correct but exceeds the current upper limit (see Note 1). Changing the GENERAL_DATA_TYPE to decimal will remove that upper limit. Note that to complete this change the DESCRIPTION of the GENERAL_DATA_TYPE also designates of the CHECKSUM value as a "non-negative decimal sum." The downside of this change is that it allows floating point values for the CHECKSUM keyword, which is not correct. Alternative fixes: 1) add an UNSIGNED_INTEGER option to GENERAL_DATA_TYPE in the PDSDD; this will still fail for CHECKSUM values beyond the unsigned 32-bit limit (4,294,967,296). Note 1: INTEGER has a range of -2,147,483,648 to +2,147,483,647 inclusive; DESCRIPTION states the value is an "unsigned 32-bit sum," but the GENERAL_DATA_TYPE of INTEGER does not make such a distinction by itself when interpreted by validation tools. 7) Whom to Contact for further Information ========================================== Department of Astronomy Small Bodies Node University of Maryland College Park, MD 20742-2421 USA ludmilla@astro.umd.edu http://pdssbn.astro.umd.edu +01(301) 405-5024(o) +01(301) 405-3538(f)