1. The algorithm for applying calibration to files is not documented. There is one hint in the SOFTWARE/CALIB/README file that the calibration files are multiplicands of the data files for FUV/EUV. However, for HSP and HDAC channels there is no clue. There needs to be clear documentation that describes how the calibration files were created for each channel and how to apply them to the data files to achieve a calibrated data file. See UVIS.DOC, Calibration Data for a description of the calibration data products and how to use them See SOFTWARE/CALIB/README for a description of how to use the calibration data See CALIB/VERSION_1/D2000_278/EUV2000_278_17_21.LBL (et. al.), DESCRIPTION keyword for a description of a calibration product and how to use it. See UVIS.DOC, Computation of Calibration Data for the location of calibration procedures and data. Users will need to read the algorithm. -- I have added the following to sec : “HSP and HDAC do not currently have a calibration process.” Also, I will not generate HDAC and HSP calibration data files since they are trivial.

2. Make it clear that the user must have IDL to use the calibration and geometry IDL programs. What these programs do is not described anywhere. Even if you are including them just for information you should provide documentation. Users should not use the calibration algorithms and, hence, do not need IDL. See UVIS.DOC section Calibration Data, in particular, “Since these algorithms are used to generate calibration data, and since the calibration data are supplied, these algorithms are for reference only. “ Users should not use the geometry algorithm since all geometry values are contained in the labels, hence users do not need IDL. See UVIS.DOC, Computation of Pointing Geometry, in particular, “The geometry values included in the data object are computed using the geometry_engine.pro.” (ibid.) The preceding references also explain the purpose of the calibration and geometry algorithms. The mechanism for calibrating data is referenced on the preceding page -I have added the following text to the AAREADME.TXT file: “The files in this directory are used to produce the geometry keyword values contained in the data object labels. User’s should use these keyword values, the geometry programs are for reference only.” Also, “Users should use the calibration data contained under the CALIB/VERSION_n directory. These calibration programs are for reference only.” I will add this to SOFTWAREINFO.TXT

3.. Filenames are not inconsistent in SOFTWARE/CALIB/VERSION_1 directory. Duplicates. --I have removed the …_save and …_original files

4. Empty DOCUMENTATION directory under SOFTWARE. -- I have removed this until we have some documentation. 5. When first reading the DATA_OBJECT_READERS_README.TXT file, it sounds like a user needs to have java and IDL to use the utilities. Please make it clear in the first paragraph if the user has a choice between IDL and Java. -- I have changed “and” to “and optionally” 6. DOCUMENT directory does not contain TXT versions of files. I can probably convert UVIS.DOC to text but the Space Science Review article contains lots of mathematical symbols and diagrams so it probably is not convertible. 7. Index file incomplete. Only HDAC data, and some rows are full of N/As. No CUMINDEX file identified in AAREADME or included on volume. This is an error which will be fixed. 8. There is an additional README file in the READERS directory I have removed the extraneous README file.

9. Need documentation for the GEOMETRY directory. If this is software, why is it not in the software directory. Documentation describing geometry is contained in UVIS.DOC, Computation of Pointing Geometry and in the geometer_engine.pro code. The UVIS.DOC text can be copied to a README file. The volume directory is root/SOFTWARE/GEOMETRY I will put the stuff into SOFTWAREINFO.TXT 10. Directory D2000_279 has a file named EUV2000_279_01_56.LBL.Z. -- I have deleted it. 11. Why are the format descriptions embedded in the calibration file labels, but not the data file labels ? I have added a description of the wavelength mapping contained in the BAND_BIN_CENTER value to the SIS

-- I have added an appendix which gives definitions of UVIS label keywords 12a. … File format objects should be included in the SIS. 12b… What is the difference between a Qube and a Cube ? A cube is what the UVIS science team calls an EUV/FUV observation which has a spatial and spectral component. These cubes are stored in PDS Qube objects. 12c… Is there calibration for non HSP and HDAC data -- No. I have added the following statement to Sec 2.5.5: “HSP and HDAC do not currently have a calibration process.” 12d… Where are the algorithms that are used to apply the calibration described? These would be the ones used in the java and IDL code. There is no documentation in the CALIB directory as described in the SIS section 3.1. See UVIS.DOC, Calibration Data See SOFTWARE/CALIB/README See CALIB/VERSION_1/D2000_278/EUV2000_278_17_21.LBL (et. al.), DESCRIPTION keyword SIS Section 3.1 contains the statement: “These calibration routines are …for reference only.“ This means that the calibration routines are reference material. -- I have added this to SOFTWAREINFO.TXT as well

