[ERROR] means that there is an error that needs to be fixed. [WARN] means that there may be an error or that there is an error that may be ignored. [DISCUSS] should be brought in the review for discussion. =============================================== NOTE: (1) Edited delivery from Maud on 2016-01-19. (2) Contains updated CIVA instrument catalog file. =============================================== Datasets Validated: RL-C-CIVA-2-FSS-V1.0 RL-C-CIVA-3-FSS-V1.0 RL-CAL-CIVA-2-PDCS-V1.0 RL-CAL-CIVA-2-PHC-V1.0 RL-CAL-CIVA-3-PDCS-V1.0 RL-CAL-CIVA-3-PHC-V1.0 =============================================== Errors for: GLOBAL (all datasets) [ERROR] files: ' ... /*.PDF' --> Ensure that all PDF files should be in PDF/A-1a or PDF/A-1b format. [ERROR] file: 'CALIB/CALINFO.TXT' --> typo: For the non-FSS data sets, the last line should be corrected. "CIVA_CALIBRATION_DESC.TXT" => "CIVA_CALIBRATION_DESC.ASC". [SUGGEST] files: 'CALIB/CIVAP/COEFF_PHOTO_UNIT_*.LBL' --> Suggest adding FORMAT keyword to column 1. [ERROR] files: mission wide catalog files in 'CATALOG/' --> Ensure that the mission, reference, and instrument host catalog files are up to date. Some phases are up to date, but others are not. [ERROR] file: 'CATALOG/DATASET.CAT' --> [DISCUSS] The DATA_SET_DESC is very very sparse and NOT unique to a data set. Should it be expanded? For example to say briefly what CIVAM and CIVAP data are and when they are or are not included. --> typo: First word in Coordinate System section of DATA_SET_DESC should be changed from 'he' to 'The'. [SUGGEST] file: 'CATALOG/DATASET.CAT' --> Suggest adding mention to ABSTRACT_DESC when you have CIVAM data or not. [ERROR] file: 'CATALOG/INST.CAT' --> FSS has a better copy of this file than is found in other phases. Please replace with the most up to date copy. There is no reason this file should be different between phases. [ERROR] file: 'DATA/*/*.IMG' --> [DISCUSS] For the geometry keywords (SC_TARGET_POSITION_VECTOR, SC_TARGET_VELOCITY_VECTOR, SPACECRAFT_ALTITUDE, SUB_SPACECRAFT_LATITUDE, SUB_SPACECRAFT_LONGITUDE) are specified as "N/A", but is that true? Would the value of "0" or "UNK" more appropriate? Would it be different for comet vs calibration targeted data sets? --> [DISCUSS] Why is the EXPOSURE_DURATION_DESC keyword commented out? It is not a defined PDS3 keyword, but it could easily be added to Rosetta mission dictionary. --> [DISCUSS] Why is the FOCAL_PLANE_TEMPERATURE_DESC keyword commented out? It is not a defined PDS3 keyword, but it could easily be added to Rosetta mission dictionary. --> [DISCUSS] FOCAL_PLANE_TEMPERATURE has a series of values that are defined in FOCAL_PLANE_TEMPERATURE_DESC. Is this a misuse of this keyword? --> [DISCUSS] FOCAL_PLANE_TEMPERATURE has values of 999.99 which appear to be signifying an invalid value, but no where is this defined. --> [DISCUSS] There are several keywords that have a series of values (one for each camera), but is only defined as being such for one of those keywords. It would be good to have a general note added to describe what is going on. --> --> Not described: INST_CMPRS_RATE, GAIN_NUMBER --> --> Already described: INSTRUMENT_MODE_ID, EXPOSURE_DURATION --> [DISCUSS] Strongly suggest adding: LINE_DISPLAY_DIRECTION and SAMPLE_DISPLAY_DIRECTION. [SUGGEST] file: 'DATA/*/*.IMG' --> Suggest adding FORMAT fields to all TIME and CHARACTER fields. They should follow the pattern FORMAT = "A###" where "###" is the number of bytes. --> Suggest adding FORMAT fields to all ASCII_INTEGER fields. They should follow the pattern FORMAT = "I###" where "###" is the number of bytes. [ERROR] file: 'DOCUMENT/CIVA_CALIBRATION_DESC.ASC' --> Why is this file very different (and in ways that should not be) between level 2 and 3 and between some phases? (Used FSS level 2 for basis of comparison) [ERROR] file: 'INDEX/BROWSE_INDEX.LBL' --> "BROWSE_INDEX_TABLE" does not contain required element "INDEX_TYPE". [ERROR] file: 'VOLDESC.CAT' --> The value for VOLUMES is not accurate. VOLUMES should be the number of volumes contained in the VOLUME_SET_ID. Note that this team is also varying the VOLUME_SET_ID so this value may be 1. =============================================== Errors for: RL-CAL-CIVA-2-PHC-V1.0 [ERROR] file: 'DATA/CIVAM/MI/CIVA_FS2_140421052109_8_B.QUB' --> The value, "RAW_DATA_NUMBER", for "CORE_NAME" is only valid when changed to "RAW DATA NUMBER". --> Is the calibration for this file really described in this file: --> --> ^INSTRUMENT_CALIBRATION_DESC = "CIVA_CALIBRATION_DESC.ASC" --> [DISCUSS] Why is the EXPOSURE_DURATION_DESC keyword commented out? It is not a defined PDS3 keyword, but it could easily be added to Rosetta mission dictionary. --> [DISCUSS] Why is the FOCAL_PLANE_TEMPERATURE_DESC keyword commented out? It is not a defined PDS3 keyword, but it could easily be added to Rosetta mission dictionary. --> [DISCUSS] FOCAL_PLANE_TEMPERATURE has a series of values that are defined in FOCAL_PLANE_TEMPERATURE_DESC. Is this a misuse of this keyword? --> [DISCUSS] ROSETTA:SPECTROMETER_TEMPERATURE has a series of values that are defined in SPECTROMETER_TEMPERATURE_DESC. Is this a misuse of this keyword? --> [DISCUSS] There are several keywords that have a series of values (one for each camera), but is only defined as being such for one of those keywords. It would be good to have a general note added to describe what is going on. --> --> Not described: INST_CMPRS_RATE, GAIN_NUMBER --> --> Already described: INSTRUMENT_MODE_ID, EXPOSURE_DURATION, ROSETTA:SPECTROMETER_TEMPERATURE [SUGGEST] file: 'DATA/CIVAM/MI/CIVA_FS2_140421052109_8_B.QUB' --> Suggest adding FORMAT fields to all TIME and CHARACTER fields. They should follow the pattern FORMAT = "A###" where "###" is the number of bytes. --> Suggest adding FORMAT fields to all ASCII_INTEGER fields. They should follow the pattern FORMAT = "I###" where "###" is the number of bytes. =============================================== Errors for: RL-CAL-CIVA-3-PHC-V1.0 [ERROR] file: 'VOLDESC.CAT' --> The VOLUME_VERSION_ID should be changed from "VERSION 3" to "VERSION 1". [WARN] directory: 'DATA/' --> [DISCUSS] Why is there no CIVAM data when there was in level 2 data set?