General ======= - There doesn't seem to be any rhyme or reason in the use of abbreviations for the various observatories involved. Ideally, the INSTRUMENT_HOST_ID would be used in all cases - catalog file names, subdirectory names, index file names, etc. Alternately, the unabbreviated location name would also work in all cases. [root] ====== aareadme.txt - There are bits of this that I'm not sure someone who wasn't already well-versed in PDS nomenclature or the data sets in question would understand. For example, there is a reference to the "Lowell data directory", but there is no data directory with a name that looks anything like "Lowell". errata.txt - This says the DSCOLL.CAT file is incorrect. Is that true? The reason given here is odd - that's not incorrect, just incomplete. The fact that it might change later does not make it incorrect now. - Were the problems mentioned in the data either corrected or documented in the DATA_SET catalog file? If so, they should not be mentioned here. voldesc.cat - The VOLUME_SER_ID is incorrect - it sould end in "_XXXX", or at least "_00XX" - whatever was used in previous SL9_nnnn volumes. - "VOLUME 13" is not a particularly helpful volume name. Does that follow the pattern of previous SL9 disks in the series? - VOLUME_VERSION_ID should not be "PROTOTYPE". - There is no TARGET catalog file or pointer here. - If the volume ID ends in 13 and the VOLUME_NAME is "VOLUME 13", I'm pretty sure VOLUMES shouldn't be "1". catalog ======= - Where are the TARGET catalog files for Jupiter and Io? - Removed data-set specific text in the instrument and host files. sl9ebmsn.cat o There are some basic flaws in this, like: - The "Mission Overview" section never does give an actual overview of the mission. - The lead-in to the observatory list mentions spacecraft and earth- orbiting satellites and then says "a lsit follows", but the list only includes ground-based observatories, which were never mentioned above. I reworded the into slightly, but it still seems pointless to mention the non-earth-based hosts which DO NOT CONTRIBUTE to the present archive and which each has its own MISSION catalog files. - The MISSION_OBJECTIVES_SUMMARY doesn't seem to have anything to do with the objectives but rather summarizes results. um_poin.cat - This file has almost nothing to do with the instrument, it is only about the data that was taken. That information should be in the data set catalog file. - If this really is a particular high-speed photometer, then the name of it should NOT be as generic as "HIGH SPEED PHOTOMETER". - This file needs some serious proofing. - Note that this file claims that all the Jovian moons were observed, whereas the data set catalog file only mentioned Io. document ======== - DATA_SEt_ID was wrong in most places where it was mentioned. acronym.lbl - The FILE_RECORDS in the label was not equal to the number of records in the file. I edited the data file a bit anyway, just to clean up format. c14.asc - This looks like a copyrighted document. Where's it from and do we have permission to republish? - I also don't see why we're including what appears to be a beginner's guide to the care of feeding of a Celestron telescope in a PDS volume. diagram.lbl - The description consists of an excerpt from a FITS header that doesn't make sense in this context. - YOU CANNOT DESCRIBE A TIF FILE WITH A TABLE OBJECT IN A DOCUMENT DIRECTORY! What the heck is this? docinfo.txt - This claims c14.asc is a Lowell-specific manual. It isn't. - The list implies that nickel1m.asc is an ASCII version of some other manual. It isn't - at least not one in this directory. - This file claims the diagram.tif file is an illustration from the "Celestron 14 manual" (i.e., c14.asc). This is clearly marked as an illustration of a Celestron C5/C8, and doesn't appear to have anything to do with the text in c14.asc. nickel1m.lbl - Nowhere in any file in the catalog directory is the word "nickel" used. What is this doing here? - This looks like it was copied verbatim from somewhere, but no attribution is given. It cannot be included without it, even if it does belong here. index ===== indxinfo.txt - The last two sentences of the first paragraph don't make any sense to me. What's the difference between "the index table" and the "INDEX" file? - Actually, I'm not sure this description even fits the actual indices applied. I don't see any "experiment codes", for example, and I don't recall coming across the term prior to this file. It also ralks about subdirectories, presumably in the index/ directory itself, which don't exist. Is this the right info file? *indx.tab - These files can't use the INDEX_TABLE object unless they conform to the INDEX_TABLE requirements. Currently, they don't. Specifically, they are missing the required fields PRODUCT_CREATION_TIME and PRODUCT_ID - The tables have right-justified character fields. Character fields must be left-justified. index.tab - The FILE_NAME field in this file is right-justified. It's a character field and should be left-justified. lo_gic ====== /austral -------- *.lbl - The label times end in "Z". Is this correct? Are these not UTC? - The INSTRUMENT_HOST_NAME does not agree with the name in the catalog file. - How can OBSERVATION_TIME and EXPOSURE_DURATION be known, but START_TIME and STOP_TIME are "N/A"? - OBSERVER_FULL_NAME is actually two names (should be two separa values WITHOUT initial), and is not the same two names mentioned in the DESCRIPTION field. Why the difference? - LINE_DISPLAY_DIRECTON and SAMPLE_DISPLAY_DIRECTION are missing from the IMAGE definition. If these are compliant FITS files, those keywords must be present because they have values other that the default for FITS images. - The FITS files contain telescope coordinates, but these have not been transferred to the PDS labels. /ctio ----- *.lbl - The NOTE contains two real numbers without explanation. They should be explained or omitted. - The label times end in "Z". Is this correct? Are these not UTC? - The INSTRUMENT_HOST_NAME does not agree with the name in the catalog file. - How can OBSERVATION_TIME and EXPOSURE_DURATION be known, but START_TIME and STOP_TIME are "N/A"? - OBSERVER_FULL_NAME is actually an abbreviation. - LINE_DISPLAY_DIRECTON and SAMPLE_DISPLAY_DIRECTION are missing from the IMAGE definition. If these are compliant FITS files, those keywords must be present because they have values other that the default for FITS images. - The FITS files contain telescope coordinates, but these have not been transferred to the PDS labels. /lick ----- *.lbl - As above /maunakea --------- *.lbl - As above /reunioni --------- *.lbl - As above um_po ===== - Why is there only a single subdirectory here? /mtsngltn - The DATA_SET_ID contains the object identifier 'C', for "Comet", but every data file in this directory has "IO" as it's target. Why the discrepancy? In fact, the data set description in the catalog file says this data set includes "various Jovian satellite", but I see only one - Io. - In fact, there does not seem to be a good correlation between what's in the data set catalog file description and what is present in this directory. - The NOTE says this is a "test of digitization," but doesn't say what was being digitized. - The first column description says the column contains "0's and 1's", but in fact the very first row contains "12328" in this column. - The first column description makes no sense to me. - The second column says the intensity is uncalibrated, but gives no other indication of what the number might represent. Is it a raw photon count? An instrumental unit? - Any idea why the first row contains odd-looking values in every .tab file?