Review Panel Telecon notes. 

• Red entries indicate actions to be taken to remove a lien. 
• Blue entries describe the steps taken to respond to the comment.

Review submitted by Nancy Chanover 9 Apr 2007

Here are my comments regarding my review of the reformatted CIRS data.

Compliance with PDS standards:

I didn't find anything wrong here, although I am by no means an expert in the PDS standards so I defer to Lyle on this.  The data volumes were structured as I expected, and with some familiarity with the STRUCTURE of PDS data sets, I had no trouble navigating through the volumes and finding what I need.

Scientific Merit of the Data:

Very high!!  Yes, these are definitely the proper data to be archived, and yes, the reformatted data are MUCH easier to work with!  I am not a Vanilla user - I tried it once and got very frustrated very quickly - so this is a welcome addition to the CIRS data archive.  After reading over the documentation I was able to read in some data using IDL and make plots of spectra with very little trouble.  I liked that you broke up a given observation by focal plane - this made it much easier to work with.

Usability of the Data:

Formats are appropriate.  Data set is very complete.  Documentation is comprehensive.  I wonder about the utility of providing sample software for reading in the data?  Or does that get too complicated because it is dependent on what sort of processor/platform the user has?  I thought of this because in going through some of the Huygens data, I noticed that some of the instrument teams did provide software in a SOFTWARE directory, even when the data were provided in ASCII format.  [They would say "we know it is not required to provide this software since the data are in ASCII format, but here it is anyway..."]

We will provide sample FORTRAN code for (at minimum) reading the binary files.

Resolution: A new SOFTWARE directory contains simple sample programs written in C and FORTRAN, as well as sample data and representative results. 

Comments on the documentation:

- In both the TUTORIAL.TXT and AAREADME.TXT files, in the section on file naming convention, you discuss the additional bbb suffix in the GEO data.  You define bbb as "the NAIF body ID indicating which moon's position and viewing geometry is described by the file..."  Since one of the options is 699 (Saturn), might it be better to replace the word "moon" with "target?"

We will fix.

Resolution: The text now says "body" instead of "moon".

- Calibration: is there a way of determining which calibration data were used to generate the "calibrated" spectra?  You may have said this somewhere, but I don't remember where.  As we all know, instrument calibrations change (improve?), and if someone is going to be accessing this calibrated data many years from now, it would be useful to know what "vintage" calibration files were used to reduce the data.

A column of the ISPM files provides the approximate or mean time of the the sky calibration data used for a particular spectrum.  We will note this in the documentation.

Resolution: This is noted (briefly) in Section 8 of TUTORIAL.TXT.

Conor noted that the calibration software continues to evolve at GSFC.  We will attempt to document the version of the software that was used to process each volume.

Resolution: The file DOCUMENT/RELNOTES.TXT now indicates which version of the CIRS calibration pipeline has been applied. It also contains the release notes provided by the team. The existence of this file is indicated in AAREADME.TXT and in DOCUMENT/DOCINFO.TXT.

OK, that's it for now.  I did find a misspelling in one of the CATALOG files, ispm_binary.fmt.  It was "Rayleigh peack" instead of peak, but I don't remember which file it was in.  I can tell you tomorrow during the telecon.

We will fix the typo.

Resolution: Fixed. It was in peer-review file DATA/APODSPEC/ISPM_ASCII.FMT (which is now renamed DATA/ISPMDATA/ISPMDATA.FMT).