========================= New Horizons Data Volumes Delivered Oct 29, 2007 ========================= =================== General - New items =================== dataset.cat - In the Instrument description section, under the DOCUMENTS heading, replace the list with: _SSR.* NH___TI.TXT SOC_INST_ICD.* where _SSR.* is the appropriate instrument SSR paper and NH___TI.TXT is the appropriate instrument kernel file. document/payload_ssr_images/payload_ssr_images.lbl document/soc_inst_icd_images/soc_inst_icd.lbl + For Anne Raugh: Is it OK if the directory path is included as part of the filenames in the pointer(s). ============================================================== General - Outstanding items from the early October delivery ============================================================== aareadme.txt - Why are these files *so* long? I would argue some of the text should be moved to the dataset.cat file or into a new document! document/*all labels - DATA_SET_ID should be set to the ID for this data set or a list of all data sets to which this document applies. + Implemented for all labels except nh_trajectory.lbl where DATA_SET_ID is still set to "N/A". - PRODUCT_ID is not required for documents. + Removed for all labels except nh_trajectory.lbl. - The following comment records are misleading because the items in this directory are documents not data files. Remove the misleading comment records or modify the text: /* DATA OBJECT POINTERS */ /* GENERAL DATA DESCRIPTION PARAMETERS */ /* DATA OBJECT DEFINITIONS */ In fact, all of the comments cards in the labels in the document directory are not very useful, so consider deleting them. calib/*all labels document/*all labels - The SPACECRAFT_NAME and ID elements were deprecated long ago. Only SPICE gets to use these keywords because, well, SPICE is SPICE. All occurrences SPACECRAFT_NAME and SPACECRAFT_ID must be replaced with INSTRUMENT_HOST_NAME and INSTRUMENT_HOST_ID, respectively, for all labels in the calib, data, document, and index directories. + This was **not** implemented for labels in the calib and document directories! ============================================================================= ============================================================================= Items from the early October delivery are included below. They are included here only as reference. ============================================================================= ============================================================================= Bullet Key x = Item was implemented or closed. - = Item was not implemented or is still open. + = Comment All Labels ---------- x The SPACECRAFT_NAME and ID elements were deprecated long ago. Only SPICE gets to use these keywords because, well, SPICE is SPICE. All occurrences SPACECRAFT_NAME and SPACECRAFT_ID must be replaced with INSTRUMENT_HOST_NAME and INSTRUMENT_HOST_ID, respectively, for all labels in the calib, data, document, and index directories. Good - INSTRUMENT_HOST_NAME was used in the index tables. + This was **not** implemented for labels in the document directory! data/*all labels* ----------------- x Values for keywords such as QUATERNION and SC_TARGET_POSITION_VECTOR comprise an ordered set (i.e., the order of the values *is* important). According to ODL, parentheses (), not brackets {}, should be used to identify an ordered set. x Wrong constants are being used to indicate unknown, not applicable, and null values for element keywords of a numeric type. For example, For example, if the value for TARGET_CENTER_DISTANCE is not applicable, it *MUST* be set to "N/A" in the PDS label, not to -100000.e+32. Please refer to section 17.1 of the PDS Standards Reference and convert numeric constants indicating unknown, not applicable, or null values to "UNK", "N/A", or "NULL". Although the examples for "UNK", "N/A", and "NULL" values in 17.1 only use keywords with a character type, the rules apply to all types of label and catalog keyword elements, including numeric. As Anne noted, "Section 17.2 of the SR is NOT RELEVANT" for PDS labels. This section describes how to translate the figurative constants ("UNK", "N/A", and "NULL") in the labels and catalog files to numeric constants in index tables to make these products easier to use. aareadme.txt ------------ - Why are these files *so* long? I would argue some of the text should be moved to the dataset.cat file or into a new document! x Each volume has a SPICE instrument kernel such as NH_PEPSSI_V110_TI.TXT in the document directory. Since these kernels are instrument-specific, they should be listed. voldesc.cat ----------- x RECORD_TYPE is fixed length but there is not RECORD_BYTES keyword. Suggest using RECORD_TYPE = STREAM without RECORD_BYTES. x Target of "N/A"...For many volumes (nhjupe_1001, nhjupe_2001, nhjusw_1001, nhjusw_2001, nhlape_1001, nhlape_2001, nhlasw_1001, and nhlasw_2001), the TARGET_CATALOG pointer has a keyword value of N_A.CAT which implies there is a catalog file named N_A.CAT. However, this file does not exist in /catalog/. If there is no target then simply set the TARGET_CATALOG pointer to "N/A". Actually, what should the target be for the charged particle and solar wind data sets? How would one find the PEPSSI data using a target search engine if the target in "N/A"? Does NH plan to use "N/A" for the entire mission? For the commissioning and cruise phases, it may be appropriate to use "CALIBRATION" if the instrument was not really pointing at a target. Or use one of the existing target objects such as "SOLAR WIND", "DUST", or "JUPITER". catalog/dataset.cat ------------------- x The values for START_TIME and STOP_TIME should not end in "Z". x These data sets have been through a peer review, correct? Please change the ARCHIVE_STATUS to "IN LIEN RESOLUTION". - These files are poorly formatted. The PDS Standards Reference describes how to indent and highlight the various sections of a dataset.cat file. See Appendix B, pp. 1-2. + Some formatting was done but there is still a paragraph near the start of the Dataset Overview section that is still not well- formatted. x The section named "Reference Frame (often mis-labeled as Coordinate System)" should simply be "Reference Frame". catalog/ref.cat --------------- x Why does this file contain only the PDS Standards Reference as a REFERENCE_KEY_ID, and why it is listed here? The PDS_VERSION_ID implicitly handles this. x The following REFERENCE_KEY_IDs are listed in various catalog files and must be included in the REF.CAT file: REFERENCE_KEY_ID Found in ------------------ ------------------------------------------------------- ANDREWSETAL1998 pepssi.cat CHENGETAL2007 lorri.cat, all LORRI dataset.cat files CONARDETAL2005 lorri.cat DANZMANNETAL1988 alice.cat HORANYIETAL2007 sdc.cat, all SDC dataset.cat files MCCOMASETAL2007 swap.cat, all SWAP dataset.cat files MCNUTTETAL1996 pepssi.cat MCNUTTETAL2007 pepssi.cat, all PEPSSI dataset.cat files MORGANETAL2005 lorri.cat NASAAO2001 nh.cat, nhsc.cat REUTERETAL2005 leisa.cat, mvic.cat REUTERETAL2007 leisa.cat, mvic.cat, all LEISA & MVIC dataset.cat files SIEGMUND2000 alice.cat SIEGMUNDETAL1992 alice.cat SLATERETAL2001 alice.cat SLATERETAL2005 alice.cat STERN&CHENG2002 nhsc.cat STERN&SPENCER2004A nh.cat, nhsc.cat STERNETAL1995 alice.cat STERNETAL2005 alice.cat STERNETAL2007 alice.cat, all ALICE dataset.cat files WEAVERETAL2007 sdc.cat, swap.cat, all dataset.cat files document/*all labels* --------------------- - DATA_SET_ID should be set to the ID for this data set or a list of all data sets to which this document applies. - PRODUCT_ID is not required for documents. - The following comment records are misleading because the items in this directory are documents not data files. Remove the misleading comment records or modify the text: /* DATA OBJECT POINTERS */ /* GENERAL DATA DESCRIPTION PARAMETERS */ /* DATA OBJECT DEFINITIONS */ In fact, all of the comments cards in the labels in the document directory are not very useful, so consider deleting them. document/nh__vnn_ti.txt ------------------------------- x Why is the instrument kernel included in each data set? It DOES provide details about an instrument "at fingertips" which is handy! Are these kernels subject to change over the duration of the mission? Will NH deliver a SPICE data set? + Yes, NH delivered a SPICE data set. It's OK to keep the instrument kernel in the document directory. document/payload_ssr_images/payload_ssr_images.lbl -------------------------------------------------- x Parentheses indicate an ordered set of values. Use brackets {} for an unordered set of values (i.e., the order of the items is not significant). See Chapter 12 (ODL) in the PDS Standards Reference. + Implemented, but the directory where the graphics live was included as part of the filenames in the pointer(s). Is this OK? Need to ask Anne Raugh. x The ^IMAGE pointers have no objects in the label. All IMAGE pointers should be replaced with one PNG_DOCUMENT pointer set to an unordered list of PNG file names: ^PNG_DOCUMENT = { "payload_ssr_figure1.png", "payload_ssr_figure2.png", ... "payload_ssr_table1cont.png" } document/samples/*asc --------------------- x Please verify that the processes which generate the ASCII data samples correctly convert the L (logical) data type. Several sample files in at least the PEPSSI data sets have the numeric values 70 or 84 instead of "F" or "T". x Why are BSCAL/TSCAL and BZERO/TZERO being ignored? The purpose of the samples is to show the expected data values, correct? For example, when the SWAP extensions are displayed in "fv", all of the values are positive because this tool applies zero-point values and scaling factors. Yet, most of the values in the samples are negative. At first glance, it seems the sample files provide the wrong data values. + Not implemented because the ASCII reports states scaling factors and offsets were *not* applied to the data values. x It's very hard to locate a FITS data file that is given on the FILENAME line in a sample. Consider providing the **PDS volume** path instead of the SOC path. + Excellent. Thanks for adding the path. document/soc_inst_icd_images/soc_inst_icd.lbl --------------------------------------------- x Parentheses indicate an ordered set of values. Use brackets {} for an unordered set of values (i.e., the order of the items is not significant). See Chapter 12 (ODL) in the PDS Standards Reference. + Implemented, but the directory where the graphics live was included as part of the filenames in the pointer(s). Is this OK? Need to ask Anne Raugh. x The ^IMAGE pointers have no objects in the label. All IMAGE pointers should be replaced with one PNG_DOCUMENT pointer set to an unordered list of PNG file names: ^PNG_DOCUMENT = { "soc_inst_icd_equation10_1.png", "soc_inst_icd_equation10_2.png", ... "soc_inst_icd_table9_9.png" }