Hi Lyle,

Looks like many of the same problems with the UVIS documentation, index
and labels as back in November. Without Java functioning, it is
difficult to understand the data. It does appear that the documentation
explaining the data format has been greatly improved, but not enough 
for me to generate properly calibrated data.

-Mark

Cassini UVIS review                                      2004-June-02
Mark B. Vincent
PDS Atmospheres Node


ReadPDSObject.jar using Java 1.4.2 ran through the file selection
menu, then failed when clicking on last menu (JAVA, IDL, NONE).
It generated this message and error:

Warning: Cannot allocate colormap entry for default background.
Processing: /home/viking1/mvincent/CO_UVIS/DATA/D2000_296/EUV2000_296_03_35 (0 out of 1 files 
java.text.ParseException: MessageFormat parse error!
        at java.text.MessageFormat.parse(MessageFormat.java:999)
        at PDSObjectReader.load(PDSObjectReader.java:486)
        at PDSObjectReader.process(PDSObjectReader.java:172)
        at PDSObjectReader.main(PDSObjectReader.java:142)
Error: MessageFormat parse error! skipping file: /home/viking1/mvincent/CO_UVIS/DATA/D2000_296/EUV2000_296_03_35
Done

SOFTWARE/READERS/README/ReadPDSObject.jar should include the source
code to allow future users make modifications to keep code current with
the latest version of Java and IDL.

I am able to use IDL to read the data and calibration files as integer
arrays and then plot them. Though, I am trying to work out the
wavelength binning and calibration. From a quick look at
Get_FUV_03_Lab_Calibration, calibration can be somewhat complicated for
binned data. Some examples of data calibration would be useful.


The AAREADME.TXT is very detailed and very useful, thanks.


INDEX/INDEX.TAB There are no column delineators. 
Spaces between collumns much larger than necessary.
Only HDAC files are in INDEX.TAB, no EUV or FUV files.
All TARGET names are N/A. Could the target(s) be listed?

INDEX/INDEX.TAB and DATA/*/*.LBL
The SC_PLANET_POSITION_VECTOR is identical to the
SC_TARGET_POSITION_VECTOR. Both are very close to one jovian radius
larger than CENTRAL_BODY_DISTANCE. It appears that the
CENTRAL_BODY_DISTANCE as listed is actually the altitude above the
location on the target intersected by the boresight.

Should the magnitude of the SC_PLANET_POSITION_VECTOR be equal to the
CENTRAL_BODY_DISTANCE?

Should the SC_TARGET_POSITION_VECTOR be the vector of the instrument
boresight to the surface interscept point?

Please check how the geometry values are generated and their
definitions.

INDEX/INDEX.LBL No target Latitude and Longitude, nor Clock Angle to
describe where the instrument boresite pointing and slit orientation.
Same same data should be included in each label.


INDEX/INDEX.TAB, INDEX.LBL It does not appear that the INDEX.LBL and
INDEX.TAB are matched.  Example: SUB_SOLAR_LATITUDE jumps between 11.4,
62.2, -11.1 and other values. This does not sound physically possible
in the jovian system.

INDEX/INDEX.TAB has three collumns of N/A between what appears to be
the EMISSION_ANGLE and CENTRAL_BODY_DISTANCE. INDEX.LBL lists only the
SOLAR_INCIDENCE_ANGLE between the two values.


CATALOG/INSTHOST.CAT and SOFTWARE/CALIB/VERSION_1 Get_*_Calibration.pro's 
all run on as one long line.

It would be useful if all text files were reformated to at most 78
characters wide and run through PDSLINE80. PDSLINE80.pro makes all line
80 characters long including carriage return and line feeds, ask Mark
Vincent for code. Some text files do not contain the carriage return,
"^M", example CATALOG/CO_UVIS_inst.cat.

SOFTWARE/READERS/README "When the program is running, users will will..."
Delete second "will".

No documents in SOFTWARE/DOCUMENTATION/.

CATALOG/PROJREF.CAT contains only two references regarding Casini. 
Please consider including relevent published science papers.


Summary: The documentation has improved since the November 2003 review. 
Including space_science_review_article.pdf is greatly appreciated. Work 
is still required on three fronts. 1) Including reliable software and 
examples to aid users in reading and calibrating the data. 2) Improving 
geometry values. 3) Reformating text files.