Note. I can't remember what I said about the first EAICD review. AAREADME.TXT "The data set has been organized in various directories one level below the root" List them in alphabetical order. State contents for all directories. auxiliary data ((e.g. Fix multiple brackets The DTWG input files and the derived trajectory is archived within the Huygens DTWG data set. are archived VOLDESC.CAT Looks OK BROWSE/ All OK CATALOG/ CATINFO.TXT Why are files not listed in alphabetical order? DATASET.CAT The archive team does not intend to maintain such a sotfware. Sotfware is spelt incorrectly and does "a software" mean anything? INSTRUMENT.CAT The number of characters per line in this file seems larger than in other files. Is this OK? the the official Double the should be fixed PST Define on first use in this file. Project Science Team? (HASI)accelerometers Insert space at an altitude of about 160 km Make double space between of and about single space the DTWG by the PSA Make double space between DTWG and by single space Should PSA (Planetary Science Archive) be PST (Project Science Team)? HUY_DTWG_INITIAL_STATE Which directory is this file in? I couldn't find this file. Huygens Probe Initial Conditions and Event File (also in the form of a NAIF text kernel) which is also archived Which file in the archive should I look at to find this information? spacecraft(referred to as the space problem INSTRUMENT_HOST.CAT descent of the DM to the surface. The FRSS supporting structure Unusual space at the end of one line of text that isn't the usual paragraph break See MISSION.CAT for example of usual paragraph break RF data link and of the descent camera's image-taking. The DCSS is activated Same unusual space at end of line link is replaced by umbilical connections.) The CDMS has two primary functions Same unusual space at end of line Processor Valid function. TM/TC management is based Same unusual space at end of line approach. In addition to conventional Same unusual space at end of line except the MTU are turned off and the Probe is separated. During the coast phase Same unusual space at end of line on both CDMUs. The timer then returns to a standby mode. The two g-switches Same unusual space at end of line Oscillator (RUSO) on the Orbiter. The PDRS electrical architecture Same unusual space at end of line Other examples exist, but I've stopped listing them MISSION.CAT atmosphere and surface of Titan. It entered the upper atmosphere protected by a heat shield, then deployed parachutes to descend slowly to the surface Blank line inserted for no reason PERSONNEL.CAT Looks OK REFERENCE.CAT Incomplete JONES&GIOVAGNOLI1997 in INSTRUMENT_HOST.CAT JPLD-5564 in MISSION.CAT SOFT.CAT Looks OK TARGET.CAT Date is 20-01-06. Should this be 2006-01-06 or similar? Date also like this in REFERENCE.CAT and VOLDESC.CAT DOCUMENT/ DOCINFO.TXT Looks OK EAICD.LBL Looks OK EAICD.DOC Looks OK EAICD.TXT ASCII version of the EAICD to be provided. This file is incomplete EAICD.PDF Looks OK EXPERIMENTER_TO_DTWG_ICD.LBL Looks OK EXPERIMENTER_TO_DTWG_ICD.PDF Looks OK EXPERIMENTER_TO_DTWG_ICD.DOC Looks OK KAZEMINEJAD_PHD_THESIS.LBL Replace "e ort" with "effort"? RULES_OF_THE_ROAD.LBL Looks OK RULES_OF_THE_ROAD.TXT Looks OK SIMULATED_DATA_SET2004.LBL Looks OK SIMULATED_DATA_SET2004.PDF Looks OK EXTRAS/BSP_FILE/ A LBL file for this .bsp file would be helpful EXTRINFO.TXT This folder contains a ZIP file with all the routines of the DTWG software. State that these are Fortran 90 routines. The list of files is: List them in alphabetical order please Some of the filenames are incorrect. I haven't looked at any of the input files. GEOMETRY/ GEOMINFO.TXT Looks OK 030312_LS_NAIF0007.LBL Looks OK 030312_LS_NAIF0007.TXT Looks OK 030312_PCK.LBL Looks OK 030312_PCK.TXT Header of this file says "Test Only!" That does not give the data user confidence in the file EVENT_FILE_06062006.LBL Looks OK EVENT_FILE_06062006.TXT Excellent INDEX/ INDXINFO.TXT Doesn't mention the BROWSE_INDEX.LBL/TXT files INDEX.LBL Looks OK INDEX.TAB Looks OK BROWSE_INDEX.LBL Looks OK BROWSE_INDEX.TAB Looks OK DATA/ HUY_DTWG_DESCENT_POS.LBL NAME = "ATMOSPHERIC_PRESSURE_ERROR" Description for this object is missing Order of name, unit, etc for this object is unusual HUY_DTWG_DESCENT_POS.TAB Looks OK HUY_DTWG_DESCENT_VEL.LBL Several objects don't have descriptions NAME = DESC_VEL_ERROR Description is incorrect HUY_DTWG_DESCENT_VEL.TAB Should the 15 or so lines of preamble be listed here or not? I think they are an unnecessary duplication of the .LBL file. Do they correspond to the PDS formatting rules? Why is the uncertainty in descent velocity almost as large as the absolute value of the descent velocity? eg, -38.07962584 and 3.7772E+01 in the first line. Why does HUY_DTWG_DESCENT_VEL.TAB start at 64s and HUY_DTWG_DESCENT_POS.TAB start at 0s? That will confuse users unless explained. HUY_DTWG_ENTRY_AERO.LBL Several objects don't have descriptions Several objects (dimensionless numbers) don't have units that state "dimensionless" NAME = "KNUDSEN FREESTR. HARD SPHERE NR. [=2.8351E-8/RHO]" What are the units for RHO in this name? NAME = "DRAG COEFFICIENT CD " The DTWG know the difference between CD and CA, the axial force coefficient, so I expect they have labelled this does mean CD, not CA. Just checking. If it is CD, then presumably the DTWG has calculated the angle of attack. Do you want to archive the angle of attack in this file as well? HUY_DTWG_ENTRY_AERO.TAB Looks OK HUY_DTWG_ENTRY_EME2000_POS.LBL Looks OK HUY_DTWG_ENTRY_EME2000_POS.TAB Where are the uncertainties? When does entry/descent transition occur? INSTRUMENT.CAT says that entry stops at T0. If so, why does HUY_DTWG_ENTRY_EME2000_POS.TAB stop at 1074.816 s after T0? HUY_DTWG_DESCENT_POS.TAB starts at T0. Is there any overlap between the entry and descent data products? If so, that is very confusing. Descent position is in z, lat, lon Entry position is in EME x, y, z This is confusing for the data user. Please use the same frame for both. Wait - I've found HUY_DTWG_ENTRY.LBL which gives entry position in z, lat, lon frame. No problem. HUY_DTWG_ENTRY_EME2000_VEL.LBL Units are given as km, not km/s. Where are the uncertainties? HUY_DTWG_ENTRY_EME2000_VEL.TAB Looks OK I expect some data users to wonder why, if the DTWG can give a 3-D position, it can't give a 3-D velocity. An explanation would help them. HUY_DTWG_ENTRY.LBL What are the uncertainties in AoA and velocity? NAME = "ENTRY_INERTIAL_VEL" Units are stated incorrectly as km, not km/s. HUY_DTWG_ENTRY.TAB Where are the uncertainties? AoA is always zero. I presume this is because the DTWG has discarded the HASI PZR data. The .LBL file refers user to INSTRUMENT.CAT, so AoA=0 should be explained in this file as "HASI PZR data are no good". HUY_DTWG_ENTRY_MASS.LBL The order of name, unit, etc is not the same for all objects. HUY_DTWG_ENTRY_MASS.TAB Looks OK Conclusion: In your opinion, is this data set ready to be released to the scientific community? Some features of the DTWG archive need to be explained to data users, including the missing uncertainties and the entry/descent mismatch at T0 (see below), before this dataset is archived. List here the minor and editorial corrections (if any): 1) See lists above 2) 3) List here the major corrections (if any): 1) Uncertainties 2) Explain why entry/descent phases seem to overlap for 1000s after T0 There appears to be an 8km offset between these two at T0. Lat/Lon are different as well. This will confuse all data users. HUY_DTWG_DESCENT_POS.TAB 158965885.18400 0.00000 2005-01-14T09:10:20.999 2.75000000 146.57418000 195.94300000 -10.32600000 2.7500E-02 8.4704E+00 2.4000E-01 1.7000E-01 HUY_DTWG_ENTRY.TAB 158965885.18400 0.00000 2005-01-14T09:10:20.999 154.8167152 196.0778219 -10.3229124 0.0000000 321.2330581 0.0000000 0.0000000 0.0000000