Created by SBN:T.Barnes for the Rosetta MUST data sets. =============================================== Datasets Validated: RO-X-HK-3-ANTENNA_STATUS-V1.0 RO-X-HK-3-AOC_GEN-V1.0 RO-X-HK-3-EDAC-V1.0 RO-X-HK-3-HGA_APM-V1.0 RO-X-HK-3-IMP-V1.0 RO-X-HK-3-NAVCAM-V1.0 RO-X-HK-3-OCM_RCS-V1.0 RO-X-HK-3-RWL-V1.0 RO-X-HK-3-SOLAR_ARRAY-V1.0 RO-X-HK-3-STARTRACKER-V1.0 =============================================== Errors for: GLOABL (all datasets) Mac files (or Mac Extended Attributes of files) found are not PDS3 compliant and must be removed: --> RO-X-HK-3-ANTENNA_STATUS-V1.0/._AAREADME.TXT --> RO-X-HK-3-ANTENNA_STATUS-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-ANTENNA_STATUS-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-AOC_GEN-V1.0/._AAREADME.TXT --> RO-X-HK-3-AOC_GEN-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-AOC_GEN-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-EDAC-V1.0/._AAREADME.TXT --> RO-X-HK-3-EDAC-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-EDAC-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-HGA_APM-V1.0/._AAREADME.TXT --> RO-X-HK-3-HGA_APM-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-HGA_APM-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-IMP-V1.0/._AAREADME.TXT --> RO-X-HK-3-IMP-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-IMP-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-NAVCAM-V1.0/._AAREADME.TXT --> RO-X-HK-3-NAVCAM-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-NAVCAM-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-OCM_RCS-V1.0/._AAREADME.TXT --> RO-X-HK-3-OCM_RCS-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-OCM_RCS-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-RWL-V1.0/._AAREADME.TXT --> RO-X-HK-3-RWL-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-RWL-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-SOLAR_ARRAY-V1.0/._AAREADME.TXT --> RO-X-HK-3-SOLAR_ARRAY-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-SOLAR_ARRAY-V1.0/CATALOG/._SOFTWARE.CAT --> RO-X-HK-3-STARTRACKER-V1.0/._AAREADME.TXT --> RO-X-HK-3-STARTRACKER-V1.0/CATALOG/._MISSION.CAT --> RO-X-HK-3-STARTRACKER-V1.0/CATALOG/._SOFTWARE.CAT You cannot have an underscore in the DATA_SET_ID. Only alphanumeric, dash, period (for version), and forward slash are allowed. Suggest changing underscore to a dash/hyphen. Need to update in all places found (labels + documents). Invalid DATA_SET_ID values: --> RO-X-HK-3-ANTENNA_STATUS-V1.0 => RO-X-HK-3-ANTENNA-STATUS-V1.0 --> RO-X-HK-3-AOC_GEN-V1.0 => RO-X-HK-3-AOC-GEN-V1.0 --> RO-X-HK-3-HGA_APM-V1.0 => RO-X-HK-3-HGA-APM-V1.0 --> RO-X-HK-3-OCM_RCS-V1.0 => RO-X-HK-3-OCM-RCS-V1.0 --> RO-X-HK-3-SOLAR_ARRAY-V1.0 => RO-X-HK-3-SOLAR-ARRAY-V1.0 All files must have a PDS label associated with them. Please add one for the following: --> 'RO-X-HK-3-OCM_RCS-V1.0/BROWSE/OCM_ACCEL_MEAS_2014_Q1.PNG' --> 'RO-X-HK-3-OCM_RCS-V1.0/BROWSE/OCM_ESTIM_TRANS_VEL_2014_Q1.PNG' --> 'RO-X-HK-3-OCM_RCS-V1.0/BROWSE/OCM_EST_DIST_TORQUES_2014_Q1.PNG' --> 'RO-X-HK-3-OCM_RCS-V1.0/BROWSE/OCM_IMPULSE_MEAS_2014_Q1.PNG' All filenames must not be mixed case. Affected files: --> 'RO-X-HK-3-EDAC-V1.0/BROWSE/*.png' (note ".png" vs ".PNG") The NAVCAM data set should probably be a NAVCAM data set, not a ROSETTA_HK data set. HK data is included for many other instruments in their own data sets, usually side by side with the science data, but that is not required. You would just put in the description part of the ID that it was HK and replace the INSTRUMENT_ID/NAME. For instance, RO-X-NAVCAM-3-HK-V1.0 or RO-X-NAVCAM-3-HK-ENG-V1.0. Though is this data really CODMAC level 3? file: 'AAREADME.TXT' --> Introduction par 2: change "March 2014" to "March 2004" (note year) file: 'BROWSE/BROWINFO.TXT' --> The description states that only some parameters were used to generate thumbnails, but it appears that also sometimes timeframe is used as well. When browsing the user guide and eaicd, I could not find clearly what decisions lead to which browse products were generated, though the eaicd and browinfo refers the user to the user guide for more details, I can't find anything there. Doing a search for the word BROWSE, the word only appears thrice and in all instances no details are provided. file: 'RO-X-HK-3-ANTENNA_STATUS-V1.0/BROWSE/BROWINFO.TXT' --> DATA_SET_ID: Corrupted value of "RO-X-HK-3-ANTEANNA_STATUS-V1.0". Note the "ANTEANNA" vs "ANTENNA" files: 'BROWSE/*.LBL' --> Strongly suggest not using the IMAGE object, but DOCUMENT object as OSIRIS does and NAVCAM was asked to at the last review. Technically how you are using IMAGE is wrong. --> FILE_NAME: Should be the product, not the label. Note that this keyword is not required since you explicitly state where the data file is in the pointer. --> BROWSE_USAGE_TYPE: If you are not going to use it, I would drop it. It is an optional keyword. file: 'CATALOG/DATASET.CAT' --> ABSTRACT_DESC: "3 earth and 1 mars flyby" => "3 Earth and 1 Mars flybys" (note capitalization of planets and making flyby plural) --> ABSTRACT_DESC: Change the last character in the second paragraph from a colon to a period. --> ABSTRACT_DESC: Change the last character in the last paragraph from a colon to a period. --> START_TIME: For NAVCAM, the data label values start 6 months later and STARTRACKER data labels starts ~3 hours later. Are some data missing? Not an error, but odd considering for the other data sets the date/time was spot on. --> STOP_TIME: The values for RWL and SOLAR_ARRAY in the data labels are a few microseconds after the time in this file. --> CITAITON_DESC: Who are "Rosetta" and "SGS"? I would normally see something like "OSIRIS Team", which makes sense. Also best to list authors in a format as done in other data sets. If any are editors as opposed to authors, it would be best to clarify that as well. --> CITATION_DESC: Missing DATA_SET_ID value after the DS_NAME. --> CONFIDENCE_LEVEL_NOTE: Remember to update after review. file: 'CATALOG/REF.CAT' --> There is a newer version (2019-07-17) of this file (2018-08-29). file: 'CATALOG/SOFTWARE.CAT' --> SOFTWARE_DESC typo: " wi " => " will " UNIT of ".". What is this? Affected: --> RO-X-HK-3-EDAC-V1.0/DATA/NAVCAM_A_EDAC_CNTR --> RO-X-HK-3-EDAC-V1.0/DATA/NAVCAM_B_EDAC_CNTR --> RO-X-HK-3-EDAC-V1.0/DATA/STR_A_EDAC_CNTR --> RO-X-HK-3-EDAC-V1.0/DATA/STR_B_EDAC_CNTR --> RO-X-HK-3-OCM_RCS-V1.0/DATA/RCS_THRUST_ON_CYCLES_1_TO_8 --> RO-X-HK-3-OCM_RCS-V1.0/DATA/RCS_THRUST_ON_CYCLES_9_TO_12 --> RO-X-HK-3-STARTRACKER-V1.0/DATA/STR_A_B_MEAN_BACKGRND --> RO-X-HK-3-STARTRACKER-V1.0/DATA/STR_A_B_STD_DEV_BACKGRND --> RO-X-HK-3-STARTRACKER-V1.0/DATA/STR_A_STARS_1_TO_9_ID_NO --> RO-X-HK-3-STARTRACKER-V1.0/DATA/STR_A_STARS_1_TO_9_SXYZ_COORD --> RO-X-HK-3-STARTRACKER-V1.0/DATA/STR_B_STARS_1_TO_9_ID_NO --> RO-X-HK-3-STARTRACKER-V1.0/DATA/STR_B_STARS_1_TO_9_SXYZ_COORD files: 'DATA/*/*/*.LBL' --> Missing required spacecraft keywords: INSTRUMENT_HOST, INSTRUMENT_NAME, SPACECRAFT_CLOCK_START_COUNT, SPACECRAFT_CLOCK_STOP_COUNT, TARGET_NAME. If the value is "N/A", that is fine, but the keywords must be present. --> PRODUCT_CREATION_TIME keyword requires a TIME type, not a DATE type. The required format: YYYY-MM-DDThh:mm:ss[.fff] --> DATA_SET_NAME value does not match the value in the DATASET.CAT file. --> TARGET_NAME: No target was provided in the data labels, and since this data set spans the whole mission, not just 67P, the value of 67P does not seem appropriate or at least all inclusive. By way of reminder, all values found in the data labels should be found in the DS.CAT file as well (excluding "N/A" unless it is the only value, for TARGET_NAME is a required keyword). --> RECORD_TYPE: Why is this value always "STREAM"? In most if not all cases it should be "FIXED_LENGTH" for the data found herein. For instance you cannot have BINARY data be stream, otherwise you could never be able to read it. For the ASCII tables, all the tables appear to be fixed width anyways, so why not declare it as such? --> Column 1 is always named "TIME" or "(MISSION) TIME". But which time value are these? Start time, mid-time, under which system (UTC)? From one of the figures in the user guide I would guess start time. This information would be helpful. Also the ASCII and BINARY files spit out different values. How do you interpret the BINARY time values? --> Column 2 is always named "VALUE". This is not very descriptive. You have to go to the user guide to get an idea of what it might be, or the table DESCRIPTION in the file to get a guess at it. --> For Column 2 for the ASCII tables, suggest adding the FORMAT keyword. It may also be nice for the binary data as well. Recall that FORMAT is the preferred display of the values. files: 'DOCUMENT/*.PDF' --> Files need to be PDF/A-1a or PDF/A-1b compliant. file: 'DOCUMENT/EAICD_HK.PDF' --> 3.1.3.1: The RO-X-HK-3-OCM_RCS-V1.0 subdirectores are tabbed out different from the other data sets.