SDCIDA_0001 =========== *** These data are deferred. The documentation was found to be inadequate. *** If further documentation is supplied, the data will be reviewed again. *** If no additional documetation is forthcoming, the data are rejected. o Apply uniform label conventions across all Stardust data file wherever possible. o Update catalog files as appropriate. o Include a brief tutorial on measurement technique and scientific application, if possible. o Include more and better calibration examples and explanations. Without these, data are of questionable value and may not be archivable. o "Example" is not an appropriate name for the contents of that directory (under the 'document' directory). Rename it to more accurately indicate the subdirectory contents. o Provide detailed documentation for the processing performed by the octave script, including the processing algorithm. o If possible, get a better explanation of the current example. o Convert the calibration PDF file to flat ASCII if possible. o In calexmpl.pdf: - Edit calexmpl.pdf to remove typos. - Expand on the procedure provided so that, for example, each "make sure that" direction is followed by instructions for how to "make sure". - Mathematical steps must be explicitly stated, preferably in the form of an equation. - Provide detailed explanation for finding hydrogen and silver peaks in the spectrum. - Section 2, step 6 is a comment, not a processing step. - Section 3.1 is missing the error estimates they apparently intended to include (indicated by an author's note to self, "Error estimates!!!!"). - Section 3.2 refers to a "standard technique" for instrument calibration, but none is given. Details of at least one specific technique must be provided. - "Table 4" values referenced in Section 3.3 are not given at all. - The example calculation of Section 3.4 should also be defined generically in the detailed steps given in Section 2. - The pre- and post-calibrated data graphic is of poor quality. An improved graphic with better explanation should be provided. - The specific pre- and post-calibration files should be named, to allow users to check their own calibration procedures. o Include an overview of the use and scientific interpretation of the data in the "Data Set Overview" section of the data set catalog file. Examples of this interpretation should be included in the calibration procedure examples. o Detach labels from data files. o aareadme.lbl - This file has variable-length records. - This contains a DOCUMENT object. This is inappropriate - use a TEXT object. o errata.txt - There seem to be no errata, so there shouldn't be an errata file. o voldesc.cat - This file has variable-length records. - There can be only one DATA_PRODUCER in a VOLUME object. Crediting a software vendor as a data producer is inappropriate. - Who decided on the VOLUME_SERIES_NAME? Strikes me as way too generic. - line 26: "MAX-PLANCK-INSITUT" is not the way the name appears in the data dictionary. (Note that there is also a typo in the dictionary in this name that should be corrected. - line 27: Is that really the correct spelling for the FACILITY_NAME? Two Es in a row looks odd to me. - line 66: Syntax error (comma at end). - Is this the right TARGET? Isn't this an instellar dust analyzer, which would make the target interstellar dust? o In the catalog directory: - All these files have variable-length records. o cidads.cat - SPACECRAFT_NAME is a deprecated keyword. Use INSTRUMENT_HOST_NAME instead. - Missing ARCHIVE_STATUS keyword. - Is this a sufficiently specific DATA_SET_NAME? Will there be no other CIDA data from the Stardust mission? - "INTERSTELLAR PARTICLES" is not a known TARGET_NAME and no TARGET catalog file is supplied for it. Neither is it listed in the voldesc.cat file in the root directory. - This file contains two DATA_SET_TARGET objects - only one is allowed. - line 13: "spectrums" should be "spectra". - This file claims that the OBJECT_TYPE is "SPECTRUM", but the data files here are all TABLEs. o cidainst.cat - Is CIDA really a "COSMIC DUST ANALYSER" (as opposed to a "DUST IMPACT DETECTOR" or "DUST ANALYZER" or "MASS SPECTROMETER")? - The INSTRUMENT_NAME given here does not agree with the instrument name given in the aareadme.txt file in the root directory, or with the INSTRUMENT_TYPE. - line 14: REFERENCE_KEY_ID values are not suitable substitutes for standard short forms of citation. Include the correct citations. - Standard headings are not used in the INSTRUMENT_DESC text. - Who is the author of this text? Who owns the copyright? Attribute it or delete it. - line 50: There should be no apostrophe in "flyby's". - I made no systematic attempt to proof text. It needs to be reviewed by an editor prior to archiving. o insthost.cat - The LABEL_REVISION_NOTE does not indicate what was done on the successive revisions. - There should be a REFERENCE object and citation for the Stardust Mission Plan quoted in this file. It should be listed in the INSTRUMENT_HOST_ REFERENCE_INFO object. - I made no attempt to proof text or compare to other versions on other disks. It must be reviewed by an editor. o mission.cat - LABEL_REVISION_NOTE does not indicate what was done at each revision. - MISSION_STOP_DATE should not be unknown - there is an ending date mentioned in the text. - There may only be a single MISSION_TARGET object (it may be multi-valued). - Who wrote this text? Who owns the copyright? - There should be a REFERENCE object and citation for the Stardust Mission Plan quoted in this file. It should be listed in the MISSION_REFERENCE_ INFORMATION object. - The "INTERSTELLAR PARTICLES" target mentioned in the DATA_SET catalog object is not mentioned here. - I made no attempt to proof text or compare to other versions on other disks. It must be reviewed by an editor. o person.cat - line 13: INSTUTITION_NAME should match standard value (except for typo) - line 14, 69: "FINISH" should probably be "FINNISH" - All phone numbers must be in quotes. o ref.cat - Reference text is missing information (contains strings of "??"). o cidasis.txt - This is not valid syntax for an attached DOCUMENT object label. The label should be in a separate file or an appropriate object pointer provided. - I did not attempt to proof. It must be reviewed by an editor. o lblinfo.txt - line 17: This statement is incorrect. In fact, all of the documents in this directory have attached labels. - How does this file compare with other files on the same name on other Stardust volumes? - I did not attempt to proof. It must be reviewed by an editor. o onlabels.txt - How does this file compare with other files on the same name on other Stardust volumes? - I did not attempt to proof. It must be reviewed by an editor. o calexmpl.pdf - Who owns the copyright on this? Attribute it or delete it. - Any chance of an ASCII version of the text part of this? o index.tab - The indentation is odd and variable through this file. Fix it. - Columns 6 & 7 (SPACECRAFT_CLOCK_START_COUNT and SPACECRAFT_CLOCK_STOP_COUNT) have a DATA_TYPE of "TIME", but are not in ISO 8601 format. Spacecraft times should have a DATA_TYPE of CHARACTER, ASCII_INTEGER or ASCII_REAL, as appropriate. (In the data file they are treated as character strings.) - The required PRODUCT_ID column is missing. - SPACECRAFT_NAME is a deprecated keyword. Use INSTRUMENT_HOST_NAME. o datainfo.txt, et al. - This file doesn't seem to add anything, and the grammar in the one sentence is less than optimal. Delete it. - This is true for all the *info.txt files included in this hierarchy. This information is better presented in the aadreadme.txt file in the root directory. o DATA/EDFASCII/CRUISE/NEGATIVE/ & /POSITIVE/ *.tab files: - PRODUCT_TYPE is incorrect. It should be {"EDF","HK"} (based on current standard values). It has nothing to do with data objects. - Proposed INSTRUMENT_MODE_ID is overly long and is not an ID - it's a name. o cida_header.fmt - There are undefined acronyms in here (ADC, FDAQ) - UNIT values are in lower case and abbreviated. o The DATA/EDFASCII/ENCOUNTR/ directories are empty. Remove them and all references to them, or explain why they are present and empty. o DATA/HKVALUES/CRUISE/*.tab files: - PRODUCT_TYPE is incorrect. o DATA/HKVALUES/ENCOUNTR/ directory is empty. Remove it and all references to it, or explain why it is present and empty.