12 January 2004 ATMOS - Volume COCIRS_0101 (1) AAREADME.TXT (a) File is not FIXED_LENGTH, it is STREAM. This means make the following changes: (1) Change to: RECORD_TYPE = STREAM (2) Delete from file: RECORD_BYTES = 80 (b) An issue that you, Lyle and I should discuss is that fact that Vanilla is the only tool that users can use to display the data. Of the archive products in the PDS, approx. 99% can be displayed using one of the approved PDS validation tools (eg., NASAVIEW, TBTOOL, etc). I only know of two products within the archive that cannot be displayed using one of the PDS tools - MOC and TES. The reason that the products cannot be displayed is because they used non-PDS formats and/or the the products were not labelled properly. I am going to push very hard to have a discussion within the PDS Management Council on requiring all archive products to adhere to one of the PDS approved data formats which means that the product is displayable by one of the PDS tools. (c) With respect to: 2. Disk format This is formatted according to the ISO-9660 standard. If you are using file and directory names that are 8.3, then use "ISO-9660_LEVEL1". If you are using file and directory names longer than 8.3 (which you are), then use "ISO-9660_LEVEL2". (2) VOLDESC.CAT (a) Change: PDS_VERSION_ID = PDS3 to: PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM (b) Change: MEDIUM_FORMAT = "TBD" to: MEDIUM_FORMAT = "650_MB" (c) Change: VOLUME_FORMAT = "ISO-9660" to: VOLUME_FORMAT = "ISO-9660_LEVEL1" If you are using file and directory names longer than 8.3 (which you are), then use: VOLUME_FORMAT = "ISO-9660_LEVEL2" (d) Change: VOLUME_SET_ID = "COCIRS" VOLUME_SET_NAME = "CASSINI INFRARED SPECTRA" to: Values more representative of other standard values: Example: USA_NASA_PDS_GO_0017 - GALILEO EARTH/MOON NIMS EXPERIMENT DATA RECORDS V1.0 USA_NASA_PDS_CL_0001 - CLEMENTINE: EDR IMAGE ARCHIVE V1.0 USA_NASA_PDS_CL_0002 - CLEMENTINE: EDR IMAGE ARCHIVE V1.0 (e) Is this really representative of the facility name: FACILITY_NAME: PLANETARY SYSTEMS BRANCH CODE 693 (3) ERRATA.TXT (a) With respect to this note in the ERRATA.TXT file: WARNING!!! files in the SOFTWARE directory and sub-directories do not have PDS labels. All files must be labeled. It is not appropriate to indicate that some are not. This is a hard requirement. You and Lyle and I need to talk about this. (4) ERRATA.LBL (a) Files having an extension .TXT are labeled using a TEXT object (in the label file). Files having an extension of .ASC are labeled using the ASCII_DOCUMENT object. Here is an example of a ERRATA.LBL file: PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM ^TEXT = "ERRATA.TXT" OBJECT = TEXT PUBLICATION_DATE = 1998-05-01 NOTE = "ERRATA.TXT reflects any changes or errors made to the VG_1501 volume." END_OBJECT = TEXT END You might also consider using an attached label file (i.e., attaching the .TXT file to the .LBL file. (5) CATALOG/MISSION.CAT INSTHOST.CAT (a) CATALOG/INSTHOST.CAT: Line 797 - MISSION_REFERENCE_INFORMATION: Not an allowed sub-object. (It was not found on the optional or required sub-objects list) (b) I assume these are the most recent versions and the above errors are no longer present. (6) CATALOG/INST.CAT (a) This file could use some work. For instance, most, if not all, INSTRUMENT templates start with: INSTRUMENT_DESC = " Instrument Overview =================== (b) See page B-1 of the Standards Reference for a description of Field Formatting. (I have asked S.Adams to do this). (c) Add as line 8: INSTRUMENT_HOST_ID = "CO" new line 9: INSTRUMENT_ID = "CIRS" (d) Ensure that this is correct: REFERENCE_KEY_ID = "KUNDE1996" The citation lists ETAL which I suspect is not correct. (e) Remove line 170 & 171: REFERENCE_DESC = "Kunde et al, Cassini Infrared Fourier Spectroscopic Investigation, SPIE Vol. 2803, pp162-177, 1996" These two lines do not belong in the template. (7) CATALOG/DATASET.CAT (a) The DATA_SET_NAME is a direct reflection of the DATA_SET_ID. There is a 1 to 1 correspondence between each identifier in the ID and the NAME. Also, the NAME must be uppercase. The NAME must also include the Version. DATA_SET_ID = "CO-J-CIRS-2/3/4-TSDR-V1.0" Change: DATA_SET_NAME = " Cassini CIRS Time-Sequential Data Records" to: DATA_SET_NAME = "CASSINI JUP CIRS TIME SEQUENTIAL DATA RECORDS V1.0" You might consider adding "EDITED" or one of the other data types to the title. (b) At this point, I would expect the following keywords to have proper values (with the possible exception of CONFIDENCE_LEVEL_NOTE): ARCHIVE_STATUS = "UNK" DATA_OBJECT_TYPE = "UNK" DATA_SET_TERSE_DESC = "UNK" CONFIDENCE_LEVEL_NOTE = "UNK" (c) Change in line 317: "Voyager-class" to: 'Voyager-class' (d) Change in line 590: INSTRUMEN_HOST_ID = "CO" to: INSTRUMENT_HOST_ID = "CO" (e) Change: REFERENCE_KEY_ID = "KUNDE ET AL 1996" to: REFERENCE_KEY_ID = "KUNDEETAL1996" Note: Ensure that this is the correct REFERENCE_KEY_ID in the Cassini project reference file (i.e., that there are not spaces in the ID and this is the proper citation). (f) Remove line 597 & 598: REFERENCE_DESC = "Kunde et al, Cassini Infrared Fourier Spectroscopic Investigation, SPIE Vol. 2803, pp162-177, 1996" These two lines do not belong in the DATASET.CAT file. (8) CATALOG/CATINFO.TXT (a) Files having an extension .TXT are labeled using a TEXT object (in the label file). Files having an extension of .ASC are labeled using the ASCII_DOCUMENT object. Here is an example of a CATINFO.LBL file: PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM ^TEXT = "CATINFO.TXT" OBJECT = TEXT PUBLICATION_DATE = 1998-05-01 NOTE = "CATINFO.TXT describes the contents of this directory." END_OBJECT = TEXT END (9) CATALOG/PERSON.CAT (a) Check the values for LAST_NAME for each object. Two have a value of NIXON instead of the correct last name of the person. (b) Change: REGISTRATION_DATE = "1990-02-09" to: REGISTRATION_DATE = 1990-02-09 Keyword-values having a data_type of DATE must not be quoted. Make this change everywhere: CATALOG/PERSON.CAT: Line 118 CATALOG/PERSON.CAT: Line 17 CATALOG/PERSON.CAT: Line 43 CATALOG/PERSON.CAT: Line 68 CATALOG/PERSON.CAT: Line 93 (10) CATALOG/PROJREF.CAT (a) Add to lines 19 and 20: END_OBJECT = REFERENCE END (11) CATALOG/TARGET.CAT (a) Change: TARGET_DESCRIPTION = " to: TARGET_DESC = " TARGET_DESCRIPTION is not a valid keyword. (12) DOCUMENT directory (a) There are a number of files in this directory that are being listed with lowercase file names. All files must be uppercase. (13) DOCUMENT/DOCINFO.LBL (a) Files having an extension .TXT are labeled using a TEXT object (in the label file). Files having an extension of .ASC are labeled using the ASCII_DOCUMENT object. Here is an example of a DOCINFO.LBL file: PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM ^TEXT = "DOCINFO.TXT" OBJECT = TEXT PUBLICATION_DATE = 1998-05-01 NOTE = "DOCINFO.TXT lists the contents of this directory." END_OBJECT = TEXT END (b) Normally, this file only lists those files that are contained in the DOCUMENT directory (and not document directories in the SOFTWARE directory). You might consider creating a separate LBL file for the files in the SOFTWARE/DOC directory. (14) DOCUMENT/CIRS_FOV_OVERVIEW_FIG1.LBL CIRS_FOV_OVERVIEW_FIG1.TIFF (a) The label file for the TIFF file should use a TIFF_DOCUMENT pointer - see Section 9.1.2 of the Standards. (b) Note that I have changed the TIFF file name to be uppercase. Change all values in the archive volume to uppercase unless they can be mixed case; such as, DESCRIPTION keyword-values. Most of the file names in the LBL files in this director have lowercase file names. (c) I have modified the label: PDS_VERSION_ID = PDS3 RECORD_TYPE = UNDEFINED ^TIFF_DOCUMENT = "CIRS_FOV_OVERVIEW_FIG1.TIFF" OBJECT = TIFF_DOCUMENT DOCUMENT_NAME = "CIRS documentation" DOCUMENT_TOPIC_TYPE = "CIRS DOCUMENTATION" INTERCHANGE_FORMAT = BINARY PUBLICATION_DATE = 2003-11-27 DOCUMENT_FORMAT = "TIFF" END_OBJECT = TIFF_DOCUMENT END (15) DOCUMENT/CIRS_CONCEPT_HIRES.LBL CIRS_CONCEPT_HIRES.EPS (a) The label file for the EPS document should use a EPS_DOCUMENT pointer - see section 9.1.2 of the Standards. PDS_VERSION_ID = PDS3 RECORD_TYPE = UNDEFINED ^POSTSCRIPT_DOCUMENT = "cassini-rsp.ps" OBJECT = POSTSCRIPT_DOCUMENT DOCUMENT_NAME = "CIRS documentation" DOCUMENT_TOPIC_TYPE = "CIRS DOCUMENTATION" INTERCHANGE_FORMAT = ASCII PUBLICATION_DATE = 2003-11-27 DOCUMENT_FORMAT = "POSTSCRIPT" END_OBJECT = POSTSCRIPT_DOCUMENT END (b) I have not reviewed each label in this directory. Given some of the anomalies noted above, more review is probably a good idea. (16) DOCUMENT/C23PHASEB_SUM.LBL DOCUMENT/C23PHASEC_SUM.LBL DOCUMENT/C23PHASED_SUM.LBL DOCUMENT/C23PHASEE_SUM.LBL (a) These are DOCUMENT files, not TABLE files. They should be labeled as DOCUMENT files and they should have an extension of .ASC and not .TAB. The TABLE object is a very specific PDS format and carries a number of constraints that you probably don't want to deal with. Or, you can use the SPREADSHEET object to describe the type of data in these files. (17) INDEX/INDXINFO.LBL INDXINFO.TXT (a) The TXT file indicates that there is a CUMINDEX file, but it is not in the directory. Also, VOLDESC.CAT indicates that this is a single archive volume (in which case there should not be a CUMINDEX). (b) Here is an example of a INDXINFO.LBL file: PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM ^TEXT = "INDXINFO.TXT" OBJECT = TEXT PUBLICATION_DATE = 1998-05-01 NOTE = "INDXINFO.TXT describes the contents of this directory." END_OBJECT = TEXT END (18) INDEX/INDEX.LBL (a) The DESCRIPTION indicates the wrong number of bytes: DESCRIPTION = "INDEX.TAB lists all data files in this volume. Rows in this table contain 167 bytes of table data followed by one pair." (b) The DATA_SET_ID keyword has no value which is causing TBTOOL not to function properly. You can either remove this keyword or give it a value. (19) SOFTWARE/SOFTINFO.TXT (a) This file is not labeled. Include a SOFTINFO.LBL file. (20) DATA/DATAINFO.LBL (a) Files having an extension .TXT are labeled using a TEXT object (in the label file). Files having an extension of .ASC are labeled using the ASCII_DOCUMENT object. (21) DATA/APODSPEC/DATASET.LBL (a) Files having an extension .TXT are labeled using a TEXT object (in the label file). Files having an extension of .ASC are labeled using the ASCII_DOCUMENT object. (22) DATA/APODSPEC/ISPM.FMT ISPM.LBL (a) ISPM.FMT is a label file which should not itself have a label file describing it. - Delete: ISPM.LBL (and any other label files that describe FMT files) (b) If this file is used within labels which are in multiple directories, you could include this file and the other FMT files in a LABEL directory. I noticed that the ISPM.FMT file and the SPM.FMT file are almost identical with the exception of some of the column names. (23) DATA/APODSPEC/CIRS-ISPM01010100.LBL (a) The label correctly points to the DAT file. But, the pointer should be located in the FILE object: OBJECT = FILE FILE_NAME = "ISPM01010100.DAT" RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 45 ^TABLE = "ISPM01010100.DAT" ROW_BYTES = 45 FILE_RECORDS = 15513 OBJECT = TABLE NAME = ISPM INTERCHANGE_FORMAT = BINARY ^STRUCTURE = "ISPM.FMT" START_PRIMARY_KEY = (978317375) STOP_PRIMARY_KEY = (978353349) PRIMARY_KEY = ( "SCET", "DET" ) ROWS = 15513 END_OBJECT = TABLE END_OBJECT = FILE (b) With respect to the .VAR file, Section 3.4 of the SIS indicates that preceeding and following the actual data is a two-byte integer giving the length in bytes. I don't remember the actual VAX/VMS record structure, but what I do recall is that there was a two-byte integer at preceeding the data (only). I don't recall anything following the data. The use of VARIABLE_LENGTH as a record type is very specific to VAX/VMS. (c) The label needs some modification so that it will point to the VAR file and a structure for the individual rows has to be identified. OBJECT = FILE FILE_NAME = "ISPM01010100.VAR" RECORD_TYPE = VARIABLE_LENGTH RECORD_BYTES = 45 ^SPECTRUM = "ISPM01010100.VAR" ROW_BYTES = 45 FILE_RECORDS = 15513 OBJECT = SPECTRUM NAME = ISPM INTERCHANGE_FORMAT = BINARY ^STRUCTURE = "VAR.FMT" ROWS = 15513 ROW_BYTES = COLUMNS = 1 SAMPLING_PARAMETER_NAME = SAMPLING_PARAMETER_INTERVAL = OBJECT = COLUMN NAME = COLUMN_NAME DATA_TYPE = LSB_UNSIGNED_INTEGER (or) START_BYTE = 1 BYTES = DESCRIPTION = "variable column..." END_OBJECT = COLUMN END_OBJECT = SPECTRUM END_OBJECT = FILE When using the FILE object, the FILE_RECORDS keyword is required. Also, I have proposed that the PDS Management Council address this issue of using "proprietory formats" in archive products. (d) Change all values in SPICE_PRODUCT_ID to uppercase. (24) DATA/NAV_DATA/TAR.FMT (a) Change line 53: 2^31 A stellar target from the "stars" file to: 2^31 A stellar target from the 'stars' file (25) SOFTWARE/*.* (a) Files in the SOFTWARE directory and sub-directories do not have PDS labels. All files, except those in the EXTRAS directory, must be labeled. In my opinion, it is not appropriate to indicate (in the ERRATA.TXT) that some are not. This is pretty much a hard requirement. You and Lyle and I need to talk about this. (b) Also, we probably should talk about the use of proprietary software to display the science products (without having PDS software available to do serve as a backup "display" source). (26) DATA/*.* (a) Change: RECORD_TYPE = UNKNOWN to: RECORD_TYPE: UNDEFINED But, the use of UNDEFINED is discouraged (at best). PDS supports most record formats. UNDEFINED is principally used when a single label points to multiple files each having a different record format (eg., binary, stream). (b) SPICE_PRODUCT_ID: Not in data dictionary This keyword is used in most (if not all) of the science products. (27) DATA/NAV_DATA/RIN01010102.LBL RIN01010200.LBL RIN01010410.LBL (a) TARGET_NAME: Value is not a standard value: JR Change: TARGET_NAME = { "JR" } to: TARGET_NAME = "J RINGS" (28) DATA\*.* (a) A label file should not itself have a label file describing it. For example: - Delete: HSK.LBL (and any other label files that describe FMT files) Most (if not all) of the FMT files have been labeled. (29) SUMMARY OF REVIEW (a) The review took longer than I can spend (at least at this time). I have not had the opportunity to give this a "thorough review" and given the number and type of anomalies that are noted above, I would be more comfortable if a subsequent peer-review CD was produced and used for the peer-review. Hopefully, my schedule will allow for a more thorough review at that time. (b) I have not used any of the PDS tools to display the data files and RJ