Listed below are the liens/RIDs that were found at the PDS/PSA February 2016 review of the Prelanding thru Escort 1 phases of the Rosetta mission. Even though this particular data set may have not participated in the review, it uses the same pipeline and so the liens likely apply here as well. Please take note that some issues may be resolved, while others are not. If any other issues are discovered please let the PDS-SBN know. It is expected that a fully lien resolved version will be produced during post mission ops and archived with an incremented data set version number. 1)Reference ID (RID): RO-AR-RID-VIRTIS-101-FS Dataset: All VIRTIS Location: - Title: Missing Solar Flux Description: The calibrated data are provided in RADIANCE (W/m**2/sr/micron) but it would be more interesting to have REFLECTANCE. In order to easily estimate it, the archive should include the expected solar flux in the wavelength channel (W/m**2/micron) Proposed solution by reviewer: Solution 1 : Solar flux for each calibrated CAL as an additional suffix plane Solution 2 : Solar flux at 1 UA in the calibration /CALIB/ directory, then the conversion can be done by the user Review board discussion outcome and Instrument team response: Solar flux will be included in the calib directory. Stephan says it is an error from Virtis side. 2)Reference ID (RID): RO-AR-RID-VIRTIS-102-FS Dataset: RO-C-VIRTIS-3-PRL-MTP009-V1.0 and RO-C-VIRTIS-2-PRL-MTP009-V1.0 Location: /DATA/*/CAL/VIRTI_M_*/* Title: Wavelength in wrong unit Description: Units in the suffix are stated to be in microns but they are obvously in nanometers (values: 231-1043 for first row, 1.89-2.38-1 for the second row) Proposed solution by reviewer: Please either change the units in the label or the values in the qubes Review board discussion outcome and Instrument team response: a mistake in the label only for the M calibrated files 3)Reference ID (RID): RO-AR-RID-VIRTIS-103-FS Dataset: RO-C-VIRTIS-3-PRL-MTP009-V1.0 and RO-C-VIRTIS-2-PRL-MTP009-V1.0 Location: /INDEX/INDEX.* Title: Index is missing Description: INDEX.TAB and INDEX.LBL are missing in the archive Proposed solution by reviewer: Please add an index of the qubes Review board discussion outcome and Instrument team response: will be added 4)Reference ID (RID): RO-AR-RID-VIRTIS-104-FS Dataset: All VIRTIS Location: /CALIB/VIRTIS_PDS_IDL_SW_MANUAL.PDF Title: Some Calibration Files are not stated to be open by the IDL software Description: Description of how reading the calibration file is not explicit. Especially the title "How to read other (non-Virtis) PDS files?" non-VIRTIS is very confusing. Please add explicitely how to read the calibration file. Proposed solution by reviewer: Please improve the documentation Review board discussion outcome and Instrument team response: Documentation to be checked. If it is rejected Calib files should be read with v_readpds 5)Reference ID (RID): RO-AR-RID-VIRTIS-105-FS Dataset: RO-C-VIRTIS-3-PRL-MTP009-V1.0 Location: RO-C-VIRTIS-3-PRL-MTP009-V1.0/DATA/STP028/GEO Title: GEO at the wrong place Description: RO-C-VIRTIS-3-PRL-MTP009-V1.0/DATA/STP028/GEO/T1_00374511907.GEO shoud be at RO-C-VIRTIS-3-PRL-MTP009-V1.0/DATA/STP028/GEO/VIRTIS_H/T1_00374511907.GEO Proposed solution by reviewer: Please move it ! Review board discussion outcome and Instrument team response: agree to correct 6)Reference ID (RID): RO-AR-RID-VIRTIS-106-FS Dataset: RO-C-VIRTIS-3-PRL-MTP006-V1.0 and RO-C-VIRTIS-3-PRL-MTP009-V1.0 Location: AAREADME.TXT Title: Wrong file name Description: In the file AAREADME.TXT (line 60-66), the data files are incorrecly named, should be *.CAL or .GEO instead of .QUB Proposed solution by reviewer: Replace it Review board discussion outcome and Instrument team response: - 7)Reference ID (RID): RO-AR-RID-VIRTIS-107-FS Dataset: All VIRTIS Location: Many document *.TXT and *.PDF Title: Wrong VIRTIS instrument Description: In many document, VIRTIS Vex is still present Proposed solution by reviewer: Replace by VIRTIS Rosetta Review board discussion outcome and Instrument team response: - 8)Reference ID (RID): RO-AR-RID-VIRTIS-108-PSA Dataset: ALL Location: ALL Title: ALL Description: Make sure all RIDs form PSA and PDS are resolved. Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: - 9)Reference ID (RID): RO-AR-RID-VIRTIS-101-SB Dataset: MTP009-stp025 Location: geo/virtis_h Title: Distances &elevations units m Description: In Table 3 of "virtis_geometry.pdf" (pp. 11-12), IDL plane#17 is surface elevation, wrt "Digital Terrain Model" which is taken to mean the reference ellipsoid. In this way negative values are ok (e.g. -162 to -561 m for geo/virtis_h/t1_00373272493.geo), on 2014-Oct-30. Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: Not discussed with team 10)Reference ID (RID): RO-AR-RID-VIRTIS-102-SB Dataset: MTP009-stp025 Location: geo/virtis_m_vis Title: "IDL plane#18 is s/c slant distance from surface ellipsoid (varies from 25.475 to 26.414 km). This is ok, however for geo/virtis_m_vis/v1_00373274734.geo, plane#18 varies from 27.181 to 27.267 km, while plane#17 varies from 100.822 to 100.386 km. Question: How can surface elevations of ~100 km exist on such a small nucleus?" Description: This needs to be checked for all files, or Table 3 should be modified separately for -H and -M files Proposed solution by reviewer: Needs some more descriptive text in document or pointers from table to text & figure Review board discussion outcome and Instrument team response: Multiple uses of these lines depending on whether the the LOS intersects the surface or not - large offset for elevation when LOS is off the nucleus. Explained elsewhere in the documentation 11)Reference ID (RID): RO-AR-RID-VIRTIS-103-SB Dataset: MTP009-stp025 Location: cal/virtis_h Title: Radiance Uncertainties Description: In 't1_00373272493.cal', sigma_radiance = 0.00000 for all 448 line spectra in this file. This is not physical, either characterize in terms of detector and/or signal noise, or denote by a numerical flag (e.g., -9999). Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: will insert a flag to note that it is not calculated 12)Reference ID (RID): RO-AR-RID-VIRTIS-104-SB Dataset: MTP006-stp011 Location: cal/virtis_m_vis Title: - Description: In 'v1_00365574167.cal', sigma_radiance seems too large, perhaps by a factor of 10 based on "noise" level in a spectral extract (e.g., in the line spectrum represented by row 212 in frame #50), and therefore the implied SNR = 1-2, however it is clearly much higher than that. Proposed solution by reviewer: This needs to be checked for the dataset as a whole. Review board discussion outcome and Instrument team response: probably due to significant variation of noise across spectrum, ie varying with signal strength; will check that all available info is in archive 13)Reference ID (RID): RO-AR-RID-VIRTIS-105-SB Dataset: MTP009-stp025 Location: cal/virtis_h Title: - Description: Consistency of lambda cal in regions of overlapping lambda among adjacent orders. Need to understand how wavelength calibration is parsed across orders. May only be a minor concern, I'm not sure…meaning this may be a more minor than major concern. Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: Calibration procedure is still maturing - ok with reviewer 14)Reference ID (RID): RO-AR-RID-VIRTIS-106-SB Dataset: MTP009-stp025 Location: cal/virtis_h Title: dark subtraction:role of .drk files Description: I plotted line spectra separately for each order (1-8) for a .cal file. So order1 was 0:431 (IDL format). I noticed intermittent "spikes" that I took to be hot pixels. So I plotted similarly for the corresponding .drk spectrum, however the drk signal was much higher (10**4, versus ~0.1 for .cal). Perhaps there is a difference in calibration? In other words, when I subtracted the drk spectrum from its corresponding cal spectrum I saw highly negative numbers. Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: Dark very sensitive for H & requires interpolation in time and much larger than the actual signal 15)Reference ID (RID): RO-AR-RID-VIRTIS-107-SB Dataset: ALL Location: ALL Title: Consistency independent of reading s/w Description: General: The PDS manifest indices are missing. Are consistent values obtained using the PDS-3 reader, versus the virtuspds IDL package? Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: - 16)Reference ID (RID): RO-AR-RID-VIRTIS-101-MB Dataset: ALL Location: ALL Title: Technical PSA RIDs Description: Please correct all PSA RIDs. Word Document provided to the team Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: - 17)Reference ID (RID): RO-AR-RID-VIRTIS-101-SBN Dataset: ALL Location: ALL Title: Techincal PDS RIDS Description: Please correct all PDS RIDs. virtis_sbn.txt provided to the team Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: - 18)Reference ID (RID): RO-AR-RID-VIRTIS-102-SBN Dataset: ALL Location: ALL Title: Editorial from US reviewer Description: Please, correct editorial points raised by US reviewer described in the file VIRTIS_typos_diSanti.pdf Proposed solution by reviewer: - Review board discussion outcome and Instrument team response: - 19)Reference ID (RID): ro-c-virtis-101-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: calib/deadpixelmap.lb Title: Inconsistent DATA_SET_NAME Description: "DATA_SET_NAME = ""ROSETTA-ORBITER 67P VIRTIS 3 PRELANDING MTP006 V1.0"" does not match catalog/dataset.cat's (near the end) DATA_SET_NAME = ""ROSETTA-ORBITER 67P VIRTIS 3 PRELANDING MTP009 V1.0""" Proposed solution by reviewer: correct Review board discussion outcome and Instrument team response: - 20)Reference ID (RID): ro-c-virtis-102-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: calib/virtis_m_*_resp_10_v1.lbl Title: Incorrect BYTE count Description: "This is not required, but keyword INSTRUMENT_ID or _NAME would be useful. - Please change RECORD_BYTES = 1 FILE_RECORDS = 864 to RECORD_BYTES = 3456 FILE_RECORDS = 256" Proposed solution by reviewer: "1. Add keyword INSTRUMENT_NAME (or INSTRUMENT_ID). 2. Replace with correct count" Review board discussion outcome and Instrument team response: - 21)Reference ID (RID): ro-c-virtis-103-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: data/.../* Title: Incorrect value and format Description: "The values are illegal: DECLINATION = -999.999 RIGHT_ASCENSION = -999.999 FYI, ""N/A"", ""UNK"", and ""NULL"" are legal values for any type. - PROCESSING_LEVEL_ID's value needs quotes, i.e. change PROCESSING_LEVEL_ID = 2 (or 3) to PROCESSING_LEVEL_ID = ""2"" (or ""3"") - INSTRUMENT_MODE_ID's value needs quotes - DATA_QUALITY_ID's value needs quotes - Some files (the IR?) have TELEMETRY_SOURCE_ID = VIRTIS_EGSE_3 while the rest have TELEMETRY_SOURCE_ID = VIRTIS_EGSE3 If that's meant to be the same source, please always use one. - These values are legal, but meaningful values would be preferable COORDINATE_SYSTEM_ID = ""-1000012000"" COORDINATE_SYSTEM_NAME = ""67P/C-G_CK"" - If these are meant to be Standard ISIS Qubes, these required keywords are missing: BAND_BIN_CENTER, BAND_BIN_UNIT, BAND_BIN_ORIGINAL_BAND" Proposed solution by reviewer: "see description Review board discussion outcome and Instrument team response: Quote have been discussed already. Check the software value. Use correct vallues for declination and Right_Ascension 22)Reference ID (RID): ro-c-virtis-104-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: data/*/cal/.../* Title: Incorrect value and format Description: "The value is illegal. It should be PC_REAL or IEEE_REAL CORE_ITEM_TYPE = REAL LINE_SUFFIX_ITEM_TYPE = REAL is also an illegal value - Since the type of CORE_ITEM is REAL (presumably IEEE_REAL) these CORE_VALID_MINIMUM = -999 CORE_NULL = -1004 CORE_LOW_REPR_SATURATION = -1003 CORE_LOW_INSTR_SATURATION = -1002 CORE_HIGH_REPR_SATURATION = -1001 CORE_HIGH_INSTR_SATURATION = -1000 should be real values, i.e. -999.0, -1004.0, ... Please inform EN what values will be used so that EN can modify the data dictionary. - Values, except for descriptive keywords, should be upper case. CORE_UNIT = ""W/m**2/sr/micron"" It would be mildly preferable to use the existing value CORE_UNIT = ""WATT*M**-2*SR**-1*UM**-1"" - These keywords are unknwon (i.e. illegal) FRAME_PARAMETER_UNIT INSTRUMENT_TEMPERATURE_UNIT The DAWN mission added keywords DAWN:FRAME_PARAMETER_UNIT and DAWN:INSTRUMENT_TEMPERATURE_UNIT suggest to use ROSETTA:…" Proposed solution by reviewer: see description Review board discussion outcome and Instrument team response: - 23)Reference ID (RID): ro-c-virtis-105-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: data/*/cal/virtis_h/.../* Title: SUFFIX_BYTES should = 4 "SUFFIX_BYTES = 2 is illegal. Description: PDS Standards, Section A.23.1, says SUFFIX_BYTES for a QUBE is always 4. This does not match the characterization of SCET in the ICD: SUFFIX_ITEMS = (3,0,0) BAND_SUFFIX_NAME = ""SCET"" BAND_SUFFIX_UNIT = DIMENSIONLESS BAND_SUFFIX_ITEM_BYTES = 2 BAND_SUFFIX_ITEM_TYPE = MSB_UNSIGNED_INTEGER BAND_SUFFIX_BASE = 0.0 BAND_SUFFIX_MULTIPLIER = 1.0 Since SUFFIX_ITEMS = 3, BAND_SUFFIX_* must correspondingly have 3 values. This would be more accurate: SUFFIX_ITEMS = (3,0,0) BAND_SUFFIX_NAME = (SCET_HIGH_WORD, SCET_LOW_WORD, SCET_FRACTION) BAND_SUFFIX_UNIT = (DIMENSIONLESS, DIMENSIONLESS, DIMENSIONLESS) BAND_SUFFIX_ITEM_BYTES = (2,2,2) BAND_SUFFIX_ITEM_TYPE = (MSB_UNSIGNED_INTEGER, MSB_UNSIGNED_INTEGER, MSB_UNSIGNED_INTEGER) BAND_SUFFIX_BASE = (0.0, 0.0, 0.0) BAND_SUFFIX_MULTIPLIER = (1.0, 1.0, 1.0)" Proposed solution by reviewer: In the actual data, expand each of the three suffix planes to 4 bytes, then label them correctly in the metadata. Review board discussion outcome and Instrument team response: Waiver from previous review 24)Reference ID (RID): ro-c-virtis-107-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: data/*/cal/virtis_m*/.../* Title: Incorrect side plane value Description: "For virtis_h, the sideplane of SCETs for BAND was 3*2 bytes. How can virtis_m be 1*2? AXIS_NAME = (BAND,SAMPLE,LINE) SUFFIX_BYTES = 4 SUFFIX_ITEMS = (1,0,3) BAND_SUFFIX_NAME = ""SCET"" BAND_SUFFIX_ITEM_BYTES = 2 In the first file, the 4 bytes: after row 1 of data = 0x00001638 after row 2 of data = 0xffffadbe after row 3 of data = 0x00002b92 after row 4 of data = 0x00000000 How does that map into an SCET? We suspect the real value of SCET is 0x1638adbe2b92" Proposed solution by reviewer: "Change the 1 band suffix plane to 3 and have each suffix plane hold part of SCET. For the metadata, SUFFIX_ITEMS = (3,0,3) BAND_SUFFIX_ITEM_BYTES = (4,4,4) BAND_SUFFIX_NAME = (SCET_HIGH_WORD, SCET_LOW_WORD, SCET_FRACTION)" Review board discussion outcome and Instrument team response: - 25)Reference ID (RID): ro-c-virtis-108-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: data/*/cal/.../*.cal Title: Suggestion Description: "This is legal but should be more descriptive: INST_CMPRS_NAME = REVERSIBLE For examples, the current values in the dictionary are: ""BLOCK TRUNCATION CODING (BCT)"", ""DISCRETE COSINE TRANSFORM (DCT)"", ... " Proposed solution by reviewer: Consider Review board discussion outcome and Instrument team response: - 26)Reference ID (RID): ro-c-virtis-110-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: data/stp028 Title: Delete or fill in blank directory Description: "In case this is accidental, this directory is not populated like the rest, including a blank sudirectory" Proposed solution by reviewer: double check Review board discussion outcome and Instrument team response: - 27)Reference ID (RID): ro-c-virtis-111-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: document/ro_virtis_eaicd.pdf Title: ro_virtis_eaicd PDF Description: "section 3.4.3.12: the directory structure in the review does not match the structure in this document. - section 4.2.1.5: ""It should be noted that the value of the keyword SUFFIX_BYTES is 2 instead of 4, as it would be required for compatibility with ISIS software: we did not follow this convention to avoid a large wasting of space."" As mentioned above, this must be 4. The waste of space is maybe 1%, e.g. the width of the cube in the first file (t1_00372813791.cal) would change from 3456*4 + 3*2 to 3456*4 + 3*4 Maybe the Level 2 data is different? - Appendix C: The rows with DATA_SET_ID and _NAME do not contain the values in this review." Proposed solution by reviewer: see description Review board discussion outcome and Instrument team response: - 28)Reference ID (RID): ro-c-virtis-112-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: geometry/geominfo.txt Title: Unknown keyword and incorrect format Description: "RELEASE_ID = 0001 needs quotes around the value, i.e. RELEASE_ID = ""0001"" - This is an unknown keyword REVISION_ID = 0000 Perhaps use LABEL_VERSION_ID instead" Proposed solution by reviewer: see description Review board discussion outcome and Instrument team response: Remove all occurrences of REVISION and RELEASE_ID 29)Reference ID (RID): ro-c-virtis-113-RE Dataset: ro-c-virtis-3-prl-mtp009-v1.0 Location: index/index.* Title: Missing index.* Description: These files are required but missing Proposed solution by reviewer: include required files Review board discussion outcome and Instrument team response: -