SDCIDA_0001 =========== - These data are rejected for archiving because of the documentation deficiencies. It will remain in the IN_PREPARATION queue pending new documentation. SBN will continue to attempt to coax this documentation out of the PI, et al. - Is the CODMAC level in the DATA_SET_ID correct? Are these really raw, unedited telemetry data? - Dave R. notes that the CIDA data had nearly all the necessary spacecraft orientation information included in the data file. This was generally agreed to be useful, and should be done in future mission data sets where feasible. - When SPICE is used to generate geometry values in labels, the DATA_SET_ID should be referenced in the data label and the specific kernels used should be identified by filename. In cases where non-archived kernels were used, the kernel files themselves should be included in the data set archive. - It states in the ds cat that these data are level 1 spectra, and so the DSID has a codmac 1 in it. I would think these data are codmac 2, since they aren't raw telemetry. This may be a small distinction, but let's think about it. aareadme.txt - Add entries for recently received CALEXMPL_EVENT.* and CALEXMPL_SPECTRUM.* files to the DOCUMENT/ directory list. errata.txt - Is a catalog file for "INTERSTELLAR PARTICLES" coming? voldesc.cat - The data set and instrument catalog file names are incorrect. catalog/ -------- dataset.cat - Missing ABSTRACT_DESC, ARCHIVE_STATUS and CITATION_DESC - There is no attribution for the DESCRIPTION text. - DATA_SET_TARGET object must be repeated for each unique target. - Refers to a document containing thumbnail images which does not exist. It should be created and supplied. - The DATA_SET_DESC needs to be more explicit about the amount and type of science and non-science results included in the data set, and how to quickly distinguish them (like, for example, consulting the index.tab file). - The "Data Calibration" subheading in the data set description refers to a in-flight calibration example which doesn't exist. At the very least there should be a reference to a paper that shows laboratory calibration, when one is available. The processed described as "calibration" here is actually data reduction. That terminology should be changed. - There is no explanation of the target signal meaning, significance, etc. - Be sure that the DATA_SET_NAME is in all caps. - Should mention index table for recognizing real particles. - Need some references on how to calibrate the abundances and results from actual calibration experiments in the lab. - The "target signal" needs to be explained. - No explanation of what the four channels are (or how they differ - how tell positive from negative - should be redundant by description "two redundant high and two redundant low"). mission.cat - MISSION_TARGET must be repeated for each unique TARGET_NAME. instrument.cat - The instrument description, especially with respect to the channels, is inadequate. For example, it is not at all clear that the word "redundant" is being used correctly. Also there is no explanation for the pattern of zero-valued columns that appears in encounter data but not cruise data. ref.cat - Check that all references in ref.cat file are present as references in the catalog files. data/ ----- edfascii/*.lbl - SPACECRAFT_CLOCK_STOP_COUNT can't be "N/A" if SPACECRAFT_CLOCK_START_COUNT is valid. It may be the same as the START_COUNT if the observation was instantaneous, or "UNK". - Similarly, STOP_TIME cannot be "N/A" if START_TIME is valid. - The TARGET_NAME "NON SCIENCE" is not included in the mission object, nor is there a target catalog object for it. - Data are tables with attatched labels - detatched are suggested, but not required. cida_geometry.fmt - Is there a reason why almost every entry has a format of f15.3 or f15.6? Most of the entries are unit vectors, angles and velocities, and this is overkill for those. document/ --------- - The revised calexmpl.pdf document contains an example of the spectrum of a dust impact event and an example of a calibrated spectrum. However, the examples are from laboratory tests and not from the Wild 2 encounter. Should examples using Wild 2 data be supplied? - calexmp_old.pdf is not labeled. This is the old version of the calibration documet. Remove it. - In the "onlabels.txt" file, the description of the spacecraft clock count format is slightly different from that actually in these data files. - The calexmpl.old file should be deleted (it's not even labeled). - The calexmpl.pdf file contains numerous ambiguities, incomplete descriptions, etc. A better description of the channels and what is needed for each is essential. Proof-editing to make sure that values in tables and equations are properly correlated, and references to the appropriate published papers would also help. - Need examples of positive and negative and need examples that show both H and Ag. - Documentation is needed for all known and suspected malfunctions, glitches, resets, idiosynchracies, etc. of the instrument. If there were no such failures, the missing data (i.e., the zero-valued columns) must be explained. - An example of a reduction of real data (in addition to the laboratory example) is needed. - Split the known non-science data into a separate directory from the known and possible science data. - One has to guess what most things mean in the cal document. Please elaborate. Index ----- - There is no DSID in the index.tab file. - Is there a reason why almost every entry has a format of f15.3 or f15.6? Most of the entries are unit vectors, angles and velocities, and this is overkill for those. Also see, the note for cida_geometry.fmt.