====================== PEPSSI Data Volumes Delivered Oct 29, 2007 ====================== =================== General - New items =================== calib/calinfo.txt - Typos: line 12: "Documentat" -> "Document" catalog/ - Why is calibration.cat included when TARGET_NAME is set to "SOLAR WIND" in the DATA labels? catalog/calinfo.txt - Why is calibration.cat included when TARGET_NAME is set to "SOLAR WIND" in the DATA labels? catalog/dataset.cat - TARGET_NAME in DATA_SET_TARGET object is set to "N/A". Change to the value(s) used in TARGET_NAME in the DATA labels. voldesc.cat - Why is ^TARGET_CATALOG set to "CALIBRATION" with the TARGET_NAME is set to "SOLAR WIND" in the DATA labels? =========================================================== General - Outstanding items from the early October delivery =========================================================== data/*lbl - For the STATUS extensions, must the packet information for each column be repeated in each label? Is this information meaninful to the end user? document/pepssi_ssr_images/pepssi_ssr_images.lbl - The comment records are misleading because they imply this label is for a data file. Remove the comment cards. calib/hk_stat_input_20041016.lbl - In the HOUSEKEEPING_TABLE object, the value for NAME is "PEPSSI_HOUSKEEPING_TABLE". The letter "E" should be inserted between the "S" and "K". calib/hk_stat_input_20041016.lbl & .tab - The label does not correctly define the table layout. The SBN table verifier (pdstv) issues these errors: Column 1: FORMAT "G15.6" incompatible with DATA_TYPE 'Real'. Column 2: FORMAT "G15.6" incompatible with DATA_TYPE 'Real'. Column 3: FORMAT "G15.6" incompatible with DATA_TYPE 'Real'. Column 4: FORMAT "G15.6" incompatible with DATA_TYPE 'Real'. Column 5: FORMAT "G15.6" incompatible with DATA_TYPE 'Real'. Column 6: FORMAT "G15.6" incompatible with DATA_TYPE 'Real'. - Do not mix formats such as 0.0141930, -3.48000, and 6.52418E-06, within individual columns. The FORMAT keyword requires numeric values to have the same format within a column. And the decimal points should align. ============================================================== nhlape1001 - Outstanding items from the early October delivery ============================================================== /index/index.lbl & index.tab - INDEX.LBL states: START_TIME = 2006-02-20T13:16:45.823 STOP_TIME = 2006-11-23T07:15:56.379 but the minimum START_TIME in the index.tab file is 2006-02-19T23:59:59.323 and the maximum STOP_TIME in the same file is 2006-11-24T23:59:59.379. + It appears this fix was missed! ============================================================================= ============================================================================= 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 ===================== General (all volumes) ===================== Targets x How would one find the PEPSSI data if the target is "N/A"? Does NH plan to use this value 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 would another target such as "SOLAR WIND", "DUST", or "JUPITER" be appropriate? "N/A" is useless. + Using "SOLAR WIND" in the DATA labels. All aareadme.txt, info.txt, and catalog files x Please run us through a spell checker. + This appears to have been done. All info.txt files x RECORD_TYPE has inconsistent values across these files. Both STREAM and FIXED_LENGTH are used. For example, calib/calinfo.txt used FIXED_LENGTH but document/docinfo.txt uses STREAM. aareadme.txt x Typos: line 85: MEHODOLOGY -> METHODOLOGY line 108: GOUND TESTING -> GROUND TESTING line 441: Sytem -> System line 483: obvserving -> observing line 655: keywor/value -> keyword/value line 789: correspoding -> corresponding line 853: colunm -> column line 860: thsi -> this x PEPSSI_SSR.DOC is listed here but does not exist in the document directory. + Deleted x PEPSSI_EQUATION*.PNG is listed here but none of these files exist in the document directory. + Deleted. - Add an entry for the NH_PEPSSI_V110_TI.TXT SPICE kernel to the DOCUMENT section of this file. + Added voldesc.cat x 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". - Changed to "CALIBRATION" but the data labels have target_name set to "SOLAR WIND". x Actually, what should the target be for the PEPSSI data sets? + Probably solar wind per NH team. catalog/catinfo.txt x There is no file named "INSTR.CAT". Change it to "PEPSSI.CAT". catalog/*.cat x REFERENCE_KEY_IDs at the end of the catalog files must be defined in the ref.cat file. catalog/dataset.cat x The section named "Bad Time Intervals" states the "PEPSSI_BTI.txt" file lists bad time intervals. However this file (case insensitive) is not on any of the PEPSSI volumes. + Removed reference. catalog/pepssi.cat - line 51: "hockey-puck-size"? I have no clue how big a hocky puck is! x Typos: line 25: "was was" -> "was" line 86: "also earch" -> "also search" line 266: "epssilon" -> "epsilon" data/*lbl x TARGET_NAME should not be "N/A". + Changed to "SOLAR WIND" x Please read the definition for the QUATERNION_DESC object. This element is a *POINTER* to an accompanying document that describes the type of quaternion being used. Why is the quaternion described in each data label? This information should really be extracted into a document! - For the STATUS extensions, must the packet information for each column be repeated in each label? Is this information meaninful to the end user? Consider moving this information to a separate document unless it more useful for the user to see it in the label. document/docinfo.txt x Typos: line 54: MEHODOLOGY -> METHODOLOGY line 77: GOUND TESTING -> GROUND TESTING document/nh_pepssi_v110_ti.txt x Why is this file here? Is NH delivering a SPICE data set? + NH elected to keep this SPICE kernel here. Yes, NH delivered a SPICE data set. document/pepssi_ssr_images/pepssi_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 signficant). See Chapter 12 (ODL) in the PDS Standards Reference. 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 = { "pepssi_ssr_figure1.png", "pepssi_ssr_figure2.png", ... "pepssi_ssr_tablenn.png" } x DATA_SET_ID should be set to the ID for this data set. x PRODUCT_ID is not required for documents. + Still in the labels. OK to keep. - The comment records are misleading because they imply this label is for a data file. Remove the comment cards. + Not implemented yet. document/samples/pep_0033285117_691_e_1_09.asc x Column 4, CROSS_TALK_INDICATOR, is defined as a logical data type and has values of "F" or "T" when displayed in "fv". The sample file has values of 70 and 84 (the equivalent decimal values) that need to be corrected to F or T. Please verify that the processes which generate the ASCII data samples correctly convert the L (logical) data type. document/samples/pep_0033285117_691_e_1_10.asc x Columns 4 and 5 are defined as logical data types but numeric values 70 and 84 appear in this sample instead of F and T. document/samples/pep_0033285117_691_e_1_11.asc x Columns 4, 5, and 6 are defined as logical data types but numeric values 70 and 84 appear in this sample instead of F and T. document/samples/pep_0033285117_691_e_1_12.asc x Columns 4, 5, 6, and 7 are defined as logical data types but numeric values 70 and 84 appear in this sample instead of F and T. document/samples/pep_0033285117_691_s_1_*.asc x Why are these samples included in this data set? There is no FITS file associated with these samples in this data set. This is confusing. But the sampinfo.txt file explains that raw and calibrated samples are provided so this should be OK. + The sample reports now have a record that identifies the data volume where the data file resides, which helps. =========== nhjupe_1001 =========== catalog/dataset.cat x Typos: line 123: "Diagostic" -> "Diagnostic" line 124: "Diagostic" -> "Diagnostic" line 137: "read datafrom" -> "read data from" index/index.lbl & index.tab x INDEX.LBL gives a STOP_TIME of 2007-06-21T01:51:37.418 but the maximum STOP_TIME in the INDEX.TAB file is 2007-06-21T23:59:59.418. Does the index.lbl file have an incorrect value for STOP_TIME? Actually if values for the START_ and STOP_TIME columns was pulled directly from the data labels, then you're welcome to remove START_TIME and STOP_TIME keywords from the index label file! index/cumindex.tab & cumindex.lbl x Same problem as index.lbl & index.tab. =========== nhjupe_2001 =========== calib/calinfo.txt - Typos: line 12: "Documentat" -> "Document" x Change RECORD_TYPE to STREAM; calib/*lbl x The filename value for HOUSEKEEPING_TABLE should be upper-case. x The filename value for PRODUCT_ID should probably be upper-case, too. - In the HOUSEKEEPING_TABLE object, the value for NAME is "PEPSSI_HOUSKEEPING_TABLE". The letter "E" should be inserted between the "S" and "K". + Missed this change in hk_stat_input_20041016.lbl? calib/hk_n1_input_20050228.lbl & .tab x The label does not correctly define the table layout. SBN's table verifier tool (pdstv) found these errors: Column 1: FORMAT "" incompatible with DATA_TYPE 'Real'. Column 1: Field width (0) does not span the field (6 bytes). Column 2: FORMAT "" incompatible with DATA_TYPE 'Real'. Column 2: Field width (0) does not span the field (8 bytes). The FORMAT keyword needs to be inserted into each COLUMN object. For example, FORMAT = F6.4. x Why do values in table records 13 through 26 have a different format than the those in the first 12 records? Within a column, numeric values must have the same format. For example, record 13 should look this: 1.0000 0.000 calib/hk_stat_input_20041016.lbl & .tab - The label does not correctly define the table layout. The FORMAT keyword needs to be inserted into each COLUMN object. For example, FORMAT = F6.4. - Do not mix formats such as 0.0141930, -3.48000, and 6.52418e-06, within individual columns. The FORMAT keyword requires numeric values to have the same format within a column. + Some modifications were made but the label and table still do no pass pdstv! index/index.lbl & index.tab x INDEX.LBL states: START_TIME = 2007-01-06T08:46:11.382 STOP_TIME = 2007-06-21T01:51:37.418 but the minimum START_TIME in the index.tab file is 2007-01-05T23:59:59.382 and the maximum STOP_TIME in the same file is 2007-06-21T23:59:59.418. Does the index.lbl file have incorrect values for the START_TIME and STOP_TIME keywords? Actually if values for the START_ and STOP_TIME columns was pulled directly from the data labels, then you're welcome to remove START_TIME and STOP_TIME kewyords from the index label file! index/cumindex.tab & cumindex.lbl x Same problem as index.lbl & index.tab. =========== nhlape_1001 =========== catalog/dataset.cat x See nhjupe_1001. index/index.lbl & index.tab x INDEX.LBL states: START_TIME = 2006-02-20T13:16:45.823 STOP_TIME = 2006-11-23T07:15:56.379 but the minimum START_TIME in the index.tab file is 2006-02-19T23:59:59.323 and the maximum STOP_TIME in the same file is 2006-11-24T23:59:59.379. Does the index.lbl file have incorrect values for the START_TIME and STOP_TIME keywords? Actually if values for the START_ and STOP_TIME columns was pulled directly from the data labels, then you're welcome to remove START_TIME and STOP_TIME kewyords from the index label file! index/cumindex.tab & cumindex.lbl x Same problem as index.lbl & index.tab. =========== nhlape_2001 =========== calib/calinfo.txt x See nhjupe_2001. calib/*lbl x See nhjupe_2001. calib/hk_n1_input_20050228.lbl & .tab - See nhjupe_2001. calib/hk_stat_input_20041016.lbl & .tab - See nhjupe_2001. index/index.lbl & index.tab - INDEX.LBL states: START_TIME = 2006-02-20T13:16:45.823 STOP_TIME = 2006-11-23T07:15:56.379 but the minimum START_TIME in the index.tab file is 2006-02-19T23:59:59.323 and the maximum STOP_TIME in the same file is 2006-11-24T23:59:59.379. Does the index.lbl file have incorrect values for the START_TIME and STOP_TIME keywords? Actually if values for the START_ and STOP_TIME columns was pulled directly from the data labels, then you're welcome to remove START_TIME and STOP_TIME kewyords from the index label file! + It appears this fix was missed. index/cumindex.tab & cumindex.lbl x Same problem as index.lbl & index.tab.