PDS lead review of Rosetta HK data April 2020 ============================================= Reviewers: Mamoutkine: MUST-PDS-M-XXX Lawton: MUST-PDS-L-XXX Tilden Barnes: MUST-PDS-TB-XXX ============================== MUST-PDS-M-001 Common to all 11 datasets: AAREADME.TXT The data presented in this data set covers the entire Rosetta mission from March 2014 through to September 2016. It should be 2004. ------------ --> Recommended Solution (from PSA): Will fix this. ============================== MUST-PDS-M-002 Common to all 11 datasets: AAREADME.TXT I found it at least strange, that aareadme.txt file at the very top of the dataset is a pure template. It has nothing to do with the specific dataset: This dataset contains key selected housekeeping parameters from the Rosetta spacecraft subsystems as specified in the DATASET.CAT. The BROWSE data provided are overview plots of selected parameters from the DATA directory... It’s very convenient for the documentation but gives you NO CLUE what data to expect. And this is the first document that anybody will open in the dataset. ------------ --> Recommended Solution (from PSA): Ask PDS to reject this one. If not, will provide some short data set specific text. ============================== MUST-PDS-M-005 RO-X-HK-3-TCS-V1.0/BROWSE/ Browse directory has a summary graphical files (*.png) for the whole year of data. But the selection of parameters appeared to be very limited and the logic of their selection is not explained in the documentation. For example, RO-X-HK-3-TCS-V1.0\BROWSE\RPC_BOOM_TEMP_2016.PNG The whole browse directory has plots only for rpc_boom_temp. Any explanation why rpc_boom_temp? Why other parameters does not have plots? There are 13 other parameters besides rpc_boom_temp. ------------ --> Recommended Solution (from PSA): Will add some text to describe the logic behind the selection of data for TCS BROWSE, similar to other data sets. ============================== MUST-PDS-M-006 BROWSE/ directory for the following data sets: RO-X-HK-3-ANTENNASTATUS-V1.0, RO-X-HK-3-AOCGEN-V1.0, RO-X-HK-3-EDAC-V1.0, RO-X-HK-3-HGAAPM-V1.0, RO-X-HK-3-IMP-V1.0, RO-X-HK-3-OCMRCS-V1.0, RO-X-HK-3-RWL-V1.0, RO-X-HK-3-SOLARARRAY-V1.0, RO-X-HK-3-STRARTRACKER-V1.0 Please check the titles and units for the plots in the BROWSE/ directory of each of the data sets listed. Many have have no axis-titles and/or units. The best place for units would be one time in the axis title, rather than in legend for each parameter. A few specific examples: - For IMP, it looks like gyro_cons_err has no units at all. - Also for IMP, the unit in IMP_RATE is Dg/S. Most likely it’s deg/s (degree per second). It would be appropriate to use a proper spelling of units. - For OCMRCS, in rcs_cum_thrust_1_8, rcs_cum_thrust_9_12 label files there is unknown unit “gr”. Probably should be used “g” (gram). - For RWL, it looks like rwl_wheel_direction and has no units at all. - For STRARTRACKER, STR A mean background and standard deviation have no units and explanation. ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. ============================== MUST-PDS-M-007 BROWSE/ directory for the following data sets: RO-X-HK-3-EDAC-V1.0, RO-X-HK-3-HGAAPM-V1.0, RO-X-HK-3-STRARTRACKER-V1.0 For these browse products, the same parameters have different color codes on plots for different quarters. Please unify this. Some examples below. - In EDAC, BTSTP: EDAC counter could be a red, green, or blue line on different plots. - In HGAAPM, plots for different time frames (years and quarters) but for the same parameters (like APME: Measured Elev, APME: Measured Azi) have different color codes. - In STRARTRACKER, plots in str_a/b_ang_velocity for different time frames (years and quarters) but for the same parameters (like STR A angular velocity X, STR A angular velocity Y, STR A angular velocity Z) have different color codes. ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. ============================== MUST-PDS-M-008 Additional data set specific BROWSE issues / questions. SOLAR_ARRAY: - power_unit_pri_curr and power_unit_sec_volt plots are too overlapping. The alternative should be considered. STRARTRACKER: (See also MUST-PDS-M-XXX for associated DATA and EXTRAS issues) - Wrong units are used for angular velocity in /BROWSE plots: “dg/s” should be changed “deg/s”. - STR A mean background and standard deviation have no units and explanation. - Plots str_a_b_track_stars should not have labels like 1.25 or 2.75 or 3.5 (number of stars). Labels should be reconsidered for integer only numbers. - STR A op modes - please provide a description ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. ============================== MUST-PDS-M-009 RO-X-HK-3-ANTENNASTATUS-V1.0 questions on the DATA content. Data content seems to be too simple. For example, trsp_1_2_rx_bitrate_selection was chosen to browse quarterly plots as carefully chosen as being of most interest to have as thumbnails to help browse through the data sets and select data and periods of interest. But, for example, for Quarter3-2016 for parameters nttd1020 and nttd1020a we have integer value 0 (zero) for ALL time slots; for nttd2020 - value 4 for ALL time slots, for nttd202a - value 1 for ALL time slots. Two questions: 1) Why all zeros or all ones or all fours have the “most interest” in this dataset? 2) Why there is no explanation of what these 0,1 or 4 means in *info.txt or *.lbl files? The only brief explanation is found at *.LBL file: "This table gives the time profile of the TRSP1 RX Bit Rate parameter " Is the 0 bit rate normal for the extended time frame? In what units they report bit rate: bps, Mbps, other? Other examples of data: hga_mga_x_band_status: all 1 (ones) for all time slots. LBL explanation: “This table gives the time profile of the X BAND High GA parameter " s_band_tx_1_2_status: all 18 (eighteens) for all time slots. LBL explanation: "This table gives the time profile of the TX 2 S BAND Antenna parameter " More details would be recommended for the description of each data parameter (including units). Probably the best place - dataset.cat. ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. ============================== MUST-PDS-M-010 RO-X-HK-3-AOCGEN-V1.0 data units and description missing. CURRENT_AOC_MODE, WOL_MANAGER DATA and EXTRAS LBL files does not provide the unit of value and valuable description of the data. ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. This may need an update to the LBL template for AOCGEN, and a corresponding re-run of the pipeline. ============================== MUST-PDS-M-011 RO-X-HK-3-EDAC-V1.0 typo in DATASET.CAT. DATASET.CAT has typo at “Dataset Overview” - “sudirectory”. ------------ --> Recommended Solution (from PSA): Will fix this typo. ============================== MUST-PDS-M-012 RO-X-HK-3-HGAAPM-V1.0 data units definition and question. In the DATA/EXTRAS directories, HGA_A_DISP_ERR_AZ_EL and HGA_B_DISP_ERR_AZ_EL use technical jargon / shortcuts in their label files: "This table gives the time profile of the APME B Dispment Error Az parameter " The description field has enough space to use plain English full-size words: displacement, azimuth. Please correct. Why the absolute angle error and displacement in azimuth elevation measured in radiance, but the actual value of azimuth elevation measured in degree? Should it be in the same unit? For example, label files of HGA_A_ABSANG_ERR_AZ_EL and HGA_EARTH_AZ_ELEV. ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. This may need an update to the LBL template for HGAAPM, and a corresponding re-run of the pipeline. ============================== MUST-PDS-M-013 RO-X-HK-3-IMP-V1.0 DATA (and EXTRAS) questions. - The unit in IMP_RATE in original ASCII (/DATA) and binary (/EXTRAS) label files is Dg/S. Most likely it’s deg/s (degree per second). It would be appropriate to use a proper spelling of units. - gyro_cons_err label files have no units. - There is a discrepancy between imp_a/b/c_gyro and imp_rate. The imp_a/b/c_gyro using rd/s unit, but imp_rate using Dg/S. The order of magnitude for imp_a/b/c_gyro is 1E-4(rd/s). The order of magnitude for imp_rate is also 1E-4 (Dg/S). There is a big question: is it a simple error in one of the units or it’s a bigger question in the improper measurements. Other questions: 1) Why similar physical parameters use different units? 2) Why the spelling of units is inappropriate? [rd/s <-> rad/s and Dg/S <-> deg/s] ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. This may need an update to the LBL template for IMP, and a corresponding re-run of the pipeline. ============================== MUST-PDS-M-014 RO-X-HK-3-NAVCAM-V1.0, mode descriptions in the DATA and EXTRAS. Modes of the camera should be explained either in the /catalog/dataset.cat or in label files (description of the table). 1,4,5 has no sense. The explanation should be along with data (but not in the UserGuide only). ------------ --> Recommended Solution (from PSA): Will investigate and respond. ============================== MUST-PDS-M-015 Typo in VOLDESC.CAT for RO-X-HK-3-OCMRCS-V1.0 Please correct the repeating word 'for' in the description (end of line 4, beginning of line 5): DESCRIPTION = "This volume contains key parameters from Rosetta's Orbit Control Manouevres and the thruster based Reaction Control Subsystem for for the entire mission, from March 2004 until September 2016." ------------ --> Recommended Solution (from PSA): Will fix this typo. ============================== MUST-PDS-M-016 Units in RO-X-HK-3-OCMRCS-V1.0 DATA and EXTRAS labels. For rcs_cum_thrust_1_8 and rcs_cum_thrust_9_12 DATA/ and EXTRAS/ labels, there is unknown unit “gr”. Probably should be used “g” (gram). ------------ --> Recommended Solution (from PSA): Will check and correct/document as needed. This may need an update to the LBL template for OCMRCS, and a corresponding re-run of the pipeline. ============================== MUST-PDS-M-017 Improve description of wheel direction in RO-X-HK-3-RWL-V1.0 data Description of the rwl_wheel_direction either in label files or dataset.cat should be more detailed. Even the User_Guide does not provide enough information to cope with that parameter. All values from rwl_wheel_direction tables have no sense. ------------ --> Recommended Solution (from PSA): Will investigate and respond. ============================== MUST-PDS-M-018 Issues and questions with RO-X-HK-3-STRARTRACKER-V1.0 data (and extras) - For STRARTRACKER, STR A mean background and standard deviation have no units and explanation in DATA or EXTRAS. - Wrong units are used for angular velocity in data and extras label files: “dg/s” should be changed “deg/s”. - Inappropriate unit in str_a_b_integration_time: “sec”. Should be “s”. - There is no appropriate explanation for “mean background” and “std dev background” along with the data and no units in the label files for str_a_b_mean_backgrnd and str_a_b_std_dev_backgrnd. - It would be nice to have a table of stars tracker operation modes (str_a_b_mode, str_a_current_op_mode, str_b_current_op_mode) along with the data (probably in dataset.cat) rather than User_Guide only. Especially when there are a handful number of such modes. - str_a_b_star_quality_star: usage of terms shortcuts should be careful. For example, “STR A/B Star Quality stat parameter” could be considered as “quality status” or “quality statistics”. Description of quality status in the UserGuide: 2264 0 0 MAXSTARS 2264 1 1 LESSMAXGUIDE 2264 2 2 LESSMAXSTARS does not make any sense. - Description of str_a_b_std_dev_backgrnd in label files has error: "This table gives the time profile of the STR B BackGrn Stats Dev parameter " Should be “Std” (Dev). - There is no reasonable explanation for str_a_stars_1_to_9_id_no or str_b_stars_1_to_9_id_no could be found anywhere (in /data or /documents). - Label file of str_a_stars_1_to_9_magnitude and str_b_stars_1_to_9_magnitude have an ambiguous unit: “Mi”. Is it “apparent magnitude m” or is it “absolute magnitude M”. The unit should be corrected. ------------ --> Recommended Solution (from PSA): Will investigate and respond. ============================== MUST-PDS-L-001 Define all acronyms. In multiple documents including AAREADMEs, dataset.cat, insthost.cat, inst_ros_hk.cat, mission.cat, and *especially* eaicd_hk.pdf and user_guide.pdf, acronyms not always defined the first use in the document and acronyms not always in acroymn list. This is especially important in the user_guide.pdf file. Some examples (NOT complete) 'MUST' in the AAREADME file 'STREAM' in catalog/dataset.cat 'RTU' not defined in text or acronym list (looks like it is at the end of the RSOC line) in catalog/insthost.cat 'NAVCAMS' not defined in text or acronym list in catalog/insthost.cat in ro-x-hk-3-solararray-v1.0 'DMS' not defined in catalog/inst_ros_hk.cat 'MTL' in catalog/mission.cat 'ALICE' in catalog/mission.cat 'AFM' in catalog/mission.cat 'M/H' in catalog/mission.cat 'VIS', 'NIR', 'UV' not in list in document/eaicd_hk.pdf, page 4 'AOCS' not in list in document/eaicd_hk.pdf, page 32 'NIR' and 'VIS' not in list in document/user_guide.pdf, page 5 instrument names units acroymns in calbration tables acroymns in figures ------------ --> Recommended Solution (from PSA): Will update the MUST specific documentation accordingly. Will look at the MISSION.CAT and INSTHOST.CAT with PDS. ============================== MUST-PDS-L-002 Availability of Rosetta mission documents. There are many references of Rosetta mission documents. Some I can find (for example at NAIF), but many I could not find. Are they all together somewhere? Two specific examples, both from catalog/insthost.cat, - "Rosetta Mission Implementation Plan - [RO-ESC-PL-5100]" - "For more acronyms refer to Rosetta Project Glossary [RO-EST-LI-5012]" The ref.cat contains additional examples. ------------ --> Recommended Solution (from PSA): Will look at this with PDS. ============================== MUST-PDS-L-003 Comments on various documents - see comments below. catalog/dataset.cat ------------------ - locally archived? - not thrill with DATA_SET_TERSE_DESC - mis alignment relative to? - "ROS_HK__" - no extension? catalog/insthost.cat -------------------- - tense changes in document - sometimes future, sometimes past catalog/inst_ros_hk.cat ----------------------- - There are 2 lists refereing to the datasets. I am not sure about the mapping between the 2 lists. - document dataset list The Inertial Measurement Packages The Reaction wheels The Star Trackers The Navigation Cameras The High Gain Antenna The Solar Arrays The Reaction Control System General AOCMS HK data describing mode changes The Antenna Communications (HGA/MGA/S-band) EDAC radiation Correction parameters - review dataset list Rosetta Spacecraft RF Antenna Engineering Data Rosetta Spacecraft Attitude & Orbit Control System Data Rosetta Spacecraft Radiation Data Correction Data Rosetta Spacecraft High Gain Antenna Engineering Data Rosetta Spacecraft Inertial Measurement Package Data Rosetta Spacecraft Navigation Camera Engineering Data Rosetta Spacecraft Orbit Control Manoeuvre Data Rosetta Spacecraft Reaction Wheel Engineering Data Rosetta Spacecraft Solar Array & Power Engineering Data Rosetta Spacecraft Startracker Engineering Data Rosetta Spacecraft Thermal Control System Data catalog/mission.cat ----------------------- - is AO date for mission start date nominal? catalog/ref.cat --------------- - last 5 references are not alphabetical; should they be? document/eaicd_hk.pdf --------------------- - why is this document not in ref.cat [RO-SGS-IF-1006]? - page 3 earth -> Earth mars -> Mars - p 16 - is Science User guide the same as Rosetta User Manual? if not, then not listed in docs - change of font? - "science user guide" -> "Science User guide" - p 17 - NAWD0V05 - a bit more text would be helpful - explaining that NAWD0V05 is the current Attitude and Orbit Control Subsystem (AOCS) mode setting. As the chart shows, a value of 0 means that the AOCS was in Stand-By Mode. - "Satellite" - Rosetta? or maybe "Mission Operations Centre Satellite DB" - p. 26 - has "YYYY_MM" - "N is the Month Number" -> "MM is the Month Number" - p. 27 - has "YYYY_MN" and "MN is the Month number in the quarter." - a "month number in the quarter" would have me expecting 1, 2, or 3, not the month number in the year; I prefer the month number in the year, but the wording is confusing. - consistancy between pp.26 & 27 - MM, MN? - p. 28 - "The data filenames are coloured in blue." - looks black to me - p. 29 - where is the Data Archive Plan? - p. 31 - EAICD only in pdf - USERGUIDE folder? - p. 32-59 - some table columns format funky document/user_guide.pdf ----------------------- - included in refernece list? RO-SGS-UM-1002 Science User Guide for the ROSETTA HK Engineering data - page 10, "are provided in the user guide." - this doc or other doc? A general confusion about 'user guide' and 'Science User Guide' - are they the same document? If so, not referred to in consistent way. - page 15, "that are not used" maybe "included" would be a better word choice? - page 15, only place I hav seen what MUST relates to - page 18, "loss in precision" - is E20.6 required? "back of the Science User guide" - this doc? - page 19, no WORD format doc - page 20, NAWD0V05 - see document/eaicd_hk.pdf page 17 comment - pages 29 & 30 and probably others with calibration tables, 'section 2.3.5' -> section 2.4.6 - page 31, figure 7, should there be orange? - page 32, why is '.' on next line? - page 32, "24 10 N thruster for attitude", should it be "thrusters" - page 33, more period issues "limits .Temperature" "pipe-work .The" - pages 32-33, repeatitive? - page 34, fig 9, a bit fuzzy - pages 36-37, are values for Thr 12 for total of values for 12A & 12B? - page 39, blog post? - page 47, fig 18 - fuzzy - page 49, RW directions needs a bit more information (a translation table?) - page 51, coordinate system for hga? reference position diagram w/limits; A & B? - page 55, section 3.8.2, no '*' in table to denote translation info no description of different values (like earlier section had) - page 56, figure24; was imaging used then? no blue, but 2 shades of violet a bit of orange - pages 57-68, 3.9.2 - explanations of modes please - pages 57-68, 3.9.2 - frames relative to sc frame? - page 58, str_a_stars_1_to_9_magnitude listed twice - pages 58-59, deg/s in document, but dg/s in file - pages 64-65, first column references "STR A - Star 1 to 9 - XY Coordinates" but 2nd column references "STR_B_STARTS_1_TO_9_XY_CORD" and last columns reference STR B Star [1|2|3|4|5|6|7|8|9]: [X|Y] coord - pages 74-75, power_control_unit_cm_a_volt not listed; contents are listed on page 76 - pages 74-75, power_dist_unit_secondary_volt (data) but power_dist_unit_secondary_voltage (document) - pages 74-75, power_dist_unit_primary_current listed, but no primary voltage listed. Am I not understanding the use of the terms primary and secondary? - pages 74-75, power_dist_unit_secondary_volt listed, but no secondary current listed. Am I not understanding the use of the terms primary and secondary? - pages 75-76, sometimes Y- and Y+, sometime YM and YP - page 79, "DMS.Each"; spacing - page 80, "telemetry. the "; The? - pages 82-83, calibartion needs some units - page 86, fig 36, needs units - page 93, fig 40, some TBDs on placement of sensors - page 94, fig 41, parts blurry - pages 100-106, ro-x-hk-3-tcs-v1.0 - information missing - pages 100-106, section 3.12.2, can not determine which TSC is which parameter id information very different and not matching like other sets of channels; for example, GIADA values are NTSA0067 and NTSA0193 in data, but those are not what is listed in the chart - pages 100-106 looks like right most column is incomplete ******* - solar array displacement error vs misalignment? Are they additive or one includes the other - Is is nominal to use N/A as the units for counts please? - overall, present, past, future tense varies - I am not sure about using the term "calibration" to describe the tables that explain different modes. ------------ --> Recommended Solution (from PSA): Will update HK specific files (INST catalog, EAICD, USER_GUIDE and DATASET catalog(s). Will look into the updates suggested for the INSTHOST, MISSION and REF catalogs. ============================== MUST-PDS-L-004 Comments on some BROWSE products - browse directory - ro-x-hk-3-solararray-v1.0/browse/masterbusvolt_cm_ab_2014_q2.png - please make sure all acroymns and abbrevations on plots are defined somewhere (eaicd_hk.pdf and users_guide.pdf) for example, ROS, SEC - masterbusvolt_cm_ab_2016_q2.png - y range issue - power_unit_pri_curr_2014_q2.png - one value seen well, other barely example, but others YYYY_QX with same issue - power_unit_pri_curr_2014_q3.png - NPWD2920 missing? (not on legend) - power_unit_sec_volt_2014_q1.png - different colors than others of the same power_unit_sec_volt_YYYY_QX (see also MUST-PDS-M-007) ------------ --> Recommended Solution (from PSA): Will check and update the browse / documentation accordingly. ============================== MUST-PDS-L-005 Comments on missing data - The documentation generally warns that data may be missing from some directories. A comment in the sections when data is known to be missing during non-hibernation time periods would be useful. Places I found with missing data during non-hibernation time periods include - ro-x-hk-3-antennastatus-v1.0 uso_status ro-x-hk-3-aocgen-v1.0 wol_manager ro-x-hk-3-edac-v1.0 navcam_a_edac_cntr navcam_b_edac_cntr str_a_edac_cntr str_b_edac_cntr ro-x-hk-3-hgaapm-v1.0 hga_a_absang_err_az_el hga_a_disp_err_az_el hga_b_absang_err_az_el hga_b_disp_err_az_el ro-x-hk-3-navcam-v1.0 navcam_b_op_mode ro-x-hk-3-ocmrcs-v1.0 ocm_accel_meas ocm_est_dist_torques ocm_estim_trans_vel ocm_impulse_meas ro-x-hk-3-startracker-v1.0 str_a_b_no_of_stars_found ------------ --> Recommended Solution (from PSA): Will investigate and respond. Is it feasible to provide the info requested? The best places for this would be the USER_GUIDE and the DATASET.CATs. ============================== MUST-PDS-L-006 Comments on extras - ro-x-hk-3-antennastatus-v1.0 no extras directory. Planned? - ro-x-hk-3-navcam-v1.0 no extras directory. Planned? - Were leap seconds accounted for when converting the binary file timestamp to the time in the tab file? If not, please document. If so, then I do not understand my result below. From 1972 though 2015, there were 27 leap seconds (https:// naif.jpl.nasa.gov/pub/naif/pds/data/ro_rl-e_m_a_c-spice-6-v1.0/ rossp_1000/DATA/LSK/NAIF0011.TLS). Those do not appear to be accounted for in the conversion of the the timestamp to the time in the tab file. Notes: I read one extras file and label with the SBN IDL function readpds and compared the first couple values with those in the data file. The files used were ro-x-hk-3-solararray-v1.0/extras/master_bus_voltage_cm_a_b/ 2004_q1/ros_hk_npwd1024_2004_q1.* ro-x-hk-3-solararray-v1.0/data/master_bus_voltage_cm_a_b/ 2004_q1/ros_hk_npwd1024_2004_q1.tab The first 2 rows of ro-x-hk-3-solararray-v1.0/data/ master_bus_voltage_cm_a_b/2004_q1/ros_hk_npwd1024_2004_q1.tab are 2004-03-02T00:57:58.137, 2.797200E+01 2004-03-02T00:58:02.137, 2.797200E+01 The first 2 pair of values from ro-x-hk-3-solararray-v1.0/extras/ master_bus_voltage_cm_a_b/2004_q1/ros_hk_npwd1024_2004_q1.dat are 1078189078137 27.97200 1078189082137 27.97200 So the parameter's values match. Now to look at time. There is a 4 seconds difference between both sets of number - ok. From 1970 through 2003, there were 26 non-leap years and 8 leap years. Excluding leap seconds, a non-leap year is 31536000000 msec and a leap year is 31622400000 msec. (26 years * 31536000000 msec/year) + (8 years * 31622400000 msec/year) = 819936000000 msec + 252979200000 msec = 1072915200000 msec So that leaves 5273878137 msec that are in 2004. The 1st of January through the 1st of March in a leap year is 5270400000 msec. So there are 3478137 msec or 3478.137 seconds on the 2nd of March. on the 2nd of March. 00:57:58.137 is equal to (57 minutes * 60 sec/min) + 58.137 seconds = 3478.137 seconds However, this did not account for the 23 leap seconds as of 2004. Then I would expect the time to be 00:57:35.137. Am I misunderstanding something? If so, a bit more information in the documentation would be helpful please. ------------ --> Recommended Solution (from PSA): Will investigate and respond. Response from the pipeline developer for the MUST data: it seems that leap seconds were *not* accounted for in the conversion from binary to ASCII. Plan to regenerate affected data. ============================== MUST-PDS-TB-001 (Duplication of MUST-PDS-M-001) AAREADME.TXT update. Introduction par 2: change "March 2014" to "March 2004". ------------ --> Recommended Solution (from PSA): Will fix this. ============================== MUST-PDS-TB-002 End of lines in BROWINFO.TXT For RO-X-HK-3-{AOCGEN,HGAAPM,IMP,NAVCAM,STARTRACKER,TCS}-V1.0/BROWSE/BROWINFO.TXT Required End of Line characters are missing carriage return. ------------ --> Recommended Solution (from PSA): Will fix this. ============================== MUST-PDS-TB-003 Updates to DATASET.CAT files For the 'CATALOG/DATASET.CAT' - LABEL_REVISION_NOTE was changed instead of being updated. You should not be changing a label revision note, but only appending to it normally. Since this has not been released, we can live with it but it is very disconcerting: Example: =================== < LABEL_REVISION_NOTE = "2019-07-18, L. O'Rourke, Created" --- > LABEL_REVISION_NOTE = "2019-11-30, L. O'Rourke, Updated based on Sep-2019 > Review" =================== - CITATION_DESC: Year should be changed from 2019 to 2020. - CONFIDENCE_LEVEL_NOTE: Update after 2020 April review. Currently it states "Updated from Sept 2019 review" which is not helpful or a correct usage of this keyword. - TARGET_NAME: Since all values in the DATA directory were "N/A", this value in this file should also be "N/A". You cannot state 67P was the target of the data set when it was never observed. ------------ --> Recommended Solution (from PSA): Will discuss with PDS and update as needed. ============================== MUST-PDS-TB-004 Update to INST_ROS_HK.CAT - The LABEL_REVISION_NOTE has changed, not merely been updated. Normally you should not alter the label revision note, only append. Since no change was made to the contents of this file, it is distressing to see this label revision note change. Once this file is going into the archive the label revision note text should remain unchanged unless the file's text changes, in which case the label revision note should be appended to, not replaced. Please replace the text with "First version" or something to that effect. ------------ --> Recommended Solution (from PSA): Will fix this. ============================== MUST-PDS-TB-005 Error with some data format descriptions in the labels. files: 'DATA/ ... /*.LBL - COLUMN 2 mismatch. For all cases where the combination of BYTES = 15 and FORMAT = "I5", these two do not match. BYTES is 15, but the FORMAT only covers 5 bytes. FORMAT should cover all 15 bytes or the other keywords would need to be corrected (BYTES to 5, START_BYTE changing, etc). ------------ --> Recommended Solution (from PSA): Will check with PDS on where this problem is and fix as needed. ============================== MUST-PDS-TB-006 Illegal keyword in INDEX files file: 'INDEX/INDEX.LBL' - REVISION_ID: Invalid and unknown keyword. Relic of old data sets. ------------ --> Recommended Solution (from PSA): Will fix this. ============================== MUST-PDS-TB-007 Incorrect INDEX file file: 'RO-X-HK-3-AOCGEN-V1.0/INDEX/INDEX.*' - These files are for RO-X-HK-3-ANTENNASTATUS-V1.0 not RO-X-HK-3-AOCGEN-V1.0. Please regenerate the files. ------------ --> Recommended Solution (from PSA): Will fix this. ============================== MUST-PDS-TB-008 Update needed to Rosetta Mission dictionary UNKNOWN_VALUES: The following keywords have undefined values. Should be added to Rosetta Mission dictionary *or* corrected in the DATA label to a value specified in the Rosetta Mission dictionary. I noticed some values were manipulated (including or not including a dash for instance). I have not received an updated dictionary so that may also be the cause. - ROSETTA:SC_HK_SUBSYSTEM - "ANTENNASTATUS", "AOCGEN", "HGAAPM", "OCMRCS", "SOLARARRAY" - ROSETTA:SUBSYSTEM_DATA_TYPE - "X_BAND_TWTA_1_2_STATUS", "CONSERT_ANT_TEMP", "GIADA_TEMP", "MIDAS_TEMP", "MIRO_TEMP", "OSIRIS_TEMP", "RF_ANTENNA_TEMP", "ROSINA_TEMP", "RPC_BOOM_TEMP", "RPC_ICA_TEMP", "RPC_IES_TEMP", "SAS_TEMP", "SREM_TEMP", "SSP_ANT_TEMP", "VIRTIS_TEMP" ------------ --> Recommended Solution (from PSA): Will send the new dictionary to PDS. ==============================