Data Set Overview : This data set has been generated by NASA's Galileo Project in order to distribute the processed calibration files to be used with the images acquired by the Solid State Imaging (SSI) camera to the scientists and later to the Planetary Data System (PDS). Included are all Dark Current files, Shutter Offset file, Blemish files and Slope Offset/Calibration files, required to work with all image files obtained from the SSI camera system from launch through End of Mission. This disc also contains the technical documentation necessary to understand how these files may be used, as well as the source code for the computer program which the SSI scientists use to apply these files.   Parameters : The Galileo SSI camera acquires data in a digital raster-format containing 800 scan lines and 800 samples per scan line. Each picture element (pixel) in the two dimensional image array is represented as an 8-bit value between 0 and 255, proportional to the amount of light detected at that point (with 0 being the least amount of light and 255 being the greatest amount of light). The camera is equipped with seven color filters and a clear filter such that images taken through complementary filters can be combined during ground processing to produce color images. To make full scientific use of the image collection, the radiometric and geometric properties of the camera system should be understood.  This disc, GO_0001, provides calibration files and technical documentation necessary for the understanding of the images produced by the SSI camera. Also note that, calibration files and software are available through the VICAR software system at MIPS, software are available through the ISIS software system at USGS, Flagstaff and SPICE files are available through the Galileo Project.   Processing : The processing done to create each type of calibration file are explained below. All calibration files were generated using the VICAR software. The user should refer to reference 1 for more details on the software programs.  Dark Current Files and Slope Offset/Radiometric Calibration Files ------------------------------------------------------------------ Dark Current files and Slope Offset (commonly called Radiometric Calibration Files or cal files) are generated by the VICAR program GALGEN. GALGEN generates radiometric files by fitting the data from a light transfer sequence to a linear model of the light-transfer curve.  GALGEN assumes a linear model of the light-transfer function. For a given line-sample coordinate (i,j), the light-transfer function is of the form: d(i,j) : c(i,j)e(i) + dc(i,j) (1)  where e(i) is the exposure at image line i, d(i,j) is the output camera signal (DN), and c(i,j) and dc(i,j) are the slope and offset (dark-current)terms.  GALGEN assumes that the intensity of the light source is held constant and that the exposure is varied by varying the shutter speed of the camera. The exposure e(i) is computed from the light of the light cannon, the commanded shutter time t, and the shutter offset to(i):  e(i) : l*[t - to(i)] (2)  GALGEN operates in two modes. In the default mode (FIT:LINEAR), GALGEN solves for both the slope and offset terms at each pixel position in the image by fitting a straight line (via least squares) through the input data points (extracted from input files (D1,D2,D3,...). The inverse of the slope (1/c) is output to the radiometric slope file (CAL) and the offset is output to DC. If FIT:SLOPE is specified, then GALGEN solves for the slope-term only by fitting the input points to the function:  d(i,j) : c(i,j)e(i) - do(i,j) (3)  where do(i,j) is extracted from the input dark-current file (DC). The inverse of the slope (1/c) is output to CAL and no DC file is output.  If the input frames have been pre-processed by PICSUM to sum multiple frames, GALGEN will normalize the data by dividing by the picture scale (extracted from the picture label) prior to performing the fit. The picture scale may be optionally input via the NUMB parameter.  For pixels with unsuccessful fits, the CAL file will receive a 0.0, the SAT, ERR, and RMS files will receive -1.0 and the DC file will receive 0.  While processing each pixel, if a saturated level is detected, that level and all higher levels are ignored. This saturation value is 255.   Blemish Files -------------- The VICAR program BLEMGEN is used to generate Blemish Files. BLEMGEN uses files produced by the VICAR program GALGEN. Blemish Files define each blemish as a vector of the form (LINE,SAMP,CLASS,SATDN), where LINE and SAMP are the picture coordinates where the blemish occurs, SATDN is the DN value at which the pixel saturates at full-well, and CLASS describes the interpolation algorithm to be used to remove the blemish. The vectors are sorted first on LINE, then on SAMP.  Two types of blemishes are stored in the Blemish File: 1) permanent blemishes and 2) low-full-well pixels. Low-full-well pixels are treated as blemishes only when the DN value exceeds the full-well capacity of the pixel. Permanent blemishes are identified by vectors with SAT:0. If SAT>0, then the vector represents a low-full-well pixel.  BLEMISH IDENTIFICATION:  A permanent blemish is any pixel which has one of the following characteristics:  o a light-transfer function whose slope or offset is excessively high or low.  o a lower-than-average full-well.  o light-transfer function nonlinearities greater than specified thresholds.  Blemishes are identified by applying user-specified thresholds to the slope (CAL), offset (DC), saturation DN, maximum error, and rms (RMS) associated with each pixel of the CCD and generated by the VICAR program GALGEN. BLEMGEN parameters (MINSLOPE,MAXSLOPE, MINDC,MAXDC, MINSAT, MAXERR, and MAXRMS) specified at the time the files are created are used as follows:  1) Let z and dc represent the slope and offset terms of the inverse light-transfer function  e : z(d-dc)  as extracted from input files CAL and DC, respectively. Then z and dc are acceptable if:  MINSLOPE < z < MAXSLOPE and MINDC < dc < MAXDC  Otherwise, the pixel is identified as a permanent blemish.  2) Let SATDN be the DN value at which full-well is reached, as extracted from the input file SAT. Then if  SATDN < MINSAT  the pixel is identified as a permanent blemish. Else if  SATDN < 32767  the pixel is identified as a low-full-well pixel.  3) Let EMAX represent the maximum absolute difference between the light-transfer data points and the fitted curve, as extracted from the input file ERR. Then if  EMAX > MAXERR  the pixel is identified as a permanent blemish.  4) Let ERMS represent the rms error resulting from the fit, as extracted from the input file RMS. Then if  ERMS > MAXRMS  the pixel is identified as a permanent blemish.   Shutter Offset File ------------------- The Shutter Offset File was generated by Ken Klaasen in Jan. 1993 from Earth 2 in-flight calibration PCT files. These images had the advantage of having high signal levels using the shortest exposure time (which is the most sensitive to shutter offset effects) as well as covering the entire image format allowing the shutter offset dependence on line number to be determined. The approach used was to determine the line-dependent shutter offset by comparing the SSI response in two PCT frames taken in the same filter at nearly the same spacecraft rotor clock angle - one frame having a short exposure (# 25 msec) and the other having a long (3 25 msec) exposure. The disadvantage of this approach is that the two different exposures were typically acquired in different camera gain states, and the changing rotor clock angle caused both the absolute brightness level of the PCT and the brightness nonuniformities across the PCT to vary somewhat between images. It turns out, however, that corrections for these effects can be made sufficiently accurately to yield useful shutter offset determinations. In-flight calibrations never indicated any drift in the pre-launch gain ratios (see below), so these were assumed in this analysis.  The variations in PCT brightness as a function of rotor clock angle were modeled based on the geometry of the PCT system on the spacecraft. The variations are expected to follow a sine function dependence on clock angle. The observed brightness variations in flight as determined using the pre-launch SSI radiometric calibration parameters closely approximated this sine dependence. However, some obvious departures from a smooth sine dependence are apparent; these departures are correlated with images taken with the shortest exposure time indicating that the pre-launch shutter offset was likely to be in error. An improved line-dependent shutter offset was determined using a pair of green-filter PCT images having commanded exposure times of 4 1/6 msec and 25 msec. The rotor clock angles of these two frames differed by only 17 deg; an adjustment based on a sine fit to the clock-dependent brightness was made, but the PCT shading differences were assumed to be negligibly small over this small rotor clock difference. The pre-launch zero-exposure calibration was used. The value at line 400 is 1.21 msec, about 1 msec longer than the prelaunch value and consistent with the star-based in-flight values. The uncertainty is estimated to be about 0.1 msec.   Ancillary Data : All document files and detached label files contain a carriage return character (ASCII 13) and a line feed character (ASCII 10) at the end of each record. This allows the files to be read by the MacOS, DOS, Unix, and VMS operating systems. Tabular files are also described by a detached PDS label. The PDS label file has the same name as the data file it describes, with the extension .LBL; for example, the file IMGINDEX.TAB is accompanied by the detached label file IMGINDEX.LBL in the same directory. The detached PDS labels for Calibration files contain information pertaining to the image.  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.   Software : The following CD-ROM copy, display and processing software has been successfully tested using the Galileo SSI data:  Copy Software:  --DCL Exchange/network (VMS) - for ASCII files - available with VMS. --DCL COPY (VMS) - available with VMS. --VICAR Copy (VMS and UNIX) - Available with VICAR package.  Display Software:  --NASAVIEW (PC, Apple Macintosh, UNIX-SUN OS) - Available from PDS. --VICAR XVD (VMS and UNIX) - Available with VICAR package --NIH IMAGE (Apple Macintosh) - A public domain program available from the National Institute of Health. --ISIS QVIEW or CV (UNIX) - Available with ISIS package  Processing Software:  --VICAR (VMS and UNIX) - Available through the Multimission Image Processing Lab at JPL - http://rushmore.jpl.nasa.gov/ --ISIS (UNIX) - Available through the USGS in Flagstaff http://wwwflag.wr.usgs.gov/   Media/Format : Each CD-ROM disc has been formatted such that a variety of computer systems may access the data. Specifically, the discs are formatted according to the ISO 9660 level 1 Interchange Standard, and file attributes are specified by Extended Attribute Records (XARs). Formats are based on standards for archive CD-ROM products established by PDS.

