Created by SBN:T.Barnes for the Rosetta VIRTIS data sets. =============================================== Datasets Validated: RO-C-VIRTIS-2-ESC1-MTP013-V2.0 RO-C-VIRTIS-3-ESC1-MTP013-V3.0 RO-VIRTIS-5-V1.0 =============================================== Errors for: GLOABL (all datasets) file: 'RO-C-VIRTIS-2-ESC1-MTP013-V2.0/CALIB/HSOLEILROS2014.LBL' --> COL 2 START_BYTE: Currently column spans outside of length. Change value from '11' to '10'. file: 'RO-C-VIRTIS-3-ESC1-MTP013-V2.0/CALIB/HSOLEILROS2014.LBL --> RECORD_BYTES: Change from '21' to '23'. --> COL 2 START_BYTE: Currently does not encompass the data. Change value from '11' to '13'. file: 'CALIB/HSOLEILROS2014.TAB' --> Why is the L2 and L3 version of this file different? --> The L3 version of this file does not have the decimal place aligned and cuts the last significant figure if there are three digits left of the decimal. file: 'CATALOG/REF.CAT' --> This file is an old version (2018-08-29). The newest version (2019-07-17) is needed since it include more VIRTIS references. --> Missing reference FILACCHIONEETAL2016. Please add. Note not found in 2019-07-17 version either. --> Missing reference CIARNIELLOETAL2016. This is found in the 2019-07-17 version. files: 'DOCUMENT/*.PDF' --> Files need to be PDF/A-1a or PDF/A-1b compliant. file: 'DOCUMENT/RO_VIRTIS_EAICD.ASC' --> This file claims to be Issue 4.5, but the PDF file claims to be Issue 4.6. Also, this file seems to be an older version of Issue 4.5 than found in the V1.0 data set. file: 'DOCUMENT/RO_VIRTIS_EAICD.PDF' --> In the title this file claims to be Issue 4.6 21-02-2018, but the page headers state it is Issue 4.5 October 2017. Please correct. =============================================== Errors for: RO-C-VIRTIS-2-ESC1-MTP013-V2.0 Missing Data Products. Why are the following data products removed since the prior data set version: --> RO-C-VIRTIS-2-ESC1-MTP013-V1.0/DATA/STP043/VIRTIS_H/H1_00382584583.QUB --> RO-C-VIRTIS-2-ESC1-MTP013-V1.0/DATA/STP043/VIRTIS_H/S1_00382584817.QUB --> RO-C-VIRTIS-2-ESC1-MTP013-V1.0/DATA/STP043/VIRTIS_M_IR/I1_00382582821.QUB --> RO-C-VIRTIS-2-ESC1-MTP013-V1.0/DATA/STP043/VIRTIS_M_VIS/V1_00382582821.QUB file: 'RO-C-VIRTIS-2-ESC1-MTP013-V2.0/CATALOG/DATASET.CAT' --> ABSTRACT_DESC: For L2, please mention brief statement of why versioning from V1.0 data set. I believe it was adding a missing row of data? --> CITATION_DESC: For L2, The DATA_SET_ID part says V3.0, but this is V2.0. Also the year needs to be updated from 2017 to 2019, assuming that that is when the data will be released. --> DATA_SET_DESC: For L2, need to add a Version History section and populate it with the major changes between current version and previous version. file: 'RO-C-VIRTIS-2-ESC1-MTP013-V2.0/VOLDESC.CAT' --> VOLUME_VERSION_ID: L2 needs to be updated from "VERSION 1" to "VERSION 2". --> DESCRIPTION: For L2, suggest specifying what kind of data (raw/calibrated/derived/etc) to distinguish it from other MTP013 data sets. =============================================== Errors for: RO-C-VIRTIS-3-ESC1-MTP013-V3.0 file: 'RO-C-VIRTIS-3-ESC1-MTP013-V3.0/CATALOG/DATASET.CAT' --> DATA_SET_TERSE_DESC: For L3, typo "ESCORT<>1" to "ESCORT 1" --> DATA_SET_DESC: For L3, need to update Version History section to include changes in V3.0. Currently only V2.0 changes are listed. file: 'RO-C-VIRTIS-3-ESC1-MTP013-V3.0/DATA/*/*/VIRTIS_M*/*.CAL' --> CORE_ITEM_TYPE: The value "REAL" is not valid. It should be "IEEE_REAL" as was fixed in the VIRTIS_H data. =============================================== Errors for: RO-VIRTIS-5-V1.0 The DATA_SET_ID for RO-VIRTIS-5-V1.0 is invalid. Please include a target part and description. "RO-[target_abbreviation(s)]-VIRTIS-5-[description]-V1.0". Ask PSA or PDS personnel for assistance in generating an ID. file: 'RO-VIRTIS-5-V1.0/AAREADME.TXT' --> This file describes QUB files and IMG files, but none are found here in. Is something missing from the data set, does this text need to be updated? file: 'RO-VIRTIS-5-V1.0/CATALOG/DATASET.CAT' --> ABSTRACT_DESC: For L5, need to rewrite this abstract. It states only that the data set has 'calibrated' data from 'all the mission phases.' Please define what you mean by calibrated. Do you actually mean derived data? What kind of data? Maps? I see Albedo, Band Depth, Sepctral Slope, and Water Ice abundances maps. It would be good to mention this. Likewise, this data set only contains a fraction of the 67P time frame, not the entire mission. --> CITATION_DESC: For L5, this citation is for the wrong data set and the year is from before the data set was produced. Please correct. --> DATA_SET_DESC: For L5, the "Data Set Overview" and "Processing" sections do not describe the current data set, but another. It would be good to mention that there are Albedo, Band Depth, Sepctral Slope, Water Ice abundances, etc maps. --> CONFIDENCE_LEVEL_NOTE: For L5, this section is moot since there are not DATA_QUALITY_FLAG values in the data. Please rewrite this section. --> TARGET_NAME: For L5, though only 67P data is currently present in the data set, if truly encompasses the entire mission, please include the other targets when data for those targets are added. directory: 'RO-VIRTIS-5-V1.0/DATA/' --> The CATALOG/DATASET.CAT file implies that there is data from March 2004 thru end of mission, but there are only data products for Aug 2014 thru May 2015. Where is the other data? --> Where is the VIRTIS_H data mentioned in the EAICD? --> Assuming that this data set does not contain all data at this time, you should consider splitting the VIRTIS_M directory since it may be overwhelming to see all data in a single place. You could split by type of data or by mission phase, or some other logical split. files: 'RO-VIRTIS-5-V1.0/DATA/MAP/VIRTIS_M/*.LBL' --> Note I looked at one example of each type (AL,BA,BC,BD,etc) from M006 assuming each type should have the same or similar issues. --> Several keywords value are required to be a real number, not text. Drop the double quotes to fix. Affected keywords: MAXIMUM_LATITUDE, MINIMUM_LATITUDE, EASTERNMOST_LONGITUDE, WESTERNMOST_LONGITUDE = "360" --> Some maps extend over multiple MTPs (ex: BC02_GLB_M011_V01.*) or a single mission phase, instead of a single MTP as defined by the EAICD. --> It might be best to standardize the data formats for each map type since they all very similar. Currently there are slightly different record lengths, column lengths. I suggest this since there are currently multiple problems in the labels due to the subtle differences between the maps. --> --> AL*: RECORD_BYTES '26' => '27'; --> --> BA*: ROW_BYTES '27' => '26'; Col 1 BYTES '6' => '7'; Col 2 BYTES '5' => '7'; --> --> BA*: Col 3 does not match data. Either data needs another byte or these need to be fixed in label: BYTES '9' => '8', FORMAT 'F9.7' => 'F8.6', MISSING_CONSTANT '9.9999999' => '9.999999'; --> --> BC*: RECORD_BYTES '25' => '27'; Col 1 BYTES '6' => '7'; Col 2 BYTES '5' => '7'; Col 3 BYTES '7' => '9' --> --> BD*: RECORD_BYTES '25' => '27'; Col 1 BYTES '6' => '7'; Col 2 BYTES '5' => '7'; Col 3 BYTES '7' => '9' --> --> SL*: RECORD_BYTES '25' => '27'; Col 1 BYTES '6' => '7'; Col 2 BYTES '5' => '7'; Col 3 BYTES '7' => '9' --> --> WI*: ROW_BYTES '27' => '26'; Col 1 BYTES '6' => '7'; Col 2 BYTES '5' => '7'; Col 3 BYTES '7' => '9' --> --> WI*: Col 3 does not match data. Either data needs another byte or these need to be fixed in label: BYTES '9' => '8', FORMAT 'F9.7' => 'F8.6', MISSING_CONSTANT '9.9999999' => '9.999999'; files: 'RO-VIRTIS-5-V1.0/DATA/MAP/VIRTIS_M/*.TAB' --> Note I looked at one example of each type (AL,BA,BC,BD,etc) from M006 assuming each type should have the same or similar issues. --> The last row of data is missing the end of line characters for some files (ex: AL01_GLB_M006_V01.TAB) --> Col 3 value '*********' should be replaced with the missing constant I believe. (ex: BD01_GLB_M007_V01.TAB) --> BA*: Col 3 data does not have decimal place aligned (at the same byte), which is required. --> BA*: I believe Col3 is missing its last byte. The column and missing constant value is only 8 bytes long but per label it should be 9 bytes. --> WI*: Col 3 data does not have decimal place aligned (at the same byte), which is required. file: 'RO-VIRTIS-5-V1.0/DOCUMENT/RO_VIRTIS_MAP_EAICD.[PDF,ASC]' --> Sec 2.3: Mentions they cannot use long/lat for this odd shaped comet, but the data is in that format. They talk about a future version of the data set being facet based, but it would be nice to see that now. --> Sec 3.1.3 mentions VIRTIS_H data, but 3.2.5.12 states VIRTSIS_H directory is not being used. Is this something that will be included later? --> Tbl 3.5: Target values should be uppercase. --> Sec 3.1.4 after Tbl 3-5: Some maps extend over multiple MTPs (ex: BC02_GLB_M011_V01.*) or a single mission phase, instead of a single MTP as defined by the EAICD. This should be accounted for here.