DIF-C-MRI-2-EPOXI-GARRADD-V1.0 Raw Data, Comet Garradd DIF-C-MRI-3/4-EPOXI-GARRADD-V1.0 Calibrated and Resampled Data, Comet Garradd DIF-C-MRI-2-EPOXI-ISON-V1.0 Raw Data, Comet ISON DIF-C-MRI-3/4-EPOXI-ISON-V1.0 Calibrated and Resampled Data, Come ISON Catalog ======= o In the dataset.cat file description, please add full citations to the Calibration papers (i.e., as footnotes in the text – in addition to the REFERENCE objects that also exist). o There needs to be a reference to the source of the pole definition for Garradd and ISON in some appropriate place. [Note that the SPICE kernels likely involved have not been reviewed.] o There is a known issue with a solar flare that significantly affects data on a particular date. This should be noted in the data set descriptions for all affected data sets. o In dataset.cat: - The CITATION_DESC year must be '2014' since this is when the data were reviewed and released to the public. - Line 167/234: “This extension uses one byte of eight (,) bit flags to …” would better stated "This extension uses one byte consisting of eight, single-bit flags to..." - The explanation of x-size for the table: “X-size is the Spectral dimension” is wrong. - Line 273/351, in the table listing filters: Center wavelength of CLEAR6 is 650 nm not 600 nm Documents ========= o Ensure these data sets have the latest versions of these document files: day_of_year_calendar.lbl epoxi_cal_pipeline_summ.lbl epoxi_sis.lbl instruments_hampton.lbl pdsdd_epoxi.lbl quaternion_desc.lbl o In epoxi_sis.pdf: - This document says labels for HRIV, MRI, and ITS level 3/4 data, PDS keyword PROCESSING_HISTORY_TEXT contain FLAT_PRO= FLATCONS= FLATTEMP= CALWINDW= CALWINPY= but the sample labels in the SIS's 4.4.4.1 and 4.4.4.2 do not. - p. 27: "DIF-L-HRII-3_4-EPOXI-LUNAR-CALS-V1.0" should have a / not a _ i.e. "DIF-L-HRII-3/4-EPOXI-LUNAR-CALS-V1.0" - epoxy_sis.pdf pages 47-9 the figures are misaligned with the text. This needs to be corrected in every copy of the document in all data sets. o There are summary files with names like “hriv_3_4_epoxi_garrad.pdf”. In at least some of these labels in some data sets, the Julian Date field is described as being in the form “YYYYMMDD”. This needs to be fixed if it applies to this data set. o The BODY_POSITIVE_POLE_CLOCK_ANGLE or whatever it’s called, is stated to an unrealistic degree of precisicion for comets Garradd and ISON. It should certainly not be stated in these data to more accuracy than integer degrees. But in the document directory the table that lists geometry gives the same clock angle for this value as for the celestial north clock angle. If the value is not applicable, or otherwise unknown/unknowable, then the appropriate constant needs to be defined and used. o In places that describe the file naming convention, there needs to be a clear indication of which time (beginning, middle, end) is used for creating the file name. o In the Garradd data set documents, in both mri_2_epoxi_garradd.lbl and mri_3_4_epoxi_garradd.lbl: - Line 68/71: Specified format for column 2 is not consistent with Julian date - Line 96/99: Confusing sentence: If the target was within several fields-of-view, the actual target name was used although the target may not be in the image. - Line 126/129: typo: delete “this” - Line 279/282: Center wavelength for CLEAR6 is 650 nm not 600 nm - Add a note to indicate, where it is not obvious, why certain columns in the table either all have identical values, or have N/A flags. o In the ISON data, file mri_2_epoxi_ison.lbl, the body pole is not known, so the appropriate constants indicating the value is unknown should be used in the label and table columns. DATA/ ===== o The BODY_POSITIVE_POLE_CLOCK_ANGLE or whatever it’s called, is stated to an unrealistic degree of precisicion for comets Garradd and ISON. It should certainly not be stated in these data to more accuracy than integer degrees. But in the document directory the table that lists geometry gives the same clock angle for this value as for the celestial north clock angle. If the value is not applicable, or otherwise unknown/unknowable, then the appropriate constant needs to be defined and used. CALIB/ ====== o The following labels have the same syntax error: dif-c-mri-3_4-epoxi-garradd-v1.0/calib/abscalvs/mrivis_100101_2_0_1.lbl dif-c-mri-3_4-epoxi-garradd-v1.0/calib/abscalvs/mrivis_100101_2_0_2.lbl dif-c-mri-3_4-epoxi-garradd-v1.0/calib/abscalvs/mrivis_100101_2_0_3.lbl dif-c-mri-3_4-epoxi-garradd-v1.0/calib/abscalvs/mrivis_100101_2_0_6.lbl dif-c-mri-3_4-epoxi-garradd-v1.0/calib/abscalvs/mrivis_100101_2_0_7.lbl dif-c-mri-3_4-epoxi-garradd-v1.0/calib/abscalvs/mrivis_100101_2_0_9.lbl dif-c-mri-3_4-epoxi-ison-v1.0/calib/abscalvs/mrivis_100101_2_0_1.lbl dif-c-mri-3_4-epoxi-ison-v1.0/calib/abscalvs/mrivis_100101_2_0_3.lbl dif-c-mri-3_4-epoxi-ison-v1.0/calib/abscalvs/mrivis_100101_2_0_6.lbl dif-c-mri-3_4-epoxi-ison-v1.0/calib/abscalvs/mrivis_100101_2_0_7.lbl dif-c-mri-3_4-epoxi-ison-v1.0/calib/abscalvs/mrivis_100101_2_0_9.lbl - Missing RECORD_TYPE = FIXED_LENGTH