a.sdu-a-navcam-2-edr-annefrank-v3.0/browse/png/aaimages.lbl b.sdu-a-navcam-3-rdr-annefrank-v1.0/browse/png/aaimages.lbl c.sdu-c-navcam-2-edr-wild2-v3.0/browse/png/aaimages.lbl d.sdu-c-navcam-3-rdr-wild2-v3.0/browse/png/aaimages.lbl - For ^PNG_DOCUMENT = ( ... ), I suggest using {} instead of (), for I mildly contend that the order does not matter. I argue the same even more mildly for the browse_htm.lbl that point to >1 browse000n.htm - This file is legal, but removing this file and putting its info in browse/browse_htm.lbl is more common a.sdu-a-navcam-2-edr-annefrank-v3.0/calib/nc_bck_shutter.lbl b.sdu-a-navcam-3-rdr-annefrank-v1.0/calib/nc_bck_shutter.lbl c.sdu-c-navcam-2-edr-wild2-v3.0/calib/nc_bck_shutter.lbl d.sdu-c-navcam-3-rdr-wild2-v3.0/calib/nc_bck_shutter.lbl (also for .../nc_fwd_shutter.lbl) Line 44: probably the second definition of HEADER should be deleted. a.sdu-a-navcam-2-edr-annefrank-v3.0/data/datainfo.txt b.sdu-a-navcam-3-rdr-annefrank-v1.0/data/datainfo.txt c.sdu-c-navcam-2-edr-wild2-v3.0/data/datainfo.txt d.sdu-c-navcam-3-rdr-wild2-v3.0/data/datainfo.txt line 138: "/DATA/ directory layout" doesn't reflect what was distributed, not "/DATA/EDR/APPROACH" but data/approach//_
a.sdu-a-navcam-2-edr-annefrank-v3.0/document/ b.sdu-a-navcam-3-rdr-annefrank-v1.0/document/ c.sdu-c-navcam-2-edr-wild2-v3.0/document/ d.sdu-c-navcam-3-rdr-wild2-v3.0/document/ nextnavcamflightlog.xls has no text version. Replace .xls with .csv? a.sdu-a-navcam-2-edr-annefrank-v3.0/extras/pdsdd_new.full b.sdu-a-navcam-3-rdr-annefrank-v1.0/extras/pdsdd_new.full c.sdu-c-navcam-2-edr-wild2-v3.0/extras/pdsdd_new.full d.sdu-c-navcam-3-rdr-wild2-v3.0/extras/pdsdd_new.full This doesn't matter too much since EN will modify the real dd, but for NAME = "SDU:TARGET_RIGHTUPOFFSETWRTLEFTBOT" 1) NAME = "DAWN:CALLAMP_DUTY" (the following line) seems left over, and 2) GENERAL_DATA_TYPE = REAL should probably be = INTEGER with a minimum value of 0 b.sdu-a-navcam-3-rdr-annefrank-v1.0/catalog/dataset.cat DATA_SET_NAME = "STARDUST NAVCAM CALIBRATED IMAGES OF ANNEFRANK" needs a version number e.di_ear-c-i0034-3-uh22m-tmpl1-v2.0/catalog/dataset.cat - Line 122: "in V1 of this dataset individual image names had followed the format: YYMMDD_###.FIT". Many files still follow this, while others follow "Image files names often follow the format: nX_10NNN.fit". More inconsistency: some are YYYYMMDD_###.fit, e.g. data/2005/UH20050117/stands/20050117_021.lbl - Line 131: "Included within the yearly directories for 1997, 1998, and 1999 is a table of astrometric measurements of 9P/Tempel 1." I didn't see such a file. e.di_ear-c-i0034-3-uh22m-tmpl1-v2.0/data/.../*.lbl - Undefined keywords below. These could be good to add permanently to the DD, but we're not doing that anymore for PDS3. Perhaps add prefix "DI:" or "EAR:"? DECLINATION_OFFSET OFFSET_DESC RIGHT_ASCENSION_OFFSET - every file has PRODUCT_ID = "1997_UH11_21_97_TEMPEL1_971121_029_FIT" That value must be unique per file. - Spacecraft data must have keywords SPACECRAFT_CLOCK_START_COUNT and _STOP_. MISSION_PHASE_NAME also helps for spacecraft data. Is this data entirely ground based? INSTRUMENT_HOST_NAME in every label is an earth-based observatory. But then why does DATA_SET_ID = "DI/EAR-..."? - Some files have the same START_TIME and STOP_TIME, even in subdir tempel1/, e.g. data/1998/UH19980122/tempel1/980122_114.lbl and .../n1_10114.lbl Those two files are similar - perhaps the main diff is FILTER_NAME. Can a user easily distinguish those two and other such pairs? e.di_ear-c-i0034-3-uh22m-tmpl1-v2.0/document/logsheets/* Text versions needed for all files. Replace .xls with .csv? e.di_ear-c-i0034-3-uh22m-tmpl1-v2.0/voldesc.cat ^INSTRUMENT_HOST_CATALOG = "OBS376T1HOST.CAT" ^INSTRUMENT_CATALOG = "I0034INST.CAT" The actual files do not have "HOST" or "INST", i.e. obs376t1.cat, i0034.cat f.nh-j_p_ss-spice-6-v1.0/catalog/spiceds.cat TARGET.CATs needed for these TARGET_NAME = "136108 HAUMEA" TARGET_NAME = "136472 MAKEMAKE" TARGET_NAME = "KERBEROS" TARGET_NAME = "STYX" f.nh-j_p_ss-spice-6-v1.0/data/ck/merged_nhpc_2007_v006.lbl MISSION_PHASE_NAME = "JUPITER": mission.cat says the correct value is "JUPITER ENCOUNTER" f.nh-j_p_ss-spice-6-v1.0/data/ik/nh_*.lbl PLATFORM_OR_MOUNTING_NAME = "NEW HORIZONS" is syntactically legal, but the typical values are more generic, e.g. "MAGNETOMETER BOOM" "METEOROLOGY BOOM ASSEMBLY" "PIONEER VENUS ORBITER" "PROBE DESCENT MODULE" "ROTOR" "SCAN PLATFORM" "SCIENCE BOOM" "SPACECRAFT" "SPACECRAFT BUS" "STATOR" plus every label that has this also has SPACECRAFT_NAME = "NEW HORIZONS" g.nh-x-lorri-2-launch-v2.0/document/pdsdd_insert_newhorizons.txt h.nh-x-lorri-3-launch-v2.0/document/pdsdd_insert_newhorizons.txt i.nh-j-lorri-2-jupiter-v2.0/document/pdsdd_insert_newhorizons.txt j.nh-j-lorri-3-jupiter-v2.0/document/pdsdd_insert_newhorizons.txt k.nh-x-rex-2-launch-v1.0/document/pdsdd_insert_newhorizons.txt l.nh-x-rex-3-launch-v1.0/document/pdsdd_insert_newhorizons.txt m.nh-j-rex-2-jupiter-v1.0/document/pdsdd_insert_newhorizons.txt n.nh-j-rex-3-jupiter-v1.0/document/pdsdd_insert_newhorizons.txt o.nh-x-rex-2-plutocruise-v1.0/document/pdsdd_insert_newhorizons.txt This file is fine, but you could ask EN to get its value into EN's pdsdd.full, then delete it. g.nh-x-lorri-2-launch-v2.0/document/samples/*_samples.lbl h.nh-x-lorri-3-launch-v2.0/document/samples/*_samples.lbl i.nh-j-lorri-2-jupiter-v2.0/document/samples/*_samples.lbl j.nh-j-lorri-3-jupiter-v2.0/document/samples/*_samples.lbl k.nh-x-rex-2-launch-v1.0/document/samples/*_samples.lbl l.nh-x-rex-3-launch-v1.0/document/samples/*_samples.lbl m.nh-j-rex-2-jupiter-v1.0/document/samples/*_samples.lbl n.nh-j-rex-3-jupiter-v1.0/document/samples/*_samples.lbl o.nh-x-rex-2-plutocruise-v1.0/document/samples/*_samples.lbl p.nh-x-rex-3-plutocruise-v1.0/document/samples/*_samples.lbl - For ^SAMPLE_ASCII_DOCUMENT = ( ... ), I suggest using {} instead of (), for I mildly contend that the order does not matter. g.nh-x-lorri-2-launch-v2.0/document/ h.nh-x-lorri-3-launch-v2.0/document/ i.nh-j-lorri-2-jupiter-v2.0/document/ j.nh-j-lorri-3-jupiter-v2.0/document/ k.nh-x-rex-2-launch-v1.0/document/ l.nh-x-rex-3-launch-v1.0/document/ m.nh-j-rex-2-jupiter-v1.0/document/ n.nh-j-rex-3-jupiter-v1.0/document/ o.nh-x-rex-2-plutocruise-v1.0/document/ p.nh-x-rex-3-plutocruise-v1.0/document/ lorri_ssr.pdf, lumineetal1995.pdf, payload_ssr.pdf, soc_inst_icd*.pdf need text versions. g.nh-x-lorri-2-launch-v2.0/data/, h.nh-x-lorri-3-launch-v2.0/data/ Mismatches with -lorri-3-, ie. one has a file the other has no equivalent for 20060424_000819/lor_0008194193_0x633_eng_1.lbl 20060904_001968/lor_0019687017_0x630_sci_2.lbl Mismatches with -lorri-3- only in the SOC version number 20061018_002350/lor_0023502552_0X630_* g.nh-x-lorri-2-launch-v2.0/catalog/dataset.cat DATA_SET_NAME = "NEW HORIZONS LORRI POST-LAUNCH CHECKOUT RAW V" needs a version number g.nh-x-lorri-2-launch-v2.0/data/20060224_000310/ 11 files in this directory have INST_CMPRS_TYPE = NOTCOMP, and I believe all 11 have near duplicates with INST_CMPRS_TYPE = LOSSLESS. Is this ok? g.nh-x-lorri-2-launch-v2.0/document/sample/lor_*.lbl Will these two datasets exist later? It doesn't matter much for samples. DATA_SET_ID = "NH-X-LORRI-2-PLUTOCRUISE-V1.0" or DATA_SET_ID = "NH-X-LORRI-3-PLUTOCRUISE-V1.0" h.nh-x-lorri-3-launch-v2.0/catalog/dataset.cat DATA_SET_NAME = "NEW HORIZONS LORRI POST-LAUNCH CHECKOUT CALIBRATED V" needs a version number h.nh-x-lorri-3-launch-v2.0/data/20060224_000310/ 11 labels in this directory have INST_CMPRS_TYPE = NOTCOMP, and I believe all 11 have near duplicates with INST_CMPRS_TYPE = LOSSLESS. Is this ok? Every other label beneath data/ has INST_CMPRS_TYPE = LOSSLESS. h.nh-x-lorri-3-launch-v2.0/document/sample/lor_*.lbl Will these two datasets exist later? It doesn't matter much for samples. DATA_SET_ID = "NH-X-LORRI-2-PLUTOCRUISE-V1.0" or DATA_SET_ID = "NH-X-LORRI-3-PLUTOCRUISE-V1.0" i.nh-j-lorri-2-jupiter-v2.0/catalog/dataset.cat DATA_SET_NAME = "NEW HORIZONS LORRI JUPITER ENCOUNTER RAW V" needs a version number i.nh-j-lorri-2-jupiter-v2.0/data/, j.nh-j-lorri-3-jupiter-v2.0/data/ Mismatches with -lorri-3-, ie. one has a file the other has no equivalent for 20070227_003490/lor_0034900454_0x630_sci_3.lbl 20070301_003504/lor_0035047836_0x633_sci_3.lbl 20070301_003509/lor_0035098514_0x630_sci_2.lbl Mismatches with -lorri-3- only in the SOC version number 20070224_003462/lor_0034623123_0x630_* 20070228_003496/lor_0034962321_0x630_* 20070228_003496/lor_0034962391_0x630_* 20070301_003504/lor_0035047626_* to lor_0035047989_* 20070301_003508/lor_0035088784_* to lor_0035092144_* i.nh-j-lorri-2-jupiter-v2.0/data/20070611_*/*.lbl All 4 labels in these 2 directories have near duplicates only in TELEMETRY_APPLICATION_ID = "0x630" or "0x636". Is this ok? i.nh-j-lorri-2-jupiter-v2.0/document/sample/lor_*.lbl Will these two datasets exist later? It doesn't matter much for samples. DATA_SET_ID = "NH-X-LORRI-2-PLUTOCRUISE-V1.0" or DATA_SET_ID = "NH-X-LORRI-3-PLUTOCRUISE-V1.0" j.nh-j-lorri-3-jupiter-v2.0/catalog/dataset.cat DATA_SET_NAME = "NEW HORIZONS LORRI JUPITER ENCOUNTER CALIBRATED V" needs a version number j.nh-j-lorri-3-jupiter-v2.0/data/20070611_*/*.lbl All 4 labels in these 2 directories have near duplicates only in TELEMETRY_APPLICATION_ID = "0x630" or "0x636". Is this ok? j.nh-j-lorri-3-jupiter-v2.0/document/sample/lor_*.lbl Will these two datasets exist later? It doesn't matter much for samples. DATA_SET_ID = "NH-X-LORRI-2-PLUTOCRUISE-V1.0" or DATA_SET_ID = "NH-X-LORRI-3-PLUTOCRUISE-V1.0" k.nh-x-rex-2-launch-v1.0/data/, l.nh-x-rex-3-launch-v1.0/data/ Mismatches with -rex-3-, ie. one has a file the other has no equivalent for none Mismatches with -rex-3- only in the SOC version number 20060419_000776/rex_0007761719_0x7b0_* 20060419_000776/rex_0007762619_0x7b1_* 20060419_000776/rex_0007762834_0x7b1_* 20060419_000776/rex_0007764419_0x7b1_* 20060419_000776/rex_0007764634_0x7b1_* 20060419_000776/rex_0007766219_0x7b1_* 20060419_000776/rex_0007766434_0x7b1_* 20060419_000776/rex_0007768019_0x7b1_* 20060419_000776/rex_0007768234_0x7b1_* 20060601_001149/rex_0011496719_0x7b1_* 20060601_001149/rex_0011497619_0x7b1_* 20060601_001149/rex_0011497835_0x7b1_* 20060601_001149/rex_0011499419_0x7b1_* 20060601_001149/rex_0011499635_0x7b1_* 20060601_001150/rex_0011501219_0x7b1_* 20060601_001150/rex_0011501435_0x7b1_* 20060601_001150/rex_0011503019_0x7b1_* 20060601_001150/rex_0011503235_0x7b1_* 20060601_001150/rex_0011504819_0x7b1_* 20060601_001150/rex_0011505035_0x7b1_* 20060601_001150/rex_0011506619_0x7b1_* 20060601_001150/rex_0011506835_0x7b1_* 20060601_001150/rex_0011508419_0x7b1_* 20060601_001150/rex_0011508635_0x7b1_* 20060601_001151/rex_0011510219_0x7b1_* 20060601_001151/rex_0011510435_0x7b1_* 20060601_001151/rex_0011512019_0x7b1_* 20060629_001389/rex_0013891462_0x7b1_* 20060629_001389/rex_0013893982_0x7b1_* 20060629_001389/rex_0013897248_0x7b1_* 20060629_001390/rex_0013900514_0x7b1_* 20060629_001390/rex_0013903780_0x7b1_* k.nh-x-rex-2-launch-v1.0/data/20060419/*.lbl 4422 labels in these directories have near duplicates with the same START_TIME and STOP_TIME but different INST_CMPRS_TYPE (NOTCOMP or LOSSLESS) and TELEMETRY_APPLICATION_ID (0x7b0 or 0x7b1). Is this ok? Every other label beneath data/ has INST_CMPRS_TYPE = NOTCOMP. Only 3 labels in this subdir have START_TIME that no other label has rex_0007754204_0x7b0_eng_1.lbl rex_0007754204_0x7b1_eng_1.lbl rex_0007768342_0x7b1_eng_1.lbl l.nh-x-rex-3-launch-v1.0/data/20060419/*.lbl 4415 labels in these directories have near duplicates with the same START_TIME and STOP_TIME but different INST_CMPRS_TYPE (NOTCOMP or LOSSLESS) and TELEMETRY_APPLICATION_ID (0x7b0 or 0x7b1). Is this ok? Every other label beneath data/ has INST_CMPRS_TYPE = NOTCOMP. o.nh-x-rex-2-plutocruise-v1.0/data/, p.nh-x-rex-3-plutocruise-v1.0/data/ Mismatches with -rex-3-, ie. one has a file the other has no equivalent for none Mismatches with -rex-3- only in the SOC version number 64 files total, e.g. 20110520_016820/rex_0168205940_0x7b1_* o.nh-x-rex-2-plutocruise-v1.0/data/20110520_016820/rex_0168205926_0x7b1_eng_1.* Running fv on the .fit file shows Index Extension Type Dimension 0 Primary Image 5088 1 I AND Q VALUES Binary 2 cols X 1250 rows 2 RADIOMETER AND TIME TAGS Binary 2 cols X 10 rows 3 HOUSEKEEPING_0x004 Binary 3 cols X 7 rows 4 HOUSEKEEPING_0x016 Binary 6 cols X 7 rows 5 HOUSEKEEPING_0x084 Binary 3 cols X 7 rows 6 HOUSEKEEPING_0x096 Binary 6 cols X 7 rows 7 THRUSTERS Binary 28 cols X 0 rows 8 SSR SECTOR HEADERS Image 336 However, the .lbl file does not have #6. The problem might be that EXTENSION_SSR_SH_HEADER is defined twice. Other labels may have this problem. This file was chosen randomly. o.nh-x-rex-2-plutocruise-v1.0/index/index.tab Must list the labels in data/tnf/ even if fields in index.tab are blank. p.nh-x-rex-3-plutocruise-v1.0/index/index.tab Must list the labels in data/tnf/ even if fields in index.tab are blank.