Liens from the Cassini CDA data review. May 2, 2005 Participants: Steven Adams, Nicolas Altobelli, Mark Sykes, Carol Neese, David Lien, Ludmilla Kolokolova, Diane Connor, J.C. Liou, and Tyler Brown. The CDA team is responsible for resolving liens. Liens with an asterisk are not fully defined yet and will be discussed off-line to clarify what is to be done. Document directory ================== 1. Supply an ascii version of the SIS. This can (should) be a working html version to capture the formatting of the tabular information. (Diane will help Nicolas prepare this file.) 2. There will be a separate SIS for HRD. Modify the CDA SIS to indicate this. Catalog directory ================= 1. There will be a separate instrument cat for HRD. Modify the CDA instrument cat to indicate this. 2. Update the references throughout the delivery to reflect the newly published papers in the SSR. 3. Refer to the Srama instrument paper in the instrument catalog. 4. Reference information is distributed between projref.cat and cdaref.cat. Add to the description of catalog files referring to these references which ref.cat file contains its references. 5. Move the information in the errata.txt file describing which data are missing and will be supplied later to the confidence level note of the data set cat (cda.cat). Errata.txt should contain notice of known errors in the data (if any), but not missing data to be supplied later. *6. Talk off-line (Mark and Diane?) to determine whether start and stop times of the data set cat are to apply to the actual data presented or to the mission as a whole. 7. Revise dust.cat to include a list of sources such as interplanetary, interstellar, etc. 8. Add the pertinent information from the aareadme, such as the time range of the data and other descriptions of the data included, to the data set cat. 9. Add to the data set cat and to the aareadme, "As of the delivery date, the data set contains data from [specify mission phases], covering the time range [specify the time range]." 10. CDAINST.CAT instrument description has a typo: In the first sentence, spacecrafts --> spacecraft. Index directory =============== 1. CUMINDEX.TAB description listed twice in the INDXINFO.TXT file. Data directories ================ General: 1. Add information to datainfo.txt to describe what all the files are and what is in each of the subdirectories. Brief overview, just so a user will know how to find what they need. 2. The data in the subdirectories must be the same time range of data as in the impacts file and other higher level files. There should be a correspondence between the index number and the filenames in the subdirectories. 3. The team should select a single time format (either yyyy-doy or yyyy-mm-dd) and use only the one format in all instances. 4. For all data missing or yet to be supplied, this should be noted in the label of the affected data file, with an explanation of why it is missing and when it is expected to be supplied. For all data files/labels: *1. Discuss off-line whether time information should be provided in the filenames and whether the files are cumulative. 2. Use integer fields for all flags rather than character fields. 3. Start and stop times in labels should be changed to reflect the earlies and latest data in the file, out to hh:mm:ss. (Files containing non-time-constrained information about the instrument can continue to have NULL start and stop times.) CDAAREA 1. Add reference to the Srama paper to the main description to support the assertion of less than 10 percent variation. CDACOUNTER 1. Add a reference to a paper where the user can find more information about the counters. *2. Improve the description to explain what the counters keep track of and that the table represents changes to the counter values. We will need to figure out off-line what information is needed to clarify the description. CDAIMPACTS 1. Add appropriate reference to the main description file. 2. Clarify the description to show that the file includes all impacts, not just reliable ones. 3. For column 25, units should be AU instead of kilometers. 4. If considered reasonable by the team, and if the rise time uncertainty (column 17) will always be the same, this column could be omitted and the nominal error value noted in the description of the data column (column 16). 5. Column 13: "electron charge" --> "plasma electron charge" 6. Column 27, sub-saturn latitude, has all null values. Replace these with real appropriate values if possible. 7. Columns 32-33, detector RA and dec: Jitters around for a while but at a certain point stops jittering and stays at a constant value. Check whether this is indicative of any error, and if so, correct or document the problem. 8. A number of columns, including 38 and 42 but others as well, have a null value of -9.9E-99 or similar, but have many entries of 0. Make sure all null values are represented by the null value indicated in the label. *9. Talk off-line about assigning appropriate null values. We may want to suggest better null values. Mark and Nicolas will talk it over. 10. Column 40: This quality flag has not been defined yet. Nicolas will discuss with the team and with Mark what this flag will be used for, and change the description to reflect this. If the meaning of the flag is still TBD at the time the data are submitted, the column description should say this. 11. Column 45: Include a complete reference to the CDA flight software guide. Also clarify the description of this column. It says "downloaded" but it's not clear from where to to where. CDAPOINTINGS 1. Pointings jitter around but at some times stay at a constant value. Check whether this is indicative of any error, and if so, correct or document the problem. 2. In the main description, add a reference for the geometry. 3. Clarify the descriptions of columns 6, 7, 8, and 9 to show how they are derived and how they depend on the quaternion. The final description should be reviewed by the NAIF people for a sanity check (Boris Semenov via Steven Adams). 4. Add a reference to the main description to a paper giving the transformation from the quaternions to the ecliptic coordinates. Or include a description of the transformation. CDASETTINGS 1. Add reference to the Srama paper in the main description. 2. Check whether the settings values have been converted correctly. CDASPECTRA *1. All values of column 7 are zero. Nicolas will talk to Sasha about getting values for this column, or explaining why they are not there. 2. Replace the incrementing integers in the first column with a real event_id that correlates with those in the impacts file and in the filenames of the MP subdirectory. The data in CDASPECTRA should correspond with that in CDAIMPACTS and in the MP subdirectory. 3. Correct ROW (now equal to 1). 4. In main description, "twelve" should be "eleven". CDASTAT 1. Remove column 2, the local event time. 2. If the note column will never be used, it should also be removed. 3. Main description seems to imply that there is additional information somewhere about how the status changes will affect interpretation of the data. This is not so. Clarify the description. MPSIGNALS subdirectory 1. Columns 2 and 3 not yet generated. If this is an oversight, supply these data, otherwise document in the label description that it is yet to be supplied. 2. Column 2, flight time corrected with what? need explanation; include reference in column description. Expand explanation of corrected flight time noting play of offset time. In all the data subdirectories: 1. There is a column with AMPLITUDE in the name in all subdirectories, such as RECONSTRUCTED_QC_AMPLITUDE in the QCSIGNALS subdirectory. All these are to have the word AMPLITUDE changed to CHARGE. Apply this change also to all descriptions that mention these parameters. Standards liens from Steve Adams: 1. Labels are needed for the files in the document directory. 2. Steve Adams found problems in a number of the supporting files and sent emails with corrections and corrected files. These include AAREADME.TXT INDEXINFO.TXT CATINFO.TXT CDADS.CAT (replacement for CDA.CAT) DOCINFO.CAT Steve's emails with the corrections will be provided separately. end of liens.