List of liens from Jan 13-14 2014 PDS review. List of DATA_SET_ID's of New Horizon Data Sets Reviewed: NH-J-SDC-2-JUPITER-V3.0 NH-J-SDC-3-JUPITER-V3.0 NH-X-ALICE-2-PLUTOCRUISE-V1.0 NH-X-ALICE-3-PLUTOCRUISE-V1.0 NH-X-LEISA-2-PLUTOCRUISE-V1.0 NH-X-LEISA-3-PLUTOCRUISE-V1.0 NH-X-LORRI-2-PLUTOCRUISE-V1.0 NH-X-LORRI-3-PLUTOCRUISE-V1.0 NH-X-MVIC-2-PLUTOCRUISE-V1.0 NH-X-MVIC-3-PLUTOCRUISE-V1.0 NH-X-PEPSSI-2-PLUTOCRUISE-V1.0 NH-X-PEPSSI-3-PLUTOCRUISE-V1.0 NH-X-SDC-2-LAUNCH-V3.0 NH-X-SDC-2-PLUTOCRUISE-V1.0 NH-X-SDC-3-LAUNCH-V3.0 NH-X-SDC-3-PLUTOCRUISE-V1.0 NH-X-SWAP-2-PLUTOCRUISE-V1.0 NH-X-SWAP-3-PLUTOCRUISE-V1.0" ======================================================================= List of General Liens for all New Horizon data sets --------------------------------------------------- Note: Some typos do not list a line number. This is because the line number varies between each file in the various data sets. But if you do a text search (or grep) you can easily find it. File: 'aareadme.txt' --> typo?: first sentence of "Processing level:" section is not clear. --> typo: "refered" --> "referred" --> typo: "store" ---> "stored" --> "Volume Format:" section information seems to be outdated. VAX/VMS is sill around? --> typo: line 64: "NH_TRAJECTORY.*: not found in the CATALOG directory, but "NH_MISSION_TRAJECTORY.*" is found in the DOCUMENT directory. Please correct both. --> typo: line 70: "PAYLOAD.*" should be "PAYLOAD_SSR.*". --> Please add "[instrument]_CAL.*" to the list in the DOCUMENT directory section of the required reading. --> Add seq_[instrument]_[phase].* to the required reading list and describe the contents to the user --> In the aadreadme.txt, please add a forward reference at the top of “Required Reading” section to detailed reading (much) farther down in the same file to direct users to information on how the files are named in the archive. --> Required Reading, Details, SOC Instrument Control Document, 2nd paragraph, 2nd line, the file “SOC_INST_ICD.DOC” is not in the DOCUMENT directory as claimed. This information can be found in the file “SOC_INST_ICD.PDF”. --> Volume Contents, under DOCUMENT list, the files QUAT_ZXYZ_J2K_TO_INSTR.LBL and QUAT_ZXYZ_J2K_TO_INSTR.ASC do not exist. (FYI‐The files QUAT_AXYZ_INSTR_TO_J2K.LBL and QUAT_AXYZ_INSTR_TO_J2K.ASC exist in that directory. The project should consider changing the extension of this file from “ASC” to “TXT”.) --> Directory trees in aareadme.txt can be deleted, if desired. They are not required. --> Description of NH_TRAJECTORY.* says "NH Spacecraft & Jupiter trajectories" even though this is not the case for pluto cruise. --> Change "QUAT_ZXYZ_J2K_TO_INSTR*" to "QUAT_AXYZ_J2K_TO_INSTR*" to match what is found in the volume. File: 'catalog/dataset.cat' --> CITATION_DESC should specify the data set level in title. --> typo: " is is " -> " is " --> typo: "udpated" -> "updated" --> typo: "Sytem" -> "System" File: 'catalog/nh.cat' --> typo: line 86: "spectra measurements" -> "spectral measurements" --> The data found in the data sets in this review for the "Pluto Cruise" phase seem to only be a subset of the date range of 2007-06-27 to 2014-12-31 mentioned in this file. Please explain why this is the case. File: 'catalog/personnel.cat' --> Please remove these files. File: 'catalog/ref.cat' --> line 418: The REFERENCE_KEY_ID "OTTMANETAL2006" has no publication year at the end of the REFERENCE_DESC. --> May need to add missing reference "SLATERETAL2007" found in the ALICE catalog file if the ID is correct. --> The REFERENCE_KEY_ID "ASMAR&HERRERA1993" is ITAR-controlled. This should not be referenced in the PDS archive. --> The Lunine, et al. (1995) (LUNINEETAL1995) reference is unpublished and not available. Either remove it, if it provides no real value, or find it and publish it via the PDS archive with appropriate acknowledgement. --> May need to add HORANYIETAL2008 (being a mirror of HORANYIETAL2007) reference if SDC lien is resolved to included it. Files: 'data/*/*.lbl' --> The SEQUENCE_ID exceeds the max number of characters of 30 in many instances. --> --> The SEQUENCE_ID value in PDS3 is too short for NH purposes. Possible solutions were discussed briefly, and the most congenial seems to be creating a local New Horizons data dictionary with, for example, a NH:SEQUENCE_ID keyword with a longer length. N.B.: Please consult with SBN and EN before deciding on a namespace abbreviation – “NH” is too short. --> suggestion: Change SOFTWARE_NAME = "TOPDS 1.0" to SOFTWARE_NAME = "TOPDS" and SOFTWARE_VERSION = "1.0". File: 'document/docinfo.txt' --> typo: line 46: "the the" -> "the" --> typo: line 77: "with and" -> "with an" --> Suggestion: You might improve the description of NH_[instrument]_V###._TI.TXT if you added a statement that says that this file is subject to update and that the most up-to-date copy will be found at the NAIF website. --> SBN has agreed to accept PDF/A rather than the PDS3 required ASCII version of critical documents. Because this is a variation on the normal PDS3 requirements, we should mention this anomaly in the docinfo.txt file just in case PDS3 users have questions. File: 'document/samples/*_samples.lbl' --> typo: "morw" -> "more" Files: 'document/samples/*_sm.lbl' --> The SEQUENCE_ID exceeds the max number of characters of 30 in many instances. --> --> The SEQUENCE_ID value in PDS3 is too short for NH purposes. Possible solutions were discussed briefly, and the most congenial seems to be creating a local New Horizons data dictionary with, for example, a NH:SEQUENCE_ID keyword with a longer length. N.B.: Please consult with SBN and EN before deciding on a namespace abbreviation – “NH” is too short. File: 'document/samples/sampinfo.txt' --> Add a note to the sampinfo.txt fie indicating that the FITS files included in the sample/ directory are there to demonstrate format decoding only and not intended for data analysis. File: 'document/soc_inst_icd.lbl' --> line 22: The PUBLICATION_DATE value '2013-12_05' needs to be changed to '2013-12-05'. File: 'document/soc_inst_icd.pdf --> General Comment: Through out this document, multiple figure numbers are repeated presenting different pictures. The user is confused which figure is cited and discussed in the text. In addition to repeated figure numbers, figures are placed in a non-sequential order adding to the confusion. The figure numbering method is inconsistent between figures and figures exist without figure numbers or captions. A complete revision of the text and figures needs to occur so that the citations point to the proper figures and there is only one unique figure number per picture. --> typo: Section 7.2.1.1 should read "[Following the primary data unit is the] first data extension in the FITS file, [which] contains" --> typo: Lossless is a word, loss-less is not (table 7-2) and text nearby --> NEED AN ACRONYM LIST for: --> --> CCDSD (is this related to C&DH?) --> --> PERSI --> --> ApID is APID in most places --> --> IEM --> --> CODMAC --> Table 7-3 is confusing. Maybe not worth my trying to figure out, but if written consistently with 7-2 and IEM defined, might be easier. In particular the digit of the ApID is confusing when 11 and 14 are included. --> Table 7-3 is confusing because ApIDs are used that are not defined (11 and 14). --> typo: Not using the ground flatfield correction (was there one?) --> Section 8.1 Overview: "The number of pixel-limited spectral channels is the number of rows of the detector, excluding a number of rows (4) obscured by opaque adhesive at the bond joint between the two filter segments." --> --> It should be number of columns, not rows. --> Figure 8-1: Layout for LVF Filter Assembly. --> --> Why the wavelength map extracted from the data is rotated with respect to the figure in the manual? --> --> The graphic showing the wavelength map is in a different orientation from that found in the actual data files, which is deceptive. Ideally, this should reflect the formatting in the file. --> Suggestion: There was a request to provide at least an algorithm for an “easy” co-registration process (see slide 19), but there probably isn’t an easy solution for this instrument. Higher-level, co-registered products would help to mitigate this, but cannot be required as a lien on this data set. SBN will be watching and advocating for these products. --> --> (slide 19): Page 23, 'Compute pointing data' section. I computed the J2000 pointing vector for each pixel and each frame. However, it was not trivial. Is there another way to co-register data images at different wavelengths? --> Please clarify the appropriate use of the “default” and “initial” calibration files. --> PEPSSI Figure 7, cited on page 66, should be the Figure 7 shown on page 93 and NOT the Figure 7 shown on page 98. --> PEPSSI Figure 8, cited on page 66, should be the Figure 8 shown on page 94 and NOT the Figure 8 shown on pages 99 and 100. --> PEPSSI Figure 7, cited on page 68 is probably the Figure 7 shown on page 98 and NOT the Figure 7 shown on page 93. --> Section 11.2 (pg. 68), par 1, line 3: Capitalize "low-energy" to "Low-Energy" --> Section 11.2 (pg. 68), par 1, line 7,9, and par 2: Capitalize "figure" as "Figure" --> PEPSSI page 69, what is section ???1.2.1.7 here: "(see discussion in section ???1.2.1.7 below)." --> PEPSSI Section 11.3.3 Header with Keywords is blank. Was there supposed to be text here? --> PEPSSI Section 11.4.1.1 IDL L1 to Pre-L2 step, paragraph 1 on page 70: reference to section 11.3.1.2 below does not exist. --> PEPSSI Figure 6, cited on page 79 is out of order. --> PEPSSI Figure 6, cited on page 82 is not the correct figure. --> PEPSSI Figure 7, cited on page 86 is probably the Figure 7 shown on page 98 and NOT the Figure 7 shown on page 93. --> There are no files identified as instrument configuration files and no “instrument_config” directory tree in the PDS data set as stated: "The binary files can be found in the instrument_config/ directory tree of the PEPSSI PDS data set." --> PEPSSI on page 86, why is there a section 11.4.3.5.1 but no section 11.4.3.5.2? --> PEPSSI section 11.4.4 on page 88, expected to find the “PEPSSI_BTI.TXT” file, but no file was found. --> Various documents describing the PEPSSI energy ranges (inst.cat, pepssi_ssr.pdf, soc_inst_icd.pdf) show different values for the same channels: SSR - Table 1, page 13 and pepssi.cat (table at top) --> Page 78 11.4.3 Para 1: "Each file will contain exactly one observing day worth of data (i.e. one UTC day from hour 0 – 23:59:59.999...)." What happens to data acquired during leap seconds? --> --> There is actually a question about what the pipeline does for a leap second. This must be investigated, in case it impacts the archive, and the result documented accordingly. --> Expected to find a discussion on the meaning and use of checksum values in Section 6 since it seems to be universal to the project. Should it not be included within the ICD? --> Section 13 --> --> Two different name (VSDC &SDV) is confusing to a non insider. --> --> Need for an acronym list. --> --> The definition of “Threshold “ in 13.2.1. section needs some expansion. Why is that hits below threshold should be recorded “due to the way software works”? --> Section 13.3.2: SDC Calibration - Mass: The description here is out-of-date and has been superseded by research reported in James et al., 2010. This section should be updated to reflect the different calibration used for the SDC detectors. --> Section 14.5.7 SPICE Orbit and Attitude Calculations focuses entirely on the Jupiter flyby. Can this section be expanded or generalized to discuss solar wind and Pluto flyby calculations as well. --> --> There may be appropriate solar wind and Pluto coordinates available in the near future. If possible, add tabulated coordinates to this data set. If not, add a forward reference (that is, specifically note that they are not included presently, and there is an intention to include them in a future data set or revision of this data set). --> typo: Section 14.5.9 (pg 138), par 1, line 3: "described in section the" should read "described in a section of the" --> typo: Section 14.6 (pg 140), par 1, line 10: "which consists two coarse" should read "which consists of two coarse" --> Consider adding text to section 14.10.1 to describe Figure 14-26 which is currently the only content in this section. --> Consider changing the caption of Figure 14-26 from "SWAP Level 2 Pipeline Diagram" to "SWAP Level 3 Pipeline Diagram" --> page 143, Para 1, line 6 "in Error: Reference source not found" is where a link should be. --> Clean up the usage of "APIDs" and "ApIDs". File: '*plutocruise*/index/index.lbl' --> The START_TIME and STOP_TIME values are: 0000-00-00T00:00:00.000. This time is outside of the range of time for these data sets. File: '*plutocruise*/index/index.tab' --> All START_TIMEs and STOP_TIMEs are 0000-00... though the labels have values for those keywords. --> For field 12, TARGET_NAME, is 2 characters short whenever the TARGET_NAME = CALIBRATION. File: 'index/slimindx.lbl' --> All three should be INDEX_TABLE or TABLE: ======================================= ^INDEX_TABLE = "SLIMINDX.TAB" OBJECT = TABLE END_OBJECT = TABLE ======================================= File: '*plutocruise*/index/slimindx.lbl' --> The START_TIME and STOP_TIME values are: 0000-00-00T00:00:00.000. This time is outside of the range of time for these data sets. File: 'voldesc.cat' --> Remove all target catalog file references not included in the data set. --> line 59: There is miscellaneous text that needs to be removed: "skep_COMMENT INSERT_TARGTOBJS_VOLDESC contains a list of target catalog" --> Make sure ^PERSONNEL_CATALOG references are removed if the catalog file was removed. --> typo: Each line in the ADDRESS_TEXT for DATA_PRODUCER ends in text '\n'. Please remove this misc text. When there are special modes (like subframes) in operation, this should be noted in the PDS label somehow (keyword, note, etc.). In text, please make uniform the use of ApID vs APID. That is, the choice of capitalization needs to be uniform everywhere, so that users know these are the same thing. The reviewers very strongly requested that information to be provided to give users some indication of where the actual target is in the image (in pixel location, e.g.). This could be supplied as a separate table, in the labels, in an index file, or some other reasonable format. The actual solution will be worked offline with reviewers. Users will need some guidance on how to use these data, and this documentation should be referenced in the dataset.cat. We realize this my take some time to compose, but if it is at all possible it should be included. Looking to the future, is it possible to provide tutorials? If not immediately, then perhaps as part of future activities? At a minimum, is it possible to expand on the phrase “to increase sensitivity”, which appears in the general description of the dataset.cat? ======================================================================= List of liens for ALICE data sets --------------------------------------------------- Result: Certified. Has minor liens. DATA_SET_ID: NH-X-ALICE-2-PLUTOCRUISE-V1.0 NH-X-ALICE-3-PLUTOCRUISE-V1.0 Note that the reviewers found that the example presented in the SSR paper was extremely useful in understanding the basic characteristics of the data products, and much appreciated. File: 'catalog/alice.cat' --> Need to add a INSTRUMENT_REFERENCE_OBJECT for 'SLATERETAL2007' or rename the ID to 2001 or 2005, which ever is correct. If 2007 is correct, the reference needs to be added to the reference catalog file for all NH data sets. File: 'document/samples/ali_0002852226_4b0_s_1_sm.lbl' --> line 61: The value "-131" is below the acceptable minimum of "0" for EXPOSURE_DURATION with the type "REAL". Files: 'document/*.lbl' --> SPACECRAFT_NAME = "NEW HORIZONS": most labels skip this for INSTRUMENT_HOST_ID Files: 'document/seq_alice*' --> If possible, add additional information to the SEQ file, akin to that for other data sets. This could be in the label of the SEQ file, if that seems appropriate, and might be limited to getting a redefinition of the comments that are completely opaque because of the nature of the data-taking at this phase of the mission. [Note that for Pluto encounter phases more information will be available from the mission and should be included as additional documentation (a la an “observing log”).] Directory: 'data/' --> The following level 2 files have no corresponding file in level 3 data set: --> --> data/20090726_011095/ali_0110954326_0x4b1_eng_1.* --> --> data/20090726_011095/ali_0110954457_0x4b1_eng_1.* --> --> data/20090726_011095/ali_0110954588_0x4b1_eng_1.* --> --> data/20090726_011095/ali_0110954664_0x4b1_eng_1.* --> --> data/20100619_013922/ali_0139228861_0x4b1_eng_1.* File: nh-x-alice-3-plutocruise-v1.0/data/20090726_011095/ali_0110954195_0x4b1_sci_1.lbl --> All other files have 12 or 11 pointers, but this one only has 6. Is this correct? It would be helpful to have additional cookbook-type information about the details of dealing with scan data (as also requested for MVIC). Confirm that the list of files in the calib/ directory of the calibrated data set is complete (the raw data set has additional files). Also check that the number of FITS extensions listed in the label corresponds to what is actually in each of the data files. ======================================================================= List of liens for LEISA data sets --------------------------------------------------- Result: Not Certified. Delta review required. DATA_SET_ID: NH-X-LEISA-2-PLUTOCRUISE-V1.0 NH-X-LEISA-3-PLUTOCRUISE-V1.0 File: 'catalog/dataset.cat' --> Check that the content in the DATA folder is correctly described by the documentation. --> --> In the Summary section of the DATA_SET_DESCRIPTION, many of these are not found in the data, others are missing from this list. --> --> In the 'data/' are found these targets: EARTH, SUN, RADEC=279.23,38.78=Vega, RADEC=89.31,21.94=SUN, RADEC=110.00,85.00. Why isn't Earth found in the Summary list? What is the RADEC=110.00,65.00 and why isn't it listed as well? --> --> Also compare with the RALPH Calibrations and other observations section. It doesn't list everything. --> --> The TARGET_NAME values listed in the file appear correct. Note that questions in the presentation about the targeting of RA/Dec are actually referring to the FITS header, which is not a direct concern for PDS archiving (but is potentially problematic for some end users). The PDS labels do contain appropriate TARGET_NAME references. Earth was not actually observed, so any indication that it was should be expunged from labels an from other documents describing the data sets. The error maps appear to be all zero. Please investigate and document/correct as appropriate. There appears to be fixed-pattern noise in the primary image in the FITS file, and wondered if the flat field been applied. Investigate whether the flat field has been applied to the primary data (the PDU in the FITS file) for calibrated data. The ICD says it has been applied, and it should be. If these statements are true, then the very regular noise pattern needs to be explained. The calibration documents don’t seem to include the attempts to use shadow to characterize the light leak problem. Please add some sort of explanation/documentation of what was done when. Please add to the PDS label enough processing history for a user to be able to determine relatively easily all the potentially variable steps in the processing that was applied. ======================================================================= List of liens for LORRI data sets --------------------------------------------------- Result: Not Certified. Delta review required. DATA_SET_ID: NH-X-LORRI-2-PLUTOCRUISE-V1.0 NH-X-LORRI-3-PLUTOCRUISE-V1.0 File: 'calib/calinfo.txt' --> typo: The test of the calinfo.txt file states: "[calib] Directory containing calibration files for Alice data." "Alice" should be replaced with "LORRI". --> Remove references to “obsolete” files in calinfo.txt. Directory: 'catalog/' --> SBN typically does not include target catalog files for existing targets, but EN does not have a target catalog file in its database for "136108 HAUMEA" and "136472 MAKEMAKE". Please provide them. File: 'catalog/dataset.cat' --> The sequence listing currently is in DOY, but other date references are in YMD. Please add YMD to the sequence list in the dataset.cat. File: 'catalog/lorri.cat' --> typo: Whole document is written in future tense, e.g. "New Horizons is being prepared to launch in January 2006" (line 36). --> typo: PDS reference is only given after the first instance of a reference. Is this correct? --> typo: line 11: "Furthermore, is" -> "Furthermore, it is" --> typo: line 86: To what manuscript does "Figure 3" apply? Is this archived under a different name? --> typo: line 154: "++70" -> "+70" --> Correct the FOV in lorri.cat. Files: 'document/*.lbl' --> SPACECRAFT_NAME = "NEW HORIZONS": most labels skip this for INSTRUMENT_HOST_ID File: 'document/binary_lorri_img_hdr.lbl' --> typo: line 28: "seleected" -> "selected" File: 'document/nh_lorri_v100_ti.txt' --> typo: line 19: The sentence "s such..." is incomplete and/or may not be necessary given the previous paragraph. --> typo: line 138: Are these 10 references archived anywhere? If possible, when the issue of FITS format is mentioned as an explanation of the file format, please provide a reference to “more FITS information” (for example, mention the FITS Support Office), and make it clear that the image itself is always in the primary data unit (referred to as “extension zero” in some software packages). The calibration file labels should include some minimal description and basic information about how they were derived or created. Please list calibration files actually used in the data reduction in the data labels for the reduced data. There is no specific keyword for this in PDS3 – you can use NOTE. (Spice files may be listed as well, if the information is available.) [N.B.: In PDS4 there are explicit pointers to track this information, so a solution that would allow the information to be harvested programmatically is preferred.] If possible, please include a rough indication of the location of the target within the image (in pixel coordinates). Make sure the quaternion fields are populated in the data labels. If possible, add RA, Dec and clock angle to the labels. It looks like the LORRI data from 2008-10-15 also have something weird going on, where the calibrated data don’t look like the raw data, or any data. This happens to be the same date that MVIC had its windowing issue, but it’s not clear that these are related. The problem needs to be investigated and resolved as appropriate. There are some discrepancies involving references and sequences that did not result in data (as in MVIC) that should be resolved or explained. Please add instrument and instrument host IDs to data labels if they aren’t there already. ======================================================================= List of liens for MVIC data sets --------------------------------------------------- Result: Not Certified. Full review required. DATA_SET_ID: NH-X-MVIC-2-PLUTOCRUISE-V1.0 NH-X-MVIC-3-PLUTOCRUISE-V1.0 File: 'catalog/dataset.cat' --> The sequence listing currently is in DOY, but other date references are in YMD. Please add YMD to the sequence list in the dataset.cat. --> Resolve the discrepancy between the dataset.cat SEQ list and the data found in the data directories. As it is, it looks like data are actually missing, but it’s not clear that data were ever taken. File: 'document/nh_ralph_v100_ti.txt' --> typo: line 19: The sentence "s such..." is incomplete and/or may not be necessary given the previous paragraph. --> typo: line 161: Are these 13 references archived anywhere? --> Delete the incomplete reference citations from nh_ralph_v100_ti.txt. File: 'document/samples/mpf_0139719107_539_e_1_sm.lbl' --> "-87,258,824" is below the acceptable minimum of "0" for EXPOSURE_DURATION with the type "REAL". File: 'document/seq_mvic_plutocruise.tab' --> Documentation of the dimensions of the data vs. the physical size of the pushbroom aperture needs to be expanded a bit; it was not clear to the reviewers precisely what was meant. Users need an easily found index that maps file name to sequence. Preferably this would come as part of a science index with additional key user search fields. The reviewers will identify the columns to be included in such an index. The acronym “TDI” was a mystery to the reviewers. Please try to follow the convention of defining the acronym the first time it is used in a document or especially in a label. (It is not reasonable to require users to seek, download, and read an acronym list in order to understand a data label.) --> Example found in data file header: SCANTYPE=TDI, EXPTIME=2.9 The reviewers very strongly requested that information to be provided to give users some indication of where the actual target is in the image (in pixel location, e.g.). This could be supplied as a separate table, in the labels, in an index file, or some other reasonable format. The actual solution will be worked offline with reviewers. The calibrated images do not look calibrated (see knight_review_jan13.ppt slide 8). This needs to be investigated and either explained or corrected or both, as appropriate. ======================================================================= List of liens for PEPSSI data sets --------------------------------------------------- Result: Certified. Has minor liens. --> Note that the timestamp clarification (mentioned in Rudy’s presentation, slides 24-5, (or seen in 'nh-x-pepssi-3-plutocruise-v1.0/data/20070913_005203/pep_0052033917_0x691_sci_1.lbl' errors below)) is very important. SBN should wait to receive updated files related to that before posting the data, if possible. DATA_SET_ID: NH-X-PEPSSI-2-PLUTOCRUISE-V1.0 NH-X-PEPSSI-3-PLUTOCRUISE-V1.0 File: 'calib/calinfo.txt' --> typo: The test of the calinfo.txt file states: "[calib] Directory containing calibration files for LEISA data." "LEISA" should be replaced with "PEPSSI". File: 'catalog/dataset.cat' --> There is disagreement between the ApID range and the defined ApIDs in the Data section. The table that defines the ApID range is missing ApIDs 0x697 and 0x698 that are later defined in the table that lists each ApID and their meaning. File: 'catalog/pepssi.cat' --> Instrument Overview, Specifications, Energy Range values disagree with that claimed in the succeeding paragraph. --> Detector, Summary, second sentence disagrees with the Details section. Additional sources indicate that this sentence describes the sister instrument on Messenger. --> typo: line 89: "Composition" should be lowercase. --> Detector, Summary section, lines 100-101: No not all have the electron ion pair. --> Detector, Summary section, lines 101: "4 pixels" conflicts with the details section. --> line 260 equation: The conversion is probably not correct. --> line 262 equation is missing delta. "E" should be "dE" or "deltaE" File: 'nh-x-pepssi-3-plutocruise-v1.0/data/20070913_005203/pep_0052033917_0x691_sci_1.lbl' --> The lbl file has the note “PHA spectrogram of weighted (Note 1) event counts between start and end times for each energy and TOF bin”. The lbl Start and End times agree with the “MET” and “METEND” times in the Primary HDU which contains notes “(used in file creation code)”, suggesting that the times given are only for the file name. There is also a keyword “STARTMET” in the Primary HDU (“5.2062744E7 / Actual time stamp”) which does not agree with the “MET” time. However, given the number of time entries from the SPEC_ headers (“1440”), the time width represented (“0.016666666666666666” hours) suggests that the “STARTMET” is not the correct time stamp to use and that the “MET” time from the Primary HDU should be used. Since no time stamps are given in the spectrogram data and no definitive document on timing, the user is left with an uncertainty which time should really be used. This should be fixed. --> The lbl file notes that the time is given in column 1 as “ET” with the time duration given in column 4 of the “FLUX” HDU. It is unclear whether the time stamp is the beginning, middle, end, or at some other location within the accumulation window. This needs to be clarified. File: 'document/nh_pepssi_v110_ti.txt' --> Incomplete sentence in second paragraph: "Field(s) Of View (FOV(s)). As such, and also because it is not likely to be updated in a timely fashion as" --> typo: line 484: the 'x' should be a '+' like the rest on the line. File: 'document/samples/pep_0112341117_691_s_1_07.asc' --> The fifth table entry shows a rate box of “R00B(787.60,1145.14)keV”. No document has an explanation of a rate box “R00B”. File: 'index/index.tab' --> All TARGET_NAMEs are N/A though labels have "SOLAR WIND". There is missing information discussing the effect of spacecraft spin on the PEPSSI data. It is surmised that spacecraft spin information along with the instrument pixel vectors (provided in the DOCUMENT directory) could be used to resort some of the PEPSSI level 2 data in order to generate a sky map to reveal the directions of fluxes. It is not clear how much of the variation observed in the PEPSSI data is due to orientation. This should be discussed. --> The spin phase question needs to be investigated. Something appropriate needs to be said about this, once the actual effect, consequences, and relevance to the PEPSSI data are determined. ======================================================================= List of liens for SDC data sets --------------------------------------------------- Result: Not Certified. Full review required. DATA_SET_ID: NH-J-SDC-2-JUPITER-V3.0 NH-J-SDC-3-JUPITER-V3.0 NH-X-SDC-2-LAUNCH-V3.0 NH-X-SDC-2-PLUTOCRUISE-V1.0 NH-X-SDC-3-LAUNCH-V3.0 NH-X-SDC-3-PLUTOCRUISE-V1.0 File: 'calib/sdc_cal_matrix_*.tab' --> line 16: The START_TIME value should not be quotes. Otherwise getting this error: "START_TIME" only accepts a type of "TIME" and value "2006-01-17T00:00:00" was interpreted as a "TextString". File: 'catalog/dataset.cat' --> line 66: The DATA_SET_TERSE_DESC field is over the 255 character limit. It needs to be shorten. Also it appears almost identical to the ABSTRACT_DESC which it should be an abbreviated version of. --> The ABSTRACT_DESC should not describe the calibration process. --> Add a note to the dataset.cat file that explains the difference in on/off activity between the early launch and cruise data sets. --> For V3.0 datasets, the REFERENCE_KEY_ID should be changed from "N/A" to "POPPEETAL2010" since this reference is referred to twice in the file. --> The ABSTRACT_DESC for the Jupiter encounter phase data needs to be re-written to contain text that will help users find the data in, e.g., the ADS database. --> typo: for plutocruise: "werre" should be "were" --> For launch data sets, under section "SDC Updates for LAUNCH, Data sets V2.0", paragraph: " New charge-velocity-mass calibration curve", the paragraph mistakenly refers to POPPEETAL2010 but the correct reference is JAMESETAL2010. File: 'catalog/sdc.cat' --> If it is easy to replace HORANYIETAL2007 with HORANYIETAL2008, please do. Otherwise, please note someplace where a user might be thinking about references that these are the same paper. Whether or not the reference can be changed everywhere, the HORANYIETAL2007 reference object (in the reference catalog file) should be updated with a note that is it superseded by HORANYIETAL2008. --> Does there need to be some discussion of the failure of the SDC channel 11? --> typo: line 41: "usally should be "usually". Files: 'data/*/*.lbl' --> Random labels are have 1 fewer extension from the rest, not always the same missing extension for jupiter and launch level 2 data sets. Is this correct? --> All labels in the pluto level 3 2009 and 2010 directories have only one extension, instead of the 3 expected. Is this correct? --> In the Pluto Cruise calibrated data labels the last (Column 10) DESCRIPTION field begins with “Auto description failed.” This should be corrected. --> There is a hardware issue in the SDC that causes lines of crosstalk data to appear in the observational data file as well during calibration tests. Ideally, these lines should be omitted as they are not actually usable. At the least, they should be flagged as non-observation lines. Note that this involves changing bytes in the data files. File: 'document/docinfo.txt' --> "NH_MISSION_TRAJECTORY.*" is not listed. Please add it. Files: 'document/sdc_on_off_times_v0077*.tab' --> The sdc_on_off_times_v0077.tab and sdc_on_off_times_v0077_alt.tab ON/OFF SDC files are too long and not very useful for science considerations. A shorter version with only science data would be much more useful. --> Add a column to the on/off table (or create a new table, or use some other reasonable method) to enable a user to more easily find longer blocks of contiguous operation of the instrument. Directory: 'document/' --> In order to derive final validated IDP impact rates as a function of dust mass, one still has to proceed with level 4 analysis , as defined in HORANYI ETAL2007, in order to remove any suspected noisy events. This is not discussed at all in DPS data base. File: 'extra/extrinfo.txt --> typo: "SDC_CAL_MATRIX_BASE.DAT" should be "SDC_CAL_MATRIX_BASE.FIT". --> typo: last line: "viewers my not" should be "viewers may not" Please add inflight stimulus calibration data to these data sets. The fact that there are no large particles observed in any of these data sets is surprising. Some comment should be made about this in the dataset.cat file – depending on whether this ultimately appears to be true or an artifact. During cruise phases there are long (order of weeks) periods of time when the SDC is off. It is highly desirable for these data sets to have a simple table that shows these long-term periods of planned activity and inactivity to support data search and selection. There appears to be duplication of part of the raw Pluto cruise data. This should be investigated and either explained or corrected. In the calibrated data set, the corresponding data are “missing” and the FITS files throw errors when read. Make sure there is an easily discovered (in the label if it’s very short, in the dataset.cat if it’s longer, in a document that is referenced in one or both of those places if it’s very long) explanation about hits that appear below threshold. In sdc-2-plutocruise / data: why is the timestamp negative in the engineering SDC FITS files? (need to use /unsigned keyword in MRDFITS.pro on Mac OSX, IDL 7.1) In sdc-2-plutocruise / data: is there a large chunk of duplicate data store in the folders (mission day approximately 800 to 1100) – folder “data/20100723_014215”? In sdc-3-plutocruise / data : Why do the data only extend through approximately April 2009? There are file folders that are labeled as 2010 data but I always get FITS EOF extension errors when trying to read them in both IDL and with FV. Why is the number of events between plutocruise raw and plutocruise calibrated different (raw = 24,181, calibrated = 9164) – obviously related to both missing calibrated and duplicate raw data? In SDC plutocruise document folder, the SDC on/off times table (sdc_on_off_times_v0077.tab) only contains data up to September 2007. This should be updated to the correct time period of the plutocruise data (June 07 to July 10). In SDC plutocruise document folder, the nh_trajectory.tab only contains data up to September 2007. In numerous files and file types, "Celsius" is misspelled as "Celcius". Do a quick 'grep' to find them all. ======================================================================= List of liens for SWAP data sets --------------------------------------------------- Result: Certified. Has minor liens. DATA_SET_ID: NH-X-SWAP-2-PLUTOCRUISE-V1.0 NH-X-SWAP-3-PLUTOCRUISE-V1.0" File: 'aareadme.txt' --> line 39-43: Text states data taken between 2007-06-23T00:00:00 to 2010-07-18T00:00:00. I find data from 2008-05-28 to 2010-07-17. nh.cat gives the mission phase boundaries as: PLUTOCRUISE 2007-06-27 to 2014-12-31. The text should state the time range of the archive and explain why that differs from the time range of the mission phase. You could consider pointing users at seq_swap_plutocruise.tab in the DOCUMENT directory for a list of the time intervals that instrument was operating and the activities being performed. --> typo: Under the "Required Reading Summary List" section, make sure that the file two file listings' file descriptions line up. File: 'document/nh_swap_v100_ti.txt' --> typo: Add a blank line between the paragraphs on lines 267 and 272. File: 'document/swap_cal.pdf' --> Page 3, last Para - added a reference to Figure 2 in the last sentence, "Below we show the response curve..." --> Page 7, 4) Energy Bin Calculations --> --> "Since we do not know what angle the ions enter, we assume the ions enter the center of the instrument..." --> --> What are the practical consequences of this assumption and how does it impact (or fold into) your error computations? No further discussion is provided. --> --> Para refers to esa_rpa_v19_energy_binsf.csv rather than esa_rpa_v19_energy_binsf.tab --> --> Table above provides energy width. Is this full-width, half maximum or some other width? Neither text nor file label provide a description of the width parameter. --> Page 11, Background Subtraction --> --> "are scaled by the distance to the Sun squared and those scaled rates (counts*R^2/sample) are stored in.." --> --> You should provide the units for the distance to the Sun (AU vs. km will make a difference in the calculation). File: 'index/index.tab' --> All TARGET_NAMEs are N/A though labels have "SOLAR WIND".