PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = "Tony Farnham, 6 October 2003" RECORD_TYPE = STREAM SPACECRAFT_NAME = "DEEP SPACE 1" OBJECT = DATA_SET DATA_SET_ID = "DS1-C-MICAS-2-EDR-VISCCD-BORRELLY-V1.0" OBJECT = DATA_SET_INFORMATION DATA_SET_NAME = "DS1 MICAS IMAGES OF COMET 19P/BORRELLY" DATA_SET_COLLECTION_MEMBER_FLG = "N" DATA_SET_TERSE_DESC = "The Borrelly data set is a collection of images obtained by the Deep Space 1 MICAS instrument during the encounter with comet 19P/Borrelly. It includes both near and far data sets." START_TIME = STOP_TIME = DATA_SET_RELEASE_DATE = 2003-11-01 PRODUCER_FULL_NAME = "Tony Farnham" DETAILED_CATALOG_FLAG = "N" DATA_OBJECT_TYPE = "IMAGE" DATA_SET_DESC = " ---------------------------------------------------------------------------- NOTE: This is a temporary DATASET.CAT file. The DS1 program will be providing the DATASET.CAT file, but as yet, nothing has been submitted to the PDS SBN. This temporary file contains some basic information that may be useful for the data review process. Some additional information can be obtained from the USGS DS1 web site: http://astrogeology.usgs.gov/Projects/DeepSpace1/MICAS_Archive/index.htm ---------------------------------------------------------------------------- Data Set Overview ================= This data set contains pre-encounter and encounter images taken by the Deep Space 1 Miniature Integrated Camera-Spectrometer (MICAS) visible imager (VISCCD) during the encounter with comet 19P/Borrelly. In addition to the visible CCD imager, MICAS contains three other instruments: a Ultraviolet (UV) imaging spectrometer (which did not function properly), an Active Pixel Sensor (APS) imaging array, and a short-wavelength infrared (SWIR) imaging spectrometer. This catalog file only pertains to the VISCCD data from comet 19P/Borrelly. The images are all given in FITS format with detached pds labels. Far data Sequences ------------------- During the last month of approach, 11 far encounter sequences (far01-far11) were acquired with the VISCCD. Each of the different sequences is located in its own directory. The approximate times covered by these sequences are: Sequence Date Time from C/A -------- ----------- ------------- far01 25 Aug 2001 -29 day far02 29 Aug 2001 -25 day far03 07 Sep 2001 -16 day far04 10 Sep 2001 -13 day far05 13 Sep 2001 -10 day far06 15 Sep 2001 -08 day far07 16 Sep 2001 -07 day far08 18 Sep 2001 -05 day far09 20 Sep 2001 -03 day far10 21 Sep 2001 -02 day far11 22 Sep 2001 -11 hrs Near Data Sequence ------------------ The primary encounter imaging sequence (near_ccd) was collected with the VISCCD from about -85m through about -3m. All of the near_ccd data are located in the same directory. Some of the VISCCD images obtained during this phase were partial frames acquired for onboard navigation. For these files (labeled snip*), valid data was returned for only a 100x100 pixel square in which the onboard computer was tracking the target. File Naming Schemes -------------------- The filename of each image contains information describing different aspects of the observation. The terms used are as follows: Far data: 'far01' through 'far11' -- the far encounter sequence number. 'short' -- indicates short observations used for navigation and for establishing integration times. (Plans for 'long' exposures were discarded early, but the 'short' name was retained.) Near_ccd data: 'ccd' -- Denotes data obtained by the VISCCD during the encounter. 'rsen' -- Reduced State Encounter Navigation. Images used by the on-board system to identify, track, and predict the location of the nucleus for spacecraft pointing. 'srsen' -- ???? 'snip' -- Extracted sections of the full-frame images used for navigation. When the autotracking system identified the nucleus, a section of the CCD image containing the putative nucleus was extracted and saved as a snip. Used because the spacecraft did not have enough storage on board to save all the full-frame images taken during the encounter. 'far', 'mid', 'near' -- Describe the different phases of the encounter, in terms of the distance relative to closest approach. 'm1', m2' -- Mosaic images, taken when MICAS was pointed away from the predicted location of the nucleus, in case the actual location of the nucleus was not where it was predicted to be. 'bore' -- Images of the nucleus obtained between the two mosaics. These were obtained with MICAS pointed at the spacecraft's estimated location of the nucleus. 'streak' -- To obtain spatial information in the IR spectra, the spectrograph slit was panned across the nucleus. The 'streak' files were VISCCD images of the nucleus obtained during the time that the instruments were panning across the nucleus. numbering system -- The numbers at the end of the filename represent a numbering scheme that originally denoted the location of the frame in a sequence of images, the variation in an integration time, or a number of other pieces of information relating to the observation. As the design of the observations evolved, the logic of the filenames became less apparent, but was retained. Start Time and End Time ----------------------- The start and end times listed in the headers and the labels indicate the UT times of the image, as derived from the spacecraft clock (which is recorded in seconds in the NATIVE_START_TIME keyword. These times are accurate for dates after 13 Sep 2001. However, due to a clock reset and a lack of reference information, the times before 13 Sept 2001 are not accurate. It is not currently known how much the listed times deviate from the actual observation times. " END_OBJECT = DATA_SET_INFORMATION OBJECT = DATA_SET_REFERENCE_INFORMATION REFERENCE_KEY_ID = "N/A" END_OBJECT = DATA_SET_REFERENCE_INFORMATION OBJECT = DATA_SET_TARGET TARGET_NAME = "19P/BORRELLY 1 (1904 Y2)" END_OBJECT = DATA_SET_TARGET OBJECT = DATA_SET_HOST INSTRUMENT_HOST_ID = "DS1" INSTRUMENT_ID = "MICAS" END_OBJECT = DATA_SET_HOST END_OBJECT = DATA_SET END