12e… When you provide updated calibration files will there be a version_n in the software/calib directory as well ? Yes, see UVIS.DOC sec Labeling and Identification, in particular, “For example, calibration data contained under …/VERSION_2…”. The current scenario for handling versioning will work for instrument evolution. In the case of large-volume regeneration of calibration data, for example, a hypothetical version 5 which applies to all data from 1999 to 2005 we will issue a CD which contains exclusively calibration data using the same organization and conventions as all other volumes 12f… section Change SOFTWARE/CALIBRATION to SOFTWARE/CALIB 12g… section Change PDS/CALIBRATION to PDS/CALIB -- done 12h File naming convention described does not match data on volume. Please make filenames unique. Calibration data have the same exact filenames and PRODUCT_IDs as their corresponding data files. PRODUCT_Ids must be unique. Filenames should be unique. PRODUCT_ID for calibration data will be changed. -- I have changed the example in the SIS to be consistent with the data files.

12i… section has question marks. -- These have been replaced with “5.6”. 12j… Please describe in section 2.5 how you plan to accomplish validation of the data for scientific content. Section 2.5 says: “There is no validation of the scientific content of these files.” What this means is that we cannot evaluate each observation to confirm that it contains meaningful data, we will confirm that the data was taken correctly and that it is formatted correctly. This will be replaced by the statement: “Ongoing scientific analysis will be used to identify any problems with scientific content of the PDS volume.” 12k … Appendix A ( Need to fill in the rest of the appendices ) o What component of the Science planning process does this relate to ? ODC_ID -- This has been defined in a new appendix containing keyword definitions o Why is PRODUCT_CREATION_TIME = UNK ? because the product has not been created yet. o Why no value for SPACECRAFT_CLOCK_STOP_COUNT, you have STOP_TIME. we compute STOP_TIME, we do not have a telemetry value corresponding to SPACECRAFT_CLOCK_STOP_COUNT o INSTRUMENT_HOST_NAME = "CASSINI ORBITER“ -- INSTRUMENT_HOST_NAME has been changed to “CASSINI ORBITER” o Where are the compression_type values described ? in the PDS data dictionary, -- also this has been defined in a new appendix containing keyword definitions

To describe the instrument configuration, the following, (except perhaps item 1), is needed in the labels. The Hydrogen Deuterium Absorption Cell setup is described by 6 parameters (1) Is channel used or not used in the setup (2) The integration time (in seconds) (3) The dwell time (in seconds) (4) The compression algorithm (no compression, sqrt_9, byte, sqrt_8) (5) The Hydrogen cell modulation table (this is a 16-entry table) DWELL_TIME = 1 COMPRESSION_TYPE = "NONE" D_LEVEL = (0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) H_LEVEL = (0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) The integration time for the HDAC is a constant seconds and, since it is always the same, is not included in the label

The High Speed Photometer set up is described by three parameters: (1) Is the channel used or not used in the setup (3) The integration time (in seconds) (3) The compression algorithm (no compression, sqrt_9, byte, sqrt_8) INTEGRATION_DURATION = 1 COMPRESSION_TYPE = "SQRT_9"

The Far Ultra-Violet channel set up is described by15 parameters: (1) Is the channel used or not the setup (2) The integration time (in seconds) (3) The compression algorithm (no compression, sqrt_9, byte, sqrt_8). (4) The entrance slit (hi_res, lo_res, occult) (5) The HVPS level (1 to 3) (6) The description of window 1(a set of 6 integer) (7) The description of window 2 (15) The description of window 10 INTEGRATION_DURATION = COMPRESSION_TYPE = "SQRT_9" HI_VOLTAGE_POWER_SUPPLY_STATE = 1 OCCULTATION_PORT_STATE = N/A SLIT_STATE = HIGH_RESOLUTION TEST_PULSE_STATE = ON UL_CORNER_LINE = 0 UL_CORNER_BAND = 0 LR_CORNER_LINE = 63 LR_CORNER_BAND = 1023 BAND_BIN = 1 LINE_BIN = 2