Confidence Level Overview : The SSI processed calibration files contain processed data as obtained during either ground calibration activities prior to launch, or during flight calibration periods. All of the files were processed by MIPL under consultation with the members of the SSI Team, who then evaluated each file to ensure the quality of the product. These files are currently in use by science team members in their analysis.  Included in the 'limitations' section are explanations of the VICAR and PDS keywords and values. This data set contains all calibration files necessary to process all image data acquired by the SSI camera system from launch through the End of Mission.   Review : The SSI Calibration disc was reviewed prior to archiving by members of the SSI team to ensure the latest calibration files were included and that the technical documentation provided was up-to-date. The format and documentation of the CD-ROM archive volume is reviewed by PDS. The mastered and replicated CD-ROM volumes received from the vendor are compared bit-by-bit with the original data to ensure the quality of the product.   Data Coverage and Quality : Blemish files on this disc and the Spacecraft Clock range they are valid for.  Filename Valid Spacecraft Clock (SCLK) Range -------------------------------------------------------------------- 7271s_blm02.img Valid for all files 7272f_blm02.img Valid for all files 7272s_blm02.img Valid for all files 7273f_blm02.img Valid for all files 7273s_blm02.img Valid for all files 7274f_blm02.img Valid for all files 7274s_blm02.img Valid for all files 7561s_blm02.img Valid for all files 7562f_blm02.img Valid for all files 7562s_blm02.img Valid for all files 7563f_blm02.img Valid for all files 7563s_blm02.img Valid for all files 7564f_blm02.img Valid for all files 7564s_blm02.img Valid for all files 8891s_blm02.img Valid for all files 8892f_blm02.img Valid for all files 8892s_blm02.img Valid for all files 8893f_blm02.img Valid for all files 8893s_blm02.img Valid for all files 8894f_blm02.img Valid for all files 8894s_blm02.img Valid for all files 9681s_blm02.img Valid for all files 9682f_blm02.img Valid for all files 9682s_blm02.img Valid for all files 9683f_blm02.img Valid for all files 9683s_blm02.img Valid for all files 9684f_blm02.img Valid for all files 9684s_blm02.img Valid for all files clr1s_blm02.img Valid for all files clr2f_blm02.img Valid for all files clr2s_blm02.img Valid for all files clr3f_blm02.img Valid for all files clr3s_blm02.img Valid for all files clr4f_blm02.img Valid for all files clr4s_blm02.img Valid for all files grn1s_blm02.img Valid for all files grn2f_blm02.img Valid for all files grn2s_blm02.img Valid for all files grn3f_blm02.img Valid for all files grn3s_blm02.img Valid for all files grn4f_blm02.img Valid for all files grn4s_blm02.img Valid for all files red1s_blm02.img Valid for all files red2f_blm02.img Valid for all files red2s_blm02.img Valid for all files red3f_blm02.img Valid for all files red3s_blm02.img Valid for all files red4f_blm02.img Valid for all files red4s_blm02.img Valid for all files vlt1s_blm02.img Valid for all files vlt2f_blm02.img Valid for all files vlt2s_blm02.img Valid for all files vlt3f_blm02.img Valid for all files vlt3s_blm02.img Valid for all files vlt4f_blm02.img Valid for all files vlt4s_blm02.img Valid for all files  Shutter Offset file on this disc and the Spacecraft Clock range it is valid for.  Filename Valid Spacecraft Clock Count (SCLK) range ---------------------------------------------------------- calibration_so02.img Valid for all files  Slope Offset/Radiometric Calibration files on this disc and the Spacecraft Clock range they are valid for.  Filename Valid Spacecraft Clock Count (SCLK) range ---------------------------------------------------------- 727f_cal01.dat 0 - 99757699 727f_cal03.dat 99757700 - 346405899 727f_cal04.dat 346405900 - 552443499 727f_cal05.dat 552443500 - now 727s_cal02.dat 99757700 - 346405899 727s_cal03.dat 346405900 - 552443499 727s_cal04.dat 552443500 - now 756f_cal01.dat 0 - 99757699 756f_cal03.dat 99757700 - 346405899 756f_cal04.dat 346405900 - 552443499 756f_cal05.dat 552443500 - now 756s_cal02.dat 99757700 - 346405899 756s_cal03.dat 346405900 - 552443499 756s_cal04.dat 552443500 - now 889f_cal01.dat 0 - 99757699 889f_cal03.dat 99757700 - 346405899 889f_cal04.dat 346405900 - now 889s_cal02.dat 99757700 - 346405899 889s_cal03.dat 346405900 - now 968f_cal01.dat 0 - 99757699 968f_cal03.dat 99757700 - 346405899 968f_cal04.dat 346405900 - now 968s_cal02.dat 99757700 - 346405899 968s_cal03.dat 346405900 - now clrf_cal01.dat 0 - 99757699 clrf_cal03.dat 99757700 - 346405899 clrf_cal04.dat 346405900 - 552443499 clrf_cal05.dat 552443500 - now clrs_cal02.dat 99757700 - 346405899 clrs_cal03.dat 346405900 - 552443499 clrs_cal04.dat 552443500 - now grnf_cal01.dat 0 - 99757699 grnf_cal03.dat 99757700 - 346405899 grnf_cal04.dat 346405900 - 552443499 grnf_cal05.dat 552443500 - now grns_cal02.dat 99757700 - 99757700 (obsolete by 03 version) grns_cal03.dat 99757701 - 346405899 grns_cal04.dat 346405900 - 552443499 grns_cal05.dat 552443500 - now redf_cal01.dat 0 - 99757699 redf_cal03.dat 99757700 - 346405899 redf_cal04.dat 346405900 - 552443499 redf_cal05.dat 552443500 - now reds_cal02.dat 99757700 - 346405899 reds_cal03.dat 346405900 - 552443499 reds_cal04.dat 552443500 - now vltf_cal01.dat 0 - 99757699 vltf_cal03.dat 99757700 - 346405899 vltf_cal04.dat 346405900 - 552443499 vltf_cal05.dat 552443500 - now vlts_cal02.dat 99757700 - 346405899 vlts_cal03.dat 346405900 - 552443499 vlts_cal04.dat 552443500 - now  Dark Current files on this disc and the Spacecraft Clock range they are valid for.  Filenames Valid Spacecraft Clock Count (SCLK) Ranges ------------------------------------------------------------------ 1s15_dc01.dat 0 - 345999999 1s15_dc02.dat 346000000 - 346000000 (obsolete by 03 version) 1s15_dc03.dat 346000001 - 346000001 (obsolete by 04 version) 1s15_dc04.dat 346000002 - 346405899 1s15_dc05.dat 346405900 - now 1s15x_dc01.dat 0 - 345999999 1s15x_dc02.dat 346000000 - 346405899 1s15x_dc03.dat 346405900 - now 1s2_dc02.dat 160000000 - 345999999 1s2_dc03.dat 346000000 - 346405899 1s2_dc04.dat 346405900 - now 1s2x_dc02.dat 160000000 - 345999999 1s2x_dc03.dat 346000000 - 346405899 1s2x_dc04.dat 346405900 - now 2f30_dc01.dat 0 - 99757700 2f30_dc02.dat 160000000 - 345999999 2f30_dc03.dat 346000000 - 346405899 2f30c_dc04.dat 346405900 - 584054599 2f30c_dc05.dat 584054600 - now 2f30r_dc01.dat 0 - 345999999 2f30r_dc02.dat 346000000 - 346405899 2f30r_dc04.dat 346405900 - 584054599 2f30r_dc05.dat 584054600 - now 2f30x_dc01.dat 0 - 99757700 2f30x_dc02.dat 160000000 - 345999999 2f30x_dc03.dat 346000000 - 346405899 2f30xc_dc04.dat 346405900 - 584054599 2f30xc_dc05.dat 584054600 - now 2f30xr_dc01.dat 0 - 345999999 2f30xr_dc02.dat 346000000 - 346405899 2f30xr_dc04.dat 346405900 - 584054599 2f30xr_dc05.dat 584054600 - now 2f60_dc01.dat 0 - 99757700 2f60_dc02.dat 160000000 - 345999999 2f60_dc03.dat 346000000 - 346405899 2f60_dc04.dat 346405900 - 584054599 2f60_dc05.dat 584054600 - now 2f60c_dc04.dat 346405900 - 584054599 2f60r_dc04.dat 346405900 - 584054599 2f60x_dc01.dat 0 - 99757700 2f60x_dc02.dat 160000000 - 345999999 2f60x_dc03.dat 346000000 - 346405899 2f60x_dc04.dat 346405900 - 584054599 2f60x_dc05.dat 584054600 - now 2f60xc_dc04.dat 346405900 - 584054599 2f60xr_dc04.dat 346405900 - 584054599 2f8_dc02.dat 160000000 - 345999999 2f8_dc03.dat 346000000 - 346405899 2f8_dc04.dat 346405900 - 584054599 2f8_dc05.dat 584054600 - now 2f8c_dc04.dat 346405900 - 584054599 2f8c_dc05.dat 584054600 - now 2f8r_dc01.dat 0 - 345999999 2f8r_dc02.dat 346000000 - 346405899 2f8r_dc04.dat 346405900 - 584054599 2f8r_dc05.dat 584054600 - now 2f8x_dc02.dat 160000000 - 345999999 2f8x_dc03.dat 346000000 - 346405899 2f8x_dc04.dat 346405900 - 584054599 2f8x_dc05.dat 584054600 - now 2f8xc_dc04.dat 346405900 - 584054599 2f8xc_dc05.dat 584054600 - now 2f8xr_dc01.dat 0 - 345999999 2f8xr_dc02.dat 346000000 - 346405899 2f8xr_dc04.dat 346405900 - 584054599 2f8xr_dc05.dat 584054600 - now 2s15_dc01.dat 0 - 345999999 2s15_dc02.dat 346000000 - 346000000 (obsolete by 03 version) 2s15_dc03.dat 346000001 - 346000001 (obsolete by 04 version) 2s15_dc04.dat 346000002 - 346405899 2s15_dc05.dat 346405900 - now 2s15x_dc01.dat 0 - 345999999 2s15x_dc02.dat 346000000 - 346405899 2s15x_dc03.dat 346405900 - now 2s2_dc02.dat 160000000 - 345999999 2s2_dc03.dat 346000000 - 346405899 2s2_dc04.dat 346405900 - now 2s2x_dc02.dat 160000000 - 345999999 2s2x_dc03.dat 346000000 - 346405899 2s2x_dc04.dat 346405900 - now 3f30_dc02.dat 160000000 - 345999999 (yes, this sclk range is correct) 3f30_dc03.dat 0 - 99757700 (yes, this sclk range is correct) 3f30_dc04.dat 346000000 - 346405899 3f30c_dc04.dat 346405900 - 584054599 3f30c_dc05.dat 584054600 - now 3f30r_dc01.dat 0 - 345999999 3f30r_dc02.dat 346000000 - 346405899 3f30r_dc04.dat 346405900 - 584054599 3f30r_dc05.dat 584054600 - now 3f30x_dc01.dat 0 - 99757700 3f30x_dc02.dat 160000000 - 345999999 3f30x_dc03.dat 346000000 - 346405899 3f30xc_dc04.dat 346405900 - 584054599 3f30xc_dc05.dat 584054600 - now 3f30xr_dc01.dat 0 - 345999999 3f30xr_dc02.dat 346000000 - 346405899 3f30xr_dc04.dat 346405900 - 584054599 3f30xr_dc05.dat 584054600 - now 3f60_dc01.dat 0 - 99757700 3f60_dc02.dat 160000000 - 345999999 3f60_dc03.dat 346000000 - 346405899 3f60_dc04.dat 346405900 - 584054599 3f60_dc05.dat 584054600 - now 3f60c_dc04.dat 346405900 - 584054599 3f60r_dc04.dat 346405900 - 584054599 3f60x_dc01.dat 0 - 99757700 3f60x_dc02.dat 160000000 - 345999999 3f60x_dc03.dat 346000000 - 346405899 3f60x_dc04.dat 346405900 - 584054599 3f60x_dc05.dat 584054600 - now 3f60xc_dc04.dat 346405900 - 584054599 3f60xr_dc04.dat 346405900 - 584054599 3f8_dc02.dat 160000000 - 345999999 3f8_dc03.dat 346000000 - 346405899 3f8_dc04.dat 346405900 - 584054599 3f8_dc05.dat 584054600 - now 3f8c_dc04.dat 346405900 - 584054599 3f8c_dc05.dat 584054600 - now 3f8r_dc01.dat 0 - 345999999 3f8r_dc02.dat 346000000 - 346405899 3f8r_dc04.dat 346405900 - 584054599 3f8r_dc05.dat 584054600 - now 3f8x_dc01.dat 0 - 345999999 3f8x_dc02.dat 346405900 - 584054599 3f8x_dc03.dat 584054600 - now 3f8xc_dc02.dat 346405900 - 584054599 3f8xc_dc03.dat 584054600 - now 3f8xr_dc01.dat 0 - 345999999 3f8xr_dc02.dat 346000000 - 346405899 3f8xr_dc03.dat 346405900 - 584054599 3f8xr_dc04.dat 584054600 - now 3s15_dc01.dat 0 - 345999999 3s15_dc02.dat 346000000 - 346000000 (obsolete by 03 version) 3s15_dc03.dat 346000001 - 346405899 3s15_dc04.dat 346405900 - now 3s15x_dc01.dat 0 - 345999999 3s15x_dc02.dat 346000000 - 346405899 3s15x_dc03.dat 346405900 - now 3s2_dc02.dat 160000000 - 345999999 3s2_dc03.dat 346000000 - 346405899 3s2_dc04.dat 346405900 - now 3s2x_dc02.dat 160000000 - 345999999 3s2x_dc03.dat 346000000 - 346405899 3s2x_dc04.dat 346405900 - now 4f30_dc02.dat 160000000 - 345999999 (yes, this sclk range is correct) 4f30_dc03.dat 0 - 99757700 (yes, this sclk range is correct) 4f30_dc04.dat 346000000 - 346405899 4f30c_dc04.dat 346405900 - 584054599 4f30c_dc05.dat 584054600 - now 4f30r_dc01.dat 0 - 345999999 4f30r_dc02.dat 346000000 - 346405899 4f30r_dc04.dat 346405900 - 584054599 4f30r_dc05.dat 584054600 - now 4f30x_dc02.dat 160000000 - 345999999 (yes, this sclk range is correct) 4f30x_dc03.dat 0 - 99757700 ( yes, this sclk range is correct) 4f30x_dc04.dat 346000000 - 346405899 4f30xc_dc04.dat 346405900 - 584054599 4f30xc_dc05.dat 584054600 - now 4f30xr_dc01.dat 0 - 345999999 4f30xr_dc02.dat 346000000 - 346405899 4f30xr_dc04.dat 346405900 - 584054599 4f30xr_dc05.dat 584054600 - now 4f60_dc01.dat 0 - 99757700 4f60_dc02.dat 160000000 - 345999999 4f60_dc03.dat 346000000 - 346405899 4f60_dc04.dat 346405900 - 584054599 4f60_dc05.dat 584054600 - now 4f60c_dc04.dat 346405900 - 584054599 4f60r_dc04.dat 346405900 - 584054599 4f60x_dc01.dat 0 - 99757700 4f60x_dc02.dat 160000000 - 345999999 4f60x_dc03.dat 346000000 - 346405899 4f60x_dc04.dat 346405900 - 584054599 4f60x_dc05.dat 584054600 - now 4f60xc_dc04.dat 346405900 - 584054599 4f60xr_dc04.dat 346405900 - 584054599 4f8_dc02.dat 160000000 - 345999999 4f8_dc03.dat 346000000 - 346405899 4f8_dc04.dat 346405900 - 584054599 4f8_dc05.dat 584054600 - now 4f8c_dc04.dat 346405900 - 584054599 4f8c_dc05.dat 584054600 - now 4f8r_dc01.dat 0 - 345999999 4f8r_dc02.dat 346000000 - 346405899 4f8r_dc04.dat 346405900 - 584054599 4f8r_dc05.dat 584054600 - now 4f8x_dc01.dat 160000000 - 345999999 4f8x_dc02.dat 346000000 - 346405899 4f8x_dc03.dat 346405900 - 584054599 4f8x_dc04.dat 584054600 - now 4f8xc_dc03.dat 346405900 - 584054599 4f8xc_dc04.dat 584054600 - now 4f8xr_dc01.dat 0 - 345999999 4f8xr_dc02.dat 346000000 - 346405899 4f8xr_dc03.dat 346405900 - 584054599 4f8xr_dc04.dat 584054600 - now 4s15_dc01.dat 0 - 345999999 4s15_dc02.dat 346000000 - 346000000 (obsolete by 03 version) 4s15_dc03.dat 346000001 - 346000001 (obsolete by 04 version) 4s15_dc04.dat 346000002 - 346405899 4s15_dc05.dat 346405900 - now 4s15x_dc01.dat 0 - 345999999 4s15x_dc02.dat 346000000 - 346405899 4s15x_dc03.dat 346405900 - now 4s2_dc02.dat 160000000 - 345999999 4s2_dc03.dat 346000000 - 346405899 4s2_dc04.dat 346405900 - now 4s2x_dc02.dat 160000000 - 345999999 4s2x_dc03.dat 346000000 - 346405899 4s2x_dc04.dat 346405900 - now   Limitations : This section documents the currently known information about errors and discrepancies in the VICAR labels, and PDS labels and index tables for the processed calibration data set.  Information regarding errors in technical documentation provided on this disc can be found in the ERRATA.TXT.