SDNC_0003 ========= Notes: Reviewers had problem accessing these images. The attached PDS labels are not generally supported and the principal reviewer encountered serious problems getting NASAView to run on her system. In NASAView - what is the difference between "Stretch Image" and "Stretch Display"? Liens: - When SPICE is used to generate geometry values in labels, the DATA_SET_ID should be referenced in the data label and the specific kernels used should be identified by filename. In cases where non-archived kernels were used, the kernel files themselves should be included in the data set archive. errata.txt - Why have the listed errata not been corrected? catalog/ -------- dataset.cat - There is a syntax errors in this file: double quotes inside double quotes. - Missing ABSTRACT_DESC, ARCHIVE_STATUS and CITATION_DESC - The DATA_SET_DESC should point to the piimglog.pdf file for the image log table and the index.tab file. - line 461: three 301 x 301 pixel pixel windows. Do you want 'pixels' doubled? - line 590: Is 'decomutated' spelled correctly? Aren't there two m's? mission.cat - MISSION_TARGET must be repeated for each unique TARGET_NAME. - Needs updating for activities since the file was originally written. (Tony has a list of specific items to be updated.) - This file is only half the size of the mission file in the Annefrank dataset. Should the two files be merged / updated so they are the same up-to-date file? - Currently written in terms of future tense. Update to reflect the actual events? e.g. actual encounter date, approach distance, phase angle changes. Two ways to do this (per Tony): 1) update the text to past tense rather than future tense 2) add an update section that explicitly states that the rest of the text was written before the mission and this new section gives the actual data that is relevant - Tony: I don't know how accurate the targeting correction maneuver information is. If we don't know what the real corections ultimately were, then it should be made clear that the listed ones were the planned maneuvers. - Actual info that differs from text: Flyby occurred on 2004-01-02T19:21:32 UTC (98.9 days after the comet's perihelion) Closest approach distance was 236.5 km Obtained 72 images during the encounter sequence (including pairs that can be used for stereo imaging) Flyby velocity was 6.1 km/s Solar phase angle ranged from 72 deg at start of sequence, dropped to minimum of 3 deg, and increased to 103 deg at end of sequence - Also update the AnneFrank section: closest approach occurred on 2002-11-02T04:51:20.8 (-/+ 0.8 sec). closest approach distance was 3078.5 km (+/- 9 km) Solar phase angle during the close approach imaging sequence dropped from 130 deg to 47.2 deg. - Cruise 1 Phase section: "The Cruise 1 phase of the first part of the STARDUST mission nearly six years long, relatively low activity cruise." -- doesn't make sense. Neither the entire mission nor this cruise phase is six years long - where does that number come from? - Last sentence of the Wild 2 encounter section: "Any free memory left from the encounter period will be allocated to the post-encounter imaging, until memory is full used for imaging after the primary encounter period." --- Not clear what is being said. instrument.cat - Refers to calibration checks "to be done" between Annefrank and Wild 2. This information should be updated for whatever happened with these checks. - In optics section, need to define MTF. - In Scan Mirror Mechanism section, need to define DOF. - NEWBURNETAL reference is never cited in the text. data/ ----- - Do we really want all 700 images in the same subdirectory? - What is "tmp"? - The label.rpt file is litter. Please remove. - There are several new keywords that will have to be pushed through the Standards process: n0643we02.img: SCAN_MIRROR_ANGLE SCAN_MIRROR_RATE SCAN_MIRROR_TEMPERATURE SATURATED_PIXEL_COUNT *.lbl - SPACECRAFT_NAME is a deprecated keyword. Use INSTRUMENT_HOST_NAME. - Invalid keywords. - The labels I spot-checked mentioned WINDOW objects, but didn't actually contain any. Are there any WINDOW objects in these labels? - The image file labels need to include LINE_DISPLAY_DIRECTION, SAMPLE_DISPLAY_DIRECTION, and AXIS_ORDER_TYPE. n0643we02.img: - Lvtool says that the checksum = 0... god knows why, because it isn't... Perhaps a tool problem on our end, but just to be sure, have a look at the file. document/ --------- - The ASCII tables in the document directory need to be sorted out and the relevant table(s) placed in a calibration directory as a properly formatted TABLE. piimglog.asc - The label claims the .asc file is in CSV format, but character strings are not quoted. piimglog.pdf - If possible, please insert column headings at the beginning of each page of the table (or periodically throughout the table) in the piimglog.pdf file. - Some images show stripes (e.g., n2091we02.img) that are not noted or explained in the documentation. The cause of these bars needs to be tracked down and documented, and we need to search the data set and identify all images affected, if possible. Boris Semenov notes these lines are noise, and are present to a greater or lesser degree in all images. - The majority of image file names in this document end in ".01", whereas the data file names in the data directory end in "02". Boris S. (via telecon) notes that 01 vs 02 indicates versions of the label for the image. The content should be the same. This difference should be explained. - The focal length of the camera is given incorrectly, based on the pixel scales given in the labels. - A single file tabulating the pixel scale values throughout the dataset should be added if possible. - If it is possible to put pixel scale in the piimglog.pdf, please do. calrpt/*asc - Strings are not quoted. calrpt.pds - If possible, modify the calrpt.pdf file to add a page of caveats regarding the limited usefulness of the ground calibration. scdesc/scdesc.lbl - Why is the Aerogel brochure included in this label, when in other places it is treated as an autonomous document. index/ ------ index.tab and index.lbl - The column descriptions for some of the more obscure values (like reticle point descriptions, e.g.) should contain a bit more information, so that the average science user does not need to refer back to, e.g., "onlabels.txt" constantly. Actually, "inlabels.txt" does not provide a better explanation in this case. - The index file contains constant-valued columns that make the file difficult to use. Omit these columns. - index.tab: no dsid.