DITV_0003 ========= voldesc.cat - This file is missing. errata.txt - If there are no errata, there should be no errata.txt file. DI Thermal Vac Data - General Liens: - The document set should include the requirements document for the instruments. - The Ball calibration plans need to be ITAR-cleared and added to the archive. - All the FITS files indicate an OBJECT of "ground_cal" which is not particularly helpful. Is it possible to put the experiment name (EXPRMNT) there instead? Please note this was only an IRAF issue. - In the mission.cat file, there are no units in the tables. - In the mission.cat file are "n/a" entries in the look-back phase table, which contradicts the text preceding that says all three instruments will continue to operate for 60 hours. Fix this inconsistency. - In inst_hriir.cat there are typos in the units of the overview tables. Also, the information here should be compared to that available on the instrument web site and edited/improved accordingly. - In inst_hriir.cat, move the data in text into tables as far as possible. - The catalog and info.txt files need to be proofed. This should be changed to avoid ambiguity. - HRIIR data needs a discussion of the manganen wire temperature correction for the focal plane array. - The general descriptions in the filter_*.lbl files do not apply equally to all filters. In particular, the "650 nm center and 700nm width" is clearly not true in at least three cases. - There are two different things called "templog", which is misleading. One name or the other should be changed (and the change propagated to info.txt and other documentation). [One is a temperature log, one is actually an IDL program.] - In catalog files, replace "principle" with "principal". - At the Deep Impact science team meeting on 13-14 September 2004, several members requested that the Science Data Center (SDC) modifiy all HRIIR image mode 6 FITS data from the thermal-vacuuum test by multiplying both the reset and data frames by negative one. Without this modification, the data frame must be subtracted from the reset frame to ensure the resulting image had positive data number. It is more intuitive to subract the reset frame from the data frame. However, Mike A'hearn and Stef McLaughlin prefer that the data remain in the original state as used by the science team for calibration analyses. catalog/ -------- These files do not use SBN standard names. To do so would make it somewhat easier to make sure the same name is used everywhere. catinfo.txt - The dataset catalog file has a different name than the one mentioned in this file. dataset_tv3.cat - I thought all the calibartion targets were just going to be "CALIBRATION". Why "GROUND CALIBRATION"? - CITATION_DESC may not be "NULL". - There is no attribution for the DATA_SET_DESC text. No anonymous text in DATA_SET objects! - REFERENCE_KEY_ID values may NOT be used in text descriptions instead of proper citations. (They may be used in addition to them.) - In the overview section: o "Several science team members were present at all time to assist..." -- "... at all times ..." o "...obtain calibration data of the ITSVIS at for below the expected..." -- "at or below..." groundcal.cat - "CALIBRATION" is not a proper noun. TARGET_NAME should be something like "GROUND CALIBRATOR". insthost_impactor.cat - Syntax error on line 40: double quotes within double quotes. - No attribution for the text. Attribute it or delete it. - RREFERENCE_KEY_IDs instead of citations. inst_itsvis.cat - Is it really necessary and desirable to include "DEEP IMPACT" in the INSTRUMENT_NAME? - REFERENCE_KEY_ID blah blah blah mission.cat - RECORD_TYPE does not belong in catalog files. - REFERENCE_KEY_IDs without citations. - Check with Tyler on this, but I think that MISSION_HOST may not contain multi-valued keywords. It must be repeated once for each unique INSTRUMENT_HOST_ID. - Another check with Tyler: Should ALL targets (including the calibration target(s)) be included in the MISSION_TARGET list? ref.cat - RECORD_TYPE is inappropriate in catalog files. - Articles accepted but not yet printed are "in press," not "in publication." - There are line break problems in some of the references, which suggests that some fast cutting-and-pasting were done. Do all these references really end with the same line ("Space Science Reviews, submitted")? data/ ----- - Is it not possible to simplify these file names a bit? It looks to me like the first 8 bytes are redundant with the directory structure. itsvis/*.lbl - STOP_TIME cannot be "N/A" if START_TIME is valid. It may be the same as the START_TIME (for an instantaneous observations), or it may be "UNK" or possibly "NULL," if you're planning to calculate it later on. - Labels should never contain filler values like "-9999.000". They must use the figurative constants "UNK," "N/A," or "NULL". - A) How can HORIZONTAL/VERTICAL_PIXEL_SCALE be "N/A" in an image, and B) If they are, why are they in the label in the first place? - Why is there a PRODUCER_FULL_NAME credit in here but not a CITATION_DESC? templog/*.lbl - Syntax error, line 16, in the value string. - The first paragraph of the DESCRIPTION ends in mid-sentence. document/ --------- image_log/tv3_its.lbl - "Personnel" is misspelled. image_log/tv3_its.asc: - The word focust is misspelled on line 32 - The word ususally is misspelled on line 32 - The word alighment is misspelled on lines 54 436 - The word astignmatism is misspelled on lines 99 1792 - The word foward is misspelled on line 611 - The word offical is misspelled on line 1787 - The word iamges is misspelled on line 2056 - The word cude is misspelled on line 2174 - The word definitly is misspelled on line 2348 pdsdd/pdsdd_di.lbl - Spelling errors. - These descriptions (and those elsewhere that refer to this document) confuse the concepts of "local dictionary," "PDS Data Dictionary", and the hybrid that is actually present in this directory. This needs to be MUCH more clearly explained. - pdsdd_di.full apparently contains a modified form of the pdsdd.full file, BUT THERE IS NO NOTATION TO THAT EFFECT IN THE FILE HEADER. This is misleading and completely inappropriate. reports/reports.lbl - I find this description to be a bit sparse. The documents themselves seem to be colloquial, and perhaps culled from email messages. This should probably be explained. index/ ------ - Index directory standards are ignored here. index.lbl - The required "index.tab" file absolutely, positively MUST use the INDEX_TABLE object and use it properly. Other indices MUST have names other than "index.tab."