DSPE_0001 ========= o Change volume ID to "DS1PE_0001" everywhere. o Change TARGET_NAME to "19P/BORRELLY 1 (1904 Y2)" everywhere. o Compare contents of ASCII and binary data file to ensure the conversion did not alter the data values. A known problem with time-of-flight values will be fixed. o Check and verify ion efficiencies. o Amend documentation to indicate the state of knowledge of election efficiencies. o Add to the M/Q bin description a section specifying which species fall within each bin. o Add a discussion of the spacecraft potential problem, as far as it is understood. o Move information in the calinfo.txt file into a more stable, permanent location. Some of the description currently contained in the DATA_SET catalog file will be moved to the same document. o Fix the human-readable times in the data files (known software problem in the conversion). o Check the information in the (new) calibration document, including the errors identified by Vinas in his presentation slide "Issues of PEPE's Information Files": 1. Instrumental and calibration parameters should be collected into a single place for reference. 2. Correct the description of the determination of phase space density to indicate that the energy factor in the equation is energy per charge. 3. Provide a description of the physically meaningful quantities that can be determined, with formulae and algorithms. 4. The labels on Table 2 of the calibration file are incorrect - they are not detector efficiencies, they are solid angles. 5. Provide an example of composition determination. o In DATAINFO.TXT the table describing the ion singles table gives the wrong number of bytes per row. o The borrellyds.cat file description of coordinate systems needs a minus sign in front of the unit vectors. o voldesc.cat - In other cases, the PPI FACILITY_NAME has been "GEOPHYSICS AND PLANETARY PHYSICS". Please change. - The DATA_SUPPLIER object (NSSDC) is largely unpopulated. I need to know why they are considered suppliers, and if they are, the required fields should be populated with appropriate values. - The value of MEDIUM_TYPE should probably be "CD-ROM", if that's the archive medium of choice. - VOLUME_FORMAT = "ISO-9660-2" should instead be "ISO-9660_LEVEL2" o The following labels are not referenced in the index.tab file: DATA/HSK01262_A.LBL DATA/HSK01262_B.LBL DATA/HSK01263_A.LBL DATA/HSK01263_B.LBL DATA/HSK01264_A.LBL DATA/HSK01264_B.LBL DATA/HSK01265_A.LBL DATA/HSK01265_B.LBL DATA/HSK01266_A.LBL DATA/HSK01266_B.LBL o index.tab: - The 3 time fields should be unquoted. - VOLUME_ID must be included either in the label, or as a column in the table. o The object delimeter END_OBEJCT is misspelled at the end of the index.lbl file. o pepe_borrelly_ds.cat: - The DSID doesn't match the one used in the label files. Pick one. - TARGET_NAME = BORRELLY <-- should be "19P/BORRELLY 1 (1904 Y2)" o mission.cat: - embedded TAB on line 244 o Need cat files for targets: "SOLAR WIND" & "19P/BORRELLY 1 (1904 Y2)" o data_product_def_030113.lbl: - Use DSID consistent with rest of volume. - DOCUMENT_FORMAT = MSWORD <-- replace with "MICROSOFT WORD" - DOCUMENT_FORMAT = PDF <-- replace with "ADOBE PDF" - ENCODING_TYPE = "PDF-ADOBE-1.2" is not currently a standard value, but should be allowable, as it is in the format of other PDF versions - PRODUCT_TYPE = "DOCUMENT" only appears in data labels. This is a document label. o In the geometry directory, the following DSIDs appear in labels: - "DS1-C-SPICE-6-PCK-V1.0" <-- provide cat file in catalog dir - "N/A" <-- really? - "DS1-C-SPICE-6-SCLKV1.0" <-- missing hyphen, also provide cat file in catalog dir - "DS1-C-SPICE-6-SPK-V1.0" <-- provide cat file in catalog dir o In geomtry/ds1_borrelly_v01.lbl:10: - ORIGINAL_FILE_NAME = "MK97112A.TSC" Can you use SOURCE_FILE_NAME instead? Or perhaps SOURCE_PRODUCT_ID? O_F_N is not a keyword. - Refer to PDS Standards Appendix A.25: The first instance of KERNEL_TYPE should instead be KERNEL_TYPE_ID. The second instance of KERNEL_TYPE should have the value "TARGET_CONSTANTS". o In geomtry/ds1_sclkscet_00071.lbl:10: - ORIGINAL_FILE_NAME = "PK96030A.TPC" Can you use SOURCE_FILE_NAME instead? Or perhaps SOURCE_PRODUCT_ID? O_F_N is not a keyword. o In geomtry/sp19p_aut118.lbl: - The target list here should be discussed. o In the data directory, many data labels have PRODUCT_TYPE = "DATA". The PRODUCT_TYPE keyword currently has a very short list of allowable standard values: "EDR", "REDR", "REFDR", "UDR". I would suppose this value should be "EDR". o hsk0126*.lbl files: - Replace the standard value DATA_TYPE = IEEE_FLOAT with IEEE_REAL o aareadme.txt This file needs to be carefully proofed. Here's what I noted in a light reading... - line 76: Commas are not white space. - line 77: Are numeric columns really right-justified, or are they decimal-aligned? Correct it if so. - line 132: Is this statement about PPI maintaining an on-line errata list for this data set true? Delete if not. - line 141: This statement indicates there can be more than one volume called DSPE_1001. This is not, in fact, possible. - line 154: I'm pretty sure you want support and feedback FROM the users, not "of" the users, or perhaps you're missing a definite article before "support and feedback". - line 183: Caveats do not exist "in the data". Caveats are 'with respect to' the data. - line 222: "Aware of about" is not proper grammar. - line 223: None of these commas is correct. - line 249: The qualifier "in particular" can only be used when a general class is also mentioned. Either another qualifier is missing (i.e., "The PDS in general and PPI in particular") or the existing qualifier is not being used properly and should be removed. - This text must be reviewed by an editor prior to archiving. o cal_info.txt - This is not the correct name for the required info.txt file (calinfo.txt). - If there are no actual calibration data, this directory should be omitted. - This information belongs either in the data set catalog file, the instrument catalog file, or in a properly labelled document in the document directory which is then referenced by the data set and instrument catalog files. In an info.txt file with a minimal label it is untracable in the PDS archives. - This is substantial text. There should be an attribution to the author. o catinfo.txt - Not all of the files listed in this file are included in the catalog directory. Specifically, the INSTHOST.CAT and MISSION.CAT files are missing. - This directory does not contain "catalog templates" - it contains catalog FILES. Templates are blank. o pepe_borrelly_ds.cat - DATA_SET_TARGET and DATA_SET_REFERENCE_INFORMATION may not be used more than once. They should be multiple-valued. - SYNTAX ERROR: line 85 - double quotes within double quotes. - This TARGET_NAME does not follow small body standards. - The description contains substantial text that is not attributed. The author must be identified. - This text needs to be carefully proofed. On light reading I found: line 47ff: PDS REFERENCE_KEY_ID values are not satisfactory substitutes for actual citations. line 68: is "time" the right word here? If so, is another word missing? line 71: This comma and the first comma in the following line are not grammatical and should be removed. line 82ff: These are not sentences and should not end in periods. line 350ff: Not sentences, should not end in periods. line 407-8: Are these acronyms defined prior to their use here? line 426-7: Two journals are not "several". line 431: This comma is inappropriate. line 435: Why is this "Table M" when previous tables have been numbered sequentially? line 476ff: This sentence doesn't make sense to me. Is there a subject/verb number agreement problem? - None of the REFERENCE_KEY_ID values listed here are in the pepe_ref.cat file. o pepe_inst.cat - Missing PDS_VERSION_ID and LABEL_REVISION_NOTE - SYNTAX ERRORS: line 135 - double quotes in double quotes line 309 - double quotes in double quotes line 317 - double quotes in double quotes line 331 - double quotes in double quotes line 813 - ampersand in unquoted string line 823 - ampersand in unquoted string missing END statement - INSTRUMENT_REFERENCE_INFO may not be repeated - it must be multi-valued. - "YOUNGETINPRESS" is not a valid REFERENCE_KEY_ID. - INSTRUMENT_DESC must begin with "Instrument Overview". - The description text needs to be carefully proofed and updated. For example: Future perfect tense is used about events which clearly must have passed. The name of comet Wilson-Harrington is misspelled. The plural of "coma" is "comae". There is a reference to "Figure 1," which does not seem to exist. There are alignment problems in Table 2. - There is substantial text in the description field. Further, it reads as though it was prepared for publication in a print journal. The author should be cited, at the very least. Who owns the copyright on this text? o pepe_person.cat - RECORD_TYPE and RECORD_BYTES do not belong in catalog files. - SYNTAX ERRORS: Missing END_OBJECT for second PERSONNEL object. Missing PERSONNEL_ELECTRONIC_MAIL for second PERSONNEL object. Missing INSTITUTION_NAME for second PERSONNEL object. o pepe_ref.cat - This file is clearly in the midst of being edited. No attempt to validate or verify. This file must be complete and accurate prior to archiving. o elc*_a.lbl, elc*_b.lbl - PRODUCT_TYPE = DATA is not valid. The value should at least follow the pattern of current PRODUCT_TYPE values. Note that new standard values for this keyword require full PDS review and approval. - START/STOP_TIME = NULL is probably not right. "NULL" indicates a value will be supplied. If that were true, why is it not here now? - PRODUCT_VERSION_ID is an AMMOS keyword, and the value given here does not follow the formation given in the definition. Why is it here? - I find it difficult to believe that every product in this directory was created at either exactly noon or exactly 6pm. I suspect that PRODUCT_CREATION_TIME has not been trimmed to an appropriate set of significant figures. - Why is incremental day number used in START/STOP_TIME while the description gives it in YYYY-MM-DD format? If readability is the issue, START/STOP_TIME should be more readable. - The description of column 2 says the time is given "in one of the ISO standard time formats," but then lists only one format. If there is only one possible format, this should be re-worded to eliminate the implication that there is more than one format in the file. - Columns 7-10: The azimuth number - angle range correspondence should be stated in each description instead of listing all in the first description and none in the others. - Column descriptions in ASCII TABLES *MUST* have FORMAT keywords. o ion*_a.lbl, ion*_b.lbl - All of the above - The ASCII_TABLE pointers all have values of "FILE_NAME.DAT" o log*_a.lbl, log*_b.lbl - All of the above o mq*_a.lbl, mq*_b.lbl - All of the above o tof*_a.lbl, tof*_b.lbl o data_product_def_030113.lbl - Does this file name really need to be this long? - SYNTAX ERRORS: line 18 - Missing end quote - PRODUCT_TYPE - not an appropriate value given current standard values - "MSWORD" is not a valid DOCUMENT_FORMAT. Neither is "PDF" or "PDF-ADOBE-1.2". The appropriate values are "MICROSOFT WORD" and "ADOBE PDF".