Dave  & Lyle,

I spent yesterday looking over the UVIS peer 
review volume.  There are many errors in the 
details, but more importantly it is lacking the 
documentation necessary to use the data.  In my 
opinion the peer review will not be successful 
with the volume in its current state.  See my 
comments below.

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.

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.

3. .  Filenames are not inconsistent in 
SOFTWARE/CALIB/VERSION_1 directory.  Duplicates.

4.  Empty DOCUMENTATION directory under SOFTWARE.

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.

6.  DOCUMENT directory does not contain TXT versions of files.

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.

8.  There is an additional README file in the READERS directory

9.  Need documentation for the GEOMETRY 
directory.  If this is software, why is it not in 
the software directory.

10.  Directory D2000_279 has a file named EUV2000_279_01_56.LBL.Z.

11.  Why are the format descriptions embedded in 
the calibration file labels, but not the data 
file labels ? 

12.  UVIS.DOC - Needs a lot of work.

… File format objects should be included in the SIS.


… What  is the difference between a Qube and a Cube ?

… Is there calibration for non HSP and HDAC data 
?  It is not described in 2.2.5.  Calibration 
files are pretty much empty.

… 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.

… When you provide updated calibration files will 
there be a version_n in the software/calib 
directory as well ?

… section 2.2.5  - Change SOFTWARE/CALIBRATION to SOFTWARE/CALIB

… section 2.2.6 - Change PDS/CALIBRATION to PDS/CALIB
                                     Filenaming 
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. 

… section 2.3.3 has question marks.

… Please describe in section 2.5 how you plan to 
accomplish validation of the data for scientific 
content.

… 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
o Why is PRODUCT_CREATION_TIME         = UNK ?
o Why no value for SPACECRAFT_CLOCK_STOP_COUNT, you have STOP_TIME.
o INSTRUMENT_HOST_NAME          = "CASSINI ORBITER"
o Where are the compression_type values described ?

To describe the instrument configuration, the 
following, (except perhaps item 1), is needed in 
the labels.  See the attached PDF for a complete 
description. See attached file 
UVIS_IEB_EXPANDED.pdf

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)
(6) The Deuterium cell modulation table (this is a 16-entry table)

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)

The Far UltraViolet 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


The Extreme UltraViolet channel set up is described by 16 parameters
(1) Is the channel used or not in the setup
(2) The integration time (in seconds)
(3) The compression algorithm (n, sqrt_9, byte, sqrt_8).
(4) The entrance slit (hi_res, lo_res, occult)
(5) The occultation mechanism position (closed, open).
(6) The HVPS level (1 to 3)
(7) The description of window 1(a set of 6 integer)
(8) The description of window 2
ŠŠ.
(16) The description of window 10


… Should have editing markups removed - Accept all changes. 

… Include SIS ID IO-AR-024 on cover page at least.

… Signatures should include:

___________________________________
PI or Team Lead


___________________________________
Diane Conner
Cassini Archive Data Engineer


___________________________________
Your PDS Discipline Node Manager


___________________________________
Laverne Hall
PDS Project Manager


… Reference:
1. The Cassini Program Science Management Plan, 
PD699-006, Issue 006, July 1999.
Should be changed to:
2. The Cassini Program Science Management Plan, 
PD699-006, Issue 007, June 2003.














--