WILD2_KECK ========== - Missing voldesc.cat - Need a glossary for the FITS keywords. catalog/ -------- catinfo.txt: - The word aquired is misspelled on lines 15 39. - The word Senors's is misspelled on line 35. dataset.cat - Need a processing description for the DATA_SET description, especially in view of its impact on Stardust. - Is information on the photometric quality of the night available? If so, please add it. (Or a general comment in the DATA_SET description, if appropriate.) - Please document the aperture used for the standard star observations (if this is not already present). - MISSION_NAME is not allowed in DATA_SET objects. (You cannot add or omit keywords to SPECIFIC_OBJECTs like DATA_SET and most other catalog objects.) - CURATING_NODE_ID is not an allowed keyword. - The phrase "so-called" is generally considered derogatory and should not appear in the DATA_SET_DESC. If the filter is an Ellis R filter, then just say so. If it is not, then just describe it. i0039inst.cat - The instrument catalog file never gives the pixel scale. - The instrument catalog file does not give particularly good descriptions of the various instrument modes. - INSTRUMENT_TYPE value is not appropriate (it appears to me multi-valued, which would be aproblem to begin with, except it's not in the correct syntactical format for a multi-valued keyword), and it's not clear to me what was intended. - This text is extensive and looks like it was cut from a previously published source (and sloppily - there are blank spaces were the unit symbols didn't translate). Who is the author and do we have permission to republish? - Angstrom symbol is missing wherever there is a wavelength. obs378t2host.cat - The LABEL_REVISION_NOTE seems somewhat opaque. - Per Typer, the filename looks odd, but appears valid. obs378t2.cat: - DATA_SET_ID = "EAR-C-I0039-1-SBN0007-KECKIIESI-V1.0": Tyler doubts this is CODMAC 1. CODMAC data is Raw Data; Telemetry data with data embedded. These are images, and they should be something between 2 and 5. These are pretty raw images, so Tyler would pick 2. calibration_none.cat & calibration_sky.cat - The CALIBRATION catalog files are completely wrong. Fix it and propagate back through OLAF. - These two files both have the exact same TARGET_NAME. TARGET_NAME must be unique across the PDS. How are these distinguished in the data? And why? PG*.CAT & SA*.CAT - Every standard star has a TARGET object that doesn't include the basic RA and Dec of the star. If these TARGET objects stay, that minimal information should be added. If not, either provide a table with the full set of star parameters (RA, Dec, type, etc.), or omit the information entirely and refer users to the star catalogs. - Is this the appropriate approach for stellar calibration targets? 81Pwild_2.cat - The Wild 2 catalog file presented here is not consistent with the catalog file provided for this object in other data sets. - This is a different TARGET object than others submitted for this object, and it contains less information. It should NOT be the one submitted to CN. catalog/target/ --------------- - Let's not list each calibration star individually. Use STAR. - Calibration_none.cat is an odd filename. Also, the calibration target file should either be a generic or very specific. So, make a keckcalib.cat, or use an existing generic calibration catalog file. You might correlate with DI calibration targets. - calibration_sky.cat: you might use existing "SKY", "BLACK SKY" or "DARK SKY". - I'm not clear as to whether subdirs are allowed off of catalog. What happens is that the pointers in the data files get confused, since they expect these to be in the CATALOG directory. Let' get rid of the star target files, download the existing cat for SKY, and come up with a better option for NONE. Then put them in the CATALOG directory. data/ ----- - In the data directory the processed data are in a subdirectory whereas the raw data are not. There should be both a "raw" and "processed" subdirectories. - The DATA_SET_ID is not compliant. - In the FITS headers, gain and read noise are absent. The exposure time has no unit. Is it possible that the FITS normalizer expunged info from comment fields? - The processed esi0082.fit file (from 2003dec20) gave Ludmilla problems in trying to open it, where other files worked. Investigate this and make sure there is nothing pathologically wrong with the file. - Include comet centroid information in a separate table at the level of the astrometry table. - Investigate including thumbnail images for browsing in a systematic way. fits_param_table.lbl - All of the keywords that have "N/A" as a value ARE applicable and should have values, except for ABSTRACT_DESC, which should not be here at all. - PRODUCT_ID is not usually a particularly helpful thing to users for locating files. In this case, it is partly useful, in that at least it corresponds to the file name (a fact which is not mentioned). However, since the data are devided by observation date, this is only half the information needed to find the file. - Also, it looks like the PRODUCT_IDs listed in the table file do not actually correspond to the PRODUCT_IDs in the data file labels. - The DATE_OBS column has inappropriate units and data type. - Declination must be given as four separate columns, not a single column. - Right ascension must be given as three separate columns. - Why is this table delimited? - Airmass entry should have units entry removed ("none"). */*.lbl - I'm not sure OFFSET makes sense and SCALING_FACTOR should be omitted if it is 1.0. - These IMAGES need to have the following keywords included with correct values: AXIS_ORDER_TYPE LINE_DISPLAY_DIRECTION SAMPLE_DISPLAY_DIRECTION */processed/*.lbl - OFFSET and SCALING_FACTOR should be omitted if they are zero and one, respectively. - These IMAGES need to have the following keywords included with correct values: AXIS_ORDER_TYPE LINE_DISPLAY_DIRECTION SAMPLE_DISPLAY_DIRECTION Document -------- model_desc.txt: - The word uncertatinties is misspelled on line 25 templog/temp_ext_hri.txt: - The word supecedes is misspelled on line 40 index/ ------ index.tab - The FILE_SPECIFICATION_FIELD contains file names with mixed case. This is forbidden, and doesn't appear to correspond to the actual case in the data set anyway. - Many of the paths in the FILE_SPECIFIATION_FIELD are invalid. - Why is the CITATION_DESC value in this file? This is really annoying. - The first field in the index.tab file has what appears to be two forward-slashes in a row (ex: DATA/2003DEC19/PROCESSED//2003DEC19/PROCESSED/esi0014.lbl).